GF Pre Acp Eng PDF

Preface, Table of Contents
Protocol Element 1
SICAM RTUs • Ax 1703
Architecture and Data Flow 2
Common Functions Point-to-Point Traffic (BPP) 3
Multi-Point Traffic (UMP) 4
Protocol Elements
Interfacing of Protective Devices (103) 5
SICAM RTUs Field Bus (SFB) 6
Dial-Up Traffic (DIA) 7
LAN Communication (104) 8
LAN Communication (61850) 9
SNMPv3 Agent 10
PRP 11
NTP/SNTP 12
Remote Operation for SICAM
TOOLBOX II (LAN/WAN) 13
Internet Protocol Family A
Literature
Unrestricted DC0-023-2.12
Note
Please observe Notes and Warnings for your own safety in the Preface.
Disclaimer of Liability Copyright

Although we have carefully checked the contents of this publication Copyright © Siemens AG 2017
for conformity with the hardware and software described, we cannot The reproduction, transmission or use of this document or its
guarantee complete conformity since errors cannot be excluded. contents is not permitted without express written authority.
The information provided in this manual is checked at regular Offenders will be liable for damages. All rights, including rights
intervals and any corrections that might become necessary are created by patent grant or registration of a utility model or design,
included in the next releases. Any suggestions for improvement are are reserved.
welcome.
Subject to change without prior notice.
Document Label: SICRTUs-GFPREACP-ENG_V2.12
Release date: 2016-06-08
Unrestricted
Siemens AG Order no.: DC0-023-2.12
Preface
This document is applicable to the following product(s):
· SICAM RTUs
· Ax 1703
Purpose of this manual
This manual describes the function and mode of operation of system element-overlapping
services and basic system elements, that are supported on the platform SICAM RTUs.
Target Group and Safety Instructions
The document you are reading right now is addressed to users, who are in charge of the
following engineering tasks:
· Conceptual activities, as for example design and configuration
· System parameterization and system diagnostic, using the designated engineering tools
· Technical system maintenance
Above applies, as far as these tasks do not involve manipulations of the hardware.
Manipulating the hardware itself, as for example "unplugging" and "plugging" printed circuit
boards and modules, or working on terminals and/or connectors – for instance when applying
changes to the wiring – are – also if they are an issue in the context of configuration,
parameterization and diagnostic – not subject of this document.
Attention
For activities, which comprise hardware manipulations, it is essential to pay attention to the
appropriate safety instructions and to strictly adhere to the appropriate safety regulations.
Unrestricted SICAM RTUs • Ax 1703, Common Functions Protocol Elements 3

DC0-023-2.12, Edition 06.2017
Preface
Conventions Used
In this document, reference is often made to important information, notifications and

limitations. For clarification, the following conventions are thereby adhered to.
Note
Is an important note concerning characteristic or application of the described function.
Attention
Provides information and explanations, the non-observance of which can lead to faulty
behavior of the system.
technical term, phrase, or function designation This syntax, for the purpose of easier
readability, identifies a term (also consisting
of several words), a phrase, or a function
designation
The following syntax identifies a parameter or a parameter group. The context in which the
syntax is used shows whether it refers to a parameter or to a parameter group.
<parameter group> | <parameter Parameter (qualified reference, includes

group> | <parameter> "path")
Time management | Daylight saving

time | Daylight saving time
enabling
<parameter group> | <parameter Parameter group (qualified reference,
group | *> includes "path")
Time management | Daylight saving

time
<parameter> Parameter
Daylight saving time enabling

IEC_Enable
<parameter group | *> Parameter group
Daylight saving time

<parameter_*> A parameter name that ends with "_*", as
for example Inversion_*, can mean one
or all of the following (uniqueness results
from context):
Inversion
Inversion_0
Inversion_1
etc.
# "#" in a parameter group or in a parameter
in a <parameter group | *> or corespond a number between 0 to 9, as for
in a <parameter> example
PRE# … PRE0, PRE1

S#_U4_min … S0_U4_min, S1_U4_min
etc.
Unrestricted 4 SICAM RTUs • Ax 1703, Common Functions Protocol Elements

Edition 06.2017, DC0-023-2.12
Preface
Several fundamental terms
Spontaneous A spontaneous information object is an object, which with change is

Information Object transmitted spontaneously in a message, and is used for the
exchange of a process signal or a derived information (including
Status) between the system elements of the particular automation
unit, another automation unit or a control system.
A spontaneous information object is always transmitted individually
and normally has a time tag, in order to be able to establish a
chronologically consistent interrelationship later.
Message A message is used for the spontaneous transmission of process-

and system information. A message contains a spontaneous
information object, the address for the unambiguous identification of
the information, type identification and additional information
necessary for the transmission (e.g. length of the message)
Placement in the Information Landscape
Document Item Number

SICAM RTUs Platforms Configuration Automation Units and Automation DC0-021-2
Networks
SICAM RTUs Interoperability IEC 60870-5-101/104 DC0-013-2
SICAM RTUs IEC60870-5-101/104 Interoperability Certified DC0-131-2
Ax 1703 Interoperability IEC 60870-5-101/104 DA0-046-1
SICAM RTUs Interoperability IEC 60870-5-103 DC0-026-2
Ax 1703 Interoperability IEC 60870-5-103 DA0-063-1
Administrator Security Manual DC0-115-2

DC0-023-2.12, Edition 06.2017
Preface

Edition 06.2017, DC0-023-2.12
Table of Contents
1 Protocol Element......................................................................................................... 19
1.1 Overview ........................................................................................................ 20
2 Architecture and Data Flow ........................................................................................ 21
2.1 Protocol Structure........................................................................................... 22

2.1.1 Protocols according to IEC 60870-5-101/103 ............................................. 22
2.1.2 Protocols according to IEC 60870-5-104 .................................................... 23
2.1.3 Protocols according to IEC 61850 .............................................................. 24
2.2 Data Flow of Process Information ................................................................... 25
3 Point-to-Point Traffic (BPP) ........................................................................................ 27
3.1 Introduction .................................................................................................... 28

3.2 Communication according to IEC 60870-5-101 ............................................... 34
3.2.1 Data Transmission Procedure.................................................................... 34
3.2.1.1 Acknowledgement Procedure ............................................................... 34
3.2.2 Station Initialization.................................................................................... 35
3.2.3 Acquisition of Events (transmission of data ready to be sent) ..................... 35
3.2.4 General Interrogation, Outstation Interrogation........................................... 36
3.2.5 Clock Synchronization ............................................................................... 37
3.2.6 Command Transmission ............................................................................ 38
3.2.6.1 Control Location ................................................................................... 38
3.2.6.2 Control Location Check ........................................................................ 38
3.2.6.3 Set Control Location ............................................................................. 39
3.2.7 Transmission of Integrated Totals .............................................................. 40
3.2.8 File Transfer .............................................................................................. 40
3.2.9 Acquisition of Transmission Delay ............................................................. 40
3.3 Optimized Parameters for selected Transmission Facilities ............................. 41
3.4 Function for the Support of Redundant Communication Routes ...................... 45
3.4.1 Redundancy Mode "1703-Redundancy"..................................................... 45
3.4.2 Redundancy Mode "Norwegian User Conventions (NUC)" ......................... 47
3.4.3 Deactivation of Interface ............................................................................ 48
3.5 Message Conversion ...................................................................................... 49
3.5.1 Blocking .................................................................................................... 49
3.5.2 Special Functions ...................................................................................... 50
3.5.2.1 Summer Time Bit = 0 for all Messages in Transmit Direction ................. 50
3.5.2.2 Day of Week = 0 for all Messages in Transmit Direction ........................ 50
3.5.2.3 Originator Address = 0 for all Messages in Transmit Direction............... 51
3.5.2.4 WhiteList Filter...................................................................................... 51
3.5.2.4.1 Sample Applications ........................................................................ 53
3.5.2.4.2 Profile Definition: “White-List Filter” .................................................. 58
3.5.2.4.3 Profile Definition: “SICAM RTUs – IEC101” ...................................... 62

DC0-023-2.12, Edition 06.2017
Table of Contents
3.5.2.5 Data Throughput Limitation................................................................... 65

3.5.2.6 Convert General Interrogation Command in Receive Direction to
BROADCAST ....................................................................................... 66
3.5.2.7 Non Interruptible GI .............................................................................. 66
3.5.2.8 Emulate ACTCON+ for Clock Synchronization Command ..................... 66
3.5.2.9 Emulate ACTCON+/- for Commands .................................................... 67
3.5.2.10 Emulate ACTCON+ for Commands ...................................................... 68
3.5.2.11 Emulate ACTCON, ACTTERM for Commands with Control Messages.. 69
3.5.2.12 Compatibility TCS100 ........................................................................... 70
3.5.2.13 Settings for Project DBAG .................................................................... 70
3.5.2.14 Settings for Project RWE ...................................................................... 72
3.5.2.14.1 NT-Bit, IV-Bit according to RWE Requirements ................................ 72
3.6 Transparent Mode (Tunneling, Container Mode) ............................................. 73
3.7 Protocol Element Control and Return Information ........................................... 76
3.7.1 Protocol Element Control ........................................................................... 77
3.7.2 Protocol Element Return Information ......................................................... 80
4 Multi-Point Traffic (UMP)............................................................................................. 83
4.1 Introduction .................................................................................................... 84

4.2.1 Data Acquisition by Polling (Station Interrogation) ...................................... 90
4.2.1.1 Continuous Interrogation of a Remote Terminal Unit ............................. 94
4.2.1.2 Acknowledgement Procedure ............................................................... 94
4.2.1.3 Failure Monitoring in the Master Station ................................................ 95
4.2.1.4 Failure Monitoring in the Remote Terminal Unit .................................... 96
4.2.2 Station Initialization.................................................................................... 97
4.2.3 Acquisition of Events (transmission of data ready to be sent) ..................... 97
4.2.3.1 Message from the Remote Terminal Unit to the Master Station ............. 98
4.2.4 General Interrogation, Outstation Interrogation .......................................... 99
4.2.5 Clock Synchronization ............................................................................. 100
4.2.6 Command Transmission .......................................................................... 101
4.2.6.1 Message from the Master Station selectively to a Remote Terminal Unit101
4.2.6.2 Control Location ................................................................................. 102
4.2.6.3 Control Location Check ...................................................................... 102
4.2.6.4 Set Control Location ........................................................................... 103
4.2.6.5 Message from the Master Station to all Remote Terminal Units
(unacknowledged) .............................................................................. 103
4.2.7 Transmission of Integrated Totals ............................................................ 104
4.2.8 Acquisition of Transmission Delay ........................................................... 104
4.3 Optimized Parameters for selected Transmission Facilities ........................... 105
4.4 Co-ordination of Several Masters.................................................................. 115
4.5 Standby Transmission Line over the Public Telephone Network (PSTN) ....... 117
4.6 Data Transmission using Time Slot Radio..................................................... 120
4.7 Data Transmission in Relay Operation "Multi-Point Traffic with Routing" ....... 121
4.7.1 Main and Standby Transmission Line ...................................................... 126

Edition 06.2017, DC0-023-2.12
Table of Contents
4.7.2 Routing Method ....................................................................................... 127

4.7.2.1 Non-optimized Routing Method........................................................... 128
4.7.2.2 Optimized Routing Method ................................................................. 129
4.8 Function for the Support of Redundant Communication Routes .................... 130
4.8.1 Redundancy Mode "1703-Redundancy"................................................... 130
4.8.2 Redundancy Mode "Norwegian User Conventions (NUC)" ....................... 132
4.9 Message Conversion .................................................................................... 134
4.9.1 Blocking .................................................................................................. 134
4.9.2 Class 1, 2 Data ........................................................................................ 135
4.9.3 Special Functions .................................................................................... 136
4.9.3.1 Summer Time Bit = 0 for all Messages in Transmit Direction ............... 136
4.9.3.2 Day Of Week = 0 for all Messages in Transmit Direction ..................... 136
4.9.3.3 Originator Address = 0 for all Messages in Transmit Direction............. 137
4.9.3.4 Send GI Data as Class 1 Data ............................................................ 137
4.9.3.5 Send End of Init Message as Class 1 Data ......................................... 137
4.9.3.6 Send ACTCON, ACTTERM Message as Class 1 Data........................ 137
4.9.3.7 Non Interruptible GI ............................................................................ 138
4.9.3.8 Timeout Monitoring for GI Data ........................................................... 138
4.9.3.9 Convert General Interrogation Command to BROADCAST in Receive
Direction ............................................................................................. 138
4.9.3.10 Do not store General Interrogation Commands in Receive Direction ... 138
4.9.3.11 Emulate ACTCON+ for Clock Synchronization Command ................... 139
4.9.3.12 Emulate ACTCON+/- for Commands .................................................. 139
4.9.3.13 Emulate ACTCON+ for Commands .................................................... 140
4.9.3.14 Message Synchronization ................................................................... 141
4.9.3.15 Filtering of Measured Values with COT=3 in Transmit Direction .......... 141
4.10 Transparent Mode (Tunneling)...................................................................... 142
4.11 Protocol Element Control and Return Information ......................................... 145
4.11.1 Protocol Element Control ......................................................................... 146
4.11.2 Protocol Element Return Information ....................................................... 149
5 Interfacing of Protective Devices (103) .................................................................... 153
5.1 Introduction .................................................................................................. 154

5.2 Communication according to IEC 60870-5-103 ............................................. 159
5.2.1 Data Acquisition by Polling (Station Interrogation) .................................... 159
5.2.1.1 Continuous Interrogation of a Remote Terminal Unit ........................... 162
5.2.1.2 Acknowledgement Procedure ............................................................. 162
5.2.1.3 Failure Monitoring in the Master Station .............................................. 163
5.2.1.4 Failure Monitoring in the Remote Terminal Unit................................... 164
5.2.2 Station Initialization.................................................................................. 164
5.2.3 Acquisition of Events (transmission of data ready to be sent) ................... 166
5.2.3.1 Message from the Remote Terminal Unit to the Master Station ........... 166
5.2.3.2 Test Mode .......................................................................................... 166
5.2.4 General Interrogation, Outstation Interrogation......................................... 167

DC0-023-2.12, Edition 06.2017
Table of Contents

(unacknowledged) .............................................................................. 170
5.2.8 File Transfer ............................................................................................ 171
5.2.8.1 Transfer of Disturbance Records to SICAM DISTO ............................. 172
5.2.8.2 Transfer of Disturbance Records to IEC 60870-5-101/104 Systems .... 177
5.3 Transfer of Parameters for Reyrolle Protection Equipment ............................ 179
5.5.2 Redundancy Mode "Main-/Backup transmission line with 2 interfaces" ..... 190
5.5.3 Deactivation of Interface .......................................................................... 192
5.6.1 Message Conversion IEC 60870-5-101 <-> IEC 60870-5-103 .................. 194
5.6.2 Message Conversion IEC 60870-5-101 <-> IEC 60870-5-101 .................. 213
5.6.3 Message Conversion IEC 60870-5-101 <-> IEC 60870-5-103 (101) ......... 214
5.6.4 Blocking .................................................................................................. 215
5.6.5 Class 1, 2 Data ........................................................................................ 215
5.6.6.1 Send Short Circuit Location Values with GI ......................................... 216
5.6.6.2 Resetting the Short Circuit Location Values ........................................ 216
5.6.6.2.1 Reset the Short Circuit Location Values with Command ................. 217
5.6.6.2.2 Reset Short Circuit Location Values automatically.......................... 217
5.6.6.3 Signaling / Measured Value Disabling ................................................. 218
5.6.6.4 Technological Adaptation for Measured Values .................................. 218
5.6.6.5 Measured Value Change Monitoring ................................................... 220
5.6.6.6 Monitoring Intermediate and Faulty Positions of Double-Point Information222
5.6.6.7 Transfer of the Information "Blocked Activation/Tripping of the Protection"223
5.6.6.8 Transmit Non-Updated Process Images ............................................. 225
5.6.6.9 Emulation of the Going Binary Information [Master only] ..................... 225
6 SICAM RTUs Field Bus (SFB) ................................................................................... 233
6.1 Introduction .................................................................................................. 234

6.2 Communication ............................................................................................ 236

Edition 06.2017, DC0-023-2.12
Table of Contents

6.2.1.4 Failure Monitoring in the Remote Terminal Unit................................... 239
(unacknowledged) .............................................................................. 242
6.5.1 Blocking .................................................................................................. 248
6.5.2 Class 1, 2 Data ........................................................................................ 248
7 Dial-Up Traffic (DIA) .................................................................................................. 255
7.1 Introduction .................................................................................................. 256

7.2 Control of Connection Setup and Disconnection ........................................... 258
7.2.1 Security for Dial-Up Traffic ....................................................................... 259
7.2.1.1 Telephone Number Concept ............................................................... 259
7.2.1.2 Communication Protocol ..................................................................... 260
7.2.1.3 Scrambling ......................................................................................... 260
7.2.1.4 Identification of the Calling Station ...................................................... 260
7.2.1.5 Authentication (Protection against not permitted access) .................... 261
7.2.1.5.1 Authentication with Password ........................................................ 262
7.2.1.5.2 Authentication with Password + Keys for SICAM RTUs .................. 262
7.2.1.5.3 Authentication with Password + Keys for 3 rd Party Systems ........... 263
7.2.2 Connection Establishment spontaneously and cyclically, Controlling Station
<-> Controlled Station .............................................................................. 263
7.2.2.1 Cyclic Connection Setup at a settable Interval (monitoring cycle) ........ 269
7.2.3 Connection Setup Control via Modem Commands ................................... 271
7.2.3.1 AT-Hayes ........................................................................................... 271
7.2.3.2 AT-Hayes (ETSI) ................................................................................ 272
7.2.3.3 V.25bis ............................................................................................... 272
7.2.3.4 X.20 ................................................................................................... 272
7.2.3.5 X.28 ................................................................................................... 272

DC0-023-2.12, Edition 06.2017
Table of Contents
7.2.3.6 Arbitrary Main Telephone Number in a Telephone Network (PSTN) .... 273
7.2.4 Access Control (LOGIN with Password + Access Key)............................. 276
7.2.5 Disconnection Control ............................................................................. 277
7.3 Communication with existing Connection according to IEC 60870-5-101....... 280
7.3.1.4 Failure Monitoring in the Remote Terminal Unit .................................. 283
7.3.4 General Interrogation, Outstation Interrogation ........................................ 284
(unacknowledged) .............................................................................. 288
7.3.8 Acquisition of Transmission Delay ........................................................... 288
7.4 SMS Messages ............................................................................................ 289
7.5 Co-ordination of several Masters in "Multi-Master Mode" .............................. 290
7.6 Standby Transmission Line(s) over Standby Telephone Number(s) .............. 291
7.7 Multi-Hierarchical Configurations .................................................................. 292
7.8 Standby Transmission Line via Dial up Traffic ............................................... 293
7.9.1 Supported Combinations for Dial-Up Modems ......................................... 305
7.9.2 ASCII Mode ............................................................................................. 308
7.9.3 CRC Generator Polynomial ..................................................................... 309
7.10 Toll-Saving Transmission Strategies ............................................................. 310
7.11 Having a Telephone Set Connected in Parallel ............................................. 311
7.12 Functions for supporting Redundant Communication Routes ........................ 312
7.13.1 Blocking .................................................................................................. 313
7.13.2 Class 1, 2 Data ........................................................................................ 313

Edition 06.2017, DC0-023-2.12
Table of Contents
8 LAN Communication (104) ........................................................................................ 325
8.1 Introduction .................................................................................................. 326

8.2 LAN/WAN Communication according to IEC 60870-5-104 ............................ 331
8.2.1 Layer Model – General Information about the Protocols used................... 331
8.2.2 Ethernet Interface .................................................................................... 332
8.2.3 Definition of the Connections ................................................................... 333
8.2.3.1 Data Transmission Procedure............................................................. 344
8.2.3.3 Failure Monitoring ............................................................................... 348
8.2.7.1 Clock Synchronization Command ....................................................... 353
8.2.7.2 Network Time Protocol (NTP/SNTP) according RFC 1305 .................. 353
8.2.8.1 Command Transfer Monitoring (Dwell Time Monitoring) ...................... 354
8.2.8.2.1 Control Location Check.................................................................. 355
8.2.8.2.2 Set Control Location ...................................................................... 356
8.3.1 PSI-Redundancy (Synchronous Connections) ......................................... 358
8.3.2 104-Redundancy ..................................................................................... 361
8.3.2.1 104-Redundancy with 1 Ethernet Interface.......................................... 361
8.3.2.2 104-Redundancy with 2 Ethernet Interfaces ........................................ 364
8.3.4 Deactivation of Interface .......................................................................... 368
8.4 Dual-LAN Interface (DNIP) ........................................................................... 369
8.4.1.1 Switch Mode....................................................................................... 370
8.4.1.2 Line Mode (Siemens specific) ............................................................. 372
8.4.1.3 RSTP Mode........................................................................................ 373
8.4.1.4 Single Mode ....................................................................................... 374
8.4.1.5 Single + Service Mode ........................................................................ 374
8.5.1 Blocking .................................................................................................. 375
8.5.2.1 Summer Time Bit = 0 for all Messages in Transmit Direction ............... 376
8.5.2.2 Day of Week = 0 for all Messages in Transmit Direction ...................... 376
8.5.2.3 Time stamp (IV=1) in Messages in Transmit Direction......................... 376
8.5.2.4 Originator Address = 0 for all Messages in Transmit Direction............. 377
8.5.2.5 WhiteList Filter.................................................................................... 377
8.5.2.5.1 Sample Applications ...................................................................... 379
8.5.2.5.2 Profile Definition: “White-List Filter” ................................................ 384

DC0-023-2.12, Edition 06.2017
Table of Contents
8.5.2.5.3 Profile Definition: “SICAM RTUs – IEC104” .................................... 388

8.5.2.5.4 Profile Definition: “IEC60870-5-104 Ed.2”....................................... 391
8.5.2.6 Data Throughput Limitation................................................................. 394
8.5.2.7 Settings for Project DBAG .................................................................. 396
8.5.2.8 Settings for Project RWE .................................................................... 398
8.5.2.8.1 Bit by Bit Marking of the Field ........................................................ 398
8.5.2.8.2 Cyclic Measured Values ................................................................ 399
8.5.2.8.3 Address of the Return Information for Selection Command ............ 401
8.5.2.8.4 NT-Bit, IV-Bit according to RWE Requirements .............................. 402
8.7 Security Logging........................................................................................... 407
8.8 Web Server .................................................................................................. 408
9 LAN Communication (61850) .................................................................................... 411
9.1 Introduction .................................................................................................. 412

9.2 LAN Communication over Ethernet TCP/IP according to IEC 61850 ............. 420
9.2.1 Objects and Data..................................................................................... 425
9.2.1.1 Data Models ....................................................................................... 425
9.2.1.1.1 Physical Device [IED] .................................................................... 425
9.2.1.1.2 Logical Device [LD] ........................................................................ 425
9.2.1.1.3 Logical Node [LN] .......................................................................... 426
9.2.1.1.4 Data Class, Data ........................................................................... 436
9.2.1.1.5 Basic data types [CDC = Common Data Class] .............................. 437
9.2.2 Definition of the Connections ................................................................... 439
9.2.2.1 Data Transmission Procedure............................................................. 444
9.2.2.2 Failure Monitoring............................................................................... 445
9.2.4 Acquisition of Events (Transmission of Data Ready to be Sent) ............... 446
9.2.4.1 Data Transmission Server <-> Client .................................................. 446
9.2.4.1.1 Reports/Report Control Block ........................................................ 447
9.2.4.1.2 Unbuffered/Buffered Reports ......................................................... 447
9.2.4.1.3 Static/Dynamic Datasets ................................................................ 448
9.2.4.1.4 Setting Group Control Model.......................................................... 448
9.2.4.2 Data Transmission Server <-> Server with "GOOSE" [Server only] ..... 449
9.2.5 General Interrogation, Outstation Interrogation ........................................ 453
9.2.6.1 Network Time Protocol (NTP) ............................................................. 454
9.2.7.1 Control Model ..................................................................................... 456
9.2.7.1.1 Command Output Time (QU) ......................................................... 456
9.2.7.1.2 Causes of Transmission (origin)..................................................... 457
9.2.7.1.3 Command Termination .................................................................. 458

Edition 06.2017, DC0-023-2.12
Table of Contents
9.2.7.1.4 1-Out-Of-n Check [Server only] ..................................................... 459

9.2.7.1.5 Converting EXECUTE (104) à SELECT/EXECUTE (61850) [Client
only] .............................................................................................. 459
9.2.7.1.6 LastApplError [Server only] ........................................................... 460
9.2.7.1.7 Monitoring ..................................................................................... 461
9.2.7.1.8 Direct Control with Normal Security................................................ 463
9.2.7.1.9 Direct Control with Enhanced Security ........................................... 464
9.2.7.1.10 SBO Control with Enhanced Security ............................................. 466
9.2.7.2 Control Location [Client only] ............................................................. 470
9.2.7.2.1 Control Location Check.................................................................. 471
9.2.7.2.2 Set Control Location ...................................................................... 471
9.2.9 File Transfer (Disturbance Records) ........................................................ 472
9.2.9.1 Transfer of Disturbance Records to SICAM DISTO ............................. 473
9.2.9.1.1 Sequence of the Disturbance Record Transmission (between Client
and Server).................................................................................... 474
9.2.9.2 Transmission of Disturbance Records [SICAM RTUs = Server] ........... 475
9.3.2 Server Redundancy ................................................................................. 477
9.3.3 GOOSE Redundancy .............................................................................. 478
9.4 Dual-LAN interface (DNIP)............................................................................ 480
9.4.1 Switch Mode............................................................................................ 481
9.4.2 Line Mode (Siemens specific) .................................................................. 483
9.4.3 RSTP Mode............................................................................................. 484
9.4.4 Single Mode ............................................................................................ 485
9.4.5 Single + Service Mode ............................................................................. 485
9.6.1 General ................................................................................................... 490
9.6.2 Conversion IEC 60870-5-101/104 ↔ IEC 61850 ...................................... 491
9.6.2.1 IEC 61850: Basic Types ..................................................................... 491
9.6.2.2 IEC 61850: Common ACSI Types....................................................... 492
9.6.2.2.1 IEC 61850: Time Quality ................................................................ 492
9.6.2.2.2 IEC 61850: Time Stamp................................................................. 492
9.6.2.3 IEC 61850: Common Data Attribute Types.......................................... 493
9.6.2.3.1 IEC 61850: Quality......................................................................... 493
9.6.2.3.2 IEC 61850: AnalogueValue ............................................................ 493
9.6.2.3.3 IEC 61850: Vector ......................................................................... 493
9.6.2.3.4 IEC 61850: Originator .................................................................... 494
9.6.2.3.5 IEC 61850: Step position with transient indication .......................... 495
9.6.2.4 Common Data Classes ....................................................................... 496
9.6.2.4.1 IEC 61850: Controllable Single Point (SPC) ................................... 500

DC0-023-2.12, Edition 06.2017
Table of Contents
9.6.2.4.2 IEC 61850: Controllable Double Point (DPC) ................................. 501

9.6.2.4.3 IEC 61850: Controllable Integer Status (INC) ................................. 502
9.6.2.4.4 IEC 61850: Controllable Enumerated Status (ENC) ....................... 503
9.6.2.4.5 IEC 61850: Controllable Integer Status (APC) ................................ 504
9.6.2.4.6 IEC 61850: Single Point Status (SPS)............................................ 505
9.6.2.4.7 IEC 61850: Double Point Status (DPS) .......................................... 506
9.6.2.4.8 IEC 61850: Integer Status (INS)..................................................... 507
9.6.2.4.9 IEC 61850: Enumerated Status (ENS) ........................................... 507
9.6.2.4.10 IEC 61850: Protection Activation Information (ACT) ....................... 508
9.6.2.4.11 IEC 61850: Directional Protection Activation Information (ACD) ..... 509
9.6.2.4.12 IEC 61850: Setting Group (SGCB) ................................................. 511
9.6.2.4.13 IEC 61850: Binary Counter Reading (BCR).................................... 512
9.6.2.4.14 IEC 61850: Binary Controlled Step Position Information (BSC) ...... 513
9.6.2.4.15 IEC 61850: Integer Controlled Step Position Information (ISC) ....... 514
9.6.2.4.16 IEC 61850: Analogue Setting (ASG) .............................................. 515
9.6.2.4.17 IEC 61850: Integer Setting (ING) ................................................... 516
9.6.2.4.18 IEC 61850: Measured Value (MV).................................................. 517
9.6.2.4.19 IEC 61850: Complex Measured Value (CMV) ................................ 518
9.6.2.4.20 IEC 61850: Sampled Value (SAV).................................................. 519
9.6.2.4.21 IEC 61850: Collection Of Measurands (WYE) ................................ 519
9.6.2.4.22 IEC 61850: Delta (DEL) ................................................................. 520
9.6.2.4.23 IEC 61850: Sequence (SEQ) ......................................................... 520
9.6.2.4.24 IEC 61850: Device Name Plate (DPL)............................................ 521
9.6.2.4.25 IEC 61850: Logical Node Name Plate (LPL) .................................. 521
9.6.2.5 Mapping IEC 61850 ® MMS .............................................................. 522
9.6.2.5.1 Extended Common Data Classes .................................................. 522
9.6.3 Datapoint Settings in the Detailed Routing ............................................... 522
9.6.3.1 Client in Send Direction ...................................................................... 523
9.6.3.2 Client in Receive Direction .................................................................. 525
9.6.3.3 Client – Disturbance Record in Transmit Direction .............................. 526
9.6.3.4 Client – Disturbance Record in Receive Direction ............................... 526
9.6.3.5 Server in Transmit Direction ............................................................... 527
9.6.3.6 Server in Receive Direction ................................................................ 529
9.6.3.7 Server in Transmit Direction + Goose [only Edition 1].......................... 530
9.6.3.8 Server in Receive Direction + Goose [only Edition 1] .......................... 532
9.6.3.8.1 GOOSE Attributes ......................................................................... 534
9.6.3.9 Server in Transmit Direction – Default Values ..................................... 535
9.6.3.10 GOOSE Properties (System Technique) ............................................. 536
9.6.4.1 Conversion of the Time Information .................................................... 537
9.6.4.2 Signaling / Measured Value Disabling [Client only].............................. 537
9.6.4.3 Emulation of the Going Binary Information [Client only] ...................... 538
9.6.4.4 Emulation of the Data on Reception of the Attribute Beh.stVal = "OFF"
[Client only] ........................................................................................ 538

Edition 06.2017, DC0-023-2.12
Table of Contents
9.6.4.5 Technological Adaptation for Measured Values................................... 539

9.6.4.6 Measured Value Change Monitoring ................................................... 541
9.6.4.7 Monitoring Intermediate and Faulty Positions of Double Point Information
[Client only] ........................................................................................ 543
9.6.4.8 Logging of the Remote Commands at the Local Control Centre [Server
only] ................................................................................................... 544
9.6.4.9 Remote Parameterization/Diagnostic of SICAM RTUs Components via
IEC 61850 .......................................................................................... 544
9.7 Web Server .................................................................................................. 545
9.7.1 IEC 61850 Edition 1 [Client + Server]...................................................... 545
9.7.2 IEC 61850 Edition 2 [Client + Server]...................................................... 562
10 SNMPv3 Agent........................................................................................................... 581
10.1 Introduction .................................................................................................. 582

10.2 Features and Functions ................................................................................ 583
10.3 SNMP .......................................................................................................... 585
10.3.1 SNMPv2 .................................................................................................. 585
10.3.2 SNMPV3 ................................................................................................. 586
10.4 SNMP MIB – Management Information Base ................................................ 589
10.4.1 Structure of the SICAM RTUs MIB ........................................................... 590
10.5 SNMP Variables ........................................................................................... 591
10.5.1 SNMP Variables of MIB-2 ........................................................................ 592
10.5.2 SNMP Variables for SICAM RTUs ........................................................... 593
10.5.3 SNMP Variables for SICAM RTUs - Traps ............................................... 595
10.5.4 SNMP Variables for SICAM RTUs - Traps History.................................... 597
11 PRP ............................................................................................................................ 599
11.1 Introduction .................................................................................................. 600

11.2 Configuration ................................................................................................ 602
12 NTP/SNTP .................................................................................................................. 603
12.1 Introduction .................................................................................................. 604

12.2 NTP/SNTP Client ......................................................................................... 605
12.3 Integrated NTP Server.................................................................................. 608
13 Remote Operation for SICAM TOOLBOX II (LAN/WAN) ........................................... 611
13.1 Introduction .................................................................................................. 612

13.2 Remote Operation via TCP/IP + HTTP/HTTPS ............................................. 613
13.3 Remote Operation via integrated Terminal Server......................................... 614
13.4 Remote Operation via external Terminal Server............................................ 615
A Internet Protocol Family ........................................................................................... 617
A.1 Internet Protocol (IP) .................................................................................... 618

A.2 Transmission Control Protocol (TCP)............................................................ 619
A.3 User Datagram Protocol (UDP)..................................................................... 622

DC0-023-2.12, Edition 06.2017
Table of Contents
A.4 Hyper Text Transfer Protocol (HTTP) ........................................................... 623

Edition 06.2017, DC0-023-2.12
1 Protocol Element
Contents
1.1 Overview ........................................................................................................ 20

DC0-023-2.12, Edition 06.2017
Protocol Element
1.1 Overview
A protocol element is used for the exchange of data - and thereby for the transmission of
messages - over a communication interface to other automation units or devices of third-party
manufacturers, e.g. control systems.
The task of the protocol element is:
· The handling of specific communication protocols with the communication of SICAM RTUs
automation units among themselves or with devices of other manufacturers.
· The adaption of the internal message formats to the corresponding external message
formats.
· The adaption of system and addressing concepts of SICAM RTUs and the devices of
other manufacturers.
Thereby it is distinguished between protocol elements with serial communication or with

LAN/WAN communication.
Serial communication
For serial communication are available as standard protocols:
· point-to-point traffic
· multi-point traffic, optionally with relay operation
· dial-up traffic
The standard protocols are based on the interoperable standard to IEC 60870-5-101.
Yet, there is still a whole series of other available protocols such as:
· counter interfacing according to IEC 61107

· interfacing of protective devices according to IEC 60870-5-103
· MODBUS
· PROFIBUS DP
· DNP3
LAN/WAN communication
For the LAN/WAN communication Ethernet TCP/IP according to IEC 60870-5-104 or
IEC 61850 is used.

Edition 06.2017, DC0-023-2.12
2 Architecture and Data Flow
Contents
2.1 Protocol Structure........................................................................................... 22

2.2 Data Flow of Process Information ................................................................... 25

DC0-023-2.12, Edition 06.2017
Architecture and Data Flow
2.1 Protocol Structure
2.1.1 Protocols according to IEC 60870-5-101/103
Protocols according to the standards of the series IEC 60870-5 are based on the three-layer
model „Enhanced Performance Architecture“, refer to IEC 60870-5-3, Section 4. This model
has been developed especially for telecontrol systems which require particularly short reaction
times in combination with low-bandwidth transmission networks.
Protocols based on this architecture utilize only three layers of the ISO-OSI-reference model
(Layer model for the communication of open systems), namely the bit transmission layer, the
link layer and the application layer.
The physical layer utilizes ITU-T recommendations for the binary symmetric and memoryless
transmission on the required medium, in order to ensure the high data integrity of the block
encoding method in the link layer.
The following picture shows the model of the enhanced performance architecture (EPA) and
the standard definitions selected for this application-related standard.
IEC60870-5-101/-103 Protocol specific

AP
IEC 60870-5-5 functions
7 IEC 60870-5-3, IEC 60870-5-4
6
5
Layer 3-6 are not used in the EPA-layer model !
4
3
2 IEC 60870-5-2, IEC 60870-5-1

Legend:
1 Selectet ITU-T-recommendations …. IEC 60870-5-101-/103
Layer Task Functions, Characteristics, Comments

AP – Application · Transmission protocol for basic telecontrol tasks
processes according to IEC 60870-5-101 or
Transmission protocol for the information interface of
protection equipment according to IEC 60870-5-103
· Selected application functions according to
IEC 60870-5-5
· Protocol-specific functions
7 – Application layer Application · Selected information elements of the application layer acc.
Data format to IEC 60870-5-4
· Selected service data units of the application layer
according to IEC 60870-5-3
6 – Representation layer –
5 – Communication –
control layer
4 – Transport layer –
3 – Network layer –
2 – Link layer · Selected transmission procedures of the link layer
according to IEC 60870-5-2
· Selected message formats according to IEC 60870-5-1
1 – Bit transmission layer · Selected ITU-T recommendations
(Physical)

Edition 06.2017, DC0-023-2.12
2.1.2 Protocols according to IEC 60870-5-104
Protocols according to the IEC 60870-5-104 standard are based on the OSI layer model.
IEC 60870-5-5 Application Procedures

7 Mapping IEC 60870-5-101 ó IEC 60870-5-104
IEC60870-5-104 PRE-Status Time

WEB-Server Remote Sync.
6 APDU Connection
for
TOOLBOX II
5 APCI HTTP NTP Legend:

APDU ……….. Application Protocol Data Unit (IEC 60870-5-104)
4 TCP UDP APCI ……...…. Application Protocol Control Information (IEC 60870-5-104)
ARP ……...….. Address Resolution Protocol
HTTP ….....….. Hyper Text Transfer Protocol
ICMP …..…….. Internet Control Message Protocol
3 ICMP
IP IP …………….. Internet Protocol
NTP ………….. Network Time Protocol
RSTP…...……. Rapid Spanning Tree Protocol
TCP …….……. Transmission Control Protocol
2 IP Encapsulation ARP RSTP UDP ……….…. User Datagram Protocol
IP Encapsulation RFC 894

1 Ethernet …. IEC 61850

7 – Application Application · Transmission handling
· Reception handling
· Management of up to 100 connections
6 – Presentation Data format · IEC 60870-5-104 APDU's to Ax 1703 / SICAM RTUs
and compatible systems
In the "private range" according to IEC 60870-5-104,
Ax 1703 / SICAM RTUs-specific system messages
and some user data is implemented
5 – Session Interface between · IEC 60870-5-104 APCI
data format and · NTP according to RFC 1305
communication · Remote operation for SICAM TOOLBOX II
protocol
4 – Transport Communication · TCP/IP according to RFC 791 and RFC 793
3 – Network protocol · ICMP according to RFC 792
2 – Data Link LAN interface · Ethernet 10/100 Mbps according to IEEE 802.3
1–- Physical · Medium and transmission rate can be selected with
SICAM TOOLBOX II
· Connection technique (on the master control or
communication element)
RJ45 for copper and MT-RJ connector for FO
· ARP according to RFC 826
· IP Encapsulation according to RFC 894
· RSTP according to IEEE 802.1D, Edition 2004

DC0-023-2.12, Edition 06.2017
2.1.3 Protocols according to IEC 61850
Protocols according to the IEC 61870-5 standard are based on the OSI layer model.

7 Mapping IEC 60870-5-101 ó IEC 61850
IEC61850
PRE-Status Time
ACSI-Services WEB-Server Remote Sync.
6 Client
Connection
Peer-to-Peer Server for
TOOLBOX II
5 MMS HTTP NTP

Sampled Value
Legend:
Exchange
TCP
GOOSE
4 T-Profile
TCP UDP ARP ……...….. Address Resolution Protocol
3 ICMP
MMS ……….… Manufacturing Message Specification
GOOSE ……… Generic Object Oriented Substation Events
Priority Tagging IP Encapsulation RFC 894
1 (IEEE 802.1Q + IEEE 802.1p)
Ethernet
…. IEC 61850

7 - Application Application · Transmission handling
· Reception handling
· Management of multiple connections
6 - Presentation Data format · IEC 61850 ACSI to Ax 1703 / SICAM RTUs and compatible
systems
Ax 1703/SICAM RTUs-specific system messages and some
user data is implemented (e.g. transmission of disturbance
records to SICAM DISTO)
5 - Session Interface between · GOOSE
data format and · MMS
communication · HTTP
protocol
· Remote operation for SICAM TOOLBOX II
· NTP according to RFC 1305
4 - Transport Communication · TCP/IP according to RFC 791 and RFC 793; GOOSE
3 - Network protocol · ICMP according to RFC 792; GOOSE
2 - Data Link LAN interface · Ethernet 10/100 Mbps according to IEEE 802.3; GOOSE
1 - Physical · Medium and transmission rate can be selected with
SICAM TOOLBOX II

Edition 06.2017, DC0-023-2.12
2.2 Data Flow of Process Information
Process signals
I/O Process I/O

Module Module
In/Output Process
In/Output
Peripheral element
Peripheral element
TM-Bus
(PE)
(PE)
Process peripherals Process peripherals
IEC60870-5-101/104 IEC60870-5-101/104
Ax1703 PE-Bus
Processing of
Open-/closed-loop Diagnostic
commands
control function Error messages
IEC60870-5-101/104
Node bus
Internal distribution of messages with process informations (data flow control)
Basic system element

(BSE)
Communication Protocol element
function control function
Supplementary module bus (ZBG bus)
Protocol Protocol
element element
(PRE) (PRE)
Transmission link
Legend: Messages with process informations
Periodical informations
Telecontrol
Automation

DC0-023-2.12, Edition 06.2017

Edition 06.2017, DC0-023-2.12
3 Point-to-Point Traffic (BPP)
Contents
3.1 Introduction .................................................................................................... 28

3.3 Optimized Parameters for selected Transmission Facilities ............................. 41
3.4 Function for the Support of Redundant Communication Routes ...................... 45
3.5 Message Conversion ...................................................................................... 49
3.6 Transparent Mode (Tunneling, Container Mode) ............................................. 73
3.7 Protocol Element Control and Return Information ........................................... 76

DC0-023-2.12, Edition 06.2017
Point-to-Point Traffic (BPP)
3.1 Introduction
Point-to-point traffic describes a serial communications protocol with which a master station is
connected with a remote terminal unit over a communication link in a point-to-point
configuration. Each station has equal access and can spontaneously perform a data
transmission.
Master Station
TF
TF
Remote station
Legende:
TF ………..….. Transmission facility (for full duplex transmission route)
In point-to-point traffic a "symmetric transmission procedure" is used. That means, that every
station can initiate message transmissions. As a result, every station in point-to-point traffic
performs both the functions of the primary station as well as the functions of the secondary
station. The function to be performed is determined through the initiation of the data
transmission.
For point-to-point traffic a "full duplex" transmission medium is required.
The following Firmwares are available for the different systems:
Firmware System Standard and function
SICAM AK3
SICAM AK
BPPA0
SICAM BC
SICAM TM IEC 60870-5-101 Balanced (point-to-point)
Controlling or Controlled Station
CP-8000
BPPT0 CP-802x
SICAM EMIC

Edition 06.2017, DC0-023-2.12
BPPA0
BPPT0
General Functions
· Serial communication protocol according IEC60870-5-101
· Balanced transmission ü ü
− Network configuration
- Point-to-point configuration ü ü
- Multiple point-to-point configuration 1) ü ü
- max. Connections 1 1
− System or device (application function)
- Controlled Station ü ü
- Controlling Station ü ü
· Physical layer / data flow control
− Unbalanced interchange circuit accordingV.24/V.28 standard ü ü

− Balanced interchange circuit X.24/V.28 ü 2)
− Transmission medium (full duplex) ü ü
− Transmission medium (half duplex)
− Byte Frame (8E1) ü ü

− Data flow control Bit in receive direction ü ü
− Data flow control Bit in transmit direction
· Interoperability
− IEC60870-5-101 Ed.1 ü ü
− IEC60870-5-101 Ed.2
· Interoperability according to the following documents:

− SICAM RTUs Interoperability IEC 60870-5-101/104 (DC0-013-2) ü ü
− Ax 1703 Interoperability IEC 60870-5-101/104 (DA0-046-2) ü
· Acquisition of events (transmission of data ready to be sent) ü ü
· General interrogation, outstation interrogation ü ü

− Non Interruptible GI ü ü
· Clock synchronization according IEC60870-5-101

− Clock synchronization with <TI:=103> clock synchronization command ü ü
− Acquisition of transmission delay (primary station) used for correction of clock ü ü
synchronization with <TI:=106>
− Acquisition of transmission delay (secondary station) used for correction of clock ü ü
synchronization with <TI:=106>
− Correction of clock synchronization (via parameter)
− Accuracy +/-20 ms
· Command transmission ü ü
− Supervision of maximum transport delay in control direction
Command Transfer Monitoring (Dwell Time Monitoring)
− Set control location ü ü
− Check control location ü ü
· Transmission of integrated totals ü ü
· File transfer ü ü

DC0-023-2.12, Edition 06.2017
BPPA0
BPPT0
General Functions
· Optimized parameters for selected transmission facilities (modems) ü ü

− Predefined optimized parameters for selected transmission facilities
− Fre dedineable parameters for transmission facility ü ü

− 5 V power supply via DSR status signal for external modems
ü
ATTENTION: check power consumption of external modem!
· Functions for the support of redundant communication routes
− NUC redundancy (Norwegian Users Conventions)
- NUC redundancy „controlling station“
- NUC redundancy „controlled station“ ü

− 1703 redundancy ü
- Listening mode when passive ü
- Tristate of RS-232 interface when passive ü

− Deactivation of interface (with protocol element control message) ü
− Deactivation of interface (with redundancy control message)
· Protocol element control and return information

− Protocol element control
− Send (general) interrogation command to all ü ü

− Send (general) interrogation command for GI group to own BSE ü 3) ü 3)
(=simulate received general interrogation command for GI group)
− Send (general) interrogation command to selective CASDU ü ü

− Send (general) interrogation command for image GI to own BSE ü ü
− Send process reset command

− Data filter in transmit direction „ON/OFF“ ü ü
− Data filter in receive direction „ON/OFF“ ü ü
− Activate/Deactivate interface ü ü
− Activate/Deactivate interface + protocol functions ü ü
− Protocol element return information
− Station failure
− Protocol-specific return information 0 ü ü

„Interface activated/deactivated“
− Protocol-specific return information 1 ü ü
„Interface + protocol functions activated/deactivated“
· Remote maintenance with SICAM TOOLBOX II via serial connection ü ü

Edition 06.2017, DC0-023-2.12
BPPA0
BPPT0
General Functions
· Special functions
− Summer time bit (SU)=0 for all messages in transmit direction (time tag) ü ü
− Day of week (DOW)=0 for all messages in transmit direction (time tag) ü ü
− Originator address=0 for all messages in transmit direction ü ü
− WhiteList Filter ü
− Data Throughput Limitation ü
− Convert general interrogation command in receive direction to BROADCAST ü ü
− Non interruptible GI ü ü
- ACTCON for clock synchronization command ü ü
- Emulate ACTCON+/- ü ü
- Emulate ACTCON, ACTTERM for commands with control message ü ü
- Compatibility TCS100 ü ü
− Special functions for project DBAG
- Breaker delay in transmit direction ü ü

(DBAG-specific special message format <TI=150>)
- Send originator address with settable value ü ü
- Transparent Mode (tunneling, container mode) ü ü

− Special functions for project RWE
- Bit by bit marking of the field
- Cyclic measured values
- Address of the return information for selection command 2
- NT-Bit, IV-Bit according to RWE requirements ü

1) Separate interface for each single point-to-point configuration required
2) External converter CM 0829 required
3) only supported in Ax 1703 (not supported in SICAM RTUs, ACP 1703)!

DC0-023-2.12, Edition 06.2017
The operating mode of the interface is determined by parameters of the protocol element and
optional equipment.
Standard Operation Parameter and Setting Interface Signals

Mode
Unbalanced Asynchronous / Isochronous
interchange circuit Asynchronous RXD, TXD, CTS, RTS, DCD, DTR,
V.24/V.28 DSR/+5V, GND
V.28 asynchronous
Optional Operation Parameter and Setting Interface Signals

Mode
Balanced interchange Asynchronous / Isochronous
circuit X.24/X.27 Isochronous
V.11 isochronous
Bit timing internal RXD, TXD, CTS, TXC, DCD, DTR,
with CM-0829 DSR/+5V, GND
Bit timing external RXD, TXD, RTS, RXC, DCD, DTR,
DSR/+5V, GND
Balanced interface Asynchronous / Isochronous
RS-422 Asynchronous RXD, TXD, CTS, RTS, DCD, DTR,
V.11 asynchronous DSR/+5V, GND
Optical interface Asynchronous / Isochronous
(multimode fiber optic) Asynchronous RXD, TXD, +5V, GND
with CM-0827
For the communication with a remote station in point-to-point traffic according to IEC 60870-5-
101 the following basic settings are required:
· Address of the link layer

· Number of octets for the address of the link layer
· Station type
For this, in the master / remote station the parameter advanced parameters | IEC60870-
5-101 | Address of the link and the parameter advanced parameters |
IEC60870-5-101 | Address field of the link (number) must be set according to
the selected definition. For the communication in point-to-point traffic the address field of the
link must be set to the same value in the master station and in the remote station.
For the communication with a remote station in point-to-point traffic according to

IEC 60870-5-101 in addition the setting of the parameter Common settings | station
type is required. Thereby a station is to be assigned either "Station A" or "Station B".
Station type "Own Station" Station type "Remote Station"

Station A Station B
Station B Station A

Edition 06.2017, DC0-023-2.12
For the coupling of different systems with the IEC 60870-5-101 protocol, the setting of the
variable elements of the message is required. These parameters are shown in the
Interoperability List (Master and remote station must have the same parameter settings).
The following table provides an overview of which IEC-parameters are to be parameterized on

which system elements.
IEC 60870-5-101 Parameter Description System

Element
Address field of the link (number) Number of octets for the address field of the PRE
link layer
Cause of transmission (COT) Number of octets for cause of transmission BSE
Common address of ASDU Number of octets for common address of the BSE
(CASDU) ASDU
Information object address (IOA) Number of octets for the address of the BSE
information object
Acknowledgement IEC 60870-5-2 Acknowledgement on IEC 60870-5-2 layer PRE
Single character or short message (ACK)
Maximum message length BSE
Time tag Number of octets for time tag BSE
Legend:
SSE ........ Supplementary system element

(with serial interfaces, this is always configured with a PRE)
PRE ........ Protocol element
BSE ........ Basic system element

DC0-023-2.12, Edition 06.2017
3.2 Communication according to IEC 60870-5-101
3.2.1 Data Transmission Procedure
The transmission of the data from the remote terminal unit to the master station as well as
from the master station to the remote terminal unit takes place spontaneously. The
prioritization and blocking of the data to be sent takes place on the basic system element
(BSE). The data transmission is started after a startup or, with redundancy switchover after
successful station initialization.
If a remote station (secondary station) can presently not process more data messages
(messages), for the data flow control the DFC bit (Data Flow Control) is set in the control field
of the message direction secondary station ð primary station. From this moment the protocol
firmware of the primary station sends no more data messages to the remote station, until the
remote station resets the DFC-bit.
In addition a warning is output by the protocol element of the primary station.
The data is stored in the data storage of the communication function on the basic system
element (BSE) until these are deleted by the dwell time monitoring or can be transmitted to
the remote station.
The primary station also monitors whether the secondary station resets the DFC-bit within a
time that can be set with the parameter
advanced parameters | IEC60870-5-101 | DFC-monitoring time.
The state of the DFC-bit of the secondary station is interrogated by the primary station by
means of cyclic messages "REQUEST STATUS OF LINK". The cycle time can be set with the
parameter advanced parameters | IEC60870-5-101 | polling cycle for
stations with "DFC-bit = 1". If the DFC-bit is present for longer than the set monitoring
time, the interface is reported as failed.
3.2.1.1 Acknowledgement Procedure
All sent data messages must be acknowledged by the other station (secondary station).
If, with non-faulty transmission line, the acknowledgement is missing for longer than the
expected acknowledgement time, transmitted messages are repeated up to n-times (n can be
parameterized). On expiry of the number of retries, the station is flagged as faulty.
The required expected acknowledgement time is determined automatically from the set
parameters, but if necessary can be extended accordingly with the parameter advanced
parameters | monitoring times | expected_ack_time_corr_factor. This is then
the case if additional signal propagation delays, delay times or slow processing times of the
connected stations must be taken into consideration.
The number of retries for data messages is to be set with the parameter Message retries
| Retries for data message SEND/CONFIRM or for messages for station initialization
with the parameter Message retries | Retries for INIT-messages SEND/CONFIRM.
The acknowledgement can be transmitted optionally as single character (E5) or as message

with fixed length (ACK). If no additional information is to be transmitted, as standard the single
character (E5) is used for acknowledgement, however some third-party systems always
expect the acknowledgement as message with fixed length.
The message type for the acknowledgement can be selected with the parameter advanced
parameters | IEC60870-5-101 | Acknowledgement IEC60870-5-2.

Edition 06.2017, DC0-023-2.12
Failure Monitoring
The monitoring of the interface by the active master / remote terminal unit takes place by
means of cyclic transmitted (subject to acknowledgement) messages or by means of a cyclic
executed "Test function of the link layer ". The interface monitoring with "Test function of the
link layer" can be parameterized with the parameter advanced parameters |
interface_monitoring "cycle time". On expiry of the retry number the remote station is
reported as failed.
No further data is sent to a failed remote station until successful station initialization. The data
is stored in the data storage of the communication function on the basic system element
(BSE) until this is deleted by the dwell time monitoring or can be transmitted to the re-
reachable remote station.
3.2.2 Station Initialization
After startup or redundancy switchover, the operation of the interface is begun after successful
station initialization.
The initialization of the link layer of the remote terminal unit is performed by the master station
with:
· Request for the status of the link layer (REQUEST STATUS OF LINK)
· Reset of the remote terminal unit link layer (RESET OF REMOTE LINK)
Reset Command Function in the Remote Station

REQUEST STATUS OF LINK - "STATUS OF LINK" is transmitted to the remote station
RESET of REMOTE LINK - FCB-Bit (Frame Count Bit) is initialized
- Acknowledgement for RESET of REMOTE LINK is transmitted
to remote station
Note:
During faulty communication REQUEST STATUS OF LINK will be sent cyclic.
The gap between the messages is the calculated acknowledged time including the
parameterized time for expected_ack_time_corr_factor.
End of Initialization
If sending of "end of initialization" is enabled on the basic system element in the IEC 60870-5-
101/104 parameter block, after the station initialization is performed, data is only sent from the
protocol element if the "INIT-End" has been received from the basic system element for the
corresponding ASDU. "<TI=70> End of Initialization" is also transmitted to the remote station.
The clock synchronization command or general interrogation command may only be
transmitted after "INIT-End".
3.2.3 Acquisition of Events (transmission of data ready to be sent)
The transmission of data ready to be sent from the remote terminal unit to the master station
as well as from the master station to the remote terminal unit takes place spontaneously. The
prioritization and blocking of the data ready to be sent takes place on the basic system
element (BSE). The data transmission is started after a startup or, with redundancy switchover
after successful station initialization.
For further details, refer to section "Data Transmission Procedure"!

DC0-023-2.12, Edition 06.2017
3.2.4 General Interrogation, Outstation Interrogation
The general interrogation (outstation interrogation) function is used to update the master
station after the internal station initialization or after the master station has detected a loss of
information. The function general interrogation of the master station requests the remote
terminal unit to transmit the actual values of all its process variables.
Non Interruptible GI
From the remote terminal unit periodic and spontaneous data can also be transmitted during a
running general interrogation.
With the parameter advanced parameters | IEC60870-5-101 | timeout for non
interrupted GI the periodic or the periodic and spontaneous transmission of data can be
disabled during a running general interrogation
(monitoring time: "0" = GI is interruptible; "≠ 0" = GI is not interruptible).
The following parameter settings are necessary on the BSE for the non-interruptible GI:
· Sending of "end of initialization" (INIT-End) must be enabled
· General interrogation must take place from the process image (Image-GI)
With the INIT-End, the protocol element detects all ASDU's used in transmit direction.
This is required with general interrogation to all (BROADCAST) for GI-End detection.
With non-interruptible general interrogation, from the moment of "General interrogation

command received" all data of the spontaneous priority level from the basic system to the
protocol element are inhibited. This block is then terminated by the protocol element, if the
general interrogation is complete or the monitoring time "Timeout for non-interruptible GI" has
expired.
The selection of the data which should be disabled for transmission during non-interruptible GI
is to be done on the protocol element with the parameter advanced parameters |
IEC60870-5-101 | disable data during non interrupted GI for periodic data or
periodic and spontaneous data.
The monitoring time is to be set on the protocol element with the parameter advanced
parameters | IEC60870-5-101 | Monitoring time for GI-data and is used in
transmit direction for all ASDU's together. The monitoring time is retriggered for messages
with the causes of transmission <URS:=2, 7, 20, 21..36>. With general interrogation to a
selective ASDU, the monitoring time is stopped if the general interrogation command is
received with the cause of transmission <URS:=10> "Termination of Activation", with general
interrogation to all ASDU's (BROADCAST), the monitoring time is stopped if for all ASDU's the
general interrogation command is received with the cause of transmission "Termination of
Activation".

Edition 06.2017, DC0-023-2.12
3.2.5 Clock Synchronization
The clock synchronization of the remote station can be performed over the serial
communication line – controlled by the master station. The clock synchronization command is
sent spontaneously at a change of the time and cyclic 1x per minute by the master station.
With clock synchronization 1x per minute a typical accuracy of ± 20 ms can be achieved.
If the accuracy of the remote synchronization is insufficient, a local time signal receiver must
be used in the remote station.
Messages, which are sent after a startup, but before the SICAM RTUs remote terminal unit
has the correct time, contain the relative time from startup (reference day: 1.1.2001) with the
flagging of the time tag as invalid.
The clock synchronization command is sent between the 20th and 50th second of the actual
minute. The time of transmission is determined based on the parameter settings (baud rate,
message length, number of retries) and a possible presently running message transmission,
so that the clock synchronization command arrives in the remote station in all cases before
the minute change. The clock synchronization command is sent at the transmit moment,
exactly synchronized to the internal 10ms cycle. The time in the message corresponds to the
absolute time of the 1st bit during the transmission on the line.
In SICAM RTUs the cyclic transmission of the clock synchronization command for remote
synchronization is initiated automatically by the basic system element.
In Ax1703 the cyclic transmission of the clock synchronization command for remote
synchronization by the protocol element is to be activated with the parameter advanced
parameters | Send clock synchronization command cyclic.
The transmission of the clock synchronization command always takes place with high priority
at the end of the running minute (in Ax1703 between the 50th and 59 second).
The clock synchronization command is sent at the transmit moment, exactly synchronized to
the internal 10ms cycle. The time in the message corresponds to the absolute time of the 1st
bit during the transmission on the line.

DC0-023-2.12, Edition 06.2017
3.2.6 Command Transmission
Data messages in command direction are always sent spontaneously by the master station to
the remote station. The prioritization and blocking of the data to be sent already takes place
on the basic system element (BSE).
3.2.6.1 Control Location
If the function "control location" is activated, commands from the protocol element of the
master station are only then transmitted to the remote terminal unit (remote station) if the
command has been sent from an enabled control location (originator address).
The setting of the control location itself takes place with a command message in single
command format <TI=45> which is converted on the basic system element to a PRE control
message (function: set control location) by the protocol control function. The control location to
be enabled/disabled is taken from the originator of the command message.
A command received with an originator address not enabled as control location is not
transmitted from the protocol element of the master station and is discarded. For these
commands a negative confirmation of activation (ACTCON-) is sent back immediately by the
protocol element to the originator address.
3.2.6.2 Control Location Check
The control location check is used to check whether the control location, specified with the
originator address in the spontaneous information object "Command", has command
authority.
The originator address specified in the spontaneous information object "Command" must
correspond with the control location previously set.
If the originator address in the spontaneous information object "Command" does not match
with one of the control locations previously set or if no control location has been preset:
· the command is rejected

· a negative confirmation of the activation is sent (ACTCON-)
The control location check is activated as soon as a PRE control message of the type "Set
control location" is entered in the PST detailed routing on the basic system element (BSE) for
a protocol element (PRE). After startup of the PRE, the BSE sends a PRE control message
"Set control location" to the PRE. As a result the control location check function is activated on
the PRE.

Edition 06.2017, DC0-023-2.12
3.2.6.3 Set Control Location
The control location is set on the PRE with a PRE-control message (Function = Set control
location) either globally for all stations or station-selective. The control location can be set or
deleted and is applicable for all commands of a protocol element.
On the BSE the control location is set by the spontaneous information object "control location"
and is valid for all commands of a protocol element. The assignment of this message takes
place in the OPM of the SICAM TOOLBOX II with the category SICAM 1703 + Ax 1703 System
Functions / Protocol element control message.
For the derivation of the control location, the following values in the spontaneous information
object "Command" signify the originator address:
Originator Address Control Location

0 default
1 ... 127 remote command
128 ... 255 local command
Note:
The selection of the control location and the generation of the spontaneous information object
"Control location" must be programmed in an application program of the open-/closed-loop
control function.
With the spontaneous information object "Control location" in "single command" format, up to
256 control locations can be set at the same time. The information object "Control location" is
converted on the basic system element (BSE) to a PRE-control message and passed on to
the protocol element.
Due to an information object "Control location" with the single command state "ON", the
originator address is added to the list of enabled control locations (="Control location
enabled").
Due to an information object "Control location" with the single command state "OFF", all
originator addresses are deleted from the list of enabled control locations (="All control
locations not enabled").
No confirmation (ACTCON) and no termination (ACTTERM) of the command initiation is

created for the information object "Control location".
With each startup of the protocol element, all enabled control locations are reset. The control
location(s) is/are to be set with each startup of the system element.

DC0-023-2.12, Edition 06.2017
3.2.7 Transmission of Integrated Totals
A counter interrogation command triggered in the system is transmitted acknowledged from

the protocol element to the remote station.
The functionality implemented in the System SICAM RTUs concerning integrated totals is
documented in the document "Common Functions of Peripheral Elements according to IEC
60870-5-101/104".
3.2.8 File Transfer
The protocol element sends all message formats received from the basic system element
(BSE) that are defined for the transfer of files to the remote station. All message formats
received from the remote station for the transfer of files are passed on by the protocol element
to the basic system element.
The protocol element itself performs no functions for the transfer of files. Messages for the
transfer of files are passed on "transparently".
Limitation:
For the transfer of files the System SICAM RTUs supports only max. 200 data bytes per
segment!
3.2.9 Acquisition of Transmission Delay
The protocol element supports the function "Acquisition of transmission delay" and the time
correction resulting from this with clock synchronization according to IEC 60870-5. With this
procedure the transmission delay is determined with <TI=106> and the corrected time loaded
in the remote station.
The correction of the time in the clock synchronization command is performed in the remote
station.
The acquisition of the monitoring time is performed cyclic every "2 minutes".
The "Correction time for clock synchronization command" is produced from:
· Message delay
· Transmission delay
The clock synchronization command is transmitted cyclic 1x per minute to the remote station.
The time in the clock synchronization command corresponds to the absolute moment of the
1st bit during the transmission on the line.
See also section "Clock Synchronization"!

Edition 06.2017, DC0-023-2.12
3.3 Optimized Parameters for selected Transmission

Facilities
The protocol element requires a "full duplex" link.
For the adaptation to various modems or time requirements of external systems, the following
parameters can be set individually:
Parameter
Ÿ Common settings | electrical interface [SM-2541 only]
Ÿ Common settings | asynchron/isochron
Ÿ Common settings | source for receive-/transmit clock (only for "Isochronous")
Ÿ Common settings | advanced time settings | pause time (tp),
Ÿ Common settings | advanced time settings | pause time "time base" (tp)
Ÿ Common settings | advanced time settings | set up time (tv),
Ÿ Common settings | advanced time settings | set up time "time base" (tv)
Ÿ Common settings | advanced time settings | run-out time (tn),
Ÿ Common settings | advanced time settings | run-out time "time base" (tn)
Ÿ Common settings | advanced time settings | DCD handling
Ÿ Common settings | advanced time settings | bounce suppression time (tbounce)
Ÿ Common settings | advanced time settings | disable time (tdis),
Ÿ Common settings | advanced time settings | disable time "time base" (tdis),
Ÿ Common settings | advanced time settings | stability monitoring time (tstab)
Ÿ Common settings | advanced time settings | continuous level monitoring time (tcl)
Ÿ Common settings | advanced time settings | Transmission delay if countinous level (tcldly)
Ÿ advanced parameters | 5V supply (DSR) [SM-0551, SM-2551 only]
Ÿ advanced parameters | Configuration for CM-082x [SM-0551, SM-2551 only]
How the individual time settings are effective during the data transmission is shown on the
following page in a Timing Diagram.
Parameter "5V Supply (DSR)" [only SM-0551, SM-2551]
If necessary the voltage supply of the transmission facility (only 5V) – insofar as this is
sufficient – can take place over the state line DSR. The enabling of the voltage supply is
performed with the parameter advanced parameters | 5V supply (DSR). The voltage
supply is only switched on the DSR state line instead of the DSR signal with corresponding
parameter setting.
ATTENTION:
Required voltage supply and maximum current consumption of the transmission facility must
be observed!

DC0-023-2.12, Edition 06.2017
Parameter "Configuring for CM082x" [only SM-0551, SM-2551]
If an optical transformer of the type CM082x is used as external transmission facility, then the
parameter advanced parameters | Configuration for CM-082x must be set when
using a patch plug of the type CM2860.
Most transmission facilities support only certain baud rates or combinations of baud rates in
transmit/receive direction – these are to be taken from the descriptions for the transmission
facility.
The transmission rate (baud rate) is to be set depending on the submodule used for
communication, separate for transmit/receive direction with the parameter Common settings
| baud rate receiver and the parameter Common settings | baud rate
transmitter or for transmit/receive direction together with the parameter Common
settings | baud rate.
In addition, for the adaptation of the protocol to the transmission medium used or to the
dynamic behavior of the connected remote station, the following parameters are available:
Parameter
Ÿ advanced parameters | monitoring times | Character monitoring time,
Ÿ advanced parameters | monitoring times | Character monitoring time "time base"
Ÿ advanced parameters | monitoring times | idle monitoring time,
Ÿ advanced parameters | monitoring times | idle monitoring time "time base"
Ÿ advanced parameters | monitoring times | expected_ack_time_corr_factor
(see Acknowledgement Procedure)
The character monitoring time and idle monitoring time is used for message interruption
monitoring and message re-synchronization in receive direction. A message interruption is
detected if the time between 2 bytes of a message is greater than the set character monitoring
time. With message interruption the running reception handling is aborted and the message is
discarded. After a detected message interruption a new message is only accepted in receive
direction after an idle time on the line (idle time).
The protocol element can – insofar as the transmission facility (e.g. VFT-channel) makes this
signal available receive-side – evaluate the interface signal DCD and utilize it e.g. for
monitoring functions.

Edition 06.2017, DC0-023-2.12
Default parameters for transmission facilities
Time settings for Electrical RTS tp tv tn tdis DCD tbs tstab tduration tdelay A_I T Z 5V CM082x
transmission facility Interface [ms] [ms] [Bit] [ms] [ms] [ms] [sec] [ms]
RS-232 ON 0 0 0 0 YES 0 0 0 0 A I B NO NO
Legend:
Electrical interface ... Parameter Electrical interface [SM-2541 only]

RTS .......................... áâ = RTS is switched for the control of the carrier switching of the modem
RTS = ON (bei tv=0), RTS = áâ (bei tv≠0),
carrier switching (ON / OFF) with each message in transmit direction
tp ............................... Parameter Pause time (tp), Parameter Pause time_time base (tp)
tv ............................... Parameter Set-up time (tv), Parameter Set-up time_time base (tv)
tn ............................... Parameter Overtravel time (tn)", Parameter Overtravel time_time base (tn)
tdis ............................ Parameter Blocking time (tdis), Parameter Blocking time_time base (tdis)
DCD .......................... Parameter DCD-evaluation
tbs ............................. Parameter Bounce suppression time (tbs)
tstab .......................... Parameter Stability monitoring time (tstab)
tduration ................... Parameter Continuous level monitoring time (tduration)
tdelay ........................ Parameter Transmit delay at level (tdelay)
A_I ............................ Parameter Asynchronous_Isochronous, (A=asynchronous, I=isochronous)
T ............................... Parameter Bit timing (only with isochronous),(I=internal, E=external)
Z ............................... Parameter selective RT remote synchronization, (s=selective, B=BROADCAST)
5V ............................. Parameter 5V Supply (DSR) [SM-0551, SM-2551 only
CM-082 ..................... Parameter Configuring for CM082x, configuring of the interface for optical
transformer CM-082x with patch plug CM-2860 [SM-0551, SM-2551 only]

DC0-023-2.12, Edition 06.2017
The following picture shows the dynamic behavior (timing) in detail for the data transmission when using
transmission facilities with switched carrier. The protocol element requires a full duplex link i.e. both
stations (master station and remote terminal unit) can send and receive at the same time.
In the following timing the full duplex data transmission is not shown for better clarity.
RTS
tverz
tp tv Data transmission tn tsw tp tv

Master station
TXD
tPrell tPrell
DCD
tverzRTS
Data transmission
RXD
tsignal tsignal
tdis
t´verzRTS t´verzRTS
t´Prell t´Prell
DCD
t´signal
Remote station
Data transmission
RXD
t'dis
RTS
t'sw tp' t'v Data transmission t'n

TXD
t'verz
Œ Œ
tPrell tPrell
tstab tstab
tdauer
Legend:
RTS ………….. Request to Send

DCD …………. Data Carrier Detect
TXD ……...….. Transmit Data
RXD ……...….. Receive Data
tverzRTS ……….. Processing time of the transmission system

Time delay/time difference between activation of transmit part (RTS á) and receiver ready (DCD á)
tp ………….….. Break time (delay, before transmit part is activated with RTS)
tv ………….….. Setup time (transmission delay, after transmit part was activated with RTS)
tn ………….….. Reset time (delayed switch off of the transmit signal level with RTS after message transmission )
tsw ….....….….. Internal processing time
tsignal ….....….. Signal propagation delays (dependent from the used transmission facility /transmission path)
tPrell …...….….. Protective time after positive/negative DCD-edge (debounce of DCD)
tstab …...….….. Stability monitoring time – the new DCD-status is only used for message synchronisation after the expiration of the
stability monitoring time
tdauer …...….….. Continuous level monitoring time
tverz …...….….. Transmission delay – in case of a continuous level a further message transmission will be made at the latest after
the transmission delay
tdis …….….….. Disable time of the receiver after message receiption (to supress faulty signs during level monitoring)
t`x …………….. Corresponding times in the remote stations

Œ …………….. DCD valide

Edition 06.2017, DC0-023-2.12
3.4 Function for the Support of Redundant Communication

Routes
To increase the availability both master stations as well as remote terminal units can be
designed redundant. In the master station and remote terminal unit, with the parameter
advanced parameters | project specific | Redundancy control one can select
between the following redundancy controls:
· 1703-Redundancy
· Norwegian User Conventions (NUC)
· Deactivation of interface
The switchover of the redundancy state takes place system-internal through redundancy
control messages or protocol element control message.
In the master station and remote terminal unit, in addition a delay for the switchover of the
redundancy state from PASSIVE (=STANDBY) to ACTIVE can be set with the parameter
Redundancy | Delay time passive=>active.
3.4.1 Redundancy Mode "1703-Redundancy"
The redundancy mode "1703-Redundancy" is selected with the parameter advanced

parameters | project specific | Redundancy control.
In the STANDBY-station, for the synchronization of the FCB-Bit (Frame Count Bit) this is
taken from a listened RESET OF REMOTE LINK or from a valid received message with
variable block length.
The operating mode of the interface with redundancy state "PASSIVE" can be set according
to the redundancy configuration with the parameter Redundancy | operation if
passive as follows:
· Transmitter "tristate", listening mode

· Transmitter "active", listening mode
· Transmitter "active", normal mode
From the redundant, not active master / remote terminal unit, listened messages are passed
on to the basic system element (BSE) and forwarded by this in the system with the identifier
"passive" in the state.
In redundant master / remote terminal units that are not active, a failure of the interface is
monitored globally.
The failure of the interface is detected by the STANDBY station by monitoring for cyclic
message reception. The monitoring time is set with the parameter Redundancy |
listening_mode (failure monitoring time). The monitoring time is retriggered with a
message received free of errors (except REQUEST STATUS OF LINK, RESET OF REMOTE
LINK and positive acknowledgment message using single character E5H).
On receive timeout (active master / remote terminal unit or transmission facility has failed) the
interface is signaled as failed.
The failure of the interface is reset in redundant STANDBY stations, if an error-free message
(except REQUEST STATUS OF LINK and RESET OF REMOTE LINK) from the respective
remote station is "listened" or if no failure monitoring is parameterized.

DC0-023-2.12, Edition 06.2017
Activation / Deactivation of the interface in redundancy mode "passive"

For the implementation of project specific redundancy modes the interface and the operation
of the protocol can be activated/deactivated with protocol element control message when
redundancy mode is in "passive" and with parameter "operation if passive" is set to
"transmitter tristate".
The activation/deactivation of the interface can be used for supervision of redundant
communication links to the remote station.
Behavior when interface is "activated":
· the interface mode will be switched over

from transmitter "tristate", listening mode
to transmitter "active", normal operation
· all date received from remote station (listening mode) will be forwarded to basis system
element. By redundancy mode "passive" enabled the received data will be marked on
basis system element with "R=1" (data received from "passive" interface).
· all data ready for transmit sent from basis system element to protocol element will be sent
to the remote station.
Behavior when interface is "deactivated":

from transmitter "active", normal operation
to transmitter "tristate", listening mode
· all data sent from basis system element to protocol element will be discarded by the
protocol element.
PRE control message for controlling the protocol mode will be accepted only in redundancy
mode "passive".
The actual state of the interface and the protocol mode (activated/deactivated) will be sent
from protocol element to basis system element spontaneous after change of event and during
general interrogation.
No general interrogation command will be initiated by the protocol element firmware after
activation of the interface.
Note:
- the operating mode of the interface will be updated always by the AU internal protocol
element control message (redundancy control message has higher priority than PRE control
message).

Edition 06.2017, DC0-023-2.12
3.4.2 Redundancy Mode "Norwegian User Conventions (NUC)"
The redundancy mode "Norwegian User Conventions (NUC)" uses 2 communications lines
(main/stand-by transmission line) from the master station (Controlling Station) to the remote
terminal unit (Controlled Station). Each of these communications lines is fixed activated to a
specific interface in the master station and in the remote terminal unit. The data is only
transmitted to the active interface. The passive interface is only monitored by the master /
remote terminal unit.
The redundancy mode "Norwegian User Conventions (NUC)" is selected with the parameter
advanced parameters | project specific | Redundancy control.
The protocol element only supports the functions of the slave station (="Controlled Station")!
The operating mode of the interface with redundancy state "PASSIVE" is not to be
parameterized for this redundancy mode. The function is defined by the "Norwegian User
Conventions (NUC)".
Redundancy function according to "Norwegian User Conventions (NUC)" for "balanced-

Mode":
· After startup of the master station (Controlling Station) and the remote terminal unit
(Controlled Station) both stations perform the initialization of the link layer.
· After startup of the remote terminal unit (Controlled Station) both interfaces are
"PASSIVE".
The remote terminal unit (Controlled Station) sends the message "Test function of the link
layer" cyclic for monitoring the interfaces on both lines to the master station (Controlling
Station). This message is acknowledged by the master station (Controlling Station) with
NAK until this switches one of the two interfaces to "ACTIVE".
· The activation of an interface is always performed by the master station only – either
manually or automatically on failure of one interface. The activation is performed either by
a message sent from the master station (Controlling Station) on an interface to the remote
station or with the acknowledgement of the message "Test function of the link layer" with
ACK.
· The master station (Controlling Station) also sends the message "Test function of the link
layer" cyclic for monitoring the interfaces on both lines to the remote terminal unit
(Controlled Station). The "ACTIVE" interface acknowledges this message with ACK, the
passive interface with NAK.
· During the switchover from main transmission line-stand-by transmission line, no data loss
must occur in the Controlled Station. Transmitted data may only be deleted in the remote
terminal unit if these have been explicitly acknowledged by the master station. With
switchover, no general interrogation is necessary.
The passive line is monitored cyclic with the message "Test function of the link layer".
If a station no longer replies, on expiry of the number of retries this is reported as failed.

DC0-023-2.12, Edition 06.2017
In the remote terminal unit, for the redundancy mode "Norwegian User Conventions (NUC)"
the LOAD-SHARE-Mode of the communications function must be used on the basic system
element. With this mode the basic system element uses 2 fixed assigned interfaces for the
transmission of the data from a process image. With the redundancy mode "Norwegian User
Conventions (NUC)", data is only transmitted over the active interface to the master station.
Through the LOAD-SHARE-Mode a switchover without loss of data is ensured – a doubling of
data can occur under certain circumstances.
In the remote terminal unit the assignment of the interfaces for main transmission line and
stand-by transmission line is defined on a basic system element as follows:
Interface 1 Interface 2 Note

Main/Standby Main/Standby
transmission line transmission line
SSE = 128 SSE = 129 Redundant interface pair for NUC-Redundancy
Legend:
SSE ........ Supplementary system element (with serial interfaces, this is always configured with a PRE)
The SICAM RTUs remote terminal unit performs the following functions with redundancy state
"PASSIVE":
· No data for emission are requested by the basic system element

· The "Test function of the link layer" message is send cyclic – with that a failure of the
master station or a switchover of the redundancy state is detected.
· All data in signaling direction are transmitted over the active interface to the master station
· The interface is always electrically "ACTIVE" (and is not switched to "TRISTATE")
3.4.3 Deactivation of Interface
When using mobile control systems the interface can be deactivated in order to suppress the
interface failure if the control system is not connected.
With deactivated interface the transmitter of the interface is switched to "tristate" and the data
for transmission are requested from the basic system element and discarded without error
message. Received messages are discarded and not passed on to the basic system element.
The activation/deactivation of the interface takes place through PRE control messages.
The actual state will be reported via PRE return information message.
After startup of the protocol element the interface is activated by default.
With deactivation of the interface a possibly present failure of the interface is reset if no
"listening mode (failure monitoring time)" is parameterized.
With deactivated interface, no monitoring of the interface takes place!

Edition 06.2017, DC0-023-2.12
3.5 Message Conversion
Data in transmit direction are transferred from the basic system element to the protocol
element in the SICAM RTUs internal IEC 60870-5-101-/104 format. These are converted by
the protocol element to the IEC 60870-5-101 message format on the line and transmitted
according to the transmission procedure of the protocol.
Data in receive direction are converted by the protocol element from IEC 60870-5-101 format
on the transmission line to a SICAM RTUs internal IEC 60870-5-101-/104 format and
transferred to the basic system element.
3.5.1 Blocking
For the optimum utilization of the transmission paths, for the data transmission with IEC
60870-5-101 protocols the "Blocking" according to IEC 60870-5-101 is implemented. This
function is performed on the basic system element (BSE) according to the rules applicable for
this. Data to be transmitted are thereby already blocked on the basic system element and
passed on to the protocol element for transmission. The blocking for data to be transmitted
does not support the maximum possible message length according to IEC 60870-5-101!
Received data in blocked format according to IEC 60870-5-101 are passed on from the
protocol element to the basic system element in blocked format. On the basic system element
the blocked data is split up again into individual information objects by the detailed routing
function and passed on as such to the further processing. Received messages with maximum
length are transmitted SICAM RTUs internal in 2 blocks to the basic system element (BSE)
because of the additionally required transport information.
The parameters necessary for the blocking are to be set on the basic system element (BSE)
in the IEC 60870-5-101/104 parameter block.

DC0-023-2.12, Edition 06.2017
3.5.2 Special Functions
For the coupling to external systems, if necessary the following special functions can be
activated for the adaptation of the message conversion:
· Summer time bit (SU)=0 for all messages in transmit direction

(summer time bit in the time tag)
· Day of week (DOW)=0 for all messages in transmit direction
(day of week in the time tag)
· Originator address=0 for all messages in transmit direction
· WhiteList Filter
· Data Throughput Limitation
· Convert general interrogation command in receive direction to BROADCAST
· Non interruptible GI
· ACTCON for clock synchronization command
· Emulate ACTCON+/-
· Emulate ACTCON for commands
· Emulate ACTCON, ACTTERM for commands with commands
· Compatibility TCS100
· Settings for project DBAG
· Settings for Project RWE
3.5.2.1 Summer Time Bit = 0 for all Messages in Transmit Direction
With the setting of the parameter advanced parameters | IEC60870-5-101 | time

tag | summer-time bit (SU) = 0 the summer time bit (SU) in the time tag is always set
to "0" by the protocol element for all messages with time tag in transmit direction.
3.5.2.2 Day of Week = 0 for all Messages in Transmit Direction

tag | Day of week (DOW) = 0 for all messages with time tag in transmit direction the
weekday (DOW) is always set to 0 by the protocol element.
Note:
This function is only active for process information messages in transmit direction.
The day of week in clock synchronization command message is not affected!

Edition 06.2017, DC0-023-2.12
3.5.2.3 Originator Address = 0 for all Messages in Transmit Direction
With function enabled with the parameter advanced parameters | IEC60870-5-101 |

originator address in transmit direction = 0 for all messages in transmit
direction the originator address is always set to 0 by the protocol element.
Note:
The originator address (= 2nd byte of the cause of transmission) is only then sent if the
number of octets for cause of transmission (COT) is set on the basic system element to 2.
3.5.2.4 WhiteList Filter
Caused by increased using of the norm protocol IEC 60870-5-101/104 in the area of the
telecontrol engineering/process automation this protocol is also very often used to exchange
data between different providers („net couplings“).
For the protection of the own network and also not send any unwanted telegrams to the
remote network, the data traffic is reduced to the absolutely necessary minimum at such
interfaces.
Only defined telegrams (selected by type identification and cause of transmission) will be sent
in transmit direction to the remote network and only defined telegrams will be taken in receive
direction at WhiteList Filter enabled.
The WhiteList Filter can be enabled with the parameter advanced parameters |
IEC60870-5-101 profile | IEC60870-5-101 profile (type identification
check).
Possible parameter setting:
· WhiteList Filter
- This profile can be used on interfaces between different providers or regions within same provider.
- Only selected type identifications from interoperability of SICAM RTUs using balanced
mode according to IEC60870-5-101 (BPP) incl. selected type identifications used by SICAM RTUs in private range
will be passed through in transmit-/receive direction (see profile definition for “WhiteList Filter”).
· WhiteList Filter for passive PRE

- This WhiteList Filter is only active when the protocol element (PRE) is set to redundancy state “passive” with
redundancy control message.
- In redundancy state “passive” the profile for “WhiteList Filter” is used and additionally the system messages in
the private range for SICAM RTUs <TI:=135> „SICAM RTUs systemdata container (TI:=135, FC=148, IC=04)“
will be passed.
- In redundancy state “active” the profile “SICAM RTUs - IEC101“ will be used.
· SICAM RTUs - IEC101 (SICAM RTUs “Standard“)

- WhiteList Filter disabled (=default)
- This profile is typically used for interfacing SICAM RTUs systems within region of same provider.
- All supported type identifications from interoperability of SICAM RTUs using balanced mode according to
IEC60870-5-101 (BPP) incl. type identifications used by SICAM RTUs in private range (remote diagnostics, remote
configuration,…) will be passed through in transmit-/receive direction.

DC0-023-2.12, Edition 06.2017
WhiteList Filter
· the WhiteList Filter is not an interoperability document!

· the WhiteList Filter has the same definition in transmit-/receive direction
·
1)
filtered messages in transmit direction will be discarded without error
(message will be logged as normal in data flow test)
· filtered messages in receive direction will be confirmed to remote station and discarded
1)
without error
(filtered messages cannot be logged in data flow test)
· Special functions for commands:
Command messages with originator address = “0“ will be filtered in case of “COT ≠ 6” or
“COT ≠ 8”.
For commands sent with COT=ACT/DEACT, the reply for the command in receive
direction with COT=ACTCON (DEACTCON)/ACTTERM will be passed only in a time
window when this command was sent before wit COT=ACT/DEACT via this interface.
For commands received with COT=ACT/DEACT, the reply for the command in transmit
window when this command was received before wit COT=ACT/DEACT via this interface.
The time window is set to 600 seconds and cannot be parameterized.
The WhiteList Filter function stores for up to 200 commands running at the same time the
address for the command, direction (transmit/receive) and the interface information.
After termination of the command sequence according IEC60870-5-101/-104 standard
(ACTàACTCONàACTTERM) the stored command information will be deleted.
The stored command information is deleted at a faulty command sequence after expiry of
the time window at the latest.
1)
Error will be set for messages with type identifications not supported according WhiteList Filter
definition.
No Error will be set for messages with type identifications supported according WhiteList Filter
definition but with cause of transmission not supported according WhiteList Filter definition.

Edition 06.2017, DC0-023-2.12
3.5.2.4.1 Sample Applications
Following function is the same for different sample applications.
When WhiteList Filter is enabled:
· routing of unwanted message within the system will be stopped

· unwanted messages will not be transmitted
· unwanted messages in receive direction will not be passed through
· ACTCON/ACTTERM for commands will be sent only if this command was received before
via this interface
Partner Interface between SICAM RTUs Systems
Data exchange via interface (LAN, serial) between different partners (utilities) – both partners
are using SICAM RTUs systems.
Partner A Partner B
SICAM AK or TM SICAM AK or TM
WhiteList-Filter WhiteList-Filter
ETA4 or BPPA0
Messages Messages
Automation network Automation network
Unwanted message in traget system

DC0-023-2.12, Edition 06.2017
rd
Partner Interface between SICAM RTUs System and 3 Party System
Data exchange via interface (LAN, serial) between different partners (utilities) – one partner
rd
use SICAM RTUs system the other partner uses a 3 party system.
Partner A Partner B
SICAM AK or TM
Third-party system
WhiteList-Filter
ETA4
or
BPPA0
Messages Messages
Internal Segmentation between SICAM RTUs Systems
Data exchange via interface (LAN, serial) between different divisions within the same partner
(utility) – both divisions are using SICAM RTUs systems.
Automation network
Subnet A Subnet B
ETA4 or BPPA0

Edition 06.2017, DC0-023-2.12
rd
Internal Segmentation between SICAM RTUs Systems and 3 Party Systems
Data exchange via interface (LAN, serial) between different divisions within the same
rd
customer – one division uses a SICAM RTUs system the other division uses a 3 party
system.
Automation network
Subnet A Subnet B
SICAM AK or TM
Third-party system
WhiteList-Filter
ETA4
or
BPPA0
Redundant SICAM RTUs Automation Units
The WhiteList Filter is only enabled on the interfaces between the redundant systems. All
other interfaces are not affected.
Control center
Automatision network
with redundant AUs
ETA4 logical ETA4

or connection or
BPPA0 BPPA0
WhiteList-Filter Redundancy WhiteList-Filter

voter
SICAM AK SICAM AK
or TM or TM
WhiteList WhiteList
Filter (optional) Filter (optional)
ETA4 ETA4
or logical or
BPPA0 connection (optional) BPPA0

DC0-023-2.12, Edition 06.2017
Redundant SICAM RTUs Basic System Elements (BSE’s)
· The WhiteList Filter disables possible unwanted routing of system messages or messages
in the private range via possible communication loops in redundancy configuration for
redundant BSE’s.
Note:
A routing of data messages to redundant BSE’s will be suppressed per standard by passive BSE.
· The WhiteList Filter must be parameterized on PREs on both BSE’s.

· The WhiteList Filter is only activated on “passive” BSE and deactivated on “active” BSE.
Control Center
Automation network
with redundant AUs and BSEs
ETA4 logical ETA4

or connection or
BPPA0 BPPA0
WhiteList-Filter
Redundancy WhiteList-Filter
voter
SICAM AK SICAM AK
or TM or TM
WhiteList-Filter P P WhiteList-Filter
for passive PRE for passive PRE
SICAM AK with redundant

basic system elements
Aktive Passive
BSE BSE
Filter
not Filter
active! active!
System message

Edition 06.2017, DC0-023-2.12
Redundant SICAM RTUs Basic System Elements (BSE’s) – Remote Operation
· The WhiteList Filter disables possible unwanted routing of system messages via
communication loops in this redundancy configuration
· The WhiteList Filter must be parameterized on PREs on both BSE’s
· The WhiteList Filter is only activated on “passive” BSE.
· The messages from SICAM TOOLBOX II will be discarded by the activated
WhiteList- Filter on “passive” BSE but passed through on “active” BSE by non active
WhiteList Filter.
Control Center
Automation network
ETA4 logical ETA4

or connection or
BPPA0 BPPA0
SICAM RTUs WhiteList-Filter

voter
SICAM AK
or TM

Aktive Passive
BSE BSE
SICAM Filter
TOOLBOX II not Filter
active! active!
Remote operation

DC0-023-2.12, Edition 06.2017
3.5.2.4.2 Profile Definition: “White-List Filter”
The following table below includes the profile definition for “WhiteList Filter” and “WhiteList Filter for passive PRE”.
Messages with type identification will be passed through in transmit-/receive direction (CASDU “BROADCAST” not allowed)
1) Messages with type identification will be passed through in transmit-/receive direction (CASDU “BROADCAST” allowed)
Special functions for commands
2) Messages with type identification will be passed through in transmit-/receive direction (CASDU “BROADCAST” allowed) – only when “WhiteList Filter for passive PRE” is active
Messages with type identification will not be passed through in transmit-/receive direction (messages filtered out)
Type Identification COT Cause of Transmission

0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 20 37 42 44 45 46 47 48
to to to to to
19 36 41 43 63
<0>
<1> Single-point information M_SP_NA_1
<2> Single-point information with time tag M_SP_TA_1
<3> Double-point information M_DP_NA_1
<4> Double-point information with time tag M_DP_TA_1
<5> Step position information M_ST_NA_1
<6> Step position information with time tag M_ST_TA_1
<7> Bitstring of 32 bit M_BO_NA_1
<8> Bitstring of 32 bit with time tag M_BO_TA_1
<9> Measured value, normalized value M_ME_NA_1
<10> Measured value, normalized value with time tag M_ME_TA_1
<11> Measured value, scaled value M_ME_NB_1
<12> Measured value, scaled value with time tag M_ME_TB_1
<13> Measured value, short floating point value M_ME_NC_1
<14> Measured value, short floating point value with time tag M_ME_TC_1
<15> Integrated totals M_IT_NA_1
<16> Integrated totals with time tag M_IT_TA_1
<17> Event of protection equipment with time tag M_EP_TA_1
<18> Packed start events of protection equipment with time tag M_EP_TB_1
<19> Packed output circuit information of protection equipment with time tag M_EP_TC_1
<20> Packed single-point information with status change detection M_PS_NA_1
<21> Measured value, normalized value without quality descriptor M_ME_ND_1

Edition 06.2017, DC0-023-2.12

0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 20 37 42 44 45 46 47 48
to to to to to
19 36 41 43 63
<22-29>
<30> Single-point information with time tag CP56Time2a M_SP_TB_1
<31> Double-point information with time tag CP56Time2a M_DP_TB_1
<32> Step position information with time tag CP56Time2a M_ST_TB_1
<33> Bitstring of 32 bit with time tag CP56Time2a M_BO_TB_1
<34> Measured value, normalized value with time tag CP56Time2a M_ME_TD_1
<35> Measured value, scaled value with time tag CP56Time2a M_ME_TE_1
<36> Measured value, short floating point value with time tag CP56Time2a M_ME_TF_1
<37> Integrated totals with time tag CP56Time2a M_IT_TB_1
<38> Event of protection equipment with time tag CP56Time2a M_EP_TD_1
<39> Packed start events of protection equipment with M_EP_TE_1
time tag CP56Time2a
<40> Packed output circuit information of protection equipment with M_EP_TF_1
time tag CP56Time2a
<41-44>
<45> Single command C_SC_NA_1 * * *
<46> Double command C_DC_NA_1 * * *
<47> Regulating step command C_RC_NA_1 * * *
<48> Set point command, normalized value C_SE_NA_1 * * *
<49> Set point command, scaled value C_SE_NB_1 * * *
<50> Set point command, short floating point C_SE_NC_1 * * *
<51> Bitstring of 32 bit C_BO_NA_1 * * *
<52-55>
<58> Single command with time tag CP56Time2a C_SC_TC_1 * * *
<59> Double command with time tag CP56Time2a C_DC_TC_1 * * *
<60> Regulating step command with time tag CP56Time2a C_RC_TC_1 * * *
<61> Set point command, normalized value with time tag CP56Time2a C_SE_TA_1 * * *
<62> Set point command, scaled value with time tag CP56Time2a C_SE_TB_1 * * *
<63> Set point command, short floating point with time tag CP56Time2a C_SE_TC_1 * * *
<64> Bitstring of 32 bit with time tag CP56Time2a C_BO_TA_1 * * *
<65-69>
<70> End of initialization M_EI_NA_1
<71-99>
<100> Interrogation command C_IC_NA_1 1)
<101> Counter interrogation command C_CI_NA_1

<102> Read command C_RD_NA_1

DC0-023-2.12, Edition 06.2017

0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 20 37 42 44 45 46 47 48
to to to to to
19 36 41 43 63
<103> Clock synchronization command C_CS_NA_1

<104> Test command C_TS_NA_1
<105> Reset process command C_RP_NA_1
<106> Delay acquisition command C_CD_NA_1
<107> Test command with time tag CP56time2a C_TS_TA_1
<108,109>
<110> Parameter of measured value, normalized value P_ME_NA_1

<111> Parameter of measured value, scaled value P_ME_NB_1
<112> Parameter of measured value, short floating point value P_ME_NC_1
<113> Parameter activation P_AC_NA_1
<114-119>
<120> File ready F_FR_NA_1

<121> Section ready F_SR_NA_1
<122> Call directory, select file, call file, call section F_SC_NA_1
<123> Last section, last segment F_LS_NA_1
<124> Ack file, ack section F_AF_NA_1
<125> Segment F_SG_NA_1
<126> Directory {blank or X, only available in monitor (standard) direction} F_DR_TA_1*
<127>
<128-134>
<135> SICAM RTUs systemdata container (TI:=135, FC=148, IC=04) 2) 2) 2) 2) 2) 2) 2) 2) 2) 2) 2) 2) 2) 2) 2) 2) 2) 2) 2) 2) 2) 2) 2)

<136-141>
<142> SICAM RTUs user data container (TI:=142, message type = 128)
<143-255>

Edition 06.2017, DC0-023-2.12
Semantics of cause of transmission:

<0> := not used
<1> := periodic, cyclic
<2> := background scan
<3> := spontaneous
<4> := initialized
<5> := request or requested
<6> := activation
<7> := activation confirmation
<8> := deactivation
<9> := deactivation confirmation
<10> := activation termination
<11> := return information caused by a remote command
<12> := return information caused by a local command
<13> := file transfer
<14..19> := reserved for further compatible definitions (not used)
<20> := interrogated by station interrogation
<21..36> := interrogated by group 1..16 interrogation
<37> := requested by general counter request
<38..41> := requested by group 1..4 counter request
<42, 43> := reserved for further compatible definitions (not used)
<44> := unknown type identification
<45> := unknown cause of transmission
<46> := unknown common address of ASDU
<47> := unknown information object address
<48, 63> := for special use (private range - not used)

DC0-023-2.12, Edition 06.2017
3.5.2.4.3 Profile Definition: “SICAM RTUs – IEC101”
The profile SICAM RTUs – IEC101 (“SICAM RTUs Standard“) defines functionality according interoperability for SICAM RTUs according IEC60870-5-101 (BPP).
This profile will be used as standard for interfacing SICAM RTUs components.
… more details see document “SICAM RTUs Interoperability IEC 60870-5-101/104 chapter 2 “Architecture and Data Flow“
Messages will be supported (B=both directions, X=standard direction)

Messages will not be supported (valid according IEC60870-5-101 standard)
Messages will not be supported

0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 20 37 42 44 45 46 47 48
to to to to to
19 36 41 43 63
<0>
<2> Single-point information with time tag M_SP_TA_1 B

<4> Double-point information with time tag M_DP_TA_1 B
<5> Step position information M_ST_NA_1 B B* B* B* B*
<6> Step position information with time tag M_ST_TA_1 B* B* B*
<7> Bitstring of 32 bit M_BO_NA_1 B B* B*
<8> Bitstring of 32 bit with time tag M_BO_TA_1 B*

<20> Packed single-point information with status change detection M_PS_NA_1 6) 6)

<22-29>

Edition 06.2017, DC0-023-2.12

0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 20 37 42 44 45 46 47 48
to to to to to
19 36 41 43 63
<31> Double-point information with time tag CP56Time2a M_DP_TB_1 B
<32> Step position information with time tag CP56Time2a M_ST_TB_1 B* B* B*
<33> Bitstring of 32 bit with time tag CP56Time2a M_BO_TB_1 B*
<35> Measured value, scaled value with time tag CP56Time2a M_ME_TE_1 B
<37> Integrated totals with time tag CP56Time2a M_IT_TB_1 B

time tag CP56Time2a
B
time tag CP56Time2a
<41-44>
<45> Single command C_SC_NA_1 B B B B B B B B B
<46> Double command C_DC_NA_1 B B B B B B B B B
<47> Regulating step command C_RC_NA_1 B B B B B B B B B
<48> Set point command, normalized value C_SE_NA_1 B B B B B* B B B B
<49> Set point command, scaled value C_SE_NB_1 B B B B B* B B B B
<50> Set point command, short floating point C_SE_NC_1 B B B B B* B B B B
<51> Bitstring of 32 bit C_BO_NA_1 B* B* B* B* B* B B B B
<52-55>
<58> Single command with time tag CP56Time2a C_SC_TC_1 B B B B B B B B
<59> Double command with time tag CP56Time2a C_DC_TC_1 B B B B B B B B
<60> Regulating step command with time tag CP56Time2a C_RC_TC_1 B B B B B B B B
<61> Set point command, normalized value with time tag CP56Time2a C_SE_TA_1 B B B B B* B B B
<62> Set point command, scaled value with time tag CP56Time2a C_SE_TB_1 B B B B B* B B B
<63> Set point command, short floating point with time tag CP56Time2a C_SE_TC_1 B B B B B* B B B
<64> Bitstring of 32 bit with time tag CP56Time2a C_BO_TA_1 B* B* B* B* B* B B B
<65-69>
<70> End of initialization M_EI_NA_1 B
<71-99>
<100> Interrogation command C_IC_NA_1 B B B B B B B
<101> Counter interrogation command C_CI_NA_1 B B B B B B B

<103> Clock synchronization command C_CS_NA_1 B B B X X X
<104> Test command C_TS_NA_1 B B B X X X

DC0-023-2.12, Edition 06.2017

0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 20 37 42 44 45 46 47 48
to to to to to
19 36 41 43 63
<105> Reset process command C_RP_NA_1 X* X* B X X X
<106> Delay acquisition command C_CD_NA_1 B B B B X X X

<108,109>
<110> Parameter of measured value, normalized value P_ME_NA_1 X X X B X X X
<111> Parameter of measured value, scaled value P_ME_NB_1 X X X B X X X
<112> Parameter of measured value, short floating point value P_ME_NC_1 X X X B X X X

<114-119>
<120> File ready F_FR_NA_1 B B 5) 5) 5)
<121> Section ready F_SR_NA_1 B B 5) 5) 5)
<122> Call directory, select file, call file, call section F_SC_NA_1 B B B 5) 5) 5)
<123> Last section, last segment F_LS_NA_1 B B 5) 5) 5)
<124> Ack file, ack section F_AF_NA_1 B B 5) 5) 5)
<125> Segment F_SG_NA_1 B B 5) 5) 5)
<126> Directory {blank or X, only available in monitor (standard) direction} F_DR_TA_1* X X

<127>
<128-134>
<135> SICAM RTUs systemdata container (TI:=135, FC=148, IC=04) B B B B B B B B B B B B B B B B B B B B B B B

<136-141>
<142> SICAM RTUs user data container (TI:=142, message type = 128) B B B B B B B B B B B B B B B B B B B B B B B
<136-255>
*) .… blank or “X“ only

+
…..secondary application function only
B* … can be generated by PLC
5) .… transparent transmission by system
6) …. Reception possible, thereby the blocked single-point information is deblocked and further individually processed as TI = 30 (address translation occurs algorithmic).

Edition 06.2017, DC0-023-2.12
3.5.2.5 Data Throughput Limitation
The protocol element for IEC60870-5-101 balanced point-to-point does not support specific
functions for reduction of data throughput.
Data throughput can be reduced as follows:
· reducing the baud rate

(change of baud rate must be done also in remote system)
· delay before sending

e.g.: pause time “tp“
Note:
- by increasing the pause time (for data throughput reduction) a change of acknowledge timeout monitoring time in
the remote system may be necessary.

DC0-023-2.12, Edition 06.2017
3.5.2.6 Convert General Interrogation Command in Receive Direction to

BROADCAST

GI command "broadcast" all general interrogation commands <TI=100> received from the
protocol element are passed on from the transmission line with the "cause of transmission =
activation" to the basic system element with the address CASDU = BROADCAST.
3.5.2.7 Non Interruptible GI
According IEC 60870-5-101, spontaneous or periodic data can be sent during general
interrogation and thus the general interrogation can be interrupted.
When interfacing to third-party systems it can be necessary to disable the spontaneous or
periodic data transmission during general interrogation.
Note:
A detailed description of the function "Non Interruptible GI" can be found in the section
"General Interrogation, Outstation Interrogation".
3.5.2.8 Emulate ACTCON+ for Clock Synchronization Command
The transmission of ACTCON+ by the protocol element for clock synchronization can be set
with the parameter advanced parameters | IEC60870-5-101 | ACTCON for clock
sychronization command as follows:
· Do not send (=default)

· Send immediately
· Send after minute change and internal transfer of the time (DEFAULT)

Edition 06.2017, DC0-023-2.12
3.5.2.9 Emulate ACTCON+/- for Commands
· If ACTCON is not supported by the basic system element or by the peripheral element
used, then the emulation of ACTCON can be performed by the protocol element (PRE) as
follows:
Emulation of Note
ACTCON- for <TI=45> single command
<TI=46> double command
<TI=47> regulating step command
<TI=48> setpoint command, normalized value
<TI=49> setpoint command, scaled value
<TI=50> setpoint command, floating point number
ð ACTCON- send immediately from PRE if
* CASDU is not known to the PRE
ð ACTCON+/- from BSE or PE is sent from PRE
ACTCON- for <TI=100> (general-) interrogation command
* CASDU is not known to the PRE and
* CASDU ≠ FFFF (=BROADCAST)
ð ACTCON+/- from BSE is sent from PRE
ACTCON+/- for <TI=101> counter interrogation command
ð ACTCON+ send immediately from PRE if
* CASDU is known to the PRE or
* CASDU = FFFF (=BROADCAST)
ACTCON+/- for <TI=103> clock synchronization command if
ð ACTCON+ send from PRE if
* CASDU = FFFF (=BROADCAST) *)
*) the moment for the transmission of ACTCON+ can be parameterized with the parameter advanced
parameters | IEC60870-5-101 | ACTCON for clock sychronization command
Legend:

PE ........... Protocol element
The emulation of ACTCON by the protocol element (PRE) can be activated with the
parameter advanced parameters | IEC60870-5-101 | ACTCON +/- emulation. So
that the emulation can be performed by the protocol element, it must be ensured that the INIT-
End messages are passed on from the basic system element to the protocol element
(required because of the known CASDU addresses).
The parameter setting necessary is to be performed on the basic system element (BSE) in the
IEC 60870-5-101/104 parameter block.

DC0-023-2.12, Edition 06.2017
3.5.2.10 Emulate ACTCON+ for Commands
If ACTCON for commands is not supported by the peripherals element used, then the
emulation of ACTCON messages can be performed by the protocol element of the remote
terminal unit as follows:
Emulation of Note
ACTCON+ for <TI=45> single command
ð ACTCON+ from PRE send immediately (for SELECT and EXECUTE
command)
ð ACTCON+/- from BSE is filtered out by PRE and not sent!
ð ACTTERM+/- from BSE is sent from PRE
The emulation of ACTCON by the protocol element (PRE) for commands can be activated
with the parameter advanced parameters | IEC60870-5-101 | ACTCON emulation.
With function activated, ACTCON messages are emulated by the protocol element as shown
in the table. All ACTCON+/- messages that are transferred from the basic system element to
the protocol element are filtered out by the protocol element and therefore not transmitted.
ACTTERM messages that are transferred from the basic system element to the protocol
element are transmitted by the protocol element.
With function not activated, ACTCON and ACTTERM messages that are transferred from the
basic system element to the protocol element are transmitted by the protocol element, no
emulation of any kind by the protocol element takes place.
Note:
This function is not required in SICAM RTUs or if the this function is supported by the
peripheral elements used!
For the emulation of ACTCON- with unknown CASDU, the parameter advanced
parameters | IEC60870-5-101 | ACTCON +/- emulation is to be enabled.

Edition 06.2017, DC0-023-2.12
3.5.2.11 Emulate ACTCON, ACTTERM for Commands with Control

Messages
If ACTCON and ACTTERM for commands are not supported by the system, then the
emulation of ACTCON and ACTTERM – controlled by control messages – can be emulated
by the protocol element (PRE) for a previously received command.
This emulation for ACTCON, ACTTERM is often used when a protocol element for the
interfacing of external systems or one external system itself does not support this function.
The emulation of ACTCON, ACTTERM is activated on the protocol element, if the type
identification in the parameter advanced parameters | project specific | ACTCON,
ACTTERM for commands controlled by control messages | TI and the monitoring
times for ACTCON, ACTTERM "≠ 0" are parameterized.
The control can be performed by an application program of the open-/closed-loop control

function.
Due to the control messages the emulation of the messages ACTCON+/- and ACTTERM+/- of
a previously received command (TI=45, TI=46, TI=47 - Select or Execute) to the remote
station is triggered.
A message with optional type identification can be used as control message – the data
content of the control messages is not evaluated by the protocol element. The identification of
the control message takes place based only on the parameterized address.
In addition the protocol element performs a "1 out of n" check for commands.
If a further command is received from the remote station, although the previously received
command has not yet been terminated, a negative confirmation (ACTCON-) is transmitted
immediately by the protocol element to the remote station.
The control of the emulation of the messages ACTCON+/-, ACTTERM+/- by the application
program of the open-/closed-loop control function is monitored by the protocol firmware. If the
corresponding control message is not received by the protocol element within the monitoring
time, the protocol element itself sends an ACTCON- or ACTTERM- to the remote station.
The monitoring time for the reception of the confirmation of activation is to be set on the
protocol element with the parameter advanced parameters | project specific |
ACTCON, ACTTERM for commands controlled by control messages | monitoring
time ACTCON (after ACT).
The monitoring time for the reception of the termination of activation is to be set on the
protocol element with the parameter advanced parameters | project specific |
ACTCON, ACTTERM for commands controlled by control messages | monitoring
time ACTTERM (after ACTCON).
The IEC 60870-5-101/104 address of the control message (TI, CASDU1, CASDU2, IOA1,
IOA2, IOA3) for the emulation of ACTCON+ is to be parameterized with the parameter
advanced parameters | project specific | ACTCON, ACTTERM for commands
controlled by control messages | *. The addresses of the other control messages are
defined.
Address for Control Message *) Control Message

Parameterized address Control message for emulation ACTCON+
Parameterized address, IOA+1 Control message for emulation ACTCON-
Parameterized address, IOA+2 Control message for emulation ACTTERM+
Parameterized address, IOA+3 Control message for emulation ACTTERM-
*) if TI=0 is parameterized, no emulation by the protocol element takes place; ACTCON, ACTTERM
messages are transferred from the basic system element to the remote station

DC0-023-2.12, Edition 06.2017
3.5.2.12 Compatibility TCS100
For the interfacing of SICAM RTUs stations which use the protocol firmware TCS100,
corresponding parameters are to be set to ensure the compatibility concerning type of
addressing.
The type of remote station is set with the parameter advanced parameters |
compatibility TCS100 | Remote station "TCS100".
With the parameter advanced parameters | compatibility TCS100 | Address
mapping at TCS100 the type of address parameterized in the TCS100 protocol firmware is
to be set.
With the parameter advanced parameters | compatibility TCS100 | Attached
region number using remote station type TCS100 the region number to be added in
receive direction is to be selected. Either the "own region number" or a parameter-settable
region number can be added.
The parameter-settable region number is to be set with the parameter advanced
parameters | compatibility TCS100 | region number of remote station.
3.5.2.13 Settings for Project DBAG
For the implementation of the protocol firmware in DBAG projects the following special
functions can be activated:
· Breaker delay in transmit direction (DBAG-specific special message format <TI=150>)
· Send originator address with settable value
These special functions can be activated with the parameter advanced parameters |
project specific | parameter settings for project DBAG/PSI.
With function activated, messages in the format <TI=33> "32 Bit bit pattern" in the direction
basic system element ð protocol element are converted by the protocol element to the
DBAG-specific message format <TI=150> and transmitted.
Messages received in the format <TI=150> are converted by the protocol element to the
format <TI=33> "32 Bit bit pattern" and passed on to the basic system element.
In transmit direction <TI=33> "32 Bit pattern" is converted as follows:
Cause of IEC-Parameter Type Identification for Transmission to the Remote

Transmission Station
spontaneous - <TI=150> DBAG-specific format
GI with time (3 octets) <TI=4> double-point information with time tag
CP56Time2a
GI without time <TI=3> double-point information
In receive direction <TI=150> is converted as follows:
Cause of Time Format Type Identification for Transmission to Basic

Transmission System Element
spontaneous, GI with time (7 octets) <TI=33> Bitstring of 32 bits with time tag
CP56Time2a
Note:
The format <TI=150> is only defined with 7 bytes time, 3 bytes IOA, 2 bytes CASDU and 2
bytes URS! For the format <TI=150> in addition no double transmission is defined as format
without time tag!

Edition 06.2017, DC0-023-2.12
Breaker delay in transmit direction
If the delay of the circuit breaker or the time of the fault current is not available, this time can
be added by the protocol element in messages in transmit direction with the parameter
advanced parameters | project specific | parameter settings for project
DBAG/PSI | switch transfer time in transmit direction.
Message structure <TI=150> "Railway-specific Format" (in the private range)
27 26 25 24 23 22 21 20
150 Type identification
SQ Number of information objects variable structure qualifier
T P/N Cause of transmission Cause of transmission
Originator address
Station address CASDU1
N CASDU2
Technological Code (TC) IOA1
1 IOA2
0 Field address IOA3
SK8 SK7 SK6 SK5 SK4 SK3 SK2 SK1 Protection criteria (BDK)
Protection criteria reserve
0 - 255 Fault code (AK of SLT)
2ms – Code (0-255) Breaker delay
IV NT SB BL DPI DIQ of DOM
Originator time in format CP56Time2a
(corresponds to TL SCHINA, DB_Network) Dual time (7 octets)
Send originator address with settable value
In DBAG projects the originator address in transmit direction is always transferred with a fixed
parameterized value. The originator address is to be set with the parameter advanced
parameters | project specific | parameter settings for project DBAG/PSI |
originator address in transmit direction.
For this function the setting of the number of octets for cause of transmission to "2 octets" is
necessary (see IEC 60870-5-101/104 Parameters on the Basic System Element).

DC0-023-2.12, Edition 06.2017
3.5.2.14 Settings for Project RWE
For the implementation of the protocol firmware in RWE projects the following special
· NT-Bit, IV-Bit according to RWE requirements
project specific | RWE functions.
3.5.2.14.1 NT-Bit, IV-Bit according to RWE Requirements
For projects for the customer RWE, a special handling can be activated for the NT-bit and the
IV-bit of the quality descriptor of the messages in transmit direction.
If the RWE-specific functions are not activated, the NT-bit and the IV-bit in the messages are
transferred to the remote station unchanged.
If the RWE-specific functions are activated, the special handling for the NT-bit and the IV-bit
can be selected with the parameter advanced parameters | project specific | RWE-
Functions | convert of the NT bits to the IV bit in transmit direction
from the following options::
· “Variant a”: (selection = <disabled>)

NT-bit is set to "0", IV-bit is not changed
· <enabled> = “Variant b”: (selection = <enabled>)
NT-bit is set to "0", IV-bit is set if NT-bit (internal) or IV-bit (internal) is set
SICAM RTUs internal To Remote Station (Variant a) To Remote Station (Variant b)

NT-Bit IV-Bit NT-Bit IV-Bit NT-Bit IV-Bit
0 x 0 x 0 x
1 x 0 x 0 1
0 0 0 0 0 0
0 1 0 1 0 1
1 0 0 0 0 1
1 1 0 1 0 1
x = optional state, or state is not changed!

Edition 06.2017, DC0-023-2.12
3.6 Transparent Mode (Tunneling, Container Mode)
The Transparent Mode (or Container Mode) is used to pass through external computer
messages in IEC 60870-5-101 format between a remote station and a third-party control
system that is connected to the SICAM RTUs component with IEC 60870-5-104. The
container mode thus provides a "tunneling method" within the system SICAM RTUs.
These external computer messages are transmitted to or received from an external control
system in a user data container defined for SICAM RTUs in the private range of the IEC
60870-5-101.
The user data container is then not sent to the remote station, rather the IEC 60870-5-101
message contained in the message data of the user data container.
As a result either message formats in the public or private range of the IEC 60870-5-101
standard not supported by the System SICAM RTUs can be transmitted from a third-party
remote terminal unit to a third-party control system or all messages according to
IEC 60870-5-101 which do not need to be routed individually when using the container mode
in the System SICAM RTUs.
In container mode only the user data messages are transmitted transparently through the
SICAM RTUs network – messages for protocol control (station initialization, acknowledgement
messages,...) are not transmitted and are dealt with directly at the interface to the serial
interfaced external system by the protocol element.
With special procedures (e.g.: remote parameterization of a third-party system by a third-party

control system), before using the container mode it is to be checked whether the changed
chronological behavior will be tolerated by the connected third-party system and that no error
messages or failures occur as a result.
The transmission of the user data container within SICAM RTUs takes place with type
identification <TI=142> in the private range of IEC 60870-5-101 or IEC 60870-5-104
respectively. SICAM RTUs internal, several modes are provided for the use of the user data
container. The container mode uses the user data container with message type = 128 (=1703
Standard-Format).
The container mode can be activated separately for transmit / receive direction with the
parameter advanced parameters | project specific | parameter settings for
project DBAG/PSI | originator address in transmit direction and the
parameter advanced parameters | project specific | parameter settings for
project DBAG/PSI | switch transfer time in transmit direction.
With container mode activated in receive direction, all valid received messages from the third-
party system are entered in a user data container and passed on from the protocol element to
the basic system element for further distribution within the system.
With container mode activated in transmit direction, data to be sent are transferred from the
basic system element to the protocol element in a "user data container <TI=142> and
message type = 128“, read out from the user data container and the message data sent to the
third-party system.
All other data passed on from the basic system element to the protocol element for
transmission are sent unchanged to the third-party system.
The IEC-address of the user data container is fixed defined and is not to be parameterized.
(CASDU = CASDU of the remote terminal unit; IOA1, IOA2 = 255; IOA3 = 191)

DC0-023-2.12, Edition 06.2017
Segmentation
With user data containers a maximum of 180 bytes of transparent message data can be
transmitted.
Longer external computer messages (max. 256 bytes) are thus to be transmitted in several
part segments and grouped together again before transmission/processing. With missing
segments the partially transmitted parameter message is discarded.
The transparent mode only utilizes part segments with a max. length of 50 bytes of message
data!
User data container <TI=142>

The user data container is used to pass through external computer messages.
27 26 25 24 23 22 21 20
Type identification = 142
SQ 1 variable structure qualifier
Originator address
CASDU1
CASDU2
IOA1
IOA2
IOA3
: : : : : : : :
: : : : : : : : 7 bytes dual time (IEC 60870-5-101)
: : : : : : : :
Length of user data in bytes 1)
128 Message type = 128
45 UEK = 45
S=1 I=0 Status = 0x02
Number of bytes 2)
Interface number (process channel)
Sum of the segments = 1 Current segment number = 1 Segment information
22 Protocol type = 22 (=IEC 60870-5-101)
0 Reserve
Length of the message data in Bits

(LSB)

(MSB)
0 0 0 0 Function Message data (0)
: : : : : : : : :
: : : : : : : : :
: : : : : : : : :
Message data (n) max. 50 bytes
1) Length of the user data from the field UEK up to the last byte of the message data (n)
2) Number of bytes of the message data + 6 (max. 56 bytes)
Note:
The user data container is described here in the internal format of the protocol element with
the essential information fields.

Edition 06.2017, DC0-023-2.12
Elements of the Message

TI .. type identification <TI=142> User data container
CASDU, IOA .. Message address
O1 .. Octet 1 (CASDU) CASDU = CASDU of the remote station
O2 .. Octet 2 (CASDU) CASDU = CASDU of the remote station
IOA1 .. = 255
IOA2 .. = 255
IOA3 .. = 191 (subaddress)
Cause of transmission
03 .. spontaneous ... in monitoring direction
06 .. activation ... in control direction
Time
7 octets dual time Earliest possible acquisition moment of a message in AK
1703, time tag on the basic system element (BSE)
Message type = 128
Length of the user data part in Length of the user data in octets (exclusive message type)
octets
Number of bytes Number of bytes of the message data + 6
Segmentation field
Total number of segments Total number of segments (4 Bit)
... Total size = 15 segments each of 50 octets
Current segment number Current number of the transmitted segments (4 Bit)
... the 1st segment has segment number 1
Length of the message data in bit in all segments the total length of the message data is always
transmitted in bit.
Structure of the message data:

27 26 25 24 23 22 21 20
0 0 0 0 Function Control Byte Message data (0)
link address
Data (0)
:
:
Data (n) Message data (n)

Control byte "Function" (Bit 0-3)
03 .. User data SEND /
CONFIRM
04 .. User data SEND / NO
REPLY
Link address The length of the link address to be sent is determined with
a parameter.

DC0-023-2.12, Edition 06.2017
3.7 Protocol Element Control and Return Information
This function is used for the user-specific influencing of the functions of the protocol elements.
This function contains two separate independent parts:

· Protocol element control
· Protocol element return information
The Protocol Element Control enables:

· Setting the control location
· Data filter control
· Activation/Deactivation of Interface + Protocol
The Protocol Element Return Information enables:

· States of certain state lines to be used as process information
· Information about the station status/failure to be obtained
Block Diagram
Internal distribution for messages with process information
Protocol element
control
Internal
Transmission route
function
Protocol element
return information Protocol element
Messages with process information

Messages with system information

Edition 06.2017, DC0-023-2.12
3.7.1 Protocol Element Control
With the help of messages with process information, the protocol element control on the basic
system element enables specific functions of the protocol elements to be controlled.
The specific functions are determined by the protocol element implemented.
The assignment of the messages with process information to the functions is carried out with the
help of process-technical parameters of the SICAM RTUs system data protocol element control
message.
The messages for protocol control are transmitted immediately from the basic system element
to the protocol element, regardless of the user data to be sent and the priority control.
For messages with process information which are used in SICAM RTUs as protocol element control
message, an unused CASDU is to be used! All CASDU´s for process information are distributed
automatically to the corresponding remote terminal unit.

DC0-023-2.12, Edition 06.2017
Possible functions:
PST Detail Routing

Function SF Station Z-Par Fl Note
This function is processed on the BSE and
sent to the protocol element as system
Send (general) interrogation
240 255 - message and not using PRE-control
command
message!
CASDU = BROADCAST
Send (general) interrogation This function is processed on the BSE and
command for GI-group to own BSE 1) not sent to the protocol element as PRE-
241 255 -
(=simulate received general interrogation control message!
command for GI group)
Set/delete control location (global)

SCS=<ON>: Set control location (HKA)
Set control location 2) 242 255 65535 (global)
SCS=<OFF>: Delete control location (HKA)
(global)
Reset command - This function is not presently supported by
243 255
PRE!
244 255 CASDU message and not using PRE-control
command
message!
CASDU = selective
Data filter in transmit direction "ON" 0 255 - Do not send all messages from BSE
Data filter in transmit direction "OFF" 1 255 - Send all messages from BSE
Data filter in receive direction "ON" 2 255 - All received messages not to BSE
Data filter in receive direction "OFF" 3 255 - All received messages to BSE
255 - - Reset interface failure
"Deactivate" interface 4 - Do not send all messages from BSE
- Received messages are discarded
"Activate" interface 5 255 -
The PRE is forced to send a (general)
interrogation command (image-GI) to
Send (general) interrogation command FFFF, own BSE.
6 255
(image GI) 0-FFFE Z-PAR: FFFF .. all CASDU's
(BROADCAST)
0-FFFE … selective CASDU
2) - The control location can be enabled/disabled only by single command <TI=45>.
- Set control location function requires “additional parameter_(PRE)” (=Z-Par) = 65535 in BSE’s PST-detail
routing.
- If a PRE-control message for "set control location" is included in the PST-detailed routing on the BSE, the
BSE will send a PRE-control message "Set control location" with additional parameter = 65535 after startup of
the PRE to enable control location function on PRE.
- The control location (HKA) to be enabled/disabled is taken by the BSE firmware from the originator of the
command message used as PST control message and sent to PRE as PRE control message with additional
parameter set as follows:
SCS = <ON> additional parameter in PRE-control message = HKA

SCS = <OFF> additional parameter in PRE-control message = HKA + 256

Edition 06.2017, DC0-023-2.12
Possible functions: (continued)
Parameter
In redundancy mode "passive" and with
parameter "operation if passive" =
''Deactivate'' "transmitter tristate" the interface and
20 - -
Interface + protocol function protocol function can be
activated/deactivated via PRE control
message.
''Activate'' "transmitter tristate" the interface and
21 - -
message.
Legend:
SF ........... Control function_(PRE)

Station .... Station number (= 255 in point-to-point traffic)
Z-Par ...... Additional parameter_(PRE)
Fl ............ Edge
SCS ........ Single command state
HKA ........ Originator address "control location" (HKA)

DC0-023-2.12, Edition 06.2017
3.7.2 Protocol Element Return Information
The protocol element return information on the basic system element generates messages with
process information in monitor direction and thereby enables states of the protocol elements to
be displayed or processed.
There are three different categories of return information:
· Status of the status lines

· Protocol-specific return information (dependent on the protocol element used)
· Status of the stations
The assignment of the messages with process information to the return information is carried out
on the basic system element with the help of process-technical parameters of the
SICAM RTUs system data protocol element return information.
From which source the parameterized return information are to be generated, is set with the
parameters "Supplementary system element" and "Station number".
Messages for protocol element return information are transmitted spontaneously from the
protocol element to the basic system element with change or as reply to a general
interrogation command.
Possible return information BPP:
Parameter
Return information function_(PRE) Station Note
Status DTR 1)
Status DTR 255 0 = status line inactive
1 = status line active
Status DSR 1)
Status DSR 255 0 = status line inactive
Station failure 255 1 = Station failed 2)
Interface activated/deactivated":
Return information for PRE control message
"activate/deactivate" interface
protocol-specific return information 0 255
0 = interface "activated"
1 = interface "deactivated"
Interface + protocol functions "activated/deactivated":
"activate/deactivate" interface + protocol functions
0 = interface + protocol functions "deactivated"
1 = interface + protocol functions "activated"
1) States of the state lines are transmitted spontaneously from the protocol element to the basic system element
with change or as reply to a general interrogation command; the spontaneous transmission of the current states
takes place internally in a 100ms grid
ð state line changes shorter than 100ms are not guaranteed to be transmitted!
2) not supported by BSE!
Legend:
Station .... station number

255 = station number not used!

Edition 06.2017, DC0-023-2.12

DC0-023-2.12, Edition 06.2017
4 Multi-Point Traffic (UMP)
Contents
4.1 Introduction .................................................................................................... 84

4.4 Co-ordination of Several Masters.................................................................. 115
4.5 Standby Transmission Line over the Public Telephone Network (PSTN) ....... 117
4.6 Data Transmission using Time Slot Radio..................................................... 120
4.7 Data Transmission in Relay Operation "Multi-Point Traffic with Routing" ....... 121
4.10 Transparent Mode (Tunneling)...................................................................... 142

DC0-023-2.12, Edition 06.2017
Multi-Point Traffic (UMP)
4.1 Introduction
Multi-point traffic describes a serial communications protocol with which a master station is
connected with one or several remote terminal units over a communications link in a linear or
star configuration. The data traffic is controlled by the master station.
Either data messages or station interrogation messages are transmitted from the master
station. Data from the remote terminal unit to the master station can only be transmitted as
reply to a station interrogation.
Master station
TF
TF TF TF
Remote station-1 Remote station-2 Remote station-n n <= 100
Legende:
TF ………..….. Transmission Facility
In multi-point traffic an "unbalanced transmission procedure" is used. That means, that as

primary station the master station initiates all message transmissions, while the remote
terminal units, which are secondary stations, may only transmit when they are called.
The multi-point traffic only requires a "half duplex" transmission medium and can be used in a
star or linear structure.
The master station and the remote terminal units in multi-point traffic function with a
communications protocol according to IEC 60870-5-101. The supported functionality
(Interoperability) is shown in the document "IEC 60870-5-101/104 Interoperability
SICAM RTUs" in the section "Interoperability for SICAM RTUs in Multi-Point Traffic".
UMPMA0 SICAM AK3

SICAM AK
IEC 60870-5-101 Unbalanced (Multipoint MASTER)
SICAM BC
SICAM TM
UMPSA0 SICAM AK3
SICAM AK
IEC 60870-5-101 Unbalanced (Multipoint SLAVE)
SICAM BC
SICAM TM
UMPMT0 CP-8000
CP-802x IEC 60870-5-101 Unbalanced (Multipoint MASTER)
SICAM EMIC
UMPST0 CP-8000
CP-802x IEC 60870-5-101 Unbalanced (Multipoint SLAVE)
SICAM EMIC

Edition 06.2017, DC0-023-2.12
UMPMA0
UMPMT0
UMPSA0
UMPST0
General Functions
· Serial communication protocol according IEC60870-5-101 ü ü ü ü
· Unbalanced transmission Master ü ü
· Unbalanced transmission Slave ü ü

- Point-to-point configuration
- Multiple point-to-point configuration (separate interface for each

single point-to-point configuration required)
- Multipoint-partyline ü ü ü ü
- Multipoint-star ü ü ü ü
- max. Connections 100 1 100 1

- Controlled Station ü ü

− Unbalanced interchange circuit accordingV.24/V.28 standard ü ü ü ü
− Balanced interchange circuit X.24/V.28 ü 1) ü 1)
− Transmission medium (full duplex)
− Transmission medium (half duplex) ü ü ü ü

− Byte Frame (8E1) ü ü ü ü
− Data flow control Bit supervision ü ü
· Interoperability
− IEC60870-5-101 Ed.1 ü ü ü ü
− IEC60870-5-101 Ed.2

− SICAM RTUs Interoperability IEC 60870-5-101/104 (DC0-013-2) ü ü ü ü
− Ax 1703 Interoperability IEC 60870-5-101/104 (DA0-046-2) ü ü
· Data acquisition by polling (station interrogation) ü ü ü ü

− Continuous Interrogation of a Remote Terminal Unit ü ü
− Station failure delay ü ü
− Quick check procedure
· Acquisition of events (transmission of data ready to be sent) ü ü ü ü

DC0-023-2.12, Edition 06.2017
UMPMA0
UMPMT0
UMPSA0
UMPST0
General Functions
· General interrogation, outstation interrogation ü ü ü ü

− Non Interruptible GI ü ü
− Send GI-data as class 1 data ü ü
− Convert general interrogation command in receive direction to ü ü
Broadcast
− Do not store general interrogation commands in receive direction
− Timeout monitoring for GI-data
· Clock synchronization according IEC60870-5-101 ü ü ü ü

− Clock synchronization with <TI:=103> clock synchronization command ü ü ü ü
− Acquisition of transmission delay (primary station) used for correction
of clock synchronization with <TI:=106>
− Acquisition of transmission delay (primary station) used for correction ü ü
of clock synchronization (with request status of link = proprietary)
− Acquisition of transmission delay (secondary station) used for ü ü
correction of clock synchronization with <TI:=106>
− Correction of clock synchronization (via parameter) ü ü
− Accuracy +/- +/-
20ms 20ms
− Accuracy (relay operation) 2) +/- +/-

20ms 20ms
· Command transmission ü ü
− Demand ü ü

· Transmission of integrated totals ü ü
· File transfer ü ü ü ü
· Optimized parameters for selected transmission facilities (modems)

− Predefined optimized parameters for selected transmission facilities ü ü ü ü
− Free definable parameters for transmission facility ü ü ü ü
− 5V power supply via DSR status signal for external modems.
ü ü ü ü
· Standby transmission line over the public telephone network
ü ü
(PSTN)
· Data transmission using time slot radio ü ü ü ü
· Co-ordination of several masters ü ü ü ü
· Data transmission in relay operation mode

ü ü ü ü
(multi-point traffic with routing)
− Main and Standby Transmission Line ü ü ü ü

Edition 06.2017, DC0-023-2.12
UMPMA0
UMPMT0
UMPSA0
UMPST0
General Functions

− NUC redundancy (Norwegian Users Conventions) ü ü
- NUC redundancy „controlling station“ ü
- NUC redundancy „controlled station“ ü

− 1703 redundancy ü ü
- Listening mode when passive ü ü
- Tristate of RS-232 interface when passive ü ü

− Activation/Deactivation of interface when passive with protocol element ü ü
control message
− Deactivation of interface (with redundancy control message)

− Protocol element control messages
− Send (general) interrogation command to all ü ü ü ü

− Send (general) interrogation command for GI group to own BSE ü 3) ü 3) ü 3) ü 3)
− Send (general) interrogation command to selective CASDU ü ü

− Send (general) interrogation command for image GI to own BSE
− Reset command

− Data filter in transmit direction „ON/OFF“ ü ü
− Data filter in receive direction „ON/OFF“ ü ü
− Activate/Deactivate interface + protocol functions ü ü
− Add / Remove station to station polling ü ü
− Call cycle START / STOP / CONTINUE ü ü
− Continuous call station x ON / OFF ü ü
− Main/ Standby transmission line ACTIVE ü ü
− I – Bit handling for time ON / OFF ü ü
− Station failure ü ü
− Station status ü ü
− Status DTR (1 = state line active) ü ü ü ü
− Status DSR (1 = state line active) ü ü ü ü
− Protocol-specific return information 0 -3, 6, 7, 8- 11 ü ü
− Protocol-specific return value (retries in % of the last full hour) ü ü
· Remote maintenance with SICAM TOOLBOX II via serial connection ü ü

DC0-023-2.12, Edition 06.2017
UMPMA0
UMPMT0
UMPSA0
UMPST0
General Functions
− Summer time bit (SU)=0 for all messages in transmit direction (summer ü ü ü ü
time bit in time tag)
− Day of week (DOW)=0 for all messages in transmit direction (day of ü ü ü ü
week time tag)
− Originator address=0 for all messages in transmit direction ü ü ü ü
− WhiteList Filter
− Data Throughput Limitation
− Send GI-data as class 1 data ü ü

− Non interruptible GI ü ü
− Convert general interrogation command to BROADCAST in receive ü ü
direction
− Do not store general interrogation commands in receive direction ü ü
− Send End of init message as class 1 data ü ü
− Send ACTCON, ACTTERM message as class 1 data ü ü
− Send ACTCON for clock synchronization command ü ü
− Emulate ACTCON+/- ü ü
− Emulate ACTCON, ACTTERM for commands (with control message) ü ü
− Message synchronization ü ü
− Filtering of measured values with COT=3 (spontaneous) in transmit ü ü
direction
· Transparent Mode (Tunneling) ü ü
1) external converter CM-0829 required
2) with relay operation accuracy will be reduced 10 ms per routing station

Edition 06.2017, DC0-023-2.12
The operating mode of the interface is determined by parameters of the protocol element.
Standard Operation Parameter and Setting Interface Signals

Mode
Unbalanced Asynchronous / Isochronous
interchange circuit Asynchronous RXD, TXD, CTS, RTS, DCD, DTR,
V.24/V.28 DSR/+5V, GND
V.28 asynchronous
Optional Operation Parameter and Setting Interface Signals

Mode
Balanced interchange Asynchronous / Isochronous
circuit X.24/X.27 Isochronous
V.11 isochronous
Bit timing internal RXD, TXD, CTS, TXC, DCD, DTR,
DSR/+5V, GND
Bit timing external RXD, TXD, RTS, RXC, DCD, DTR,
DSR/+5V, GND
Balanced interface Asynchronous / Isochronous
RS-485 Asynchronous RXD, TXD, CTS, RTS, DCD, DTR,
V.11 asynchronous DSR/+5V, GND
with CM-0829
Optical interface Asynchronous / Isochronous
(multimode fiber optic) Asynchronous RXD, TXD, +5V, GND
with CM-0827

DC0-023-2.12, Edition 06.2017
4.2.1 Data Acquisition by Polling (Station Interrogation)
The transmission of the data from the remote terminal units to the master station takes place
by means of station-selective station interrogations (interrogation procedure, polling),
controlled by the master station; i.e., changed data is stored in the remote terminal unit and
transmitted to the master station with the interrogation of this remote terminal unit. The
interrogation procedure of the master station ensures, that remote terminal units are
interrogated sequentially, whereby remote terminal units with important data can be
interrogated more often. Remote terminal units may only transmit when they are called.
The interrogation procedure can be influenced with the following parameters:

· Continuous cycle
· Existing stations
· Number of calls until station change
· Number of stations to be called until change of priority level
· Priority level assignment (each station is assigned one of the 4 priority levels:
high priority, medium priority, low priority-A, low priority-B)
The interrogation procedure can be performed either continuously (= continuous cycle) or only
on request. The continuous interrogation of the remote terminal units by the master station
interrogation procedure is to be performed by enabling the parameter advanced
parameters | continuous cycle.
The station-selective parameters of the master station for the interrogation cycle such as "Stat
No", "Link Address", "Station Enabling", "Station failure", "Priority Level" and "Number of calls"
are to be set in the parameter station definition.
In every remote terminal unit, the station-selective address must be set with the parameter
Common settings | Address of the link. This address must be unambiguous for each
multi-point traffic line.
In the master station and in the remote terminal unit, the number of octets is to be
parameterized with which the address field is transmitted on the line with the parameter
advanced parameters | IEC60870-5-101 | Address field of the link (number).
The prioritization of the station interrogation can be parameterized by means of corresponding

parameter setting of the number of stations called until level change with the following
parameters:
Parameter
Ÿ Station call prioritization | No. of stat. calls in high priority lvl
Ÿ Station call prioritization | No. of stat. calls in mid. priority lvl
Ÿ Station call prioritization | No. of stat. calls in low prior. lvl(A)
Ÿ Station call prioritization | No. of stat. calls in low prior. lvl(B)

Edition 06.2017, DC0-023-2.12
Through parameterization of the interrogation procedure the following characteristics can be

achieved:
· A remote terminal unit which has a lot of data to send - e.g. continuously changing
measured values – does not impair the disposal of the data of the other remote terminal
units.
· Each remote terminal unit is interrogated within a determinable time (deterministic).
· Remote terminal units with important data or those with a large volume of data to be
transmitted can be interrogated more frequently than the others.
on request. The control of the interrogation procedure on request can be realized with protocol
control messages in the function diagram.
In the running interrogation cycle, data and system messages are transmitted spontaneously
from the master station according to the parameter setting as follows:
· One RTU selective (acknowledged)

· All RTU’s (unacknowledged)
If the interrogation cycle has been stopped by protocol control messages or the listening mode
is switched on, no station interrogation takes place. With the interrogation cycle stopped,
spontaneous data messages continue to be transmitted to the remote terminal units. With
listening mode switched on, the messages are normally not transmitted from the master
station to the remote terminal units, rather discarded directly on the basic system element
(BSE) by the function "User data filter".

DC0-023-2.12, Edition 06.2017
Example: Prioritization of the station interrogation
Below the prioritization of the station interrogation for continuous cycle is shown based on the
specified parameters as an example.
Parameter for "Station call prioritization"

High priority level ................... Number of stations called until level change = 2
Medium priority level .............. Number of stations called until level change = 2
Low priority level (A) .............. Number of stations called until level change = 1
Low priority level (B) .............. Number of stations called until level change = 1
Station U0, U4....................... High priority level / Number of calls until station change = 2
Station U1,U2,U3 .................. Medium priority level / Number of calls until station change = 2
Station U5,U6,U7, U8 ............ Low priority level (A) / Number of calls until station change = 1
Station U9,U10 ...................... Low priority level (B) / Number of calls until station change = 1
Œ
t
U0
U1
U2
U3
U4
U5
U6
U7
U8
U9
U9
U10
U10
Legend:
…..….. Remote station in the „High priority level“
…..….. Remote station in the „Medium priority level“
…..….. Remote station in the „Low priority level (A)“
U10 …..….. Remote station in the „Low priority level (B)“

,....….. Data message, short acknowledgement (remote station à master station)
,......Data message (Command), calling message (remote station à master station)
Z ………….….. Master station

U0..U10 ….….. Remote station U0 .. Remote station U10
Œ …………….. Command from master station à remote station U0
t ………………. Continous station polling time (request) from remote station U0 (after command from master station à remote station U0)

Edition 06.2017, DC0-023-2.12
variable elements of the message is required. These parameters are shown in the
Interoperability List (Master and all Slaves must have the same parameter settings).


Element
Address field of the link (number) Number of octets for the address field of the link PRE
layer
(CASDU) ASDU
information object
Acknowledgement IEC 60870-5-2 Acknowledgement on IEC 60870-5-2 layer PRE
Legend:
SSE ........ supplementary system element

(with serial interfaces this is always configured with a PRE)

DC0-023-2.12, Edition 06.2017
4.2.1.1 Continuous Interrogation of a Remote Terminal Unit
The "continuous interrogation of a remote terminal unit" can be activated automatically in the
master station with the function "Demand" or spontaneously with protocol control messages.
With function activated, a station interrogation is always executed by the master station to only
one selected station. An automatically started continuous interrogation of one remote terminal
following a message transmission is known as a demand.
Data messages ready for sending to same remote station will be sent during demand in
progress.
Through a demand, following a message transmission (e.g. command, setpoint value) the
master station can quickly fetch changed data from the remote terminal unit (e.g. measured
values after command or setpoint value). With demand, the continuous interrogation of a
remote terminal unit is terminated after timeout or a message to another remote terminal unit.
With control of the demand using protocol control messages, the continuous interrogation of a
remote terminal unit can be terminated spontaneously through a corresponding protocol
control message.
All data messages transmitted selectively to a remote terminal unit must be acknowledged by
this RTU. If, with non-faulty transmission line, the acknowledgement is missing for longer than
the expected acknowledgement time, transmitted messages are repeated up to n-times (n can
be parameterized). On expiry of the number of retries, the station is set as faulty.
The acknowledgement from the remote terminal unit to the master station can be transmitted
as single character (E5), if no additional information (such as DCF-Bit or ACD-Bit) is to be
transmitted. If additional information is to be transmitted, the acknowledgement is transmitted
as message with fixed length (ACK).
Instead of the acknowledgement with single character (E5H) the acknowledgement can be
transmitted as message with fixed length (ACK).
The message type for the acknowledgement can be selected in the remote terminal unit with
the parameter advanced parameters | IEC60870-5-101 | Acknowledgement
IEC60870-5-2.
connected remote terminal units must be taken into consideration.
The number of retries is to be set in the master station for messages for station interrogation
and data messages with the parameter Message retries | Retries for data message
SEND/CONFIRM (station selective) or for messages for station initialization with the
parameter Message retries | Retries for INIT-messages SEND/CONFIRM (station
selective).
The number of retries is to be set in the remote station for data messages with the parameter
Message retries | retries for data message (remote station --> master
station). On expiry of the number of retries (e.g. if the master station keeps unchanged the
FCB-Bit for a number of times when FCV=1), the interface will be marked as faulty in the
remote station and the protocol element of the remote station is waiting for new station
initialization.

Edition 06.2017, DC0-023-2.12
4.2.1.3 Failure Monitoring in the Master Station
The monitoring of the interface by the active master station takes place by means of the cyclic
running interrogation procedure (station interrogation). A remote terminal unit is reported as
failed by the master station after expiry of the number of retries. Retries to a remote terminal
unit are thereby always sent in succession immediately after expiry of the expected
acknowledgement time i.e. no other remote terminal units are interrogated during a running
retry handling. For failed remote terminal units, a communication fault is only then reported if
this is parameterized accordingly in the parameter "Station failure" of the station
definition.
The failure of remote terminal units is thus detected by the master station during the normal
interrogation cycle. Failed remote terminal units continue to be interrogated by the master
station with the interrogation procedure, however no message retry is performed for such
remote terminal units during the station interrogation.
The interrogation cycle for failed stations can be set with the parameter advanced
parameters | IEC60870-5-101 | polling cycle for faulty stations. As a result,
failed remote terminal units are removed from the running interrogation procedure for a certain
time and from then are only interrogated in the parameterized grid.
No data is transmitted from the master station to failed remote terminal units. The data is
stored in the data storage of the communication function on the basic system element (BSE)
until these are deleted by the dwell time monitoring or are transmitted to the non-failed remote
terminal unit.
Station failure delay

If short-term communication faults lead again and again to station failures, and the number of
retries in the master station is not to be increased further, then the transfer of the fault can be
delayed.
Through the station failure delay, short-term communication faults no longer lead to a station
failure.
With station failure delay, the failure of a remote terminal unit (after expiry of the number of
retries) is not immediately reported as failed, rather only after expiry of a settable delay time.
The delay time can be parameterized with the parameter advanced parameters |
station failure delay.
Station failure (PRE)

Station failure delay Station failure delay
Station failure (BSE)
Legend: Œ • Ž
Œ …………….. Station failure is forwarded to BSE
• …………….. Going station failure is forwarded to BSE
Ž …………….. Short-term station failure (PRE) not forwarded to BSE due to s tation failure delay
The station failure delay is performed by the protocol firmware of the master station station-
selective. With station failure delay only the "coming" fault is delayed – a "going" fault is
passed on immediately to the basic system element.
Note:
During the station failure delay, no data is transmitted to the affected remote terminal units. à
Due to the dwell time monitoring on the BSE, certain data is deleted after expiry of the
monitoring time if these could not be transmitted!

DC0-023-2.12, Edition 06.2017
4.2.1.4 Failure Monitoring in the Remote Terminal Unit
The monitoring of the interface in the remote terminal unit is performed by monitoring for
"cyclic message reception with station interrogation or station-selective data messages".
The monitoring time is to be set in the remote terminal unit with the parameter advanced
parameters | monitoring times | call monitoring time.
The monitoring timeout is normally only retriggered in the remote terminal unit with station-
selective call messages or station-selective data messages.
The parameter advanced parameters | monitoring times | call timeout

retrigger also with "request status of link" is only to be used if this function is
explicitly required (special functionality or due to downward compatibility). The message
"Request Status of Link" is transmitted from the master station during the initialization phase,
with the "acquisition time of the transmission time" and with station failure.
If during failure of the communication line (e.g. signaling direction only) in the remote terminal
unit a failure of the communication link is also to be detected, then the call timeout in the
remote terminal unit must not be retriggered with "Request Status of Link"!
The monitoring time in the remote terminal unit must be set sufficiently high, so that this does
not expire unintentionally during the transmission of larger quantities of data from other
remote terminal units (e.g. during general interrogation).
As an additional function the remote station can set the interface as faulty on expiry of retries
for data messages. The number of retries is to be set in the remote station for data messages
with the parameter Message retries | retries for data message (remote
station --> master station). On expiry of the number of retries (e.g. if the master
station keeps unchanged the FCB-Bit for a number of times when FCV=1), the interface will
be marked as faulty in the remote station and the protocol element of the remote station is
waiting for new station initialization.
With failed interface, data to be transmitted are stored in the data storage on the basic system
element (BSE) of the remote terminal unit until these are deleted by the dwell time monitoring
or can be transmitted to the master station.

Edition 06.2017, DC0-023-2.12
After startup, redundancy switchover or after communication error the operation of the
interface is started after successful station initialization. The failure of the interface will be
detected by the master station and remote station with the failure monitoring function.
The initialization of the link layer of the remote station is performed by the master station with:
Reset Command Function in the Remote Terminal Unit

REQUEST STATUS OF LINK - "STATUS OF LINK" is transmitted to the master station
RESET OF REMOTE LINK - FCB-Bit (Frame Count Bit) is initialized
- Acknowledgement for RESET of REMOTE LINK is
transmitted to master station
Data of the remote terminal unit ready to be sent are stored on the basic system element
(BSE) in the remote terminal unit until transmission.
See also section "Data Acquisition by Polling (Station Interrogation)".

DC0-023-2.12, Edition 06.2017
4.2.3.1 Message from the Remote Terminal Unit to the Master Station
Messages from the remote terminal unit to the master station are only transmitted with station
interrogation. A quick-check procedure for speeding up the transmission of data is not
implemented.
Coarse Time Message

When transmission of messages with short time format (ms, sec, min) is used, the protocol
element of the remote terminal unit can send the missing time information (date + hour) with
clock synchronization command in monitoring direction.
Notes:
- CP24Time2a … short time format (3 octet time information including ms and sec)
- CP56Time2a … long time format (7 octet time information including full date + time)
The transmission of the coarse time message can be activated with the parameter advanced
parameters | IEC60870-5-101 | coarse time in transmit direction.
Transmission of Coarse Time:
· do not send coarse time

· send coarse time always before message with short time tag
· send coarse time only when changed before message with short time tag
The coarse time will be sent using <TI:=103> clock synchronisation command in monitoring
direction with same CASDU, IOA of following message with time tag and cause of
transmission "spontaneous".
The coarse time will be sent automatically 1x after restart / redundancy switchover / RESET of
st
remote Link before following 1 message with time tag.

Edition 06.2017, DC0-023-2.12
A general interrogation command "to all" triggered in the system is always transferred by the
communications function on the basic system element (BSE) station-selective to the protocol
element of the master station and also transmitted station-selective by this to the remote
terminal units.
Non-Interruptible General Interrogation

Spontaneous data is also transmitted from the remote terminal unit during a running general
interrogation. With the parameter advanced parameters | IEC60870-5-101 | timeout
for non interrupted GI the spontaneous transmission of data can be disabled in the
remote terminal unit during a running general interrogation
(monitoring time: "0" = GI uninterruptible; "≠ 0" = GI is not uninterruptible).
The following parameter settings are necessary on the BSE for the non-interruptible GI:
· Sending of "end of initialization" (INIT-End) must be enabled
· General interrogation must take place from the process image (Image-GI)
With the INIT-End, the protocol element detects all ASDU's used in transmit direction.
This is required with general interrogation to all (BROADCAST) for GI-End detection.
With non-interruptible general interrogation, from the moment of "General interrogation

command received" all data of the spontaneous priority level from the basic system to the
protocol element are inhibited. This block is then terminated by the protocol element, if the
general interrogation is complete or the monitoring time "Timeout for non-interruptible GI" has
expired.
The monitoring time is to be set on the protocol element with the parameter advanced
parameters | IEC60870-5-101 | Monitoring time for GI-data and is used in
transmit direction for all ASDU's together. The monitoring time is retriggered for messages
with the causes of transmission <URS:=2, 7, 20, 21..36>. With general interrogation to a
selective ASDU, the monitoring time is stopped if the general interrogation command is
received with the cause of transmission <URS:=10> "Termination of Activation", with general
interrogation to all ASDU's (BROADCAST), the monitoring time is stopped if for all ASDU's the
general interrogation command is received with the cause of transmission "Termination of
Activation".

DC0-023-2.12, Edition 06.2017
The clock synchronization of the remote terminal units can be performed over the serial
communication line – controlled by the master station. The clock synchronization command
will be sent spontaneous at change of time or cyclic by the master station.
The period for cyclic clock synchronization can be set with the parameter advanced
parameters | cycle time for sending clock synchronization command.
Accuracy: typical ± 20 ms (clock synchronization 1x per minute)

(with relay operation accuracy will be reduced 10 ms per
routing station)
be used in the remote terminal unit.
Messages that are transmitted after a startup, but before the remote terminal unit has the
correct time, contain the relative time from startup (reference day: 1.1.2001) with the flagging
of the time tag as invalid.
The clock synchronization command is sent from the protocol element of the master station to
the remote terminal units either station-selective or BROADCAST according to the selected
transmission facility.
When using the "freely definable transmission facility" the type of transmission of the clock
synchronization command can be selected with the parameter Common settings | free
defineable interface modem | Send clock synchronization command to each
station selective.
With clock synchronization the time can be corrected by the remote station.
The correction time can be calculated by the master station using <TI:=106> "delay
acquisition command " and sent to the remote station or optionally configurable in the remote
station with the parameter advanced parameters | IEC60870-5-101 | correction
time for time synchronisation command (T_Delay).
· "T_Delay = 0":
The correction time (T_Delay) can be set by the master station using <TI:=106> delay
acquisition command (otherwise T_Delay = 0).
New time of RTU; time in ACTCON for <TI:=103> = t <TI:103> + tD<TI:=106> - tDtel
· "T_Delay <> 0":
New time of RTU; time in ACTCON for <TI:=103> = t <TI:103> + t_Delay
(t<TI:=103> = new time for remote station included in <TI:=103>; t<TI:=106> = correction time
included in <TI:=106>; tDtel = message transmission time)
If required the protocol element of the remote station can send the message "activation
confirmation" (ACTCON+) for the clock synchronization command.
This function can be enabled with the parameter advanced parameters | IEC60870-5-
101 | ACTCON for clock sychronization command as follows (se also section special
functions):

· Send immediately
· Send immediately and ignore (do not accept clock synchronization command)

Edition 06.2017, DC0-023-2.12
With relay operation the clock synchronization command is only transmitted BROADCAST via
selected routing paths. Only a few parameterized routing paths are used, with which all
stations (remote terminal units and routing stations) can be reached. All stations which receive
or forward a clock synchronization command use this for the synchronization of their own
clock.
Due to this necessary procedure a time setting operation with relay operation can also take
several minutes. During the transmission it is ensured, that the time in the clock
synchronization command is updated with each new emission. Delay times due to the
transmission facility are acquired automatically by the protocol element and taken into
consideration during the updating of the time.
4.2.6.1 Message from the Master Station selectively to a Remote

Terminal Unit
Station-selective data messages in command direction are always inserted into the running
interrogation procedure (station interrogation) by the master station with high priority after
termination of the data transmission in progress. Data to be sent from the basic system
element (=BSE) are always prioritized 1:1 with station interrogations.
Demand
If the reaction of the remote terminal unit to a transmitted message is to be acquired quickly
by the master station, a "Demand" (=parameter-settable station-selective continuous
interrogation) can be executed from the master station. This "station-selective demand" is
retriggered by further messages to the same station (message parameterized with demand),
or aborted by messages to other stations.
The selection of the type identification and setting of the continuous polling time for type
identification necessary for the "demand" can be performed in the parameters advanced
parameters | call procedure per type identification | *.
Data Flow Control

If a remote terminal unit cannot process more data messages (messages), the DFC bit (Data
Flow Control) is set in the control field of the message direction remote terminal unit ð master
station. From this moment the protocol firmware of the master station sends no more data
messages to the corresponding remote terminal unit, until the remote terminal unit resets the
DFC-bit. The protocol firmware also monitors whether the remote terminal unit resets the
DFC-bit within a time that can be set with the parameter advanced parameters |
IEC60870-5-101 | DFC-monitoring time.
If the DFC-bit is present for longer than the set monitoring time, the warning "DFC-Bit timeout
to station No. xx" is output.

DC0-023-2.12, Edition 06.2017
master station are only then transmitted to the addressed remote terminal unit if the command
has been sent from an enabled control location (originator address).
authority.
correspond with one of the control locations previously set.

the PRE.

Edition 06.2017, DC0-023-2.12

0 default
Note:
control function.
enabled").
Due to an information object "Control location" with the single command state "OFF", the
originator address is deleted from the list of enabled control locations (="control location not
enabled").
The deleting of the control locations can be carried out either station-selective for each control
location individually or globally for all stations and all control locations.

locations are to be set again after every startup of the protocol element.
(unacknowledged)
Messages from the multi-point traffic master station "unacknowledged to all" are inserted at
any time into a running interrogation cycle (station interrogation) after termination of the data
transmission in progress. The message is thereby transmitted several times by the master
station with the parameterized number of message retries according to the parameter
Message retries | Retries for data message SEND/NO REPLY (broadcast)
Afterwards the interrupted interrogation cycle is resumed.

DC0-023-2.12, Edition 06.2017
A counter interrogation command triggered in the system is transmitted from the protocol
element of the master station either station-selective or “to all” (=BROADCAST) according to
the parameter advanced parameters | IEC60870-5-101 | send counter
interrogation command as "Broadcast". This parameter is transferred to the basic
system element after startup of the protocol element.
A counter interrogation command to be sent is then already made available to the protocol
element by the basic system element, station-selective or BROADCAST.
60870-5-101/104".
The protocol element of the remote terminal unit supports the "Acquisition of transmission
delay" and the time correction resulting from this with clock synchronization according to IEC
60870-5. With this procedure the transmission delay is determined with <TI=106> and the
corrected time loaded in the remote terminal unit. The correction of the time in the clock
synchronization command is carried out in the remote terminal unit.
The protocol element of the master station uses a SICAM RTUs specific method for the
"acquisition of transmission delay". With this method the transmission delay per remote
terminal unit is determined by the protocol firmware of the master station with the sequence
"Request Status Of Link" and the reply from the remote terminal unit "Status of Link" and from
this an automatically determined correction value is derived.
The acquisition of the monitoring time can be carried out cyclic. The cycle time can be set with
the parameter advanced parameters | station specific clock sychronization |
cycle time for 1703-spec. acquisition of transmission delay.
With the parameter advanced parameters | station specific clock

sychronization | correction time for clock synchronization command an
additional correction value can be parameterized.
The clock synchronization command is transmitted station-selective. The time in the clock
synchronization command is already corrected by the protocol firmware of the master station
with the automatically determined correction value and the parameterized correction value.

Edition 06.2017, DC0-023-2.12

Facilities
The protocol element supports selected transmission facilities - for these the parameters are
set fixed – the selection of the transmission facility is carried out with the parameter Common
settings | interface modem. By selecting the "freely definable transmission facility"
certain parameters can be set individually.
facility.
When using the transmission facility "DLC-Modem (CE-0740, CE-0741)" in addition the
parameters DIP switch S1/1 .. S1/4 and the parameter frequency range (=current DIP-switch
settings of the DLC-Modem) must be parameterized in Common settings | DLC-Modem
(CE-0740, CE-0741) | *. These parameters are used for the optimization of the data
transmission via DCL-Modem (CE-0740, CE-0741) and for the automatic setting of the
required time settings in the protocol firmware.
When using the transmission facility "SATTELLINE 2ASxE Time Slot Radio Modem" in
addition the parameter Common settings | Time slot radio modem (SATTELLINE
2ASxE) | failure monitoring, the parameter Common settings | Time slot radio
modem (SATTELLINE 2ASxE) | length of time slot and the parameter Common
settings | Time slot radio modem (SATTELLINE 2ASxE) | start second of
time slot must be parameterized. These parameters are used for the optimization of the
data transmission with time slot radio technique.
After the transmission of broadcast messages an extra pause can be inserted regardless of
the transmission facility used. This pause is required for remote terminal units of third-party
manufacturers, if these can only process further messages after a transmission pause
following the reception of BROADCAST-messages.
The pause after broadcast messages can be set in the master station with the parameter
advanced parameters | advanced time settings | pause time after broadcast
message (tp_bc) and the parameter advanced parameters | advanced time
settings | pause time after broadcast message "time base" (tp_bc).
If the pause time is set to "0", a minimum pause of 33 bit is maintained by the protocol
element.

DC0-023-2.12, Edition 06.2017
Apart from this, a transmission facility, that can be freely defined by the user, can be selected,
for which all parameters that are available can be individually set. This is then necessary, if
transmission facilities are to be used that are not predefined or if modified parameters are to
be used for predefined transmission facilities. For the selection of the freely definable
transmission facility the parameter Common settings | interface modem is to be set to
"freely definable".
Only after that are all supported parameters displayed and can be parameterized with the
required values (see Table with Default Parameters for Transmission Facilities).
Parameter
Ÿ Common settings | free defineable interface modem | asynchron/isochron
Ÿ Common settings | free defineable interface modem | source for receive-
/transmit clock (only for "Isochronous")
Ÿ Common settings | free defineable interface modem | pause time (tp),
Ÿ Common settings | free defineable interface modem | pause time "time base" (tp)
Ÿ Common settings | free defineable interface modem | set up time (tv),
Ÿ Common settings | free defineable interface modem | set up time "time base"
(tv)
Ÿ Common settings | free defineable interface modem | run-out time (tn),
Ÿ Common settings | free defineable interface modem | run-out time "time base"
(tn)
Ÿ advanced parameters | advanced time settings | pause time after broadcast
message (tp_bc),
message "time base" (tp_bc)
Ÿ Common settings | free defineable interface modem | DCD handling
Ÿ Common settings | free defineable interface modem | bounce suppression time
(tbounce)
Ÿ Common settings | free defineable interface modem | disable time (tdis),
Ÿ Common settings | free defineable interface modem | disable time "time base"
(tdis)
Ÿ Common settings | free defineable interface modem | stability monitoring time
(tstab)
Ÿ Common settings | free defineable interface modem | continuous level monitoring
time (tcl)
Ÿ Common settings | free defineable interface modem | Transmission delay if
countinous level (tcldly)
Ÿ Common settings | free defineable interface modem | Send clock synchronization
command to each station selective
Ÿ Common settings | free defineable interface modem | 5V supply (DSR)
[only SM-0551, SM-2551]
Ÿ Common settings | free defineable interface modem | Configuration for CM-082x
[SM-0551, SM-2551 only]
page 114 in a Timing Diagram.

Edition 06.2017, DC0-023-2.12
Parameter "5V Supply (DSR)" [SM-0551, SM-2551 only]
performed with the parameter Common settings | free defineable interface modem
| 5V supply (DSR). The voltage supply is only switched on the DSR state line instead of
the DSR signal with corresponding parameter setting
ATTENTION:
be observed!
Parameter "Configuring for CM082x" [SM-0551, SM-2551 only]
If an optical transformer of the type CM-082x is used as external transmission facility, then the
parameter Common settings | free defineable interface modem |
Configuration for CM-082x must be set when using a patch plug of the type CM-2860.
Parameter
(see acknowledgement procedure in the master station)
The protocol element can – insofar as the transmission facility (e.g. VFT-channel) makes this
signal available receive-side – evaluate the interface signal DCD and utilize it e.g. for
monitoring functions.

DC0-023-2.12, Edition 06.2017
Default parameters for transmission facilities with UMPMxx (not valid for SM-2541)
Transmission facility Electrical RTS tp tv tn tp_bc tdis DCD tbs tstab tdura tdelay A_I T Z 5V CM082x
Interface [ms] [ms] [Bit] [ms] [ms] [ms] [ms] tion [ms]
[sec]
Modem for "4-wire circuit transmission line " RS-232 ON 0 0 3 0 35 YES 5 5 60 200 A I B NO NO
(SAT-VFM,-WT,-WTK,-WTK-S, CE-0700)
Modem for "2-wire circuit transmission line " RS-232 áâ 0 35 3 0 35 YES 5 5 60 200 A I B NO NO
SAT DMS (ring configuration) RS-232 ON 0 0 5 0 0 NO 0 0 0 0 A I s NO NO
SAT-DMS (ring configuration; AU transmitted RS-232 áâ 0 50 5 0 35 YES 5 5 60 200 A I s NO NO
with WT)
RADIO digital RS-232 áâ 30 100 11 0 50 YES 10 5 0 200 A I B NO NO
Radio analog RS-232 áâ 50 300 50 ms 0 100 YES 10 5 0 200 A I B NO NO
Direct connection (RS-485) RS-485 áâ 0 1 0 0 0 NO 0 0 0 0 A I B YES NO
DLC-Modem (CE-0740, CE-0741) RS-232 áâ 0 0 0 0 0 NO 0 0 0 0 A I B NO NO
Modem for "4-wire circuit transmission line" RS-232 ON 0 0 3 0 0 YES 5 5 60 200 A I B NO NO
(CE-0701)
Modem for "2-wire circuit transmission line" RS-232 áâ 22 30 3 0 0 YES 5 5 60 200 A I B NO NO
(CE-0701)
Modem for "2-wire circuit transmission line" RS-232 áâ 0 60 5 0 35 YES 5 5 60 200 A I s NO NO
(CE-0701 via remote modems)
Modem for "2-wire circuit transmission line" RS-232 áâ 0 1 0 0 0 NO 0 0 0 0 A I s NO NO
(CE-0701 via remote modem Westermo TD-32)
Modem for "2-wire circuit transmission line" RS-232 áâ 0 1 0 0 0 NO 0 0 0 0 A I s NO NO
(CE-0701 via remote modem Westermo GD-01)
Direct connection (RS-232) RS-232 ON 0 0 0 0 0 NO 0 0 0 0 A I B NO NO
CM-0821 Ring RS-232 ON 0 0 0 0 0 NO 0 0 0 0 A I B NO NO
CM-0821 Star, CM-0827 RS-232 ON 0 0 0 0 0 NO 0 0 0 0 A I B YES NO
SATTELLINE 2ASxE time slot radio modem RS-232 áâ 0 10 0 0 0 NO 0 0 0 0 A I B NO NO
Freely definable (default settings) RS-232 áâ 30 100 11 0 0 NO 10 5 10 200 A I B NO NO
Freely definable

Edition 06.2017, DC0-023-2.12
Time settings “free definable“ for selected converters/modems with UMPMxx, UMPSxx (SICAM AK3, SICAM A8000/CP-8000/CP-8021/CP-8022)
Interface Modem “free definable” Electrical RTS tp tv tn tp_bc tdis DCD tbs tstab tdura tdelay A_I T Z 5V CM082x
[sec]
2) 3)
Direct-Connection “RS-485/RS-422“ RS-232 áâ 5 5 0 0 0 NO 0 0 0 0 A I B YES NO
(optional with CM-0829)
3)
RS-485/RS-422 Interface with RS-232 áâ 5 5 0 0 0 NO 0 0 0 0 A I B NO NO
Phönix Interface Converter
RS232<-> RS485/RS422
4)
“PSM-ME-RS232/RS485-P“
Optical Interface with RS-232 ON 0 0 0 0 0 NO 0 0 0 0 A I B NO NO
Siemens RS232-FO Converter 7XV5652
Optical Interface/Starcoupler with RS-232 ON 0 0 0 0 0 NO 0 0 0 0 A I B YES NO
Siemens Mini-Starcoupler 7XV5450
(via CM-0847 or via RS-322)
1)
… electrical interface to converter/modem
2)
… recommendation for settings in case of retries or communication errors/-failures with setting “Direct Connection (RS-485)“
3)
… recommendation for settings for baud rates < 9600 Bit/s: tp=50ms.
4)
… Phönix converter with enabled function “automatic transmit/receive changeover”

DC0-023-2.12, Edition 06.2017
Default parameters for transmission facilities with UMPM00 (SM-2541 only)
[sec]
Modem for "4-wire circuit transmission line " RS-232 ON 0 0 3 0 35 YES 5 5 60 200 A I B NO NO
Modem for "2-wire circuit transmission line " RS-232 áâ 0 35 3 0 35 YES 5 5 60 200 A I B NO NO
SAT DMS (ring configuration) RS-232 ON 0 0 5 0 0 NO 0 0 0 0 A I s NO NO
SAT-DMS (ring configuration; AU transmitted RS-232 áâ 0 50 5 0 35 YES 5 5 60 200 A I s NO NO
with WT)
OPTICAL RS-232 áâ 0 1 0 0 0 NO 0 0 0 0 A I B YES NO
RADIO digital RS-232 áâ 30 100 11 0 50 YES 10 5 0 200 A I B NO NO
Radio analog RS-232 áâ 50 300 50 ms 0 100 YES 10 5 0 200 A I B NO NO
Direct connection (RS-485) RS-485 áâ 0 1 0 0 0 NO 0 0 0 0 A I B YES NO
DLC-Modem (CE-0740, CE-0741) RS-232 áâ 0 0 0 0 0 NO 0 0 0 0 A I B NO NO
Modem for "4-wire circuit transmission line" RS-232 ON 0 0 3 0 0 YES 5 5 60 200 A I B NO NO
(CE-0701)
Modem for "2-wire circuit transmission line" RS-232 áâ 22 30 3 0 0 YES 5 5 60 200 A I B NO NO
(CE-0701)
Freely definable (default settings) RS-232 áâ 30 100 11 0 0 NO 10 5 10 200 A I B NO NO
Freely definable

Edition 06.2017, DC0-023-2.12
Default parameters for transmission facilities with UMPSxx (not valid for SM-2541)
[sec]
Modem for "4-wire circuit transmission line " RS-232 áâ 0 30 3 - 0 NO 5 5 60 200 A I - NO NO
(SAT-VFM,-WT,-WTK,-WTK-S,CE-0700)
Modem for "2-wire circuit transmission line " RS-232 áâ 3 30 3 - 35 YES 5 5 60 200 A I - NO NO
SAT DMS (ring configuration) RS-232 ON 0 1 Bit 5 - 0 NO 0 0 0 0 A I - NO NO
SAT-DMS (ring configuration; AU transmitted RS-232 áâ 0 50 5 - 35 YES 5 5 60 200 A I - NO NO
with WT)
RADIO digital RS-232 áâ 30 100 11 - 50 YES 10 5 0 200 A I - NO NO
Radio analog RS-232 áâ 50 300 50 ms - 100 YES 10 5 0 200 A I - NO NO
Direct connection (RS-485) RS-485 áâ 0 1 0 - 0 NO 0 0 0 0 A I - YES NO
DLC-Modem (CE-0740, CE-0741) RS-232 áâ 0 0 0 - 0 NO 0 0 0 0 A I - NO NO
Modem for "4-wire circuit transmission line" RS-232 áâ 0 55 3 - 0 NO 0 0 0 0 A I - NO NO
(CE-0701)
Modem for "2-wire circuit transmission line" RS-232 áâ 22 30 3 - 0 YES 5 5 60 200 A I - NO NO
(CE-0701)
Direct connection (RS-232) RS-232 ON 0 0 0 - 0 NO 0 0 0 0 A I - NO NO
SATTELLINE 2ASxE time slot radio modem RS-232 áâ 0 1 0 - 0 NO 0 0 0 0 A I - NO NO
Freely definable (default settings) RS-232 áâ 30 100 11 - 0 NO 10 5 10 200 A I - NO NO
Freely definable

DC0-023-2.12, Edition 06.2017
Default parameters for transmission facilities with UMPS00 (SM-2541 only)
[sec]
Modem for "4-wire circuit transmission line " RS-232 áâ 0 30 3 - 0 NO 5 5 60 200 A I - NO NO
Modem for "2-wire circuit transmission line " RS-232 áâ 3 30 3 - 35 YES 5 5 60 200 A I - NO NO
SAT DMS (ring configuration) RS-232 ON 0 1 Bit 5 - 0 NO 0 0 0 0 A I - NO NO
SAT-DMS (ring configuration; AU transmitted RS-232 áâ 0 50 5 - 35 YES 5 5 60 200 A I - NO NO
with WT)
OPTICAL or SATTELLINE 2ASxE time-slot RS-232 áâ 0 1 RS-232 - 0 NO 0 0 0 0 A I - YES NO
radio modem
RADIO digital RS-232 áâ 30 100 11 - 50 YES 10 5 0 200 A I - NO NO
Radio analog RS-232 áâ 50 300 50 ms - 100 YES 10 5 0 200 A I - NO NO
Direct connection (RS-485) RS-485 áâ 0 1 0 - 0 NO 0 0 0 0 A I - YES NO
DLC-Modem (CE-0740, CE-0741) RS-232 áâ 0 0 0 - 0 NO 0 0 0 0 A I - NO NO
Modem for "4-wire circuit transmission line" RS-232 áâ 0 55 3 - 0 NO 0 0 0 0 A I - NO NO
(CE-0701)
Modem for "2-wire circuit transmission line" RS-232 áâ 22 30 3 - 0 YES 5 5 60 200 A I - NO NO
(CE-0701)
Direct connection (RS-232) RS-232 ON 0 0 0 - 0 NO 0 0 0 0 A I - NO NO
SATTELLINE 2ASxE time slot radio modem RS-232 áâ 0 1 0 - 0 NO 0 0 0 0 A I - NO NO
Freely definable (default settings) RS-232 ON 30 100 11 - 0 NO 10 5 10 200 A I - NO NO
Freely definable

Edition 06.2017, DC0-023-2.12
Legend:
Electrical interface.........Parameter electrical interface [SM-2541 only]

RTS ...............................áâ = RTS is switched for the control of the carrier switching of the modem with each message (ON / OFF)
tp ....................................Parameter Pause time (tp), Parameter Pause time time base (tp)
tv .................................... Parameter Set-up time (tv), Parameter Set-up time time base (tv)
tn ....................................Parameter overtravel time (tn), Parameter overtravel time time base (tn)
tp_bc ..............................Parameter Pause time after broadcast message (tp_bc), Parameter Pause time after broadcast message_time base (tp_bc) – valid only for MASTER
station!
tdis .................................Parameter Blocking time (tdis), Parameter Blocking time time base (tdis)
DCD ............................... Parameter DCD-assessment
tbs ..................................Parameter Bounce suppression time (tbs)
tstab ............................... Parameter Stability monitoring time (tstab)
tduration ........................ Parameter Continuous level monitoring time (tduration)
tdelay ............................. Parameter transmit delay for level (tdelay)
A_I .................................Parameter Asynchronous_Isochronous
T.....................................Parameter Bit timing (only with isochronous) (I=internal, E=external)
Z.....................................Parameter send clock synchronization command station-selective (s=selective, B=BROADCAST) – valid only for MASTER station!
CM082x ......................... Parameter Configuring for CM082x. Configuring the interface for optical transformer CM-082x with patch plug CM-2860 [SM-0551, SM-2551only]
5V .................................. Parameter 5V Supply (DSR) [SM-0551, SM-2551 only]

DC0-023-2.12, Edition 06.2017
The following picture shows the dynamic behavior (timing) in detail for the data transmission
when using transmission facilities with switched carrier.
Only for
BROADCAST-
messages
RTS
tverz
tp tv Data transmission tn tp_bc tsw tp tv

Master station
TXD
tPrell tPrell
DCD
tverzRTS
Data transmission
RXD
tsignal tsignal
tdis
t´Prell t´Prell
DCD
t´signal
Remote station
Data transmission
RXD
t'dis
RTS

TXD
t'verz
Œ Œ
tPrell tPrell
tstab tstab
tdauer
Legend:


tp_bc ……….….. Break time after BROADCAST-Messages
(some systems require a longer break after the transmission of BROADCAST -messages before the next message
can be sent)

tdis …….….….. Disable time of the receiver after message receiption (to supress faulty signs during level monitoring )

Edition 06.2017, DC0-023-2.12
4.4 Co-ordination of Several Masters
One interface of a SICAM RTUs master station can manage up to 100 remote terminal units.
If more than 100 remote terminal units are to be connected on one line to a SICAM RTUs
master station (e.g. for radio communication with the same radio frequency), then several
interfaces of the SICAM RTUs master station can be connected in parallel (max. 16). These
interfaces are then coordinated, so that always only 1 interface is active at one moment and
the master function only interrogates those remote terminal units that are assigned to this
interface.
Coordination connection *)
DSR DTR ERR DSR DTR ERR DSR DTR ERR
Master station Master station Master station

GND GND GND
(Interface-1) (Interface-2) (Interface-m)
MASTER-1 MASTER-2 MASTER-m
m <= 16
TF
Remote station-1 T Remote station-1 T Remote station-1 T
Remote station-2 T Remote station-2 T Remote station-2 T
Remote station-n T Remote station-n T Remote station-n T
n <= 100 n <= 100 n <= 100

Legend:
T, TF …...…... Transmission facility

DSR ……….… Data Set Ready (V.24/V.28 Status line) – Coordination signal „OUT“ *)
DTR …….…… Data Terminal Ready (V.24/V.28 Status line) – Coordination signal „IN“ *)
ERR ……….… In case of Power OFF or failure of the communication interface the coordination line must be closed „external“ !
*) …………….. The coordination connection requires also a connection of the GND -lines of the V.24/V.28 interfaces of the master stations !
The coordination of multiple interfaces is enabled in the protocol element of the master station
with the parameter advanced parameters | masterkoordination.
The assignment of the remote terminal unit to the associated master (=interface of the master
station) is defined in the remote terminal unit with the parameter advanced parameters |
radio area identifier/master number. The determination of the master number is
carried out in the master station either with the parameter advanced parameters | radio
area identifier/master number or with the parameter advanced parameters |
coordination several masters | master number for coordination.
This assignment must be performed in every remote terminal unit and in every master.
The master number is transmitted in the message on the line in the 2nd octet of the link
address.
The coordination of the interfaces of the master station takes place by means of the interface
signals DTR and DSR. Thereby in each case the DTR-line (=output) of an interface is
connected with the DSR-line (=input) of the next interface of the master station and in this way
a communication link of all interfaces to be coordinated is established. It must be ensured
through external circuitry, that with a failure of one interface, the coordination circuit is closed.
A coordination of multiple masters is only possible with closed coordination circuit.
Data in control-/monitoring direction can be transmitted only if the Master of the own Master
station is "active" by the master coordination.
à The data transmission will be delayed in both directions when using coordinated Masters!

DC0-023-2.12, Edition 06.2017
For the parallel connection of the interfaces, for each interface of the master station a
separate transmission facility must be used or suitable wiring of the interface lines with diodes.
Note:
Since the interface lines DTR and DSR are used for the coordination, the interface cannot be
switched to tristate during inactive coordination!
After a restart, the master with the lowest master number first sends an "Initialization Token"
on the coordination circuit to the next master after a delay time (t_start_delay). The delay time
is calculated automatically by the protocol element according to the set parameters (baud
rate, master number,...). All masters which presently do not carry out any station interrogation,
relay this "Initialization Token" to the next master. If a master receives the "Initialization
Token" it has transmitted itself, it starts with the station interrogation of its remote terminal
units. If a master is presently performing the station interrogation of its remote terminal units at
this time, this master does not pass on the "Initialization Token" to the next master. When this
master has concluded its station interrogations, it steps to the next master with a Stepping
Token.
The transmit time can be set for every master with the parameter advanced parameters |
coordination several masters | max. number of polling messages befor
activating next master. On expiry of this time, a "Stepping Token" is transmitted on the
coordination circuit and thus stepped to the next master.
The function "demand" (=parameter-settable station-selective continued polling of a slave
after transmission of a command) will be stopped during stepping over to next coordinated
master and continued afterwards.
In addition each master monitors whether it receives a token on the coordination circuit within
a time that can be set with the parameter advanced parameters | coordination
several masters | monitoring time for cordination of several master. On
expiry of this monitoring time, all remote terminal units of a master are flagged as failed. To
resume the coordination, the master sends an "Initialization Token" to the next master.
On the coordination circuit, "Initialization Token" (100ms pulse) and "Stepping Token" (30ms
pulse) are transmitted with different pulse lengths.
Timing for the coordination of multiple master stations:
Œ
t_start-delay
t_token-tio
i w w w
Master station-1
DTR
100ms 30ms
i` w` w`
DSR
Data
i w w
Master station-2
DTR
i` w` w` w`
DSR
Data
i w w
Master station-n
DTR
i` w` w`
DSR
Data
Legend:
DTR ……...….. Data Terminal Ready - „Coordination signal (OUT)“

DSR …….……. Data Set Ready - „Coordination signal (IN)“
Data ……...….. Transmission time (Data transmission) of the master station with the own remote stations
i …….…..…….. Initialization Token (OUT) - 100ms

i` …...…..…….. Initialization Token (IN)
w …...…..…..... Stepping Token (OUT) - 30ms
w` …..….…...... Stepping Token (IN)
t_token-tio …... Token timeout monitorint time
t_start-delay … Delay after RESET – transmission of an initialization token
after the end of the delay time
Œ …………….. RESET

Edition 06.2017, DC0-023-2.12
4.5 Standby Transmission Line over the Public Telephone

Network (PSTN)
The data transmission between master station and the remote terminal units during fault-free
operation takes place over the main transmission line. Failed remote terminal units can be
interrogated on the standby transmission line over the public telephone network (PSTN).
For this, a connection is established from the interface for standby transmission line over the
public telephone network (PSTN), which establishes a transparent communications link to a
transmission facility (TF), for multi-point traffic preferably at the other end of the transmission
line. The connection setup is thereby initiated with the state line DTR – the telephone number
is fixed programmed in the modem.
Presently, for the standby transmission line operation over the public telephone network
(PSTN) at master station end only the dial-up modem WESTERMO TD32 is supported and at
remote terminal units end, the modems WESTERMO TD32 (=analog) or WESTERMO GD01
(=GSM). At the remote terminal unit end, in addition a protocol converter WESTERMO MD54
is required.
Note: The protocol converter WESTERMO MD54 is required for the conversion of different
used baud rates and for "removing" of gaps in messages received via GSM (gaps caused by
transmission in telephone network).
Schematic configuration for standby transmission line operation over telephone network:
Master station
ACP-1703 Basic system element (BSE)
Œ Function diagram Œ
•
•
UMPMA0 UMPMA0
“Main transmission line“ “Standby transmission line“
(SSE = 128 or 130) (SSE = 129 or 131)
Ž DTR CTS
MODEM
TF
Public telephone
network “PSTN“ MODEM
Protocol
• converter
TF
TF TF TF TF
Remote station-1 Remote station-2 Remote station-3 Remote station-n
Main transmission line Standby transmission line

Legend:

Œ …………….. Failed remote stations are signaled to the basic system element as failed.
• …………….. Failed remote stations must be signaled to the standby protocol element with the protocol element control
message "standby transmission line ACTIVE“
Ž …………….. The standby transmission line via dial-up traffic is established with status line DTR
(modem configuration must be done „offline“; telephone number is stored in the modem).
The build-up connection will be signaled with CTS status line.
• …………….. The coordination of main-/standby transmission lines takes place with internal protocol control messages
• …………….. The transmission path for standby must guarantee a transparent connection
(no gaps in messages, baud rate and byte frame to TF on standby transmission line must be identical with the
baud rate and byte frame used on the main transmission line)
…………….. Example for conductor interruption and hence split in remote stations accessible on main and standby
transmission line.

DC0-023-2.12, Edition 06.2017
The standby transmission line operation over public telephone network (PSTN) is activated on
the protocol element of the interface for standby transmission line with the parameter
advanced parameters | master for stand-by transmission line (PSTN).
The assignment of the interface for main transmission line and standby transmission line is
defined as follows:
Main Line Standby Line Note

SSE = 128 SSE = 129 The SSEs for main-/standby transmission line must be on the same
BSE.
SSE = 130 SSE = 131
Legend:
SSE ........ supplementary system element (with serial interfaces this is always configured with a PRE)
The remote terminal units are interrogated by the master station predominantly on the main
transmission line. If the protocol element of the master station detects a remote terminal unit
on the interface of the main transmission line as failed, then this is reported to the basic
system element (BSE) as failed.
The station failure is to be transferred as protocol control message to the interface for standby
transmission line by using the function diagram on the basic system element (BSE). The
testing of the standby transmission line is also to be realized with the function diagram.
With the parameter advanced parameters | Master for stand-by transmission

line via PSTN | delay time for activation of stand-by transmission line
the protocol element for standby transmission line performs a station-selective delayed
selection of the standby transmission line. If a remote terminal unit reported as failed on the
main transmission line is reported as OK again during the delay time, no standby transmission
line is established for this remote terminal unit.
After expiry of the delay time the standby transmission line is set-up. If the connection setup is
not successful, after a pause that can be set with the parameter advanced parameters |
Master for stand-by transmission line via PSTN | Pause between not
successful dial-up sequence a new connection setup is initiated. If the connection
cannot be established over the public telephone network (PSTN) after max. 4 dialing attempts,
the corresponding remote terminal units are also reported as failed by the interface for
standby transmission line.
The established standby transmission line is reported to the protocol element for main
transmission line by an internal protocol control message. From this moment, the protocol
elements of the interfaces for main and standby transmission line coordinate themselves with
internal protocol control messages in such a way, that the remote terminal units of the multi-
point traffic line are always only interrogated by one interface (main or standby transmission
line) at one time.
After a completed message transmission including receipt of the acknowledgement, the

control is transferred to the other interface with the internal protocol control message ("send
next message"). Station interrogations on the standby transmission line are always started
after a delay time. This delay time prevents of processing of possibly delayed messages
received from the remote terminal unit on the standby transmission line caused by station
interrogation on the main line.
Failed remote terminal units also continue to be interrogated on the main transmission line
(but from now on every 10th time). If a failed remote terminal unit can be reached again on the
main transmission line, the standby transmission line handling is terminated for this RTU. If all
remote terminal units can be reached again on the main transmission line, the connection for
standby transmission line is terminated after a delay time of 1 minute.

Edition 06.2017, DC0-023-2.12
The parameter setting of main-/standby transmission line is carried out in the topology. From
this parameter setting the routing of the internal protocol control messages necessary for the
coordination is also derived.
Functions of the protocol converter for standby transmission line:
· Adaptation of the baud rate

The baud rate from/to transmission facility (ÜE) on the standby transmission line must be
identical with the baud rate from/to transmission facility (ÜE) on the main transmission line.
· Adaptation of the byte frame
The byte frame from/to transmission facility (ÜE) on the standby transmission line must be
identical with the byte frame from/to transmission facility (ÜE) on the main transmission
line.
· Removal of message gaps
Messages to the transmission facility (ÜE) on the standby transmission line must not
contain any gaps (pauses).
Notes:
· The "Standby Transmission Line over the Public Telephone Network (PSTN)" will be
supported in the master station only for following transmission facilities: *)
- Modem for "2-wire circuit transmission line"
(CE-0701 via remote modem Westermo TD-32)
- Modem for "2-wire circuit transmission line"
(CE-0701 via remote modem Westermo GD-01)
*) Data transmission with "no Parity"!
· On the protocol element for standby transmission line, in addition a greater time for the
message interruption monitoring is to be set with the parameter advanced parameters
| monitoring times | Character monitoring time
and the parameter advanced parameters | monitoring times | Character
monitoring time "time base".

DC0-023-2.12, Edition 06.2017
4.6 Data Transmission using Time Slot Radio
With time slot radio the radio transmission may only be utilized during a particular time
(typically max. 6 seconds per minute). The remaining time is utilized for the radio transmission
of other systems – this transmission method is called "Time Slot Technique".
For the utilization of the time slot technique in Germany, for this 5 frequencies are approved
nationwide for the exclusive professional data radio transmission using the time slot method.
In this method, in each case 10 users can utilize a common frequency for 6 seconds each
within 1 minute. The synchronization of the time slot takes place by means of a DCF-77 signal
(atomic clock), so that overlaps are excluded.
This new method can be used everywhere, where there are no time-critical data or where data
is collected over a certain period before the transmission, in order to then send these in a
packet. Since no station needs to be mobile, fixed installed local radio data networks can be
established. The applications can be seen in the areas of measurement data transmission
between fixed stations, power utilities, water, waste water, meteorology, control data to fixed
stations, packet-orientated control tasks, alarm transmissions and many more.
As a result the user has other benefits:

· high ranges
· free point-to-point data transmission
· free point-to-multipoint data transmission
· free data transmission in master-slave operation
· free data transmission for multi master networks
· low interferences from neighboring disturbance emitters
Through the use of suitable additional devices (Time Slot Unit) in the master station and the
implementation of suitable procedures, it is ensured, that no time slot violation occurs during
the data transmission. The SATELLINE-TSU (Time Slot Unit) is a unit with integrated DCF-77
receiver – this unit switches through the transmission lines between the transmitting station
and the connected time slot radio modem for the set time slot.
The TSU is normally used in each station that cannot manage the time slot in a highly precise
manner. For MASTER / SLAVE configurations the TSU is mostly only used in the MASTER –
through suitable measures in the communications protocol implemented, a time slot violation
by the SLAVE must be prevented (especially through a message still sent by the SLAVE at
the end of the time slot).
For this the state line input CTS in the MASTER is wired with the signal CTS of the TSU
(Clear to Send). This signal is "ACTIVE" for the respective station during the assigned time
slot. The master only sends data during the assigned time slot, but only until the reply from the
remote terminal unit is transmitted completely, in all cases within the time slot. The CTS-signal
from the TSU is also monitored for plausibility. If the CTS-signal from the TSU switches to
inactive during a running message transmission before expiry of the parameterized "Length of
the time slot", the interface of the master station is switched immediately to TRISTATE – in
addition the CTS-signal of the TSU is monitored for failure.
The data transmission using the time slot method is selected by selecting the transmission
facility "SATTELLINE 2ASxE time slot radio modem " with the parameter Common settings
| interface modem. When using this transmission facility, in addition, in the MASTER the
parameter Common settings | Time slot radio modem (SATTELLINE 2ASxE) |
failure monitoring and the parameter Common settings | Time slot radio modem
(SATTELLINE 2ASxE) | length of time slot und der Parameter Common settings
| Time slot radio modem (SATTELLINE 2ASxE) | start second of time slot
must be parameterized. These parameters are used for the optimization of the data
transmission with time slot radio technique.

Edition 06.2017, DC0-023-2.12
4.7 Data Transmission in Relay Operation "Multi-Point

Traffic with Routing"
In relay operation, messages transmitted from the master station can also reach the remote
terminal unit indirectly (and vice versa), namely by way of intermediate stations along the
transmission path, that can always communicate directly with their respective adjacent station.
Such stations lying along the path between source and destination of a message transmission
"only" provide a routing function for the transmission in question (namely reception and
forwarding of messages). In this sense, such stations are routing stations. Remote terminal
units themselves can also be used as routing stations for other remote terminal units.
All stations participating in the multi-point traffic are equipped with protocol elements for relay
operation and through this possess the capability of routing – in general besides their process-
related tasks and independent from these. The routing paths are defined through
parameterization in the master station. The routing for a routing path can take place via up to
7 routing stations. For each station a primary path and a secondary path can be defined.
With wired communication, the relay operation can be used for regenerating the signal: if for
example a very remote station can only be reached with great difficulty, error-free
communication is often only possible with a very high number of retries. By routing the
messages over a routing station, the attainability can be improved considerably.
With radio communication, it can happen, that due to the geographical location or the limited
transmitting power and an insufficient number of transmission frequencies, not all stations can
be reached with just one transmitter installed in the master station. With the communication
procedure of the relay operation, despite the use of the most simple of radio devices (even
with low transmitting power), the required communication tasks are resolved with just one
single radio frequency in the entire automation range.
The function "Relay Operation" is a SICAM RTUs-specific expansion of the IEC 60870-5-101
protocol in multi-point traffic.
The function Relay Operation is activated by enabling the parameter advanced parameters
| Repeater function (Routing). By enabling this parameter, the parameters required for
relay operation such as "Routing method", "Retries until path change" and "Routing paths" are
first displayed.
If the relay function is not enabled, the protocol functions according to IEC 60870-5-101.
With function enabled, the protocol no longer corresponds with the IEC 60870-5-101 standard,
since an extra block is used in the message for the routing information for the relay function.
The user data formats themselves continue to be used according to IEC 60870-5-101.
LINK Routing-Information IEC 60860-5-101 ASDU LINK
IEC 60870-5-1 Expansion for relay IEC 60870-5-1

IEC 60870-5-2 operation
Control field Routing Routing

(Length, Index) Station-Nr. „1" Station-Nr. „n“
Index Index

DC0-023-2.12, Edition 06.2017
Parameters for relay operation:
· Enabling of the relay function with the parameter advanced parameters | Repeater
function (Routing)
· Switchover main-/standby transmission line with the parameter advanced parameters
| Repeater function (Routing) | retries until switchover to stand-by
line
· Routing method (optimized/not optimized) with the parameter advanced parameters |
Repeater function (Routing) | routing procedure
· "Radio circuit identifier/master number" with the parameter advanced parameters |
radio area identifier/master number
· "Routing paths" (path-type, destination station number, routing station number) with the
parameters advanced parameters | Repeater function (Routing) | routing-
paths | path type, Destination station number, routing station nr.
Multi-point traffic with relay operation over radio

In utilities, many small and medium size stations fail to become automated because of
communication problems. Where dedicated lines or, because of poor infrastructure, dial-up
traffic cannot be used, one often has to fall back on radio communication. Thereby it can
happen, that due to the geographical location or the limited transmitting power and an
insufficient number of transmission frequencies, not all stations can be reached with just one
transmitter installed in the master station.
Relay operation solves this problem despite using only the most simple radio communication
units (even of low transmitting power) with only one single frequency in the entire automation
range.
Functioning principle of the radio relay operation

In particular in mountainous regions, where even the highest elevation is in most cases
insufficient for a radio transmitter, in order to reach every individual valley the radio relay
operation provides the solution to the problem. Up to 7 routing stations can be used for the
data transfer (with regard to routing and fulfilling process-related tasks - e.g. telecontrol
functionality - see above). A chronological coordination of all transmitter up-switching
operations in the entire network thereby takes place.
‚
’
‘ Ž •
U3
Œ U1 •
“ U2
•
Z
U4
Legend:
Z ….…...….….. Master station
U1,U2, U3 .….. Remote stations (used as routing stations in this example )
U4 ….....….….. Adressed remote station
Œ,•,Ž,•…..... Messages in direction: master station à remote station
•,‘,’,“…..... Messages in direction: remote station à master station
‚ …………….. In case of adequate transmission power U3 can also be reached directly from U 1 (=shorter path)

Edition 06.2017, DC0-023-2.12
A message is transported via radio by means of multi-point traffic (half duplex) over a
predefined path from the source (master station or RTU depending on the direction) to the
destination (RTU or master station depending on the direction). The path leads
· either from the source directly to the destination, or – if that is not possible -
· Indirectly from the source – via one or more routing stations, which only forward messages
– to the destination.
From the example in the picture above it can be seen, that individual stations cannot reach
others directly via radio because of the mountains situated in between. Stations which are
capable of communicating with one another directly via radio communication are located
within one "radio region": the example shown includes the following radio regions: (Z, U1),
(U1, U2, U3) and (U3, U4).
For the transmission of a message from the master station Z to the remote terminal units U1,
U2, U3, and U4, the following routes are possible (reverse direction along the same route):
Source Destination Route Note

Z U1 Z ð U1
Z U2 Z ð U1 ð U2
Z U3 Z ð U1 ð U3 shorter route ð advantageous
Z U3 Z ð U1 ð U2 ð U3 longer route ð disadvantageous
Z U4 Z ð U1 ð U3 ð U4
Legend:
Z, U source, destination
u routing station
In the following picture, radio regions are represented by closed curves.
Main transmission line
Standby
transmission
U1 line U3
U2
Z
Radio regions U4
Legend:
Z ….…...……........ Master station
U1,U2, U3, U4 …. Remote stations (U1,U2,U3 serve in this example also as routing stations )
Radio regions …... All stations in the same radio region can communicate with each other
…….... Main transmission line (ZðU1ðU3ðU4, U4ðU3ðU1ðZ)
………. Standby transmission line (ZðU1ðU2ðU3ðU4, U4ðU3ðU2ðU1ðZ)
The shortest route along which an outstation can be reached is determined by parameter
setting. This route is also contained in the message transmitted. All stations within reach of
the respective transmitter will receive the message. However, it will be retransmitted only by
the routing station that is next in the routing order and thus be passed on in the relay
operation - until it arrives at its destination.

DC0-023-2.12, Edition 06.2017
The function of the routing stations can be taken over by remote terminal units with process-
related tasks. If remote terminal units cannot be reached directly or without gaps over other
remote terminal units due to the local circumstances, additional stations must be used for
routing (data relay stations).
All remote terminal units – even those which only have routing tasks – are interrogated by the
master station in a configurable interrogation cycle. Stations with important data can be called
several times in one interrogation cycle. The transmission of the data from the remote terminal
units to the master station take place by means of a relay-wise forwarded, selective station
interrogation (Polling). The remote terminal unit stores changed data and transmits these back
to the master station in the same manner with a station interrogation of this station.
To increase the availability, besides the main transmission line a redundant route (standby
transmission line) can be defined.
Transmit time limitation of the radio equipment
So that remote terminal units or radio equipment that are functionally impaired do not lead to a
blocking of the link, it is advisable to equip the radio equipment used with a transmit time limit
(e.g. external equipment connected between remote terminal unit and radio equipment, which
monitors the RTS signal). This unit should switch the radio equipment off after a settable
maximum time. After this protection device has responded in a disturbance event, the
interrogation cycle to the remaining stations can continue to be carried out by the master
station.
Speech
The utilization of the radio equipment for telephony cannot be enabled with intermediate
routing stations and because of the use of only one radio frequency (speech must be buffered
in the routing stations).
In this case a separate radio channel is to be used for the transmission of speech (e.g. mobile
radio).
For remote terminal units that can be reached directly from the master station, the radio
equipment of the master station and the remote terminal unit can however be used for speech
transmission. So that an interface fault signaling in the master station does not occur with
speech transmission (data transmission not possible due to activated speech connection), on
switchover of the radio equipment the master station is provided with a binary information,
through which the interrogation cycle is stopped. On termination of the speech transmission
the interrogation cycle is resumed.
Time tagging, clock synchronization

The routing often over several routing stations causes longer total transmission times. Here it
is particularly advisable to perform the time tagging for process information directly at the point
of origin. The management of a real-time clock necessary in each of the remote terminal units
for time tagging must often manage without decentral time signal receiver for reasons of cost
and poor reception locations in many cases.
The clock synchronization of the remote terminal units can also be carried out over the serial
communication line. The clock synchronization is typically carried out once per minute by the
master station. The typical accuracy that can be achieved through this is ± 20 ms and with
relay operation an additional 10 ms per routing station (see also section Clock
Synchronization).

Edition 06.2017, DC0-023-2.12
Radio circuit identifier
When using the same radio frequencies in different, local and geographically separated
regions, due to over-ranges in the radio communication, a remote terminal unit could receive
station interrogations or even commands from a third-party master station.
If, for example, several multi-point traffic areas – each with a master station - are formed in
one automation network, then a mutual influencing (over-ranges) and an undesirable system
behavior caused as a result can be prevented, by
· assigning a different radio frequency to every multi-point traffic area or/and

· performing a station number assignment unambiguous over all areas or/and
· an unambiguous assignment (in the framework of the configuration options) of all stations
to their respective own master station with the help of the radio circuit identifier.
The radio circuit identifier must be configured in the master station and in every remote
terminal unit.
The assignment of the remote terminal units to the associated master (=interface of the
master station) is defined with the parameter advanced parameters | radio area
identifier/master number. The master number is transmitted in the message on the line
in the 2nd octet of the link address.
All messages from the master station are sent with the configured radio circuit identifier.
Messages are only then evaluated by the routing stations, if the radio circuit identifier
contained in the message corresponds with that configured. As a result, messages that are
received from third-party master stations / remote terminal units (due to over-ranges in the
radio communication) are ignored.

DC0-023-2.12, Edition 06.2017
4.7.1 Main and Standby Transmission Line
For every remote terminal unit that cannot be reached directly, but only via routing stations,
the main transmission line must be configured in the master station (Routing Information:
series of RTU-addresses, over which a remote terminal unit can be reached from the master
station over the shortest route). In addition, for every remote terminal unit a standby
transmission line can be configured (Routing Information: series of RTU-addresses, over
which a remote terminal unit can also be reached from the master station).
The parameters for "Routing" are only displayed by enabling the parameter advanced
parameters | Repeater function (Routing). For every routing-path (main or standby
transmission line) to a remote terminal unit (destination station number) a new row must be
parameterized in the spreadsheet with the parameters for "Destination station No.", "Path
type" and "Routing station No.1...7". Every remote terminal unit in multi-point traffic (directly
reachable remote terminal unit and routing station) is to be recorded in the parameter
station definition. Thereby a new row is appended in the spreadsheet for every remote
terminal unit and the corresponding station-specific parameter entered.
With fault-free station interrogation, all remote terminal units are interrogated directly,
respectively over the configured main transmission line.
If remote terminal units cannot be reached from the master station over the main transmission
line (failure/fault of transmit/receive systems, of routing stations, the RTU itself, etc.),
communication is attempted over the configured standby transmission line. With the
parameter advanced parameters | Repeater function (Routing) | retries until
switchover to stand-by line the moment for the switchover from main to standby
transmission line can be defined. If this attempt to obtain an acknowledgement also fails
(expiry of number of retries ) or if no standby transmission line has been configured, the
remote terminal unit is flagged as faulty.
Configured standby transmission lines are checked in the background at configurable

intervals. If stations are only reachable over the standby transmission line, the main
transmission line is monitored in the background.
With fault-free communication, a standby transmission line configured for a station is checked
after every 20 station interrogations (default). With faulty main transmission line, with
configured standby transmission line this is checked after every 10 station interrogations.
With faulty main or standby transmission line, a warning is generated by the master station in
the form of "station-selective binary information".
Quality assessment of main and standby transmission line

A quality assessment is carried out for the main and standby transmission line. The quality of
a route is derived from the message retries required. If the quality of a route is no longer
provided, a warning is also derived from the master station.
For the quality assessment, the last 16 messages per route are assessed. If from the last 16
messages, more than a configurable number have not been acknowledged, a warning is
output.

Edition 06.2017, DC0-023-2.12
4.7.2 Routing Method
Received messages are re-transmitted immediately after complete reception by "data relay
stations", if these are determined for further transmission based on the "Routing Information"
(in the message) and with own radio circuit identifier.
Messages received by stations that are not defined as "End station" (= addressed remote
terminal unit) or "data relay station" (station is not or not yet provided in the routing information
of the message), are not processed further.
The received routing information is entered in the reverse order by the addressed "End
station" for the reply message to be transmitted. Consequently, the reply message is
transmitted through the network over the route specified by the master station.
In relay operation, stations can be reached through the "Routing method" implemented over a
maximum of 7 "data relay stations" (routing stations).
For stations that can be reached directly from the master station, the configuration of routing
information is not necessary.
The structure of the routing information used in the message is defined with the parameter
advanced parameters | Repeater function (Routing) | routing procedure .
D7 D6 D5 D4 D3 D2 D1 D0
0 0 Index Length
Routing station - 1 Index = 0
Length Routing station - 4 Index = 3
Legend:
Length ...….…..Number of registered routing stations (1..7)

- The length of the routing field is dynamically administrated in case of an „optimized routing method“.
That means that only those routing stations are registered in the routing fields which are actually required .
- „Non-optimized routing methods“ transmit the routing field always in „maximal length“ (8 Bytes)
In the routing field „Length“ only the actual number of used fields for routing stations must be entered .
Unused routing fields are initialized with „FF“.
Index ………… Information about the processed routing fields (0..6).

DC0-023-2.12, Edition 06.2017
4.7.2.1 Non-optimized Routing Method
With the "non-optimized routing method" the routing information in messages is managed
"statically".
In messages formats with fixed block length the routing information is always available with
maximum length. In messages formats with variable block length the routing information is
always available with variable length (same as used for "optimized routing method").
The routing information is always available with maximum length in messages with
fixed/variable block length.
Station interrogations / acknowledgements are generally transmitted with the "message format
with fixed block length", user data is transmitted with the "message format variable block
length".
Single characters are not used!
Example: Management of the routing information with 3 routing stations for "non-optimized
routing method" (e.g. for REQUEST STATUS OF LINK).
Œ • Ž •
“ ’ ‘ •
Z U1 U2 U3 U4
LINK LINK LINK LINK

Œ Target station-Nr. = U4 • Target station-Nr. = U4 Ž Target station-Nr. = U4 • Target station-Nr. = U4
0 0 0 3 0 0 1 3 0 0 2 3 0 0 3 3
U1 0 U1 0 U1 0 U1 0
3 U2 1 U2 1 U2 1 U2 1
U3 2 U3 2 U3 2 U3 2
FF 3 FF 3 FF 3 FF 3
FF 4 FF 4 FF 4 FF 4
FF 5 FF 5 FF 5 FF 5
FF 6 FF 6 FF 6 FF 6
Ax-1703 Ax-1703 Ax-1703 Ax-1703
User data User data User data User data
LINK LINK LINK LINK
“ ’ ‘ •
LINK LINK LINK LINK
Target station-Nr. = U4 Target station-Nr. = U4 Target station-Nr. = U4 Target station-Nr. = U4
0 0 3 3 0 0 2 3 0 0 1 3 0 0 0 3
U3 0 U3 0 U3 0 U3 0
U2 1 U2 1 U2 1 U2 1
U1 2 U1 2 U1 2 U1 2
FF 3 FF 3 FF 3 FF 3
FF 4 FF 4 FF 4 FF 4
FF 5 FF 5 FF 5 FF 5
FF 6 FF 6 FF 6 FF 6
Ax-1703 Ax-1703 Ax-1703 Ax-1703
LINK LINK LINK LINK
Legende:
Z ….…...…... Master station

U1,U2, U3 ... Remote stations (serve as routing stations in this example)
U4 ….....…... Adressed remote station
Œ,•,Ž,•….. Message direction: Master station à Remote station
•,‘,’,“….. Message direction: Remote station à Master station

Edition 06.2017, DC0-023-2.12
4.7.2.2 Optimized Routing Method
With the "optimized routing method for relay operation" the routing information in messages is
managed "dynamically".
Station interrogations to remote terminal units that can be reached directly from the master
station, contain no routing information (= message format with fixed block length). Such
remote terminal units, if there are no data to be transmitted, reply with a single character or a
short acknowledgement (no routing information in the message). Data is transmitted with the
"message format with variable block length" and a "0-Routing Information".
Station interrogations to remote terminal units that cannot be reached directly from the master
station, contain only the routing information necessary (message format with variable block
length). Such remote terminal units, if there are no data to be transmitted, reply with an
acknowledgement message and the necessary routing information (message format with
variable block length). Data is generally transmitted with the "message format with variable
block length" and the necessary routing information.
Example: Management of the routing information with 3 routing stations for "optimized routing
method"
Œ • Ž •
“ ’ ‘ •
Z U1 U2 U3 U4
LINK LINK LINK LINK

Œ Target station Nr. = U4 • Target station Nr. = U4 Ž Target station Nr. = U4 • Target station Nr. = U4
0 0 0 3 0 0 1 3 0 0 2 3 0 0 3 3
U1 0 U1 0 U1 0 U1 0
3 U2 1 U2 1 U2 1 U2 1
U3 2 U3 2 U3 2 U3 2
Ax-1703 Ax-1703 Ax-1703 Ax-1703
LINK LINK LINK LINK
LINK LINK LINK LINK

“ Target station Nr. = U4 ’ Target station Nr. = U4 ‘ Target station Nr. = U4 • Target station Nr. = U4
0 0 3 3 0 0 2 3 0 0 1 3 0 0 0 3
U3 0 U3 0 U3 0 U3 0
U2 1 U2 1 U2 1 U2 1
U1 2 U1 2 U1 2 U1 2
Ax-1703 Ax-1703 Ax-1703 Ax-1703
LINK LINK LINK LINK
Legend:
Z ….…...…... Master station

U1,U2, U3 ... Remote stations (serve as routing stations in this example)
U4 ….....…... Adressed remote station
Œ,•,Ž,•….. Message direction: Master station à Remote station
•,‘,’,“….. Message direction: Remote station à Master station

DC0-023-2.12, Edition 06.2017

Routes
designed redundant.
In this section, the possible redundancy concepts themselves that can be realized are not
described, rather only those functions for the support of redundant communication routes
supported by the protocol element.
In the master station and the remote terminal unit, with the parameter advanced
parameters | project specific | Redundancy control one can select between the
following redundancy controls:
· 1703-Redundancy
· Norwegian User Conventions (NUC)
control messages.
In the master station, in addition a delay for the switchover of the redundancy state from
PASSIVE (=STANDBY) to ACTIVE can be set with the parameter Redundancy | Delay
time passive=>active.
passive as follows:
· Interface "tristate" – only listening mode

· Interface "active" – only listening mode
· Interface "active" – interrogation mode
From the redundant, not active master / remote terminal unit, listened messages are passed
on to the basic system element (BSE) and forwarded by this in the system with the identifier
"passive" in the state.
In redundant master stations that are not active, a failure of the interface is monitored globally
and the failure of remote terminal units monitored station-selective.
The failure of the interface is detected by the STANDBY master station by monitoring for
cyclic message reception. The monitoring time is set with the parameter Redundancy |
listening_mode (failure monitoring time). On receive timeout (active master station
or transmission facility of the master station has failed) the interface is signaled as failed.
The failure of a remote terminal unit is detected by the STANDBY master station through
station-selective monitoring for cyclic message reception. On station-selective receive timeout
(remote terminal unit or transmission facility of the remote terminal unit has failed) the remote
terminal unit is signaled as failed.
Station-specific pending faults are reset in a redundant STANDBY master station, if a fault-
free message from the respective station is "listened".

Edition 06.2017, DC0-023-2.12
Activation / Deactivation of the interface in redundancy mode "passive"
For the implementation of project specific redundancy modes the interface and the operation
of the protocol can be activated/deactivated with protocol element control message when
redundancy mode is in "passive" and with parameter "operation if passive" is set to
"transmitter tristate".
The activation/deactivation of the interface can be used for supervision of redundant
communication links to the remote station.
Behavior when interface is "activated":

from transmitter "tristate", listening mode
to transmitter "active", normal operation
· all data ready for transmit sent from basis system element to protocol element will be sent
to the remote station.
Behavior when interface is "deactivated":

from transmitter "active", normal operation
to transmitter "tristate", listening mode
· all data sent from basis system element to protocol element will be discarded by the
protocol element.
PRE control message for controlling the protocol mode will be accepted only in redundancy
mode "passive".
The actual state of the interface and the protocol mode (activated/deactivated) will be sent
from protocol element to basis system element spontaneous after change of event and during
general interrogation.
No general interrogation command will be initiated by the protocol element firmware after
activation of the interface.
Note:
The operating mode of the interface will be updated always by the AU internal protocol
element control message (redundancy control message has higher priority than PRE control
message).

DC0-023-2.12, Edition 06.2017
4.8.2 Redundancy Mode "Norwegian User Conventions (NUC)"
The redundancy mode "Norwegian User Conventions (NUC)" uses 2 communications lines
(main/stand-by transmission line) from the master station (Controlling Station) to the remote
terminal unit (Controlled Station). Each of these communications lines is fixed activated to a
specific interface in the master station and in the remote terminal unit. The data is only
transmitted to the active interface. The passive interface is only monitored by the master.
The redundancy mode "Norwegian User Conventions (NUC)" is supported in the master
station and in the remote terminal unit and selected with the parameter advanced
parameters | project specific | Redundancy control.
The switchover of the redundancy state in the master station takes place system-internal
through redundancy control messages.
The operating mode of the interface with redundancy state "PASSIVE" is not to be
parameterized for this redundancy mode. The function is defined by the "Norwegian User
Conventions (NUC)".
Redundancy function according to "Norwegian User Conventions (NUC)" for "unbalanced-

Mode":
· After startup of the Controlling Station, this starts the communication on both interfaces
with the message "Request Status of Link". The Controlling Station decides which of the
interfaces is to be switched to "ACTIVE" for the data transmission as main transmission
line (Primary-Line). The other interface is used as standby transmission line and remains
at "PASSIVE".
· After startup of the remote terminal unit (Controlled Station), this waits for the initialization
of the interfaces by the master station (Controlling Station) for the redundancy mode. After
startup both interfaces are "PASSIVE". The remote terminal unit activates that interface on
which the message "Reset of Remote Link" is received from the master station (Controlling
Station) as main transmission line (Primary Line).
· For monitoring the standby transmission line (Backup Line) the master station sends the
message "Request Status of Link" cyclic.
· With a communication failure on the main transmission line or with unintentional
switchover to the standby transmission line, the Controlling Station sends a message
"Reset of Remote Link" on the previous standby transmission line. With that the previous
standby transmission line is now used as main transmission line (Primary Line). From now
on, the Controlled Station is interrogated by the Controlling Station on the previous main
transmission line with "Request Status of Link" and as a result monitored for failure (with
"Request Status of Link" switchover to the standby transmission line takes place).
· During the switchover from main transmission line-stand-by transmission line, no data loss
must occur in the Controlled Station. Transmitted data may only be deleted in the remote
terminal unit if these have been explicitly acknowledged by the master station. With
switchover, no general interrogation is necessary.
The SICAM RTUs master station performs the following functions with redundancy state
"PASSIVE":
· only "Request Status of Link" is sent – with that the failure of the remote terminal units is
detected
· All data in command directions are discarded and not transmitted
· The interface is always electrically "ACTIVE" (and is not switched to "TRISTATE").

Edition 06.2017, DC0-023-2.12
The master station monitors the standby transmission line by means of cyclic "Request Status
of Link" messages.
If a remote terminal unit no longer replies, on expiry of the number of retries this is reported as
failed. As a result, a failure of the interface is monitored globally and the failure of remote
terminal units is monitored station-selective.
In the SICAM RTUs remote terminal unit, for the redundancy mode "Norwegian User
Conventions (NUC)" the LOAD-SHARE-Mode of the communications function must be used
on the basic system element. With this mode the basic system element uses 2 fixed assigned
interfaces for the transmission of the data from a process image. With the redundancy mode
"Norwegian User Conventions (NUC)", data is only interrogated by the master station over
the active interface. Through the LOAD-SHARE-Mode a switchover without loss of data is
ensured – a doubling of data can occur under certain circumstances.
In the remote terminal unit (Ax 1703) the assignment of the interfaces for main transmission
line and stand-by transmission line is defined on a basic system element as follows:
Interface 1 Interface 2 Note

Main/Standby Main/Standby
transmission line transmission line
Legend:
SSE ........ Supplementary system element (with serial interfaces, this is always configured with a PRE)
The SICAM RTUs remote terminal unit performs the following functions with redundancy state
"PASSIVE":
· No data for emission are requested by the basic system element

· All data in signaling direction are transmitted over the active interface to the master station
· The interface is always electrically "ACTIVE" (and is not switched to "TRISTATE")
After a restart of the remote terminal unit, for the redundancy mode "Norwegian User
Conventions (NUC)" by default both interfaces are switched to "PASSIVE".
The master station decides which interface of the remote terminal unit is to be operated as
"ACTIVE".
The switchover to "ACTIVE" takes place with the message "Reset of Remote Link".
The switchover to "PASSIVE " takes place with the message "Request Status of Link".
Notes:
· In the remote terminal unit the parameter advanced parameters | monitoring times | call
timeout retrigger also with "request status of link" must be activated!
· The message "Request Status of Link" from the master station on the "ACTIVE" interface
may only be transmitted to failed remote terminal units. This message is used with NUC-
Redundancy for the switchover to "PASSIVE".
The message "Request Status of Link" is used with the station-selective clock
synchronization of the 1703 master station for the acquisition of the transmission time.
à With NUC-Redundancy, the clock synchronization command may only be transmitted
BROADCAST and not station-selective!

DC0-023-2.12, Edition 06.2017
element in the SICAM RTUs internal IEC 60870-5-101/104 format. These are converted by
on the transmission line to a SICAM RTUs internal IEC 60870-5-101/104 format and
4.9.1 Blocking

Edition 06.2017, DC0-023-2.12
4.9.2 Class 1, 2 Data
According IEC60870-5-101, data can be sent in multipoint configurations using unbalanced

transmission mode from remote station to master station as data class 1 or as data class 2.
The default operation of the master station is polling the remote stations with request data
class 2.
The remote station reports to the master station with the ACD-Bit=1 in the control field of the
message, that class 1 data is stored in the remote station for transmission.
For this, a class 1 message is buffered on the protocol element until this is requested by the
master station.
The assignment of the data as data class 1 or data class 2 has to be done on the basic
system element (BSE).
The prioritization of data (class 1, 2) can be selected in the remote station with the parameter
advanced parameters | IEC60870-5-101 | prioritization of data.
Prioritization of data (Class 1, 2):
· Class 2 (=default)
From the remote terminal unit in multi-point traffic, data is normally always transmitted for
SICAM RTUs master stations as class 2 data. SICAM RTUs internal mechanisms for the
prioritization of the data to be sent provide extensive options in order to be able to transmit
important data to the master station.
· Class 1, 2
Transmission of "data class 1" and "data class 2" according IEC60870-5-101.
Note:
Data class 1 can be sent by the remote station as reply for data class 2 request if there is
no data class 2 stored for transmission at specific time.
· Class 1, 2 (ARCC – project specific)
Data class 1 will be sent only as reply for data class 1 requests.
Data class 2 will be sent only as reply for data class 2 requests.
Send ACTCON, ACTTERM, INIT-End as class 1 data
The assignment of the messages ACTCON, ACTTERM and INIT-End to the data class 1
takes place by special function of the protocol element.
The enabling of the function is carried out on the protocol element by setting the parameter
advanced parameters | IEC60870-5-101 | prioritization of data to "Class 1,2".
The other parameters for the assignment of the messages ACTCON, ACTTERM and INIT-
End to the data class 1 are displayed on enabling the function.
The detailed description is included in the section special functions.
Required parameter settings on the basic system element:
· Sending of "end of initialization" must be enabled

DC0-023-2.12, Edition 06.2017
For the interfacing to external systems the following special functions can be activated for the
adaptation of the message conversion:

· Send GI-data as class 1 data
· Send End of init message as class 1 data
· Send ACTCON, ACTTERM message as class 1 data
· Non interruptible GI
· Timeout monitoring for GI-data
· Convert general interrogation command to BROADCAST in receive direction
· Do not store general interrogation commands in receive direction
· ACTCON for clock synchronization command
· Emulate ACTCON+/-
· Emulate ACTCON for commands
· Message synchronization
· Filtering of measured values with COT=3 (spontaneous) in transmit direction

tag | summer-time bit (SU) = 0 the summer time bit (SU) in the time tag is always set
to “0" by the protocol element for all messages with time tag in transmit direction.
4.9.3.2 Day Of Week = 0 for all Messages in Transmit Direction

tag | Day of week (DOW) = 0 the day of the week (DOW) in the time tag is always set to
“0” by the protocol for all messages with time tag in transmit direction.
Note:

Edition 06.2017, DC0-023-2.12

originator address in transmit direction = 0 for all messages in transmit
direction the originator address is always set to 0 by the protocol element.
Note:
The originator address (= 2nd byte of the cause of transmission) is only then sent if the
number of octets for cause of transmission (COT) is set on the basic system element to 2.
4.9.3.4 Send GI Data as Class 1 Data
When interfacing remote stations to third-party master stations it can be necessary to transmit
all GI-data to the master station as class 1 data.
For SICAM RTUs stations, GI-data is always transmitted as class 2 data.
With the parameter advanced parameters | IEC60870-5-101 | prioritization of
data (GI-data) the protocol element of the remote terminal unit is instructed to transmit GI-
data that are to be transmitted to the master station as reply to a general interrogation
command with the set priority (class 1 or class 2), regardless of the SICAM RTUs internal
parameter setting.
4.9.3.5 Send End of Init Message as Class 1 Data
the end of initialization message to the master station as class 1 data.
For SICAM RTUs stations, the end of initialization message is always transmitted as class 2
data.
With the parameter advanced parameters | IEC60870-5-101 | advanced
parameters (prioritization of data) | prioritization of data INIT-END (TI
70) the protocol element of the remote terminal unit will be instructed to transmit the end of
initialization message with the selected data class (class 1 or class 2), regardless of the
SICAM RTUs internal parameter setting.
4.9.3.6 Send ACTCON, ACTTERM Message as Class 1 Data
the messages for "activation confirmation" (ACTCON) and "activation termination"
(ACTTERM) to the master station as class 1 data.
For SICAM RTUs stations, this messages will be sent as default with the same data class
priority as used for the associated indication.
With the parameter advanced parameters | IEC60870-5-101 | advanced
parameters (prioritization of data) | prioritization of data
ACTCON,ACTTERM (TI45-51, TK101-107) the protocol element of the remote terminal unit
will be instructed to transmit the messages for "activation confirmation" (ACTCON) and
"activation termination" (ACTTERM) to the master station with the selected data class (class 1
or class 2), regardless of the SICAM RTUs internal parameter setting.

DC0-023-2.12, Edition 06.2017
4.9.3.7 Non Interruptible GI
According IEC 60870-5-101, spontaneous or periodic data can be sent during general
interrogation and thus the general interrogation can be interrupted.
When interfacing remote stations to third-party master stations it can be necessary to disable
the spontaneous or periodic data transmission during general interrogation.
Note:
A detailed description of the function "Non Interruptible GI" can be found in the section
"General Interrogation, Outstation Interrogation".
4.9.3.8 Timeout Monitoring for GI Data
With parameter advanced parameters | IEC60870-5-101 | Monitoring time for

GI-data enabled, all data following a general interrogation command are to be transmitted
from the protocol element of the remote terminal unit to the master station as class 1 data. A
timeout is thereby started with the message "ACTCON for general interrogation command"
and retriggered with each message with the cause of transmission "interrogated by station
interrogation" or "background scan". As long as the timeout is running, all data is transmitted
to the master station as class 1 data regardless of their cause of transmission.
This procedure for class 1 data does not conform to IEC 60870-5-101 and is thus only to be
implemented when coupling to master stations which specifically require this procedure!
4.9.3.9 Convert General Interrogation Command to BROADCAST in

Receive Direction
With the parameter advanced parameters | IEC60870-5-101 | GI command

"broadcast" enabled, all general interrogation commands <TI=100> received by the
protocol element of the remote terminal unit are transferred to the basic system element from
the transmission line with the "cause of transmission = activation" with the address CASDU =
BROADCAST.
4.9.3.10 Do not store General Interrogation Commands in Receive

Direction
When a general interrogation is in progress, further received general interrogation commands

wil be stored on base system element (BSE) as 1703 standard operation (for each CASDU
and each group) and processed after termination of general interrogation in progress.
When interfacing remote stations to third-party master stations it can be necessary that
general interrogation commands should not be stored (only the actual requested GI-data
should be sent).
advanced parameters | IEC60870-5-101 | GI-handling to "ARCC (project specific)".
With this parameter enabled only the actual general interrogation command will be processed;
A stored GI-request will be deleted and possible GI-transmission in progress will be stopped
and discarded by the protocol element.
à Only GI-data for last received general interrogation command will be sent.

Edition 06.2017, DC0-023-2.12
4.9.3.11 Emulate ACTCON+ for Clock Synchronization Command
The transmission of ACTCON+ by the remote terminal unit for the clock synchronization can
be set with the parameter advanced parameters | IEC60870-5-101 | ACTCON for
clock sychronization command as follows:

· Send immediately
· Send immediately and ignore (do not accept clock synchronization command)
More details for clock synchronization command can be found in section clock
synchronization.
4.9.3.12 Emulate ACTCON+/- for Commands
If ACTCON is not supported by the basic system element or by the peripheral element used,
then the emulation of ACTCON can be performed by the protocol element (PRE) of the
remote terminal unit as follows:
Emulation of Note
ACTCON- for <TI=45> single command
<TI=48> setpoint command, normalized value
<TI=49> setpoint command, scaled value
<TI=50> setpoint command, floating point number
ð ACTCON+/- from BSE or PE is sent from PRE
ACTCON- for <TI=100> (general-) interrogation command
* CASDU is not known to the PRE and
ð ACTCON+/- from BSE is sent from PRE
ACTCON+/- for <TI=101> counter interrogation command
ð ACTCON+ send immediately from PRE if
* CASDU is known to the PRE or
* CASDU = FFFF (=BROADCAST)
ACTCON+/- for <TI=103> clock synchronization command if
ð ACTCON+ send from PRE if
* CASDU = FFFF (=BROADCAST) *)
*) the moment for the transmission of ACTCON+ in the remote terminal unit can be parameterized
with the parameter advanced parameters | IEC60870-5-101 | ACTCON for clock
sychronization command
Legend:

PE ........... Protocol element

DC0-023-2.12, Edition 06.2017
The emulation of ACTCON in the remote terminal unit can be activated on the protocol
element with the parameter advanced parameters | IEC60870-5-101 | ACTCON +/-
emulation. So that the emulation can be performed by the protocol element, it must be
ensured that the INIT-End messages are passed on from the basic system element to the
protocol element (required because of the known CASDU addresses).
The parameter setting necessary is to be performed on the basic system element (BSE) in the
IEC 60870-5-101/104 parameter block.
4.9.3.13 Emulate ACTCON+ for Commands
If ACTCON for commands is not supported by the peripherals element used, then the
emulation of ACTCON messages can be performed by the protocol element of the remote
terminal unit as follows:
Emulation of Note
ACTCON+ for <TI=45> single command
ð ACTCON+ from PRE send immediately (for SELECT and EXECUTE
command)
ð ACTCON+/- from BSE is filtered out by PRE and not sent!
ð ACTTERM+/- from BSE is sent from PRE
The emulation of ACTCON for commands in the remote terminal unit can be activated on the
protocol element with the parameter advanced parameters | IEC60870-5-101 |
ACTCON emulation.
With function activated, ACTCON messages are emulated by the protocol element as shown
in the table. All ACTCON+/- messages that are transferred from the basic system element to
the protocol element are filtered out by the protocol element and therefore not transmitted.
ACTTERM messages that are transferred from the basic system element to the protocol
element are transmitted by the protocol element.
With function not activated, ACTCON and ACTTERM messages that are transferred from the
basic system element to the protocol element are transmitted by the protocol element, no
emulation of any kind by the protocol element takes place.
Note:
This function is not required in SICAM RTUs or if the this function is supported by the
peripheral elements used!
For the emulation of ACTCON- with unknown CASDU, the parameter advanced
parameters | IEC60870-5-101 | ACTCON +/- emulation is to be enabled.

Edition 06.2017, DC0-023-2.12
4.9.3.14 Message Synchronization
With the parameter advanced parameters | IEC60870-5-101 | message

synchronization one can select between the following methods of synchronization for
disturbed reception:
Standard (IEC 60870-5-1) Mode-A (68 xx yy)

Received byte sequences "68,X,Y" (without Received byte sequences "68,X,Y" (without gaps
gaps between the bytes): between the bytes):
If X ≠ Y If X ≠ Y
ð Message synchronization after a pause ð The receiver must discard 68 and begin with
(> 33 Bit Idle) the IEC message check from X.
(without pause > 33 Bit Idle)
4.9.3.15 Filtering of Measured Values with COT=3 in Transmit Direction

rd
When interfacing remote stations to 3 party master stations, it can be necessary to suppress
(filtering) measured values with cause of transmission "spontaneous". These measured
values will be requested by master station using general interrogation command with groups
or transmitted cyclic.
The filter for transmission of spontaneous measured values can be activated on protocol
element with the parameter advanced parameters | IEC60870-5-101 | filtering of
measured values with COT=3 in transmit direct..
Following messages with measured values and cause of transmission "spontaneous" will be
filtered out when function is enabled:
· <TI:= 9> Measured value, normalized value

· <TI:=10> Measured value, normalized value with time tag
· <TI:=11> Measured value, scaled value
· <TI:=12> Measured value, scaled value with time tag
· <TI:=13> Measured value, short floating point value
· <TI:=14> Measured value, short floating point value with time tag
· <TI:=34> Measured value, normalized value with time tag CP56Time2a
· <TI:=35> Measured value, scaled value with time tag CP56Time2a
· <TI:=36> Measured value, short floating point value with time tag CP56Time2a
Note:
Only measured values with <TI:=34,35,36> will be sent from basic system element (BSE) to
protocol element (PRE). The different IEC60870-5-101 message formats for transmission on
line to 3rd party master station will be generated by protocol element according the parameter
settings for IEC60870-5-101 parameters (located on BSE).
The suppressed (filtered out) measured values will not be sent by the protocol element to the
master station and deleted without any error or warning.

DC0-023-2.12, Edition 06.2017
4.10 Transparent Mode (Tunneling)
The Transparent Mode (or Container Mode) is used to pass through external computer
messages in IEC 60870-5-101 format between a remote station and a third-party control
system that is connected to the SICAM RTUs component with IEC 60870-5-104. The
container mode thus provides a "tunneling method" within the system SICAM RTUs.
These external computer messages are transmitted to or received from an external control
system in a user data container defined for SICAM RTUs in the private range of the
IEC 60870-5-101. The user data container is then not sent to the remote terminal unit, rather
the IEC 60870-5-101 message contained in the message data of the user data container.
As a result, either message formats in the public or private range of the IEC 60870-5-101
standard not supported by the System SICAM RTUs can be transmitted from a third-party
remote terminal unit to a third-party control system or all messages according to
IEC 60870-5-101 which do not need to be routed individually when using the container mode
in the System SICAM RTUs.
In container mode only the user data messages are transmitted transparently through the
SICAM RTUs network – messages for protocol control (station initialization, station
interrogation, acknowledgement messages,...) are not transmitted and are dealt with directly
on the interface to the external remote terminal unit by the protocol element for the master
station.
With special procedures (e.g.: remote parameterization of a third-party remote terminal unit by
a third-party control system), before using the container mode it is to be checked whether the
changed chronological behavior will be tolerated by the connected third-party systems and
that no error messages or failures occur as a result.
The transmission of the user data container within the System SICAM RTUs takes place with
type identification <TI=142> in the private range of IEC 60870-5-101 or IEC 60870-5-104
respectively. SICAM RTUs internal, several modes are provided for the use of the user data
container. The container mode uses the user data container with message type = 128 (=1703
Standard-Format).
The container mode can be activated separately for transmit / receive direction with the
parameter advanced parameters | project specific | Container mode in
transmit direction and the parameter advanced parameters | project specific
| Container mode in receive direction.
With container mode activated in receive direction, all valid received messages from the third-
party system are entered in a user data container and passed on from the protocol element to
the basic system element (BSE) for further distribution within the system.
With container mode activated in transmit direction, data to be are transferred from the basic
system element (BSE) to the protocol element in a "user data container <TI=142> and
message type = 128“, read out from the user data container and the message data sent to the
third-party system. All other data passed on from the basic system element (BSE) to the
protocol element for transmission are sent unchanged to the third-party system.
The IEC-address of the user data container is fixed defined and is not to be parameterized
(CASDU = CASDU of the remote terminal unit; IOA1, IOA2 = 255; IOA3 = 191).

Edition 06.2017, DC0-023-2.12
Segmentation
transmitted. Longer external computer messages (max. 256 bytes) are thus to be transmitted
in several part segments and grouped together again before transmission/processing. With
missing segments the partially transmitted parameter message is discarded.
data!
User data container <TI=142>

The user data container is used to pass through external computer messages.
27 26 25 24 23 22 21 20
Originator address
CASDU1
CASDU2
IOA1
IOA2
IOA3
: : : : : : : :
: : : : : : : : 7 bytes dual time (IEC 60870-5-101)
: : : : : : : :
45 UEK = 45
S=1 I=0 State
Number of bytes 2)
Interface number (process channel)
Sum of the segments = 1 Current segment number = 1 Segment information
22 Protocol type = 22 (=IEC 60870-5-101)
0 Reserve

(LSB)

(MSB)
0 0 0 0 Function Message data (0)
: : : : : : : : :
: : : : : : : : :
Message data (n) max. 50 bytes
2) Number of bytes of the message data + 6 (max. 56 bytes)
Note: The user data container is described here in the internal format of the protocol element
with the essential information fields.

DC0-023-2.12, Edition 06.2017

O1 .. Octet 1 (CASDU) CASDU = CASDU of the remote terminal unit
O2 .. Octet 2 (CASDU) CASDU = CASDU of the remote terminal unit
IOA1 .. = 255
IOA2 .. = 255
IOA3 .. = 191 (subaddress)
Time
Message type = 128
octets
Number of bytes Number of bytes of the message data + 6
Segmentation field
Total number of segments Total number of segments (4 Bit)
... Total size = 15 segments each of 50 octets
Current segment number Current number of the transmitted segments (4 Bit)
Length of the message data in bit in all segments the total length of the message data is always
transmitted in bit.
Structure of the message data:
27 26 25 24 23 22 21 20
0 0 0 0 Function Control Byte
Link address
Data (0)
:
:
Data (n)

Control byte "Function" (Bit 0-3)
03 .. User data SEND / CONFIRM
04 .. User data SEND / NO REPLY
Link address The length of the link address to be sent is determined
with a parameter.

Edition 06.2017, DC0-023-2.12

· Applicational control of the station interrogation

· Setting control location
· Testing the reachability of stations
· the suppression of errors with intentionally switched-off stations (Station Service)

· the obtaining of station interrogation information
· the obtaining of information about the route state/failure of main/standby transmission line
Block Diagram
Protocol element
control
Internal
Transmission route
function
Protocol element


DC0-023-2.12, Edition 06.2017
message.
Possible master station functions:
Parameter
Call cycle START 0 125 -
Call cycle STOP (disabling) 1 125 -
Call cycle CONTINUE (enabling) 2 125 -
Z-Par=continuous call time (n * 100ms)
Continuous call station x ON 3 0 – 99 0 -65535 Z-Par=0: Continuous call without time input
(stopped by other function)
Continuous call station x OFF 4 0 – 99 -
Main transmission line ACTIVE 5 0 – 99 -
Standby transmission line ACTIVE 6 0 – 99 -
Master coordination (Token) only used internal between PRE's!
10
for Main-/Standby line
Connection set-up 11 reserved for internal use!
Connection closed 12 reserved for internal use!
- deactivate interface
- RS232 interface = TRISTATE
"Deactivate" interface 13
- redundancy bit in received messages
will not be set *)
"Activate" interface 14 activate interface *)
''Deactivate'' "transmitter tristate" the interface and
20 - -
message.
''Activate'' "transmitter tristate" the interface and
21 - -
message.
*) nearly same function as with system internal redundancy control function but controllable with protocol element
control message

Edition 06.2017, DC0-023-2.12
Possible master station functions: (continued)
PST Detail Routing

Function **) SF Station Z-Par Fl Note
only parameterized RTUs can be added to
the station polling.
Add station to station polling 128 0 – 99 -
ð otherwise error "faulty PST-control
message"
only parameterized RTUs can be removed
from the station polling.
ð otherwise error "faulty PST-control
Remove station from station polling 129 0 – 99 0,1
message"
Z-Par=0: Reset present station fault
Z-Par=1: Do not change present station fault
240 - - message and not using PRE-control
command
message!
CASDU = BROADCAST
241 - -
SCS=<ON>: set control location (HKA)

65535
(all stations)
125
SCS=<OFF>: reset control location (HKA)
65535
(all stations)
Set control location 2) 242
65535
(selective station)
0 – 99
65535
(selective station)
Reset command 243 This function is actually not supported by
- -
PRE!
244 - CASDU message and not using PRE-control
command
message!
CASDU = selective
routing.
SCS = <ON> additional parameter in PRE control message = HKA

SCS = <OFF> additional parameter in PRE control message = HKA + 256
Legend:
SF .............. Control function_(PRE)

Station ....... Station number
0 - 99 = station 0 - 99 of the selected protocol element
125 = all stations of the selected protocol element (=BROADCAST)
Z-Par ......... Additional parameter_(PRE)
Fl ............... Edge
SCS ........... single command state
HKA ........... Originator address (HKA) = 0 - 255

DC0-023-2.12, Edition 06.2017
Possible remote terminal unit functions:
PST Detail Routing

I – Bit handling for time "OFF" 0 - - *)
I – Bit handling for time "ON" 1 - - *)
Send (general) interrogation command 240 This function is processed on the BSE and
message and not using PRE-control
message!
CASDU = BROADCAST
Send (general) interrogation command 241 This function is processed on the BSE and
for GI-group to own BSE 1) not sent to the protocol element as PRE-
(=simulate received general interrogation command control message!
for GI group)
Reset command 243 This function is actually not supported by

PRE!
*) the protocol element stores the moment/state for the last received PRE-control message
"I–Bit handling for time ON / OFF" (=ti/e/a) from basic system element
for all messages with process information with time tag in transmit direction, the Invalid-Bit of the time tag is set
by the protocol element, if the time in the message is the same or after the moment ti/e
for all messages with process information with time tag in transmit direction, the Invalid-Bit of the time tag is
reset by the protocol element, if the time in the message is the same or after the moment ti/a
Legend:

Z-Par.......... Additional parameter_(PRE)
Fl ................ Edge

Edition 06.2017, DC0-023-2.12
· Status of the state lines

Possible return information of master station:
Parameter
Status DTR (1 = state line active) 255 Status DTR 1)
0 = status line inactive
Status DSR (1 = state line active) 255 Status DSR 1)
Station status 0 – 99 1 = Station enabled for call cycle
Station failure 0 – 99 1 = Station failed
Interface activated/deactivated":
"activate/deactivate" interface
0 = interface "activated"
1 = interface "deactivated"
Interface + protocol functions "activated/deactivated":
"activate/deactivate" interface + protocol functions
0 = interface + protocol functions "deactivated"
1 = interface + protocol functions "activated"
1) states of the state lines are transmitted spontaneously from the protocol element to the basic system element
takes place internally in a 100 ms grid ð State line changes shorter than 100 ms are not guaranteed to be
transmitted!

DC0-023-2.12, Edition 06.2017
Possible return information of master station (continued):
Parameter
protocol-specific return information 0 0 – 99 Main transmission line parameterized
protocol-specific return information 1 0 – 99 Main transmission line OK
protocol-specific return information 2 0 – 99 Main transmission line faulty
protocol-specific return information 3 0 – 99 Main transmission line NOK
protocol-specific return information 8 0 – 99 Standby transmission line parameterized
protocol-specific return information 9 0 – 99 Standby transmission line OK
protocol-specific return information 10 0 – 99 Standby transmission line faulty
protocol-specific return information 11 0 – 99 Standby transmission line NOK
protocol-specific return information 0 255 Cycle IDLE
- cycle control is stopped.
User data messages will be sent furthermore.
protocol-specific return information 1 255 Cycle NORMAL MODE
- cycle control running in normal mode
(cyclic RTU interrogation)
protocol-specific return information 2 255 Continuous call
- Continuous call of an RTU presently running
protocol-specific return information 3 255 Cycle stopped
- cycle has been stopped with PST – control message
protocol-specific return information 6 255 Sending "Data to all"
- User data message "to all" (BROADCAST) is now
being transmitted
protocol-specific return information 7 255 Sending "data message"
- station-selective user data message is now being
transmitted
protocol-specific 0 – 99 The return information value can be selected
return information value via parameter.
- retries in % (of the last full hour)
IEEE 754 floating point format will be used for

return information value.
Legend:

0 - 99 Station 0-99 of the selected protocol element
255 Station number not used!
Possible remote terminal unit return information:
Parameter
Status DTR 255 Status DTR 1)
Status DSR 255 Status DSR 1)
takes place internally in a 100ms grid ð State line changes shorter than 100ms are not guaranteed to be
transmitted!

Edition 06.2017, DC0-023-2.12

DC0-023-2.12, Edition 06.2017
5 Interfacing of Protective Devices (103)
Contents
5.1 Introduction .................................................................................................. 154

5.2 Communication according to IEC 60870-5-103 ............................................. 159
5.3 Transfer of Parameters for Reyrolle Protection Equipment ............................ 179

DC0-023-2.12, Edition 06.2017
Interfacing of Protective Devices (103)
5.1 Introduction
For the interfacing of digital protective devices or protective devices according to IEC 60870-
5-103, a serial communications protocol is implemented for multi-point traffic, with which one
master station is connected with one or several protective devices (remote terminal units) over
a communication link in a linear or star configuration.
The data traffic is controlled by the master station. Either data messages or station
interrogation messages are transmitted from the master station. Data from the remote terminal
unit to the master station can only be transmitted as reply to a station interrogation.
Master station
TF
TF TF TF
Legende:

The master station and the remote terminal units in multi-point traffic function with a
communications protocol according to IEC 60870-5-103. The supported functionality
(Interoperability) is shown in the document SICAM RTUs Interoperability IEC 60870-5-103
(DC0-025-1) or in the document Ax 1703 Interoperability IEC 60870-5-103 (DA0-072-1)
respectively.
SICAM AK3
SICAM AK
103MA0 IEC 60870-5-103 Unbalanced (Multipoint MASTER)
SICAM BC
SICAM TM
SICAM AK3
SICAM AK
103SA0 IEC 60870-5-103 Unbalanced (Multipoint SLAVE)
SICAM BC
SICAM TM
CP-8000
103MT0 CP-802x IEC 60870-5-103 Unbalanced (Multipoint MASTER)
SICAM EMIC

Edition 06.2017, DC0-023-2.12
103MA0
103MT0
103SA0
General Functions
· Serial communication protocol according IEC60870-5-103 ü ü ü
· Unbalanced transmission Master ü ü

(Primary Station)
· Unbalanced transmission Slave ü
(Secondary Station)
- Point-to-point configuration (Master+ 1 Slave) ü ü ü
- Multiple point-to-point configuration (separate interface for each single ü ü ü

point-to-point configuration required)
- Multipoint partyline ü ü ü
- Multipoint star ü ü ü
- max. Connections 100

1)
1 100
2)
- Controlled Station ü

− Unbalanced interchange circuit accordingV.24/V.28 standard ü ü ü
− Transmission medium (full duplex)
− Transmission medium (half duplex) ü ü ü

− Byte Frame (8E1) ü ü ü
− Data flow control Bit supervision ü ü
· Interoperability
− Compatibility level 1 (VDEW/ZVEI Standard) ü ü ü
− Compatibility level 2 (Disturbance Data) ü ü ü
− Compatibility level 3 (Generic Services)
− Message Conversion (protocol mode / message format)

- IEC60870-5-103 / IEC60870-5-103 “standard“ [default] ü ü ü
- IEC60870-5-101 / IEC60870-5-101 ü
- IEC60870-5-103 / IEC60870-5-101 “tunneling mode“ ü 3) ü 3) ü 3)
− IEC 60870-5-103 Interoperability (DC0-026-2) ü ü ü
· Data acquisition by polling (station interrogation) ü ü ü

− Continuous Interrogation of a Remote Terminal Unit ü ü
− Station failure delay
− Quick check procedure
· Acquisition of events (transmission of data ready to be sent) ü ü ü

− Test Mode ü ü

DC0-023-2.12, Edition 06.2017
103MA0
103MT0
103SA0
General Functions
· General interrogation, outstation interrogation ü ü ü

− Delayed transmission of general intwerrogation command ü ü
− Timeout monitoring for GI-data
· Clock synchronization according IEC60870-5-103 ü ü ü

− cyclic clock synchronization (parameterizable) ü ü
− correction of clock synchronization (via parameter) ü ü
− Accuracy +/-
20ms
· Command transmission ü ü ü
− Demand ü ü

· Transmission of integrated totals ü ü ü
· File transfer
− Disturbance records to SICAM DISTO ü ü ü
− Disturbance records to control centre systems according ü ü
IEC 60870 5 101/104
· Optimized parameters for selected transmission facilities (modems)
− Predefined optimized parameters for selected transmission facilities ü ü ü
− Free definable parameters for transmission facility ü ü ü
− 5 V power supply via DSR status signal for external modems.
ü ü ü
− 1703 redundancy ü
- Listening mode when passive ü
- Tristate of RS-232 interface when passive ü

− Activation/Deactivation of interface when passive ü
with protocol element control message
− Main-/Backup transmission line with 2 interfaces ü
− Deactivation of interface (with redundancy control message) ü

− Protocol element control messages

Edition 06.2017, DC0-023-2.12
103MA0
103MT0
103SA0
General Functions
− Send (general) interrogation command to all ü ü ü

− Send (general) interrogation command for GI-group to own BSE ü4) ü4) ü4)
− Send (general) interrogation command to selective CASDU ü ü ü

− Send (general) interrogation command for image GI to
own BSE
− Reset command

− Call cycle START / STOP / CONTINUE ü ü
− Continuous call station x ON / OFF ü ü
− Station failure ü ü
− Station status ü ü
− Status DTR (1 = state line active) ü ü ü
− Status DSR (1 = state line active) ü ü ü
− Protocol-specific return information 0 -3, 6, 7 ü ü
· Remote maintenance with SICAM TOOLBOX II via serial connection
− Send short-circuit location values with GI ü ü
− Resetting the short-circuit location values ü ü
- Reset short-circuit location values with command ü ü
- Reset short-circuit location values automatically ü ü

− Signaling / measured value disabling ü ü
− Technological adaptation for measured values ü ü ü
− Measured value change monitoring ü ü
− Monitoring intermediate and faulty positions of double-point information ü ü
− Transfer of the information "blocked activation/tripping of the protection" ü ü
− Transmit non-updated process images ü ü
− Emulation of the going binary information ü ü
− Remote-configuration of Reyrolle relays ü ü
1) recommandation max. 30 stations
2) recommandation max. 10 stations
3) IEC 60870-5-101 messages are transmitted in IEC 60870-5-103 container messages (in the
private range)
... with SICAM RTUs configurations with BC 1703 the conversion
of IEC 60870-5-101 à IEC 60870-5-103 à IEC 60870-5-101 can be omitted

DC0-023-2.12, Edition 06.2017
General Functions
Communication between one central station and one or more remote protective devices
· Unbalanced multi-point (multi-point traffic) according to IEC 60870-5-103
103Mxx is controlling station (primary station), 103Sxx / protective device is
controlled station (secondary station).
─ Supported functionality according to
− SICAM RTUs Interoperability IEC 60870-5-103 (DC0-026-1)
− Ax 1703 Interoperability IEC 60870-5-103 (DA0-063-1)
─ Data acquisition by polling (station interrogation)
─ Acquisition of events (transmission of data ready to be sent)
─ General interrogation, outstation interrogation
─ Clock synchronization
− Cyclic, can be set in a seconds grid
─ Command transmission
− Set control location, control location check
─ File transfer
− Disturbance records to SICAM DISTO
− Disturbance records to control centre systems according to IEC 60870-5-101/104
─ Generic functions
· Resetting the short-circuit location values
· Measured value change monitoring
· Monitoring intermediate and faulty positions of double-point information
· Transmission of parameters and diagnostic information for Reyrolle protection equipment
(Embedded REYDISP)
· Optimized parameters for selected transmission facilities
· Functions for supporting redundant communication routes
· Message conversion
– IEC 60870-5-101 ó IEC 60870-5-103
– IEC 60870-5-101
– IEC 60870-5-101 ó IEC 60870-5-103 "Container Mode"
The operating mode of the interface is determined by parameters and optional equipment.
Standard Operation Extras 1) Interface Signals

Mode
Unbalanced interchange --- RXD, TXD, CTS, RTS, DCD, DTR,
circuit V.24/V.28 DSR/+5V, GND
V.28 asynchronous
Optional Operation Extras 1) Interface Signals

Mode
Balanced interface CM-0829 RXD, TXD, CTS, RTS, DCD, DTR,
RS-485 DSR/+5V, GND
V.11 asynchronous
with CM-0829
Optical interface CM-0827 RXD, TXD, +5V, GND
(multimode fiber optic)
with CM-0827
1) Extras are optional equipment

Edition 06.2017, DC0-023-2.12
interrogated sequentially, whereby remote terminal units with important data can be
interrogated more often. Remote terminal units may only transmit when they are called.
The interrogation procedure can be influenced with the following parameters:

· Continuous cycle
· Existing stations
· Number of calls until station change
· Number of stations to be called until change of priority level
· Priority level assignment (each station is assigned one of the 4 priority levels:
high priority, medium priority, low priority-A, low priority-B)
on request. The continuous interrogation of the remote terminal units by the master station
interrogation procedure is to be performed by enabling the parameter advanced
parameters | continuous cycle.
No", "Link Address", "Station Enabling", "Station failure", "Priority Level", "Number of calls",
“Block of class 2 data” are to be set in the parameter station definition.
Common settings | Address of the link. This address must be unambiguous for each
multi-point traffic line. For IEC 60870-5-103 the number of octets for the "Address field of the
link layer" is defined with 1 octet.
The prioritization of the station interrogation can be parameterized by means of corresponding

parameter setting of the number of stations called until level change with the following
parameters:
Parameter
Ÿ Station call prioritization | No. of stat. calls in high priority lvl
Ÿ Station call prioritization | No. of stat. calls in mid. priority lvl
Ÿ Station call prioritization | No. of stat. calls in low prior. lvl(A)
Ÿ Station call prioritization | No. of stat. calls in low prior. lvl(B)
Through parameterization of the interrogation procedure the following characteristics can be

achieved:
· A remote terminal unit which has a lot of data to send - e.g. continuously changing
measured values – does not impair the disposal of the data of the other remote terminal
units.
· Each remote terminal unit is interrogated within a determinable time (deterministic).
· Remote terminal units with important data or those with a large volume of data to be
transmitted can be interrogated more frequently than the others.

DC0-023-2.12, Edition 06.2017

Interrogation Procedure of Master Station - Change of Station during
The master station will do a change of station during interrogation procedure when:
· “requested data not available” message received from remote station

· “data class 2“ message received with “ACD=0“ from remote station
(ACD=0: remote station has no “data class 2“ stored for sending)
· limit for number of consecutive station calls reached
(e.g. remote station has permanent “data class 2” ready for sending)
· “NAK confirmation“ message received from remote station
· no answer from remote station received (e.g. in case of error – after retries)
· remote station failed and no answer received after 1x retry

Edition 06.2017, DC0-023-2.12
Below the prioritization of the station interrogation for continuous cycle is shown based on the
specified parameters as an example.
Parameter for "Station call prioritization"

High priority level……….Number of stations called until level change = 2
Medium priority level…...Number of stations called until level change = 2
Low priority level (A)……Number of stations called until level change = 1
Low priority level (B)……Number of stations called until level change = 1
Station U0, U4…………..High priority level / Number of calls until station change = 2
Station U1,U2,U3……….Medium priority level / Number of calls until station change = 2
Station U5,U6,U7, U8….Low priority level (A) / Number of calls until station change = 1
Station U9,U10………….Low priority level (B) / Number of calls until station change = 1
Œ
t
U0
U1
U2
U3
U4
U5
U6
U7
U8
U9
U9
U10
U10
Legend:
…..….. Remote station in the „High priority level“
…..….. Remote station in the „Medium priority level“

…..….. Remote station in the „Low priority level (A)“
U10 …..….. Remote station in the „Low priority level (B)“

,..…...….. Data message, short acknowledgement (remote station à master station)
,…..….. Data message (Command), calling message (remote station à master station)


DC0-023-2.12, Edition 06.2017
For the interfacing of protection equipment with the protocol IEC 60870-5-103, no variable
elements of the message are provided.
Description IEC 60870-5-103 Note

Number of octets for the address field of the link 1 Octet
layer
Number of octets for cause of transmission 1 Octet
Number of octets for common address of the 1 Octet ASDU is identical with
ASDU address of link layer
(=station address)
Number of octets for the address of the 2 Octets IOA1 = Function type
information object IOA2 = Information
number
Acknowledgement message Single character or
short message (ACK)
Number of octets for time tag 4 Octets
one selected station. An automatically started continuous interrogation of one remote terminal
following a message transmission is known as a demand. Data messages ready for sending
to same remote station will be sent during demand in progress.
control message.
be parameterized). On expiry of the number of retries, the station is flagged as faulty.
the case, if additional signal propagation delays, delay times or slow processing times of the
selective).

Edition 06.2017, DC0-023-2.12
The acknowledgement from the remote terminal unit to the master station is transmitted as
single character (E5), if no additional information (DCF / ACD-Bit) is to be transmitted. If
additional information is to be transmitted, the acknowledgement is transmitted as message
with fixed length (ACK).
retry handling. For failed remote terminal units, a communication fault is only then reported, if
this is parameterized accordingly in the parameter station definition | station
failure.
station with the interrogation procedure however no message retry is performed for such
The interrogation cycle for failed stations can be set with the parameter advanced
parameters | IEC-parameter | polling cycle for faulty stations. As a result,
failed remote terminal units are removed from the running interrogation procedure for a certain
time and from then are only interrogated in the parameterized grid.
terminal unit.
Fault Monitoring in redundant Master Stations

In redundant configurations the fault monitoring in the PASSIVE (=STANDBY) master station
is done global for the failure of the interface and station-selective for the remote terminal units.
cyclic message reception (receive timeout). The monitoring time is set with the parameter
Redundancy | listening_mode (failure monitoring time).
The failure monitoring (station-selective or global) will be retriggered with each error free
received message. On receive timeout (active master station or transmission facility of the
master station has failed) the interface is signaled as failed.
To enable a station selective fault monitoring in the PASSIVE master station even if there is
less or no user data to be sent from the remote terminal units to the master station, the active
master station will send (if failure monitoring time ≠ 0) cyclic a "Reset FCB" or "Request Status
of Link" message to each single remote terminal unit. The cyclic sending of these messages
will be done in following time raster: failure monitoring time / 2. This message will be
confirmed by the remote terminal unit with an ACK message (station address or link address
is part of the ACK message – this enables station selective failure monitoring).
If the remote terminal unit will provide cyclic data for sending, a cyclic sending of "Reset FCB"
or "Request Status of Link" message to each single remote terminal unit is not necessary.
The message type for cyclic sending to enable station selective failure monitoring (Reset FCB
or Request Status of Link) is to be set in the master station with the parameter Redundancy
| cyclic message for station selective failure monitoring.

DC0-023-2.12, Edition 06.2017
The monitoring of the interface in the remote terminal unit is carried out by monitoring for
"cyclic station interrogation". The monitoring time is to be set in the remote terminal unit with
the parameter advanced parameters | call monitoring time.
The call monitoring time will be retriggered in the remote terminal unit usually by station
selective polling messages.
The parameter advanced parameters | call timeout retrigger also with "reset
FCB or KE" has to be used only when formally required (specific functionality or required for
downward compatibility). The message "Request Status of Link" will be sent by the Master
Station during station initialization, acquisition of transmission delay and in case of station
failure.
If an failure of the communication link must be recognized also in the remote terminal unit in
case of faulty communication link (e.g. only monitoring direction is broken), then the message
"Request Status of Link" can’t be used for call timeout retrigger.
The communication with a protective device (remote terminal unit) can only be started after
successfully executed station initialization.
A distinction is made between a reset of the protection equipment itself and a reset of the
communications function of the protective device.
The transmission procedure can be set in the remote terminal unit with the parameter Common
settings | operating mode of the interface. The corresponding station initialization
is selected by means of the selected operating mode.
Operating mode of the interface: IEC 60870-5-103, IEC 60870-5-103 (101)

A reset of the communications function in the protective device (remote terminal unit) is
triggered from the master station by sending a Reset-command. This is generally sent from
the master station if,
· the master station is being initialized (reset or redundancy switchover)

· the protective device (remote terminal unit) does not reply within a defined time
(reset or interface fault)
The reset command does not influence the protection function itself, rather only resets the
communications part of the protective device. The reset command can be transmitted as,
· Reset of frame count bit (FCB) or

· Reset of communications unit (KE)

Edition 06.2017, DC0-023-2.12
After a reset of the master station, the station initialization is always performed with the reset
command "Reset of KE". After redundancy switchover or with station failure, remote terminal
units are initialized with the reset command "Reset FCB". If the remote terminal unit does not
react within a settable time, then the corresponding remote terminal unit is initialized with the
reset command "Reset KE". The time for the switchover of the station initialization can be set
with the parameter advanced parameters | station initialization timeout.

Reset KE [FC=0] - FCB-Bit (Frame Count Bit) is initialized
- Transmit buffer + process image (SSE+BSE) is deleted
Reset FCB [FC=7] **) - FCB-Bit (Frame Count Bit) is initialized
*) in redundant configurations "Reset FCB" or "Request Status of Link" can be sent cyclic to enable
station-selective failure monitoring in STANDBY master station
Operating mode of the interface: IEC 60870-5-101

If the message conversion mode "IEC 60870-5-101" is parameterized in the SICAM RTUs
remote terminal unit, the station initialization takes place according to IEC 60870-5-101.
with:

REQUEST STATUS OF LINK [FC=9] - "STATUS OF LINK" is transmitted to the
master station
RESET of REMOTE LINK [FC=0] - FCB-Bit (Frame Count Bit) is initialized
- Acknowledgement for RESET of REMOTE LINK is


DC0-023-2.12, Edition 06.2017
(BSE) in the remote terminal unit until transmission.
implemented.
5.2.3.2 Test Mode
In the mode "Test Mode" spontaneous binary information and cyclic measured values are
identified in the protective device for the further processing in the control system by means of
the cause of transmission "Test Mode". That means, that message that are normally
transmitted with cause of transmission "spontaneous" or "cyclic" are transmitted with the
cause of transmission "Test Mode".
Messages that are transmitted from the remote terminal unit to the master station with cause
of transmission "Test Mode" can be discarded (filtered out) by the protocol element of the
master function or - if conversion for specific message is supported - converted and
transferred to the basic system element for further distribution/processing.
Possible selections for test mode in receive direction:
· test mode = NO
All received indications from the protection devices with
"cause of transmission = test" <COT=7> will be discarded (filtered out) and
not forwarded to BSE.
All other messages received from the protection devices with
"cause of transmission = test" <COT=7> will be converted to IEC60870-5-101/-104 and
forwarded to BSE with "cause of transmission = spontaneous" <COT=3> and "T=0"
· test mode = YES
All received messages from the protection devices with
"cause of transmission = test" <COT=7>) will be converted to IEC60870-5-101/-104 and
· test mode = YES (T=0)
All received messages from the protection devices with
"cause of transmission = test" <COT=7>) will be converted to IEC60870-5-101/-104 and
Data with test-bit set (T=1) will be routed 1703 internally without any evaluation and sent out
via IEC60870-5-101/-104.
The handling of the data with cause of transmission "Test Mode" can be set on the protocol
element of the master station with the parameter station definition | test mode.
When using the protocol firmware on SMx551 this parameter is part of the station
definition).

Edition 06.2017, DC0-023-2.12
information. The general interrogation function of the master station requests the remote
terminal unit to transmit the actual values of the process variables subject to GI.
A general interrogation command "to all" triggered in the system is always transferred from the
terminal units with "CASDU = BROADCAST".
Some protective devices cannot immediately process a general interrogation command in

certain situations (e.g. after startup, going interface fault or station initialization). Often, the
general interrogation command is then only received by the protection equipment after the
transmission of the identification information or after successful clock synchronization. For
configurations with such protection equipment, a solution for this problem can be offered with
the parameter advanced parameters | send initiation of general
interrogation after delay.
If generic data is used, this function is to be enabled with the parameter advanced
parameters | generic data. With function enabled, a "general interrogation command"
triggered in the system is also transmitted as "GI-command for Generic Data" to the
corresponding remote terminal unit.
(See also in section Message Conversion "Generic Data".)
The clock synchronization of the remote terminal units can be performed over the serial
The period for cyclic clock synchronization can be set with the parameter advanced
parameters | cycle time for sending clock synchronization command.
The accuracy (typical) is ± 20 ms (clock synchronization 1x per minute). If the accuracy of the
remote synchronization is insufficient, a local time signal receiver must be used in the remote
terminal unit.
The clock synchronization command will be sent by the protocol element of the master station
(either spontaneously after startup/at change of time or cyclic) as BROADCAST message
(SEND/NO REPLY service) to the remote stations. The cyclic clock synchronization of the
remote terminal units will be done by the protocol element itself.
If the clock synchronization of the master station fails, the protocol element of the master
station can stop the clock synchronization of the remote stations over the serial
communication line. The remote stations will detect a failure of the clock synchronization and
data with time tag will be sent including "IV-bit of time = 1".
This function can be enabled in the master station with the parameter advanced
parameters | Synchronization also with invalid time.
Default: "Synchronization also with invalid time" = YES.
Note:
- IEC 60870-5-103 does not define procedures for acquisition of transmission delay and
therefore no correction of the time for clock synchronization!

DC0-023-2.12, Edition 06.2017

Terminal Unit
Demand
Data Flow Control

If a remote terminal unit cannot process more data messages (messages), the DFC bit (Data
Flow Control) is set in the control field of the message direction remote terminal unit ð master
station. From this moment the protocol firmware of the master station sends no more data
messages to the corresponding remote terminal unit, until the remote terminal unit resets the
DFC-bit.
The status of the DFC-bit of the corresponding remote terminal units is interrogated cyclic by
the master station with "REQUEST STATUS OF LINK". The protocol firmware of the master
station also monitors whether the remote terminal unit resets the DFC-bit within a time that
can be set with the parameter advanced parameters | IEC-parameter | DFC-
monitoring time. If the DFC-bit is set for longer than the set monitoring time, an station
specific diagnostic information will be set (external error).
Remote terminal units with set DFC-Bit can be interrogated with low priority and consequently
less often by the master station during the station interrogation. With the parameter
advanced parameters | IEC-parameter | operating mode for "DFC-bit = 1" it
can be selected, whether remote terminal units are to continue being interrogated in the
interrogation cycle or with low priority in a slower interrogation cycle. The cycle time can be
parameterized with the parameter advanced parameters | IEC-parameter | polling
cycle for stations with "DFC-bit = 1".

Edition 06.2017, DC0-023-2.12
authority.

the PRE.

DC0-023-2.12, Edition 06.2017

0 default
Note:
control function.
enabled").
enabled").

(unacknowledged)
Message retries | Retries for data message SEND/NO REPLY (broadcast)
The protocol element for IEC 60870-5-103 master function only sends the clock
synchronization command as "Message unacknowledged to all". All other messages are
transmitted station-selective.

Edition 06.2017, DC0-023-2.12
A counter interrogation command triggered in the system is transmitted from the protocol
element of the master station either station-selective or “to all” (=BROADCAST) according to
the parameter advanced parameters | IEC-parameter | send counter
interrogation command as "Broadcast". This parameter is transferred to the basic
system element after startup of the protocol element.
A counter interrogation command to be sent is then already made available to the protocol
element by the basic system element, station-selective or BROADCAST.
A station-selective counter interrogation command is however only then sent by the protocol
element, if an identification message has been received from the corresponding remote
terminal unit during startup with the ASCII text "BC1703ACP".
5.2.8 File Transfer
Disturbance records are recorded and stored in protection equipment. These can be read out
by the master station with the procedures defined in IEC 60870-5-103 for the transfer of files.
The protocol element of the master function supports the following possibilities for reading out
and transferring disturbance records:
· Transfer of disturbance records to SICAM DISTO

· Transfer of disturbance records to IEC 60870-5-101/104 systems
The protocol element of the remote terminal unit supports the transfer of disturbance records
according to IEC 60870-5-103. The disturbance records are managed either in the System
SICAM RTUs on the basic system element (BSE) for protection functions or in another
connected protective device.
SICAM RTUs internal, the IEC 60870-5-103 messages for the transmission of disturbance
records are transmitted in a user data container defined for SICAM RTUs in the private range
of the IEC 60870-5-101.
IEC 60870-5-101/104 *) IEC 60870-5-103

<TI=142> User data container <TI=23> Disturbance event overview
<TI=26> Ready to transmit disturbance data
<TI=27> Ready to transmit one channel
<TI=28> Ready to transmit marks
<TI=29> Transmission of marks
<TI=30> Transmission of disturbance values
<TI=31> Transmission end
<TI=142> User data container <TI=24> Order to transmit disturbance data
<TI=25> Acknowledgement for disturbance data
transmission
*) all with time tag CP56Time2a
The IEC 60870-5-101/104 address of this user data container (CASDU1, CASDU2, IOA1,
IOA2, IOA3) is to be parameterized with the parameter advanced parameters | addr.
for user data container in rx (disturbance record) | *. If the IEC 60870-5-103
protocol element in the remote terminal unit is set to an integrated (local) interface, then the
parameter setting of the address of the user data container is not required – the distribution of
this user data container takes place automatically in this case.
In transmit direction (monitoring direction) a parameter setting of the address of the user data
container is not necessary. IEC 60870-5-103 messages in user data containers are always
transmitted from the protocol element of the remote terminal unit.

DC0-023-2.12, Edition 06.2017
5.2.8.1 Transfer of Disturbance Records to SICAM DISTO
Configuration with SICAM DISTO
The transfer of disturbance records from protection equipment is controlled by SICAM DISTO
(Windows Application). Disturbance records are read out from the protection equipment by
SICAM DISTO according to IEC 60870-5-103 and saved as file in IEEE Comtrade format.
The data transmission between SICAM DISTO and the protocol element to which the
protection equipment are connected, is carried out in the System SICAM RTUs with the user
data containers provided for this purpose.
The protocol element itself performs no special sequences for the transmission of disturbance
records (except cyclic requests of disturbance records overview from protection equipment).
Control System (Host-System)

with SICAM DISTO
AK-Driver 61850-Driver
IEC 60870-5-104
Data in 104 container

(103 Format)
Station control device
SICAM AK 3
or
SICAM TM
Data in 103 format

IEC 60870-5-103

Edition 06.2017, DC0-023-2.12
Disturbance Records Container
All IEC 60870-5-103 message formats necessary for the transfer of disturbance records from
protection equipment are transmitted from the protocol element of the master station between
SICAM DISTO and the protocol element of the master function in a user data container
(=”disturbance records container”) defined for SICAM RTUs in the private range of IEC 60870-
5-101. Only the IEC 60870-5-103 message format included in the user data container will be
transmitted to the protection equipment, and not the data container itself.
identification <TI=142> in the private range of IEC 104-5-104. SICAM RTUs internal, several
modes are provided for the use of the user data container. For the transfer of disturbance
records, the user data container is used with message type = 128 (=1703 Standard-Format).
For each interface with protection equipment connected, a user data container (=”disturbance
records container”) must be parameterized in SIP message address conversion for transmit
and receive direction with unambiguous address and not used station address (e.g. “99” =
“virtual station address”).
The assignment of the message address for the spontaneous information object "User data
container" is carried out in the OPM II with the category firmware / Trans_container and the
category firmware / Rec_container. The "container type" has to be set to "disturb. data
container" with the parameter Containtertype_Rec and the parameter
Containtertype_Tra.
In SICAM RTUs the addresses of all user data containers for the transfer of disturbance
records are to be entered in the data flow filter.
In Ax 1703 the addresses of the user data containers are to be entered in the corresponding
Ax 1703-PRE detailed routings PDS (QID-ST = 254 ... SSE as source).
With the parameterization of the message addresses for the disturbance records container,
the transfer of disturbance records to SICAM DISTO will be enabled.
Sequence of the Disturbance Record Transmission (Protection Device - SICAM DISTO)
The protocol element of the master station will send a cyclic request (every 5 minutes) for
transmission of disturbance records directory to connected protection equipment. With this
procedure the disturbance record overview will be sent cyclic from the protection equipment to
SICAM DISTO. During disturbance record transmission in progress cyclic request will be
retriggered with each single disturbance record message.
Cyclic Request for Disturbance Records Overview:

- the cycle time (5 minutes) for requests of disturbance records is fixed and cannot be changed via parameter.
- the cycle time (5 minutes) for requests of disturbance records will be retriggered with following messages:
with 103Mx0: disturbance records container message BSE ßà PRE
with VDEZ01: disturbance records container message BSE ß PRE
Note: - if a disturbance record transmission is running in forever loop (e.g. caused by error detected by SICAM DISTO
and restart of disturbance transmission) the cycle time for request of disturbance records overview will be
retriggered permanently.
à in this case no disturbance records directories will be requested (even not from other protection equipment)!
à this behavior is as defined because SICAM DISTO will initiate a request for disturbance records overview
in case of successful/failed disturbance record transmission via positive / negative confirmation by
SICAM DISTO.
- the request for the disturbance record overview will be sent as broadcast (send/no reply) for each function type with
station number 255.
Note.: - function type of all connected protection devices (e.g.: function type 128 = “distance protection“,
160 = “overcurrent protection“, …) will be learned from list of recorded disturbance records if sent spontaneous
or during general interrogation and with min. 1x disturbance record included.
- if only protection devices are connected without recorded disturbance record then no function code will be
learned and no cyclic request for disturbance records overview will be started.
- a correct disturbance record container address must be parameterized in SIP message address conversion.
with 103Mx0: in transmit-and receive direction (Containtertype_Rec and Containertype_Tra).
with VDEZ01: in receive direction.
- the “virtual station address” used for transmission of disturbance records container must be added in topology and
(if used) in data flow filters (pass through filters) but this “virtual station address” must not included in the
station definition.
- a disturbance records overview (also empty directories) will be always sent to SICAM DISTO.

DC0-023-2.12, Edition 06.2017
IEC 60870-5-103 Communication

Protocol Element [Master] SICAM DISTO
Services
… cyclic request of
list of recorded disturbances
updated list of recorded

disturbances from protection device list of recorde
d distu rbance
s
(spontan or requested) (ASDU=23)
file ready for transmission
select file and

ction or faul
t start transmission of selected
Order: sele
(ASDU =24) disturbance record
ready for tran
smission of
disturbance
(ASDU =26) data
data
disturb ance
abortio n of
request or (ASDU =24)
transmission
ready for tran
smission of tag
(ASDU=28) s
ion
tag transmiss
abortion of
request or
(ASDU=24)
transmission
of init ial status tag
s (ASDU =29
transmission of tags )
transmission
of tags (ASDU=
29)
end of transmi
ssion of tags
(ASDU =31 )
negative
e positive or
acknowledg
(ASDU=25)
ready for tran

transmission of disturbance data
smisssion of
1st channel the
(ASDU=27)
of transm ission of
abortion
request or DU=24)
a channel (AS
disturbance val
ues of request
ed channel
(ASDU=30)
disturbance valu
es of requeste
d channel
(ASDU=30)
end of transm
ission of 1st
channel
(AS DU=31)
itiv e or negative
e pos
acknowledg )
(ASDU=25
ready for tran

transmission of channels smisssion of
the
2nd channe
l (ASDU=27)
n of transmission of
abortio
request or l (ASDU=24
)
2nd channe
of following
transmission
abortion of
request or DU=24)
channels (AS
end of transmi
ssion of last
channel (AS
DU=31)
negative
e positive or
acknowledg
(ASDU=25)
end of transmi
ssion of disturb
ance data
(AS DU=31)
file transmission completed
negative
e positive or
acknowledg
(ASDU=25)
updated list of recorded

disturbances from protection device updated list
of recorded
disturbances
(spontan or requested) (ASDU=23) updated list of recorded
disturbances
… cyclic request of
list of recorded disturbances
data requested by protocol element
data transmitted from protection equipment
File Transfer between Protocol Element and SICAM DISTO

Edition 06.2017, DC0-023-2.12
Segmentation
transmitted.
Longer parameter messages from REYDISP (max. 256 bytes) are thus to be transmitted in
several part segments and grouped together again before transmission/processing. With
data!
User data container <TI=142> for transmission of disturbance records
27 26 25 24 23 22 21 20
1 variable structure qualifier
Originator address
CASDU1
CASDU2
IOA1
IOA2
IOA3
: : : : : : : :
: : : : : : : : 7 octets dual time in CP56Time2a
format
: : : : : : : :

(1703 standard format)
45 UEK = 45
S=1 I=0 Status = 0x02
1 - 255 Number of bytes IEC 60870-5-103

message + segment info 2)
R Number of segments Segment number Segment information
TI Message data (0)

IEC 60870-5-103 Format
: : : : : : : : :
: : : : : : : : :
: : : : : : : : :
Message data (n)

IEC 60870-5-103 Format
max. 50 Bytes
2) Length of the user data from the field segment information up to the last byte of the message data
(n)
Note:

DC0-023-2.12, Edition 06.2017

CASDU1 = LSB of the CASDU CASDU = CASDU of the remote terminal unit
CASDU2 = MSB of the CASDU CASDU = CASDU of the remote terminal unit
IOA1
IOA2
IOA3
Time
Message type = 128
octets
Number of bytes Number of bytes for message data incl. segmentation field
Segmentation field
Number of segments Total number of segments
Segment number Current number of the transmitted segment
Direction bit (R) 0 = control direction (SICAM DISTO ð PRE)
1 = monitoring direction (PRE ð SICAM DISTO)

Edition 06.2017, DC0-023-2.12
5.2.8.2 Transfer of Disturbance Records to IEC 60870-5-101/104 Systems
Disturbance records (fault data) from protection equipment can be transmitted from the
protocol element of the master station to a central control system according to
IEC 60870-5-101/104 "Transmission of Files in Monitoring Direction (disturbance record
transmission of a protective device)". In the control system the disturbance records are
displayed for evaluation and saved to data carrier.
After the order to transmit the fault data by the higher-level master station has taken place, the
selected file is read out from the protective device by the protocol element of the master
station according to IEC 60870-5-103 and buffered in the memory of the protocol element.
After the transmission of the file from the protective device has concluded, this is transmitted
to the higher-level master station according to IEC 60870-5-101/104 "Transfer of Files in
Monitoring Direction (disturbance record transmission of a protective device)". The file is only
deleted in the protective device after the complete transmission of the file to the higher-level
master station.
The protocol element only supports the transmission of one file at one time.
For the transmission of the file to the higher-level master station, the corresponding IEC
60870-5-101/104 type identifications are processed or generated by the protocol element.
SICAM RTUs internal, presently IEC 60870-5-101/104 messages for the transmission of files
can only be transported with a maximum length of 200 bytes (a SICAM RTUs internal
"Segmentation" of these messages is presently not yet supported). For the transmission to the
higher-level control system, if necessary the message length can be parameterized with the
parameter advanced parameters | file transfer | Maximum message length for
one segment and thus be set "shorter" (concerns "Segment" and "File Directory").
IEC 60870-5-101/104 Messages in Control Direction for the Transmission of Files

<TI=122> File directory interrogation, file selection, file interrogation, section interrogation
<TI=124> File confirmation, section confirmation
IEC 60870-5-101/104 Messages in Monitoring Direction for the Transmission of Files

<TI=120> File ready
<TI=121> Section ready
<TI=123> Last section, last segment
<TI=125> Segment
<TI=126> File directory
The assignment of the IEC 60870-5-101/104 message address for the spontaneous
information object "disturbance record container" is carried out in the OPM II in the master
station in the process-technical parameterization in transmit direction (to SICAM DISTO) with
the category firmware / Tra_container and in receive direction (from SICAM_DISTO) with the
category firmware / Rec_container (container type = disturbance data container).
For each single protective device, the address for the sub-directory and the address for each
disturbance record are to be parameterized in the process technique.

DC0-023-2.12, Edition 06.2017
The protocol element monitors a running transmission of a file both in the direction of the
higher-level master station as well as in the direction of the protective device. A failure during
a running transmission of a file is detected by the protocol element by means of a monitoring
time (Timeout). With the parameter advanced parameters | file transfer | Timeout
for filetransfer this monitoring time can be parameterized.
With a failure of a running transmission, the disturbance file stored in the memory of the
protocol element is deleted and the current file directory transmitted to the higher-level master
station. Since the disturbance file is only deleted in the protective device after successful
transmission to the higher-level master station, in the event of an error this can be transmitted
again.
The spontaneous transmission of the file directory can be deactivated with the parameter
advanced parameters | file transfer | spontaneous transmission of
directory list. If the spontaneous transmission is deactivated, the higher-level master
station must request the transmission of the file directory.
For the transmission of disturbance files to the higher-level master station, the messages of
several protective devices can be used with the same CASDU or also per protective device
with one unambiguous CASDU.

Edition 06.2017, DC0-023-2.12
5.3 Transfer of Parameters for Reyrolle Protection

Equipment
If digital protective devices from the firm Reyrolle are used in combination with a control centre
system SICAM 230, REYDISP – the Engineering Tool for Reyrolle Protective Devices – can
be implemented directly on the control centre system SICAM 230 "Embedded REYDISP".
The transfer of parameters from/to Reyrolle protection equipment is controlled by REYDISP.

REYDISP is thereby used on the control centre system (SICAM 230, SAT 250 SCALA) under
Windows. Parameters are transmitted from REYDISP to the protection equipment in the
private range of IEC 60870-5-103.
The data transmission between REYDISP and the protocol element to which the protection
equipment are connected, is carried out in the System SICAM RTUs with the user data
containers provided for this purpose. REYDISP does not require its own interface to
SICAM RTUs – the communication takes place over the interface of the control centre system
(REYDISP is coupled to the software of the control centre system over a software interface).
The protocol element itself performs no special sequences for the transmission of parameters.
All IEC 60870-5-103 message formats necessary for the transfer of parameters from/to
Reyrolle protection equipment are transmitted from the protocol element of the master station
between REYDISP and the protocol element of the master function in a user data container
defined for SICAM RTUs in the private range of IEC 60870-5-101/104. Then the user data
container is not transmitted to the protection equipment, rather the IEC 60870-5-103 message
format contained in the message data of the user data container.
identification <TI=142> in the private range of IEC 104-5-104. SICAM RTUs internal, several
modes are provided for the use of the user data container. For the transmission of
parameters, the user data container is used with message type = 132 (=REYDISP parameter
container).
All data sent from REYDISP via user data container are transmitted to the remote terminal
units by the protocol firmware on conclusion of the running message transmission sequence.
User data containers to non-parameterized remote terminal units are not transmitted by the
protocol firmware and are discarded! With station-selective addressing, in addition the reply
from the protective device following this is transmitted back to REYDISP via user data
container. In addition, all message formats received from the protective devices with unknown
type identification are also passed on to REYDISP via user data container.
For each interface with protection equipment connected, an unambiguous address must be
parameterized for a user data container in transmit and receive direction. The assignment of
the message address for the spontaneous information object "User data container" is carried
out in the OPM II with the category firmware / Trans_container and the category firmware /
Rec_container The "container type" has to be set to "Reydisp container" with the parameter
Containtertype_Rec and the parameter Containtertype_Tra. With the parameterization
of the message addresses, the transfer of parameters to REYDISP is also activated.
In SICAM RTUs the addresses of all user data containers for the transfer of disturbance
records are to be entered in the data flow filter. In Ax 1703 the addresses of the user data
containers are to be entered in the corresponding Ax 1703-PRE detailed routings PDS (QID-
ST = 254 ... SSE as source).

DC0-023-2.12, Edition 06.2017
Segmentation
transmitted.
Longer parameter messages from REYDISP (max. 256 bytes) are thus to be transmitted in
several part segments and grouped together again before transmission/processing. With
User data container <TI=142> "REYDISP parameter container"
27 26 25 24 23 22 21 20
T P/N 3 Cause of transmission
0 Originator address
CASDU1
CASDU2
IOA1
IOA2
IOA3
: : : : : : : :
: : : : : : : : 7 octets dual time in CP56Time2a
: : : : : : : : format
Length of the user data part in bytes *)

("REYDISP parameter container")
DIR Number of segments Segment number Segment information
Link Address (station number)
Container type
Message data (0)
: : : : : : : : :
: : : : : : : :
: : : : : : : : :
Message data (n) ... max. 180 Bytes
*) Number of bytes from segment information up to and including the last byte of the message data
Note:

Edition 06.2017, DC0-023-2.12

CASDU1 = LSB of the CASDU CASDU = CASDU of the remote terminal unit
CASDU2 = MSB of the CASDU CASDU = CASDU of the remote terminal unit
IOA1
IOA2
IOA3
03 .. spontaneous ... in control direction and monitoring direction
Time
7 octets dual time
Message type = 132 REYDISP parameter container
octets
Segmentation field
Number of segments Total number of segments
Segment number Current number of the transmitted segment
Direction bit (DIR) 0 = control direction (REYDISP ð PRE)
1 = monitoring direction (PRE ð REYDISP)
Link address Station number of the protection equipment
Container type 0 = "IEC 60870-5-103" message
1 = "IEC 60870-5-1/FT1.2" message with fixed block length
2 = "IEC 60870-5-1/FT1.2" single character
Container type "1" IEC 60870-5-1/FT1.2 "Message with fixed block length"
27 26 25 24 23 22 21 20
DIR Number of segments Segment number = 1 Segment information
=1
1 Container type
10H Start character
1 FKT-Code = 9 *) Control field
Link address (0-254) Station address of the protection

equipment
Checksum
16H Stop character
*) For the transparent transmission of IEC 60870-5-101/FT1.2 message formats, presently only
function code < FKT = 9 > "Request Status of Link" is supported!

DC0-023-2.12, Edition 06.2017
Container type "0" IEC 60870-5-103 message "Message with variable block length"
27 26 25 24 23 22 21 20
DIR Number of segments Segment number Segment information
0 Container type
Type identification (253, 254, 255) IEC 60870-5-103 message format *)

message data (0)
SQ variable structure qualifier
T P/N Cause of transmission
CASDU1
Function type
Information number
: : : : : : : : :
Message data (n)
max. 180 bytes
*) The IEC 60870-5-101, IEC 60870-5-103 frame is not transmitted in the REYDISP parameter
container; this is regenerated by the protocol element during transmission.
Control direction:
<TI=254> REYDISP parameter frames
<TI=255> REYDISP parameter "last frame"
Monitoring direction:
<TI=253> REYDISP termination of private data response frame
<TI=254> REYDISP parameter frames
<TI=255> REYDISP parameter "last frame"
Container type "2" IEC 60870-5-1/FT1.2 "Single character"
27 26 25 24 23 22 21 20
DIR Number of segments Segment number = 1 Segment information
=1
2 Container type *)
E5H Single character
*) The transparent transmission of IEC 60870-5-101/FT1.2 message formats for single character is
only supported in monitoring direction (SICAM RTUs ð REYDISP)!

Edition 06.2017, DC0-023-2.12

Facilities
facility.
After the transmission of broadcast messages an extra pause can be inserted regardless of
the transmission facility used. This pause is required for remote terminal units of third-party
manufacturers, if these can only process further messages after a transmission pause
following the reception of BROADCAST-messages.
The pause after broadcast messages can be set in the master station with the parameter
advanced parameters | advanced time settings | pause time after broadcast
message (tp_bc) and the parameter advanced parameters | advanced time
settings | pause time after broadcast message "time base" (tp_bc).
If the pause time is set to "0", a minimum pause of 33 bit is maintained by the protocol
element.
Apart from this a transmission facility that can be freely defined by the user can be selected,
for which all available parameters can be individually set. This is then necessary if
be used for predefined transmission facilities.
For the selection of the freely definable transmission facility the parameter Common
settings | interface modem is to be set to "freely definable". Only after that are all
supported parameters displayed and can be parameterized with the required values (see
Table with Default Parameters for Transmission Facilities).

DC0-023-2.12, Edition 06.2017
Parameter
Ÿ Common settings | asynchron/isochron
Ÿ Common settings | source for receive-/transmit clock (only for "Isochronous")
Ÿ Common settings | free defineable interface modem | pause time (tp),
Ÿ Common settings | free defineable interface modem | pause time "time base" (tp)
Ÿ Common settings | free defineable interface modem | set up time (tv),
Ÿ Common settings | free defineable interface modem | set up time "time base"
(tv)
Ÿ Common settings | free defineable interface modem | run-out time (tn),
Ÿ Common settings | free defineable interface modem | run-out time "time base"
(tn)
message (tp_bc),
message "time base" (tp_bc),
Ÿ Common settings | free defineable interface modem | DCD handling
Ÿ Common settings | free defineable interface modem | bounce suppression time
(tbounce)
Ÿ Common settings | free defineable interface modem | disable time (tdis),
Ÿ Common settings | free defineable interface modem | disable time "time base"
(tdis)
Ÿ Common settings | free defineable interface modem | stability monitoring time
(tstab)
Ÿ Common settings | free defineable interface modem | continuous level monitoring
time (tcl)
Ÿ Common settings | free defineable interface modem | Transmission delay if
countinous level (tcldly)
Ÿ Common settings | free defineable interface modem | Send clock synchronization
command to each station selective
[SM-0551, SM-2551 only]
[SM-0551, SM-2551 only]

Edition 06.2017, DC0-023-2.12
the DSR signal with corresponding parameter setting.
ATTENTION:
be observed!
Parameter "Configuring for CM082x" [only SM-0551, SM-2551]
If an optical transformer of the type CM082x is used as external transmission facility, then the
Configuration for CM-082x must be set when using a patch plug of the type CM2860.
Parameter
The protocol element can – insofar as the transmission facility makes this signal available
receive-side – evaluate the interface signal DCD and utilize it e.g. for monitoring functions.
When using an optical ring with CM-0821, the status of the optical ring is signaled with the
interface signal DCD. A failure of the optical ring is indicated as a warning by the protocol
element in the diagnostic.
(DCD – active .......... Ring OK; DCD – inactive ........ Warning Ring NOK)

DC0-023-2.12, Edition 06.2017
Default parameters for transmission facilities with 103M00, 103S00 (SM-2541 only)
Transmission facility Electrical RTS tp tv tn tp_bc tdis DCD tbs tstab tduration tdelay A_I T
Interface [ms] [ms] [Bit] [ms] *) [ms] [ms] [ms] [sec] [ms]
CM-0821 Ring RS-232 ON 0 1 0 0 0 NO 0 0 0 0 A I
CM-0821 Star, CM-0826, CM-0827, CM-0829 RS-232 ON 0 1 0 0 0 NO 0 0 0 0 A I
Optical (CM-0827) RS-232 ON 0 1 0 0 0 NO 0 0 0 0 A I
Direct connection (RS-485) RS-485 áâ 0 1 0 0 0 NO 0 0 0 0 A I
Freely definable
*) only possible for 103M00 (MASTER)!
Default parameters for transmission facilities with 103Mx0, 103Sx0 (not valid for SM-2541)
Transmission facility Electrical RTS tp tv tn tp_bc tdis DCD tbs tstab tduration tdelay A_I T 5V 1) CM082x 2)
Interface [ms] [ms] [Bit] [ms] 2) [ms] [ms] [ms] [sec] [ms]
CM-0821 Ring RS-232 ON 0 0 0 0 0 NO 0 0 0 0 A I YES NO
CM-0821 Star, CM-0827 RS-232 ON 0 0 0 0 0 NO 0 0 0 0 A I YES NO
Direct connection (RS-485 with CM-0829) RS-232 áâ 0 1 bit 0 0 0 NO 0 0 0 0 A I YES NO
Direct connection (RS-232) 3) RS-232 ON 0 0 0 0 0 NO 0 0 0 0 A I NO NO
Freely definable
1) on the DSR interface line a 5V voltage is output for the supply of the transmission facility
2) only possible for 103MT0 (MASTER)!

Edition 06.2017, DC0-023-2.12
Legend:
Electrical interface............... Parameter electrical interface [only SM-2541]
RTS ..................................... áâ = RTS is switched for the control of the carrier switching of the modem with each message (ON / OFF)
tp .......................................... Parameter Pause time (tp), Parameter Pause time time base (tp)
tv .......................................... Parameter Set-up time (tv), Parameter Set-up time time base (tv)
tn .......................................... Parameter overtravel time (tn), Parameter overtravel time time base (tn)
tp_bc .................................... Parameter Pause time after broadcast message (tp_bc), Parameter Pause time after broadcast message_time base (tp_bc)
tdis ....................................... Parameter blocking time (tdis), Parameter block time time base (tdis)
DCD ..................................... Parameter DCD-assessment
tbs ........................................ Parameter Bounce suppression time (tbs)
tstab ..................................... Parameter Stability monitoring time (tstab)
tduration .............................. Parameter Continuous level monitoring time (tduration)
tdelay ................................... Parameter transmit delay for level (tdelay)
A_I ....................................... Parameter Asynchronous/Isochronous
T........................................... Parameter Bit timing (only with isochronous) (I=internal, E=external)
CM082x ............................... Parameter Configuring for CM082x. Configuring the interface for optical transformer CM-082x with patch plug CM-2860 [only SM-0551, SM-2551]
5V ........................................ Parameter 5V Supply (DSR) [only SM-0551, SM-2551]

DC0-023-2.12, Edition 06.2017
Only for
BROADCAST-
messages
RTS
tverz
tp tv Data transmission tn tp_bc tsw tp tv

Master station
TXD
tPrell tPrell
DCD
tverzRTS
Data transmission
RXD
tsignal tsignal
tdis
t´Prell t´Prell
DCD
t´signal
Remote station
Data transmission
RXD
t'dis
RTS

TXD
t'verz
Œ Œ
tPrell tPrell
tstab tstab
tdauer
Legend:
t verzRTS ……….. Processing time of the transmission system
t p ………….….. Break time (delay, before transmit part is activated with RTS)
t v ………….….. Setup time (transmission delay, after transmit part was activated with RTS)
t n ………….….. Reset time (delayed switch off of the transmit signal level with RTS after message transmission )
t p_bc ……….….. Break time after BROADCAST-Messages
(some systems require a longer break after the transmission of BROADCAST -messages before the next message
can be sent )
t sw ….....….….. Internal processing time
t signal ….....….. Signal propagation delays (dependent from the used transmission facility /transmission path)
t Prell …...….….. Protective time after positive/negative DCD-edge (debounce of DCD)
t stab …...….….. Stability monitoring time – the new DCD-status is only used for message synchronisation after the expiration of the
t dauer …...….….. Continuous level monitoring time
t verz …...….….. Transmission delay – in case of a continuous level a further message transmission will be made at the latest after
t dis …….….….. Disable time of the receiver after message receiption (to supress faulty signs during level monitoring )

Edition 06.2017, DC0-023-2.12

Routes
To increase the availability master stations can be designed redundant.
In the master station one of the can select between the following redundancy controls:
· 1703-Redundancy
· Main-/Backup transmission line with 2 interfaces
In the master station only the redundancy mode "1703-Redundancy" is supported and does
not need to be set with a parameter.
In the remote terminal unit, no function for the support of redundant communications routes is
supported by the protocol element!
control messages.
passive as follows:
· Interface "TRISTATE" – only listening mode

· Interface "ACTIVE" – only listening mode
· Interface "ACTIVE" – interrogation mode
From the redundant – non-active master station, listened messages are passed on in the
system with the identifier "passive" in the status.

DC0-023-2.12, Edition 06.2017
5.5.2 Redundancy Mode "Main-/Backup transmission line with 2

interfaces"
When using the redundancy mode "Main-/Backup transmission line with 2 interfaces" the data
transmission between the master station (controlling station) and the remote terminal units
(controlled stations) takes place via the main transmission line or via the backup transmission
line (stand-by transmission route).
The redundancy mode "Main-/Backup transmission line with 2 interfaces" will be activated on
both protocol elements with the parameter Redundancy | stand-by transmission
route.
In the error free operation mode the protocol element (PRE) for the main transmission line will
control the data transmission from the basic system element (BSE), the data transmission to
the remote terminal units preferred via the main transmission line but also (for monitoring) via
the backup transmission line. Received data from the remote terminal units will also be
handled and transmitted to the basic system element (BSE) by the protocol element for the
main transmission line. The data transmission via the backup transmission line is also
controlled by the protocol element for the main transmission line.
The data exchange between the assigned protocol elements will be done using a tunneling
mechanism.
Schematic configuration for "Main-/Backup Line with 2 interfaces":
Master station
Ax-1703 Basic system element (BSE)
ŒŽ • ŒŽ
103MA0 103MA0
“Main transmission route“ “Backup transmission route“
(SSE = 128 oder 130) (SSE = 129 oder 131)
•• ••
TF TF
TF TF TF TF
Remote station-1 Remote station-2 Remote station-3 Remote station-n
MAIN line (in error free operation mode)
BACKUP line (in error free operation mode)
MAIN line (in case of error) BACKUP line (in case of error)
Legend:

Œ …………….. During failure free operation, data for sending from basic system element (BSE) will be always requested
from the protocol element (PRE) for the main transmission line and sent by the PRE via main transmission line
(default) or backup transmission Line.
During failure free operation, received data will be handled by the protocol element (PRE) for the main
transmission line and sent to basic system element (BSE).
• …………….. During failure free operation, station polling or data messages will be sent preferred via the main transmission line
but also in certain time intervals via the backup transmission line (but not double)
Ž …………….. If the protocol element for main transmission line is available , failed remote stations will be signaled to the basic
system element (BSE) always by the protocol element for the main transmission line .
• …………….. The sending via the 2nd Interface (main-/backup transmission line) will be done using internal
protocol element control message without routing by parameterization (tunneling).
• …………….. In case of error (break of communication line), the communication with the remote stations will be done using
Main- and Backup Line.
…………….. Example for break of communication line and allocation of the remote stations accessible via the main
transmission line and accessible via the backup transmission line .

Edition 06.2017, DC0-023-2.12
A feature of this redundancy mode is supporting a switch over from main transmission line to
backup transmission line without loss of data in case of failure of a transmission modem of the
master station or break of the communication line in a way that enables communication to the
remote stations either via main transmission line or backup transmission line.
In case of failure of a protocol element for main/- or backup line, data can be lost in transmit
direction during redundancy switchover between the assigned protocol elements.
The assignment of the interface for main transmission line and backup transmission line is
defined as follows:
Main Line Backup Line Note

SSE = 128 SSE = 129 The SSEs for Main-/Backup transmission line must be on the same
BSE
SSE = 130 SSE = 131 The SSEs for Main-/Backup transmission line must be on the same
BSE
Legend:
In the error free operation mode the data communication from/to the remote stations will be
done preferred via the main transmission line controlled by the protocol element for the main
st
transmission line. The time synchronization control message will be sent 1 always via the
main transmission line and also via the backup transmission line. The backup transmission
line will be checked cyclically by the protocol element for the main transmission line. During
check cycle the protocol element polls all remote stations once via the backup transmission
line. Data to be sent via the protocol element for backup transmission line will be requested by
the protocol element for backup transmission line and deleted without generating error and
without sending.
If a communication error to a remote station on the communication line (main- or backup

transmission line) will be detected by the protocol element for the main transmission line, an
alarm information will be sent to the basic system (BSE). A remote station will be signaled as
faulty if no communication to this station is possible via main transmission line and backup
transmission line. Faulty remote stations will be polled further in the basic cycle but without
retries. If communication to a faulty remote station is possible again via main- or backup
transmission line the error for this station will be reset.
In case of communication errors from the master station to the remote station, retries will be
sent by the master station via backup transmission line. Following retries will be transmitted
alternately via main transmission line or via backup transmission line.
Both protocol elements perform a cyclic monitoring of the assigned partner protocol element
for this redundancy mode. If the "Active" protocol element fails, the previous "Passive"
protocol element will become "Active" starting with the protocol handling. After redundancy
switch over a general interrogation command will be sent by the now "Active" protocol element
to the remote stations.In this situation, the data transmission will be done only via the own
serial interface of the remaining protocol element. The assigned partner protocol element for
this redundancy mode will be supervised further on. When the failed protocol element is
available again, the redundancy via main-/backup transmission line is also available again.
If the protocol element for backup transmission line is actually "Active" and the protocol
element for main transmission line becomes available again no redundancy switchover will be
initiated and the protocol element for backup transmission line and the protocol element will
be further "Active". Requesting data for sending from the basic system element (BSE),
transmission of data to the remote stations, receiving data from the remote stations and error
handling will be fully controlled by the protocol element for the backup transmission line.

DC0-023-2.12, Edition 06.2017
A cyclic switchover between the assigned protocol elements is not supported!

The "Passive" protocol element will become "Active" only in case of failure of the partner
protocol element.
Notes for parameter settings

· All data to the remote stations must be routed in the master station to both assigned interfaces
· Stand-by transmission line parameter in topology parameters must be deactivated for this redundancy
mode
· The line-by-line redundancy will not be supported by the protocol element in this redundancy mode
· The simulation of measured values during general interrogation must be delayed by the protocol
element using the parameter advanced parameters | Imitation from measured values of
GI
· The simulation of data with NT-bit (not topical) in case of failure must be delayed on the basic system
element.
With the possibility of deactivation of interface by protocol control messages, simple

redundancy solutions can be realized.
With deactivated interface the transmitter of the interface is switched to "tristate" and the data
for transmission are requested from the basic system element and discarded without error
message. Received messages are discarded and not passed on to the basic system element.
The activation/deactivation of the interface takes place through PRE control messages.
With function enabled with the parameter Redundancy | interface deactivation the
interface is deactivated after startup of the protocol element.
With deactivation of the interface a possibly present failure of the interface is reset if no
"listening mode (failure monitoring time)" is parameterized.
With activation of the interface, a general interrogation message is transmitted to the remote
station by the protocol element.
With deactivated interface, no monitoring of the interface takes place!

Edition 06.2017, DC0-023-2.12
Data in receive direction are converted by the protocol element from the message format on
the transmission line to a SICAM RTUs internal IEC 60870-5-101/104 format and transferred
to the basic system element.
The protocol element supports the following modes for the message conversion:
Message Conversion Mode Communication Protocol to the Protection Equipment Z U

IEC 60870-5-101 ó IEC 60870-5-103 - Transmission procedure: IEC 60870-5-103 ü ü
- Message formats: IEC 60870-5-103
IEC 60870-5-101 ó IEC 60870-5-101 - Transmission procedure: IEC 60870-5-101 - ü
- Message formats: IEC 60870-5-101
IEC 60870-5-101 ó IEC 60870-5-103 - Data communication control: IEC 60870-5-103 ü ü
(101) "Container Mode" - Message formats: IEC 60870-5-101 (Transparent-Mode)
IEC 60870-5-101 messages are transmitted in IEC 60870-5-103
container messages (in the private range)
... with SICAM RTUs configurations with BC 1703 the conversion
of IEC 60870-5-101 ð IEC 60870-5-103 ð IEC 60870-5-101
can be omitted.
Z Master station
U Remote terminal unit (protection equipment)
The mode for the message conversion (and also for the transmission procedure) can be set in
the remote terminal unit with the parameter Common settings | operating mode of
the interface. In the master station no parameter for this is provided, for IEC 60870-5-101
the corresponding protocol firmware for multi-point traffic is to be implemented as master
station.
The assignment of the message address for the spontaneous information objects with
message conversion mode "IEC 60870-5-101 ó IEC 60870-5-103" is carried out in the OPM
II with the SIP-Message Address Conversion.

DC0-023-2.12, Edition 06.2017
5.6.1 Message Conversion IEC 60870-5-101 <-> IEC 60870-5-103
Data in control direction are transferred from the basic system element to the protocol element
in the SICAM RTUs internal IEC 60870-5-101/104 format. These are converted by the
protocol element to the IEC 60870-5-103 message format on the line and transmitted
Data in monitoring direction are received by the protocol element depending on the
transmission procedure according to IEC 60870-5-103 and converted by the protocol element
to the internal IEC 60870-5-101-/104 format and then passed on to the basic system element.
The supported functionality (Interoperability) is evident in the document SICAM RTUs

Interoperability IEC 60870-5-103 (DC0-025-1) or in the document Ax 1703 Interoperability
IEC 60870-5-103 (DA0-072-1) respectively.
Note:
Generic data is only limitedly supported!
The parameterization of the address conversion from IEC 60870-5-101 ó IEC 60870-5-103
address and message format takes place with the "SIP-Message Address Conversion".
IEC 60870-5-101/104 ð ï IEC 60870-5-103

Station No. SICAM RTUs internal station number Link address SICAM RTUs internal station number (0-99)
(0-99)
CASDU1 CASDU
CASDU2 CASDU Station address of the protection equipment
IOA1 IOA FUN Function type
IOA2 INF Information number
IOA3
TI Type identification *) TI Function type (type identification) 1)
diverse Additional info per category
*) see message conversion in transmit/receive direction

Edition 06.2017, DC0-023-2.12
Message conversion in control direction (public range of IEC 60870-5-103)
IEC 60870-5-101/104 IEC 60870-5-103 Z U

--- --- <TI=6> Time synchronization 1) ü ü
--- General interrogation command <TI=7> General interrogation command ü ü
(SICAM RTUs internal)
<TI=50> Setpoint command, short floating <TI=10> Generic data (setpoint command) ü -
point number
<TI=45> Single command <TI=20> General command ü ü
<TI=46> Double command
<TI=47> Regulating step command <TI=20> General command ü -
--- General interrogation command <TI=21> Generic command (general interrogation ü -
(SICAM RTUs internal) command) 2)
<TI=142> User data container <TI=24> Order to transmit disturbance data ü ü
"Disturbance record transmission to <TI=25> Acknowledgement for disturbance data ü ü
SICAM DISTO" transmission
<TI=45> Single command --- Reset of the fault locations 3) ü -
<TI=46> Double command (only acts protocol element internal)
<TI=122> Interrogation of file directory, 4) ü
file selection, file interrogation,
section interrogation
<TI=124> file confirmation,
section confirmation
1) Is generated by the protocol element; SICAM RTUs internal, the time management message (function code
156) is used
2) Only general interrogation command for generic data is supported!
3) This command is not transmitted (acts only protocol element internal)
ð The fault locations of the parameterized LINK-Address are reset to the corresponding initial value!
4) Is generated by the protocol element (only 103MA0); "Transmission of Files in Monitoring Direction (disturbance
record transmission of a protective device) according to IEC 60870-5-101/104"
Message conversion in control direction (private range of IEC 60870-5-103)
IEC 60870-5-101/104 IEC 60870-5-103 Z U

<TI=45> single command <TI=232> Command to protective device "ALSTOM" ü -
<TI=46> double command <TI=45,46> Command with SELECT/EXECUTE "ALSTOM" ü -
<TI=45,46> Command without SELECT/EXECUTE "ALSTOM" ü -
<TI=142> User data container <TI=254> REYDISP Parameter Frame ü -
"Parameter messages <TI=255> REYDISP Parameter "Last Frame" ü -
to Reyrolle protective
devices"

DC0-023-2.12, Edition 06.2017
Message conversion in monitoring direction (public range of IEC 60870-5-103)
IEC 60870-5-101/104 1) IEC 60870-5-103 Z U

<TI=30> Single-point information with time tag <TI=1> Time-tagged message ü ü
<TI=31> Double-point information with time tag
<TI=38> Events of protection equipment with time tag
<TI=39> Packed start events of protection equipment
with time tag
<TI=40> Packed output circuit information of protection
equipment with time tag
<TI=30> Single-point information with time tag <TI=2> Time-tagged message with relative ü
<TI=31> Double-point information with time tag time
<TI=36> Measured value, short floating point number
with time tag
<TI=38> Events of protection equipment with time tag
<TI=39> Packed start events of protection equipment
with time tag
<TI=40> Packed output circuit information of protection
equipment with time tag
<TI=34> Measured value, normalized value <TI=3> Measurands I ü ü
with time tag
<TI=35> 5) Measured value, scaled value with time tag
<TI=36> 5) Measured value, short floating point number
with time tag
<TI=34> Measured value, normalized value <TI=4> Real-time measured values with ü ü
with time tag relative time
with time tag
<TI=30> Single-point information with time tag <TI=5> Identification information 2) ü ü
<TI=31> Double-point information with time tag
--- --- <TI=6> Time synchronization, binary ü
information 2)
--- --- <TI=8> General interrogation end 2) ü
<TI=34> Measured value, normalized value with time <TI=9> Measurands II ü ü
tag
with time tag
<TI=36> Measured value, short floating point number <TI=10> Generic data (measured value) 3) ü
with time tag
--- --- <TI=11> Generic identification
<TI=120> File ready 4) <TI=23> Disturbance event overview ü
<TI=121> Section ready <TI=26> Ready to transmit disturbance data ü
<TI=123> Last section, last segment <TI=27> Ready to transmit one channel ü
<TI=125> Segment <TI=28> Ready to transmit marks ü
<TI=126> File directory <TI=29> Transmission of marks ü
<TI=30> Transmission of disturbance ü
<TI=31> values Transmission end ü
<TI=142> User data container <TI=23> Disturbance event overview ü ü

"Disturbance record transmission to SICAM <TI=26> Ready to transmit disturbance data ü ü
DISTO" <TI=27> Ready to transmit one channel ü ü
<TI=28> Ready to transmit marks ü ü
<TI=29> Transmission of marks ü ü
<TI=30> Transmission of disturbance ü ü
<TI=31> values Transmission end ü ü
1) all with time tag format CP56Time2a

2) is generated in the RTU directly by the protocol element!
3) only data in the format GDD [DATATYPE] = 7 (short Real IEEE STD 754) are supported!
4) Is generated by the protocol element (only 103MA0); "Transmission of Files in Monitoring Direction (disturbance
record transmission of a protective device) according to IEC 60870-5-101/104"
5) not supported by protocol element for IEC60870-5-103 slave in SICAM RTUs (103Sx0)

Edition 06.2017, DC0-023-2.12
Message conversion in monitoring direction (private range of IEC 60870-5-103)
IEC 60870-5-101/104 *) IEC 60870-5-103 Z U

<TI=30> Single-point information <TI=33> Real-time information ü
with time tag (SEG protective devices)
<TI=31> Double-point information
with time tag
<TI=30> Single-point information <TI=65> Single-point information with time "ALSTOM" ü
with time tag <TI=66> Single-point information without time "ALSTOM" ü
<TI=30> Single-point information <TI=67> Double-point information with time "ALSTOM" ü
with time tag <TI=68> Double-point information without time "ALSTOM" ü
with time tag
with time tag
<TI=33> Bit string of 32 bits with <TI=71> 32 Bit binary value "ALSTOM" ü
time tag <TI=72>
<TI=34> Measured value, <TI=140> Measured values SIEMENS ü
normalized value with
time tag
<TI=35> Measured value, scaled
value with time tag
<TI=36> Measured value, short
floating point number with
time tag
<TI=36> Measured value, short <TI=204> Measured value short floating point ü
floating point number with (Reinhausen TAPCON 240)
time tag
<TI=36> Measured value, short <TI=205> Measured value 28 Bit ü
floating point number with (SIEMENS Siprotec)
time tag
<TI=37> Integrated totals with time
tag
<TI=142> User data container <TI=253> REYDISP Termination of ü
"Parameter messages to Private Data Response Frame
Reyrolle protective <TI=254> REYDISP Parameter Frame ü
devices" <TI=255> REYDISP Parameter "Last Frame" ü
*) all with time tag format CP56Time2a

DC0-023-2.12, Edition 06.2017
Causes of transmission in control direction
IEC 60870-5-101/103 Master Remote

Station Station
URS Cause of transmission
8 Time synchronization, command ü ü
9 GI-initiation ü ü
19 ALSTOM command <TI:=232> *) ü
20 General command ü ü
31 Disturbance data transmission ü ü
40 Generic write command ü
42 Generic read command
*) only for ALSTOM protection equipment!
Causes of transmission in monitoring direction
IEC 60870-5-101/103 Master Remote

Station Station
URS Cause of transmission
1 spontaneous ü ü
2 cyclic ü ü
3 Reset information FCB ü ü
4 Reset information KE ü ü
5 Startup/restart information ü ü
6 First start information ü
7 Test mode ü ü
8 Time synchronization, binary information ü ü
9 General Interrogation ü ü
10 GI-End information ü ü
11 Local operation
12 Remote operation ü ü
13 Remote operation negative *) ü
20 Return information to remote command positive ü ü
21 Return information to remote command negative ü
31 Disturbance data transmission ü ü
40 Return information to generic write command positive
41 Return information to generic write command negative
42 Generic reading; data valid ü
43 Generic reading; data invalid
44 Confirmation of a generic write command
*) only for ALSTOM protection equipment!

Edition 06.2017, DC0-023-2.12
Type Identification 6: Time Synchronization
The assignment of the IEC 60870-5-103 message address for the spontaneous information object "time synchronization" takes place without parameter setting by the
protocol element of the master station.
The time synchronization is always transmitted "BROADCAST" (Send/no Reply) from the protocol element of the master station to the protection equipment spontaneously
with a change of the time and cyclic in a parameter-settable grid.
Elements of the Message (SICAM RTUs internal) BSE ð PRE Elements of the Message (IEC 60870-5-103) ZðU
Function code = 156 Time management (SICAM RTUs internal) Type identification
Information code = 0 .. Clock not evaluated TI 6 .. Time synchronization
synchronization
Message address
CASDU = 255.. Station address of the
protection equipment (BROADCAST)
FUN = 255 .. Global function type
INF = 0 .. Information number System function (time synchronization)
Cause of transmission (COT)
COT = 8 .. Time synchronization
Time Time
CP56Time2a ... Dual time with 7 octets With this SICAM RTUs internal message, CP56Time2a ... Dual time with 7 octets In the message the time of the 1st bit is
the internal clock of the protocol element is entered on the line
set and a time synchronization of the
protection equipment connected in
initiated.

DC0-023-2.12, Edition 06.2017
Type Identification 7: General Interrogation Command
The assignment of the IEC 60870-5-103 message address for the spontaneous information object "general interrogation command" takes place without parameter setting by
the protocol element of the master station. The general interrogation command is transmitted from the protocol element of the master station selectively for every CASDU
per Link-Address (station address of the protection equipment).
Function code = 155 General interrogation request Type identification
Information code = 1 .. Source-GI request (SICAM RTUs internal) not evaluated TI 7 .. General interrogation command
Message address Message address
CASDU .. Station address of the protection CASDU .. Station address of the
equipment protection equipment
FUN = 255 .. Global function type
INF = 0 .. Information number System function
Cause of transmission (COT) Cause of transmission (COT)
<6> .. activation COT = 9 .. General interrogation initiation
qualifier of interrogation not evaluated
Cycle number (SCN)
SCN = 0-255 .. Cycle number Beginning from 0, the cycle number is
increased by 1 with each transmitted
general interrogation command (per
protective device).
All data of a protective device subject to GI
that are transmitted following a general
interrogation command are transmitted with
the cycle number of the general
Note:
The cycle number is not evaluated in the
master station.
Note:
The IEC 60870-5-103 message in monitoring direction "General interrogation End" is not evaluated by the protocol element of the master station!
ACTCON and ACTTERM for general interrogation request are not emulated by the protocol element of the master station!

Edition 06.2017, DC0-023-2.12
Type identification 20: General Command

Type identification 45, 46, 232: General Command (in the private range)
The assignment of the message address for the spontaneous information object "general command" is carried out in the OPM II in the master station with the category
firmware / Trans_command and in the remote terminal unit with the category firmware / Rec_command.
Elements of the Message (IEC 60870-5-101/104) BSE ó PRE Elements of the Message (IEC 60870-5-103) ZðU
Type identification Type identification 1)
TI 45 .. single command TI 20 ... General command
TI 46 .. double command TI 232 ... Command to protective device Private range 2)
TI 45,46 .. Command with SEL / EXE Private range 2)
TI 45,46 .. Command without SEL / EXE Private range 2)
Type identification Type identification 1)

TI 47 .. regulating step command TI 20 .. General command
CASDU (CASDU1, CASDU2) Parameter-settable CASDU .. Station address of the protection Parameter-settable
IOA (IOA1, IOA2, IOA3) Parameter-settable equipment
FUN .. Function type Parameter-settable
INF .. Information number Parameter-settable
Return information identification (RII) Parameter-settable
<6> .. Activation <20> .. general command
<7> .. Confirmation of activation PREð BSE (after reception of RM or TIO) <19> .. Only for ALSTOM <TI=232> 2)
<8> .. Abortion of activation not supported
<9> .. Confirmation of the abortion of not supported
activation
<10> .. Termination of activation PREð BSE (after reception of RM or TIO)
P/N .. positive/negative confirmation PREð BSE (after reception of RM or TIO)
T .. Test not evaluated
Originator address see Setting Control Location!
Qualifier of command Qualifier of command Only for <TI=45>, <TI=46> 2)
QU <0> .. no additional definitions QU <0> .. no additional definitions
QU <1> .. Short command execution time QU <1> .. Short command execution time
QU <2> .. Long command execution time QU <2> .. Long command execution time
QU <3> .. persistent command Not supported QU <3> .. persistent command
S/E <0> .. execute only for IEC 60870-5-103 <TI=45,46> 1) S/E <0> .. execute
S/E <1> ..select S/E <1> .. select
Single command Double command Double command (DCO)
(SCO) (DCO) <0> .. Not allowed
<0> .. OFF <0> .. not allowed <1> .. OFF
<1> .. ON <1> .. OFF <2> .. ON
<2> .. ON <3> .. not permitted
<3> .. not allowed
1) TI is defined with the additional info in the OPM (see Special Functions)
2) Command message in the private range of IEC 60870-5-103 to "ALSTOM" protection equipment (qualifier of command as for IEC 60870-5-101) ß only supported by master station!

DC0-023-2.12, Edition 06.2017
Special functions (SIP-message address conversion of the master station):
· Additional info
<0> = General command <TI=20>according to IEC 60870-5-103
<1> = General command <TI=232>
to ALSTOM protective device in the "Private range" (COT=19)
<2> = General command <TI=45,46>
to ALSTOM protective device in the "Private range" with SELECT / EXECUTE
<3> = General command <TI=45,46>
to ALSTOM protective device in the "Private range" without SELECT / EXECUTE
<4> = General command <TI=20>according to IEC 60870-5-103 to remote station (protection equipment) and emulation of
SELECT / EXECUTE handling according IEC 60870-5-101/-104 to basic system element (BSE)
The max. delay between SELECT / EXECUTE will be monitored by the protocol element and the time can be configured with the parameter advanced
parameters | advanced time settings | Timeout Execute.
<5> = General command <TI=232> to ALSTOM protective device in the "Private range" (COT=20)
· Cross-over (exchange) of the double command states ON ó OFF during the message conversion IEC 60870-5-101 ð IEC 60870-5-103
· Return information monitoring time
The master station monitors whether the return information for a command is received within a settable time from the remote terminal unit.
With IEC 60870-5-103, the return information for the command is always transmitted with the address of the command.
Emulation of Condition
ACTCON+ - Return information is received from the protection equipment with COT =<12> (=remote operation) or
COT=<20> (=positive acknowledgement of command) or return information monitoring time = "0"
ð ACTCON+ emulate from PRE to BSE
ACTCON- - No return information received (return information monitoring time expired)
- Return information is received from the protection equipment with COT=<21>
(=negative acknowledgement of command)
ð ACTCON- emulate from PRE to BSE
ACTTERM+ - Return information is received from the protection equipment with COT=<20>
(=positive acknowledgement of command) or return information monitoring time = "0"
ð ACTTERM+ emulate from PRE to BSE
ACTTERM- - No return information received (return information monitoring timeout) but
ACTCON+ already transferred
- Return information is received from the protection equipment with COT=<13> (=remote operation negative)
ð ACTTERM- emulate from PRE to BSE
Legend:


Edition 06.2017, DC0-023-2.12
Type Identification 10: Generic Data (Setpoint Command)
The assignment of the message address for the spontaneous information object "Generic Data (Setpoint Command)" is carried out in the OPM II with the category firmware /
Trans_generic_setpoint command(GDD=7).
Elements of the Message (IEC 60870-5-101/104) BSE ð PRE Elements of the Message (IEC 60870-5-103) ZðU
Type identification Type identification
TI 50 .. Setpoint command, short floating TI 10 .. Generic data Setpoint Command
point number
CASDU (CASDU1, CASDU2) Parameter-settable CASDU .. Station address of the Parameter-settable
IOA (IOA1, IOA2, IOA3) Parameter-settable protection equipment
FUN = 254 .. Generic function type
INF = 250 .. Information number Generic function
<6> .. Activation <40> .. generic write command
<7> .. Confirmation of activation PREðBSE (immediately by PRE)
<8> .. Abortion of activation not supported
<9> .. Confirmation of the abortion of not supported
activation
<10> .. Termination of activation not supported
P/N .. positive/negative confirmation positive
Originator address not evaluated
Generic data description (data record)
RII = 0 .. Return information identification Not supported
NGD = 1 .. Number of generic data records
GIN .. Generic identification number parameter-settable GIN [ group, entry ]
KOD = 1 .. Actual Value
GDD [DATATYPE] = 7 .. IEEE STD 754 short Real IEEE STD 754
GDD [DATASIZE] = 4 .. 4 octets
GDD [NUMBER] = 1 Number of data elements
GDD [CONT] =0 No following data elements
Data Generic data
short floating point number IEEE STD 754 32 Bit floating point value GID = short floating point number 32 Bit floating point value
(IEEE STD 754)
Identifier for setpoint command (QOS)
QL <0> .. not defined Not supported
QL <1..127> Not supported
S/E <0> .. execute Not supported
S/E <1> ..select Not supported

DC0-023-2.12, Edition 06.2017
Type Identification 21: Generic Command (general interrogation command for generic data)
The assignment of the message address for the spontaneous information object "Generic command (general interrogation command for generic data)" is carried out without
parameter setting by the protocol element of the master station.
The general interrogation command is transmitted selectively for every CASDU per Link-Address (station address of the protection equipment).
Function code = 155 General interrogation request Type identification
Information code = 1 .. Source-GI request (SICAM RTUs internal) not evaluated TI 21 .. Generic command General interrogation command for generic
data
CASDU .. Station address of the protection CASDU .. Station address of the
equipment protection equipment
FUN = 254 .. Generic function type
INF = 245 .. Information number Generic function
<6> .. Activation COT = 9 .. General interrogation initiation
T .. Test Not evaluated
P/N .. positive/negative confirmation Not evaluated
Originator address Not evaluated
qualifier of interrogation not evaluated Generic data description (data record)
RII = 0 .. Return information identification Beginning from 0, the cycle number is
(=cycle number) increased by 1 with each transmitted
general interrogation command (per
protective device).
All data of a protective device subject to GI
that are transmitted following a general
interrogation command are transmitted with
the cycle number of the general
Note:
The cycle number is not evaluated in the
master station.
NOG = 0 .. Number of generic identifications
Note:
ACTCON and ACTTERM for general interrogation request are not emulated by the protocol element of the master station!

Edition 06.2017, DC0-023-2.12
Type Identification 253: REYDISP termination of Private Data Response Frame

Type Identification 254: REYDISP Parameter Frame
Type Identification 255: REYDISP Parameter "Last Frame"
The assignment of the message address for the spontaneous information object "user data container" is carried out in the OPM II with the category firmware /
Trans_container and the category firmware / Rec_container. The parameter Containtertype_Rec and the parameter Containertype_Tra has to be set to "Reydisp
container". (See also section "Transmission of Parameters for Reyrolle Protection Equipment")
Elements of the Message (IEC 60870-5-101/104) BSE ó PRE Elements of the Message (IEC 60870-5-103) ZóU
TI 142 .. User data container User data container for TI 253 .. REYDISP termination of Monitoring direction
REYDISP parameter data Private Data Response Frame
TI 254 .. REYDISP Parameter Frame control/monitoring direction
TI 255 .. REYDISP Parameter "Last Frame" control/monitoring direction
CASDU (CASDU1, CASDU2) Parameter-settable CASDU .. Station address of the Parameter-settable
IOA (IOA1, IOA2, IOA3) Parameter-settable protection equipment
FUN = xx .. is not evaluated! *)
INF = xx .. is not evaluated! *)
<3> .. spontaneous COT = xx .. is not evaluated! 1)
T .. Test Not evaluated
P/N .. positive/negative confirmation Not evaluated
Originator address Not evaluated
User data part IEC 60870-5-103 message formats for the
transmission of REYDISP parameter data
is transmitted in the user data part of the
user data container.
*) these items of information are copied 1:1 from the user data container into IEC 60870-5-103 without assessment

DC0-023-2.12, Edition 06.2017
Type Identification 23: Disturbance Event Overview

Type Identification 24: Order to Transmit Disturbance Data
Type Identification 25: Acknowledgement for Disturbance Data Transmission
Type Identification 26: Ready to Transmit Disturbance Data
Type Identification 27: Ready to Transmit One Channel
Type Identification 28: Ready to Transmit Marks
Type Identification 29: Transmission of Marks
Type Identification 30: Transmission of Disturbance Values
Type Identification 31: Transmission End
The assignment of the message address for the spontaneous information object "user data container" is carried out in the OPM II with the category firmware /
Trans_Container and the category firmware / Rec_Container. The parameter Containter-type_Rec and the parameter Container-type_Tra has to be set to "disturb.
data container". (See also in section "File Transfer")
Elements of the Message (IEC 60870-5-101/104) BSE ó PRE Elements of the Message (IEC 60870-5-103) ZóU
TI 142 .. User data container User data container for disturbance record TI 23 .. Disturbance event overview Monitoring direction
transmission TI 24 .. Order to Transmit Disturbance Data Control direction
TI 25 .. Acknowledgement for Disturbance Control direction
Data Transmission Monitoring direction
TI 26 .. Ready to Transmit Disturbance Data Monitoring direction
TI 27 .. Ready to Transmit One Channel Monitoring direction
TI 28 .. Ready to Transmit Marks Monitoring direction
TI 29 .. Transmission of Marks Monitoring direction
TI 30 .. Transmission of Disturbance Values Monitoring direction
TI 31 .. Transmission End
CASDU (CASDU1, CASDU2) Parameter-settable CASDU .. Station address of the protection Parameter-settable
IOA (IOA1, IOA2, IOA3) Parameter-settable equipment
FUN = 255 .. Only for TI 24 2)
INF = 0 … only for TI 24 2)
<3> .. spontaneous in monitoring direction <31> .. only with TI 24 2)
<6> .. Activation in control direction
P/N .. positive/negative confirmation not evaluated
Originator address not evaluated
User data part 1)
1) IEC 60870-5-103 message formats for the transmission of files are transmitted in the user data part of the user data container
2) these items of information only have the specified values with TI 24 – with all other TI's these items of information are copied 1:1 from the user data container into IEC 60870-5-103
without assessment

Edition 06.2017, DC0-023-2.12
Type Identification 1: Time-Tagged Message

Type Identification 2: Time-Tagged Message with Relative Time
The assignment of the message address for the spontaneous information object "binary information" is carried out in the OPM II in the master station with the category
firmware / Rec_binary information and in the remote terminal unit with the category firmware / Trans_binary_information.
Elements of the Message (IEC 60870-5-101/104) BSE ï PRE Elements of the Message (IEC 60870-5-103) ZïU
(all with time tag CP56Time2a) TI 1 .. Time-tagged message
TI 30 .. Single-point information TI 2 .. Time-tagged message with relative
TI 31 .. Double-point information Only for relative time as measured value time 1)
TI 32 .. Measured value, short floating point
number
TI 38 .. Protection event
TI 39 .. Blocked activation of protection
TI 40 .. Blocked triggering of the protection
CASDU (CASDU1, CASDU2) Parameter-settable CASDU .. Common address of ASDU Parameter-settable
IOA (IOA1, IOA2, IOA3) Parameter-settable FUN .. Function type Parameter-settable
Cause of transmission (COT) Cause of transmission (COT) 2)
<3> .. spontaneous <1> .. Spontaneous
<20> .. Interrogated by station <7> .. Test mode 3)
interrogation <9> .. General interrogation
<12> .. Return information, caused by a <11> .. Local operation
local command
<11> .. Return information, cause by a <12> .. Remote operation
remote command
T .. Test
P/N .. positive/negative confirmation Not defined
Originator address
Quality descriptor
BL = 0 .. blocked Not used
SB = 0 .. substituted Not used
NT .. not topical Emulated by the basic system element on
failure of the protocol element or the
remote terminal unit
IV = x .. invalid only TI 39,40
EI = 0 .. Elapsed time Not used
(0/1 = valid/invalid)

DC0-023-2.12, Edition 06.2017
- Double-point information state (DPI) only TI 31 Double-point information (DPI)
- Binary information state (ES) only TI 38
<0> .. undetermined state intermediate position <0> .. not used
<1> .. OFF <1> .. OFF
<2> .. ON <2> .. ON
<3> .. undetermined state faulty position <3> .. not used
Time Time
CP56Time2a ... Dual time with 7 octets CP32Time2a ... Dual time with 4 octets
start events of protection equipment only TI 39
SRD .. start of operation in reverse direction The IEC 60870-5-103 binary information
SIE .. start of operation IE (earth current) state can be assigned one of these binary
SL3 .. start of operation phase L3 informations
SL2 .. start of operation phase L2
SL1 .. start of operation phase L1
GS .. General start of operation
Binary information to the output current of the only TI 40
protection equipment The IEC 60870-5-103 binary information
CL3 .. command to output circuit phase L3 state can be assigned one of these binary
CL2 .. command to output circuit phase L2 information
CL1 .. command to output circuit phase L1
GC .. General command to output circuit
- Measured value, short floating point number only TI 36 (relative time as measured Relative time (CP16Time2a)
- Elapsed time (CP16Time2a) value)
- relay duration time (CP16Time2a) only TI 38
- relay operation time (CP16Time2a) only TI 39
only TI 40
- Measured value, short floating point number only TI 36 Fault number
Additional information (SIN) 4)
1) Binary information with relative time is not supported by SICAM RTUs remote terminal unit!
2) Binary information with other causes of transmission are discarded!
3) For more details see section "Test Mode"
4) Controlling station: not evaluated!
Controlled station: In monitoring direction the additional information (SIN) is used as follows:
Cause of transmission = general interrogation ð SIN = cycle number of the GI-command
Cause of transmission = command acknowledgement ð SIN = return information identification of the command
Cause of transmission = other ð SIN = not used!

Edition 06.2017, DC0-023-2.12
Suggestions for the SIP message address conversion of the master station:
· Type information (selection of the data to be converted from the IEC 60870-5-103 message)
From IEC 60870-5-103 messages in the format "Binary information with time tag", the state of the double-point information can be converted to a IEC
60870-5-101/104 message format. The correct type identification (TI) is to be parameterized for the selected data.
From IEC 60870-5-103 messages in the format "Binary information with relative time", the state of the double-point information or the relative time or the
fault number can be converted to IEC 60870-5-101/104 message format. The correct type identification (TI) is to be parameterized for the selected data. For
every data type selected, a routing record must be entered in the SIP message address conversion.
· Additional info ... binary information type
With additional info "only coming binary information", after the transfer of the received binary information "coming", the binary information "going" is
emulated by the protocol element with the "received time + 10 ms".
· GI-initiation ... Initiation of a general interrogation command on reception of this binary information
· Double-point information assignment
With this function, 2 received single-point information can be converted to one double-point information.
· Note: For both single-point information, the same SICAM RTUs address of the double-point information must be parameterized!
· Intermediate/faulty position suppression_t: (intermediate/faulty position suppression time)
If no intermediate/faulty position suppression time is parameterized, then a received double-point information is transferred immediately to the basic system
element. With intermediate/faulty position suppression time parameterized, a received double-point information with intermediate or faulty position is not
transferred to the basic system element. The double-point information is buffered on the protocol element and an intermediate or faulty state position
suppression is performed. If a valid switching state (ON or OFF) is received during the suppression time, then this double-point information state is
transferred immediately to the basic system element and the intermediate/faulty position suppression handling is terminated. After expiry of the suppression
time, the intermediate/faulty position of the double-point information is transmitted to the basic system element.

DC0-023-2.12, Edition 06.2017
Type Identification 33: Binary Information with Time Tag

Type Identification 65: Single-Point Information
Type Identification 66: Single-Point Information with Time Tag
Type Identification 67: Double-Point Information
Type Identification 68: Double-Point Information with Time Tag
The assignment of the message address for the spontaneous information object "binary information" is carried out in the OPM II in the master station with the category
firmware / Rec_binary information.
(all with time tag CP56Time2a) TI 33 .. Binary information with time tag 1a)
TI 30 .. Single-point information TI 65 .. Binary information without time tag 1b)
TI 31 .. Double-point information TI 66 .. Binary information with time tag 1b)
TI 67 .. Binary information without time tag 1b)
TI 68 .. Binary information with time tag 1b)
1a) Binary information with time tag SEG-protective device – private range!
1b) Binary information with time tag ALSTOM-protective device – private range!

Edition 06.2017, DC0-023-2.12
Type Identification 3: Measurands I

Type Identification 4: Time-Tagged Measurands with Relative Time
Type Identification 3: Measurands II
The assignment of the message address for the spontaneous information object "measured value" in receive direction is carried out in the OPM II in the master station with
the category firmware / Rec_measured value. The assignment of the message address for the spontaneous information object "measured value" in transmit direction is
carried out in the OPM II in the slave station with the category firmware / Trans_measured value.
(all with time tag CP56Time2a) TI 3 .. Measurands I
TI 34 .. Measured value, normalized value TI 4 .. Time-Tagged measured values with fault location
TI 35 .. Measured value, scaled value 1) 4) relative time
TI 36 .. Measured value, short floating point TI 9 .. Measurands II
number 4)
Subvalue … number of the measurand Parameter-settable
in message
<3> .. spontaneous <1> .. spontaneous
<2> .. cyclic
<20> .. interrogated by station <9> .. general interrogation
interrogation
Originator address Not defined

Quality descriptor
BL = 0 .. blocked Not used
SB = 0 .. substituted Not used ER = x .. Error
NT .. not topical NT = ER 2)
<0> .. if NT=0 and IV=0 3)
<1> .. if NT=1 or IV=1 3)
IV = x .. invalid
OV = x .. Overflow
OV = x .. overflow
MEA … Measurand-type Parameter-settable
value 1) converted and scaled 103-measurand 103-measurand <TI:=3,9 only>
value 1) converted and scaled 103-measurand SCL … short circuit location <TI:=4 only> Parameter-settable
- - FAN (fault number) <TI:=4 only> The FAN (=fault number) will be
incremented with each “general trip”
received from BSR à PRE.
- - RET … relative time <TI:=4 only> =0

DC0-023-2.12, Edition 06.2017
1) short-circuit location values that are converted to the IEC 60870-5-101/104 message format "<TI35> measured value, scaled value with time tag", can, if necessary, be multiplied by a
parameter-settable factor in the master station before the conversion; as a result, the places after the decimal point that are otherwise truncated can be shown in the new format; the
factor can be set with the parameter advanced parameters | multiplication factor for fault location value (fract.digit)
2) receive direction Master only
3) transmit direction Slave only
4) not supported by protocol element for IEC60870-5-103 slave in SICAM RTUs (103Sx0)
Special functions (SIP-message address conversion of the master station):
· Type of measured values (selection of the measurand data format in IEC60870-5-103 Message)
<0> = Measurand value from Measurand I or Measurand II
<1> = Measurand value from real-time measurand value with relative time
<2> = relative time from real-time measurand value with relative time
<3> = disturbance record number from real-time measurand value with relative time
Note:
For Type identification 3 (Measurand I) or type identification 9 (Measurand II) or type identification 140 (Siemens measurand values) only Type of measured values =
"0" (Measurand I or Measurand II) is valid.

Edition 06.2017, DC0-023-2.12
5.6.2 Message Conversion IEC 60870-5-101 <-> IEC 60870-5-101
If the IEC 60870-5-103 protocol element in the remote terminal unit is used on an integrated
(local) interface, the transmission protocol can be switched over from IEC 60870-5-103 to IEC
60870-5-101 if required. As a result, no additional configuration of a protocol element is
necessary.
This is only meaningful, if a SICAM RTUs master station is used and all remote terminal units
are also connected with IEC 60870-5-101. In this case, the otherwise necessary message
conversion from IEC 60870-5-103 ó IEC 60870-5-101 can be omitted and the messages are
transferred 1:1 in transmit/receive direction.
The remote terminal unit then behaves like a IEC 60870-5-101 remote terminal unit in multi-
point traffic.
element in the SICAM RTUs internal IEC 60870-5-101/104 format. These are converted by

DC0-023-2.12, Edition 06.2017
5.6.3 Message Conversion IEC 60870-5-101 <-> IEC 60870-5-103 (101)
The transmission protocol IEC 60870-5-103 is implemented on the line. With this operation
mode, all data in IEC 60870-5-101 format between SICAM RTUs master/remote terminal units
are transmitted with a user data container in the private range of IEC 60870-5-103. As a
result, between SICAM RTUs systems, no parameterization of the address conversion IEC
60870-5-101 ó IEC 60870-5-103 is required. The data transmission to protection equipment
(remote terminal units) of other manufacturers is carried out according to IEC 60870-5-103.
Data messages are transmitted from the basic system element in SICAM RTUs internal IEC
60870-5-101/104 message format to the protocol element and transmitted from this 1:1 in a
IEC 60870-5-103 user data container message (in the private range) defined for
SICAM RTUs.
In receive direction, the IEC 60870-5-101 message format is read out from the user data
container and transferred to the basic system element in the SICAM RTUs internal IEC
60870-5-101/104 message format. The operating mode for the message conversion (101-
Mode) is signaled to the master station from the 1703 Bay-Controller with the startup signal.
Notes:
- In the master station and in the remote terminal unit, the IEC-parameters (number of bytes
for COT, CASDU, IOA) must be set identical.
- In the master station (SICAM RTUs), in the receive detailed routing the message conversion
for a binary information (IEC 60870-5-103 à IEC 60870-5-101) must be entered, even if this
is not received due to the parameterized address conversion IEC 60870-5-101 ó
IEC 60870-5-103(101). This "Dummy parameter setting" is presently required due to the
"self-learning data flow" in SICAM RTUs.
IEC 60870-5-103 User Data Container <TI=200>
27 26 25 24 23 22 21 20
Type identification IEC 60870-5-103
SQ 1 variable structure qualifier :
T P/N 1 = spontaneous Cause of transmission :
Z ð U: = 255 Z ï U: = device address CASDU (common address of

ASDU) :
Z ð U: = 178 Z ï U: = 178 FUN (function type) :
Z ð U: = 0 Z ï U: = 0 INF (information address)

IEC 60870-5-103
Type identification IEC 60870-5-101
SQ variable structure qualifier :
T P/N Cause of transmission
Originator address
CASDU1
CASDU2
IOA1
IOA2
IOA3
: : : : : : : :
: : : : : : : :
: : : : : : : :
IEC 60870-5-101

Edition 06.2017, DC0-023-2.12
5.6.4 Blocking
The data transmission according to IEC 60870-5-103 defines no blocking! The protocol
element of the remote terminal unit thus also does not support any blocking in the
"IEC 60870-5-103" operating mode of the interface.
The protocol element of the remote terminal unit supports other operating modes for the
operation with a SICAM RTUs master station, with which the transmission of IEC 60870-5-101
message formats can be performed without conversion to IEC 60870-5-103.
With the "IEC 60870-5-101" operating mode of the interface, the transmission procedure
according to IEC 60870-5-101 is implemented with IEC 60870-5-101 message formats. With
the "IEC 60870-5-103(101)" operating mode of the interface, the transmission procedure
according to IEC 60870-5-103 is implemented with IEC 60870-5-101 message formats.
For the optimum utilization of the transmission paths, with the data transmission with IEC
60870-5-101 message formats, the "Blocking" according to IEC 60870-5-101 is implemented.
This function is performed on the basic system element (BSE) according to the rules
applicable for this. Data to be transmitted are thereby already blocked on the basic system
element and passed on to the protocol element for transmission. Received data in blocked
format according to IEC 60870-5-101 are passed on from the protocol element to the basic
system element in blocked format. On the basic system element the blocked data is split up
again into individual information objects by the detailed routing function and passed on as
such to the further processing.
Measured values are normally transmitted from the protection equipment (remote terminal
units) as "Class 2 data" and all other information as "Class 1 data".
If protection equipment only supply "Class 1 data", then the master station can omit an
interrogation for "Class 2 data" for these stations. For this the type of data interrogation can be
determined selectively for every remote terminal unit in the master station in the parameters
for the station definition with the parameter station definition |
prioritization of data.
In the "IEC 60870-5-103" operating mode of the interface, the protocol element of the remote
terminal unit supports class 1 data and class 2 data according to IEC 60870-5-103.
The assignment of the data to class 1 data or class 2 data is performed by the protocol
element of the remote terminal unit without necessary parameterization. If binary information
are to be transmitted from the remote terminal unit, these are buffered on the protocol element
until these class 1 data is interrogated by the master station. Class 1 data stored for
transmission are indicated to the master station with ACD-Bit=1 in the control field of every
message.
In the "IEC 60870-5-101" and "IEC 60870-5-103(101)" operating mode of the interface, only
class 2 data is supported!
SICAM RTUs internal mechanisms for the prioritization of the data to be sent provide
extensive options in order to be able to transmit important data to the master station.

DC0-023-2.12, Edition 06.2017
For the coupling of protection equipment, if necessary the following special functions can be
· Send short-circuit location values with GI

· Resetting the short-circuit location values
· Signaling / measured value disabling
· Technological adaptation for measured values
· Transfer of the information "blocked activation/tripping of the protection"
· Transmit non-updated process images
· Emulation of the going binary information
5.6.6.1 Send Short Circuit Location Values with GI
With general interrogation, short-circuit location values are not transmitted from the protection
equipment. If the short-circuit location values are also expected with general interrogation in
higher-level control centre systems, then with a general interrogation these can be emulated
by the protocol element from the internal process image.
This function is set with the parameter advanced parameters | send fault location
values within GI.
5.6.6.2 Resetting the Short Circuit Location Values
Short-circuit location values are transmitted from the protection equipment in monitoring
direction with the type identification "<TI=4> real-time measured values with relative time".
Short-circuit location values are not reset by the protection equipment!
For the processing of the short-circuit location values in the control centre system, the protocol
element provides the following special functions:
· Reset short-circuit location values with command

· Reset short-circuit location values automatically
The short-circuit location values are reset in the internal process image of the protocol
element and from this emulated spontaneously to the BSE with the parameterized initial
values.
A large number of short-circuit location values to be emulated with initial value, can soon lead
to a high data load in the system, through which problems can occur with the further
distribution in the system.
The resetting of the short-circuit location values can be slowed with the parameter advanced
parameters | send initial values with delay. Thereby, a parameterized pause is
always maintained after 5 short-circuit location values emulated with initial value (=measured
value messages). The pause is also parameterized with the parameter advanced
parameters | send initial values with delay.

Edition 06.2017, DC0-023-2.12
5.6.6.2.1 Reset the Short Circuit Location Values with Command
After the spontaneous transmission of the short-circuit location values from the protective
devices, these can be reset on the protocol element with a special command message.
The reset short-circuit location values are transmitted spontaneously from the protocol
element with the parameterized initial value.
The assignment of the message address for the spontaneous information object "Command
to reset the short-circuit location values" is carried out in the OPM II with the category
firmware / Trans_command_reset_error_location.
With an IEC 60870-5-101/104 command message, all short-circuit location values received
from one protection device (<TI=4> real-time measured values with relative time), can be
reset in the process image of the protocol element of the master station.
A specific command message must be used for each protective device (i.e. per LINK-
address).
This command is not transmitted, rather only processed "protocol element internal". The short-
circuit location values are reset to the parameter-settable "Initial value".
The initial values for the short-circuit location values can be parameterized for the various IEC
60870-5-101/104 measured value formats with the parameter advanced parameters |
initialization value 16 bit normalized (TI 34), the parameter advanced
parameters | initialization value 16 bit scaled (TI 35) and the parameter
advanced parameters | initialization value Floating Point (TI 36).
5.6.6.2.2 Reset Short Circuit Location Values automatically
After the spontaneous transmission of the short-circuit location values from the protective
devices, these can be reset by the protocol element after a parameter-settable time.
The reset short-circuit location values are transmitted spontaneously from the protocol
element with the parameterized initial value.
This function is activated with the parameter advanced parameters | reset fault
location values and the parameter advanced parameters | imitate
initialization values. In addition, with the parameter advanced parameters |
reset fault location values the delay time is also set.
The initial values for the short-circuit location values can be parameterized for the various IEC
60870-5-101/104 measured value formats with the parameter advanced parameters |
initialization value 16 bit normalized (TI 34), the parameter advanced
parameters | initialization value 16 bit scaled (TI 35) and the parameter
advanced parameters | initialization value Floating Point (TI 36).
The IEC 60870-5-101/104 format for every short-circuit location value is parameterized in the
SIP message address conversion.

DC0-023-2.12, Edition 06.2017
5.6.6.3 Signaling / Measured Value Disabling
The signaling / measured value disabling is a function of the protection equipment and can be
activated globally (for binary information and measured values together) for example by
means of a key lock switch or by means of a control input in the protection equipment.
Through the signaling / measured value disabling function, the spontaneous transmission of
the data from the protection equipment to the master station is deactivated.
With activation/deactivation of the signaling / measured value disabling in the protection
equipment, the signal "signaling / measured value disabling" is transmitted spontaneously to
the master station. The signaling / measured value disabling is transmitted as last signal with
activation and as first signal with deactivation.
With activation of the signaling / measured value disabling, the data concerned are not
emulated to the basic system element by the protocol element of the master station with the
status "Blocked" in the IEC 60870-5-101/104 format.
With deactivation of the signaling / measured value disabling, to update the data a general
interrogation can be triggered to the protection equipment by the protocol element of the
master function.
So that the general interrogation can be triggered with deactivation of the signaling /
measured value disabling, the information "signaling / measured value disabling" of the
protection equipment must be entered in the SIP message address conversion in receive
direction with the category firmware / Rec_binary information. In addition, in the category the
setting "initiate GI with going edge" must be selected in the field GI-initiation.
5.6.6.4 Technological Adaptation for Measured Values
The technological adaptation enables the measured value supplied by the protection
equipment to be transformed into a technological or normalized value. Into which value
conversion can take place, is dependent on the format of the spontaneous information object
"Measured value" to be transferred.
Spontaneous Information Object Value Range Meaning

-15
Measured value, normalized value - 1 ... + 1-2 normalized, percent representation
Measured value, scaled value - 32768 technological, integer
...
+ 32767
-37
Measured value, short floating point - 8,43 * 10 technological, floating point
...
38
+ 3,37 * 10
Depending on the protocol element, the parameters for the technological adaptation are
parameterized per measured value as
· Adaptation line with 2 interpolation points (X_0%, X_100%, Y_0%, Y_100%)
The received measured value is adapted linear according to the parameter setting by the
protocol element before transfer to the basic system element.
The adaptation line with 2 interpolation points is to be parameterized for each measured value
with the parameters "X_0%", "X_100%", "Y_0%" and "Y_100%". For this, the technological value
Y0 is parameterized for the lower limit of the measuring range X0 and the technological value
Y100 for the upper limit of the measuring range X100.
The adaptation line with "kx+d" is to be parameterized for each measured value with the
parameters "Factor_k" and "Offset_d".

Edition 06.2017, DC0-023-2.12
Bipolar measured values without zero-range suppression and plausibility check

Example for <TI:3,9>
Value Meaning Parameter

X0 -1 lower boundary of the measuring range (set by parameter) X_0%
X100 +1 upper boundary of the measuring range (set by parameter) X_100%
Y0 technological value at X0 Y_0%
Y 100 technological value at X100 Y_100%
Y100 Normalized value
X0 X100
Y0
Data point quality descriptor
IV
OV

DC0-023-2.12, Edition 06.2017
5.6.6.5 Measured Value Change Monitoring
Measured values are transmitted from some protection equipment with the smallest changes
in measured value or even cyclic.
So as not to load the following transmission facilities unnecessarily, the measured value is
monitored for change in accordance with the following rules:
· The first value received after startup is transmitted immediately

· Every change of the quality descriptors blocked, invalid or overflow triggers an immediate
transmission
· Change monitoring in accordance with the method of the additive threshold value
procedure
Additive threshold value procedure

In the parameterized processing grid the measured value is monitored for change. If the
deviation from the last spontaneously transmitted measured value is greater than the
parameterized "Threshold_absolute", the new measured value is transmitted immediately.
Otherwise, in the parameterized processing grid the deviations from the last spontaneously
transmitted measured value are totaled according to the polarity sign. Only when the amount
of this total exceeds the parameterized Thresh_additive is the current measured value
spontaneously transmitted.
thresh thresh Processing

uncond additive
0 0
à value will be sent to BSE immediately after change
0 ≠0
≠0 0 à value will be sent to BSE immediately after change during next
processing grid
≠0 ≠0 - change of value greater or equal than thresh_uncond
à value will be sent to BSE immediately after change during
next processing grid
- change of value less than thresh_additive
à additive threshold value procedure
A transmission of the measured value due to a general interrogation does not influence the
threshold value procedure.
By means of parameterization it is defined:
─ Processing grid: 1 s…25.5 s

─ Threshold_Unit (optional): % or absolute
─ Thresh_uncond : 0.00%...103.00% or 0.0…999.9
─ Thresh_additive: 0.0%...1000.0% or 0.0…999.9
The percentages given refer to the parameterized value for Y100 – Yat X=0.
Die Werte für die Parameter Schwelle_additiv und Schwelle_unbedingt sind

Absolutwerte und beziehen sich immer auf den Wert nach der technologischen Anpassung.
The processing grid is to be parameterized for all measured values with the parameter
advanced parameters | Measured value thresholds | cycle time for measured
change monitoring.
The thresholds are to be parameterized depending on the protocol element either for every
measured value with the parameter thresh_additive and the parameter thresh_uncond
or one can be selected from max. 16 parameter-settable measured value thresholds for each
measured value with the parameter Measured value threshold.

Edition 06.2017, DC0-023-2.12
The measured value thresholds are to be parameterized with the parameters advanced
parameters | Measured value thresholds | *.
The following example describes a standard case, in which the adaptation line goes through
the zero point (origin) (Yat X=0 = 0).
Examples
Technological value Y100 4000
Processing grid 0.1 s
Thresh_uncond 2.00% represents a change of 80
Thresh_additive 150.0% represents an additive total of 6000
Example 1: After transmission due to the exceeding of the large threshold, the value has
changed once by 79 (< the large threshold) and subsequently remains
constant. The measured value is transmitted after 7.5 seconds.
0.0s 0.1s 0.2s 0.3s 0.4s 0.5s 0.6s 0.7s 0.8s ... 7.4s 7.5s
Measured value 300 379 379 379 379 379 379 379 379 ... 379 379
Difference >80 79 79 79 79 79 79 79 79 ... 79 79
Additive total 0 79 158 237 316 395 474 553 632 ... 5925 6004
Transmission x x
constant. The measured value is transmitted after 10 minutes.
0.0s 0.1s 0.2s 0.3s 0.4s 0.5s 0.6s 0.7s 0.8s ... 599.9 600s
Measured value 300 301 301 301 301 301 301 301 301 ... 301 301
Difference >80 1 1 1 1 1 1 1 1 ... 1 1
Additive total 0 1 2 3 4 5 6 7 8 ... 5999 6000
Transmission x x
Example 3: After transmission due to the exceeding of the large threshold, the value
continually changes by ±1. The measured value is not transmitted.
0.0s 0.1s 0.2s 0.3s 0.4s 0.5s 0.6s 0.7s 0.8s ... 7.4s 7.5s
Measured value 300 301 300 299 300 301 300 301 299 ... 300 301
Difference >80 1 0 -1 0 1 0 1 -1 ... 0 1
Additive total 0 1 0 1 0 1 0 1 1 ... 0 1
Transmission x

DC0-023-2.12, Edition 06.2017
5.6.6.6 Monitoring Intermediate and Faulty Positions of Double-Point

Information
Double-point information that are transmitted from the protection equipment, or single-point
information that are transmitted from protection equipment and converted to double-point
information on the protocol element, can be monitored by the protocol element for
intermediate and faulty position (in most cases protection equipment do not have any
monitoring for intermediate and faulty position implemented).
Thereby, the transfer of an intermediate position (neither ON- nor OFF binary information
exists) or a faulty position (both ON- as well as OFF binary information exists) is suppressed
by the protocol element for a parameter-settable time.
On reception of a double-point information with intermediate or faulty position, a monitoring

time is started and the double-point information is not transferred. If the double-point
information is received during the monitoring time with valid binary information state (ON or
OFF), the monitoring time is stopped and the double-point information with the valid binary
information state is transferred.
On expiry of the monitoring time, the double-point information with the state "intermediate or
faulty position" is transferred with the received time.
The assignment of the message address for the spontaneous information object "Double-point
information" is carried out in the OPM II with the category firmware / Rec_binary information.
A suppression time can be parameterized for the suppression of intermediate and faulty
position for each double-point information (parameter inter-/faulty_t).

Edition 06.2017, DC0-023-2.12
5.6.6.7 Transfer of the Information "Blocked Activation/Tripping of the

Protection"
Disturbance information from protection equipment can be transferred in the direction IEC
60870-5-101/104 with the message formats provided especially for this "blocked activation of
protection" and "blocked triggering of protection".
With the message "blocked activation of protection" several protection activation signals and
the relay duration time are transmitted.
With the message "blocked triggering of protection" several binary information are transmitted
to the output current circuit of the protective device and the relay operation time.
IEC 60870-5-101/104 IEC 60870-5-103

<TI=39> Packed start events of protection with <TI=2> Binary information with relative
time tag time
<TI=40> Packed output circuit information of <TI=2> Binary information with relative
protection equipment with time tag time
<TI=39> Packed Start Events of Protection IEC 60870-5-103 Disturbance

with Time Tag (SPE) Information *)
GS general start of operation <INF=84> general start of operation
SL1 start of operation phase L1 <INF=64> activation L1
SIE start of operation IE (earth current) <INF= >
SRD start of operation in reverse direction <INF= >
<TI=40> Packed Output Circuit Data of Protection IEC 60870-5-103 Disturbance

with Time Tag (OCI) Information 1)
GC general command to output circuit <INF=68> General triggering
CL1 command to output circuit phase L1 <INF=69> triggering L1
*) the specified information number represents the default values according to IEC 60870-5-103
(protection equipment can also transmit these disturbance binary information with different
address)
The assignment of the message address for the spontaneous information object "blocked
activation/triggering of protection" is carried out in the OPM II with the category firmware /
Rec_packed_start_event_output_circuit.
The disturbance binary information are always transmitted from the protection equipment as
single binary information messages. For the transfer with the IEC 60870-5-101/104 message
format, the binary information state of several start events of protection equipment and a relay
duration time/relay operation time (relative time) are transmitted in one message.
The moment of transfer of the IEC 60870-5-101/104 message can be determined with the
parameter advanced parameters | packed start events/output circuit of
protection equipment.
· Transfer with change of a binary information state.

· Transfer only with going general start of operation or trip information
The message is time tagged again by the protocol element with the transfer.
· Transfer only with going general start of operation or trip information.
With the transfer, the message is time tagged by the protocol element with the time of the
coming general start of operation or trip information.

DC0-023-2.12, Edition 06.2017
Transfer with change of a binary information state

The message "blocked activation of protection" or "blocked triggering of protection" is
transferred with each binary information change in the message. As relay duration time/relay
operation time the relative time of the changed disturbance information is entered.
Transfer only with going general start of operation or trip information (time from PRE)
IEC 60870-5-103 disturbance information are only received by the protocol element after
coming disturbance information for general activation /-tripping and buffered until transfer of
the IEC 60870-5-101/104 message "blocked activation/triggering of protection“.
The message "blocked activation of protection" or "blocked triggering of protection" is only

transferred after reception of the going disturbance information for general activation/-
triggering. As relay duration time/relay operation time the relative time of the going
disturbance information is entered.
If no going disturbance information arrives within 60 seconds after a “coming” disturbance

information for general activation/-triggering, then the message "blocked activation of
protection" or "blocked triggering of protection" is transferred by the protocol element.
As relay duration time/relay operation time the relative time of the last changed disturbance
information is entered.
Transfer only with going general start of operation or trip information

(time from protection equipment)
The function is identical as for "Transfer only with going general start of operation or trip
information (time from PRE)", but with the transfer the message is time tagged by the protocol
element with the time of the coming general activation or trip information (time from the
protection equipment).

Edition 06.2017, DC0-023-2.12
5.6.6.8 Transmit Non-Updated Process Images
After a general interrogation, the protocol firmware of the master station sends all non-
received but parameterized data points for binary information with status "interrogated by
station interrogation". The quality descriptor of the data points of failed remote terminal units is
transmitted with "not topical".
The emulation of these data points will be started after a parameterizable delay time (default =
number of stations * 5 seconds) – from transmission of the general interrogation command.
The delay time for the emulation of the data points can be parameterized with the parameter
advanced parameters | timeout for emulation of not updated process data
after GI.
The emulation of these data points can be deactivated with the parameter advanced
parameters | not updated process data base.
The emulation of the data not received for GI must then be deactivated, if in combination with
the automatic data flow routing in SICAM RTUs a general parameter setting (surplus) for the
data of protection equipment is used. The reason is, that the protection equipment are not
always configured the same, i.e. they do not always supply the same volume of data.
In this case, data have been emulated by the protocol element following a general
interrogation, which are possibly not transferred at all by the protection equipment.
à If in the master station a surplus quantity of the data model is parameterized, emulated but
not received data points would always be signaled as "faulty".
5.6.6.9 Emulation of the Going Binary Information [Master only]
With IEC 60870-5-103, protection signals are only transmitted with the state "ON" (coming).
For IEC 60870-5-101/104, the "coming/going state" is always required for every signal.
The protocol element with IEC60870-5-103 master function can emulate the "Going Signal"
automatically for selected signals in receive direction. The "Going Signal" is emulated
immediately after sending the coming signal with the time of the coming signal + 10
milliseconds.
The emulation of the going signal can be parameterized in the SIP message address
conversion in receive direction in the category firmware / Rec_binary information for each
signal in the field type_of_binary_information.
With additional info "type of binary information = only coming binary information", after the
transfer of the received binary information "coming", the binary information "going" is emulated
by the protocol element with the "received time + 10 ms".

DC0-023-2.12, Edition 06.2017



Block Diagram
Protocol element
control
Internal
Transmission route
function
Protocol element


Edition 06.2017, DC0-023-2.12
message.

DC0-023-2.12, Edition 06.2017
PST Detail Routing

Continuous call station x ON 3 0 – 99 0 -65535 Z-Par=0: Continuous call without time
input (stopped by other function)
- Reset interface failure
"Deactivate" interface 5 - - - Do not send all messages from BSE
- Received messages are discarded
"Activate" interface 6 - -
command
message!
CASDU = BROADCAST
241 - -

65535
(all stations)
125
65535
(all stations)
65535
(selective station)
0 – 99
65535
(selective station)
Reset command 243 This function is not presently supported
by PRE!
command
message!
CASDU = selective
routing.


Edition 06.2017, DC0-023-2.12
Legend:

0 - 99 Station 0 - 99 of the selected protocol element
125 Station 0 - 99 of the selected protocol element (=BROADCAST)
Fl ............... Edge
SCS ........... Single command state
PST Detail Routing

Send (general) interrogation command 240 - - message and not using PRE-control
message!
CASDU = BROADCAST
241 - -
Reset command 243 This function is not presently supported

by PRE!
command
message!
CASDU = selective
Legend:


DC0-023-2.12, Edition 06.2017


Edition 06.2017, DC0-023-2.12
Possible master station return information:
Parameter
- User data message "to all" (BROADCAST) is now being
transmitted
transmitted
takes place internally in a 100 ms grid ð state line changes shorter than 100 ms are not guaranteed to be
transmitted!
Legend:

0 - 99 Station 0-99 of the selected protocol element
Parameter
takes place internally in a 100ms grid ð state line changes shorter than 100 ms are not guaranteed to be
transmitted!

DC0-023-2.12, Edition 06.2017
6 SICAM RTUs Field Bus (SFB)
Contents
6.1 Introduction .................................................................................................. 234

6.2 Communication ............................................................................................ 236

DC0-023-2.12, Edition 06.2017
SICAM RTUs Field Bus (SFB)
6.1 Introduction
The SICAM RTUs Field Bus describes a serial communications protocol with which a
SICAM RTUs master station in multi-point traffic is connected with one or several
SICAM RTUs remote terminal units over a communications link in a linear or star
configuration. The data traffic is controlled by the master station and is optimized for the
application as field bus.
Master station
TF
TF TF TF
Legende:

The master station and the remote terminal units in multi-point traffic operate with a
communications protocol according to IEC 60870-5-101.

Edition 06.2017, DC0-023-2.12
General Functions
The SICAM RTUs field bus is based on IEC 60870-5-101 and supports the following
functions:
Communication between one central station and up to 100 remote stations

· Unbalanced multi-point (multi-point traffic)
SFBMxx is controlling station (primary station), SFBSxx is controlled station (secondary
station).
− Cyclic, every 5 seconds
─ Transmission of integrated totals
The operating mode of the interface is determined by parameters of the protocol element and
optional equipment.
Operating mode Parameter and Setting Interface Signals

Unbalanced Asynchronous / Isochronous TXD, RXD, GND, RTS, DTR, DSR/+5V,
interchange circuit Asynchronous DCD, CTS
V.24/V.28
V.28 asynchronous
Optical interface Asynchronous / Isochronous RXD, TXD, CTS, DCD, DTR, DSR/+5V,
(multimode fiber optic) Asynchronous GND
with CM-0827
Balanced interface RXD, TXD, CTS, RTS, DCD, DTR,
RS-485 DSR/+5V, GND
V.11 asynchronous

DC0-023-2.12, Edition 06.2017
6.2 Communication
interrogated sequentially, whereby remote terminal units with important data is interrogated
more often. Remote terminal units may only transmit when they are called.
The interrogation procedure is performed continuously (= continuous cycle).
No", "Station Enabling", "Station failure", are to be set in the parameters in the station
definition.
Common settings | Address of the link (=own station number). This address must be
unambiguous for each field bus line.
The prioritization of the station interrogation cannot be influenced through parameterization.

The interrogation procedure executes a station change after every station interrogation.


Edition 06.2017, DC0-023-2.12
Number of calls until station change = 1 (for all stations)
Station change: Below, as an example, the prioritization of the station interrogation is shown
for continuous cycle.
Œ
t
U0
U1
U2
U3
U4
U5
U6
U7
U8
U9
U10
Legend:
…..….. Remote stations
,..…...….. Data message, short acknowledgement (remote station à master station)
,…..….. Data message (Command), calling message (remote station à master station)

For the interfacing of the SICAM RTUs remote terminal units with the field bus protocol
according to IEC 60870-5-101, the setting of the variable elements of the message is to be set
as required (Master and all Slaves must have the same parameter settings).


Element
Address field of the link (number) Number of octets for the address field of the link PRE
layer
(CASDU) ASDU
information object
Acknowledgement 60870-5-2 Acknowledgement on IEC 60870-5-2 layer PRE
Single character *)
*) fixed by the protocol element!
Legend:

DC0-023-2.12, Edition 06.2017
one selected station. An automatically started continuous interrogation of one emote terminal
following a message transmission is known as a demand.
Data messages ready for sending to same remote station will be sent during demand in
progress.
control message.
be parameterized). On expiry of the number of retries, the station is flagged as faulty.
selective).
The acknowledgement from the remote terminal unit to the master station is always
transmitted with the single character (E5H).

Edition 06.2017, DC0-023-2.12
retry handling. For failed stations, a communication fault is only then reported if this is
parameterized accordingly in the parameter "Station failure" of the station definition.
station with the interrogation procedure, however no message retry is performed for such
terminal unit.
The monitoring of the interface in the remote terminal unit is carried out by monitoring for
"cyclic station interrogation". The monitoring time is to be set in the remote terminal unit with
the parameter advanced parameters | call monitoring time. In addition, with the
parameter advanced parameters | monitoring times | call timeout retrigger
also with "request status of link" it can also be set whether the monitoring time is
to be retriggered not only by station-selective call or data messages, but also with station-
selective messages for station initialization – these are only transmitted during the initialization
phase.
With failed interface, data to be transmitted are fetched by the protocol firmware and
negatively acknowledged internally to the basic system element. As a result, the data is stored
in the data storage on the basic system element (BSE) of the remote terminal unit until these
are deleted by the dwell time monitoring or can be transmitted to the master station.

DC0-023-2.12, Edition 06.2017
with:

- Acknowledgement for RESET OF REMOTE LINK is
The end of initialization according to IEC 60870-5-101 is not supported by this protocol
element!
(BSE) in the remote terminal unit until transmission. For the optimization of the reaction time,
up to 10 messages are already fetched by the protocol element in the remote terminal unit
from the basic system element before a station interrogation and stored in the internal
memory of the protocol element. With a station interrogation, a message is transmitted to the
master station from the internal memory. If the internal memory on the protocol element is
empty, the protocol element of the remote terminal unit function replies with a short
acknowledgement ("have no more data").
implemented.

Edition 06.2017, DC0-023-2.12
terminal units.
The clock synchronization of the remote terminal units is performed over the serial
The period for cyclic clock synchronization is set to 5 seconds (not configurable).
Accuracy: 1ms (with cyclic clock synchronization every 5 seconds)
The clock synchronization command is transmitted cyclic by the protocol element of the
master station to all remote terminal units with a BROADCAST message.
The period for the transmission of the clock synchronization command <TI=103> is fixed
beginning from the 3rd second in the 5 second grid (i.e. at every
3,8,13,18,23,28,33,38,43,48,53,58-th second a clock synchronization command is
transmitted).
The protocol element in the remote terminal unit corrects the time contained in the message
with the message delay and adds the exact reception moment in units of 1ms.
For this purpose, the firmware splits up the 10ms ticker provided by the system into a 1ms
clock pulse. In addition, the clock synchronization message (FC = 156) is specially identified
for the time server in the system (Bit# 5 of the migration status). Based on this identifier the
time server performs a synchronization of the system time every 10th second.
ATTENTION:
- The 1 ms accuracy is presently only provided in the System AM 1703, since only the time
server in AM 1703 supports this functionality!
- The protocol element does not correct any transmission delays caused by non transparent
communication equipment!

DC0-023-2.12, Edition 06.2017

Terminal Unit
(unacknowledged)
Message retries | Retries for data message SEND/NO REPLY (broadcast) .
A counter interrogation triggered in the system is always transmitted station-selective by the

protocol element of the master station to the remote terminal units.
A counter interrogation command to be sent is then already made available station-selective
to the protocol element by the basic system element.

Edition 06.2017, DC0-023-2.12

Facilities
facility.
The transmission rate (baud rate) is depending on the submodule used for communication
either fixed by the protocol element firmware or can be set for transmit/receive direction
together with the parameter Common settings | baud rate.
Apart from this a transmission facility that can be freely defined by the user can be selected,
for which all available parameters can be individually set. This is then necessary if
be used for predefined transmission facilities.
For the selection of the freely definable transmission facility the parameter Common
settings | interface modem is to be set to "freely definable".
Parameter
[SM-0551, SM-2551 only]
[SM-0551, SM-2551 only]

DC0-023-2.12, Edition 06.2017
the DSR signal with corresponding parameter setting.
ATTENTION:
be observed!
Parameter "Configuring for CM-082x" [only SM-0551, SM-2551]
If an optical transformer of the type CM-082x is used as external transmission facility, then the
Configuration for CM-082x must be set when using a patch plug of the type CM-2860.
Parameter

Edition 06.2017, DC0-023-2.12
Default parameters for transmission facilities with UMPM01, UMPS01
Transmission facility Electrical RTS tp tv tn tdis DCD tbs tstab tduration tdelay
Interface [ms] [ms] [Bit] [ms [ms] [ms] [sec] [ms]
]
CM-0821 Ring RS-232 áâ 0 1 0 0 NO 0 0 0 0
CM-0821 Star, CM-0826, CM-0827, CM-0829 RS-232 áâ 0 1 0 0 NO 0 0 0 0
Freely definable
Default parameters for transmission facilities with SFBMA1, SFBSA1
Transmission facility Electrical RTS tp tv tn tdis DCD tbs tstab tduration tdelay 5V CM082x
Interface [ms] [ms] [Bit] [ms [ms] [ms] [sec] [ms]
]
CM-0821 Ring RS-232 áâ 0 0 0 0 NO 0 0 0 0 YES NO
CM-0821 Star, CM-0826, CM-0827, CM-0829 RS-232 áâ 0 0 0 0 NO 0 0 0 0 YES NO
Freely definable
Legend:
Electrical interface.........Parameter Electrical interface [SM-2541 only]
RTS ...............................áâ = RTS is switched for the control of the carrier switching of the modem with each message (ON / OFF)
tp ....................................Pause time (tp), Pause time time base (tp)
tv ....................................Set-up time (tv), Set-up time time base (tv)
tn ....................................overtravel time (tn), overtravel time time base (tn)
tdis .................................disable time (tdis), disable time time base (tdis)
DCD ...............................DCD-assessment
tbs ..................................Bounce suppression time (tbs)
tstab ...............................Stability monitoring time (tstab)
tduration ........................Continuous level monitoring time (tduration)
tdelay .............................Transmit delay with level (tdelay)
CM082x .........................Parameter Configuring for CM082x. Configuring the interface for optical transformer CM-082x with patch plug CM-2860 [SM-0551, SM-2551 only]
5V ..................................Parameter 5V Supply (DSR) [SM-0551, SM-2551 only]

DC0-023-2.12, Edition 06.2017
RTS
tverz
tp tv Data transmission tn tsw tp tv

Master station
TXD
tPrell tPrell
DCD
tverzRTS
Data transmission
RXD
tsignal tsignal
tdis
t´Prell t´Prell
DCD
t´signal
Remote station
Data transmission
RXD
t'dis
RTS

TXD
t'verz
Œ Œ
tPrell tPrell
tstab tstab
tdauer
Legend:



tdis …….….….. Disable time of the receiver after message receiption (to supress faulty signs during level monitoring )

Edition 06.2017, DC0-023-2.12

Routes
In the master station the following operating modes are supported for redundancy:
· 1703-Redundancy (Standard)
control messages.
In the remote terminal unit, no function for the support of redundant communications routes is
supported by the protocol element!
From the redundant – non-active master station, listened messages are passed on in the
system with the identifier "passive" in the status.
passive as follows:

· Interface "ACTIVE" – interrogation mode

DC0-023-2.12, Edition 06.2017
6.5.1 Blocking
From the remote terminal units in multi-point traffic, data is always transmitted to the master
station as class 2 data.

Edition 06.2017, DC0-023-2.12



Block Diagram
Protocol element
control
Internal
Transmission route
function
Protocol element


DC0-023-2.12, Edition 06.2017
message.

Edition 06.2017, DC0-023-2.12
PST Detail Routing

Continuous call station x ON 3 0 – 99 0 -65535 Z-Par=0: Continuous call without time
input (stopped by other function)
command
message!
CASDU = BROADCAST
241 - -

65535
(all stations)
125
65535
1) 2)
(all stations)
Set control location 242
65535
(selective station)
0 – 99
65535
(selective station)
This function is not presently supported
Reset command 243
by PRE!
command
message!
CASDU = selective
1) not supported by SICAM RTUs!
routing.

Legend:
SF ..................... Control function_(PRE)

Station .............. Station number
0 - 99 = station 0 - 99 of the selected protocol element
125 = all stations of the selected protocol element (=BROADCAST)
Z-Par ................ Additional parameter_(PRE)
Fl ...................... Edge
SCS .................. single command state
HKA .................. Originator address (HKA) = 0 - 255

DC0-023-2.12, Edition 06.2017
PST Detail Routing

Send (general) interrogation command 240 - - message and not using PRE-control
message!
CASDU = BROADCAST
Send (general) interrogation command This function is processed on the BSE and
for GI-group to own BSE 1) 241 - - not sent to the protocol element as PRE-
(=simulate received general interrogation command control message!
for GI group)
This function is not presently supported by

Reset command 243
PRE!
command
message!
CASDU = selective
Legend:
SF .....................Control function_(PRE)
Station ..............Station number
Z-Par.................Additional parameter_(PRE)

Edition 06.2017, DC0-023-2.12


DC0-023-2.12, Edition 06.2017
Possible return information of master station:
Parameter
- User data message "to all" (BROADCAST) is now
being transmitted
transmitted
with change or as reply to a general interrogation command.
The spontaneous transmission of the current states takes place internally in a 100ms grid.
ð State line changes shorter than 100ms are not guaranteed to be transmitted!
Legend:
Station ..............Station number

0…99 Station 0-99 of the selected protocol element
Possible return information of remote terminal unit:
Parameter
Return information Station Note
function_(PRE)
1) States of the state lines are transmitted spontaneously from the protocol element to the basic
system element with change or as reply to a general interrogation command.
The spontaneous transmission of the current states takes place internally in a 100ms grid.
ð State line changes shorter than 100ms are not guaranteed to be transmitted!

Edition 06.2017, DC0-023-2.12
7 Dial-Up Traffic (DIA)
Contents
7.1 Introduction .................................................................................................. 256

7.2 Control of Connection Setup and Disconnection ........................................... 258
7.3 Communication with existing Connection according to IEC 60870-5-101 ....... 280
7.4 SMS Messages ............................................................................................ 289
7.5 Co-ordination of several Masters in "Multi-Master Mode" .............................. 290
7.6 Standby Transmission Line(s) over Standby Telephone Number(s) .............. 291
7.7 Multi-Hierarchical Configurations .................................................................. 292
7.8 Standby Transmission Line via Dial up Traffic ............................................... 293
7.10 Toll-Saving Transmission Strategies ............................................................. 310
7.11 Having a Telephone Set Connected in Parallel ............................................. 311
7.12 Functions for supporting Redundant Communication Routes ........................ 312

DC0-023-2.12, Ausgabe 06.2017
Dial-Up Traffic (DIA)
7.1 Introduction
Dial-up traffic describes a serial communications protocol with which a master station is
connected with one or more remote terminal units over the public telephone network "PSTN"
(ISDN, GSM, analog/digital). A connection setup for the transmission of data over the
telephone network can be performed spontaneously by the master station as well as by the
remote terminal unit. With connection established, the data traffic is controlled by the master
station.
Master station
TF TF
Telephone network
“PSTN“
(ISDN, GSM, analog/digital )
TF TF TF
Legend:
TF ………..….. Transmission facility (Modem)
With connection established in dial up mode the transmission of telecontrol data is based on
IEC60870-5-101 (unbalanced) with proprietary extensions and the usage of additional
message formats in the private range of IEC60870-5-101 for authentication and coordination
of connection control information.
In dial-up traffic, with connection established an "unbalanced transmission procedure" is used.

That means, that with connection established, as primary station the master station initiates all
message transmissions, while the remote terminal units, which are secondary stations, may
only transmit when they are called.
The dial-up traffic only requires only a "half duplex" transmission medium.
The communication protocol for data transmission of telecontrol data in dial up mode is based
on following features:
· Connection setup according AT-Hayes (Industrial standard for modem control)

· Authentication (Access control, LOGIN) in the private range of IEC 60870-5-101
· Data transmission with established connection according IEC 60870-5-101 (unbalanced)
· Disconnection control information in the private range of IEC 60870-5-101
· "CSD-services" (Circuit Switched Data) used for data transmission with GSM

Edition 06.2017, DC0-023-2.12
General Functions
Communication between one central station and up to 100 remote stations

· Unbalanced multi-point (dial-up traffic) based on IEC 60870-5-101
DIAMxx is controlling station (primary station), DIASxx is controlled station (secondary
station).
· Controlling connection establishment and disconnection
─ Connection establishment spontaneously and cyclically, controlling station ó
controlled station
− Establishing a connection cyclically at a settable interval (monitoring cycle)
* for transmission of low-priority data
* for monitoring the station availability
* for clock synchronization
─ Controlling connection establishment by means of modem commands
− AT Hayes, V.25bis, X.20, X.28
− Arbitrary main telephone number of a telephone network (PSTN)
─ Access control (LOGIN with password) in the private range of IEC 60870-5-101
─ Disconnection control in the private range of IEC 60870-5-101
· Communication when a connection is established according to
unbalanced multi-point (dial-up traffic) based on IEC 60870-5-101
− Each time a connection has been established
− When a connection is established, one time per minute
─ Transmission of integrated totals
· Co-ordination of several masters in "multi-master operation" (availability and data
throughput)
─ The controlling station can simultaneously establish connections to different controlled
stations
· Standby transmission line(s) by means of standby telephone numbers of the same or
another (PSTN) telephone network
· Multi-hierarchical configurations
· Toll-Saving Transmission Strategies
· Having a telephone set connected in parallel
The operating mode of the interface is determined by the protocol element.
Operating mode Parameter and Setting Interface Signals

Unbalanced Asynchronous / Isochronous TXD, RXD, GND, RTS, DTR, DSR/+5V,
interchange circuit DCD, CTS
V.24/V.28
V.28 asynchronous Asynchronous

DC0-023-2.12, Edition 06.2017
7.2 Control of Connection Setup and Disconnection
A connection setup for the transmission of data over the telephone network can be performed
spontaneously or cyclic by the master station as well as by the remote terminal unit.
A spontaneous connection setup always takes place when important spontaneous data is to
be transmitted, a general interrogation or even a monitoring cycle is to be performed.
A cyclic connection setup can be performed by the master station as well as by the remote
terminal unit at a settable interval (monitoring cycle) and is used in particular for:
· Monitoring the station availability

· Transmission of low priority data
· Clock synchronization
The connection setup and disconnection via the data transmission facilities is controlled with
AT-Hayes, CCITT V.25bis, X.20 or X.28 commands (modem control). With connection
established, a communication protocol based on IEC 60870-5-101 "Unbalanced Multi-Point
(multi-point traffic)" is used.
The protocol element uses special administration messages in the private range of IEC
60870-5-101 to control the connection setup and disconnection, the use of a standby
transmission line, and access (password protection).
Co-ordination of several masters in "multi-master mode"

In the so-called multi-master mode, provided there are several dial-up modems available in
the master station and just as many SM-25xx/DIAMxx protocol elements, more than one
connection can be established simultaneously with different remote stations, whereby no fixed
assignment of the remote terminal units to one specific master is required. By means of that
higher availability and higher data throughput is achieved.
Red Telephone
In the master station one interface can be established for dial-up traffic with a separate dial-up
modem as "Red Telephone". This interface is used by the master station only for incoming
calls. With that, at least one line is kept free for incoming calls in the central station for
important data from the remote terminal units.
In the remote terminal unit, commonly only one telephone number (main telephone number) of
the master station is parameterized. The stepping to the individual modems in the master
station is normally carried out by the function "Private branch series or telephone number
stepping" of the telephone system or by a corresponding service of the telephone network
operator.
An active connection setup is not carried out by the master station over this interface. The
function "Red Telephone" is only implemented in combination with the function "Multi-Master
in dial-up traffic" and is enabled in the expanded parameters with the parameter advanced
parameters | red telephone.
The failure management of the remote terminal units is carried out over the other interfaces in
multi-master dial-up traffic.
The modem for the "Red Telephone" can be supervised by a monitoring cycle (to all stations)
controlled by the protocol element or by user using PRE-control message.

Edition 06.2017, DC0-023-2.12
Common utilization of one modem by different interfaces
An "active interface" established by the redundancy state in dial-up traffic always requires one
specific transmission facility. A coordinated utilization of a transmission facility by several
different interfaces is not supported!
If interfaces are designed redundant, only one transmission facility is necessary. The active
interface carries out the control of the modem and the transmission of data – the passive
interface switches all interface lines to "tristate" and can perform a listening function of the
transmitted data in receive direction.
7.2.1 Security for Dial-Up Traffic
For the data communication using dial up mode a serial based communication protocol based
on IEC60870-5-101 with proprietary extensions will be used:
· Connection setup according AT-Hayes (Industrial standard for modem control)

· Authentication (Access control, LOGIN) in the private range of IEC 60870-5-101
· Data transmission with established connection according IEC 60870-5-101 (unbalanced)
· Disconnection control information in the private range of IEC 60870-5-101
à no verification of calling numbers!

à no scrambling of data during transmission!
The data transmission of telecontrol data in dial up mode is done in general via public
telephone network (PSTN, GSM and ISDN). This network enables worldwide access to each
station. To protect stations in dial up mode against unauthorized access, appropriate methods
are necessary.
Following methods can be used in controlling station (Master) and controlled stations (Slaves)
to protect the systems against unauthorized access and unauthorized manipulation when
using telecontrol data transmission in dial up mode:
· Call number concept

· Characteristics of communication protocol used
· Scrambling of data (actually not used)
· Identification of calling station
· Authentication (with Password and Validation Key)
7.2.1.1 Telephone Number Concept
By the use of "not published telephone numbers" in dial up mode the telephone numbers of
the stations are usually known only by a very little user circle (the insiders) and could not
easily found out by foreign parts. Although scanning the telephone numbers and an access
attempt would be theoretically possible this is not lucrative in comparison with Internet based
protocols because the required time for doing this is extensive.
A base protection offers a telephone number concept and can be improved by use of "closed
user groups" further.
The function "closed user groups" is a service of the telecom suppliers (but this service is not
supported by all suppliers) which enables making of a telephone call only between the fixed
phone numbers for the user group.
An access to the stations from "the outside" is not possible!

DC0-023-2.12, Edition 06.2017
7.2.1.2 Communication Protocol
By the use of a not published data communication protocol for the data transmission of
telecontrol data in the dial up mode detailed knowledge is required over the used protocol for
the access to the stations.
The data communication protocol used for transmission of telecontrol data in dial up mode
based on IEC60870-5-101 is a communication protocol used only in a very specific
technological segment of "telecontrol and automation systems". This communication protocol
is not in the main focus for usual hacking attacks such as Internet protocols like TCP/IP and
http.
The specific modifications of the protocol (such as authentication, additional check field,
station number concept) offers an additional protection which requires very detailed
knowledge of the communication protocol used for transmission of telecontrol data in dial up
mode.
In case of erroneous LOGIN the remote station will not sent data to or accept data from the
calling station. The connection will be released by the remote station after timeout.
The polling cycle used by the data communication protocol for transmission of telecontrol data
in dial up mode cause that the remote station will not send any spontaneous data after
connection setup. This means, the remote station will send data after connection setup only
after successful authentication and during valid polling procedure.
7.2.1.3 Scrambling
The data communication protocol for transmission of telecontrol data in dial up mode based
on IEC60870-5-101 does actually not support scrambling of data!
7.2.1.4 Identification of the Calling Station
After connection set-up by the remote station an identification of the remote station is carried
out by the master station using a "quick check procedure".
For this the master station sends a general query after Request for access demand according
IEC60870-5-2 ("Request status of link" as a broadcast message) to the remote station.
This message is acknowledged by the remote station by sending a "status of link" message
(including the link address of the remote station).
The master station supports only a communication from/to remote stations with registered
station numbers. The station numbers will be parameterized in the master station.
à No identification (validation) of the telephone number of the calling station!

Edition 06.2017, DC0-023-2.12
7.2.1.5 Authentication (Protection against not permitted access)
To increase the security against unauthorized access to the station in dial up mode the data
communication protocol used for transmission of telecontrol data in dial up mode based on
IEC60870-5-101 use an authentication (password and access key) after every connection set-
up.
The authentication (LOGIN procedure) will be done after each successful connection set-up
(doesn't matter if the connection set-up is initiated by the master station or by the remote
station) and after successful procedure for station identification.
The authentication will be controlled by the master station and confirmed after successful
verification by the remote station.
Possible methods for authentication:
· Basic Security: Password

· Enhanced Security: Password+ access key (for SICAM RTUs stations)
·
rd
Enhanced Security: Password + access key (for 3 party systems)
The method for authentication can be selected in the master station for each individual remote
station (default = enhanced security for SICAM RTUs remote stations). The modification of the
authentication method is only possible by specific authority and activation keys.
The method for authentication can be set in the remote station to "automatic detection" or set
to a specific authentication method. A deactivation of the authentication is not supported!
à For security reasons the security mode in the remote station should be set to
"Enhanced Security"!
rd
For interfacing 3 party systems supporting this communication protocol used for transmission
of telecontrol data in dial up mode an "authentication using password" or an "authentication
rd
using password + access key (for 3 party systems)" must be used.

DC0-023-2.12, Edition 06.2017
7.2.1.5.1 Authentication with Password
The authentication with password is only used in combination with older systems and enables
a basic protection "Basic security" against unauthorized access. This security mode is not
longer used with standard configurations (is used only for interfacing of older existing remote
stations or 3rd party systems which cannot be upgraded to "Enhanced Security Mode").
· The password is parameterized and stored in the master station and in the remote station
· The password + station number will be sent to the remote station after each connection
set-up included in the LOGIN-procedure (the password will not be scrambled)
· The remote station will verify the validity of the received password + station number after
each connection set-up
à if password + station number is valid a "positive activation confirmation" for the
LOGIN command will be sent to the master station
· Data transfer enable
à the master station enables the data transfer from/to the remote station only after
receiving a "positive activation confirmation" according the defined LOGIN procedure
à the remote station enables the data transfer from/to the master station only after
receiving a valid password " according the defined LOGIN procedure
7.2.1.5.2 Authentication with Password + Keys for SICAM RTUs
The authentication with "password + access key for SICAM RTUs remote stations" is used in
actual and new configurations as default and enables an extensive protection "Enhanced
Security" against unauthorized access in combination with easy parameterization. This
authentication method use a password and additional 2 different dynamic generated keys (64
bit each).
The keys (access activation key and access confirmation key) have a time-limited validity
implemented and therefore the keys will be different at every connection set-up!
The access to the SICAM RTUs remote station will be enabled only with valid password and
valid access activation key. The data transfer from the remote station will be activated in the
master station only after receiving a valid access confirmation key.
· The password is parameterized and stored in the master station and in the remote station
· The access activation key (64 Bit) is generated dynamically in the master station
· The password + access activation key + station number will be sent to the remote station
after each connection set-up included in the LOGIN-procedure (the password will not be
scrambled)
· The remote station will verify the validity of the received password + access activation key
+ station number after each connection set-up
à if password + access activation key + station number is valid a "positive activation
confirmation" for the LOGIN command will be sent to the master station including the
new generated access confirmation key.
à the master station checks also the validity of the access confirmation key
· Data transfer enable
à the master station enables the data transfer from/to the remote station only after
receiving a "positive activation confirmation" including a valid access confirmation key
according the defined LOGIN procedure
à the remote station enables the data transfer from/to the master station only after
receiving a valid password + access activation key according the defined LOGIN
procedure
This authentication method is only used for SICAM RTUs systems and this method will not be
published!

Edition 06.2017, DC0-023-2.12
7.2.1.5.3 Authentication with Password + Keys for 3rd Party Systems
The authentication with "password + access key for 3rd party remote stations" is actually not
used!
This authentication method will be published to manufacturer of 3 rd party system on request if

rd
3 party remote stations must be interfaced to SICAM RTUs master station and "Enhanced
Security" must be supported to increase protection against unauthorized access.
The authentication method is similar to the authentication with "password + access key for
"SICAM RTUs remote stations" but different methods for generating the keys will be used.
7.2.2 Connection Establishment spontaneously and cyclically,

Controlling Station <-> Controlled Station
With an error-free state, a connection setup by the master or remote terminal unit is always
initiated to the telephone number (first telephone number) of the remote station, which is set
according to the parameter connection setup | stand-by transm. line switchover
mode.
After a successful connection establishment, the following functions are performed:
· Access control (LOGIN with password)

· Clock synchronization of the remote terminal unit by the master station
· Transmission of the user data between master station and remote terminal unit
· GI-request of the master station to the remote terminal unit (optional)
The general interrogation function after every active connection establishment can be
activated in the master station with the parameter connection setup | Send online GI
with active connection setup. The general interrogation command is thereby generated
by the protocol element of the master station itself and transmitted to the remote terminal unit.

DC0-023-2.12, Edition 06.2017
Redials
If with an active connection setup attempt no connection can be established, the connection
setup attempt is repeated after a settable delay (Pause-1). After a settable number of dialing
attempts, if necessary switching to a differently parameterized delay (Pause-2) can be
performed.
If standby telephone numbers are also available for the connection setup to the remote
station, these can be used for redials. The use of main/standby telephone numbers is
established by the mode for connection setup – this is set with the parameter connection
setup | stand-by transm. line switchover mode. If no standby telephone number is
parameterized, all connection setup attempts are performed only to the parameterized main
telephone number.
Redials are thereby always performed directly one after the other on expiry of the
parameterized timeouts and delays. Redials from the master station to a remote terminal unit
are not interrupted by data to another remote terminal unit.
In the master station, if another remote terminal unit calls during a dialing pause for redials,
the handling for redials in progress is interrupted and the incoming call is accepted. After
termination of this connection, a new connection setup is performed to that remote terminal
unit whose redials were previously interrupted. For this remote terminal unit, the redials are
not resumed, rather started again.
If a connection still cannot be established after expiry of the parameterized maximum number
of dialing attempts, the remote station is reported as failed. In the master station, the message
not transmitted is discarded after expiry of the dialing attempts. In the remote terminal unit, the
message is negatively acknowledged to the basic system element and as a result offered for
transmission again until the dwell time for this message has expired. If no dwell time is
parameterized, this message is offered for transmission again and again.
If there is a message to be sent to a failed remote terminal unit or master station, with the
parameter connection setup | 1st dialling attempt with faulty station it can
be defined whether redials are to be performed or not.
After a successful connection establishment and communication with a previously failed or
unreachable remote station, the failure is reset and redials performed again from the next
connection setup.
If an existing connection is interrupted during a running station interrogation and there are no
more data or acknowledgements to be transmitted, a fault or warning is notified but the
connection is not re-established immediately. If there are still data to be transmitted,
afterwards a connection setup is performed again immediately.
The maximum number of dialing attempts is set with the parameter connection setup |
number of dialling attempts.
The delay (pause) between the dialing attempts is set with the parameter connection
setup | Pause -1 between dialling retries and the parameter connection setup
| Pause -2 between dialling retries. The switchover of the delay can be
parameterized with the parameter connection setup | Pause switchover at "n"
dialling retries.
If a passive connection triggering occurs during the transmission of data, then the message
sent but not yet acknowledged by the remote station is negatively acknowledged to the basic
system element (BSE) and transmitted again after the next connection establishment. A fault
is however only then set, if this faulty behavior occurs several times in succession. The limit is
set with the parameter connection setup | Failure number of attempts.

Edition 06.2017, DC0-023-2.12
Call acceptance (passive connection setup)
An incoming call is accepted either immediately or after a call acceptance delay.

The delay time for accepting an incoming call can be set with the parameter connection
setup | call acception delay.
Connection setup modes of the master station

If a second telephone number (standby telephone number) is parameterized for the remote
terminal unit in the master station in addition to the main telephone number, the connection
setup to the remote terminal unit is performed to that telephone number that is determined
with the selected "Mode for connection setup".
Depending on the "Mode for connection setup" for the selection of the telephone number the
criteria "Number of redials already performed", "PRE-control message (selection of the
telephone number)" or the moment in time are evaluated.
Use of telephone numbers during

connection setup
Telephone numbers Mode-0 Mode-1 Mode-2 Mode-3 Mode-4
(per remote terminal unit)
Main telephone number ü ü ü ü ü
Standby telephone number (optional) ü ü ü ü
The main telephone number of every remote terminal unit is to be set in the master station
with the parameters station definition | Main Tel No The standby telephone number
of every remote terminal unit is to be set in the master station with the parameters station
definition | Secondary phone number.

DC0-023-2.12, Edition 06.2017
Mode for Connection Setup Note

Mode-0 Main number A connection setup to the remote terminal unit is only performed to
the main telephone number.
Mode-1 Main number + standby number A connection setup to the remote terminal unit is always performed
to the main telephone number first.
à If the connection to the main telephone number cannot be

established, after a number of redials that can be set with the
parameter connection setup | Mode 1 switchover after
"m" dialling retrys | number of redials until
changeover ("m") , further dialing attempts are performed to the
standby telephone number.
Mode-2 Main number + standby number A connection setup to the remote terminal unit is always performed
(alternating telephone numbers) to the main telephone number first.

established, further dialing attempts are made alternating to the
standby telephone number and then to the main telephone number
again.
Mode-3 Main number + standby number A connection to the remote terminal unit is established either to the
(day/night operation) main telephone number or to the standby telephone number
depending on the time of day.
à The time range in which the main telephone number is used is

to be parameterized with the parameter connection setup |
Mode 3 day_night | day number - hour and with the
parameter connection setup | Mode 3 day_night | day
number - minute.
à The time range in which the standby telephone number is used

is to be parameterized with the parameter connection setup |
Mode 3 day_night | night number - hour and with the
parameter connection setup | Mode 3 day_night | night
number - minute.
Example: from 08:00 - 20:00 … connection to the remote terminal
unit only via the main telephone number
from 20:00 - 08:00 … connection to the remote terminal
unit only via the standby telephone number
Mode-4 Main number + standby number A connection to the remote terminal unit is established to that
(selection with PRE control telephone number (main or standby telephone number) selected
message) via PRE control message.
à If the connection to this telephone number cannot be

established, redials are only performed to the selected telephone
number.

Edition 06.2017, DC0-023-2.12
Connection setup modes of the remote terminal unit
If other telephone numbers (standby telephone numbers) are parameterized for the master
station in the remote terminal unit in addition to the main telephone number, the connection
setup to the master station is performed to that telephone number that is determined with the
selected "Mode for connection setup".
Depending on the "Mode for connection setup" for the selection of the telephone number the
criteria "Number of redials already performed", "PRE-control message (selection of the
telephone number)" or the moment in time are evaluated.
Use of telephone numbers during connection setup

Master Station Telephone Number(s) Mode-0 Mode-1 Mode-2 Mode-3 Mode-4 Mode-5
Main telephone number (MASTER 1) ü ü ü ü ü ü
Standby telephone number 1 (MASTER 1) ü ü ü ü ü
Standby telephone number 2 (MASTER 1) ü ü
Standby telephone number 3 (MASTER 1) ü ü
Main telephone number (MASTER 2) ü
Standby telephone number 1 (MASTER 2) ü
Connection Setup Mode Note

Mode-0 Main number A connection setup to the master station is only performed to the
main telephone number.
The main telephone number is to be set with the parameter

connection setup | Telephon number mode 0 | main
phone number.
Mode-1 Main number + standby number A connection setup to the master station is always performed to the
main telephone number first.

established, after a number of redials that can be set with the
parameter connection setup | Mode 1 switchover after
"m" dialling retrys | number of redials until
changeover ("m"), further dialing attempts are performed to the
standby telephone number.
phone number.
The standby telephone number is to be set with the parameter

connection setup | Telephon number mode 1 |
substitute phone number 1.
Mode-2 Main number + 3 standby A connection setup to the master station is always performed to the
numbers main telephone number first.
(alternating telephone numbers)
established, every other dialing attempt is performed to the next
parameterized standby telephone number.
If all parameterized standby telephone numbers have been used
for a connection setup, this is continued again with the main
telephone number.
phone number.
The standby telephone numbers are to be set with the parameter

connection setup | Telephon number mode 2 | *.

DC0-023-2.12, Edition 06.2017
Mode-3 Main number + standby number A connection to the master station is established either to the main
(day/night operation) telephone number or to the standby telephone number depending
on the time of day.
à The time range in which the main telephone number is used is

to be parameterized with the parameter connection setup |
Mode 3 day_night | day number - hour and with the
parameter connection setup | Mode 3 day_night | day
number - minute.
à The time range in which the standby telephone number is used

is to be parameterized with the parameter connection setup |
Mode 3 day_night | night number - hour and with the
parameter connection setup | Mode 3 day_night | night
number - minute.
Example: from 08:00 - 20:00 … connection to the master station
only via the main telephone number
from 20:00 - 08:00 … connection to the master station
only via the standby telephone number
phone number.

Mode-4 Main number + standby number A connection to the master station is established to that telephone
(selection with PRE control number (main or standby telephone number) selected via PRE
message) control message.
à If the connection to this telephone number cannot be

established, redials are only performed to the selected telephone
number.
phone number.

Mode-5 Standby transmission line via Remote terminal units are connected to the master station over the
dial-up traffic main transmission line (SICAM RTUs multi-point traffic or point-to-
point protocol). Every remote terminal unit is also equipped with a
dial-up modem. If the remote terminal unit is no longer reachable
on the main transmission line, a connection over the telephone
network (dial-up traffic) is established automatically.
à The standby transmission line over dial-up traffic is only

activated after that time that can be set with the parameter "Delay
time for selection of the standby transmission line". If the remote
terminal unit can be reached again on the main transmission line
during this delay time, the standby transmission line is not
activated.
à An activated standby transmission line over dial-up traffic is only

terminated after expiry of that time that can be set with the
parameter "Delay time after termination of the standby
transmission line".
The main telephone number for Master 1 is to be set with the
parameter connection setup | Telephon number mode 5 |
Master 1 main phone number.
The main telephone number for Master 2 is to be set with the
parameter connection setup | Telephon number mode 5 |
Master 2 main phone number.
The standby telephone numbers for the Master 1 and Master 2 are
to be set with the parameters connection setup | Telephon
number mode 5 | *.

Edition 06.2017, DC0-023-2.12
7.2.2.1 Cyclic Connection Setup at a settable Interval (monitoring cycle)
A cyclic connection setup can be performed by the master station as well as by the remote
terminal unit at a settable interval (monitoring cycle) and is used in particular for:
· Monitoring the station availability, monitoring the remote station

· Transmission of low priority data from the remote terminal unit to the master station
In the monitoring cycle of the master station, a connection setup is performed 1 x to every
parameterized remote terminal unit. Through the monitoring cycle, failed remote terminal units
are detected by the master station and signaled as failed.
In the monitoring cycle – triggered by the remote terminal unit, a connection setup is
performed 1x to the master station. Through this monitoring cycle, if necessary a failure of the
master stations can be detected by the remote terminal unit.
For failed remote terminal units, a cyclic monitoring can be performed - in a shorter time-scale
as required.
After a connection establishment during the monitoring cycle, the following functions are
always performed:
· Monitoring message (REQUEST STATUS OF LINK) is transmitted from the master station
to the remote terminal unit
· Transmission of low priority data from the remote terminal unit to the master station
(these data is stored in the remote terminal unit and first transmitted with the next
connection setup)
Spontaneous data from the master station to another remote terminal unit during a running
monitoring cycle are transmitted after the disconnection of an existing connection. The
monitoring cycle is thereby interrupted by spontaneous data and then resumed – these
remote terminal units are then no longer handled in the monitoring cycle.
Spontaneous data from the master station to that remote terminal to which a connection has
just been established through the monitoring cycle are transmitted immediately.
The monitoring cycle is enabled with the parameter advanced parameters | monitoring
times | carry out monitoring. The monitoring can thereby be performed cyclic, time-
controlled or time-controlled by the multimaster function on the basic system element.

DC0-023-2.12, Edition 06.2017
Cyclic monitoring
The cyclic monitoring starts after startup of the master or remote terminal unit after the very
first expiry of the parameterized monitoring time and is therefore not performed immediately
after startup and also not at defined absolute moments. In the remote terminal unit, the period
for cyclic monitoring is retriggered with every connection setup.
The cycle time for the cyclic monitoring can be set with the parameter advanced
parameters | monitoring times | cyclic monitoring | multiplicator and the
parameter advanced parameters | monitoring times | cyclic monitoring |
time base. The cyclic monitoring can be performed in the time range of 1x / minute to max.
1x / 42 days.
The cycle time for the cyclic monitoring of failed remote terminal units by the master station
can be set with the parameter connection setup | monitoring cycle for failed
stations. The cyclic monitoring of failed remote terminal units can be performed in the time
range of 1x / minute to max. 1x / 4 hours.
In the "Multi-Master" operating mode, cyclic monitoring is not supported.

(à Parameter error if cyclic monitoring is parameterized)
Time-controlled monitoring
With time-controlled monitoring, the monitoring cycle is started at defined absolute moments.
The moments are to be set with the following parameters:
Time Moment 1:
Ÿ advanced parameters | monitoring times | time controlled monitoring | time 1
hour
minute
Time Moment 2:
hour
minute
Time Moment 3:
hour
minute
Time Moment 4:
hour
minute

Edition 06.2017, DC0-023-2.12
Time-controlled monitoring by basic system element (multi-master)

For the multi-master operating mode in the master station, a time-controlled monitoring can be
implemented, controlled by the multi-master function of the basic system element. When the
moment for a monitoring cycle is reached on the basic system element, beginning from the
next minute a monitoring cycle over all assigned multi-master interfaces (except the interface
for "Red telephone") to the first remote terminal units is started. In a minute grid, a monitoring
cycle to the next remote terminal units is then initiated, until all remote terminal units have
been handled by this.
If the number of connected remote terminal units is greater than the number of multi-master
interfaces of a basic system element in the master station, then it is ensured, that every
modem also uses a multi-master interface and has thus been tested.
7.2.3 Connection Setup Control via Modem Commands
The connection setup is controlled, depending on the parameterized procedure, either with a
state line (telephone number of the remote station is stored in the modem) or with messages
for the control of the modem (telephone number is contained in the message).
Supported connection setup procedures:
· AT-Hayes
· AT-Hayes (ETSI)
· V.25bis (108.1)
· V.25bis (108.2)
· X.20
· X.28
In most cases the required procedure for the connection setup control is determined by the
transmission facility used (modem).
With the selection of a predefined transmission facility, the connection setup procedure is
determined automatically – with the selection of the "freely definable transmission facility" the
procedure can be set with the parameter Common settings | Modem free definable |
connection setup (procedure).
7.2.3.1 AT-Hayes
The Hayes command set (also AT command set) is a command set for the control of
modems. It was developed by the company Hayes, still applicable today as recognized
industry standard.
With the AT-Hayes commands, the modem is parameterized, the modem status interrogated,
the connection setup initiated and modem binary information transmitted.
The control of modems with AT-Hayes commands takes place only in Command Mode. With
established connection, the data is transmitted transparently with corresponding parameter
setting of the modems.

DC0-023-2.12, Edition 06.2017
7.2.3.2 AT-Hayes (ETSI)
The Hayes command set (also AT command set) is a command set for the control of modems
and has been expanded by ETSI (European Telecommunications Standard Institute)
especially for TETRA modems. The essential difference is in the different format for the return
information from the modem. (see also AT-Hayes)
7.2.3.3 V.25bis
According to the interface procedure for the V.25bis connection setup control, the following
methods of operation are provided:
· Method 108.1
The connection setup to the remote station in dial-up traffic is controlled with a state line.
The telephone number of the remote station is stored in the modem.
à This method can be implemented in remote terminal units in dial-up traffic.
· Method 108.2
The connection setup to the remote station in dial-up traffic is controlled with a message in
Command Mode. The telephone number of the remote station is stored in the terminal and
is transmitted to the modem with every connection setup.
à This method can be implemented in master stations and remote terminal units in dial-up
traffic.
7.2.3.4 X.20
X.20 is an ITU-T (CCITT) recommendation for interfaces between data terminal equipment
(DTE) and data transmission equipment (DÜE) for Asynchronous-Duplex-Transmission in
public telephone networks. X.20 defines a transmission procedure for the connection setup
between one data terminal equipment (DTE) and one transmission equipment (DCE) in Start-
Stop mode.
The X.20 interface is applicable for the Start-Stop mode, which is intended for transmission
rates between 50 Bit/s and 300 Bit/s according to X.1. The DÜE is used here purely as
converter between the interface lines and the transmission line.
The interface according to X.20 manages with one line each for the transmit and receive data,
in addition there is a return line (operating earth).
7.2.3.5 X.28
The X-recommendations of the ITU (CCITT) refer to the data transmission in public data
networks (PDN).
With the help of the X.28-interface data terminal equipment operating asynchronously can
access the data transmission service transferred by data packet. For the X.28-interface there
are three user classes provided, which differ in the transmission rate. The classes lie between
50 Bit/s and 1200 Bit/s. Network operators can however offer higher transmission rates.
The data terminal equipment (SICAM RTUs) is thereby coupled to a data transmission
equipment "PAD" (= Packed Assembler Disassembler).

Edition 06.2017, DC0-023-2.12
7.2.3.6 Arbitrary Main Telephone Number in a Telephone Network (PSTN)
For the establishment of a connection in dial-up traffic the telephone number of the remote
station is required.
To increase the availability in dial-up traffic, depending on operating mode there are one or
several standby telephone numbers available. If a remote station cannot be reached via its
main telephone number, it can be called over a standby telephone number – if such a one is
available.
The own telephone number must always be parameterized. This is transmitted to some
modems and can be used by the network operator for error detection.
e.g.: if an incorrect telephone number is parameterized in the master or remote terminal unit
and as a result a subscriber is called again and again by one modem.
Telephone numbers in the master station

In the master station the own telephone number and a main and standby telephone number
for each remote terminal unit can be parameterized.
The telephone numbers of the remote terminal units are entered for each RTU in the
parameters of the station definition.
For the parameterization of the telephone numbers, the following parameters are available:
· Own telephone number: with the parameter

Common settings | own phone number
· Main telephone number: per RTU with the parameter
station definition | Main Tel No
· Standby telephone number: per RTU with the parameter
station definition | Secondary phone number

DC0-023-2.12, Edition 06.2017
Telephone numbers in the remote terminal unit

In the remote terminal unit the own telephone number and up to 8 different telephone
numbers can be parameterized. With a connection setup, based on the parameter
connection setup | stand-by transm. line switchover mode, the parameter
connection setup | Pause switchover at "n" dialling retries, the error states
and the moment, it is decided, which telephone number is used.
For the transmission of SMS information, in addition an own telephone number to be
parameterized is used.
For the parameterization of the telephone numbers, the following parameters are available:
· Own telephone number:

Common settings | own phone number
· Main telephone number of the master: (based on the mode used for connection setup)
connection setup | Telephon number mode 0 | main phone number
connection setup | Telephon number mode 5 | Master 1 main phone number
connection setup | Telephon number mode 5 | Master 2 main phone number
· Standby telephone numbers of the master: (based on the mode used for connection
setup)
connection setup | Telephon number mode 1 | substitute phone number 1
connection setup | Telephon number mode 5 | Master 1 substitute phone
number 1
number 2
number 3
number 1
number 2
number 3
· Mobile telephone number (SMS recipient):

Common settings | Modem GSM-TC35 data box | mobile phone number (SMS-
receiver)

Edition 06.2017, DC0-023-2.12
Parameterization of the telephone numbers
The telephone number consists of max. 32 ASCII characters, whereby special characters –
depending on the selected connection setup procedure – can be inserted for special functions.
The own telephone number must always be parameterized. This is transmitted to certain
modems and used for diagnostic purposes.
Permissible Characters in the parameterized Telephone Number

AT-Hayes V.25bis (108.1) V.25bis (108.2) X.20 X.28
Telephone number 0…9 0…9 0…9 0…9
Wait until dialing tone detected : :
(continuous tone)
Dialing pause 1 second < <
Dialing pause 3 seconds = =
Dialing pause for AT-Hayes modems ,
Press earthing key > >
Flash key & &
Pulse dial P P
Tone dial T T
End of the telephone number *) <BLANK> <BLANK> <BLANK> <BLANK> <BLANK>
*) the end of the telephone number is defined with <BLANK> (=space)
Note:
With the parameterization of the telephone number, the non-used characters at the end of the
telephone number are filled automatically by the OPM with <BLANK's>.
à if the telephone number is now to be changed and additional characters are required for
this, then the <BLANK's> at the end of the telephone number must be deleted before
entering the new characters.
Example:
0.01291290 … getting a trunk line with the numeral <0>, dialing pause with the character <,>

DC0-023-2.12, Edition 06.2017
7.2.4 Access Control (LOGIN with Password + Access Key)
To increase the security against unauthorized access, after a successful connection

establishment (regardless whether the connection setup has been initiated by the master
station or remote terminal unit) a login procedure with password and access activation key
verification is performed in the private range of IEC60870-5-101.
After the connection establishment, an identification of the remote terminal unit is performed
by the master station with a "Quick-Check procedure". For this, the master station sends a
general request to the remote terminal unit for access request ("Request Status of Link" as
broadcast message). This message is replied to by the remote terminal unit with a "Status of
Link" (with the link address of the remote terminal unit).
If the station address of the remote station is not parameterized in the master station, the
master station will not start the "Quick-Check procedure" and the remote station will set the
error “modem blocked”. During “modem blocked” the remote station will not initiate a dial-up
procedure. Only a dial-up sequence initiated by the master station to the specific remote
station will reset the error and release the „modem blocked mode”.
After the connection establishment and the procedure for station identification, the LOGIN
procedure is initiated by the master station. The master station sends a LOGIN-message to
the remote terminal unit with the password parameterized in the master station and a dynamic
generated access activation key. If the identified remote terminal unit is not parameterized in
the master station or is dynamically deactivated or the access-key is not valid, the LOGIN-
message is sent with the password "BLOCK". The LOGIN-message is acknowledged by the
remote terminal unit.
· Positive confirmation
If in the remote terminal unit, the password received matches the password parameterized
in the remote terminal unit and the access activation key is valid, the transmission of user
data to the master station is enabled and the LOGIN-message sent with positive
confirmation and generated access reply key during the following station interrogation.
The data transmission from the remote terminal unit to the master station is activated and
a possibly present fault "Modem blockade" is reset.
· Negative confirmation
If the password does not match or the password "Block" has been received or the access
activation key is not valid, the remote terminal units sends the LOGIN-message with
negative conformation and the data transmission from the remote terminal unit to the
master station remains blocked.
With negative confirmation, the master station nevertheless sends user data to the remote
terminal unit – these are discarded in the remote terminal unit.
The connection remains established at most until the maximum connection time – the
connection time is however not retriggered.
The remote terminal unit sends no data to the master station.
In the master station, the warning "Modem blockade of Station-x" is signaled.
In the remote terminal unit, the warning "Dialing blockade due to false password" is
signaled.
The password is parameterized in the master station and in the remote terminal unit for each
protocol element for dial-up traffic with the parameter Common settings | Login
password.
Note:
With the parameterization of the password, the non-used characters at the end of the
password are filled automatically by the OPM with <BLANKs>.
If the password is now to be changed and additional characters are necessary for this, then
the <BLANKs> at the end of the password must be deleted before entering the new
characters.
The access control (LOGIN with password + access key) takes place with a message in the
private range of the IEC 60870-5-101 with type identification <TI:=146>.
The LOGIN procedure can not be deactivated with a parameter setting!

Edition 06.2017, DC0-023-2.12
7.2.5 Disconnection Control
Dial-up communication protocol for SICAM RTUs use “disconnect Control in the private
Range of IEC60870-5-101”.
For the cost-optimized transmission of data in dial-up traffic, the connection should only then
be established when it is really required and a connection should thereby only be established
as long as absolutely necessary.
An existing connection in dial-up traffic is normally only disconnected by the master station at
the earliest after the "minimum connection time" in the following cases:
· The maximum connection time is reached

· The connection time per type identification has elapsed and the remote terminal unit has
no more data to transmit
· The remote terminal unit has no more data to transmit
An existing connection in dial-up traffic is disconnected by the remote terminal unit in the
following cases:
· The remote terminal unit does not dial the master station due to an incorrectly
parameterized telephone number.
· The disconnection has been performed by the master station, but the modem in the
remote terminal unit does not detect the connection as terminated. *)
· With connection established, the remote terminal unit is no longer called by the master
station within a time that can be set with the parameter advanced parameters |
monitoring times | timeout station call. *)
______
*)
the cause for these problems is in most cases a faulty or incorrectly switched DCD state line
The disconnection control is initiated by the master station with the message "HANG UP
DIALED LINE" (in the private range of IEC 60870-5-101) to the remote terminal unit with the
cause of transmission "ACTIVATION". As soon as the remote terminal unit has received this
message, no more data for transmission are received from the basic system element.
Afterwards the master station sends one more interrogation message for class 2 data in order
to still fetch data that are already prepared for transmission in the remote terminal unit. After
that the connection is disconnected by the master station.
If the "Multi-Master" function is used in the master station, the master station always
terminates the connection to a station, so that the next connection setup to this station is
always performed with FCB-Bit=1 (Frame Count Bit). Through this it is ensured, that with a
connection setup over another multi-master interface, the FCB-Bit has the correct status.
The connection time can be transmitted to the basic system element from the protocol
element as protocol element return information. On the basic system element, if necessary
this can be distributed for further processing in the system. In the master station the
connection time is managed for each remote terminal unit. The connection time can be
generated as absolute value or as relative value.
The connection time as absolute value is the sum of the connection times to one remote
terminal since reset or since the last reset of the connection time counter with PRE control
message.
The connection time as relative value is the connection duration of the last connection.
Whether the connection time counter is to be managed as absolute value or relative value can
be set with the parameter advanced parameters | connection time counter.

DC0-023-2.12, Edition 06.2017
Maximum connection time
With connection established, the connection is terminated by the master station on expiry of
the maximum connection time at the latest (regardless of "connection time per message type"
or if the remote terminal unit still has more data to transmit). The maximum connection time is
to be set in the master station with the parameter advanced parameters | monitoring
times | connection time maximum.
Minimum connection time

An established connection is terminated at the earliest after expiry of the minimum connection
time if the remote terminal unit has no more data to transmit. The minimum connection time is
to be set in the master station with the parameter advanced parameters | monitoring
times | connection time minimum.
Note:
If the connection setup is initiated by PRE control message and a minimum connection time is
configured with parameter ‘’Z-Par”, the parameter connection time minimum is ignored.
Remote terminal unit has no more data to transmit

An established connection is terminated prematurely by the master station if no message-type
specific connection time is active and the remote terminal unit has no more data to transmit. If
the remote terminal unit has no more data to transmit, station interrogations of the master
station are replied to by the remote terminal unit with short acknowledgements (=single
character "E5H"). The connection is disconnected by the master station after a parameter-
settable number of short acknowledgements in succession. The number of short
acknowledgements for the premature connection release is to be set in the master station with
the parameter advanced parameters | monitoring times | connection
initiation no data.
Connection time per message type
After the transmission of certain messages in transmit or receive direction, the connection can
remain established for a settable time, controlled by the master station, even if the remote
terminal unit has no data to transmit during this time.
This function enables the master station to transmit a command or setpoint value to the
remote terminal unit in the same connection establishment and to acquire a binary information
or measured value change (caused by the command or setpoint value).
With remote parameterization, remote diagnostic and firmware loading of the remote terminal
unit, the connection must also be established for longer and consequently the "maximum
connection time" set accordingly.
The "connection time per message type" is retriggered with each message of the selected
type identifications. An established connection is terminated prematurely by the master station
after expiry of the "connection time per type identification", if the remote terminal unit has no
more data to transmit.
A connection is terminated by the master station at the latest after expiry of the maximum
connection time.

Edition 06.2017, DC0-023-2.12
For the transmission of the following messages, the connection must not be terminated
prematurely:
· System messages for loading the firmware

· System messages for remote parameterization
· System messages for remote diagnostic
· Command or setpoint value with continuous call of a remote terminal unit (demand)
The selection of the type identification and setting of the connection time for type identification
necessary for the connection time per message type can be performed in the parameters
advanced parameters | connection time for each type identification | *.
For system messages (system data container with type identification TI=135), in addition the
connection times can be parameterized for 10 freely selectable function codes.
The selection of the function codes and setting of the connection time can be carried out in the
parameters advanced parameters | connection time for TI 135 | *.
Function Code Function Connection Designation

(Index) Code Time (default)
Function code A 128 20 sec Service command with confirmation
Function code B 129 20 sec Service reply
Function code C 130 20 sec Service message SK-format
--- 131 --- Service command without confirmation
In the system message container, all system messages are transmitted that are not covered
by the public range (remote parameterization, firmware loading, …).

DC0-023-2.12, Edition 06.2017
7.3 Communication with existing Connection according to

IEC 60870-5-101
With connection established, the data traffic is controlled by the master station.
If the connection setup has been carried out by the remote terminal unit, the master station
still requires the station address for the cyclic station interrogation with connection
established. The link address of the remote terminal unit (=station address) is determined by
the master station with a "Quick-Check Procedure". For this, the master station sends a
general request to the remote terminal unit for access request ("Request Status of Link" as
broadcast message). This message is replied to by the remote terminal unit with a "Status of
Link" (with the link address of the remote terminal unit).
The transmission of the data from the remote terminal unit to the master station with
established connection takes place by means of station-selective station interrogations
(interrogation procedure, polling), controlled by the master station; i.e., changed data is stored
in the remote terminal unit and transmitted to the master station with the interrogation of this
remote terminal unit. The interrogation procedure of the master station ensures, that the
remote terminal unit to which the connection has been established is interrogated permanently
as long as the connection exists. The remote terminal unit may only then transmit data when it
is called.
The interrogation procedure in dial-up traffic cannot be influenced with parameters!
The station-selective parameters of the master station for dial-up traffic, such as "Stat No",
"Station enable", "Station failure", "Main telephone number", "Standby telephone number",
"BD Main number", "BD Standby number" and "RTU modem” are to be set in the parameters
stationdefinition.
In every remote terminal unit, the station-selective address (= station address) must be set
with the parameter Common settings | Address of the link. This address must be
unambiguous for each dial-up traffic line.
The length of the "Address field of the link layer (number of octets)" is fixed for dial-up traffic at
1 octet in the master station and in the remote terminal unit.
In dial-up traffic with connection established, data and system messages are always
transmitted selectively and acknowledged from the master station to the remote terminal unit
during the running interrogation cycle.
Data to all remote terminal units are either already handled by the basic system element itself
or station-selective by the protocol element.
With the redundancy state "Passive", no connection setup is carried out by the master station
and no station interrogation takes place. In addition, messages to be sent are not transmitted
from the master station to the remote terminal units, rather discarded directly on the basic
system element (BSE) by the function "User data filter".
For the coupling of different systems with the IEC 60870-5-101 protocol in dial-up traffic, the
setting of the variable elements of the message is required. These parameters are shown in
the Interoperability List or the corresponding description.

Edition 06.2017, DC0-023-2.12

1)
IEC 60870-5-101 Parameter Description System Element Octets
Address field of the link (number) Number of octets for the address field of the --- 1
link layer
Cause of transmission (COT) Number of octets for cause of transmission BSE 2
Common address of ASDU Number of octets for common address of BSE 2
(CASDU) the ASDU
Information object address (IOA) Number of octets for the address of the BSE 3
information object
Acknowledgement IEC 60870-5-2 Acknowledgement on IEC 60870-5-2 layer --- 2)
1) the number of octets are fixed by the dial-up protocol and may not be changed!
2) as "acknowledgement to IEC 60870-5-2 layer" only the single character is used for dial-up traffic
Legend:
SSE ........... supplementary system element (with serial interfaces this is always configured with a PRE)
PRE ........... Protocol element
BSE ........... Basic system element
The "Continuous interrogation of a remote terminal unit in dial-up traffic" is always performed
with connection established. The master station thereby carries out a permanent station
interrogation for the duration of the connection only to that remote terminal unit to which a
connection is established.
The duration of the connection can be controlled dynamically within the maximum connection
time through the parameterization of the connection time per message type. The connection
time per message type is retriggered with the parameterized time with each message.
Through the continuous interrogation, following a message transmission (e.g. command,

setpoint value) the master station can quickly fetch changed data from the remote terminal
unit (e.g. measured values after command or setpoint value). The continuous interrogation is
terminated after expiry of the connection time.
During "continuous interrogation of one remote terminal unit" no data ate transmitted to other
remote terminal units. These remain stored on the basic system element and are transmitted
after disconnection of the connection.
The connection setup can also be carried out with protocol control messages. Thereby, the
connection time and thus the continuous interrogation of a remote terminal unit can be
determined independent of the parameter setting. For spontaneous messages to the remote
terminal unit, the connection time is determined by the connection time per message type.
The maximum connection time is however always limited by the parameter setting.

DC0-023-2.12, Edition 06.2017
With connection established, all data messages transmitted to a remote terminal unit must be
acknowledged by this RTU. If, with non-faulty transmission line, the acknowledgement is
missing for longer than the expected acknowledgement time, transmitted messages are
repeated up to n-times (n can be parameterized). On expiry of the number of retries, the
remote terminal unit is flagged as faulty. The connection remains established – further
messages are transmitted without retries.
The connection is terminated by the master station at the latest after expiry of the maximum
connection time.
For the automatic determination of the expected acknowledgement time, the times of the
selected transmission facility in the remote terminal unit are also taken into consideration by
the DIAMA0 protocol firmware.
parameter Message retries | Retries for INIT-messages SEND/CONFIRM
(station selective).
In the master station, in addition the number of retries for the "Quick-Check-Procedure" for
interrogation for access request can be set with the parameter Message retries |
Retries for Request after access inquiry.
The acknowledgement from the remote terminal unit to the master station is transmitted as
single character (E5).
The monitoring of the remote terminal unit by the active master station with connection
established takes place by means of the cyclic running interrogation procedure (station
interrogation).
If there are no user data to be transmitted, the remote terminal units are monitored by the
cyclic or time-controlled monitoring cycle. In the monitoring cycle of the master station, a
connection setup is performed 1 x to every parameterized remote terminal unit. Through the
monitoring cycle, failed remote terminal units are detected by the master station and signaled
as failed.
With connection established, a remote terminal unit is reported as failed by the master station
after expiry of the number of retries. Retries to a remote terminal unit are thereby always sent
in succession immediately after expiry of the expected acknowledgement time i.e. the
connection is not disconnected and no other remote terminal units are interrogated during a
running retry handling. For failed remote terminal units, a communication fault is only then
reported, if this is parameterized accordingly in the parameter Stationsdefinition |
Station failure.
With connection established, the failure of remote terminal units is thus detected by the
master station during the normal interrogation cycle or the monitoring cycle. Failed remote
terminal units continue to be interrogated by the master station in the monitoring cycle.
Redials to failed remote terminal units can be deactivated with the parameter connection
setup | 1st dialling attempt with faulty station.
For failed remote terminal units, a cyclic monitoring can be performed - in a shorter time-scale
as required. The time-scale can be set with the parameter connection setup |
monitoring cycle for failed stations.

Edition 06.2017, DC0-023-2.12
Data from the master station to the remote terminal unit which could not be transmitted during
the redials are discarded.
In the remote terminal unit, with connection established, the monitoring of the master station is
carried out by the function "Monitoring for cyclic message reception“.
If there are no user data to be transmitted, if necessary the remote terminal unit can monitor
the master station with the cyclic or time-controlled monitoring cycle. In the monitoring cycle of
the remote terminal unit, a connection setup is performed 1 x to the master station. Through
the monitoring cycle, a failed master station is detected by the remote terminal unit and
signaled as failed.
The monitoring time for cyclic message reception is to be set in the remote terminal unit with
the parameter advanced parameters | monitoring times | timeout station call.
This monitoring time is retriggered in the remote terminal unit by station-selective call
messages or station-selective data messages. If the monitoring time elapses, the connection
is terminated by the remote terminal unit.
After a connection setup, the station initialization is performed by the master station in the
following cases:
· After restart of the master station or remote terminal unit

· After redundancy switchover of the master station
· After going interface failure of a remote terminal unit
After successful station initialization, with a connection setup no further station initialization is
performed.
with:

- Acknowledgement for RESET OF REMOTE LINK is
The end of initialization according to IEC 60870-5-101 is not supported by this protocol
element!

DC0-023-2.12, Edition 06.2017
Data that are to be transmitted from the remote terminal unit to the master station are stored
on the basic system element (BSE) in the remote terminal unit until transmission.
In dial-up traffic, the remote terminal unit itself can establish a connection to the master station
and in this way ensure a fast transmission of the data. Data that are not to be transmitted
immediately, are stored in the remote terminal unit and transmitted during the next connection
setup.
For special applications (redundancy configurations or standby transmission line operation via
dial-up traffic) all data to be transmitted can be deleted in the remote terminal unit as long as
no connection is established. This function can be set in the remote terminal unit with the
parameter advanced parameters | behavior if connection is not established.
With connection established, messages from the remote terminal unit to the master station are
only transmitted with station interrogation. A quick-check procedure for speeding up the
transmission of data is not implemented.
In dial-up traffic, the general interrogation of remote terminal units must be carried out station-
selective by the master station and due to the connection setup required to every selective
remote terminal unit according to the transmission facility used / number of remote terminal
units and the parameters set for connection time, takes accordingly long (up to 1 hour and
even more).
terminal units.
For communication in dial-up traffic, the general interrogation function can be triggered after
every active connection setup by the master station. This function can be activated in the
master station with the parameter connection setup | Send online GI with active
connection setup. The general interrogation command is thereby generated by the protocol
element of the master station itself and transmitted to the remote terminal unit.

Edition 06.2017, DC0-023-2.12
Setting the time
In dial-up traffic, the clock of remote terminal units can be set and synchronized by the master
station over the communications link.
In dial-up traffic, the setting of the clock of remote terminal units must be carried out station-
selective by the master station and due to the connection setup required to every selective
remote terminal unit according to the transmission facility used / number of remote terminal
units and the parameters set for connection time, takes accordingly long (up to 1 hour and
even more).
A clock synchronization is performed by the master station immediately after every connection
setup (regardless whether spontaneous or cyclic, initiated by the master or remote terminal
unit) – with connection established cyclic every minute, as long as the connection exists.
The clock synchronization command is not transmitted spontaneously by the protocol element
of the master station with a change of the time.
For switchover from/to daylight-saving time, so that this can be performed punctually in
remote terminal units, this is emulated by the protocol firmware in the remote terminal unit.
The moments for the switchover from/to daylight-saving time are parameterized in the remote
terminal unit on the basic system element in the parameters for time management.
Messages that are transmitted from the remote terminal unit after a startup, but before the
remote terminal unit has the correct time, contain the relative time from startup (reference day:
1.1.2001) with the flagging of the time tag as invalid.
Remote Synchronization
In dial-up traffic, the clock synchronization of the remote terminal units can be performed
cyclic over the serial communications link – controlled by the master station. The remote
synchronization is performed in the monitoring cycle.
Due to the cost-optimized transmission in dial-up traffic (typical remote synchronization 1x /

day) and the delayed transmission of data in the telephone network (especially with GSM), the
accuracy that can be achieved is rather modest. The achievable accuracy is also dependent
on the quartz used in the electronics of the remote terminal unit.
Remote Synchronization 1x / Day

Quartz Accuracy Max. Inaccuracy Max. Inaccuracy Example
[per hour] *) [per day] *)
-5
10 360 ms 8.6 sec AK 1703
-4
10 3.6 sec 86.4 sec SICAM MIC
*) Inaccuracy due to the delay of the data transmission in the telephone network is NOT taken into
consideration here.i.e. depending on the transmission facility used, additional delays are also
possible here
be used in the remote terminal unit.

DC0-023-2.12, Edition 06.2017

Terminal Unit
Demand
If the reaction from the remote terminal unit to a transmitted message is to be acquired quickly
by the master station, the connection – controlled by the master station – can remain
established for a settable time, even if the remote terminal unit has no data to transmit during
this time.
This function enables the master station to transmit a command or setpoint value to the
remote terminal unit in the same connection establishment and to acquire a binary information
or measured value change (caused by the command or setpoint value).
The "connection time per message type" is retriggered with each message of the selected
type identifications. An established connection is terminated prematurely by the master station
after expiry of the "connection time per type identification", if the remote terminal unit has no
more data to transmit.
A connection is terminated by the master station at the latest after expiry of the maximum
connection time.
The selection of the type identification and setting of the connection time for type identification
necessary for the connection time per message type can be performed in the parameters
advanced parameters | connection time for each type identification | *.
For system messages (system data container with type identification TI=135), in addition the
connection times can be parameterized for 10 freely selectable function codes.
The selection of the function codes and setting of the connection time can be carried
out in the parameters advanced parameters | connection time for TI 135 | *.

Edition 06.2017, DC0-023-2.12
authority.
correspond with the control location previously set.
the control locations previously set or if no control location has been preset:

the PRE.

0 Not defined
Note:
control function.
enabled").
enabled").

DC0-023-2.12, Edition 06.2017

(unacknowledged)
In dial-up traffic, unacknowledged messages from the master station to all remote terminal
units are not supported!
Since a BROADCAST-transmission is not possible in dial-up traffic, messages to all must

always be transmitted selectively to all remote terminal units.
In dial-up traffic, the counter interrogation command to remote terminal units must be
transmitted station-selective by the master station and due to the connection setup required to
every selective remote terminal unit according to the transmission facility used / number of
remote terminal units and the parameters set for connection time, takes accordingly long (up
to 1 hour and even more).
A counter interrogation command "to all" triggered in the system is always transferred by the
terminal units.
In dial-up traffic, the protocol element of the remote terminal unit does not support "Acquisition
of the transmission delay" and the correction of the time resulting from this for clock
synchronization according to IEC 60870-5.
The protocol element of the master station uses a SICAM RTUs specific method for the
"acquisition of transmission delay". With this method, the transmission delay is always
determined after connection setup by the master station with the procedural sequences
"Request Status Of Link" and the reply from the remote terminal unit "Status of Link" and a
correction value derived automatically from this.
With connection established, the clock synchronization command is transmitted from the
master station selectively to the connected remote terminal unit. The time in the clock
synchronization command is already corrected by the protocol firmware of the master station
with the automatically determined correction value.

Edition 06.2017, DC0-023-2.12
7.4 SMS Messages
The remote terminal unit in dial-up traffic can also transmit SMS messages (Short Message
Service) to a parameterized telephone number (mobile telephone) with the GSM-Modem
"Siemens TC35, Cinterion MC52iT". For the transmission of SMS messages, no connection is
established to the master station for the transmission of data. The transmission of an SMS
message (ASCII text) to the GSM-modem is carried out with the AT-Hayes commands
implemented in the GSM-Modem for the transmission of SMS messages.
SMS messages are transmitted to the telephone number (mobile phone) parameterized with
the parameter Common settings | Modem GSM-TC35 data box | mobile phone
number (SMS-receiver). The transmission of the SMS messages takes place
unacknowledged.
SMS messages are triggered with messages for protocol element control.
Format of the SMS message: [designation of the remote terminal unit]:[ASCII text of the SMS
message]
Example: Transformer station Siemensstraße: Transformer voltage Phase

3 failed
Date + Time for the SMS messages is presently not transmitted by the remote terminal unit.
In the remote terminal unit, freely parameter-settable ASCII texts for max. 10 different SMS
messages can be parameterized with the parameters Common settings | Modem GSM-
TC35 data box | #. SMS information. In addition, with the parameter Common
settings | Modem GSM-TC35 data box | Name of the RTU for SMS an
unambiguous designation of the remote terminal unit can be parameterized. This is always
sent together with the transmission of an SMS message.

DC0-023-2.12, Edition 06.2017
7.5 Co-ordination of several Masters in "Multi-Master Mode"
In the so-called multi-master mode, provided there are several dial-up modems available in
the master station and just as many SM-25xx/DIAMxx protocol elements, more than one
connection can be established simultaneously with different remote stations, whereby no fixed
assignment of the remote terminal units to one specific master is required. By means of that
higher availability and higher data throughput is achieved.
For the data transmission to a remote terminal unit, the multi-master function on the basic
system element decides over which assigned protocol element the data is sent. If a message
cannot be transmitted over one multi-master interface, this is transmitted from the basic
system element over one of the remaining multi-master interfaces.
The data transmission is ended when the data have been deleted on the basic system
element by the dwell time monitoring or the data could not be successfully transmitted over
any of the interfaces.
Through protocol element control messages, a connection setup/disconnection to the remote

terminal unit can be performed over a specific selected protocol element or by a protocol
element selected by the multi-master function on the basic system element.
In multi-master mode, a remote terminal unit is only then signaled as failed by the basic
system, if this cannot be reached over any of the assigned protocol elements.
The multi-master mode can only be used with the protocol elements of the assigned basic
system element. An independent multi-master function can be implemented on any basic
system element. A multi-master mode is not possible with protocol elements of another basic
system element!
For the multi-master mode, all assigned interfaces with master function (MASTER) must be
parameterized identically!
In multi-master mode, the connection time counters in the protocol element return information
are only transferred from the protocol element of the master station as relative values
(=connection time of the last connection).
In multi-master mode, no standby number is supported for the connected remote terminal
units!

Edition 06.2017, DC0-023-2.12
7.6 Standby Transmission Line(s) over Standby Telephone

Number(s)
In dial-up traffic – provided there are several modem connections in the master station or
remote terminal unit – standby transmission lines can be realized over standby telephone
numbers in the same or another telephone network (PSTN). This way, a remote terminal unit
can call the master station over a standby telephone number, if the master station cannot be
reached with the main telephone number.

DC0-023-2.12, Edition 06.2017
7.7 Multi-Hierarchical Configurations
In dial-up traffic, multi-hierarchical configurations can also be realized. This means that
additional stations can be connected to a dial-up remote station, also using different
communication protocols.

Edition 06.2017, DC0-023-2.12
7.8 Standby Transmission Line via Dial up Traffic
The data transmission between master station and the remote terminal units during fault-free
operation is carried out over the main transmission line in point-to-point or multi-point traffic -
for SICAM RTUs also over LAN. Every remote terminal unit is also equipped with a dial-up
modem. If the remote terminal unit is no longer reachable on the main transmission line, a
connection over the standby transmission line (telephone network) is established
automatically. For remote terminal units in multi-point traffic, a station-selective switchover to
the standby transmission line takes place.
Schematic configuration for standby transmission line operation over public telephone network
(PSTN):
Master station
Ax/ACP-1703 Basic system element (BSE)
Œ Œ Œ • • • •
ETA2 BPPxx UMPMxx DIAMxx DIAMxx DIAMxx DIAMxx

“Main transmission line“ “Main “Main “Standby “Standby “Standby “Standby
(only ACP 1703) transmission line“ transmission line“ transmission line“ transmission line“ transmission line“ transmission line“
(SSE = 128) (SSE = 129) (SSE = 130) (SSE = 131)
TF TF MODEM MODEM MODEM MODEM

Telephone network
“PSTN“

Standby transmission line
MODEM TF MODEM TF MODEM TF MODEM
ETA2 DIASxx UMPSxx DIASxx UMPSxx DIASxx UMPSxx DIASxx
Remote station-1
(only ACP 1703) Remote station-2 Remote station-3 Remote station-n
Legend:
TF ………..….. Transmission facility
Œ …………….. Failed remote stations are signaled to the basic system element (BSE) or will be detected from the BSE.
• …………….. If required, a connection to a failed remote station can be established from the BSE via the standby transmission line .

DC0-023-2.12, Edition 06.2017
Standby transmission line via dial up traffic:
· Multi Master function required for standby transmission line

· For a standby transmission line, one or several main transmission lines are supported
· The protocols for main-/standby transmission line must be always within the same
automation unit
· Standby transmission line configurations in hierarchical configurations are supported
(scaling of the timeouts for each hierarchical section required)
· Automatic switchover to the standby transmission line in case of failure of the main
transmission line (failure monitoring via keep-alive message timeout). If the main
transmission line is OK again, an automatic switchover will be done for activating the main
transmission line again.
· "Connection setup mode" must be set to "mode-5" in the remote station
· If master station does not use redundant dial up masters (only “Master 1”), parameters for
telephone numbers for Master 2 in dial up slave must be parameterized with telephone
numbers for Master 1!
In the remote terminal unit (Ax 1703) the assignment of the interface for main transmission
line and stand-by transmission line is defined on a basic system element as follows:
Main Line Standby Line Note

SSE = 128 SSE = 129 The SSEs for main/standby transmission line must be on the same
BSE.
SSE = 130 SSE = 131
Legend:
SSE supplementary system element (with serial interfaces this is always configured with a PRE)
PRE Protocol element
BSE Basic system element
In the Ax 1703 remote terminal unit, for the interfaces (main transmission line + standby
transmission line) the "Data Split Mode" must be used for the communication to redundant
remote stations. In the remote terminal unit, the data is only to be routed for the main
transmission line. The activated standby transmission line is reported by the protocol element
for dial-up traffic in the remote terminal unit to the assigned protocol element for main
transmission line. As a result a failure of the main transmission line is detected early in the
remote terminal unit and the measures required for activating the standby transmission line
are implemented.
In SICAM RTUs the assignment of the interface for main and standby transmission line is not
defined. The parameter setting of main-/standby transmission line is carried out in the
topology. From this parameter setting the routing of the internal protocol control messages
necessary for the coordination is also derived.
The remote terminal units are interrogated by the master station predominantly on the main
transmission line. If the protocol element of the master station detects a remote terminal unit
on the interface of the main transmission line as failed, then this is reported to the basic
system element (BSE) as failed.
The failure of the remote terminal unit is detected on the basic system element either by
means of the station failure information (Ax 1703) or by means of special "Keep Alive"
messages (SICAM RTUs) transmitted cyclic by the remote terminal unit.

Edition 06.2017, DC0-023-2.12
The standby transmission line operation over dial-up traffic is only activated to a remote
terminal unit no longer reachable on the main transmission line after a time that can be set
with the parameter Redundancy | delay time for activation of stand-by
transmission line. The standby transmission line establishes a connection to the remote
terminal unit over the public telephone network (PSTN). If the remote terminal unit can be
reached again on the main transmission line during this delay time, the standby transmission
line operation is not activated. The connection to the remote terminal unit over the standby
transmission line is only established if there are data to be transmitted. The connection time is
limited by the parameter for the limitation of the connection time.
When the remote terminal unit can be reached again on the main transmission line, the
standby transmission line operation over dial-up traffic to this remote terminal unit is
terminated again after a time that can be set with the parameter Redundancy | delay
time after finalizing of the stand-by trans. line.
Failed remote terminal units continue to be also interrogated on the main transmission line. If
a failed remote terminal unit can be reached again on the main transmission line, the standby
transmission line handling is terminated for this after a delay time.
The standby transmission line is tested by the cyclic monitoring function of the master station.

DC0-023-2.12, Edition 06.2017

Facilities
The protocol element supports selected transmission facilities - for these the essential
parameters are set fixed – the selection of the transmission facility is carried out with the
parameter Common settings | interface modem. Some transmission facilities require
additional parameters – these are then to be set according to the application.
By selecting the "freely definable transmission facility" certain parameters can be set
individually.
Note:
After modem exchange (or for some modems also after switching on the supply voltage again)
it is advisable to perform a reset of the master or remote terminal unit! With that it is ensured
that the modems are loaded with the default settings.

Edition 06.2017, DC0-023-2.12
Settings for all supported modems

· Transmission rate
Transmission facilities mostly support only certain baud rates – these are shown in the
descriptions for the transmission equipment.
The transmission rate (baud rate) for the transmission of data is to be set according to the
transmission facility used, for transmit/receive direction together with the parameter data
mode baud rate in the "General Settings" of the selected transmission facility, e.g.:
Common settings | Modem GSM-TC35 data box | data mode baud rate
The transmission rate (baud rate) for the transmission of commands to the modem is set
fixed according to the transmission facility used and can not be changed.
· AT-Hayes Commands
For modems that are controlled with AT-Hayes commands, additional AT-Hayes
commands can be parameterized, that are transmitted to the modem either during the
initialization of the modem after startup of the station or before every connection setup.
With these AT-Hayes commands, either additional parameters can be set in the selected
modem or all necessary parameters in the modem can be set with the selection of the
"freely definable transmission facility".
AT-Hayes commands that are to be transmitted to the modem during the initialization, are
to be parameterized with the parameters advanced parameters | AT-commands |
modem-initialisation ##.
AT-Hayes commands that are transmitted to the modem before every connection setup
are to be parameterized with the parameters advanced parameters | AT-commands |
before connection setup ##.
· Idle monitoring time, character monitoring time
The idle monitoring time and character monitoring time are used to adapt the protocol to
the transmission medium used or to the dynamic behavior of the connected remote station
respectively.
The idle monitoring time and character monitoring time are used for message interruption
detected if the time between 2 bytes of a message is greater than the set character
monitoring time. With message interruption the running reception handling is aborted and
the message is discarded. After a detected message interruption a new message is only
accepted in receive direction after an idle time on the line (idle time). These monitoring
times are to be set with the parameters advanced parameters | monitoring times
| Character monitoring time, advanced parameters | monitoring times |
Character monitoring time "time base", and advanced parameters |
monitoring times | idle monitoring time, advanced parameters |
monitoring times | idle monitoring time "time base".
The DIAMA0 protocol firmware automatically sets the required character monitoring time
for the selected transmission facility of the remote terminal unit.

DC0-023-2.12, Edition 06.2017
Specific settings for modem: "GSM-TC35 Datenbox, MC52iT"

· Pin Code
When using the transmission facility "GSM-TC35 Datenbox", the parameter Common
settings | Modem GSM-TC35 data box | GSM M20 Box - pincode must be set if
the input of the PIN-Code in the SIM-card of the GSM network provider is activated.
Note:
If the PIN-Code request is not required, then for this the SIM-card must be inserted into a
mobile telephone and the PIN-Code request deactivated. This setting is stored on the SIM-
card.
à In the protocol element, the PIN-Code request is deactivated by setting the parameter
Common settings | Modem GSM-TC35 data box | GSM M20 Box - pincode to the
value "10000".
· SMS messages
When using the transmission facility in the remote terminal unit, by using the function
"SMS Messages", freely definable ASCII texts for max. 10 different SMS messages can be
parameterized with the parameters Common settings | Modem GSM-TC35 data box
| #. SMS information. In addition, with the parameter Common settings | Modem
GSM-TC35 data box | Name of the RTU for SMS an unambiguous designation of
the remote terminal unit can be parameterized. This is always sent together with the
transmission of an SMS message.
· Telephone number SMS recipient
When using the transmission facility in the remote terminal unit, SMS messages are
transmitted to the mobile telephone number set with the parameter Common settings |
Modem GSM-TC35 data box | mobile phone number (SMS-receiver).
· Line modulation (V.32, V.110)
When using the transmission facility TC35, MC52iT in the remote terminal unit and the
transmission facility WESTERMO ID90 V.90 (ISDN) in the master station, in the remote
terminal unit the parameter Common settings | Modem GSM-TC35 data box | line
modulation is to be set to V.110.
Specific settings for modem: "Westermo ID90 (ISDN)"

· B-channel protocol (X.75, V.110)
With ISDN, information for the connection setup, information about service detection etc.
are transmitted on the D-channel. On the B-channel, the conversation, fax or data is
transmitted.
When using the modem "WESTERMO ID90/V90" in the master station, in the remote
terminal units either ISDN/analog/ or GSM modems can be used. Depending on the
modem used in the remote terminal units, a corresponding B-channel protocol setting is
required for all ISDN modems.
X.75 (CCITT-Standard)
Protocol for 64 KBit/s transmissions in the ISDN B-channel, mostly with 2 KByte packet
length, optionally with V.42bis data compression.
à Must be used as B-channel protocol, if a station in dial-up traffic uses the
KABELMETALL LGM 64K.
V.110
Designation for a standard for the transmission of data between an analog connection and
an ISDN connection (data rate 1,200 to 19,200 Bit/s, asynchronous) or between two ISDN
connections (data rate 56 or 64 kBit/s) on the B-channel.
à Must be used as B-channel protocol, if a station in dial-up traffic uses a GSM or an
analog modem.
When using the transmission facility "Westermo ID90 (ISDN)", the transmission protocol to
be used can be set with the parameter Common settings | Modem Westermo ID90
V.90 | B-Channel protocol.

Edition 06.2017, DC0-023-2.12
Specific settings for modem: "freely definable"

Apart from this, a transmission facility, that can be freely defined by the user, can be selected,
for which all parameters that are available can be individually set. This is then necessary if
be used for predefined transmission facilities. For the selection of the freely definable
transmission facility the parameter Common settings | interface modem is to be set to
"freely definable".
When using the transmission facility "freely definable", the following parameters can be set:
· 5V Supply (DSR)
performed with the parameter Common settings | Modem free definable | 5V
supply (DSR). The voltage supply is only switched on the DSR state line instead of the
DSR signal with corresponding parameter setting.
ATTENTION:
Required voltage supply and maximum current consumption of the transmission facility
must be observed!
· Automatic call acceptance by the modem
An incoming call can be accepted immediately by the modem through corresponding
setting of the parameter Common settings | Modem free definable | automatic
call acception by modem.
If an incoming call is not to be accepted by the modem, then the call acceptance is
controlled by the protocol element. The call acceptance takes place after the call
acceptance delay time by means of a corresponding control message to the modem in
command mode.
· Command mode baud rate
The transmission rate (baud rate) for the transmission of messages in command mode
to/from the modem, is either "defined", "freely parameter-settable in specific ranges" or
"identical to the transmission rate in data transmission mode", depending on the
transmission facility used.
Some modems require a particular baud rate for the data transmission in command mode,
which can then also be different from the baud rate used in data mode.
The transmission rate (baud rate) for the transmission of data in command mode is to be
set for transmit/receive direction together with the parameter Common settings |
Modem free definable | command mode baud rate.
· Data mode baud rate
The transmission rate (baud rate) for the transmission of data messages to/from the
modem can be parameterized in specific ranges depending on the transmission facility
used.
The transmission rate (baud rate) for the transmission of data messages in data mode is
to be set for transmit/receive direction together with the parameter Common settings |
Modem free definable | data mode baud rate.

DC0-023-2.12, Edition 06.2017
· Command mode data bits, parity, stop bits, end character, message end
For the data transmission of messages from/to the modem in command mode, the byte
frame can be set with the parameter Common settings | Modem free definable |
command mode data bits, the parameter Common settings | Modem free
definable | command mode parity and the parameter Common settings | Modem
free definable | command mode stop bits.
The data transmission in command mode always takes place in ASCII mode. The
character at the end of the message (<CR>, <LF>, …) can be set with the parameter
Common settings | Modem free definable | command mode message end. If no
end character is parameterized, a message received by the modem is processed after a
settable time from the last received character.
This time can be set with the parameter Common settings | Modem free definable
| command mode message end.
· Data mode data bits, parity, stop bits
For the transmission of messages from/to the modem in data mode, the byte frame can be
set with the parameter Common settings | Modem free definable | data mode
data bits, the parameter Common settings | Modem free definable | data
mode parity and the parameter Common settings | Modem free definable |
data mode stop bits.
· Data mode "ASCII transmission"
Some transmission facilities do not support the transmission of data with "8 data bits". With
these transmission facilities, the data transmission must be carried out in ASCII mode. The
data transmission in ASCII mode and the corresponding byte frame must be set identical
in the master station and in all connected remote terminal units.
The data transmission in ASCII mode is to be set with the parameter Common settings
| Modem free definable | data mode ASCII-transmission. The character at the
end of the message (<CR>, <LF>,…) can be set with the parameter Common settings
| Modem free definable | data mode end character if ASCII.
Note:
With the data transmission in ASCII mode the message length is doubled!
· CRC generator polynomial
The transmission of data messages (in data mode) can also be secured by means of a
CRC generator polynomial. This additional security can be activated with the parameter
Common settings | Modem free definable | data mode CRC-
generatorpolynom.
The additional message security with CRC generator polynomial should always be used if
modems do not support the transmission of the parity bit.
· Connection setup procedure
The connection setup/disconnection is to be controlled with a procedure supported by the
modem depending on the connected modem. The selected procedure is to be set with the
parameter Common settings | Modem free definable | connection setup
(procedure).
· Connection setup V25.bis command
With the parameter Common settings | Modem free definable | connection
setup V25.bis_commands it is determined whether the connection setup with V.25bis
(108.2) is to be performed with the command CRI or CRN.
· Call acceptance with call acceptance delay
With the parameter Common settings | Modem free definable | Call
acception while call accept. delay it is parameterized with which command the
call acceptance is performed with call acceptance delay.
For AT-Hayes the call acceptance takes place with the command "ATA", for V.25bis the
control of the call acceptance is carried out with the commands "DIC" (Disconnect
Incoming Call) and "CIC (Connect Incoming Call).
· Evaluate modem messages in data mode
If the data transmission is carried out in ASCII mode, then the function for the detection of
the modem commands must be parameterized with the parameter Common settings |
Modem free definable | Assessment of modem inform. (data mode). Only
through this function is an unambiguous detection of command mode and data
transmission mode possible.

Edition 06.2017, DC0-023-2.12
· Use DCD state line for the connection setup/disconnection control with AT-Hayes
For the connection setup (procedure) with AT-Hayes, (if the ASCII transmission data mode
is not used) the DCD state line must be used for the connection setup/disconnection
control. The status of the DCD state line is used especially for the detection whether the
connection is established or has been terminated again and thus for the detection of
command mode and data transmission mode. The assessment of the state line is to be set
with the parameter Common settings | Modem free definable | DCD is used if
AT-Hayes.
· Disconnection using escape sequence (AT-Hayes)
If the data transmission is carried out in ASCII mode, then the disconnection of the
connection can be performed with the so-called "escape sequence".
For the connection setup (procedure) with AT-Hayes, as escape sequence the character
string "+++" is transmitted to the modem and with connection setup (procedure) with X.28,
the character string "0x10". Through this "escape sequence" the connection is
disconnected and the modem switches over from data transmission mode to command
mode.
The disconnection of the connection using “escape sequence" is enabled with the
parameter Common settings | Modem free definable | Conn. release via
escape seq. (AT-Hayes).
· Disconnection via command
With the connection setup (procedure) with AT-Hayes, the disconnection of the connection
can be carried out with the command "ATH0". For the connection setup (procedure) with
X.28, the disconnection of the connection can be carried out with the command "CLR".
If the function "Disconnect the connection with command" is not enabled with the
parameter Common settings | Modem free definable | connection release
via command, the disconnection of the connection is controlled over state lines.

DC0-023-2.12, Edition 06.2017
Parameters for transmission facilities
Transmission Facility
Westermo Westermo Coherent Siemens Cinterion Westermo Westermo Kabelmetall Kabelmetall Westermo Freely
* TD-32 * TDW-33 * Eurocom- * M20-Box * MC52iT * ID90 * ID90 V.90 LGM/H 64K LGM/H 64K * GD01 definable
* TDW-33 * TD-35 24 Siemens * IDW90 "Direct "Normal * GDW-11
* TD-36 * TD-36 * TC35 Mode" Mode"
* TC35i
Parameter "5V Supply (DSR)" NO NO YES NO NO NO NO NO NO NO NO
Parameter "Automatic call acceptance by modem" NO NO NO NO NO NO NO NO NO NO NO
Parameter "Command mode baud rate" 9600 9600 1200 9600 9600 9600 9600 19200 19200 9600
Parameter "Command mode data bits" 8 8 8 8 8 8 8 8 8 8 8
Parameter "Command mode end character" <CR> <CR> <CR> <CR> <CR> <CR> <CR> <CR> <CR> <CR> <CR>
<LF> <LF> <LF> <LF> <LF> <LF> <LF> <LF> <LF>
Parameter "Command Mode Parity" No No No No No No No No No No No
Parameter "Command mode stop bits" 1 1 1 1 1 1 1 1 1 1 1
Parameter "Command mode message end" 100 Bit 100 Bit 100 Bit 100 Bit 100 Bit 100 Bit 100 Bit 100 Bit 100 Bit 100 Bit 100 Bit
Parameter "Use DCD with AT-Hayes" YES YES YES YES YES YES YES YES YES YES YES
Parameter "Data mode ASCII transmission" NO NO NO NO NO NO NO NO NO NO NO
Parameter "Data mode baud rate" 9600 9600 1200 9600 9600 9600 9600 19200 19200 9600
Parameter "Data mode CRC generator polynomial" YES YES YES YES YES YES YES YES YES YES NO
Parameter "Data mode data bits" 8 8 8 8 8 8 8 8 8 8 8
Parameter "Data mode end character if ASCII" <CR> <CR> <CR> <CR> <CR> <CR> <CR> <CR> <CR> <CR> <CR>
<LF> <LF> <LF> <LF> <LF> <LF> <LF> <LF> <LF> <LF> <LF>
Parameter "Data Mode parity" No No No No No No No Even Even No No
Parameter "Data mode stop bits" 1 1 1 1 1 1 1 1 1 1 1
Parameter "Evaluate modem messages (data mode)" NO NO NO NO NO NO NO NO NO NO NO
Parameter "Call acceptance with call acceptance delay" YES YES YES YES YES YES YES YES YES YES YES
Parameter "Disconnection via escape sequence (AT- Do not Do not Do not send Do not Do not Do not Do not Do not Do not Do not Do not
Hayes)" send send send send send send send send send send
Parameter "Disconnection via command" NO NO NO NO NO NO NO NO NO NO NO
Parameter "Connection setup (procedure)" AT-Hayes AT-Hayes AT-Hayes AT-Hayes AT-Hayes AT-Hayes AT-Hayes AT-Hayes AT-Hayes AT-Hayes AT-Hayes
Parameter "Connection setup V25.bis_command" CRI,<C> CRI,<C> CRI,<C> CRI,<C> CRI,<C> CRI,<C> CRI,<C> CRI,<C> CRI,<C> CRI,<C> CRI,<C>

Edition 06.2017, DC0-023-2.12
Transmission Facility
SIMOCO SEPURA INSYS GSM INSYS PSTN
SRM1000 SRH3500 56K
Parameter "5V Supply (DSR)" NO NO
Parameter "Automatic call acceptance by modem" NO NO
Parameter "Command mode baud rate" 38400 38400
Parameter "Command mode data bits" 8 8
Parameter "Command mode end character" <CR> <CR>
<LF>
Parameter "Command Mode Parity" No No
Parameter "Command mode stop bits" 1 1
Parameter "Command mode message end" 100 Bit 100 Bit
Parameter "Use DCD with AT-Hayes" NO YES
Parameter "Data mode ASCII transmission" YES NO
Parameter "Data mode baud rate" 38400 38400
Parameter "Data mode CRC generator polynomial" YES NO
Parameter "Data mode data bits" 8 8
Parameter "Data mode end character if ASCII" <CR> <CR>
<LF> <LF>
Parameter "Data mode parity" No No
Parameter "Data mode stop bits" 1 1
Parameter "Evaluate modem messages (data mode)" YES NO
Parameter "Call acceptance with call acceptance delay" YES YES
Parameter "Disconnection via escape sequence (AT- send send
Hayes)"
Parameter "Disconnection via command" YES YES
Parameter "Connection setup (procedure)" AT-Hayes AT-Hayes
"ETSI"
Parameter "Connection setup V25.bis_command" CRI,<C> CRI,<C>

DC0-023-2.12, Edition 06.2017
Time settings for "freely definable transmission facility"

Note:
For a freely definable transmission facility, if necessary time seetings are also to be set with
the parameters advanced parameters | Software test points | timeout for
user modems | * .
The time settings are stored permanently in the protocol firmware for the predefined
transmission equipment.
Default Setting Note

Parameter "Timeout 2" 100
Parameter "Timeout 7 Active" 10
Parameter "Timeout 7 10
Passive"
Parameter "Timeout A" 300
Parameter "Timeout B" 300
Parameter "Timeout D" 5
Parameter "Timeout E" 50
Parameter "Timeout F" 2
Parameter "Timeout 1C" 200
Parameter "Timeout 1D" 10
Parameter "Timeout 1E" 10
Parameter "Timeout 1F" 10
Parameter "Timeout 2B" 20
Parameter "Timeout 2C" 30

Edition 06.2017, DC0-023-2.12
7.9.1 Supported Combinations for Dial-Up Modems
Master Station (MASTER) (*)

Westermo Westermo Westermo Coherent Siemens * Cinterion MC52iT J Westermo INSYS 56K INSYS
* TD-32 V * TDW-33 J (11) * TDW-33 J * Eurocom-24 * M20-Box V * Siemens TC35 V * GD01 V PSTN (6) GSM 4.1
* TDW-33 J (11) * TD-35 V * Siemens TC35i V * GDW-11 J (5), (6), (8)
* TD-36 J * TD-36 J * Wavecom WMO2 (5)
* FALCOM A2 (5)
analog (10) analog (10) analog (10) analog (10) GSM GSM GSM analog GSM
* Westermo TD-32 V
analog X X
* WestermoTD-35 V
* Westermo TDW-33 J
* WestermoTD-35 V analog X X
* WestermoTD-36 J
* Westermo TDW-33 J analog X
* Coherent Eurocom24 analog X X X
* Siemens M20-Box V GSM X X X X X
* Cinterion MC52iT J
* Siemens TC35 V
* Siemens TC35i V GSM X X X X X
* Wavecom WMO2
Remote terminal unit ( SLAVE) (*)
* FALCOM A2
* Westermo GD-01 V
GSM X X X X X
* Westermo GDW-11
* INSYS GSM 4.1 GSM X X
Freely definable
(*) the designated modem type must be selected as transmission facility in the protocol firmware !

DC0-023-2.12, Edition 06.2017
Master Station (MASTER) *)
SIMOCO SEPURA Westermo * Kabelmetall * Kabelmetall Freely definable

* SRM1000 * SRH3500 * ID90 V.90 V LGM/H 64K V LGM/H 64K V
* IDW90 J "Direct-Mode" "Normal-Mode"
(7) (3) (1) (2)
TETRA V TETRA V ISDN, analog, ISDN ISDN

GSM
* SIMOCO SRM1000 TETRA V X
SEPURA SRH3500 TETRA V X
* Westermo TD-32 V
analog X
* Westermo TD-35 V
* Westermo TDW-33 J
* Westermo TD-35 V analog X
* Westermo TD-36 J
* Coherent Eurocom24 analog X
* Siemens M20-Box V GSM X
* Cinterion MC52iT J
* Siemens TC35 V
* Siemens TC35i V GSM X
* Wavecom WMO2
* FALCOM A2
Remote terminal unit ( SLAVE) (*)
* Westermo GD-01 V
GSM X
* Westermo GDW-11
* Westermo ID90 V
ISDN X X (4), (9)
* Westermo IDW90 J
* Kabelmetall
LGM/H 64K V ISDN X X
"Direct Mode"
* Kabelmetall
LGM/H 64K V ISDN X
"Normal-Mode"
*) the designated modem type must be selected as transmission facility in the protocol firmware.!

Edition 06.2017, DC0-023-2.12
(1) ISDN transmission in "Direct-Mode" (=fast); the transmission rate for the data mode must be set the same in all stations!
LGM 64K (ISDN modem as Single-Euro-Format module), LGH 64K (ISDN modem as DIN rail module)
Note: The direct mode can only be used with the same modem type in the master station and remote terminal unit.
A subsequent expansion with ISDN modems of other manufacturers is not possible without changing parameters!
(2) ISDN transmission in "Normal Mode" (=slow); the transmission rate for the data mode can be set differently in stations!
Note: ISDN transmission in "Normal Mode" should be used where possible à subsequent expansion with different systems more easily possible (possibly dissimilar baud rate)!
The jumpers on the LGM/H 64K modem must be set to "Auto bauds"!
LGM 64K (ISDN modem as single Euroformat module), LGH 64K (ISDN modem as DIN rail module)
(3) only SMx551/DIAMA0
(4) As B-channel protocol, either X.75 (=X.75 transparent with LGM/H64K) or V.110 (=Normal Mode with LGM/H64K) must be set!
(5) Internally these modems use the SIEMENS TC-35 GSM Engine and are therefore compatible with the Siemens TC35 GSM Modem!
(6) This modem can presently not be selected, but has been tested with internal tests with the settings "freely definable" as modem for the master station.
(7) only available for protocol elements on SMx551 !
(8) only SMx551/DIASA0
(9) this configuration is not supported as standard by the protocol elements !
(Note: … but this configuration was tested using USER-definable modem parameters)
(10) If an ISDN telephone system is used in the Master Station, all interfaces for analog dial up modems must be configured as "data interface".
Otherwise a data call to the remote station will be indentified as "voice call" by the GSM modem of the remote station.
(11) Westermo TDW-33 modem requires Westermo TDW-33 as remote modem for proper operation!
e.g. If Westermo TDW-33 is used in combination with Westermo TD-36 as remote modem, dial-up connection will break down during connection time typically >1 minute
caused by synchronization problems.
V ... discontinued product or discontinued service!

J ... compatible replacement modem (this type of modem can be used as a replacement without changing any parameters)

DC0-023-2.12, Edition 06.2017
7.9.2 ASCII Mode
With connection established, the data transmission is preferably carried out in the format 8E1
defined according to IEC 60870-5-101 (1 Start Bit, 8 Data Bits, 1 Parity Bit "Even", 1 Stop Bit).
Transmission facilities do not always support the transparent transmission in the 8 Bit format
for data. When using such transmission equipment, the ASCII mode must be used. In ASCII
mode, the transmission is carried out in the 7 Bit format for data.
The byte frame for the ASCII mode can be set with the parameter Common settings |
Modem free definable | data mode data bits, the parameter Common settings |
Modem free definable | data mode parity and the parameter Common settings |
Modem free definable | data mode stop bits.
The protocol element thereby converts every HEX-character to be transmitted to 2 ASCII-

characters. e.g.: 68H … is transmitted as <68> (= 36H, 38H).
Due to the ASCII mode the message length doubles, but the data bytes are transmitted with
shorter byte frames.
In addition, in ASCII mode an extra message header is inserted at the beginning of the
message ":" and optionally at the end of the message. The extra message header at the end
of the message can be parameterized with the parameter Common settings | Modem
free definable | data mode end character if ASCII.
The ASCII mode is activated automatically for transmission equipment which do not support
any 8 Bit mode for data. With selected transmission facility (ÜE) "USER defined Modem" the
ASCII mode can be activated with the parameter "Data Mode ASCII transmission".
Note:
With ASCII mode activated, due to the required message frame, even with connection
established the data transmission no longer corresponds with the IEC 60870-5-101!
The user data themselves are transmitted with message formats according to
IEC 60870-5-101 – in ASCII-Mode.
: LINK *) IEC 60860-5-101 ASDU *) CRC-CCITT *) LINK *) <CR> <LF>
IEC 60870-5-1 optional IEC 60870-5-1

IEC 60870-5-2
*) all printable ASCII-signs in range 0..9, A..F (30H .. 39H, 41H-46H)
Optionally, in ASCII mode an additional message protection (CRC-CCITT) can be inserted,

since especially with formats "without Parity Bit" the transmission protection d=4 is not longer
provided.
Note: CRC-CCITT consists of 4 characters in ASCII-Mode.

Edition 06.2017, DC0-023-2.12
7.9.3 CRC Generator Polynomial
With connection established the SICAM RTUs dial-up traffic uses a transmission procedure
according to IEC 60870-5-101 "unbalanced".
To increase the transmission protection an extra block is inserted for message protection
(CRC-CCITT), which is not provided according to IEC 60870-5-101.
If with connection established the transmission procedure definitely according to IE C60870-5-

101 must be used, then this extra block for the message protection (with selected
transmission facility (ÜE) "USER defined Modem" can be deactivated with the parameter
"Data Mode CRC generator polynomial".
In ASCII mode, this extra block for message protection is definitely required especially for
formats "without Parity Bit", since otherwise considerable deterioration of the transmission
protection could occur.
LINK LINK
: IEC 60860-5-101 ASDU CRC-CCITT IEC60870-5-1 <CR> <LF>
IEC60870-5-1 IEC60870-5-2 CS 16
The calculation of the extra block for message protection takes place beginning with the
control field (IEC 60870-5-2) including all IEC 60870-5-101 data bytes (the checksum field is
no longer included). The extra block for message protection is inserted in the message before
the checksum field (CS).
The calculation of the checksum (CS) takes place according to IEC 60870-5-1 beginning with
the control field (IEC 60870-5-2) including all IEC 60870-5-101 data bytes and including the
optionally inserted CRC block.

DC0-023-2.12, Edition 06.2017
7.10 Toll-Saving Transmission Strategies
By means of corresponding parameterization (maximum connection time, prioritization,

selection of process data for spontaneous transmission when data have changed, etc.) the
transmission of data can be reduced to a minimum necessary for the process management.
Whenever a station (central station, remote station) has data ready for spontaneous
transmission, it makes a connection to the partner station.
Apart from the spontaneous transmission, there is the so-called "monitoring cycle": DIAMxx
and DIASxx can also establish a cyclic connection to the remote stations and thus verify their
availability. It is common to parameterize the master in such a way, that it monitors its remote
terminal units cyclic. If necessary, every remote terminal unit can also be parameterized, so
that it monitors its master.
When a connection is established – be it spontaneous or cyclic – all data ready to be

transmitted are in all cases transmitted – regardless whether they are selected for
spontaneous transmission or not.

Edition 06.2017, DC0-023-2.12
7.11 Having a Telephone Set Connected in Parallel
One can also make a normal telephone call over a telephone connection which is used with a
modem for the transmission of data, as long as the operation of a parallel telephone set is
supported by the modem.
If there is no data connection, phone calls can be made at any time.

If a data connection is established it cannot be influenced by the telephone set. If a call comes
in the modem takes the call either immediately or after a settable delay.
Before the modem accepts a call, the call can also be accepted by hand over the telephone.

DC0-023-2.12, Edition 06.2017
7.12 Functions for supporting Redundant Communication

Routes
control messages.
In the master station the information "Ring" (it rings) can be used as protocol return
information for the control of the redundancy state.
In the remote terminal unit, no functions for the support of redundant communications routes
are supported by the protocol element!
From the redundant, non-active master station, listened messages are passed on to the basic
system element (BSE) and forwarded by this in the system with the identifier "passive" in the
state.
passive as follows:

With redundancy state "PASSIVE" all transmit-side interface signals are switched to
"TRISTATE".
With redundancy state "PASSIVE" the interface may only be switched to "ACTIVE" if no
common modem is used (e.g.: with locally separated redundant masters).
In redundant master stations that are not active (=PASSIVE master station), no failure of the
interface is monitored and also no station-selective failure of remote terminal units.
For configurations with locally separated redundant master stations and the use of the
function "Telephone number stepping", the protocol element return information "It’s ringing
(RING)" can be utilized for the control of the redundancy switchover. The telephone number
stepping is offered as a service by the operator of the telephone network. In the remote
terminal unit, commonly only one telephone number of the master station is stored. If the
master station on the main connection does not accept the call within a defined time, the call
of the remote terminal unit is transferred to another connection (to the STANDBY master) by
the telephone number stepping.

Edition 06.2017, DC0-023-2.12
7.13.1 Blocking
In dial-up traffic, data from the remote terminal unit are always transmitted to the master
station as class 2 data (except TM 1703 mic as remote terminal unit in dial-up traffic).
In dial-up traffic, with the assignment of the data to be sent, it is defined through the priority
whether a connection setup is to be performed immediately when these data change or
whether these data is only to be transmitted during the next connection setup.

DC0-023-2.12, Edition 06.2017



· the obtaining of information about the route state/failure of main/standby transmission line
Block Diagram
Protocol element
control
Internal
Transmission route
function
Protocol element


Edition 06.2017, DC0-023-2.12
message.
Multi-Master or Single-Master
In the master station, protocol element control messages can be distributed to a protocol
element directly with "PRE_(PST) = 128 – 131" or with "PRE_(PST) = 254" to the multimaster
function on the basic system element (BSE). The multimaster function on the BSE then
decides to which assigned protocol element the protocol element control message is sent.

DC0-023-2.12, Edition 06.2017
Possible master station functions "Single-Master" (or PST direct to PRE):
Protocol element control messages with "PRE_(PST) = 128-131" are distributed further by the
basic system element directly to the respective selective protocol element:
Function PST Detail Routing Note

SF Station Z-Par Fl
Z-Par=0.65535: no minimum connection time
Start monitoring cycle
0 125 0 -65535 Z-Par=1-65534: minimum connection time
(initiate)
(n * 100ms)
Connection setup to remote terminal
1 0 – 99 0 -65535 Z-Par=1-65534: minimum connection time
unit
(n * 100ms)
0 – 99,
Connection release 2 -
125
Reset connection time counter 0 – 99, The function of the counter is defined with a
3 -
(or connection setup counter) 125 parameter.
A connection setup to the remote terminal unit is
0 – 99,
Use main telephone number first 4 - carried out to the main telephone number first
125
(see Mode-4, connection setup procedure)
A connection setup to the remote terminal unit is
0 – 99,
Use standby telephone number first 5 - carried out to the standby telephone number
125
first (see Mode-4, connection setup procedure)
0 – 99,
Terminate call attempts (abort) 6 -
125
Via dial-up traffic switch standby
transmission line operation ON for 7 0 – 99 -
remote terminal unit (Ax) 1)
Via dial-up traffic switch standby

transmission line operation OFF for 8 0 – 99 -
remote terminal unit (Ax) 1)
Activate standby transmission line and Z-Par=0.65535: no minimum connection time

connection setup to remote terminal Z-Par=1-65534: minimum connection time
10 0 – 99 0 -65535
unit over activated standby (n * 100ms)
transmission line (Ax) 1)
Connection release to remote terminal

unit and deactivate standby 11 0 – 99 -
transmission line (Ax) 1)
only parameterized RTUs can be added to the

Add station to station polling 128 0 – 99 - station polling
ð otherwise error "faulty PST-control message"
only parameterized RTUs can be removed from
the station polling
Remove station from station polling 129 0 – 99 0,1 ð otherwise error "faulty PST-control message"
Z-Par=0: Reset present station fault
Z-Par=1: Do not change present station fault
This function is processed on the BSE and sent
Send (general) interrogation to the protocol element as system message and
240 - -
command not using PRE-control message!
CASDU = BROADCAST
Send (general) interrogation This function is processed on the BSE and not
command for GI-group to own BSE 3) sent to the protocol element as PRE-control
241 - -
(=simulate received general interrogation message!

Edition 06.2017, DC0-023-2.12
Possible master station functions "Single-Master" (or PST direct to PRE): (Continued)

SF Station Z-Par Fl
65535
(all stations)
125
SCS=<OFF>: reset control location (HKA) (all
65535
stations)
65535
(selective station)
0 – 99
65535
(selective station)
This function is processed on the BSE and sent to
Send (general) interrogation the protocol element as system message and not
244 - CASDU
command using PRE-control message!
CASDU = selective
1) not supported by SICAM RTUs!
routing.


DC0-023-2.12, Edition 06.2017
Possible master station functions "Multimaster" (PST to Multimaster function on BSE):

Protocol element control messages with "PRE_(PST) = 254" are distributed further by the
multimaster function on the basic system element (BSE) to a freely assigned multimaster
interface (protocol element):

SF Station Z-Par Fl
Connection setup to remote terminal 2)
1 0 – 99 0 -65535 Z-Par=1-65534: minimum connection time
unit
(n * 100ms)
… is only transferred by the multimaster function
Connection release 2 0 – 99 -
if a connection is established to this station.
Terminate call attempts (abort) 6 0 – 99 -
Activate standby transmission line and Z-Par=0.65535: no minimum connection time
connection setup to remote terminal Z-Par=1-65534: minimum connection time
10 0 – 99 0 -65535
unit over activated standby (n * 100ms)
transmission line 1)
Connection release to remote terminal … is only transferred by the multimaster function

unit and deactivate standby 11 0 – 99 - if a connection is established to this station.
transmission line 1)

Z-Par=1-65534: minimum connection time 2)
Connection setup to remote terminal (n * 100ms)
12 0 – 99 0 -65535
unit via ''red telephone'' … with this PST-control message a USER
controlled monitoring of the modem for the
"red telephone" can be realized.
This function is processed on the BSE and sent to
the protocol element as system message and not
using PRE-control message!
Send (general) interrogation command 240 - - CASDU = BROADCAST
The (general) interrogation command will be
forced to transmit by BSE for each individual
station.
1) this PRE control messages are used by BSE for integrated function “standby transmission line operation” only
(other usage is not supported)
2) during connection established the minimum connection time will be always retriggered with this PST control
message; the connection will be released latest after elapsed maximum connection time
Legend:

0 - 99 = selective station 0 - 99 of the selected protocol element
125 = all parameterized stations of the selected protocol element
Z-Par.......... additional parameter_(PRE)

Fl ................ edge
HKA ........... originator address (HKA) = 0 - 255

Edition 06.2017, DC0-023-2.12

SF Station Z-Par Fl
Start monitoring cycle
0 - -
(initiate)
Reset connection time counter
3 - -
(or connection setup counter)
A connection setup to the master station is
Use main telephone number first 4 - - carried out to the main telephone number first
(see Mode-4, connection setup procedure)
A connection setup to the master station is
carried out to the standby telephone number
Use standby telephone number first 5 - -
first. (see Mode-4, connection setup
procedure)
Terminate call attempts (abort) 6 - -
Send SMS message 1 7 - -
command
message!
CASDU = BROADCAST
241 - -

command
message!
CASDU = selective
Legend:

Station ....... Station number (not used = 255)

DC0-023-2.12, Edition 06.2017


Edition 06.2017, DC0-023-2.12
Possible master station return information "Single-Master":
Return information function_(PRE) Parameter Note

Station
Status RTS 1)
Status RTS 255 0 = status line inactive
Status CTS 1)
Status CTS 255 0 = status line inactive
Status DCD 1)
Status DCD 255 0 = status line inactive
Status DTR 1)
Status DSR 1)
protocol-specific return information 0 0 – 99 Connection setup "stored (flagged in advance)"
protocol-specific return information 1 0 – 99 Connection setup "in progress"
protocol-specific return information 2 0 – 99 Connection "established"
Connection setup "not possible" 2)
protocol-specific return information 3 0 – 99
(number of redials elapsed without success)
protocol-specific return information 4 0 – 99 Connection setup executed successfully 2)
Dialing pause
(after an unsuccessful connection setup attempt, a dialing
pause is performed, afterwards a new connection setup is
initiated)
protocol-specific return information 6 0 – 99 Connection "terminated" 2)
Connection setup not possible

protocol-specific return information 7 0 – 99 2)
(Station not enabled on protocol element)
"The telephone line has been unplugged"

protocol-specific return information 9 0 – 99 Status of Layer 1 interrogation.
(only applicable for Kabelmetall ISDN terminal adapter)
"It’s ringing" (RING)

protocol-specific return information 14 255 With redundant configurations this information can be used for
redundancy switchover.
The return value can be selected via parameter.
- connection time counter (connection time in seconds)
protocol-specific return value 0 – 99 (for active/passive connection setup)
Format of the return value: "IEEE 754 Floating Point".

DC0-023-2.12, Edition 06.2017
Possible master station return information "Multi-Master":

Station
Status RTS 1)
Status RTS 255 0 = status line inactive
Status CTS 1)
Status CTS 255 0 = status line inactive
Status DCD 1)
Status DCD 255 0 = status line inactive
Status DTR 1)
Status DSR 1)
protocol-specific return information 1 0 – 99 Connection setup "in progress"
protocol-specific return information 2 0 – 99 Connection "established"
protocol-specific return information 6 0 – 99 Connection "terminated" 2)
"It’s ringing" (RING)

protocol-specific return information 14 255 With redundant configurations this information can be used for
redundancy switchover.
PRE0 assigned
protocol-specific return information 0 255 (Multimaster function cannot perform any connection setup
over this PRE)
PRE1 assigned
over this PRE)
PRE2 assigned
over this PRE)
PRE3 assigned
over this PRE)
All PRE's assigned
over these PRE's)
transmitted!
2) these information are transmitted as "transient information"; transmit general interrogation command to basic
system element (ON/OFF-status of the information is transmitted immediately in succession)
Legend:
Station Station number

0 - 99 = Station 0-99 of the selected protocol element
255 = Station number not used
PRE Protocol element

Edition 06.2017, DC0-023-2.12

Station
Status RTS (1= state line active) 255 1)
Status CTS (1 = state line active) 255 1)
Status DCD (1 = state line active) 255 1)
Status DTR (1 = state line active) 255 1)
Status DSR (1 = state line active) 255 1)
Station status 255 1 = Station enabled for call cycle

Station failure 255 1 = master station failed
protocol-specific return information 0 255 Connection setup "stored (flagged in advance)"
protocol-specific return information 1 255 Connection setup "in progress"
protocol-specific return information 2 255 Connection "established"
protocol-specific return information 4 255 Connection setup executed successfully 2)
Dialing pause
(after an unsuccessful connection setup attempt, a dialing
pause is performed.
Afterwards a new connection setup is initiated)
protocol-specific return information 6 255 Connection "terminated" 2)
Connection setup not possible

protocol-specific return information 7 255 2)
(Station not enabled on protocol element)
"The telephone line has been unplugged"

protocol-specific return information 9 255 Status of Layer 1 interrogation.
(only applicable for Kabelmetall ISDN terminal adapter)
The return information value can be selected via parameter.

protocol-specific return information retries in % (of the last full hour)
255
value IEEE 754 floating point format will be used for
return information value.
transmitted!
2) these information are transmitted as "transient information"; transmit general interrogation command to basic
system element (ON/OFF-status of the information is transmitted immediately in succession)
Legend:

255 = Station number not used

DC0-023-2.12, Edition 06.2017

Edition 06.2017, DC0-023-2.12
8 LAN Communication (104)
Contents
8.1 Introduction .................................................................................................. 326

8.2 LAN/WAN Communication according to IEC 60870-5-104 ............................ 331
8.4 Dual-LAN Interface (DNIP) ........................................................................... 369
8.7 Security Logging........................................................................................... 407
8.8 Web Server .................................................................................................. 408

DC0-023-2.12, Edition 06.2017
LAN Communication (104)
8.1 Introduction
The IEC 60870-5-104 protocol is a transmission protocol on OSI-layer 5-7 for the
communication between control systems or between master stations and remote terminal
units. For OSI-layer 3+4 the TCP/IP protocol is implemented.
The protocol is especially suitable for SCADA applications.
In contrast to the IEC 60870-5-101 protocol, which establishes connections over serial
interfaces, the IEC 60870-5-104 interface enables the communication over networks (Local
Area Network "LAN" and Wide Area Network "WAN"). Thereby common network components
such as switches and routers can be used.
The IEC 60870-5-104 protocol uses a signal-orientated data model. Every message
represents one data point, such as e.g. one measured value, setpoint value, command or
alarm. This message is thereby defined by an address and a data type. The address then
determines which signal is concerned, i.e. transmitter and receiver must know the meaning of
the address.
For the transmission of data, a "TCP-Connection" is established between 2 participating

stations. One station can establish an independent connection to several different stations.
Each station has equal access and can spontaneously perform a data transmission.
Master station-1 Master station-2 Master station-n

LAN-Interface LAN-Interface LAN-Interface
Switch Switch
Router Router
LAN/WAN-Network
Router Router Router
Switch Switch Switch
LAN-Interface LAN-Interface LAN-Interface LAN-Interface
Remote station-1 Remote station-2 Remote station-n
max. 100 connections per LAN-Interface
ETA2 SICAM AK
ETA4 SICAM BC IEC 60870-5-104 controlling-/controlled station
SICAM TM
ET84 CP-8000 IEC 60870-5-104 controlling-/controlled station

CP-802x
ET24 SICAM AK3 IEC 60870-5-104 controlling-/controlled station

Edition 06.2017, DC0-023-2.12
ETA2
ETA4
ET84
ET24
General Functions
· LAN/WAN Communication over Ethernet TCP/IP - General

− 10 Mbit/s (full duplex) ü ü ü 1) ü 1)
− 10 Mbit/s (half duplex) ü ü ü 1) ü 1)
− 10 Mbit/s (full duplex , auto negotiation) ü ü 1) ü 1)
− 10 Mbit/s (half duplex, auto negotiation) ü ü 1) ü 1)
− 10/100 Mbit/s (half duplex / full duplex, auto negotiation) ü ü ü 1) ü 1)
− 100 Mbit/s (full duplex) ü ü ü 1) ü 1)
− 100 Mbit/s (half duplex) ü ü ü 1) ü 1)
− 100 Mbit/s (full duplex, auto negotiation) ü ü 1) ü 1)
− 100 Mbit/s (half duplex, auto negotiation) ü ü 1) ü 1)
− Auto-MDIX (Auto Medium Dependent Interface Crossover) ü 1) ü 1)
− Parameters for TCP/IP optimization ü ü ü 1) ü 1)
− TCP/IP Keep Alive ü ü ü
· LAN/WAN Communication over Ethernet TCP/IP according to

IEC 60870-5-104
− Controlled station ü ü ü 7) ü 7)
− Controlling station ü ü ü ü
− max. connections 100 2) 100 2) 100 3) 100 3)
· Supported Ports
− Port 2404: IEC 60870-5-104 ü ü ü ü
− Port 80: HTTP (Hypertext Transfer Protocol) - “Web server“ ü
− Port 80: HTTP (Hypertext Transfer Protocol) - ü ü 1) ü 1)
“Remote operation for SICAM TOOLBOX II“
− Port 443: HTTPS (Hypertext Transfer Protocol over SSL/TLS) -
“Web server“
− Port 443: HTTPS (Hypertext Transfer Protocol over SSL/TLS) - ü ü 1) ü 1)
− Port 123: NTP V3 (Network Time Protocol) ü ü ü 1) ü 1)
− Port 123: SNTP V3 (Simple Network Time Protocol) ü ü 1) ü 1)
− Port 2001: “Remote operation for SICAM TOOLBOX II“ ü
· Special Protocols
− Address Resolution Protocol (Gratuitous ARP) ü ü 1) ü 1)
− SICAM RTUs Interoperability IEC 60870-5-101/104 (DC0-013-2) ü ü ü ü
− Ax 1703 Interoperability IEC 60870-5-101/104 (DA0-046-2) ü
· Acquisition of events (transmission of data ready to be sent) ü ü ü ü
· General interrogation, outstation interrogation ü ü ü ü
· Clock synchronization according to NTP (Network Time Protocol)

− NTP server ü ü ü 1) ü 1)
− NTP client ü ü ü 1) ü 1)
− SNTP client ü ü 1) ü 1)

DC0-023-2.12, Edition 06.2017
ETA2
ETA4
ET84
ET24
General Functions
· Command transmission
− Supervision of maximum transport delay in control direction ü ü ü ü
Command Transfer Monitoring (Dwell Time Monitoring)
− Set control location ü ü ü
− Check control location ü ü ü
· Transmission of integrated totals ü ü ü ü

− Protocol element control
− Interface “enable/disable” ü ü ü
− Send (general) interrogation command ü ü ü ü
− Send (general) interrogation command for GI group to own BSE ü 6) ü 6) ü 6) ü 6)
− Preset control location ü ü ü

− Remote operation “enable/disable” ü ü 1) ü 1)
− Station failure ü
− PRE return information 0 “Status DATA TRANSFER (BSE)” ü ü ü ü
− PRE return information 1 “Status DATA TRANSFER (104)” ü ü ü ü
− PRE return information 2 “Remote operation “enabled/disabled” ü ü 1)
− PSI redundancy (synchronous connections) ü ü ü ü
− 104 redundancy according IEC 60870 5 104 Edition 2.0)
- 104 redundancy “controlling station“ ü
- 104 redundancy “controlled station“ with 1 Ethernet interface ü ü ü ü
- 104 redundancy “controlled station“ with 2 Ethernet interfaces ü ü ü 4)

− 1703 redundancy ü ü ü ü
− Deactivation of interface (with protocol element control message) ü ü ü
− Deactivation of interface (with redundancy control message) ü ü
− Dual LAN interface with integrated switch for ring or star configurations
(DNIP)
- RSTP mode (max. 39 devices in ring configuration) ü
- Line Mode ü
- Switch mode ü ü 1) ü 1)
- Single mode ü
- Single + service mode ü
· SICAM TOOLBOX II connection over LAN/WAN ("remote

connection")
− Remote connection based on HTTP/HTTPS ü ü 1) ü 1)
− User authentication in SICAM RTUs using “Connection Password” ü ü 1) ü 1)
− Remote connection based on integrated terminal server ü
(Enable/Disable) option
− “Warning Remote Connection” ü ü ü 1) ü 1)

Edition 06.2017, DC0-023-2.12
ETA2
ETA4
ET84
ET24
General Functions
− Remote operation “enable/disable” via control message ü ü 1) ü 1)

· Web Server
− Integrated web server to display connection, statistic and developer ü
information
− Access to the web server with standard web browser via HTTP ü
(Hyper Text Transfer Protocol)
− Password for web server ü
− Web server (enable/disable) option ü
· Security
− IPSec VPN
- IPSec in tunnel mode: initiator ü ü 1) ü 1)

- Authentication / encryptionbased on pre-shared key ü ü 1) ü 1)
- Internet Key Exchange protocol: IKEv1 ü ü 1) ü 1)
- Authentication algorithms: HMAC-SHA1, HMAC-MD5 ü ü 1) ü 1)
- Encryption algorithms: AES-128, 3DES ü ü 1) ü 1)
- Diffie-Hellman group: Group1, Group2 ü ü 1) ü 1)
− Security Logging
- Syslog Client ü 5) ü 1) ü 1)
− Summer time bit (SU) = 0 for all messages in transmit direction (time ü ü ü ü
tag)
− Day of week (DOW) = 0 for all messages in transmit direction (time ü ü ü ü
tag)
− Time stamp (IV = 1) in messages in transmit direction ü ü
− Originator address = 0 for all messages in transmit direction ü ü ü ü
− WhiteList filter ü ü ü
− Data throughput limitation ü ü ü
− Special functions for project DBAG
- Breaker delay in transmit direction (<TI:= 150>) ü ü
- Send originator address with settable value ü ü

− Special functions for project RWE
- Bit by bit marking of the field ü ü
- Cyclic measured values ü ü
- Address of the return information for selection command 2 ü ü
- NT-Bit, IV-Bit according to RWE requirements ü ü

− Suppress error in case of connection failure ü ü ü ü
− Error handling for connection with “failure = suppress”
- NT-Bit simulation after connection failure ü ü ü ü
- General interrogation after connection is OK

DC0-023-2.12, Edition 06.2017
1) in CP-8000/CP-802x, this function is integrated on the basic system element

2) recommendation max. 30 connections
(in case of high load of connection or large number of data points)
3) recommendation max. 10 connections
(in case of high load of connection or large number of data points)
4) nd
only in combination with 2 Ethernet interface with SM-2558/ETA4
5) only in combination with CP-2014/CPCX25
7) With mode of Ethernet ports = "1 IP address (connected ports in switch mode)" only one PRE for
the local LAN interfaces may be configured as “controlling station” (not both).
With mode of Ethernet ports = "2 IP addresses (independent ports)” both PRE’s for local LAN
interfaces can be configured as “controlling station”.
Note:
- ”controlling/controlled“ function is to be set per station in the parameters for connection
definition.

Edition 06.2017, DC0-023-2.12
8.2 LAN/WAN Communication according to IEC 60870-5-104
8.2.1 Layer Model – General Information about the Protocols used
Protocols according to the IEC 60870-5-104 standard are based on the OSI layer model.

7 Mapping IEC 60870-5-101 ó IEC 60870-5-104
IEC60870-5-104 PRE-Status Time

WEB-Server Remote Sync.
6 APDU Connection
for
TOOLBOX II
5 APCI HTTP NTP Legend:

APDU ……….. Application Protocol Data Unit (IEC 60870-5-104)
4 TCP UDP APCI ……...…. Application Protocol Control Information (IEC 60870-5-104)
ARP ……...….. Address Resolution Protocol
3 ICMP
IP Encapsulation RFC 894
1 Ethernet …. IEC 61850

7 - Application Application · Transmit handling
· Receive handling
6 - Presentation Data format · IEC 60870-5-104 APDU's to Ax 1703 / SICAM RTUs and
compatible systems
Ax 1703/SICAM RTUs-specific system messages and
some user data is implemented
5 - Session Interface between · IEC 60870-5-104 APCI
data format and · NTP according to RFC 1305
communication · Remote operation for SICAM TOOLBOX II
protocol
4 - Transport Communication · TCP/IP according to RFC 791 and RFC 793
3 - Network protocol · ICMP according to RFC 792
2 - Data Link LAN interface · Ethernet 10/100 Mbps according to IEEE 802.3
SICAM TOOLBOX II
· RSTP according to IEEE 802.1D, Edition 2004
Note
In the Appendix there is a short description of the protocols (layer 1-5).

DC0-023-2.12, Edition 06.2017
8.2.2 Ethernet Interface
The Ethernet Interface is implemented on communication interface hardware (NIP) or on basis

system element hardware board.
Ethernet Speed (10/100 Mbit/s), Full-/Half Duplex [ETA2 only]

The transmission rate (10/100 Mbit/s) and the method of transmission (full duplex/half duplex)
on the Ethernet is determined with the parameter advanced parameters | Ethernet
speed and duplex or when using dual-Lan interface (Dual Ethernet NIP) with the
parameter advanced parameters | DNIP (Dual Ethernet NIP) | Ethernet speed
and duplex | Port# ethernet speed and duplex. In the default setting this parameter
is set to "Auto negotiation" and only needs to be specifically adjusted in exceptional cases.
Auto negotiation ("Auto-Sensing") is an Ethernet procedure by which two connected devices
(e.g. a network port of a computer and the network port of a Router, Hub or Switch) choose
common transmission parameters, such as speed, duplex mode, and flow control. In this
process, the connected devices first share their capabilities regarding these parameters and
then choose the highest performance transmission mode they both support. This procedure is
only used for wired Ethernet ((twisted pair cable) – but not for WLAN-, fiber optic- or coaxial
cables.
Note:
If problems occur with the default setting when coupling other systems directly with cross-over
cables or when using HUB's or other network components, here "half duplex" is to be used.
Monitoring of Ethernet Interface (“Ethernet LINK UP“)

The system element monitors for each Ethernet interface if the link is established (“LINK UP“).
When the link is not established (“LINK DOWN“) a diagnostic information “Ethernet link not
established” can be set (default = “no diagnostic information“).
Port specific diagnostic information will be enabled with the parameter Network settings |
advanced parameters | Diagnostic information for Ethernet-link status X#.
For system elements supporting 2 Ethernet ports the diagnostic information “LINK DOWN“ will
be set individually for each port.

Edition 06.2017, DC0-023-2.12
8.2.3 Definition of the Connections
IP Addresses
Every device which is connected to a TCP/IP network has an unambiguous IP address.
The protocol firmware supports only IP addresses in the format IPv4 (=32 Bit). With that, 2 32,
in other words 4,294,967,296 addresses can be represented. The IP address is mostly
represented in the dotted decimal notation.
Example: 192.168.122.195
The IP address of the own station is to be parameterized in the system-technical parameters

with the parameter IP address | own IP address.
The IP address(es) of the remote station(s) is(are) to be parameterized for each connection in
the system-technical parameters of the connection definition.
Port numbers
Every IP connection is defined by the IP address of the own station and the remote station
and the port number. The port numbers are defined by the IANA (Internet Assigned Numbers
Authority).
Port numbers used in the LAN/WAN protocol firmware:
ETA2
ETA4
ET84
ET24
Port
Number Protocol Standard
2404 IEC 60870-5-104 IEC 60870-5-104 Edition 2.0 ü ü ü ü
HTTP RFC 2616 (HTTP/1.1)
80 ü
(Hypertext Transfer Protocol)
HTTP (Hypertext Transfer Remote operation for
80 ü ü1) ü1)
Protocol) SICAM TOOLBOX II
HTTPS
443 (Hypertext Transfer Protocol Remote operation for ü ü1) ü1)
over SSL/TLS) SICAM TOOLBOX II
NTP V3 RFC 1305
123 ü ü ü1) ü1)
(Network Time Protocol)
SNTP V4 RFC 2030
123 ü ü1) ü1)
(Simple Network Time Protocol)
Remote operation for ---
2001 *) ü
SICAM TOOLBOX II
RSTP IEEE 802.1D, Edition 2004
---- ü
(Rapid Spanning Tree Protocol)
1) in CP-8000/CP-802x, this function is integrated on the basic system element
2) this port number is not registered with IANA!
Legend:
RFC Request for Comments

DC0-023-2.12, Edition 06.2017
Address Resolution Protocol (Gratuitous ARP)
The “ARP“ address resolution protocol is used for mapping of IP address to MAC address.
The mapping is stored in ARP tables of involved network devices.
After link up (restart or re-connect LAN cable) the Ethernet interface sends several gratuitous
ARP as “Broadcaset ARP request“ with own IP address as source- and destination IP
address. With the unsolicited gratuitous ARP procedure the Ethernet interface sends actual
(or new) MAC address and the ARP/MAC tables of the connected network devices will be
updated immediately. With untypical number of gratuitous ARPs in network communication
hardware problems causing link up/link down can be identified.
Default Router (Default Gateway)

If the own network is connected by means of a router, then the IP address of the default router
is to be set in the system-technical parameters of the protocol firmware with the parameter IP
address | Default router (default gateway).

Edition 06.2017, DC0-023-2.12
Subnet Mask
The subnet mask is a bit mask, which splits up an IP address into a network part and a device
part (host part). It is used in IP networks to make routing decisions.
The subnet mask is to be set in the system-technical parameters of the protocol firmware with
the parameter IP address | Subnet mask.
The subnet mask is exactly as long as the IP address on which it is applied (therefore 32 Bit
for IPv4). All bits of the network part are set to "1" and all bits of the device part to "0".
Predominantly, the notation of a network mask is not performed binary, rather (as for IP
addresses too) frequently in decimal notation (dotted decimal notation).
Consequently, the IPv4 network mask for a 27 bit network part reads 255.255.255.224.
The usable address space of a network is defined by the subnet mask. For a 27 bit network
part, the first 27 places of the IP address of the network part are identical and for all hosts of
the network. The network part is continuous in all practical cases of application (without zeros
in between).
Example: Calculation of network and host section

IPv4 address = 192.168.122.195
Network part = 27 Bit à Subnet mask = 255 . 255 . 255 . 224
11111111 11111111 11111111 11100000
Decimal Binary Calculation

IP Address 192.168.122.195 11000000 10101000 01111010 11000011 IP address
Network mask 255.255.255.224 11111111 11111111 11111111 11100000 AND Subnet mask
Network part 192.168.122.192 11000000 10101000 01111010 11000000 = Network part

Network mask~ 255.255.255.224 00000000 00000000 00000000 00011111 AND (NOT subnet mask)
Device part 3 00000000 00000000 00000000 00000011 = Device part
A network mask with 27 bits set produces a network part of 192.168.122.192.

5 bits, and therefore 32 addresses, remain for the device part.
In the example above, the smallest host address ends with 11000000 (decimal: 192), the
largest possible host address with the octet 11011111 (decimal: 223). The address range for
the subnet in the example is therefore 192.168.122.192 to 192.168.122.223.
The largest address is by definition reserved for the IP broadcast and the smallest address
describes the network itself. They are therefore not included among the freely usable
addresses.
In practice, the default gateway is often assigned to the smallest (in the example, binary:
11000001, decimal: 193) or the largest (in the example, binary: 11011110, decimal: 222)
usable IP address in the network.

DC0-023-2.12, Edition 06.2017
Connection-specific parameters
In the master station and in the remote terminal unit(s), the required settings are to be carried
out in the parameters of the connection definition for every connection.
The following parameters can be set per connection:
· Stat. No
The station number is used SICAM RTUs internal for the routing of the data, diagnostic
treatment and failure management. The station number is the SICAM RTUs internal
reference for that connection to which an IP address is assigned. During the data
transmission, only the IP address assigned to the station number is transmitted, the station
number is not transmitted.
For the data flow routing, the data to be transmitted are routed to a "station number"
(connection number = destination station number).
The station number (Stat. No.) is to be entered in the parameter connection
definition | Stat. no. for each connection.
· Connection
A parameterized connection can be activated/deactivated with the parameter
connection definition | Connection; e.g. this way connections can be prepared,
that are first activated at a later time by means of parameterization.
· Connection setup [ET02, ETA2 only]
For every TCP/IP connection, one party is either "Listener (Server)" or "Connector
(Client)". The TCP/IP connection is always only established by the "Connector (Client)".
With the parameter connection definition | connection setup the role of the
own station is to be parameterized for every connection (listener “server”, connector
”client”).
This parameter is not longer supported by newer protocol element firmwares (the role is
fixed as: controlling station = connector; controlled station = listener).
· Data flow control, Controlling/Controlled
Through the plant configuration, it is determined for every connection whether a station
according to IEC 60870-5-104 is a "Controlling Station" or a "Controlled Station".
Therefore for every connection one party is to be parameterized either as "Controlling
Station" or as "Controlled Station".
The IEC 60870-5-104 data flow is started/stopped by the "Controlling Station".
With the parameter connection definition | data flow control or connection
definition | controlling/controlled the role of the own station is to be
parameterized for every connection.
· IP-address
For every connection the IP address of the remote station is to be parameterized.
The IP address (Internet-Protocol) is a number, which permits the addressing of parties in
LAN/WAN IP networks. This address must always be unambiguous in one network.
The IP address is to be parameterized as follows (example): 192.168.122.195
The IP address of the remote station is to be parameterized for every connection with the
parameters connection definition | IP-addr.
· IP address A, IP address B, IP address C, IP address D [ET02 only]
LAN/WAN IP networks. This address must always be unambiguous in one network.
( A B C D )
parameters connection definition | IP-addr *.

Edition 06.2017, DC0-023-2.12
· Redundancy
For every connection, its redundancy function is to be determined for the selected
redundancy control:
- No redundancy [Default]
- Real connection
- Virtual connection
- Connection has IEC 60870-5-104 Controlling functionality - i.e. no redundancy
For further detailsrefer to section "Functions for the support of redundant communication
routes".
With the parameter connection definition | Redundancy the function of the own
station is to be parameterized for every connection.
· RedGroup
When using the redundancy according to IEC 60870-5-104, every connection can be
assigned to one of several redundancy groups.
For further details about this, refer to section "Functions for the support of redundant
communication routes".
With the parameter connection definition | RedGroup the redundancy group
number is parameterized for the connection.
· Stop behavior
If the own station is parameterized as "Controlled Station" and the IEC 60870-5-104 data
transfer has been stopped by the "Controlling Station" with "STOP DataTransfer
activation)", with the parameter connection definition | stop behaviour it can
be selected if in state “STOP” all messages in transmit direction (including End of Init) will
be saved or discarded.
Note: With “stop behavior = discard” a buffer overflow is avoided in the state “STOP”.
· Network connection
Optimized IEC60870-5-104 parameters for network connection:
- LAN (IEC 104 default)
- WAN
- LAN (fast dropout detection)
- GPRS
- Satellite
- free definable 1
- free definable 2
- free definable 3
· 104-Parameter [ETA2 only]
For every connection, with the parameter connection definition | 104-parameter
one from max. 4 possible 104-Parameter parameter-groups can be selected. In these
parameter groups, IEC 60870-5-104 specific parameters are to be set.
104-Parameter Groups:
- Group 0 - 3
· 104-Parameter" and "104-Par. expanded [ET02 only]
For every connection, with the parameters connection definition | 104-
parameter and connection definition | 104-par. extended one from max. 4
possible 104-Parameter parameter-groups can be selected. In these parameter groups,
IEC 60870-5-104 specific parameters are to be set.
104-Parameter Groups:
- Standard, Group 0
- Standard, Group 1
- Expanded, Group 0
- Expanded, Group 1

DC0-023-2.12, Edition 06.2017
· Failure
For certain redundancy configurations or operating modes, for the SICAM RTUs internal
diagnostics, the failure of a connection can be suppressed with the parameter
connection definition | Failure.
If the failure is suppressed, the connection is never signaled in the diagnostic as failed and
all messages in transmit direction (also INIT-End) are discarded until the connection is
established!
Note: As a result a ring overflow is avoided with non-connected remote stations.
· Weekday
With function enabled with the parameter connection definition | day of week
the day of week (DOW field of the time tag) is always set to “0” by the LAN/WAN protocol
element for all messages in transmit direction.
· Daylight-saving time
With function enabled with the parameter connection definition | summertime the
summer time bit (SU bit of the time tag) is always set to “0” by the LAN/WAN protocol
element for all messages in transmit direction.
· Originator address
With function enabled with the parameter connection definition | originator
address the originator address is always set to “0” by the LAN/WAN protocol element for
all messages in transmit direction.
· Clear Ring Buffer
At failure of connection the protocol element can read data from the ring buffer from the
basic system element (BSE) after timeout and delete data without error. This function can
avoid ring buffer overflow on basic system element (BSE).
The function can be enabled with the parameter connection definition | clear
ring buffer.
The delay time can be parameterized with the parameter advanced parameters |
timeout clear ring buffer.
· Profile (type identification check)
The selected profile defines the type identifications to be supported for communication
with remote system.
Depending on selected profile, enhanced checks for fields of IEC60870-5-104 message
will be executed.
Supported Profiles:
- SICAM RTUs - IEC104 (“SICAM RTUs “Standard“)
- IEC60870-5-104 Ed.2 (“KEMA conformance tested”)
- WhiteList Filter
- WhiteList Filter for passive PRE
The required profile can be selected with the parameter connection definition |
profile (type identification check).
· Data throughput limit in receive direction (msg/s)
· Data throughput limit in transmit direction (msg/s)
The protocol element for IEC60870-5-104 in SICAM RTUs supports a limitation of data
throughput in transmit-/receive direction for IEC60870-5-104 data messages.
The number of messages/second in transmit direction can be parameterized with the
parameter connection definition | Data throughput limit in transmit
direction (msg/s). (0 = no data throughput limitation).
The number of messages/second in receive direction can be parameterized with the
parameter connection definition | Data throughput limit in receive
direction (msg/s). (0 = no data throughput limitation).

Edition 06.2017, DC0-023-2.12
IEC60870-5-104 Parameters
variable elements of the message according to IEC 60870-5-104 to the following defined
values is required:

Element
Cause of transmission (COT) Number of octets for cause of transmission = 2 BSE
(CASDU) ASDU = 2
Information object address (IOA) Number of octets for address of the information BSE
object = 3
Maximum message length max. 253 BSE
Time tag Number of octets for time tag = 7 BSE
BSE = Basic system element
Note
If one parameter does not correspond to the required setting, a parameter error is reported!
IEC 60870-5-104 Parameters / TCP Parameters

The IEC 60870-5-104 specific parameters for "Definition of monitoring times" and "Maximum
number of unacknowledged I-format frames k and acknowledgement w" are grouped into
parameter groups. One of these parameter groups (104 parameter, network connection) can
be selected for every connection.
Note
The modifying of the 104 specific parameters requires detailed knowledge of the IEC 60870-5-104
protocol and should therefore only be performed by communications experts or after consultation!

DC0-023-2.12, Edition 06.2017
Supported IEC60870-5-104 / TCP Parameters
Network Connection
LAN (fast dropout

(IEC 104 default)
free definable 1
free definable 2
free definable 3
detection)
group 1-4
Satellite
GPRS
WAN
LAN
Parameter
IEC 104 parameters
timeout connection setup t0 5 5 5 60 5 5 5 5 30
timeout transmit t1 15 60 7 250 60 15 15 15 15
timeout transmit acknowledge t2 10 10 2 10 10 10 10 10 10
timeout connection check t3 20 20 10 250 20 20 20 20 20
Max. no. of APDUs until 12 12 12 12 60 12 12 12 12

acknowledgement (k)
number of APDUs until 8 8 8 8 8 8 8 8 8
acknowledgement (w)
TCP-parameters 1) 1)
2) 2) 2) 2) 2) 2) 2) 2) 2)
transmission optimization
initial TCP retransmission timeout 2500 2500 100 2500 2500 2500 2500 2500 2500
minimum TCP retransmission 250 250 100 1000 250 250 250 250 500
timeout
maximum TCP retransmission 5000 5000 200 10000 5000 5000 5000 5000 5000
timeout
MSS (maximum segment size) 1460 1460 1460 512 1460 1460 1460 1460 1460
transmit direction
3) 3) 3) 3) 3) 3) 3) 3)
TCP connection close RST
Firmwares
ETA2 —
ETA4 — — — — — — — —
ET84 — —
ET24 — — — — — — — —
1) The settings for TCP parameters can not be changed in CP-8000/CP-802x (ET84)
2) possible settings:
- default (ack delay, no nagle)
- bandwith (ack delay, nagle)
- throughput (no ack delay, nagle)
- response time (no ack delay, no nagle)
3) possible settings:
- close with FIN or RST (default)
- close with RST

Edition 06.2017, DC0-023-2.12
The following IEC 60870-5-104 parameters can be set per parameter group:
· Timeout Connection Setup t0

Timeout for connection setup.
Note:
The parameters Network connection | * | IEC 104 parameter | timeout
connection setup t0 or 104 parameter | group # | timeout connection
setup t0 or 104 parameter | standard group # | timeout connection setup
or 104 parameter | extended group # | timeout connection setup are not
evaluated by the protocol!
· Timeout Transmit t1
Timeout for transmit or test frames.
Transmitted data (Information/Transmit-/Test frames) must be acknowledged by the
remote station at the latest before expiry of the Timeout t1 with a transmit or test frame.
On timeout the connection is terminated and then re-established.
The Timeout t1 is to be parameterized with the parameter Network connection | * |
IEC 104 parameter | timeout transmit t1 or with the parameter 104 parameter
| group # | timeout transmit t1 or with the parameter 104 parameter |
standard group # | timeout transmit t1 or with the parameter 104 parameter
| extended group # | timeout transmit t1.
· Timeout Transmission Acknowledgement t2
Timeout for acknowledgement, if no data is transmitted t2<t1.
With the simultaneous transmission of user data (I-Frames) in both directions,
acknowledgements are sent together in the user data messages. For the data
transmission of user data in only one direction, an acknowledgement (S-frame) is sent
after Timeout t2 at the latest.
IEC 104 parameter | timeout transmit acknowledge t2 or with the parameter
104 parameter | group # | timeout transmit t1 or with the parameter 104
parameter | group # | timeout transmit acknowledge t2 or with the parameter
104 parameter | standard group # | timeout transmit acknowledge t2 or
with the parameter 104 parameter | extended group # | timeout transmit
acknowledge t2.
· Timeout Connection Test t3
Timeout for the transmission of Test-Frames, if no data traffic t3>t1.
If no data is transmitted with connection established, then a test frame (TESTFR act) is
sent after t3 at the latest. This must be replied to by the remote station, also with a Test-
Frame (TESTFR con). This test procedure can be performed independently by both sides
of a connection. The Timeout t2 is retriggered by the reception of
Information/Transmit/Test frames.
IEC 104 parameter | timeout connection check t3 or with the parameter 104
parameter | group # | timeout connection check t3 or with the parameter 104
parameter | standard group # | timeout connection check t3 or with the
parameter 104 parameter | extended group # | timeout connection check
t3.

DC0-023-2.12, Edition 06.2017
The following parameters can be set for each parameter group for "Maximum number of
unacknowledged I-format frames k and acknowledgement w":
· Maximum number of unacknowledged APDUs (k)

Greatest difference between receive sequence number and transmit status variable.
User data is transmitted from one station to the remote station without needing to receive
an immediate acknowledgement for the transmitted user data. However, if after a max.
number (k) of transmitted but not yet acknowledged ASDUs no acknowledgement has
been received, no further data is sent until the reception of the acknowledgement.
An acknowledgement must now be sent by the remote station before expiry of t1.
For IEC 60870-5-104 a sum acknowledgement is used i.e. all consecutively numbered
messages received without error up to a moment in time are acknowledged with an
acknowledgement message.
The maximum number of unacknowledged APDUs (k) is to be parameterized with the
parameter Network connection | * | IEC 104 parameter | Max. no. of
APDUs until acknowledgement (k)or with the parameter 104 parameter | group
# | Max. no. of APDUs until acknowledgement (k) or with the parameter 104
parameter | standard group # | Max. no. of APDUs until acknowledgement
(k) or with the parameter 104 parameter | extended group # | Max. no. of
APDUs until acknowledgement (k).
· Number of APDUs until acknowledgement (w)
Acknowledgement at the latest after reception of "w" I-format APDUs.
User data is transmitted from one station to the remote station without needing to receive
an immediate acknowledgement for the transmitted user data. An acknowledgement is
sent after the reception of a max. number (w) of user data messages (APDUs).
Recommendation: "w" should not exceed 2/3 of the "k"-value.
The number of APDUs until acknowledgement (w) is to be parameterized with the
parameter Network connection | * | IEC 104 parameter | number of APDUs
until acknowledgement (w) or with the parameter 104 parameter | group # |
number of APDUs until acknowledgement (w) or with the parameter 104
parameter | standard group # | number of APDUs until acknowledgement
(w) or with the parameter 104 parameter | extended group # | number of
APDUs until acknowledgement (w).
The following TCP/IP parameters are supported by the protocol firmware:
· MSS (Maximum Segment Size) transmit direction

One TCP packet typically has a maximum size of 1500 Bytes. It may only be so large, that
it fits in the transmission layer situated below, the Internet protocol IP. TCP and IP
protocols each define a header of 20 Bytes size. Therefore 1460 bytes are left over for the
user data in a TCP/IP packet.
With the parameter Network connection | * | TCP-parameter | MSS (maximum
segment size) transmit direction or with the parameter advanced parameters
| TCP/IP optimizations | MSS (maximum segment size) transmit direction
the maximum user data length is determined in the TCP/IP packet (max. 1460 Bytes).
The modification of the parameter "MSS (Maximum Segment Size) transmit direction" is
then definitely required, if TCP/IP is implemented in combination with transmission
systems which cannot transmit the TCP packets with the max. defined size (e.g. GPRS
supports max. 500 Bytes).
· Transmission optimization
The data transmission over TCP/IP can be optimized with the parameter Network
connection | * | TCP-parameter | transmission optimization or with the
parameter advanced parameters | TCP/IP optimizations | transmission
optimization for the following requirements:
- Default (ACK delay, no Nagle)
- Bandwidth (ACK delay, Nagle)
- Throughput (no ACK delay, Nagle)
- Reaction time (no ACK delay, no Nagle)
(for details about this, refer to section "Data Transmission Procedure")

Edition 06.2017, DC0-023-2.12
· Maximum Segment Size (MSS)

Rarely some communication systems supports only a restricted maximum segment size
(MSS) for Ethernet frames (MSSmax = 1460 bytes).
e.g.: some GPRS systems supports only max. MMS = 512 bytes.
The max. segment size (MMS) can be set with the parameter Network connection | *
| TCP-parameter | MSS (maximum segment size) transmit direction or with
the parameter advanced parameters | TCP/IP optimizations | MSS (maximum
segment size) transmit direction.
· Initial value TCP expected acknowledgement time
The data transmission at TCP-level starts with the set initial value for the expected
acknowledgement time. The initial value is to be set with the parameter Network
connection | * | TCP-Parameter | Minimum TCP Quittungserwartungszeit or
with the parameter advanced parameters | TCP/IP optimizations | TCP
retransmission timeout | initial TCP retransmission timeout. Depending
on the quality of the connection, the expected acknowledgement time is adapted
dynamically between the parameterized minimum and maximum TCP expected
acknowledgement time.
· Maximum TCP expected acknowledgement time
The maximum TCP expected acknowledgement time can be modified with the parameter
Network connection | * | TCP-parameter | maximum TCP retransmission
timeout or with the parameter advanced parameters | TCP/IP optimizations |
TCP retransmission timeout | maximum TCP retransmission timeout.
· Minimum TCP expected acknowledgement time
The minimum TCP expected acknowledgement time can be modified with the parameter
Network connection | * | TCP-parameter | minimum TCP retransmission
timeout or with the parameter advanced parameters | TCP/IP optimizations |
TCP retransmission timeout | minimum TCP retransmission timeout.
· TCP connection close
The mode for the termination of a TCP/IP connection can be modified with the parameter
Network connection | * | TCP-parameter | TCP connection close or with the
parameter advanced parameters | TCP/IP optimizations | TCP connection
close for the following requirements:
- close with FIN or RST (default)
- close with RST
(for details about this, refer to section "Data Transmission Procedure")
By default, the parameters are set so that no modification is necessary.

DC0-023-2.12, Edition 06.2017
8.2.3.1 Data Transmission Procedure
from the master station to the remote terminal unit takes place spontaneously for each LAN
connection. For each LAN connection, the data transmission is comparable with that between
2 stations over a virtual point-to-point connection.
Data Transmission Procedure

The prioritization and 104-blocking of the data to be sent takes place on the basic system
element (BSE). The data transmission is started after a startup or with redundancy switchover
after establishment of the TCP/IP connection and after "STARTDTact".
The data storage on the basic system element is managed individually for each LAN
connection (excluded from this are special redundancy modes such as e.g. "synchronous
connections").
Data messages "to all" are already split up selectively for every LAN connection by the
communications function on the basic system element (BSE).
Data messages to "prepared connections" will be requested by the protocol element but not
sent and discarded without error message. The protocol element will send a positive activation
confirmation (ACTCON+) for general interrogation command and test command to the basic
system element.
The data processing of the TCP packets can be influenced by the parameter Network
connection | * | TCP-parameter | transmission optimization or with the
parameter advanced parameters | TCP/IP optimizations | transmission
optimization – the moment for the transmission of a TCP packet is controlled by the Nagle
algorithm. The Nagle algorithm is applied with the TCP protocol and should prevent too small
packets, for which the additional overhead due to header etc. is considerably larger than the
actual user data.
Nagle algorithm for the transmission of TCP packets:
· If a TCP packet is full, then send immediately

· If a TCP packet is not full, then this is first sent when a TCP acknowledgement is received.

Edition 06.2017, DC0-023-2.12
The data pick-up from the basic system element is performed in such a way, that on the one
hand the blocking per connection is optimally utilized, and on the other, one connection with a
lot of data does not block others unnecessarily long. With the data pick-up for transmission,
the connections are processed in ascending order. The communications function on the basic
system element performs the prioritization of the data per connection. During the data pick-up,
the highest priority data object is always offered for transmission.
Note:
For the optimum prioritization and blocking of the data with LAN/WAN communication, only
1 priority level is to be used.
à As a result a more favorable prioritization for LAN is achieved, since the data for
transmission for each connection (=destination station) are requested in groups
(=blocked) by the LAN/WAN protocol element. In addition, through the blocking at TCP/IP
level, several messages for this connection are transmitted.
à Due to this the processing of the connections according to the Round-Robin principle is
ensured (Connections are processed in ascending order).
System data is processed with high priority by the communications function on the basic
system element and transferred to the LAN/WAN protocol element for transmission as fast as
possible.
Data transmission control with Start/Stop (data flow block)

For every TCP connection, one station is either "Listener (Server)" or "Connector (Client)".
After startup, redundancy switchover or after a failure of the connection, every connection on
TCP level is established by that station defined as "Connector (Client)".
For IEC 60870-5-104 the data transfer is controlled by the Controlling-Station with the
messages Start/Stop data transfer. After establishment of a connection at TCP/IP level, the
transmission of the data according to IEC 60870-5-104 is stopped.
The data transfer according to IEC 60870-5-104 is started by that station defined as
"Controlling Station" with STARTDTact (Start Data Transfer Activation).
After reception of the confirmation from the remote station (STARTDTcon = Start Data
Transfer Confirmation) the connection is ready for the transmission of the data.
According to IEC 60870-5-104 the data transmission must be started by the Controlling
Station with STARTDTact (Start Data Transfer ACTIVATION). The start must be confirmed by
the remote station (Controlled Station) with STARTDTcon (Start Data Transfer
CONFIRMATION). If no STARTDTcon has been received within t1 after sending
STARTDTact, the connection is terminated again. User data may only be transmitted after
successful connection establishment.
The data transmission is stopped by the Controlling Station with STOPDTact (Stop Data
Transfer ACTIVATION). STOPDTact is confirmed by the remote station (Controlled Station)
with STOPDTcon (Stop Data Transfer CONFIRMATION).
After start of the IEC60870-104 data transfer with the message STARTDTact by the
controlling station, a general interrogation command can be sent to the controlling station if
required (for update of the process data base). The function GI after "Start Data Transfer" can
be enabled with the parameter advanced parameters | compatibility | GI after
START DT or with the parameter 104 parameter | advanced parameters | GI after
START DT for all connections of the protocol element.
With function enabled, the protocol element will send an internal system message to the basic
system element; this will initiate a sending of a general interrogation command to the
controlling station.

DC0-023-2.12, Edition 06.2017
Start-/Stop data transfer messages are transmitted with U-Frames "Unnumbered Control
Functions" and are used by the Controlling Station in order to control the data transfer from a
Controlled Station. Stop Data Transfer is used especially when several connections are
established to one station but one connection (e.g. due to redundancy) is not used. Start/Stop
Data Transfer is intended to prevent a possible loss of data during the switchover to another
connection.
The duration of the stopped data transfer is not monitored!
If, as Controlling Station, one remote station blocks the data transfer for a longer period, an
overflow of the data storage (rings) on the basic system element (BSE) can occur and through
this a fault in the system is signaled.
The handling of the user data with stopped "Data Transfer" can be parameterized for each
connection with the parameter connection definition | stop behaviour.
Handling of the user data if the data transmission is stopped with STOPDTact:
· "Save" [Default]
The data is stored in the data storage of the communications function on the basic system
the remote station.
Advantage: Storage of the data with stopped data transfer
Disadvantage: Ring overflow possible
· "Discard"
All data in transmit direction are read out immediately from the basic system element
(BSE) by the protocol firmware, not transmitted and discarded without error message.
As a result an overflow of the data storage (rings) is prevented.
Advantage: Ring overflow is prevented
Disadvantage: Data loss
Connection Termination
The following possibilities for closing a TCP/IP connection are available:
· Close with FIN or RST (default)

─ 4-way handshake (FIN, ACK, FIN, ACK) for all “known IP addresses“ (configured in the
connection definition).
Such a termination occurs for instance if a IEC 60870-5-104timeout expires or when a
IEC 60870-5-104message with an illegal frame format is received. If the remote station
cannot be reached or does not respond to the FIN, the socket will only be deleted after
a TCP timeout (3 minutes). During this time the socket and its resources are occupied
and this can cause resource problems with the result that no new connections can be
established. Possible reasons:
- Denial-of-service attack
- Faulty remote station
─ 1-way handshake (RST)
Such a termination occurs for instance if
- the IP address of the remote station is not included in the connection definition
- a connection to a remote station is already established, and the remote station tries to
establish further connection.
· Close with RST
IEC 60870-5-104 defines the termination of a connection with 4-way handshake. The
closing of a connection with 1-way handshake (RST) only can be used for the following
cases:
─ robust interface required (e.g. with an insecure WAN or Internet)
─ downward compatible applications

Edition 06.2017, DC0-023-2.12
For each connection, all data messages transmitted must be acknowledged by the remote
station. Thereby, not every individual IEC 60870-5-104 packet that can contain several IEC
60870-5-104 message objects must be acknowledged, rather several consecutively numbered
messages received without error up to a moment in time can also be acknowledged in one
operation with one acknowledgement message (sum acknowledgement procedure).
With this sum acknowledgement procedure, user data is transmitted from a station to the
remote station without an acknowledgement needing to be received immediately for the
transmitted user data. If no acknowledgement has been received after a maximum number (k)
of transmitted but not yet acknowledged IEC 60870-5-104 packets (ASDU's), no further data
is sent until reception of the acknowledgement.
The max. number (k) of messages is to be set with the parameter Network connection | *
| IEC 104 parameter | Max. no. of APDUs until acknowledgement (k)or with the
parameter 104 parameter | standard group # | Max. no. of APDUs until
acknowledgement (k) or the parameter 104 parameter | extended group # | Max.
no. of APDUs until acknowledgement (k) .
An acknowledgement must now be sent by the remote station before expiry of t1.
With the simultaneous transmission of user data (I-Frames) in both directions,
acknowledgements are sent together in the user data messages. For the data transmission of
user data in only one direction, an acknowledgement (S-frame) is sent after Timeout t2 at the
latest.
On reception of IEC 60870-5-104 packets (APDUs) with user data, an acknowledgement must
be sent at the latest after reception of a settable maximum number of messages. The max.
number (w) of messages is to be set with the parameter Network connection | * | IEC
104 parameter | number of APDUs until acknowledgement (w) or with the
parameter 104 parameter | standard group # | number of APDUs until
acknowledgement (w) or with the parameter 104 parameter | extended group # |
number of APDUs until acknowledgement (w) .
The retries are (insofar as necessary) performed automatically by the TCP/IP layer of the
protocol until the termination of the connection and can only be influenced indirectly with the
parameter Network connection | * | TCP-Parameter | Initial value TCP
retransmission timeout , Network connection | * | TCP-parameter | maximum
TCP retransmission timeout , Network connection | * | TCP-parameter |
minimum TCP retransmission timeout or with the parameter advanced parameters |
TCP/IP optimizations | TCP retransmission timeout | initial TCP
retransmission timeout , advanced parameters | TCP/IP optimizations | TCP
retransmission timeout | maximum TCP retransmission timeout , and the
parameter advanced parameters | TCP/IP optimizations | TCP retransmission
timeout | minimum TCP retransmission timeout .
The data transmission at TCP level starts the data transmission with the settable initial value
for the expected acknowledgement time. Depending on the quality of the connection, the
expected acknowledgement time is adapted dynamically between the parameterized minimum
and maximum TCP expected acknowledgement time.
If, with connection established, the IEC 60870-5-104 acknowledgement for transmitted data
(information/transmit/test frames) is missing for longer than the set 104 expected
acknowledgement time (timeout t1), all IEC 60870-5-104 messages already sent but not yet
acknowledged are negatively acknowledged to the basic system element (BSE), the TCP
connection is terminated with RST and the remote station flagged as failed.
The connection is setup again after a fixed implemented delay time of 2 seconds.

DC0-023-2.12, Edition 06.2017
Note:
The parameters Network connection | * | IEC 104 parameter | timeout
connection setup t0 and 104 parameter | group # | timeout connection setup
and 104 parameter | standard group # | timeout connection setup and 104
parameter | extended group # | timeout connection setup are not evaluated by
the protocol!
The error message for the failed connection is reset after successfully established connection
at TCP level.
8.2.3.3 Failure Monitoring
The monitoring of every established connection is carried out by the active master / remote
terminal unit either by means of (subject to acknowledgement) spontaneously transmitted user
data messages or by means of cyclic transmitted messages (Test-Frames). The failure
monitoring can be carried out independently by both participating stations of a connection.
The Test-Frames are generated by the protocol firmware itself and are not transferred to the
basic system element.
If no user data is transmitted with a connection established and activated data transfer, a
Test-Frame (TESTFR act) is sent at the latest after expiry of the time t3 (Timeout Connection
Test). This Test-Frame must be replied (acknowledged) by the remote station with a Test-
Frame (TESTFR con) at the latest before expiry of the timeout t1.
The "Test function of the link layer" (test command) also enables a cyclic message
transmission and monitoring controlled by the basic system element.
This test function can be parameterized on the basic system element (BSE) in the IEC 60870-
5-101/104 parameter block.
The timeout t3 is retriggered with the transmission of user data messages or test frames. After
a message transmission, the remote station is signaled as failed after expiry of the monitoring
time t1 (Timeout) and the TCP connection is terminated with RST or FIN. For further details,
refer to section “Acknowledgement Procedure”.
No further data is sent to failed remote stations until successful establishment of the
connection.
the re-reachable remote station.

Edition 06.2017, DC0-023-2.12
Error Handling for “Failed” Connections
The failure of a connection can be suppressed with the parameter connection definition
| Failure.
The error handling for faulty connections with “failure = suppress” can be set with the
parameter advanced parameters | Error handling for connections with
”failure = suppress”.
Error handling for faulty connection if ”failure = suppressed” – Mode-0“: (=default)
· no error in diagnostics
· no NT-Bit emulation for received data by BSE
· no general interrogation command initiated by BSE after connection error
Error handling for faulty connections if ”failure = suppressed – Mode-1“: *)
· no error in diagnostics
· NT-Bit emulation for received data by BSE
· general interrogation command initiated by BSE after connection error
______
*) ETA2 supports only mode-1 (without parameter)!
not supported by ETA4 with “IEC60870-5-104 redundancy with 2 Ethernet interfaces”!
During connection failure all data messages in transmit direction (including “End of Init”) will
be discarded. (ring overflow caused by non-connected remote stations will be avoided).
Connection Failure “notify/suppress” with 104-Redundancy with 1 Ethernet Interface
Supported settings for “failure = notify/suppress“ (each redundancy group):
Failure for “virtual connection“ Failure for “real connection(s)“ *) supported

notify notify ü
notify suppress ü
suppress notify
suppress suppress
*) Parameter settings for all real connections of a redundancy group must be the same!

DC0-023-2.12, Edition 06.2017
After startup, the connection for every connection is established to TCP/IP level and then to
104-level by the Controlling Station by means of STARTDTact (Start Data Transfer
Activation). Afterwards the transmission of user data and other system messages to the
remote station is started either immediately or only after the transmission of the INIT-End
message.
The INIT-End message "<TI=70> End of Initialization" is only transmitted to the remote station
for each ASDU after startup of the component or the basic system element, if the following
preconditions are fulfilled:
· Connection is established at TCP/IP level

· Connection is established at IEC 60870-5-104 level with STARTDTact
· Sending of „end of initialization" must be enabled on the basic system element in the IEC
60870-5-101/104 parameter block
· "INIT-End" has been received by the basic system
· Parameter connection definition | stop behaviour = “save”
· Parameter connection definition | failure = “notify”
from the master station to the remote terminal unit takes place spontaneously with connection
established and for each connection. The prioritization and 104-blocking of the data ready to
be sent takes place on the basic system element (BSE). The data transmission is started after
a startup or, with redundancy switchover, after successful establishment of the connection.

Edition 06.2017, DC0-023-2.12
station after the internal connection initialization or after the master station has detected a loss
of information. The general interrogation function <TI:=100> of the master station requests the
remote terminal unit connected over one connection to transmit the current values of all its
process variables.
communications function on the basic system element (BSE) station-selective (per
connection) to the protocol element of the master station and transmitted by this to the remote
terminal units.
A general interrogation command to a "prepared connection" will not be transmitted but

positive confirmed (ACTCON+) by the protocol element.
After start of the IEC60870-104 data transfer with the message STARTDTact by the
controlling station, a general interrogation command can be sent to the controlling station if
required (for update of the process data base). For further details, refer to section "Data
Transmission Procedure" | "Data transmission control with Start/Stop (data flow block)".
If the IEC60870-104 data transfer will be stopped by the controlling station using STOPDTact
during running general interrogation, the not sent general interrogation data stored on BSE
can be discarded or continued with sending after STARTDTact.
This function can be enabled on BSE with the parameter Communication | PRE# |
Advanced settings | Failure behavior for process inform (GI). With selection
“Delete“ all process information with cause of transmission “interrogated by station
interrogation“ including ACTCON and ACTTERM will be deleted in case of communication
failure or STOPDTact.
The deactivation of a general interrogation <COT:= 8> (DEACT) is not supported. If a

deactivation is received, the protocol element responds with DEACTCON- with <COT:=45>
(unknown cause of transmission).

DC0-023-2.12, Edition 06.2017
In networks and in systems with time-critical applications, a precise time is essential.
The clock synchronization for IEC 60870-5-104 can be performed in the following ways:
· Clock synchronization command <TI:=103>

· Network Time Protocol (NTP) according to RFC 1305
· Network Time Protocol (SNTP) according to RFC 2030
For SICAM RTUs a clock synchronization using NTP is recommended!
Messages that are transmitted after a startup contain the
· current time, if the automation unit already has been synchronized previously
· relative time from startup (reference date), if the automation unit already has never been
synchronized
Reference date for SICAM RTUs: 1.1.2001
Reference date for Ax1703: 1.1.1997
In both cases, the time tag is marked as invalid until the first reception of the synchronizing
event.

Edition 06.2017, DC0-023-2.12
8.2.7.1 Clock Synchronization Command
The clock synchronization of the remote station can be performed over the network.
With SICAM RTUs the clock synchronization command <TI:=103> is sent spontaneously at a
change of time and cyclic 1x per minute with the actual time.
The procedure for clock synchronization defined in IEC 60870-5-5 is not recommended for
use with network communication, because the transmission delay cannot be evaluated and
therefore a correction of transmission delay cannot be performed properly.
However, the clock synchronization with the clock synchronization command can be
implemented in configurations with networks if the "maximum network delay" is less than the
accuracy required for time synchronization.
If for instance the network provider guarantees, that the maximum delay for the transmission
in the network is never greater than 400 milliseconds and the accuracy required for the time
synchronization is only 1 second, then this procedure can be used for clock synchronization.
If the accuracy of clock synchronization via network is insufficient, a local time signal receiver
or clock synchronization via NTP must be used by the remote station.
SICAM RTUs as Sender of Clock Synchronization Command

th
The clock synchronization command will be sent cyclic at the 30 second of minute.
In SICAM RTUs the transmission of the clock synchronization command is initiated by the
Before switchover of daylight saving time the clock synchronization command will be sent (in
advance) with new time.
SICAM RTUs as Receiver of Clock Synchronization Command

With SICAM RTUs the correct setting of time is only ensured if the clock synchronization
th th
command will be received between 10 and 50 second.
In SICAM RTUs the new time will be set at next change of minute.
Attention:
With SICAM RTUs the new time must be sent in (advance) at change of daylight saving time,
otherwise the time is not correct for up to 1 minute.
8.2.7.2 Network Time Protocol (NTP/SNTP) according RFC 1305
For further details refer to chapter 12, NTP/SNTP.

DC0-023-2.12, Edition 06.2017
With connection established (Data Transfer must be started and the number of
unacknowledged APDUs must not be reached) data messages in command direction are
always transmitted spontaneously from the master station to the remote station. The
prioritization and 104-blocking of the data to be sent already takes place on the basic system
element (BSE). Commands and other messages defined according to IEC 60870-5-104 are
always transmitted without 104-blocking.
For commands in transmit direction the function “control location check“ can be enabled
optionally. If control location check is enabled, commands will be sent to remote station only if
the originator address of the command was enabled before by PRE control message.
A test command <TI:=107> with cause of transmission <COT=6> (=activation) can be sent by
the basic system element for each connection.
The test command must be confirmed by the remote station with cause of transmission
<COT=7> (=activation confirmation) and P/N=1 (ACTCON+).
The check of the correct confirmation of the test commend will be done on the basic system
element.
A test command sent from the basic system element a "prepared connection" will not be
transmitted but positive confirmed (ACTCON+) by the protocol element.
For further details, refer to section "Data Transmission Procedure" and “Message
Conversion”.
8.2.8.1 Command Transfer Monitoring (Dwell Time Monitoring)
During the transmission of data in networks, unwanted delays can occur. So that no unwanted
process behavior is triggered due to a delayed output of commands, the LAN/WAN protocol
element can monitor the transmission time (dwell time) of the data in the network for selected
process information in control direction.
The dwell time monitoring prevents the system of processing "old commands".
If the monitoring is activated, on reception of a command message over the LAN interface, the
time tag in the message is compared with the current time of the component.
If the determined command delay time (transmission time of the data in the network) is greater
than the parameterized command delay monitoring the command message is discarded
without error message.
If the time of the component is not yet set while dwell time monitoring is activated, the
behavior to handle received command messages can be selected with the parameter
advanced parameters | Discard command when local time not set or with the
parameter Command delay supervision | Discard command when local time not
set.
The controlling station detects the failed command output through the missing of the
confirmation of activation (ACTCON).
The time for the command delay monitoring is to be parameterized on the basic system
element (BSE) in the IEC 60870-5-101/104 parameters per protocol element.
The command delay monitoring can also be deactivated (Command delay
supervision = 0).
To localize the error, the number of commands discarded by the command delay monitoring
since RESET is summed for each connection and the last discarded command messages are
also saved in a diagnostic ring. The counters and the diagnostic ring can be read out with the
SICAM TOOLBOX II (ST-Emulation).

Edition 06.2017, DC0-023-2.12
Monitoring the command delay for the following message types (TI's):
· <TI:=58> Single command with time tag CP56Time2a
· <TI:=59> Double command with time tag CP56Time2a
· <TI:=60> Regulating step command with time tag CP56Time2a
· <TI:=61> Setpoint command, normalized value with time tag CP56Time2a
· <TI:=62> Setpoint command, scaled value with time tag CP56Time2a
· <TI:=63> Setpoint command, short floating point number value with time tag
CP56Time2a
· <TI:=64> Bit pattern of 32 bit with time tag CP56Time2a
· <TI:=107> Check command with time tag CP56Time2a
Notes:
- The message conversion in receive direction can also generate the assigned message types
without time tag. As a result, indirectly the internal type identifications <TI=45, 46, 47, 48,
59, 50, 51 and 104> are also affected.
- The command delay monitoring is only carried out for command messages with the cause of
transmission ACT (Activation)!
For commands in transmit direction the function “control location check“ can be enabled
optionally.
If the function “control location check” is disabled (not used), commands will be sent always to
remote station.
If the function "control location" is enabled, commands will be sent to remote station only if the
8.2.8.2.1 Control Location Check
For commands in transmit direction the function “control location check” can be enabled
optionally.
If the function “control location check” is disabled (not used), commands will be sent always to
remote station.
authority.

DC0-023-2.12, Edition 06.2017
If the function “control location check” is enabled and If the originator address in the
spontaneous information object "Command" does not match with one of the control locations
previously set or if no control location has been preset:

the PRE.
8.2.8.2.2 Set Control Location

0 Not defined
Note:
control function.
enabled").
enabled").


Edition 06.2017, DC0-023-2.12
A counter interrogation command "to all" triggered in the system is always transferred by the
connection) to the protocol element of the master station and transmitted by this to the remote
terminal units.
60870-5-101/104".

DC0-023-2.12, Edition 06.2017

Routes
designed redundant.
In this section, not the possible redundancy concepts themselves that can be realized are
described, rather only those functions supported by the protocol element for the support of
redundant systems or communication routes.
The following redundancy modes are supported:
· PSI-Redundancy (Synchronous Connections)

· 104-Redundancy
· 1703-Redundancy
Note
Only 1 redundancy mode can be used per protocol element!
· A ll redundancy modes (except "deactivation of interface") can use the additional

functionality of dual-LAN interface (DNIP):
· Switch Mode
· Line Mode (Siemens specific)
· RSTP Mode
Using "Line Mode" or "RSTP Mode" of dual-LAN interface (DNIP), redundancy concepts on
Ethernet level can be realized.
8.3.1 PSI-Redundancy (Synchronous Connections)
The redundancy mode "PSI-Redundancy (synchronous connections)" is a proprietary function

and is only implemented in plants with a control system (Controlling Station) from the
manufacturer "PSI". This redundancy function is not defined in the IEC 60870-5-104 standard!
This redundancy mode is selected by setting the parameter redundancy | Redundancy

mode to PSI-Redundancy and with that is continuously activated.
A switchover/control of the redundancy through system-internal redundancy control messages

as well as the redundancy functions of the Controlling Station are not supported for this
redundancy mode!

Edition 06.2017, DC0-023-2.12
Functioning method of synchronous connections:
· The data is sent over the synchronous connections with the same data content
· The data is sent over the synchronous connections in the same order
· The data is sent over the synchronous connections with the same IEC 60870-5-104
sequence number
The data to the first synchronous connection established is transmitted beginning with the
sequence number "0". The data to other synchronous connections established later is
transmitted with the current consecutive sequence number (the sequence number for
received data is individual for each synchronous connection)
· The data is transmitted over the synchronous connections with as little chronological offset
as possible
· In receive direction, there is no specific function for synchronous connections – received
data is transferred to the basic system element for each synchronous connection
Controlling Controlling
Controlling Station(s)
Station 1 Station 2
Network
Ž (optional) Controlled Station

[PRE] [PRE]
Legend:
•
VC
Œ ….. Data in transmission direction are stored in one central process image • for the
virtual connection (=for all synchronous connections together ) .
Ž ….. The data of the (1703-internal) virtual connection are transmitted with
- equal data content
- equal sequence numbers
- preferably small temporal offset
•
Process image
on the synchronous connections to the connected remote stations .
(Control of the data transmission with STARTDTact may not be used with synchronous
connections)
• ….. The data transmission between BSE and PRE takes place via a „virtual connection“
• ….. Data in receive direction are passed from each of the synchronous connections to the
basic system element (BSE) either with the „virtual connection“ or with the
„real connection“ (settable).
[BSE]
Logical connection
• Œ
On the LAN/WAN protocol element, synchronous connections for PSI redundancy and normal
connections (without redundancy) can be used mixed.
For synchronous connections, system internally only 1 virtual connection may be

parameterized and at least 2 or more real connections. The synchronous connections form a
group – these are handled as one connection in transmit direction from the perspective of the
communications function on the basic system element.
The synchronism of the connections is controlled directly by the LAN/WAN protocol element.
The data transferred from the basic system element for transmission to the synchronous
connections are duplicated by the LAN/WAN protocol element to the assigned connections.
Due to the synchronism of the connections during transmission, the data throughput is defined
by the slowest remote station. With acknowledgement required, a further transmission can
only then take place when all remote stations have acknowledged.

DC0-023-2.12, Edition 06.2017
In transmit direction, on the basic system element the data is only routed to the "virtual
connection“ and passed on immediately to the remote station by the LAN/WAN protocol
element without TCP/IP blocking. If the control of the data transmission is stopped for one
connection, the data for this connection are discarded.
In receive direction, the data is passed on to the basic system element either with the station
number of the virtual connection or with the station number of the real connection. The
selection of the station number is performed with the parameter redundancy | station
number for received telegrams.
On failure of one real connection, this is signaled as failed. On failure of all real connections,
in addition the virtual connection is signaled as failed.
Necessary parameter settings for synchronous connection on the LAN/WAN protocol element:
· Virtual Connection
A selected connection is to be defined as virtual connection in the parameters
connection definition | Redundancy.
The virtual connection is only used for the internal communication with the basic system
element. This connection does not exist on the LAN (the IP address of the virtual
connection is of no significance and is not used).
Note:
For connections that are operated without redundancy, the parameter connection
definition | Redundancy is to be set to "none".
· Synchronous Connections (real connections)
All connections to the connected remote stations that are to be handled as synchronous
connections are to be defined as real connections in the parameters connection
definition | Redundancy.
For the real connections, in addition all necessary parameters of the connection
definition (such as IP address of the remote station,…) must be parameterized.
· IEC 60870-5-104 Data Flow Control of the own station (Controlling/Controlled)
The data flow control is defined for all synchronous connections together with the
parameter connection definition | data flow control for the virtual connection!
Necessary parameter settings of the communications function/topology on the basic system

element for synchronous connections in transmit direction:
· Deactivation of the state compression

· All user data must be assigned to one priority level
· For the failure management, the real connections must be entered in the topology
· For the real connections the disabling of system data must be activated in the topology
· For the failure management of the data in receive direction, the parameter setting of the
topology and the source ID is required
· The virtual connection and all real connections must be parameterized as "Controlled"
· No data may be routed to a real connection
Limitations:
· A special handling for synchronous connections is only implemented in transmit direction!

· Synchronous connections to one SICAM RTUs component must not be used!
· With synchronous connections the remote station may not use Start/Stop for the control of
the data transmission!
· The formation of redundancy groups for synchronous connections is not supported!
· Data in transmit directions must not be routed "to all"!

Edition 06.2017, DC0-023-2.12
8.3.2 104-Redundancy
With 104-redundancy, one remote terminal unit (Controlled Station) is connected with one or
several redundant master stations (Controlling Stations) over several logical connections. The
data transmission always takes place only over 1 started connection per redundancy group.
The redundancy mode "104-Redundancy" is defined in the IEC 60870-5-104 standard. It is

based on 2 or more connections that are jointly managed in one redundancy group.
This redundancy mode is selected by setting the parameter redundancy | Redundancy

mode to 104-Redundancy and through the connection-specific settings.
A switchover/control of the redundancy through system-internal redundancy control messages

as well as the redundancy functions of the Controlling Station are not supported for this
redundancy mode!
Redundancy Function according to IEC 60870-5-104:
· The master station (Controlling Station) and the remote terminal unit (Controlled Station)
support multiple "logical connections"
· Multiple logical connections are grouped to form one redundancy group
· Within a redundancy group only 1 logical connection may be started
· Only the master station (Controlling Station) decides which logical connection within a
redundancy group is started
· All logical connections of a redundancy group are monitored by means of test frames
· One redundancy group is only supplied by one process image
Note
The 104-redundancy can be used only within the same basic system element (BSE)!
(distributed 104-redundancy over several BSE's is not supported).
8.3.2.1 104-Redundancy with 1 Ethernet Interface
The 104-redundancy with 1 Ethernet interface enables the interfacing of one component to
remote stations with redundant Ethernet interfaces over 1 Ethernet network. Example for a
remote station with redundant interfaces is e.g. one system with two Ethernet interfaces or two
systems that are operated redundantly or a combination of both.
A TCP connection exists for every redundant Ethernet interface of the remote station and
these redundant connections are grouped to form a redundancy group. Only one of these
redundant connections may be started by the Controlling Station and data transmitted.
Simplified, on the NIP the 104-redundancy group can be seen as a switch that selects to
which connection the data to be sent are transferred. For details about Start/Stop refer to
section "Control of the Data Transmission with Start/Stop".
The Controlling Station switches between the redundant connections. There are two types of
redundancy switchover, the "soft switchover" and the "hard switchover".

DC0-023-2.12, Edition 06.2017
The soft switchover takes place via application, e.g. during tests or if a part of the controlling
station is to be taken out of operation. First the previously started connection is stopped with a
STOPDTact. Only when STOPDTcon has been received by the controlling station is a
STARTDTact sent to another connection. This then becomes the new started connection.
The hard switchover occurs when the controlling station detects a connection failure (e.g.
through a 104-Timeout). A STARTDTact is then sent immediately over another connection.
This then becomes the new started connection. If at this moment in the controlled station the
previously started connection is still established (because the controlled station has not
detected any connection failure), it is closed immediately.
Several redundancy groups independent of each other are possible.
Precisely one redundancy group can be assigned to each connection.

The SICAM RTUs internal redundancy control messages are not used in the controlled
station.
In the SICAM RTUs controlling station the entire LAN/WAN protocol element is switched to
"ACTIVE/PASSIVE" by the SICAM RTUs internal redundancy control messages.
Redundancy group 1 Redundancy group 2
Controlling Station Controlling Station
Interface 1 Interface 2 Interface 1 Interface 2
Network
Ž (optional) Controlled Station

VC
VC
[PRE] [PRE]
• • Legend:
Œ ….. Data in transmit direction are stored in a central process image • for each redundancy
group for the virtual connections .
(RG1 = Redundancy group 1, RG2 = Redundancy group 2)
Ž ….. The data transmission takes only place via the connection on which the
• •
Process image Process image
IEC60870-5-104 data transfer was startet with STARTDTact.
( Data transmission may only be activated on 1 connection )
RG1 RG2
per redundancy group
• ….. Data in receive direction are transmitted with the „virtual connection“
„logical connections“ towards the remote station (s) ( started

[BSE]
„logical connections“ towards the remote station (s) ( stopped
• Œ Œ

Edition 06.2017, DC0-023-2.12
Functioning method of the 104-Redundancy in the Controlled Station:
· Several redundancy groups can be defined for each LAN/WAN protocol element
· Every redundancy group consists of one or more "real" connections and only 1 "virtual
connection" for the communication to the basic system element.
The connections of a redundancy group in transmit direction are handled as one
connection (=virtual connection) from the perspective of the communications function on
the basic system element.
· The data is transmitted from the basic system element to the LAN/WAN protocol element
over the "virtual connection" assigned to the redundancy group.
As a result, the connections of a 104-redundancy group are supplied from only one
process image.
· The data is only transmitted to the remote station over the started "real connection" of the
104-redundancy group. The data transmission is controlled by the controlling station with
START/STOP Data Transfer.
· Every connection (and therefore the 104-sequence numbers also) is managed
independently
· In receive direction, the data of a 104-redundancy group are transmitted to the basic
system element with the station number assigned to the "virtual connection"
On the LAN/WAN protocol element, connections for 104-redundancy and normal connections
(without redundancy) can be used mixed.
Special parameter settings for 104-Redundancy in the "Controlling Station" on the LAN/WAN
protocol element:
· Redundancy Mode
The parameter redundancy | Redundancy mode must be set to "104-Redundancy".
· Redundancy
For all connections with controlling functionality according to 104-redundancy, the
parameter connection definition | Redundancy is to be set to "104-Contr-Red".
For the connections, in addition all necessary parameters of the connection
· IEC 60870-5-104 data flow control of the own station (Controlling/Controlled)
parameter connection definition | data flow control is to be set to
"controlling".
· Stop Behavior
parameter connection definition | stop behaviour is to be set to "save".

DC0-023-2.12, Edition 06.2017
Parameter settings for 104-Redundancy in the "Controlled Station" on the LAN/WAN protocol
element:
· Redundancy Mode
The parameter redundancy | Redundancy mode must be set to "104-Redundancy".
· Virtual Connection
For each 104-redundancy group, one connection is to be defined as "virtual connection" in
the parameters connection definition | Redundancy.
The virtual connection is only used for the internal communication with the basic system
element. This connection does not exist on the LAN (the IP address of the virtual
connection is of no significance and is not used).
Notes:
- Virtual connections may not be parameterized in the connection definitions as
"deactivated" or "without error signalization"!
- only the virtual connection must be included in the topology definition.
(including of real connections of 104-redundancy group in topology definition will
cause buffer overflow)
· Real Connections
All connections of the 104-redundancy groups to the remote stations are to be defined in
the parameters connection definition | Redundancy as "real connections".
For the real connections, in addition all necessary parameters of the connection
Note:
Real connections may not be parameterized in the parameters connection
definition | Connection as "deactivated"!
· Redundancy Group
With 104-redundancy a connection can be assigned to one of several redundancy groups.
Each redundancy group can be controlled independently of the other 104-redundancy
groups. For each 104-redundancy group, the data transmission can be activated over 1 of
the assigned connections.
The redundancy group is defined with the parameter connection definition |
RedGroup.
· IEC 60870-5-104 data flow control of the own station (Controlling/Controlled)
The data flow control is to be set to "controlled" for all connections of the IEC 60870-5-104
redundancy group with the parameter connection definition | data flow
control.
8.3.2.2 104-Redundancy with 2 Ethernet Interfaces
The 104-redundancy with 2 Ethernet interface enables the redundant interfacing of one
component to remote stations with redundant Ethernet interfaces over 2 Ethernet networks.
Example for a remote station with redundant interfaces is e.g. one system with two Ethernet
interfaces or two systems that are operated redundantly or a combination of both.
A TCP connection exists for every redundant Ethernet interface of the remote station and
these redundant connections are grouped to form a redundancy group. Only one of these
redundant connections may be started by the Controlling Station and data transmitted.
Simplified, on the NIP the 104-redundancy group can be seen as a switch that selects to
which connection the data to be sent are transferred. With 104-redundancy with two Ethernet
interfaces, on the BSE there is also a switch that selects to which NIP the data to be sent are
transferred and consequently the redundancy group extends over both NIPs and the BSE. For
details about Start/Stop refer to section "Control of the Data Transmission with Start/Stop".
The controlling station switches between the redundant connections. There are two types of
redundancy switchover, the "soft switchover" and the "hard switchover".

Edition 06.2017, DC0-023-2.12
The soft switchover takes place via application, e.g. during tests or if a part of the controlling
station is to be taken out of operation. First the previously started connection is stopped with a
STOPDTact. Only when STOPDTcon has been received by the controlling station is a
STARTDTact sent to another connection. This then becomes the new started connection.
The hard switchover occurs when the controlling station detects a connection failure (e.g.
through a 104-Timeout). A STARTDTact is then sent immediately over another connection.
This then becomes the new started connection. If at this moment in the controlled station the
previously started connection is still established (because the controlled station has not
detected any connection failure), it is closed immediately.
Several redundancy groups independent of each other are possible.
Precisely one redundancy group can be assigned to each connection.
The SICAM RTUs internal redundancy control messages are not used in the controlled
station.
In the SICAM RTUs controlling station the entire LAN/WAN protocol element is switched to
"ACTIVE/PASSIVE" by the SICAM RTUs internal redundancy control messages.
Controlling Station Controlling Station (Redundant)
Interface 1 Interface 2 Interface 3 Interface 4
Network Network
Ž Controlled Station
[PRE] [PRE]
• •
VC
VC
Ž
Legend:
Œ ….. Data in transmit direction are stored in a central process image • for each redundancy
group for the virtual connections .
Ž ….. The data transmission takes only place to those LAN /WAN-PRE on which the
IEC60870-5-104 data transfer was started with STARTDTact.
•
Process image
( Data transmission may only be activated on 1 connection )
( the virtual connection numbers must be set equal on both PRE’s ).
• ….. Data in receive direction are transmitted with the „virtual connection“
„logical connections“ towards the remote station (s) ˆ started
[BSE] „logical connections“ towards the remote station (s) ˆ stopped
• Œ

DC0-023-2.12, Edition 06.2017
Supported configurations for 104-Redundancy with 2 Ethernet Interfaces:
System System element PRE0 PRE1 PRE2 PRE3

ZSE=128 ZSE=129 ZSE=130 ZSE=131
ü ü
SICAM AK CP-2017/PCCX25 - SM-2558/ETA4 - SM-2558/ETA4
SM-2556/ETA2 SM-2556/ETA2
CP-2016/CPCX26 ü
x CP-2016 / ET24 - ü
CP-2019/PCCX26 CP-2019 / ET24 SM-2558/ETA4
CP-2016/CPCX26 ü
SICAM AK 3
CP-2019/PCCX26
CP-2016 / ET24 x - ü
CP-2019 / ET24 SM-2558/ETA4
CP-2016/CPCX26 ü
CP-2016 / ET24 CP-2016 / ET24 - ü
CP-2019/PCCX26 CP-2019 / ET24 CP-2019 / ET24 SM-2558/ETA4
Legend: x … not equipped

- … not possible
Functioning method of the 104-Redundancy in the Controlled Station:
· Several redundancy groups can be defined for each LAN/WAN protocol element
· Every redundancy group consists of one or more "real" connections and only 1 "virtual
connection" for the system-internal communication.
The connections of a redundancy group in transmit direction are handled as one
connection (=virtual connection) from the perspective of the communications function on
· The virtual connections must be parameterized the same on both LAN/WAN PRE's (same
number of virtual connections, same assignment to station numbers, same redundancy
groups).
· The number of the real connections and the station numbers for real connections may be
different on both PRE’s.
· Max. 4 real connections can be assigned to one redundancy group.
· The data transmission is started by the controlling station with the messages STARTDTact
and only 1 connection may be activated per redundancy group.
i.e. for each redundancy group a connection is activated either on interface 1 or on
interface 2.
The data transmission from the basic system element to the LAN/WAN protocol element is
also only activated for the "virtual connection" of the corresponding interface assigned to
the redundancy group.
· The data is transmitted from the basic system element to the LAN/WAN protocol element
over the "virtual connection" assigned to the redundancy group.
As a result, the connections of a redundancy group for 2 Ethernet interfaces are supplied
from only one process image.
· The data is only transmitted to the remote station over the activated "real connection" of
the redundancy group on one Ethernet interface.
· For all non-activated connections the connection is established at TCP level – every
connection is monitored with test frames.
· Every connection (and therefore the sequence numbers also) is managed independently
· In receive direction, the data of a 104-redundancy group are transmitted to the basic
system element with the assigned "virtual connection".
· On the LAN/WAN protocol element, connections for 104-redundancy and normal
connections (without redundancy) can only be used mixed on the less significant protocol
element (SSE = 128 or 129).
· For 104-redundancy with 2 Ethernet interfaces, the same rules are applicable for
parameter settings as for 104-redundancy with 1 Ethernet interface.

Edition 06.2017, DC0-023-2.12
With the redundancy mode “1703-redundancy”, one remote terminal unit (Controlled Station)
is connected with one or several master stations (Controlling Stations) over several logical
connections. The data transmission takes place over all connections.
The redundancy mode "1703-Redundancy" is selected by setting the parameter connection

definition | Redundancy to "none".
The switchover of the redundancy state ("ACTIVE" ó"PASSIVE") takes place system-internal
Redundancy function of the standard redundancy mode:
· The data transmission is started by the controlling station for every connection with
STARTDTact but not stopped with redundancy state "PASSIVE".
· The data transmission is carried out on all connections independent of the other
connections
· All data transferred from the basic system element to the LAN/WAN protocol element for
transmission are transmitted to the remote station even with the redundancy state
"PASSIVE".
· The data transmission is controlled from one specific process image for each connection
· The switchover to "PASSIVE" takes place globally per LAN/WAN protocol element and not
selectively per connection
In the redundancy state "PASSIVE", the message <TI:=107> check command with time tag
CP56Time2a can be disabled for transmission by the LAN/WAN protocol element with the
parameter redundancy | send test command (TI107) if passive and the message
<TI:=103> clock synchronization command with the parameter redundancy | send time
setting (TI103) if passive.

DC0-023-2.12, Edition 06.2017
For specific redundancy configurations the Ethernet interface can be deactivated.
Activation/deactivation of the Ethernet interface with:
· PST control message

· Redundancy control message
The activation/deactivation of the Ethernet interface with redundancy control message can be
enabled with the parameter redundancy | disable Ethernet-Port if passive.
If the activation/deactivation of the Ethernet interface with redundancy control message is
enabled the PST control message can not be used.
After restart of the protocol element the Ethernet-interface is activated per default.
Functions during "Interface DISABLE":
· Ethernet Port will be disabled

(disconnect Ethernet connection; TCP/IP connection will be released)
· no services possible (IEC 60870-5-104, WEB, NTP, remote operation)
Note: behavior is the same as with disconnected LAN cable.
· Warning: "interface DISABLED" (diagnostic message)

· all IEC60870-5-104 connections will be released after 104 timeouts
The function "Deactivation of interface" can not be used with dual-LAN interface (DNIP)!

Edition 06.2017, DC0-023-2.12
8.4 Dual-LAN Interface (DNIP)
The Dual-LAN interface (DNIP) is supported only by selected protocol element firmwares and
has a integrated "switch functionality" with 2 Ethernet interfaces (Port-0, Port-1).
The protocol element for Dual-LAN interface can be used for specific configurations (e.g.
redundancy on Ethernet).
The Dual-LAN interface can also be used as single LAN-Interface (e.g. as a preparation for
later use with Line- or RSTP-Mode).
Note
The Dual-LAN interface has only 1 IP-address (the Ports P0, P1 of the integrated switch does not have an
own IP-address).
Whith the Dual-LAN interface, there is only one protocol element (IEC 60870-5-104), supporting either P0
interface or P1 interface (but not both at the same time)!
The Dual-LAN interface can be used only in specified supported configurations, however, not for 2
independent, parallel working IEC 60870-5-104 interfaces!
Schematic configuration of Dual-LAN interfaces:
P0 P1
Switch
MAC-address
LAN/WAN protocol elelemt
The operating mode for the Dual-LAN interface can be set with the parameter advanced
parameters | DNIP (Dual Ethernet NIP) | operation mode.
Operation modes for Dual-LAN Interface:
· Switch Mode [Default] *)
· Line Mode *)
· RSTP Mode *)
· Single Mode
· Single + Service Mode
*) see also section "Function for the Support of Redundant Communication Routes"
on the Ethernet is to be determined for each individual port for all operation modes using dual-
LAN interface (Dual Ethernet NIP) with the parameter advanced parameters | DNIP
(Dual Ethernet NIP) | Ethernet speed and duplex | Port# ethernet speed
and duplex.

DC0-023-2.12, Edition 06.2017
Requirements for configuration of protocol elements on BSE:
PRE Note
SSE = 128 can not be used! *)
SSE = 129 Protocol element (IEC 60870-5-104) using dual-LAN interface (Port-0 + Port-1)
SSE = 131 Protocol element (IEC 60870-5-104) using dual-LAN interface (Port-0 + Port-1)
*) the dual-LAN interface (DNIP) use both RJ45 interface connectors – therefore no additional serial
interface using SM-0551 can be used in combination with DNIP
Cross Over
For the operating mode Switch or RSTP mode, each port of the DNIP can be set individually
to "Cross Over" by the protocol element. So standard network cables (LAN) can be used for
connecting to the next device (…it is not necessary to use Cross Over cables!)
The Function for "Cross Over" can be set with the parameter advanced parameters |
DNIP (Dual Ethernet NIP) | Crossover | Port# crossover.
The default setting is "standard" (=no Cross Over).
8.4.1.1 Switch Mode
The dual-LAN interface (DNIP) with operating mode "Switch Mode" will be used often in
configurations where only one additional device has to be connected to LAN network. When
using DNIP in 1703, no additional external switch is required in this configurations.
Switch
Network
P0 P1
DNIP 3rd Party

device
1703
In the operation mode "Switch Mode" all Ethernet frames will forwarded to all ports of DNIP
(also internal port to protocol element) and in all directions by the integrated switch.

Edition 06.2017, DC0-023-2.12
Switch Mode (overview):
· Received Ethernet frames including the MAC-address of the DNIP will be forwarded to
DNIP for processing
· Received Ethernet frames not including the MAC-address of the DNIP will be forwarded to
the other port by integrated switch
· Ethernet frames to be sent by DNIP will be sent from the integrated switch via the port
which has already learned the MAC-address of the remote station
· Received Ethernet frames (BROADCAST) will be forwarded by integrated switch to DNIP
for processing and retransmitted on the other port
· Ethernet frames (BROADCAST) to be send from DNIP will be sent from the integrated
switch via all ports
Note:
The forwarding of the data to the ports will by done by the DNIP's integrated switch hardware
and not by the firmware of the protocol element.
The actual status of the ports in "Switch Mode" can be monitored with the integrated web
server.
Status information for Switch Mode:
· MAC-address of the own DNIP interface

· Autonegotiation
Automatic negotiation of the speed of the link (10/100Mbit) and full-/half-duplex.
· Link
UUP (Link UP = link available), Down (Link DOWN = link not available)
· Speed
10Mbit or 100Mbit
· Duplex-Mode
full-duplex or half-duplex

DC0-023-2.12, Edition 06.2017
8.4.1.2 Line Mode (Siemens specific)
The dual-LAN Interface (DNIP) with the operation mode "Line Mode" will be used in
redundancy configurations on Ethernet level. The protocol element controls the function of the
integrated switch – only one port of the DNIP will be switched to "Forwarding".
Line Mode (overview):
· Data-link-layer (layer-2) is always established for both port's.

· The forwarding of the Ethernet frames will be done only on the port set to "forwarding" .
The other Ethernet port is set to "blocking".
· The protocol element controls the function of the ports for the forwarding of the Ethernet
packages:
- "blocking"
- "forwarding"
(default settings: port-0 = "forwarding", port-1 = "blocking")
In case of failure of the Ethernet connection ("link down" of the port set to "forwarding") the
protocol element will set immediately the failed port to "blocking" and the other port to
"forwarding".
Switch
Switch
Network
Switch
Switch
Control of the Switches i LAN with RSTP

P0 P1
logical connection for P0+P1 = OK
DNIP
logical connection for P0 = NOK
1703 LAN by switch „opened“
(controled by RSTP)
After the activation of a port of the DNIP-interface (= switch to "forwarding"), specific Ethernet
frames will be sent by protocol element to enable a fast learning of the new route to access
the MAC-address of the DNIP for the switches in the network. The used procedure is Siemens
specific (proprietary) with special Ethertype for Ethernet frames.

Edition 06.2017, DC0-023-2.12
The actual status of the ports in "Line Mode" can be monitored with the integrated web server.
Status information for Line Mode:

· Autonegotiation
Automatic negotiation of the speed of the link (10/100Mbit) and full-/half-duplex.
· Link
UP (Link UP = link available), Down (Link DOWN = link not available)
· Geschwindigkeit
10Mbit or 100Mbit
· Duplex-Mode
· Port Status
Forwarding ………Forwarding of Ethernet frames is enabled
Blocking ………… Forwarding of Ethernet frames is blocked
8.4.1.3 RSTP Mode
The RSTP protocol (Rapid Spanning Tree Protocol) is a standardized network protocol for
redundancy control of backup links in network with fast enabling/disabling of backup links.
The RSTP protocol is used for disabling redundant backup links in local network and if
necessary to enable backup links in case of failure of a link.
The maximum number of switches in a network will be calculated on the basis of the RSTP
timer for "max age": max. number of switches = max age - 1. That means, in a ring topology
up to 39 devices can be connected.
The RSTP-Protocol is defined in the standard IEEE 802.1D, Edition 2004.

DC0-023-2.12, Edition 06.2017
8.4.1.4 Single Mode
The dual-LAN interface (DNIP) has 2 integrated Ethernet interfaces (Port-0, Port-1).
The DNIP operating mode "single" use only LAN-interface with port-0 for the communication
with other remote systems.
The LAN-Interface with Port-1 will be deactivated by the protocol element and can not be used
(no monitoring / no diagnostic / no LED's for LAN-Interface Port-1!).
Note:
The dual-LAN interface (DNIP) with operating mode "Single Mode" can be used as a
preparation for later use with Line, Switch or RSTP Mode.
8.4.1.5 Single + Service Mode
The DNIP operating mode "Single + Service Mode" use only LAN-interface with port-0 for the
communication with other remote systems.
The LAN-Interface with Port-1 can be used only as connector for network service access; also
analyzing of network data transfer on Port-0 using WireShark is supported (data from Port-0
will "mirrored" to Port-1) (no monitoring / no diagnostic for LAN-Interface Port-1 (link down);
LED's will be displayed)!
Note:
The dual-LAN interface (DNIP) with operating mode "Single + Service Mode" can be used as
a preparation for later use with Line, Switch or RSTP-Mode.

Edition 06.2017, DC0-023-2.12
element in the SICAM RTUs internal format. These are converted by the protocol element to
the IEC 60870-5-104 message format on the line and transmitted according to the
transmission procedure of the IEC 60870-5-104 protocol.
Data in receive direction are converted on the transmission line by the protocol element from
IEC 60870-5-104 format to a SICAM RTUs internal format and transferred to the basic system
element.
Object Numbering
All IEC 60870-5-104 message objects are transmitted with an unambiguous IEC 60870-5-104
sequence number. In one TCP-packet several IEC 60870-5-104 message objects can be
transmitted. A blocked IEC 60870-5-104 message (with several individual messages) is
handled as one message object.
The sequence number is managed for each connection and is an ascending number in the
range 0-32767 (modulus 32768). The sequence number is used for the acknowledgement
procedure defined for IEC 60870-5-104.
8.5.1 Blocking
For the optimum utilization of the transmission paths, for the data transmission with
IEC 60870-5-104 protocol the "Blocking" according to IEC 60870-5-101/104 is implemented.
This function is performed on the basic system element (BSE) according to the rules
applicable for this. Data to be transmitted are thereby already blocked on the basic system
element and passed on to the protocol element for transmission.
With LAN-communication, several messages blocked according to IEC 60870-5-104 can be

entered in one TCP-packet before this is transmitted.
length are transmitted SICAM RTUs internal in several blocks to the basic system element
(BSE) because of the additionally required transport information.

DC0-023-2.12, Edition 06.2017
For the coupling to external systems, if necessary the following special functions can be

· time stamp (IV=1) in messages in transmit direction
· WhiteList Filter
· Data Throughput Limitation
· Settings for Project DBAG
· Settings for Project RWE
With the setting of the parameter connection definition | summertime to “suppress”,

the summer time bit (SU) in the time tag is always set to “0" by the protocol element for all
messages with time tag in transmit direction.
8.5.2.2 Day of Week = 0 for all Messages in Transmit Direction
With the setting of the parameter connection definition | day of week to “suppress”,
the day of the week (DOW) in the time tag is always set to “0” by the protocol for all
messages with time tag in transmit direction.
Note:
8.5.2.3 Time stamp (IV=1) in Messages in Transmit Direction
If the time synchronization of the own AU fails (i.e. after timeout of free running time or
monitoring time for sync. event), the I bit of the internal system clock will be set in
SICAM RTUs. All data with time stamp from local I/O’s will be sent with IV=1 for time tag. All
data with time stamp from remote RTU’s via serial or LAN based interface will be sent with IV-
Bit for time tag from remote RTU.
With the setting of the parameter advanced parameters | time stamp (IV=1) in
messages in transmit direction and if the time synchronization of the own AU fails, the
protocol element will send all messages with <TI:=30, 31, 32, …40> in transmit direction with
IV=1 for time tag.
Note:
In Ax 1703 the I bit of the internal system clock will not be set.
The failure of the time synchronization of the own AU must be sent in Ax 1703 with a protocol
element control message to the protocol element (user error à message conversion à
protocol element control message).

Edition 06.2017, DC0-023-2.12
With the setting of the parameter connection definition | originator address to

“suppress”, for all messages in transmit direction the originator address is always set to “0” by
8.5.2.5 WhiteList Filter
Caused by increased using of the norm protocol IEC 60870-5-101/104 in the area of the
telecontrol engineering/process automation this protocol is also very often used to exchange
data between different providers (”net couplings“).
For the protection of the own network and also not send any unwanted telegrams to the
remote network, the data traffic is reduced to the absolutely necessary minimum at such
interfaces.
Only defined telegrams (selected by type identification and cause of transmission) will be sent
in transmit direction to the remote network and only defined telegrams will be taken in receive
direction at WhiteList Filter enabled.
The WhiteList Filter can be enabled for each single connection with the parameter
connection definition | profile (type identification check).
Possible parameter setting: … (profile definitions see later in this chapter) *)
· WhiteList Filter
- This profile can be used on interfaces between different providers or regions within same provider.
- Only selected type identifications from “Interoperability of SICAM RTUs using IEC60870-5-104 (ETA4)” incl.
selected type identifications used by SICAM RTUs in private range will be passed through in transmit-/receive
direction (see profile definition for “WhiteList Filter”).
· WhiteList Filter for passive PRE

- This WhiteList Filter is only active when the protocol element (PRE) is set to redundancy state “passive” with
redundancy control message.
- In redundancy state “passive” the profile for “WhiteList Filter” is used and additionally the system messages in
the private range for SICAM RTUs <TI:=135> „SICAM RTUs systemdata container (TI:=135, FC=148, IC=04)“
will be passed.
- In redundancy state “active” the profile “SICAM RTUs - IEC104“ will be used.
· SICAM RTUs - IEC104 (“SICAM RTUs “Standard“)

- WhiteList Filter disabled (=default).
- This profile is typically used for interfacing SICAM RTUs systems within region of same provider.
- All supported type identifications from “Interoperability of SICAM RTUs using IEC60870-5-104 (ETA4)” incl. type
identifications used by SICAM RTUs in private range (remote diagnostics, remote configuration,…)
will be passed through in transmit-/receive direction.
· IEC60870-5-104 Ed.2 (“KEMA conformance tested”)

- WhiteList Filter disabled and data in private range are disabled.
- This profile will be used if interface should be used as conformance tested according IEC60870-5-104 by KEMA.
Note: for this profile
- Only the supported type identifications from interoperability for SICAM RTUs “Protocol Implementation
Conformance Statement (PICS) - Interoperability of SICAM AK, SICAM TM according to IEC 60870-5-104 (ETA4)
as Controlled Station “will be passed through in transmit-/receive direction.
- Type identifications in private range (e.g.: remote diagnostics, remote parameterization,…) will not be supported!
______
*) Profiles requires additional parameter settings on BSE + PRE!

DC0-023-2.12, Edition 06.2017
WhiteList Filter
· The WhiteList Filter is not an interoperability document!
· The WhiteList Filter has the same definition in transmit-/receive direction
· Filtered messages in transmit direction will be discarded without error 1)
(message will be logged as normal in data flow test)

· Filtered messages in receive direction will be confirmed to remote station and discarded
without error *)
(filtered messages cannot be logged in data flow test)
· Special functions for commands:
Command messages with originator address = “0“ will be filtered in case of COT ≠ “6” or
COT ≠ “8”.
For commands sent with COT=ACT/DEACT, the reply for the command in receive
window when this command was sent before wit COT=ACT/DEACT via this
interface/connection.
For commands received with COT=ACT/DEACT, the reply for the command in transmit
window when this command was received before wit COT=ACT/DEACT via this
interface/connection.
The time window is set to 600 seconds and cannot be parameterized.
The WhiteList Filter function stores for up to 200 commands running at the same time the
address for the command, direction (transmit/receive) and the interface/connection
information.
After termination of the command sequence according IEC 60870-5-101/-104 standard
(ACTàACTCONàACTTERM) the stored command information will be deleted.
The stored command information is deleted at a faulty command sequence after expiry of
the time window at the latest.
1) Error will be set for messages with type identifications not supported according WhiteList Filter
definition.
No Error will be set for messages with type identifications supported according WhiteList Filter
definition but with cause of transmission not supported according WhiteList Filter definition.

Edition 06.2017, DC0-023-2.12
8.5.2.5.1 Sample Applications
Following function is the same for different sample applications.
When WhiteList Filter is enabled:
· routing of unwanted message within the system will be stopped

· unwanted messages will not be transmitted
· unwanted messages in receive direction will not be passed through
· ACTCON/ACTTERM for commands will be sent only if this command was received before
via this interface
Partner Interface between SICAM RTUs Systems
Data exchange via interface (LAN, serial) between different partners (utilities) – both partners
are using SICAM RTUs systems.
Partner A Partner B
ETA4 or BPPA0
Messages Messages

DC0-023-2.12, Edition 06.2017
rd
Partner Interface between SICAM RTUs System and 3 Party System
Data exchange via interface (LAN, serial) between different partners (utilities) – one partner
rd
use SICAM RTUs system the other partner uses a 3 party system.
Partner A Partner B
SICAM AK or TM
Third-party system
WhiteList-Filter
ETA4
or
BPPA0
Messages Messages
Internal Segmentation between SICAM RTUs Systems
Data exchange via interface (LAN, serial) between different divisions within the same partner
(utility) – both divisions are using SICAM RTUs systems.
Automation network
Subnet A Subnet B
ETA4 or BPPA0

Edition 06.2017, DC0-023-2.12
rd
Internal Segmentation between SICAM RTUs Systems and 3 Party Systems
Data exchange via interface (LAN, serial) between different divisions within the same
rd
customer – one division uses a SICAM RTUs system the other division uses a 3 party
system.
Automation network
Subnet A Subnet B
SICAM AK or TM
Third-party system
WhiteList-Filter
ETA4
or
BPPA0
Redundant SICAM RTUs Automation Units
The WhiteList Filter is only enabled on the interfaces between the redundant systems. All
other interfaces are not affected.
Control center
Automatision network
with redundant AUs
ETA4 logical ETA4

or connection or
BPPA0 BPPA0
WhiteList-Filter
voter
SICAM AK SICAM AK
or TM or TM
WhiteList WhiteList
Filter (optional) Filter (optional)
ETA4 ETA4
or logical or
BPPA0 connection (optional) BPPA0

DC0-023-2.12, Edition 06.2017
Redundant SICAM RTUs Basic System Elements (BSEs)
· The WhiteList Filter disables possible unwanted routing of system messages or messages
in the private range via possible communication loops in redundancy configuration for
redundant BSE’s.
Note:
A routing of data messages to redundant BSE’s will be suppressed per standard by passive BSE.
· The WhiteList Filter must be parameterized on PREs on both BSE’s.

· The WhiteList Filter is only activated on “passive” BSE and deactivated on “active” BSE.
Control Center
Automation network
ETA4 logical ETA4

or connection or
BPPA0 BPPA0
WhiteList-Filter Redundancy WhiteList-Filter

voter
SICAM AK SICAM AK
or TM or TM

Aktive Passive
BSE BSE
Filter
not Filter
active! active!
System message

Edition 06.2017, DC0-023-2.12
Redundant SICAM RTUs Basic System Elements (BSEs) – Remote Operation
· The WhiteList Filter disables possible unwanted routing of system messages via
communication loops in this redundancy configuration
· The WhiteList Filter must be parameterized on PREs on both BSE’s
· The WhiteList Filter is only activated on “passive” BSE.
· The messages from SICAM TOOLBOX II will be discarded by the activated
WhiteList- Filter on “passive” BSE but passed through on “active” BSE by non active
WhiteList Filter.
Control Center
Automation network
ETA4 logical ETA4

or connection or
BPPA0 BPPA0
SICAM RTUs WhiteList-Filter

voter
SICAM AK
or TM

Aktive Passive
BSE BSE
SICAM Filter
TOOLBOX II not Filter
active! active!
Remote operation

DC0-023-2.12, Edition 06.2017
8.5.2.5.2 Profile Definition: “White-List Filter”
The following table below includes the profile definition for “WhiteList Filter” and “WhiteList Filter for passive PRE”.
Messages with type identification will be pass through in transmit-/receive direction (CASDU “BROADCAST” not allowed)
1) Messages with type identification will be pass through in transmit-/receive direction (CASDU “BROADCAST” allowed)
Special functions for commands
2) Messages with type identification will be pass through in transmit-/receive direction (CASDU “BROADCAST” allowed) – only when “WhiteList Filter for passive PRE” is active
Messages with type identification will not be passed through in transmit-/receive direction (messages filtered out)

0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 20 37 42 44 45 46 47 48
to to to to to
19 36 41 43 63
<0>
<5> Step position information M_ST_NA_1
<7> Bitstring of 32 bit M_BO_NA_1

Edition 06.2017, DC0-023-2.12

0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 20 37 42 44 45 46 47 48
to to to to to
19 36 41 43 63
<22-29>
<31> Double-point information with time tag CP56Time2a M_DP_TB_1
<32> Step position information with time tag CP56Time2a M_ST_TB_1
<33> Bitstring of 32 bit with time tag CP56Time2a M_BO_TB_1
<35> Measured value, scaled value with time tag CP56Time2a M_ME_TE_1
<37> Integrated totals with time tag CP56Time2a M_IT_TB_1
time tag CP56Time2a
time tag CP56Time2a
<41-44>
<45> Single command C_SC_NA_1 * * *
<46> Double command C_DC_NA_1 * * *
<47> Regulating step command C_RC_NA_1 * * *
<48> Set point command, normalized value C_SE_NA_1 * * *
<49> Set point command, scaled value C_SE_NB_1 * * *
<50> Set point command, short floating point C_SE_NC_1 * * *
<51> Bitstring of 32 bit C_BO_NA_1 * * *
<52-55>
<58> Single command with time tag CP56Time2a C_SC_TC_1 * * *
<59> Double command with time tag CP56Time2a C_DC_TC_1 * * *
<60> Regulating step command with time tag CP56Time2a C_RC_TC_1 * * *
<61> Set point command, normalized value with time tag CP56Time2a C_SE_TA_1 * * *
<62> Set point command, scaled value with time tag CP56Time2a C_SE_TB_1 * * *
<63> Set point command, short floating point with time tag CP56Time2a C_SE_TC_1 * * *
<64> Bitstring of 32 bit with time tag CP56Time2a C_BO_TA_1 * * *
<65-69>
<70> End of initialization M_EI_NA_1
<71-99>
<100> Interrogation command C_IC_NA_1 1)
<101> Counter interrogation command C_CI_NA_1


DC0-023-2.12, Edition 06.2017

0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 20 37 42 44 45 46 47 48
to to to to to
19 36 41 43 63

<105> Reset process command C_RP_NA_1
<108,109>
<110> Parameter of measured value, normalized value P_ME_NA_1

<111> Parameter of measured value, scaled value P_ME_NB_1
<112> Parameter of measured value, short floating point value P_ME_NC_1
<114-119>
<120> File ready F_FR_NA_1

<121> Section ready F_SR_NA_1
<122> Call directory, select file, call file, call section F_SC_NA_1 1)
<123> Last section, last segment F_LS_NA_1

<124> Ack file, ack section F_AF_NA_1
<125> Segment F_SG_NA_1
<126> Directory {blank or X, only available in monitor (standard) direction} F_DR_TA_1*
<127>
<128-134>
<135> SICAM RTUs systemdata container (TI:=135, FC=148, IC=04) 2) 2) 2) 2) 2) 2) 2) 2) 2) 2) 2) 2) 2) 2) 2) 2) 2) 2) 2) 2) 2) 2) 2)

<136-141>
<136-255>

Edition 06.2017, DC0-023-2.12
Semantics of cause of transmission:

<0> := not used
<1> := periodic, cyclic
<2> := background scan
<3> := spontaneous
<4> := initialized
<5> := request or requested
<6> := activation
<7> := activation confirmation
<8> := deactivation
<9> := deactivation confirmation
<10> := activation termination
<11> := return information caused by a remote command
<12> := return information caused by a local command
<13> := file transfer
<14..19> := reserved for further compatible definitions (not used)
<20> := interrogated by station interrogation
<21..36> := interrogated by group 1..16 interrogation
<37> := requested by general counter request
<38..41> := requested by group 1..4 counter request
<42, 43> := reserved for further compatible definitions (not used)
<44> := unknown type identification
<45> := unknown cause of transmission
<46> := unknown common address of ASDU
<47> := unknown information object address
<48, 63> := for special use (private range - not used)

DC0-023-2.12, Edition 06.2017
8.5.2.5.3 Profile Definition: “SICAM RTUs – IEC104”
The profile SICAM RTUs – IEC104 (“SICAM RTUs Standard“) defines functionality according interoperability for SICAM RTUs according IEC60870-5-104 (ETA4).
This profile will be used as standard for interfacing SICAM RTUs components.
… more details see document “SICAM RTUs Interoperability IEC 60870-5-101/104 chapter 4 “Architecture and Data Flow“


0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 20 37 42 44 45 46 47 48
to to to to to
19 36 41 43 63
<0>
<5> Step position information M_ST_NA_1 B B* B* B* B*

<7> Bitstring of 32 bit M_BO_NA_1 B B* B*

<20> Packed single-point information with status change detection M_PS_NA_1 6) 6)

<22-29>

Edition 06.2017, DC0-023-2.12

0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 20 37 42 44 45 46 47 48
to to to to to
19 36 41 43 63

time tag CP56Time2a
B
time tag CP56Time2a
<41-44>
<48> Set point command, normalized value C_SE_NA_1 B B B B B* B B B B
<49> Set point command, scaled value C_SE_NB_1 B B B B B* B B B B
<50> Set point command, short floating point C_SE_NC_1 B B B B B* B B B B
<51> Bitstring of 32 bit C_BO_NA_1 B* B* B* B* B* B B B B
<52-55>
<58> Single command with time tag CP56Time2a C_SC_TC_1 B B B B B B B B B
<59> Double command with time tag CP56Time2a C_DC_TC_1 B B B B B B B B B
<60> Regulating step command with time tag CP56Time2a C_RC_TC_1 B B B B B B B B B
<61> Set point command, normalized value with time tag CP56Time2a C_SE_TA_1 B B B B B* B B B B
<62> Set point command, scaled value with time tag CP56Time2a C_SE_TB_1 B B B B B* B B B B
<63> Set point command, short floating point with time tag CP56Time2a C_SE_TC_1 B B B B B* B B B B
<64> Bitstring of 32 bit with time tag CP56Time2a C_BO_TA_1 B* B* B* B* B* B B B B
<65-69>
<71-99>
7) 7)
<101> Counter interrogation command C_CI_NA_1 B B B B B B B

<103> Clock synchronization command C_CS_NA_1 X X B B B B

DC0-023-2.12, Edition 06.2017

0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 20 37 42 44 45 46 47 48
to to to to to
19 36 41 43 63
<105> Reset process command C_RP_NA_1 X+ X+ B X X X

<107> Test command with time tag CP56time2a C_TS_TA_1 B B B B B B
<108,109>
<110> Parameter of measured value, normalized value P_ME_NA_1 X X X B B B B
<111> Parameter of measured value, scaled value P_ME_NB_1 X X X B B B B
<112> Parameter of measured value, short floating point value P_ME_NC_1 X X X B B B B

<114-119>
<120> File ready F_FR_NA_1 B B 5) 5) 5)
<121> Section ready F_SR_NA_1 B B 5) 5) 5)
<122> Call directory, select file, call file, call section F_SC_NA_1 B B B 5) 5) 5)
<123> Last section, last segment F_LS_NA_1 B B 5) 5) 5)
<124> Ack file, ack section F_AF_NA_1 B B 5) 5) 5)
<125> Segment F_SG_NA_1 B B 5) 5) 5)

<127>
<128-134>
<135> SICAM RTUs systemdata container (TI:=135, FC=148, IC=04) B B B B B B B B B B B B B B B B B B B B B B B

<136-141>
<142> SICAM RTUs user data container (TI:=142, message type = 128) B B B B B B B B B B B B B B B B B B B B B B B
<143-255>
*) blank or “X“ only
+ secondary application function only
B* can be generated by PLC
5) transparent transmission by system
6) Reception possible, thereby the blocked single-point information is deblocked and further individually processed as TI = 30 (address translation occurs algorithmic)
7) Not supported; reply sent with COT=45 „unknown cause of transmission“

Edition 06.2017, DC0-023-2.12
8.5.2.5.4 Profile Definition: “IEC60870-5-104 Ed.2”
The profile IEC60870-5-104 Ed.2 (“KEMA Conformance tested“) defines IEC60870-5-104 Ed. 2 functionality as conformance tested by KEMA.
This profile is used at interfaces required functionality as conformance tested according IEC60870-5-104 Ed. 2 by KEMA.
… more details see document “Protocol Implementation Conformance Statement (PICS) - Interoperability of SICAM AK, SICAM TM according to IEC 60870-5-104 (ETA4) as Controlled Station“


0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 20 37 42 44 45 46 47 48
to to to to to
19 36 41 43 63
<0>
<5> Step position information M_ST_NA_1 X B* B* B* B*

<7> Bitstring of 32 bit M_BO_NA_1 X B* B*

<22-29>

DC0-023-2.12, Edition 06.2017

0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 20 37 42 44 45 46 47 48
to to to to to
19 36 41 43 63

time tag CP56Time2a
B
time tag CP56Time2a
<41-44>
<48> Set point command, normalized value C_SE_NA_1 B B B B B B B B B
<49> Set point command, scaled value C_SE_NB_1 B B B B B B B B B
<50> Set point command, short floating point C_SE_NC_1 B B B B B B B B B
<51> Bitstring of 32 bit C_BO_NA_1

<52-55>
<58> Single command with time tag CP56Time2a C_SC_TC_1 B B B B B B B B B
<59> Double command with time tag CP56Time2a C_DC_TC_1 B B B B B B B B B
<60> Regulating step command with time tag CP56Time2a C_RC_TC_1 B B B B B B B B B
<61> Set point command, normalized value with time tag CP56Time2a C_SE_TA_1 B B B B B B B B B
<62> Set point command, scaled value with time tag CP56Time2a C_SE_TB_1 B B B B B B B B B
<63> Set point command, short floating point with time tag CP56Time2a C_SE_TC_1 B B B B B B B B B
<64> Bitstring of 32 bit with time tag CP56Time2a C_BO_TA_1

<65-69>
<71-99>
<101> Counter interrogation command C_CI_NA_1 X X X X X X X


Edition 06.2017, DC0-023-2.12

0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 20 37 42 44 45 46 47 48
to to to to to
19 36 41 43 63
<105> Reset process command C_RP_NA_1 X+ X+ X X X X

<107> Test command with time tag CP56time2a C_TS_TA_1 B B B B B B
<108,109>
<110> Parameter of measured value, normalized value P_ME_NA_1 X X X X
<111> Parameter of measured value, scaled value P_ME_NB_1 X X X X
<112> Parameter of measured value, short floating point value P_ME_NC_1 X X X X

<114-119>
<120> File ready F_FR_NA_1 X X 1) 1) 1)
<121> Section ready F_SR_NA_1 X X 1) 1) 1)
<122> Call directory, select file, call file, call section F_SC_NA_1 X X X 1) 1) 1)
<123> Last section, last segment F_LS_NA_1 X X 1) 1) 1)
<124> Ack file, ack section F_AF_NA_1 X X 1) 1) 1)
<125> Segment F_SG_NA_1 X X 1) 1) 1)

<127>
<128-134>
<135> SICAM RTUs systemdata container (TI:=135, FC=148, IC=04)

<136-141>
<143-255>
*) blank or “X“ only
+ secondary application function only
X* can be generated by PLC
1) transparent transmission by system

DC0-023-2.12, Edition 06.2017
8.5.2.6 Data Throughput Limitation
The protocol element for IEC60870-5-104 in SICAM RTUs supports a limitation of data
throughput in transmit-/receive direction for IEC60870-5-104 data messages.
The data throughput limitation is used for the limitation of the data throughput from/to partner
or division interface.
Data Throughput Limitation:
· connection specific parameters

· separate parameters for number of messages/second in transmit-/receive direction
· a message is a selective or blocked IEC60870-5-104 message (APDU)
· no delay in communication if data throughput is below limit
· data throughput limitation in receive direction in case of exceeded limit by delay of
acknowledge message according IEC60870-5-104
· data throughput limitation in transmit direction in case of exceeded limit by delay of
transmission of IEC60870-5-104 data messages
Note:
The data throughput limitation works properly only if the IEC60870-5-104 parameters are set
to the same values on both sides.
Data Throughput Limitation in Transmit Direction
The number of messages/second in transmit direction can be parameterized per connection

with the system technical parameters of the connection definition for every connection
in the field Data throughput limit in transmit direction (msg/s). (0 = no data
throughput limitation).
If the number of messages/second for a single connection exceeds the parameterized limit
then the data transmission is stopped for this connection until next second.
A communication error “data throughput in transmit direction” is set if the data throughput has
reached permanently 90% of the parameterized limit within the last 10 minute window.

Edition 06.2017, DC0-023-2.12
Data Throughput Limitation in Receive Direction
The number of messages/second in receive direction can be parameterized per connection

with the system technical parameters of the connection definition in the field Data
throughput limit in receive direction (msg/s). (0 = no data throughput limitation).
If the number of messages/second for a single connection reaches the parameterized limit,
the transmission of the confirmation for the received message will be delayed in a way that
limit the number of received messages in middle at the parameterized limit.
If the delay would cause in exceeding timeout t2 (e.g.: “k” parameter in the remote system is
set to a very high value in relation to parameterized limit) the data throughput limitation will be
stopped to avoid connection failure caused by delayed IEC60870-5-104 confirmation.
Restriction:
In worst case the number of messages /second in receive direction can be higher by “k” of the
remote system (k=max. number of not confirmed messages = IEC60870-5-104 parameter).
If the number of messages/second for a single connection exceeds the parameterized limit
within a time slot (1 second) then the number of messages/second for the next time slot(s) will
be reduced by the exceeded number of messages.
A communication error “data throughput in receive direction” is set if the data throughput has
reached permanently 90% of the parameterized limit within the last 10 minute window.

DC0-023-2.12, Edition 06.2017
8.5.2.7 Settings for Project DBAG
For the implementation of the protocol firmware in DBAG projects the following special
· Breaker delay in transmit direction (DBAG-specific special message format <TI=150>)

· Send originator address with settable value
project specific settings | DBAG functions.
With function activated, messages in the format <TI=33> "32 Bit bit pattern" in the direction
basic system element ð protocol element are converted by the protocol element to the
DBAG-specific message format <TI=150> and transmitted.
Messages received in the format <TI=150> are converted by the protocol element to the
format <TI=33> "32 Bit bit pattern" and passed on to the basic system element.
In transmit direction <TI=33> "32 Bit bit pattern" is converted as follows:
Cause of IEC-Parameter Type Identification for Transmission to the Remote

Transmission Station
spontaneous - <TI=150> DBAG-specific format
CP56Time2a
GI without time <TI=3> double-point information
In receive direction <TI=150> is converted as follows:
Cause of Time Format Type Identification for Transmission to Basic

Transmission System Element
spontaneous, GI with time (7 octets) <TI=33> Bit pattern of 32 Bit with time tag CP56Time2a
Note:
The format <TI=150> is only defined with 7 bytes time, 3 bytes IOA, 2 bytes CASDU and 2
bytes URS! For this format no double transmission is defined as format without time tag!

Edition 06.2017, DC0-023-2.12
Breaker delay in transmit direction

If the delay of the circuit breaker or the time of the fault current is not available, this time can
be added by the protocol element in messages in transmit direction with the parameter
advanced parameters | project specific settings | DBAG functions | switch
transfer time in transmit direction.
Message structure <TI=150> "Railway-specific Format" (in the private range)
27 26 25 24 23 22 21 20
SQ Number of information objects variable structure qualifier
T P/N cause of transmission Cause of transmission
Originator address
Station address CASDU1
N CASDU2
Technological Code (TC) IOA1
1 IOA2
0 Field address IOA3
SK8 SK7 SK6 SK5 SK4 SK3 SK2 SK1 Protection criteria (BDK)
Protection criteria reserve
0 - 255 Fault code (AK of SLT)
2ms – Code (0-255) Breaker delay
IV NT SB BL DPI DIQ of DOM
Originator time in format CP56Time2a
(corresponds to TL SCHINA, DB_Network) Dual time (7 octets)
Send originator address with settable value

In DBAG projects the originator address in transmit direction is always transferred with a fixed
parameterized value. The originator address is to be set with the parameter advanced
parameters | project specific settings | DBAG functions | originator
address in transmit direction.
For this function the setting of the number of octets for cause of transmission to "2 octets" is
necessary (see IEC 60870-5-101/104 Parameters on the Basic System Element).

DC0-023-2.12, Edition 06.2017
8.5.2.8 Settings for Project RWE
For the implementation of the protocol firmware in RWE projects the following special
· Bit by bit marking of the field

· Cyclic measured values
· Address of the return information for selection command 2
· NT-Bit, IV-Bit according to RWE requirements
project specific settings | RWE functions and are effective for all connections of
the LAN/WAN protocol element.
8.5.2.8.1 Bit by Bit Marking of the Field
For RWE switchgear projects, the configuration of the plants is divided into "voltage level",
"station number" and "field".
This structuring is represented on the 5-stage IEC 60870-5-101/104 address of the data.
The definition of which part of the address (CASDU, IOA) the field addresses is carried out in
the parameters advanced parameters | project specific settings | RWE
functions | bit-level flag of bay | *.
All set bits in the "Bit by bit marking of the field" define the range of the address of the field. All
reset bits in the mask define the range of the addresses for data points within the fields.
The assignment of the measured values to the fields is determined by the structuring of the
address.
For cyclic group 0 measured values, no field-specific functions are implemented on the
LAN/WAN protocol element.
The transmission of cyclic group 2 measured values is activated by field-specific selection

commands. On the LAN/WAN protocol element the cyclic measured values are not
activated/deactivated by the selection command itself, rather indirectly by the return
information for the selection command.

Edition 06.2017, DC0-023-2.12
With the return information for selection command 2, those cyclic group 2 measured values
whose address for the field after masking matches the mask for "Bit by bit marking of the field“
are activated/deactivated for transmission.
Bit by Bit marking of the Address Range for Fields

Field "Mask"
[HEX] BIN Dec [HEX]
CASDU1 FF 11111111 0-255 [00-FF]
CASDU2 FF 11111111 0-255 [00-FF]
IOA1 00 00000000 --
IOA2 00 00000000 --
IOA3 FC 11111100 252-255 [FC-FF]
Notes:
- all bits with "1" in the mask declare the address range of the field
- all bits with "0" in the mask declare the address range of the data points within the field
- the bit by bit marking of the field is always the same for RWE projects!
Example:
Parameterized
Return Bit by Bit marking Addresses of the Return Information
Information of the Field "Mask" determined by this
Address
[HEX] [BIN] [HEX] BIN Dec [HEX]
CASDU1 00 00000000 FF 11111111 0-255 [00-FF]
CASDU2 00 00000000 FF 11111111 0-255 [00-FF]
IOA1 21 00100001 00 00000000 21
IOA2 56 01010110 00 00000000 56
IOA3 03 00000011 FC 11111100 3,7,11,15,19,…,255 [03,07,0F,13,…,FF]
8.5.2.8.2 Cyclic Measured Values
Measured values can be transmitted cyclic to the remote station from the internal process
image by the protocol element itself. For this special function, the activation of the "RWE-
specific functions" and the use of the selective data flow in SICAM RTUs is required.
For cyclic measured values the following groups are supported:
· Group 0: cyclic measured values with a parameter-settable cycle time

(default cycle time)
· Group 2: cyclic measured values – are only transmitted for selection 2
(high priority cycle time)
Group 2 measured values (PSG measured values) are first transmitted cyclic after activation
with the selection command 2.

DC0-023-2.12, Edition 06.2017
The selection of the measured values for the cyclic transmission and the assignment of the
measured values to the group is carried out in the process-technical parameter setting for the
selective data flow in SICAM RTUs in the field "Function group".
Function Group Group Note

0-249 --- No cyclic measured value! (measured value is transmitted
spontaneous)
250 0 Cyclic measured value with a parameter-settable cycle time
(default cycle time; typically 3 sec)
251 1 Cyclic measured value – is only transmitted for activation with
selection command 1;
not used with LAN/WAN protocol element!
252 2 Cyclic measured value – is only transmitted for activation with
selection command 2 (high priority cycle time; typically 0.5 sec)
Note:
The functional groups required for cyclic measured values must not be used for other functions!
The updating of the process image for cyclic measured values takes place during the
transmission of spontaneous measured values or during general interrogation to the
LAN/WAN protocol element – from now on these measured values are transmitted cyclic (not
spontaneous and not with GI) to the remote station.
For the transmission of the cyclic measured values, SICAM RTUs internal (between basic
system element and LAN/WAN protocol element) the message format "<TI:=35> measured
value, scaled value with time tag CP56Time2a" is used.
Cyclic measured values are always transmitted from the LAN/WAN protocol element to the
remote station without time tag with the message format "<TI:=11> measured value, scaled
value" and with the cause of transmission "cyclic".
The cycle time for the transmission of cyclic measured values can be set with the parameter
advanced parameters | project specific settings | RWE functions | cyclic
measured value | base cycle time and the parameter advanced parameters |
project specific settings | RWE functions | cyclic measured value | high
priority cycle time.
The transmission of the cyclic measured values to the remote station takes place with
maximum possible blocking according to IEC 60870-5-104. The blocking for cyclic measured
values is performed by the LAN/WAN communications element itself. The parameters
provided for the blocking on the basic system element (BSE) in the IEC 60870-5-101/104
parameter block are not evaluated.
During the transmission of the cyclic measured values, the transmission of spontaneous data
is disabled. All cyclic measured values are prepared for transmission in one operation at the
respective cycle moment.
Limitations:
· max. 2000 cyclic measured values

· Cyclic measured values are only supported in SICAM RTUs with selective data flow
· An address conversion for cyclic measured values is not supported
· Cyclic measured values are only supported for 1 connection
(only to the 1st connection in the detailed routing)
· Cyclic measured values must not be routed to a redundant connection

Edition 06.2017, DC0-023-2.12
Note:
So that the process data is transmitted with the latest values as fast as possible after a going
interface fault, the function "delete ring with communication failure" is to be deactivated in the
communications function on the basic system element. This setting is therefore necessary,
because the general interrogation in the system is only triggered later and consequently, until
the updating of the cyclic measured values, due to the general interrogation, old values are
transmitted to the remote station.
Group 0 measured values
With function enabled, group 0 measured values are always transmitted cyclic.
The cycle time can be set with the parameter advanced parameters | project
specific settings | RWE functions | cyclic measured value | base cycle
time.
Group 1 measured values (selection command 1)

Group 1 measured values are not supported!
Group 2 measured values (selection command 2)

Group 2 measured values (PSG measured values) are first transmitted cyclic after activation
with the selection command 2. If the transmission of the measured values is not activated with
the selection command 2, these measured values are not transmitted.
After startup, by default these measured values are not transmitted.
The activation of the group 2 measured values takes place on the LAN/WAN protocol element
not directly with the selection command 2, rather with the return information for the selection
command 2.
The cycle time can be set with the parameter advanced parameters | project
specific settings | RWE functions | cyclic measured value | high priority
cycle time.
8.5.2.8.3 Address of the Return Information for Selection Command
The activation of the group 2 measured values does not take place on the LAN/WAN protocol
element with the selection command 2 itself, rather with the return information for the selection
command 2. The selection command is processed in the function diagram of the component
according to the RWE requirements and with successful selection the return information is
generated for the selection command 2.
The selection of the group 2 measured values is supported for all fields, whose address range
has been determined by the "Bit by bit marking of the field".
The address of the return information for the selection command 2 is to be parameterized with
the parameters advanced parameters | project specific settings | RWE
functions | cyclic measured value | address of the return information of
select command 2 | *.
As return information address, only those sections of the address are to be parameterized that
are not part of the address range for the field. Consequently, as return information address
only the field-internal address is to be parameterized. The bits of the address which identify
the field in the return information address for selection command 2 are not evaluated by the
LAN/WAN protocol element.
For the return information of the selection command 2, SICAM RTUs internal only the
message format "<TI:=30> single-point information with time tag CP56Time2a" is used. The
cyclic transmission of the group 2 measured values is activated with the single-point
information state "ON" and deactivated with the state "OFF".

DC0-023-2.12, Edition 06.2017
The selection of the group 2 measured values can be carried out either "Locally" or
"Remotely". The return information for the selection command 2 is only transmitted
spontaneously to the remote station with the cause of transmission "Return information,
caused by a remote command" or "Return information, caused by a local command".
With general interrogation, the return information for the selection command is not transmitted
to the remote station!
The assignment of the measured values to the fields is determined by the structuring of the
address for RWE.
With the return information for selection command 2, those cyclic group 2 measured values
whose address for the field after masking matches the mask for "Bit by bit marking of the field“
are activated/deactivated for transmission.
8.5.2.8.4 NT-Bit, IV-Bit according to RWE Requirements
For projects for the customer RWE, a special handling can be activated for the NT-bit and the
IV-bit of the quality descriptor of the messages in transmit direction.
If the RWE-specific functions are not activated, the NT-bit and the IV-bit in the messages are
transferred to the remote station unchanged.
If the RWE-specific functions are activated, the special handling for the NT-bit and the IV-bit
can be selected with the parameter advanced parameters | project specific
settings | RWE functions | convert of the NT bits to the IV bit in
transmit direction from the following options:
· Variant a: (selection = <disabled>)

NT-bit is set to "0", IV-bit is not changed
· Variant b: (selection = <enabled>)
NT-bit is set to "0", IV-bit is set if NT-bit (internal) or IV-bit (internal) is set
SICAM RTUs internal To Remote Station (Variant a) To Remote Station (Variant b)

NT-Bit IV-Bit NT-Bit IV-Bit NT-Bit IV-Bit
0 x 0 x 0 x
1 x 0 x 0 1
0 0 0 0 0 0
0 1 0 1 0 1
1 0 0 0 0 1
1 1 0 1 0 1
x = optional state, or state is not changed!

Edition 06.2017, DC0-023-2.12


· Applicational control of ENABLE/DISABLE Ethernet interface

· Information about the state of data transfer
Block Diagram
Protocol element
control
Internal
Transmission route
function
Protocol element


DC0-023-2.12, Edition 06.2017
system element enables specific functions of the protocol elements to be controlled. The
specific functions are determined by the protocol element implemented.
message.
message (FC=161, IC=0), an unused CASDU is to be used! All CASDU´s for process
information are distributed automatically to the corresponding remote terminal unit.
Possible client functions

SF Station Z-Par Fl
ENABLE Ethernet interface =
"reconnect Ethernet connection" (setup
of link connection)
Interface "Enable" 0 - - · Ethernet-Controller Chip will be
enabled
· Services enabled (IEC 60870-5-104,
WEB, NTP, remote operation)
DISABLE Ethernet interface
= "disconnect Ethernet connection"(link
will be released)
· Ethernet Controller Chip will be
disabled
Interface "Disable" 1 - - · No services possible (IEC 60870-5-
104, WEB, NTP, remote operation)
· Warning: "interface DISABLED"
(diagnostic message)
· All connections will be released after
104 timeouts
Time sync. “OK” 2 - -
With failure of the time synchronization
for the local AU, also in AK1703 the
Time sync. “NOK” 3 - - special function “Time mark (IV=1) with
messages in send direction” can be
used
This function is processed on the BSE
and sent to the protocol element as
Send (general)
240 - - system message and not using PRE-
interrogation command
control message!
CASDU = BROADCAST
Send (general) This function is processed on the BSE
interrogation command and not sent to the protocol element as
for GI-group to own BSE 241 - - PRE-control message!
(=simulate received general
interrogation command for GI
group) 1)

Edition 06.2017, DC0-023-2.12

SF Station Z-Par Fl
65535
(all stations)
125
SCS=<OFF>: reset control location
65535
(HKA) (all stations)
65535
(selective station)
0…99
65535
(HKA) (selective station)
Send (general)
244 CASDU system message and not using PRE-
control message!
CASDU = selective
Remote operation Remote Operation:
3)
245 - - Remote connection with TOOLBOX II.
“Disable“
TOOLBOX II is directly connected to device via
Remote operation remote connection using http/https.
3) 246 - - Remote maintenance via “service messages“.
“Enable“
3) only supported in SICAM RTUs (ACP 1703)!
- Set control location function requires “additional parameter_(PRE)” (=Z-Par) = 65535 in BSE’s
PST-detail routing.
- If a PRE-control message for "set control location" is included in the PST-detailed routing on the
BSE, the BSE will send a PRE-control message "Set control location" with
additional parameter = 65535 after startup of the PRE to enable control location function on
PRE.
- The control location (HKA) to be enabled/disabled is taken by the BSE firmware from the
originator of the command message used as PST control message and sent to PRE as
PRE control message with additional parameter set as follows:

Legend:
SF ........... Control function_(PRE)

Station .... Station number
0 - 99 = station 0…99 of the selected protocol element
125 = all stations of the selected protocol element (=GLOBAL)
Z-Par ...... Additional parameter_(PRE)
Fl ............ Edge
SCS ........ single command state
HKA ........ Originator address (HKA) = 0 - 255

DC0-023-2.12, Edition 06.2017
There are 2 different categories of return information:

(PRE return information "Station Status" FC=161, IC=12)
(PRE return information "General" FC=161, IC=11)
Possible LAN return information
Return information Parameter Note

function_(PRE)
Station
0 = Station OK
Station failure 0…99
1 = Station NOK (failed)
0 = remote operation disabled
remote operation -
1 = remote operation enabled
Status DATA TRANSFER (BSE) 1)
protocol-specific return
0…99 0 = data transfer from/to BSE is stopped
information 0
1 = data transfer from/to BSE is started
Status DATA TRANSFER (104-Connection) 2)
0 = IEC 60870-5-104 data transfer is stopped
protocol-specific return
0…99 (STOPDTact)
information 1
1 = IEC 60870-5-104 data transfer is started
(STARTDTact)
1) the state of the "DATA TRANSFER (BSE)" can be changed by the parameter "Stop behavior" and
"Failure" (see connection specific parameters) and und can be different to the state of "DATA
TRANSFER (104 Connection)"
2) actual state of "DATA TRANSFER (104 Connection)"
Legend:
Station ....Station number

0…99 station of the selected protocol element
125 station number not used!

Edition 06.2017, DC0-023-2.12
8.7 Security Logging
SICAM RTUs provides a security logbook which acquires security-relevant events and
transmits it by means of syslog client to an external syslog server.
More Details see “SICAM RTUs Administrator Manual”.

DC0-023-2.12, Edition 06.2017
8.8 Web Server
A web server is integrated into the protocol firmware for internal diagnostic information.
This information can be read out comfortably with a common WEB Browser (e.g. Microsoft
Internet Explorer). For the access to the web server the communications protocol "HTTP
(Hyper Text Transfer Protocol)" is used with the port number 80.
The integrated web server is addressed by means of direct specification of the IP address of
the Ethernet interface of the automation unit.
By default the web server is deactivated for security reasons. Also for security reasons, an
authentication can be configured for the access to the web server (specification of a
password).
· HTTP web server

The integrated web server can if necessary be enabled for access by the user with the
parameter HTTP web server | HTTP web server.
· Password for authentication
With authentication enabled a password can be established with the parameter HTTP web
server | password for authentication. The access to the integrated web server is
only possible after successful authentication.
Note
The values displayed on the web pages indicate the current status when the web page is started. The
values of a web page are not updated automatically!
An updating of the web page displayed in the web browser can be performed e.g. by means of the web
browser function “Refresh”.

Edition 06.2017, DC0-023-2.12
Via the integrated web server the following information can be read out:
· Diagnosis
- Ethernet
Display of the network information
(MAC address, speed, duplex mode, statistics)
- TCP/IP
own network parameters (Own IP address, default gateway, Subnet Mask)
number of server connections
- Firmware (actual firmware time)
- Data Link Errors
- Ping (initiate PING directly from Protocol Element)
- System information (Hardware, Software)
· Developer Info (internal information for software developer)
- Taskstack
- Heap
- Read Memory
- Read Register (Ethernet Controller Configuration)
- Read EEPROM
· Switch (DNIP only)

DC0-023-2.12, Edition 06.2017
Parameters for the web server:
· Authentication
For security reasons, for the access to the integrated web server a compulsory
authentication can be requested. The authentication is activated with the parameter HTTP
web server | user name for authentication. With function enabled, access is
only possible with entry of the established password.
· Password for Authentication
With authentication enabled a password can be established with the parameter HTTP web
server | password for authentication. The access to the integrated web server is
only possible after successful authentication.
· Username for Authentication
The Username for the authentication can be defined with the parameter HTTP web
server | user name for authentication.
Note: In the current protocol firmware the username is longer used for the authentication!
· Warning Web browser logged on
For logging in the system a warning can be generated with logged on user. The generation
of this warning can be activated with the parameter HTTP web server | warning
webbrowser logged on.

Edition 06.2017, DC0-023-2.12
9 LAN Communication (61850)
Contents
9.1 Introduction .................................................................................................. 412

9.2 LAN Communication over Ethernet TCP/IP according to IEC 61850 ............. 420
9.4 Dual-LAN interface (DNIP)............................................................................ 480
9.7 Web Server .................................................................................................. 545

DC0-023-2.12, Edition 06.2017
9.1 Introduction
IEC 61850 is a general, network-based transmission protocol for the protection and control in
electrical switchgear of the medium and high-voltage technique (station automation). The
standard series mainly defines:
· General definitions for switchgear

· The most important information for functions and devices,
· The exchange of information for protection, monitoring, control and measurement
· A digital interface for primary data
· A configuration language
The protocol uses TCP/IP as basic transmission protocol and the MMS protocol
(Manufacturing Messaging Specification) as classic Client-Server communication (defined in
the standard part IEC 61850-8-1). In addition, two so-called Peer-to-Peer services are
described for the real time capable communication, which sit directly on the Ethernet protocol:
· Transmission of fast scanned values according to standard part IEC 61850-9-1

(is presently not supported by the protocol element Server + Client!)
· Transmission of GOOSE messages according to standard part IEC 61850-8-1
The 61850 Client actively establishes the connection and fetches data from a 61850 Server or
sends data to a 61850 Server. The 61850 Server waits passively for a connection established
by a 61850 Client and is data source and data recipient.
In contrast to IEC 60870-5-104, which is based on a signal-orientated data model, the data
model of the IEC 61850 interface is strictly object-orientated. The name of the object in plain
text serves as identification. The objects are self-descriptive, i.e. the structure of the objects is
transmitted with the object itself in the message.
In contrast to IEC 60870-5-104, IEC 61850 is only defined for the station bus within the switch
gear and not for the process data transmission between the stations and the power control
system. For the interfacing of the power network control centre, the data must be mapped to
e.g. IEC 60870-5-101/104.
Master station-1 Master station-2 Master station-n

LAN-Interface LAN-Interface LAN-Interface
Switch Switch
Station bus Ethernet TCP/IP with IEC61850
Station bus Ethernet TCP/IP with IEC61850 Station bus Ethernet TCP/IP with IEC61850
Switch Switch Switch Switch
LAN-Interface LAN-Interface LAN-Interface LAN-Interface LAN-Interface
Remote station Remote station Remote station Remote station Remote station
(IED) #1 (IED) #2 (IED) #3 (IED) #4 (IED) #n
max. 100 connections per LAN-Interface

Edition 06.2017, DC0-023-2.12
One major peculiarity of the IEC 61850 protocol is the decoupling of the object-orientated
technological representation of the data from the communication.
The 61850 defines the appearance of the functions based on the data to outside. The
functions are indeed described but not defined.
For each connection, the SICAM RTUs protocol element supports either 61850-Server
function or 61850-Client function.
ET03 SICAM AK IEC 61850 Edition 1 Client + Server + Goose

ETA3 SICAM BC
SICAM TM
ET83 CP-8000 IEC 61850 Edition 1 Client + Server + Goose

CP-802x
ETA5 SICAM AK 3 IEC 61850 Edition 1+2 Client

SICAM AK IEC 61850 Edition 2 Server + Goose
SICAM TM
ET25 IEC 61850 Edition 1+2 Client

SICAM AK 3
IEC 61850 Edition 2 Server + Goose
ET85 CP-8000 IEC 61850 Edition 1+2 Client

CP-802x IEC 61850 Edition 2 Server + Goose
Note
ETx5 Client is supported by SICAM TOOLBOX II as of version 5.11.
ETx5 Server is supported by SICAM TOOLBOX II as of version 6.0.

DC0-023-2.12, Edition 06.2017
ETA3
ETA5
ET03
ET83
ET25
ET85
General Functions IEC 61850 Client

− 10/100 MBit (half duplex/full duplex) ü
− 10 Mbit/s (full duplex, auto negotiation) IEC61850 should be used ü 1) ü 1)
with 100 Mbit/s only!
− 100 Mbit/s (full duplex, auto negotiation) ü ü 1) ü ü 1) ü 1)
− Auto-MDIX (Auto Medium Dependent Interface Crossover) ü 1) ü 1) ü 1)
− Parameters for TCP/IP optimization
· IEC 61850 Client

− Edition 1 ü ü ü ü ü ü
− Edition 2 ü ü ü
− Max. number of servers (max. connections) 100 2) 100 2) 10 100 2) 100 2) 20
− Max. number of "Logical Devices" (for each connection) 100 100 100 3) 3) 3)
− Max. number of "Logical Nodes" (for each connection) 3) 3) 3) 3) 3) 3)
− Max. number of data points 5000 4) 5000 4) 500 10000 10000 1000
− Startup time PRE 5) 5) 5)
− Initialization time (after startup time PRE) 6) 6) 6)
− ACSI services ü 7) ü 7) ü 7) ü 7) ü 7) ü 7)
− Common Data Classes ü 7) ü 7) ü 7) ü 7) ü 7) ü 7)
− Attributes ü 7) ü 7) ü 7) ü 7) ü 7) ü 7)
− Supported functionality according to:
- PICS (Protocol Implementation Conformance Statement) ü ü ü ü ü ü
- PIXIT (Protocol Implementation Extra Information) ü ü ü ü ü ü
- Supported Logical Nodes and their Attributes ü ü ü ü ü ü
· Supported Ports
− Port 102: MMS (Manufacturing Message Specification) ü ü ü ü ü ü
− Port 80: HTTP (Hypertext Transfer Protocol) - “Web Server“ ü ü ü 1) ü ü 1) ü 1)
− Port 80: HTTP (Hypertext Transfer Protocol) - “Remote operation for ü ü 1) ü ü 1) ü 1)
SICAM TOOLBOX II“
− Port 443: HTTPS (Hypertext Transfer Protocol over SSL/TLS) - “Web ü ü 1) ü ü 1) ü 1)
Server“
− Port 443: HTTPS (Hypertext Transfer Protocol over SSL/TLS) - ü ü 1) ü ü 1) ü 1)
− Port 123: NTP V3 (Network Time Protocol) ü ü ü 1) ü ü 1) ü 1)
− Port 123: SNTP V3/V4 (Simple Network Time Protocol) ü ü 1) ü ü 1) ü 1)
− Port 2001: Remote operation for SICAM TOOLBOX II ü
· Acquisition of events
− Static Data Sets ü ü ü ü ü ü

− Dynamic Data Sets ü ü ü ü ü ü
− Buffered Reports ü 9) ü 9) ü 9) ü ü ü
− Unbuffered Reports ü ü ü ü ü ü
· Transmission of files
− Disturbance records to SICAM DISTO ü ü ü ü ü ü

Edition 06.2017, DC0-023-2.12
ETA3
ETA5
ET03
ET83
ET25
ET85
· Transmission of integrated totals ü ü ü ü ü ü
· General interrogation ü ü ü ü ü ü
− Set control location ü ü ü ü ü ü
− Check control location ü ü ü ü ü ü
− Command interlocking ü ü ü ü ü ü
− Direct Control with normal security ü ü ü ü ü ü
− Direct Control with enhanced security ü ü ü ü ü ü
− SBO control with enhanced security ü ü ü ü ü ü
· Setting groups ü ü ü ü ü ü

− NTP-Server ü ü ü 1) ü ü 1) ü 1)
− NTP-Client ü ü ü 1) ü ü 1) ü 1)
− SNTP-Client ü ü 1) ü ü 1) ü 1)
− 1703 redundancy ü ü ü ü
− Server redundancy
− GOOSE redundancy
− Dual LAN interface with integrated switch for ring or star

configurations (DNIP)
− RSTP mode ü
− Line Mode ü
− Switch mode ü ü 1) ü 1) ü 1)
− Single mode ü ü 1) ü 1) ü 1)
− Single + Service mode ü ü 1) ü 1) ü 1)
· Protocol Element Control and Return Information
− PRE control message
− START connection to server ("Initiate") ü ü ü ü ü

− STOP connection to server ("Initiate") ü ü ü ü ü
− Send (general) interrogation command ü ü ü ü ü ü
− Send (general) interrogation command for GI group to ü ü 8) ü 8) ü 8) ü 8) ü 8)
own BSE (=simulate received general interrogation command for GI group)
− Preset control location ü ü ü ü ü ü
− PRE return information
· SICAM TOOLBOX II connection over LAN/WAN

("remote connection")
− Remote connection based on HTTP/HTTPS ü ü 1) ü ü 1) ü 1)
− User authentication in SICAM RTUs using “Connection Password” ü ü 1) ü ü 1) ü 1)
− Warning “Remote Connection” ü ü 1) ü ü 1) ü 1)

DC0-023-2.12, Edition 06.2017
ETA3
ETA5
ET03
ET83
ET25
ET85
· Web Server
− Integrated web server to display connection- statistic- and developer ü ü ü ü ü ü
information
− Access to the web server with standard web browser via HTTP ü ü ü 1) ü ü 1) ü 1)
− Access to the web server with standard web browser via HTTPS ü ü 1) ü ü 1) ü 1)
(Hyper Text Transfer Protocol Secure)
− Supported Web Browsers:
- Microsoft Internet Explorer 5, 6, 7, 8, 9 ü ü ü
- Microsoft Internet Explorer 9, 10, 11 ü ü ü
- Microsoft Edge ü ü ü
− Conversion of the time information (UTC; local time w/o normal ü ü ü ü ü ü
time/daylight saving time)
− Signaling / measured value disabling ü ü ü ü ü ü
− Emulation of the going binary information ü ü ü ü ü ü
− Emulation of the data on reception of the attribute Beh.stVal = "OFF" ü ü ü ü ü ü
and Beh.stVal = "BLOCKED"
− Technological adaptation for measured values ü ü ü ü ü ü
− Measured value change monitoring ü ü ü ü ü ü
− Monitoring intermediate and faulty positions of double-point ü ü ü ü ü ü
information
− Logging of the remote commands at the local control center
− Remote parameterization/diagnostic of SICAM RTUs components via ü ü ü ü ü ü

IEC 61850
1) in CP-8000/CP-802x or SICAM AK3 with local PRE (PRE without NIP) this function is integrated on the basic
system element
2) recommendation: max. 30 connections (ETA5, AT25: max. 50) (in case of high load of connection or large
number of data points / logical devices / logical nodes)
3) not limited (limited only by free memory)
4) due to performance matters (initialization times upon connection setup), no more than 2000 data points are
recommended
5) max. startup time (with 10000 data points): approx. 4 min
min. startup time (with 1 data point): approx. 30…60 s (dependent on the configuration of the AU)
6) after startup and terminated initialization of the PRE, the initialization time amounts for each connected Server
1…3 s (dependent on the data extent in the Server); for instance initialization time at 100 Mbit/s and typical data
extent for each Server (approx. 500 data points):
1x SIPROTEC 5...ca. 2.5 s 1x SIPROTEC 4...ca. 2 s
10x SIPROTEC 5...ca. 25 s 10x SIPROTEC 4...ca. 20 s
7) the supported ACSI Services, Common Data Classes and Attributes are described in the sections 9.2.1.1.5,
Basic data types [CDC = Common Data Class] and 9.6.2, Conversion IEC 60870-5-101/104 ↔ IEC 61850

Edition 06.2017, DC0-023-2.12
ETA3
ETA5
ET03
ET83
ET25
ET85
General Functions IEC 61850 Server

− 10/100 Mbit/s (half duplex/full duplex) ü
− 10 Mbit/s (full duplex, auto negotiation) IEC61850 should be used ü 1)
with 100 Mbit/s only!
− 100 Mbit/s (full duplex, auto negotiation) ü ü 1) ü ü 1) ü 1)
− Auto-MDIX (Auto Medium Dependent Interface Crossover) ü 1)
− Parameters for TCP/IP optimization
· IEC 61850 Server

− Goose 6) ü ü ü ü ü ü
− Max. number of Clients (max. connections) 6 6 6 6 6 6
− Max. number of "Logical Devices" (including all servers) 10 10 10 300 300 300
− Max. number of "Logical Nodes" (including all servers) 400 400 400 2) 9) 9) 9)
− Max. number of data points 3) 3) 3) 5) 5) 5)
− ACSI services ü 4) ü 4) ü 4) ü 4) ü 4) ü 4)
− Data classes ü 4) ü 4) ü 4) ü 4) ü 4) ü 4)
− Attributes ü 4) ü 4) ü 4) ü 4) ü 4) ü 4)
− Supported functionality according to:
- PICS (Protocol Implementation Conformance Statement) ü ü ü ü ü ü
- PIXIT (Protocol Implementation Extra Information) ü ü ü ü ü ü
- Supported Logical Nodes and their Attributes ü ü ü ü ü ü
· Supported Ports
− Port 102: MMS (Manufacturing Message Specification) ü ü ü ü ü ü
− Port 80: HTTP (Hypertext Transfer Protocol) - “Web Server“ ü ü ü 1) ü ü 1) ü 1)
− Port 80: HTTP (Hypertext Transfer Protocol) “Remote connection for ü ü 1) ü ü 1) ü 1)
SICAM TOOLBOX II“
− Port 443: HTTPS (Hypertext Transfer Protocol over SSL/TLS) - “Web ü ü 1) ü ü 1) ü 1)
Server“
− Port 443: HTTPS (Hypertext Transfer Protocol over SSL/TLS) - ü ü 1) ü ü 1) ü 1)
“Remote connection for SICAM TOOLBOX II“
− Port 123: NTP V3 (Network Time Protocol) ü ü ü 1) ü ü 1) ü 1)
− Port 123: SNTP V3/V4 (Simple Network Time Protocol) ü ü 1) ü ü 1) ü 1)
− Port 2001: “Remote connection for SICAM TOOLBOX II“ ü
· Acquisition of events (transmission of data ready to be sent)

− Static Data Sets ü ü ü ü ü ü
− Dynamic Data Sets
− Buffered Reports ü ü ü
− Unbuffered Reports ü ü ü ü ü ü
· Transmission of files
− Disturbance records to SICAM DISTO ü ü ü ü ü ü
· Transmission of integrated totals ü ü ü ü ü ü

DC0-023-2.12, Edition 06.2017
ETA3
ETA5
ET03
ET83
ET25
ET85
· General interrogation ü ü ü ü ü ü
− Set control location
− Check control location
− Command interlocking
− Direct Control with normal security ü ü ü ü ü ü

− Direct Control with enhanced security ü ü ü ü ü ü
− SBO control with enhanced security ü ü ü ü ü ü
· Setting groups ü ü ü ü ü ü

− NTP-Server ü ü ü 1) ü ü 1) ü 1)
− NTP-Client ü ü ü 1) ü ü 1) ü 1)
− SNTP-Client ü ü 1) ü ü 1) ü 1)
− 1703 redundancy ü ü
− Server redundancy ü ü ü ü ü ü
− GOOSE redundancy ü ü ü ü ü ü
− Dual LAN interface with integrated switch for ring or star
configurations (DNIP)
- RSTP mode ü
- Line Mode ü
- Switch mode ü
- Single mode ü
- Single + Service mode ü
· Protocol Element Control and Return Information

− PRE control message
- Send (general) interrogation command ü ü ü ü ü ü
- Send (general) interrogation command for GI group to own BSE ü ü 8) ü 8) ü 8) ü 8) ü 8)

- Preset control location

− PRE return information
· SICAM TOOLBOX II connection over LAN/WAN ("remote

connection")
− Remote connection based on HTTP/HTTPS ü ü 1) ü ü ü
− User authentication in SICAM RTUs using Connection Password ü ü 1) ü ü ü
− Warning “Remote Connection” ü ü 1) ü ü 1) ü 1)
· Web Server
− Integrated web server to display connection-, statistic- and developer ü ü ü ü ü ü
information
− Access to the web server with standard web browser via HTTP ü ü ü ü ü ü
− Supported Web Browsers:

Edition 06.2017, DC0-023-2.12
ETA3
ETA5
ET03
ET83
ET25
ET85
- Microsoft Internet Explorer 5, 6, 7, 8, 9 ü ü ü
- Microsoft Internet Explorer 9, 10, 11 ü ü ü
- Microsoft Edge ü ü ü
− Conversion of the time information (UTC; local time w/wo normal ü ü ü ü ü ü
time/daylight saving time)
− Signaling / measured value disabling
− Emulation of the going binary information
− Emulation of the data on reception of the attribute Beh.stVal = "OFF"

and Beh.stVal = "BLOCKED"
− Technological adaptation for measured values ü ü ü ü ü ü
− Measured value change monitoring ü ü ü ü ü ü
− Monitoring intermediate and faulty positions of double-point
information
− Logging of the remote commands at the local control center ü ü ü ü ü ü
− Remote parameterization/diagnostic of SICAM RTUs components via ü ü ü ü ü ü
IEC 61850
1) In CP-8000/CP-802x, or SICAM AK3 with local PRE (PRE without NIP) this function is integrated on the basic
system element
2) May be less due to the number of parameterized connections: with 2 Clients a total of 400 Logical Nodes is
possible, with 4 Clients a total of 200 Logical Nodes is possible
3) The max. possible number of data points can not be stated here in general since this is dependent on several
factors (number of connected Clients, number of used Logical Devices, number of used Logical Nodes, number
of Reports, Memory of the Reports, …); with ETA3 it is additionally dependent on the free memory of the basic
system element (depending on whether a function chart is used, which protocols are configured, …)
4) The supported ACSI Services, Common Data Classes and Attributes are described in the sections 9.2.1.1.5,
Basic data types [CDC = Common Data Class] and 9.6.2, Conversion IEC 60870-5-101/104 ↔ IEC 61850
5) Formulas for the determination of the total number of data points (n):
Unbuffered reports: #LD • 54 + #CON (13 (#LD + #DP/60) • 2) + #DP • 14 = n
Buffered reports: #LD • 54 + #CON (19 (#LD + #DP/60) • 2) + #DP • 14 = n
Unbuffered + buffered reports: #LD • 54 + #CON (32 (#LD + #DP/60) • 2) + #DP • 14 = n
Meaning: Thereby, the following maximum values apply:

#LD number of logical devices ETA5 ET25 ET85
#CON number of connections n = 80000 n = 30000 n = 20000
#DP number of data points
6) only data attributes are supported with Goose Publish and Goose Subscribe (no Data Objects)!
9) unlimited (limited only by available memory)!
Note
As max. possible number with combination of Client and Server the smaller value applies respectively.
Example ET85: 1000 data point + 6 connections.

DC0-023-2.12, Edition 06.2017
9.2 LAN Communication over Ethernet TCP/IP according to

IEC 61850
The IEC 61850 standard series essentially defines:

· Standardized Information
─ for circuit breakers, measured value unit, measured values, status, control, Meta data
etc. with self-description (IEC 61850-7-4)
─ standardized information are based on a set of about 20 general basic types "CDC =
Common Data Classes" (status, measured value, count,…) (IEC 61850-7-3)
─ some of the standardized information are switchgear-specific, others are general
─ the definition of new information models by reusing the standardized information is
explicitly supported
· Standardized Services
─ for unrestricted access to values, signaling of values and archiving/interrogation of
values, …, controlling devices (IEC 61850-7-2)
─ the standardized services can be applied both to the standardized information
(EC 61850-7-4) as well as to any expanded or new information models
· Standardized Networks
─ for the exchange of messages in a narrower sense, suitable standards are selected
─ the standardized services, the standardized information and all other information are
communicated over standardized communication systems (IEC 61850-8-1/ -9-1/ -9-2)
· Standardized Configurations
─ devices and the entire switchgear are described completely formal
─ the IEC 61850-6 standard provides an XML-based system description language
(Substation Configuration Language, SCL) with which the standardized configuration
files are created
„Signals“ Configuration file according IEC61850-6

Logical node & Information models (labeled
Data objects IEC61850-7-4/...7-3 Informations)
describes all layers
Publish/subscribe
Information
Services read/write
exchange switch
„Interface“ (IEC61850-7-2) signal/archive
Mapping on e.g.
Communication MMS and Ethernet, TCP/IP
profiles TCP/IP/Ethernet
(IEC61850-8-1)
Answer Command
values
Device
Network

Edition 06.2017, DC0-023-2.12
Protocols according to the IEC 61870-5 standard are based on the OSI layer model

7 Mapping IEC 60870-5-101 ó IEC 61850
IEC61850
PRE-Status Time
ACSI-Services WEB-Server Remote Sync.
6 Client
Connection
Peer-to-Peer Server for
TOOLBOX II
5 MMS HTTP NTP

Sampled Value
Legend:
Exchange
TCP
4 GOOSE T-Profile
TCP UDP ARP ……...….. Address Resolution Protocol
3 ICMP
MMS ……….… Manufacturing Message Specification
GOOSE ……… Generic Object Oriented Substation Events
Priority Tagging IP Encapsulation RFC 894
1 (IEEE 802.1Q + IEEE 802.1p)
Ethernet
…. IEC 61850

7 - Application Application · Transmit handling
· Receive handling
6 - Presentation Data format · IEC 61850 ACSI to Ax 1703/SICAM RTUs and compatible
systems
Ax 1703/SICAM RTUs-specific system messages and some
user data is implemented (e.g. transmission of disturbance
records to SICAM DISTO)
5 - Session Interface between · GOOSE
data format and · MMS
communication · HTTP
protocol
· Remote operation for SICAM TOOLBOX II
· NTP according to RFC 1305
4 - Transport Communication · TCP/IP according to RFC 791 and RFC 793; GOOSE
3 - Network protocol · ICMP according to RFC 792; GOOSE
2 - Data Link LAN interface · Ethernet 10/100 Mbps according to IEEE 802.3; GOOSE
SICAM TOOLBOX II

DC0-023-2.12, Edition 06.2017
Relevant Standards
Standard Note
IEC 61850-1 Introduction and Overview
- Introduction and overview of the standards of the IEC 61850 series
IEC 61850-2 Dictionary
- Collection of terms
IEC 61850-3 General Requirements (… especially on the network components)
- Quality requirements (reliability), maintainability, system availability, portability,
IT security)
- Environmental conditions
- Auxiliary services
- Other standards and other rules of engineering
IEC 61850-4 System and Project Management
- Engineering service requirements (classification of parameters, technical work
tools, documentation)
- System utilization cycle (product versions, production setting, support after
production setting)
- Quality control (responsibilities, test equipment, type tests, system tests,
factory acceptance tests "FAT" and location acceptance tests "SAT“)
IEC 61850-5 Communication Requirements for Functions and Device Models
- Principle of the logical nodes
- Logical communication links
- Concept of assigned information elements for the communication (PICOM)
- Logical nodes and assigned PICOM
- Functions
- Performance requirements (response times etc.)
- „Dynamic Scenarios“ (requirements on the information flow under various
operating conditions)
IEC 61850-6 Language for the configuration of station automation systems ("Engineering")
- formal description of the single-pole scheme, of devices and system structure and
their assignment to the single-pole scheme
IEC 61850-7-1 Basic communication structure for station and bay-related secondary technology
equipment – principles and models
- Introduction in IEC 61850-7
- Communication principles and models
equipment – Abstract Communication Services Interface (ACSI)
- Description of the abstract communication service interface (ACSI)
- Specification of the abstract communication services
- Model of the server database
equipment – Common Data Classes
- Abstract common data classes and attribute definitions
equipment – Compatible Logic Nodes and Data Classes
- Definition of logical nodes, data objects and their logical addressing
IEC 61850-8-1 Specific Communication Services Modeling (SCSM) – Modeling on MMS
(acc. to ISO/IEC 9501-1 and -2) and ISO/IEC 9501-3
- Illustration for the communication within the entire station (Client-Server
communication and "GOOSE" messages)
IEC 61850-9-1 Specific Communication Services Modeling (SCSM) – Scanned values over serial
Simplex-Multiple-Point-to-Point connection
- Model for the Point-to-Point-like, unidirectional communication of scanned values
of the transformer (with and without Merging Unit)
IEC 61850-9-2 Specific Communication Services Modeling (SCSM) – Scanned values over ISO/IEC
8802-3
- Model for the bus-type, flexible communication of scanned values of the
transformer (with and without Merging Unit)
IEC 61850-10 Conformity Check
- Procedure for the conformity check
IEC 60255-24 IEEE COMTRADE

Edition 06.2017, DC0-023-2.12
Note:
The underlined standards contain essential information for the implementation of the
IEC 61850 functions in the protocol element.
IEC 61850 Definition of Terms
Designation Abbreviation Note

ACSI ACSI Abstract Communication Service Interface
The protocol-independent user interface 'ACSI' decouples the
applications from the underlying communication protocols and bus
physics.
Common Data CDC The IEC 61850 defines different Common Data Classes.
Class Common Data Classes are e.g. single-point information, double-
point information, single command (incl. the return information),
double command (incl. the return information), setpoint value, …
Data D Data is e.g. commands, binary information, status, time, …
Data Class Data Class is also called Common Data Class (CDC)
Data Set DS Selection from the object-orientated data model
(selective data of the hierarchical attributes)
Dynamic Data Dynamic data sets are generated (created) by the client per RUN-
Set Time.
Different Data Sets are created for each Physical Device.
Functional FC The functional constraint (FC) is used for structured grouping of
Constraint data (e.g.: measured values, spontaneous events, command
objects,…)
Static Data Set The Static Data Set is fixed predefined and is either
(a) determined automatically by the device
per Functional Constraint (fixed) ß in SICAM RTUs Server
(b) specified with parameterization tool
rd
e.g.: the static data set for 3 party devices is generated by
an configurator and loaded into the device
Directory DIR The Directory (=MMS-Directory) of the server contains all data that
can be sent in transmit direction or receive direction.
GOOSE The Generic Object Oriented Substation Events (GOOSE) is a
transmission service of IEC 61850 for generic status events, that
can be sent simultaneously per Multicast to multiple devices in
order to satisfy high real-time requirements.
Typical cases of application are the spontaneous transmission of
switching device settings in the decentral interlocking of switching
commands in substations.
GOOSE messages use the ether-type specification for VLAN, the
prioritization and are represented directly on the Ethernet layer.
Logical Device LD A Logical Device is one function in a device (Physical Device).
A Physical Device can contain several functions (Logical Devices).
Logical Devices are e.g. protection functions, control functions,
disturbance recording, measured value acquisition, …
The designation of the Logical Devices is not fixed and can
therefore be freely defined.
Logical Node LN A Logical Node is a subfunction of a Logical Device. Every
subfunction is represented by data objects, which essentially
represent the process information.
Logical Nodes are e.g. switches, protection functions (KU, DTL,
distance calculation), …
LOG Archive function – similar to the decentral archive "DEAR"
…but is presently not supported!

DC0-023-2.12, Edition 06.2017
Designation Abbreviation Note

MMS MMS Manufacturing Message Specification
The Manufacturing Message Specification (MMS) standardizes the
exchange of messages in the production area. MMS provides
functions that can be used for the observation, inspection and
control of device operations and technical processes.
Physical Device IED The Physical Device (also called IED; IED = Intelligent Electronic
Device) is a device usually with 1 Ethernet interface – but can also
be equipped for redundant configurations with several Ethernet
interfaces.
Report Spontaneous transmission from ServeràClient takes place using
Reports
Buffered Reports: [FC = BR]
- spontaneous data remain stored with interface fault
Unbuffered Reports: [FC = RP]
- spontaneous data is deleted with interface fault
Report Control Every Report (in the server) has its own Report Control Block
Block The characteristics of the respective Report are entered in the
Report Control Block
e.g.
- Reference to the Data Set
- Trigger for the transmission (spontaneous, general
interrogation, …)
- Data Set Name (optional)
-…
The Report Control Block can be read and written by the client.
ICD ICD IED Capability Description
Complete configuration of an Intelligent Electronic Device (IED).
This file needs to be supplied by each manufacturer to make the
complete system configuration.
CID CID Configured IED Description
Description file of a selective Intelligent Electronic Device (IED).
EXT in SIPROTEC means “extended” and not “extras“.
SCD SCD Substation Configuration Description
Description file of a whole substation – this is normally created with
a system configurator and contains the Engineering for the entire
plant.
SCL SCL Substation Configuration Language
PICS PICS Protocol Implementation Conformance Statement *)
PIXIT PIXIT Protocol Implementation eXtra Information for Testing *)
MICS MICS Model Implementation Conformance Statement

SCSM SCSM Specific Communication Service Mapping
PICOM PICOM Pieces of Communication
*) the IEC 61850 Interoperability is documented in the documents PICS and PIXIT

Edition 06.2017, DC0-023-2.12
9.2.1 Objects and Data
9.2.1.1 Data Models
The data models for IEC 61850 describe the real data of a device, that can be read or written
over the communication.
The data models are strictly object-orientated. The objects are functions that the user of the
substation requires and knows. Every object defines mandatory or optional data objects.
9.2.1.1.1 Physical Device [IED]
The physical device is also called IED [Intelligent Electronical Device]. The physical device is
a device normally with 1 Ethernet interface. For redundant configurations the physical device
can also be equipped with several Ethernet interfaces.
The IED-Name can be parameterized with the parameter IEC61850 | server | IED
name. However, this IED-Name is not used by the protocol firmware and is only displayed on
the main page of the web server. The IED-Name required for IEC 61850 is only taken by the
protocol element from the data of the SIP message address conversion in transmit/receive
direction.
9.2.1.1.2 Logical Device [LD]
A logical device is one function in a physical device. A physical device can contain several
functions (logical devices). Logical devices are for instance protection functions, control
functions, disturbance recording, measured value acquisition.
The designation of the logical devices is not fixed and can thus be freely defined.
For SIPROTEC the following designations for logical devices will be used:
CTRL .............. Control

DR .................. Disturbance Recording
EXT ................ Extras
MEAS ............. Measurement
PROT.............. Protection

DC0-023-2.12, Edition 06.2017
9.2.1.1.3 Logical Node [LN]
A logical node is a sub function of a logical device. Every sub function is represented by data
objects, which essentially represent the process information.
IEC 61850-7-4 presently defines 92 logical nodes – these largely cover all areas of a modern
substation.
Number of
Designation
Logical Node Categories defined Logical
(first letter)
Nodes
A Automatic Control 4
C Supervisory Control 5
G Generic References 3
I Interfacing and Archiving 4
L System Logical Node 3
M Meetering and Measurement 8
P Protection Functions 28
R Protection Related Functions 10
S Sensors and Monitoring 4
T Instrument Transformer 2
X Switchgear 2
Y Power Transformers 4
Z Further Power System Equipment 15
The IEC 61850 standard series also contains clear rules for the expansion of the information
models. Included among these are supplements to the logical nodes, new logical nodes,
expanded and new data and new data attributes.

Edition 06.2017, DC0-023-2.12
The following logical nodes are supported by SICAM RTUs Client/Server (applies only for
IEC 61850 Edition 1).
Note
As of IEC 61850 Edition 2 all the logical nodes are supported based on the supported CDCs.
Logical Nodes Description S C

A Automatic Control
ANCR Neutral Current Regulator ü ü
ARCO Relative Power Control - -
ATCC Automatic Tap Changer Controller ü ü
AVCO Voltage Control - -
C Supervisory Control
CALH Alarm Handling ü ü
CCGR Cooling Group Control ü ü
CILO Interlocking ü ü
CPOW Point-On-Wave Switching - -
CSWI Switch Controller ü ü
G Generic References
GAPC Generic Automatic Process Control ü ü
GGIO Generic Process I/O ü ü
GSAL Generic Security Application - -
I Generic References
IARC Archiving - -
IHMI Human Machine Interface ü ü
ITCI Telecontrol Interface - -
ITMI Telemonitoring Interface - -
L System Logical Node

LLN0 Logical Node Zero ü ü
LPHD Physical Device Information ü ü
M Metering and Measurement

MDIF Differential Measurements ü ü
MHAI Harmonics Or Interharmonics - -
MHAN Non Phase Related Harmonics Or Interharmonics - -
MMTR Metering ü ü
MMXN Non Phase Related Measurement ü ü
MMXU Measurement ü ü
MSQI Sequence & Imbalance ü ü
MSTA Metering Statistics ü ü
P Protection Functions
PDIF Differential ü ü
PDIR Direction Comparsion ü ü
PDIS Distance ü ü
PDOP Directional Overpower ü ü
PDUP Directional Underpower ü ü

DC0-023-2.12, Edition 06.2017

PFRC Rate Of Change Of Frequency ü ü
PHAR Harmonic Restraint ü ü
PHIZ Ground Detector ü ü
PIOC Instantaneous Overcurrent ü ü
PMRI Motor Restart Inhibition ü ü
PMSS Motor Starting Time Supervision ü ü
POPF Over Power Factor ü ü
PPAM Phase Angle Measuring ü ü
PSCH Protection Scheme ü ü
PSDE Sensitive Directional Earthfault ü ü
PTEF Transient Eart Fault ü ü

P Protection Functions continued
PTOC Time Overcurrent ü ü
PTOF Over Frequency ü ü
PTOV Overvoltage ü ü
PTRC Protection Trip Conditioning ü ü
PTTR Thermal Overload ü ü
PTUC Undercurrent ü ü
PTUF Under Frequency ü ü
PTUV Undervoltage ü ü
PUPF Under Power Factor ü ü
PVOC Voltage Controlled Time Overcurrent ü ü
PVPH Volts per Hz ü ü
PZSU Zero Speed Or Underspeed ü ü
R Protection Related Functions
RADR Disturbance Recorder Channel Analog ü -
RBDR Disturbance Recorder Channel Binary ü -
RBRF Breaker Failure ü ü
RDIR Directional Element ü ü
RDRE Disturbance Recorder Function ü ü
RDRS Disturbance Record handling - -
RFLO Fault Locator ü ü
RPSB Power Swing Detection / Blocking ü ü
RREC Autoreclosing ü ü
RSYN Synchronism-Check or Synchronising ü ü
S Sensors and Monitoring
SARC Monitoring And Diagnostic For Arcs - -
SIMG Insulation Medium Supervision (Gas) ü ü
SIML Insulation Medium Supervision (Liquid) ü ü
SPDC Monitoring And Diagnostics For Partial Discharges - -
T Instrument Transformer
TCTR Current Transformer ü ü
TVTR Voltage Transformer ü ü

Edition 06.2017, DC0-023-2.12

X Switchgear
XCBR Circuit Breaker ü ü
XSWI Circuit Switch ü ü
Y Power Transformers
YEFN Earth Fault Neutralizer (Petersen Oil) - -
YLTC Tap Changer ü ü
YPSH Power Shunt - -
YPTR Power Transformer ü ü
Z Further Power System Equipment
ZAXN Auxiliary Network ü ü
ZBAT Battery ü ü
ZBSH Bushing - -
ZCAB Power Cable - -
ZCAP Capacitor Bank - -
ZCON Converter - -
ZGEN Generator - -
ZGIL Gas Insulated Line - -
ZLIN Power Overhead Line - -
ZMOT Motor - -
ZREA Reactor - -
ZRRC Rotating Reactive Component - -
ZSAR Surge Arrestor ü ü
ZTCF Thyristor Controlled Frequency Converter - -
ZTCR Thyristor Controlled Reactive Component - -
The logical nodes "LLN0" and "LPHD0" must always be present in every logical device. The
logical nodes "LLN0" and "LPHD1" are created automatically by the protocol element for every
logical device, insofar as these have not already been defined through the parameterization
(SIP message address conversion).
The logical node "LLN0" contains data which apply for all logical nodes of the logical device
(e.g. revision status of the parameters).
The logical node LPHD1 contains data of the IED's [Intelligent Electronical Device = Physical
Device] – these are applicable for all logical nodes of the physical device (e.g. rating plate).
Logical nodes are structured hierarchically and contain different groups of information:
· Common Logical Node Information

· Optional Logical Node Information
· Status Information
· Settings
· Measured Values
· Controls

DC0-023-2.12, Edition 06.2017
Example:
Logical Node
XCBR1 Logical Node: Circuit Breaker [ XCBR ]
Common Logical Node Information

Mode …………..……………………. [Mod] … information independent from
Behavior ……...………..…………… [Beh] the dedicated function represented
by the LN.
Health ……………………………….. [Health] E.g. mode, health, name plate, ...
Name Plate ……………………...…..[NamePlt]
Optional Logical Node Information

Local Operation ……………………. [Loc]
External Equipment Health ……….. [EEHealth]
External Equipment Name Plate …. [EEname]
Operation Counter ……………...…..[OpCnt]
Controls
… are data, which are changed by
Switch Position ..…………………… [Pos] commands like switchgear state
(ON/OFF), tap changer position or
Block Opening ……….…………….. [BlkOpn] resetable counters.
Block Closing ………………………..[BlkCls] E.g. total active power, total
Charger Motor Enabled ………..….. [ChaMotEna] reactive power, frequency, net real
energy since last reset, ...
Metered Values (Measured Values) … are analogue data measured

from the process or calculated in
Sum of Switched Amperes…. [SumSwARs] the functions like currents,
(resetable) voltages, power etc.
e.g. total active power, total
reactive power, frequency, net real
energy since last reset, …
Status Information
Circuit Breaker Operating …………. [CBOpCap] … information representing either
Capability the status of the process or of the
function allocated to the LN.
Point On Wave Switching ………... [POWCap] e.g. switch type, switch operating
Capability capability,...
Circuit Breaker Operating. ………... [MaxOpCap]
Capability When Fully Charged

Edition 06.2017, DC0-023-2.12
The precise structure of the logical nodes is documented in the IEC 61850-7-4 standard.
In the following example, the structure of the logical node for the circuit breaker [XCBR] is
documented schematically with designation of the fields.
Phsyical Device
IED Locical Device #1
LD#1 Locical Device #2
LD#2
Logical Node
LHPD
These logical nodes must be
created on each logical device
LLN0 Logical Node LN Reference
e.g. XCBR1 XCBR1
[LLName] ………….... Logical Node Attribute

[LOC] ………………... Common Logical Node Information
[EEHealth] ………….. Logical Node Attribute „POS“

Data CDC = „Controllable Double Point“ (DPC)
[EEName] ……………
Data Reference
[OpCnt] ………………
[Pos] ……………….… Position Controls

XCBR1.Pos
Data Attribute Data Attribute Reference

[ctlVal] ……. Control Value XCBR1.Pos.ctlVal
Attribute Type = BOOLEAN Logical Node
CONTROL
0 = OFF
Attribute Type
1 = ON
XCBR
[operTim] … Operate Time XCBR1.Pos.operTim
[origIn] ……. Originator XCBR1.Pos.orIgin
[ctlNum] ….. Control Number XCBR1.Pos.ctlNum
Common Data Class:

Status Value „Controllable Double Point“
(DPC)
Attribute
[stVal] ….…. Status Value XCBR1.Pos.stVal
Attribute Type = CODED ENUM
0 = intermediate-state
1 = off Attribute Type
2 = on
STATUS
3 = bad-state
[q] ……..….. Quality XCBR1.Pos.q
[t] ……….... Time Stamp XCBR1.Pos.t
[stSeld] ….... Selected Œ XCBR1.Pos.stSeld

SUBSTITUTION
[subEna] ..… Substit. Enable XCBR1.Pos.subEna

[subVal] ...… Substit. Value XCBR1.Pos.subVal
[subQ] …..… Substit. Q • XCBR1.Pos.subQ
[subID] ….… Substit. ID Ž XCBR1.Pos.subID
[pulseConfig] ..… Pulse Configuration XCBR1.Pos.pulseConfig

DESCRIPTION and
CONFIGURATION,
[ctlModel] …...…. Control Model XCBR1.Pos.ctlModel

EXTENSION
[sboTimeout] ….. SBO Timeout XCBR1.Pos.sboTimeout

[sboClass] …..… SBO Class XCBR1.Pos.sboClass
[d] ………………. Textual desc. of data XCBR1.Pos.d
[dataNs] ……..… Data Name Space XCBR1.Pos.dataNs
[cdcNs] ……...… CDC Name Space XCBR1.Pos.cdcNs
[BlkOpn], [BlkCls], [ChaMotEna]
[SumSwArs] Metered Values
[CpOpCap], []POWCap], [MaxOpCap] Status Information
e.g. XCBRn
Œ… The controllable data is in the status „selected“
•… Value used to substitute the data attribute „q“
Locical Device #2 Ž… Shows the address of the device that made the substitution.
LD#n The value of null shall be used if subEna is false of if the device is not known

DC0-023-2.12, Edition 06.2017
The following example shows the representation of the logical node in the IEC 61850-7-4
standard for the circuit breaker (XCBR).
Legend: M…Mandatory (these attributes must be supported mandatory)

O…Optional (these attributes can be supported optionally)
The Common Data Class [CDC] is shown in the field "Attr. Type".
The following example shows the representation of the basic data types [CDC] in the
IEC 61850-7-3 standard for the Common Data Class "Controllable Double Point (DPC)".

Edition 06.2017, DC0-023-2.12
IEC 61850 Address

The IEC 61850 address is represented as readable text (ASCII-characters) and is presently
limited to max. 62 characters. The syntax of the 61850 variable names [Data Attribute
Reference] is defined by the IEC 61850 standard.
Every object is unambiguously identified by its address (name of the object) in plain text.
Due to the address, the objects are self-descriptive.
Structure (principle):
IED001_CTRL/Q0CSWI1.Pos.ctlVal
LDName LNName DataName DataAttributeName
LDName/LNName.DataName.DataAttributeName
LDName ………Logical Device Name
LNName .…….. Logical Node Name
Data and data attributes can thereby occur several times in the structure.
IED001.MEAS / Q1MMXU1 . PhV . phsA . cVal . mag . f
LDName LNName DataName DataName
DataAttributeName
DataComponentName
DataComponentName
Edition 1:
61850 address: LDName + "/" + FCD = 32 + 1 + 29 = max. 62 characters

FCD: LNName + DataName + DataAttributeName + DataComponentName =
max. 29 characters
LDName: IEDName + LDName = max. 32 characters
LNName: LN_prefix + LN_classname + LN_instanceID = max. 11 characters
Lnclassname: = max. 4 characters
DataName: = max. 10 characters
Edition 2:
61850 address: LDName + "/" + FCD = 64 + 1 + 64 = max. 129 characters

FCD: LNName + DataName + DataAttributeName + DataComponentName =
max. 64 characters
LDName: IEDName + LDName = max. 64 characters
LNName: LN_prefix + LN_classname + LN_instanceID = max. 11 characters
Lnclassname: = max. 4 characters
DataName: = max. 10 characters
Note
The address must not contain any special characters (excluded from this are the established separating
characters "/" and ".") and no umlauts.
In Edition 2 there may also be no more “.” In the Logical Device Name.

DC0-023-2.12, Edition 06.2017
The structure of the IEC 61850 address is explained with the help of the following example.
IEC61850 Address (example): BC1703CTRL/Q00XCBR1.Pos.stVal
Data Attribute Reference
Data Reference
Logical Node Reference
Functional Constraint Data (FCD)
BC1703 CTRL / Q00 XCBR 1 . Pos . stVal

Data Attribute Name
- the name is standardized (61850)
Data Name
(Data Object Name)
Logical Node Name „Suffix“
Name ”LNName“
- only numbers are allowed
IEC 61850 Address

Logical Node
Logical Node Name „Class“
Logical Node Name „Prefix“

[optional]
- the name is freely definable
Logical Device Name [optional]
Name ”LDName“
Logical Device
IED Name (physical device)

(the 1st sign must be a character)
… the seperators at these positions are defined by standard IEC 61850

optional fields (all other fields are mandatory!)
Examples for the valid syntax of 61650 addresses:
BC1703CTRL/Q00XCBR1.Pos.stVal
VL.C01/Q0XCBR1.Mod.stVal
T403B1CTRL/GGIO10.SPCSO0.ctlVal
IED001MEAS/Q1MMXU1.Mod.ctlVal
System information module failed: BC1703CTRL/SYSGGIO1.SPCSO1.stVal

Reference voltage U4: BC1703MEAS/GGIO1.AnInU4.mag.f
Examples for a 61850 address with max. recursion depth:
IED001.MEAS/Q1MMXU1.PhV.phsA.cVal.mag.f
BC1703_E17CTRL/GO_E07GGIO1.DPCSOQ1.stVal

Edition 06.2017, DC0-023-2.12
MMS Address
For the transmission the IEC 61850 address is converted by the protocol element on the line
to the defined format of the MMS address.
The MMS address is presently used with max. 65 characters. Of the 65 bytes, 3 characters
are fixed reserved through the FCD (Functional Constraint Data) and 1 separating character
by the MMS address structure. As a result, the present implementation produces a max.
possible length for the 61850 address of 62 characters.
MMS-Adresse (Example): BC1703CTRL/Q00XCBR1$ST$Pos$stVal

Functional Constraint Data (FCD)
BC1703 CTRL / Q00 XCBR 1 $ ST $ Pos $ stVal
• • • •
Functional Constraint
- built by the protocol element
(2 signs fixed)
• The separators at these positions are defined by the MMS -Norm
Functional Constraint
The field "Functional Constraint [FC]" of the MMS address is inserted by the protocol element
itself.
One IEC 61850 Common Data Class [CDC] consists of various Functional Constraints (a
Common Data Class is e.g. single-point information, double-point information, …)
FC Functional Constraint
CF Attribute used for configuration
CO Control
DC Attribute used for description
EX Attribute used for extensions of common data classes
MX Measurands (analog values)
SE Attribute used for edit parameter group
SG Attribute used for active parameter group
SP Setpoint
ST Status Information
SV Attribute used for substitution
Examples for the valid syntax of MMS addresses:
BC1703CTRL/Q00XCBR1$ST$Pos$stVal
VL.C01/Q0XCBR1$ST$Mod$stVal
T403B1CTRL$GGIO10$CO$SPCSO0$ctlVal
BC1703_E17CTRL/GO_E07GGIO1$ST$DPCSOQ1$stVal
Examples for MMS addresses with max. recursion depth:
VL.C01/MMXU1$MX$A$phsA$cVal$mag$f

DC0-023-2.12, Edition 06.2017
9.2.1.1.4 Data Class, Data
Attributes are those data objects which contain real information.
The attributes are assigned to the common data classes. The common data classes [CDC's]
are documented in the IEC 61850-7-3 standard.
The elements "Physical Device", "Logical Device", "Logical Node" and "Data Class" are only
used for the structuring of the data.
The CDC's are structural elements with attribute-types that contain (apart from a few
exceptions) no further sub-structures.
Attribute types (without SUB-structure): e.g.: BOOLEAN, INT8U, INT32U, …

Attribute types (with SUB-structure): e.g.: TimeStamp, Quality, Originator, …
SUB-structures defined in 61850 will be mapped to MMS SUB-structures (if supported by

MMS) or mapped to common data classes.
Note
Attribute types in upper case / lower case (e.g. TimeStamp) have a further sub-structure.
Attribute types in upper case (e.g. BOOLEAN) have no further sub-structure.

Edition 06.2017, DC0-023-2.12
9.2.1.1.5 Basic data types [CDC = Common Data Class]
All standardized information according to IEC 61850-7-4 (e.g. circuit breaker, measured value
unit, measured values, status, control, meta data) are based on a set of about 30 general
basic data types (status, measured value, count).
The basic data types are known as Common Data Classes [CDC] and are defined in the
IEC 61850-7-3 standard.
CDC 1) Common Data Class Specification for Ss Sr SsG SrG Cs2) Cr 2)

[abbrev.]
Status Information
SPS Single Point Status ü - ü ü - ü
DPS Double Point Status ü - ü ü - ü
INS Integer Status ü - ü - - ü
ENS Enumerated Status ü 3) - ü 3) ü 3) - ü 3)
ACT Protection Activation Information ü - ü ü - ü
ACD Directional Protection Activation ü - ü ü - ü

Information
SEC Security Violation Counting - - - - - -
BCR Binary Counter Reading ü - - - - ü
Measurand Information
MV Measured Value ü - ü ü - ü
CMV Complex Measured Value ü - ü ü - ü
SAV Sampled Value ü - ü ü - ü
WYE Collection Of Measurands ü - ü ü - ü

(Phase to ground related measured
value of a three phase system)
DEL Delta (phase to phase related measured ü - ü ü - ü
value of a three phase system)
SEQ Sequence ü - ü ü - ü
HMV Harmonic Value - - - - - -
HWYE Harmonic Value for WYE - - - - - -
HDEL Harmonic Value for DEL - - - - - -
Controllable Status Information

SPC [ST|CO] Controllable Single Point ü|- -|ü ü|- ü|- -|ü ü|-
DPC [ST|CO] Controllable Double Point ü|- -|ü ü|- ü|- -|ü ü|-
INC [ST|CO] Controllable Integer Status ü|- -|ü ü|- - -|ü ü|-
ENC [ST|CO] Controllable Enumerated Status ü|- 3) -|ü 3) ü|- 3) - -|ü 3) ü|- 3)
BSC [ST|CO] Binary Controlled Step Position ü|- -|ü - - -|ü ü|-
Information
ISC [ST|CO] Integer Controlled Step Position ü|- -|ü - - -|ü ü|-
Information
Controllable Analog Information
APC Controllable analog set point information ü|- 3) -|ü 3) - - -|ü 3) ü|- 3)
Status Settings
SPG Single Point Setting - - - - - -
ING [SP] Integer Status Setting ü 3) ü 3) - - ü ü
Analog Settings
ASG [SP] Analog Setting ü 3) ü 3) - - ü ü
CURVE Setting Curve - - - - - -

DC0-023-2.12, Edition 06.2017
CDC 1) Common Data Class Specification for Ss Sr SsG SrG Cs2) Cr 2)

[abbrev.]
Description Information
DPL Device Name Plate ü 4) - - - - -
LPL Logical Node Name Plate ü 4) - - - - -
CSD Curve Shape Description - - - - - -
SGCB Setting Group Control Block 5) ü ü - - ü ü
For commands, the “Extended Common Data Classes” defined in the IEC 61850-8-1 standard
are used. These "Extended Common Data Classes" consist of several attributes that are used
differently according to IEC 61850 Control Model.
CDC 1) Extended Common Data Class Ss Se SsG SrG Cs Ce

[abbrev.] Specification for 2) 2)
Controllable Status Information

SPC [ST|CO] Extended Common Data Class ü|- -|ü ü|- ü|- -|ü ü|-
Controllable Single Point
DPC [ST|CO] Extended Common Data ü|- -|ü ü|- ü|- -|ü ü|-
ClassControllable Double Point
INC [ST|CO] Extended Common Data Class ü|- -|ü ü|- - -|ü ü|-
Controllable Integer Status
BSC [ST|CO] Extended Common Data Class Binary ü|- -|ü - - -|ü ü|-
Controlled Step Position Information
ISC [ST|CO] Extended Common Data Class Integer ü|- -|ü - - -|ü ü|-
Controlled Step Position Information
Controllable Analog Information
APC Extended Common Data Class ü|- 3) -|ü 3) - - -|ü 3) ü|- 3)
Controllable Analog Set Point
Information
1) Common Data Classes with the additional designation [ ST|CO] are supported differently by the
Server/Client for the Functional Constraints "ST" (Status Information) and "CO" (Control)
2) in the protocol element with 61850-Client function, for data (attributes) in transmit/receive direction
that are not contained in the 61850 standard, the Common Data Class (CDC) can be
parameterized
Devices of different manufacturers utilize the possibility in order to expand the logical nodes
defined in the standard with additional attributes for data in the private range. For the expansion in
the private range, only Common Data Classes can be selected that are already defined in the
standard and are supported by the protocol element. The expansions are only supported at the
logical node level and with the parameterization the highest value Common Data Class in the
hierarchy must be parameterized.
Examples: VL.C01/CSWI1.SPos.ctlVal (SPos = DPC)
VL.C01/XCBR1.SPos.ctlVal (SPos = DPC)
VL.C01/MMXU1.STotW.mag.f (STotW = MV)
VL.C01/MMXU1.AS.phsA.cVal.mag.f (AS = WYE)
3) applies only for IEC 61850 Edition 2
4) this information is generated by PRE
5) SGCB is a Control Block and not a Common Data Class, but is handled as a CDC by the protocol
element
Legend:
Ss ...........Server transmitting
Sr ............Server receiving
Cs ........... Client transmitting
Cr ............ Client receiving
SsG.......... Server transmitting GOOSE (publish)
SrG .......... Server receiving GOOSE (subscribe)

Edition 06.2017, DC0-023-2.12
9.2.2 Definition of the Connections
IP Addresses
Every device which is connected to a TCP/IP network has an unambiguous IP address.
The protocol firmware supports only IP addresses in the format IPv4 (=32 Bit). With that, 2 32,
in other words 4,294,967,296 addresses can be represented. The IP address is mostly
represented in the dotted decimal notation.
Example: 192.168.122.195
The IP address of the own station is to be parameterized in the system-technical parameters

with the parameter IP address | own IP address.
The IP address(es) of the remote station(s) is(are) to be parameterized for each connection in
the system-technical parameters of the connection definition.
Port Number
Every IP connection is defined by the IP address of the own station and the remote station
and the port number. The port numbers are defined by the IANA (Internet Assigned Numbers
Authority).
Port numbers used in the LAN/WAN protocol firmware:
ETA3
ETA5
ET03
ET83
ET25
ET85
Port
Number Protocol Standard
102 MMS
(Manufacturing Message ISO/IEC 9506 ü ü ü ü ü ü
Specification)
HTTP
80 (Hypertext Transfer Protocol) RFC 2616 ü ü ü ü ü 1) ü 1)
(HTTP/1.1)
HTTP Remote operation for
80 ü ü ü ü 1) ü 1)
(Hypertext Transfer Protocol) SICAM TOOLBOX II
HTTPS
443 (Hypertext Transfer Protocol over Web Server ü ü ü ü 1) ü 1)
SSL/TLS)
HTTPS
443 (Hypertext Transfer Protocol over Remote operation for ü ü ü ü 1) ü 1)
SSL/TLS) SICAM TOOLBOX II
NTP V3
123 ü ü ü ü ü 1) ü 1)
(Network Time Protocol) RFC 1305
SNTP V4
123 ü ü ü ü 1) ü 1)
(Simple Network Time Protocol) RFC 2030
Remote operation for Remote operation for
2001 2) ü
SICAM TOOLBOX II SICAM TOOLBOX II
RSTP
---- (Rapid Spanning Tree Protocol) IEEE 802.1D, Edition ü
2004
1) In CP-8000/CP-802x, or SICAM AK3 with local PRE (PRE without NIP) this function is integrated
on the basic system element
2) This port number is not registered at IANA!
Legend:
RFC Request for Comments

DC0-023-2.12, Edition 06.2017
Default Router (Default Gateway)

If the own network is connected by means of a router, then the IP address of the default router
is to be set in the system-technical parameters of the protocol firmware with the parameter IP
address | Default router (default gateway).
Subnet Mask
The subnet mask is a bit mask, which splits up an IP address into a network part and a device
part (host part). It is used in IP networks to make routing decisions.
The subnet mask is to be set in the system-technical parameters of the protocol firmware with
the parameter IP address | Subnet mask.
The subnet mask is exactly as long as the IP address on which it is applied (therefore 32 Bit
for IPv4). All bits of the network part are set to "1" and all bits of the device part to "0".
Predominantly, the notation of a network mask is not performed binary, rather (as for IP
addresses too) frequently in decimal notation (dotted decimal notation).
Consequently, the IPv4 network mask for a 27 bit network part reads 255.255.255.224.
The usable address space of a network is defined by the subnet mask. For a 27 bit network
part, the first 27 places of the IP address of the network part are identical and for all hosts of
the network. The network part is continuous in all practical cases of application (without zeros
in between).
Example: Calculation of network and host section

IPv4 address = 192.168.122.195
Network part = 27 Bit à Subnet mask = 255 . 255 . 255 . 224
11111111 11111111 11111111 11100000
Decimal Binary Calculation

Network mask 255.255.255.224 11111111 11111111 11111111 11100000 AND Subnet mask
Network part 192.168.122.192 11000000 10101000 01111010 11000000 = Network part

Network mask~ 255.255.255.224 00000000 00000000 00000000 00011111 AND (NOT subnet mask)
Device part 3 00000000 00000000 00000000 00000011 = Device part
A network mask with 27 bits set produces a network part of 192.168.122.192.

5 bits, and therefore 32 addresses, remain for the device part.
In the example above, the smallest host address ends with 11000000 (decimal: 192), the
largest possible host address with the octet 11011111 (decimal: 223).
The address range for the subnet in the example is therefore 192.168.122.192 to
192.168.122.223.
The largest address is by definition reserved for the IP broadcast and the smallest address
describes the network itself. They are therefore not included among the freely usable
addresses.
In practice, the default gateway is often assigned to the smallest (in the example, binary:
11000001, decimal: 193) or the largest (in the example, binary: 11011110, decimal: 222)
usable IP address in the network.

Edition 06.2017, DC0-023-2.12
Connection-specific parameters
In the master station and in the remote terminal unit(s), the required settings are to be carried
out in the parameters of the connection definition for every connection.
The following parameters can be set per connection:
· "Station Number"
reference for that connection to which an IP address is assigned. During the data
transmission, only the IP address assigned to the station number is transmitted, the station
number is not transmitted.
For the data flow routing, the data to be transmitted are routed to a "station number"
(connection number = destination station number).
The station number is to be entered for each connection in the parameters connection
definition | Station number.
· "Enable"
A parameterized connection can be activated/deactivated with the parameter
connection definition | Enable.
Thus, connections can be prepared that are activated only at a later moment by means of
parameterization.
· "Station Failure"
For certain redundancy configurations or operating modes, for the SICAM RTUs internal
diagnostics, the failure of a connection can be suppressed with the parameter
connection definition | Station failure.
If the failure is suppressed, the connection is never signaled in the diagnostic as failed and
all messages in transmit direction are discarded until the connection is established!
Note: As a result a ring overflow is avoided with non-connected remote stations.
· "Own Mode"
For every TCP/IP connection one party is either "Server (Listener)" or "Client (Connector)".
The TCP/IP connection is always only established by the "Client (Connector)".
With the parameter connection definition | Own mode the role of the own station
is to be parameterized for every connection.
· "IP-addr"
LAN IP networks. This address must always be unambiguous in one network.
parameters connection definition | IP-addr.
· "AE Qualifier"
This parameter applies for a connected server, if that requires resp. checks the
corresponding AE Qualifier for the connection setup. The value of the AE Qualifier is in the
ICD file of the corresponding server.
The AE Qualifier is to be parameterized for every connection with the parameters
connection definition | AE qualifier.
The settings of the variable elements of the message in the IEC 60870-5-101/104 parameter
block of the basic system element are not evaluated by the 61850 protocol element.

DC0-023-2.12, Edition 06.2017
In the 61850 Client as of Edition 2, the following parameters can be set per connection:
· "Timeout IEC61850 connection"

Timeout for the cyclic connection reestablishment to the connected device (default 10 s).
· "Timeout IEC61850 services"
Timeout for IEC61850 services, every service must be confirmed within this timeout. This
timeout is increased during command transmission to the Timeout ACTàCON (default
7 s).
· "Reports"
Selection of reports. With unbuffered, buffered and buffered, unbuffered both are used
with priority to the first selection. With unbuffered and buffered only the parameterized
reports are used (unbuffered, buffered/buffered, unbuffered/unbuffered/buffered/single
read requests)
· "Timeout buffered reports"
After a communication breakdown, the Buffered Report will not be flushed during this time
(default 0).
· "cbName dynamic"
Values of reports writable (dynamic).
· "dataSet dynamic"
· "rpID dynamic"
· "optFields dynamic"
· "bufTime dynamic"
· "trgOps dynamic"
· "intgPd dynamic"
· "Dynamic datasets"
Server supports dynamic datasets.
· "Elements for dataset"
Count of elements for dynamic datasets (typical = default 60).
· "Beh.stVal = 2 (blocked)"
If the attribute "Beh.stVal" changes to blocked, all hierarchical data points from the
connected device are generated with the parametrized status. If "LLN0.Beh.stVal" is used,
all data points from the logical device are generated.
· "Beh.stVal = 5 (off)"
If the attribute "Beh.stVal" changes to off, all hierarchical data points from the connected
device are generated with the parametrized status. If "LLN0.Beh.stVal" is used, all data
points from the logical device are generated.
· "Convert commands EXE -> SEL/EXE"
Automatic conversion of execute commands to IEC61850 select/execute commands.
· "Delay SEL -> EXE (ms)"
With automatic conversion of execute commands this time is used between SEL and EXE
(default 0).
· "Termination"
Derive Termination for commands from the IEC 61850 Termination or from the return
information, if the IEC 61850 Termination is before the return information. A received neg.
Termination will always be generated (IEC 61850 command termination/ IEC 61850 return
information).

Edition 06.2017, DC0-023-2.12
· "Timeout SEL -> EXE (s)"

Max. time between Select and Execute for commands (default 20 s).
· "Timeout ACT -> CON (s)"
Max. time between Activation and Confirmation for commands (default 20 s).
· "Timeout CON-> TERM (s)"
Max. time between Confirmation and Termination for commands (default 20 s).
· "Intermediate position suppression time (s)"
Intermediate state suppression time for double-point information (default 0).
· "Faulty state suppression time (s)"
Faulty state suppression time for double-point information (default 0).
· "IED name"
IED name for ICD file import. This parameter should not be changed manually.
· "ICD/SCD file"
ICD file name for ICD import. This parameter should not be changed manually.
· "File transfer"
File transfer in connected Server supported.
· "TrgOps data change"
Trigger Op value in connected Server supported.
· "TrgOps quality change"
· "TrgOps data update"
· "TrgOps integrity"
· "TrgOps general interrogation"

DC0-023-2.12, Edition 06.2017
9.2.2.1 Data Transmission Procedure
The transmission of data ready to be sent from the master station (61850-Client) to the remote
terminal unit (61850-Server) takes place spontaneously with connection established and for
each connection.
The transmission of data ready to be sent from the remote terminal unit (61850-Server) to the
master station (61850-Client) takes place either spontaneous by means of 61850-Reports or
interrogated by the master station.
For each LAN connection, the Client-Server data transmission is comparable with that
between 2 stations over a virtual point-to-point connection.
In addition, with 61850, for the transmission of data between servers the multicast
transmission procedure "GOOSE" (Generic Object Oriented Substation Events) is used.
on the Ethernet is determined with the parameter advanced parameters | Ethernet
speed and duplex or when using dual-Lan interface (Dual Ethernet NIP) with the
parameter advanced parameters | DNIP (Dual Ethernet NIP) | Ethernet speed
and duplex | Port# ethernet speed and duplex. In the default setting this parameter
is set to "Auto negotiation" and only needs to be specifically adjusted in exceptional cases.
Auto negotiation ("Auto-Sensing") is an Ethernet procedure by which two connected devices
(e.g. a network port of a computer and the network port of a Router, Hub or Switch) choose
common transmission parameters, such as speed, duplex mode, and flow control. In this
process, the connected devices first share their capabilities regarding these parameters and
then choose the highest performance transmission mode they both support. This procedure is
only used for wired Ethernet ((twisted pair cable) – but not for WLAN-, fiber optic- or coaxial
cables.
Note
If problems occur with the default setting when coupling other systems directly with cross-over cables or
when using HUB's or other network components, here "half duplex" is to be used.
The data storage on the basic system element is managed individually for every LAN
connection. Data messages "to all" are already split up selectively for every LAN connection
by the communications function on the basic system element (BSE).
The prioritization of the data to be sent to the protocol element takes place on the basic
system element (BSE). System data is processed with high priority by the communications
function on the basic system element and transferred to the protocol element for transmission
as fast as possible.
This prioritization is of no significance for the protocol element with 61850-Server function.
The data is received from the basic system element by the protocol element, entered in the
IEC 61850 organized process image on the protocol element and prepared for transmission
according to IEC 61850.
The possible 104-blocking for the data transmission between basic system element ó
protocol element is not used.
In the SICAM RTUs protocol element with 61850-Client function, with the parameter
IEC61850 | client | Timeout IEC61850 Services the monitoring time for 61850
Services (e.g.: Read/Write) can be set. For commands, this monitoring time is extended to the
time that can be set with the parameter IEC61850 | Timeout Confirmation ->
Termination (as of 61850 Ed.2: connection definitions | Timeout CON → TERM).

Edition 06.2017, DC0-023-2.12
9.2.2.2 Failure Monitoring
The monitoring of every connection by the master station (Client) and by the remote terminal
unit (Server) is carried by means of cyclic transmitted messages (TCP Keep Alive Frames).
The failure monitoring can be carried out independently by both participating stations of a
connection.
The "TCP Keep Alive Frames" are generated and monitored by the TCP/IP-Stack of the
protocol firmware itself and are not transferred to the basic system element.
The time scale for the cyclic transmission of the "TCP Keep Alive Frames" is determined with
the parameter advanced parameters | TCP keep alive time.
If with connection established, the cyclic reception of the "TCP Keep Alive Frames" is missing,
the failure of the connection is signaled by the TCP/IP-Stack of the protocol firmware. The
failure of a connection is signaled immediately by the protocol element to the basic system
element, insofar as this is not disabled in the parameters of the connection definition
with the parameter Station failure.
With connection failed, the client attempts to re-establish a connection to the assigned server
in a cyclic time-scale. The time-scale can be set with the parameter IEC61850 | Client |
Timeout IEC61850 connection setup (as of 61850 Ed.2: connection definitions |
connection establishment (s)).
No further data is sent from the connections with Client-functionality to failed remote stations
until successful establishment of the connection and the initialization of the connection.
the re-reachable remote station.
From the connections with Server-functionality, further data is requested from the basic
system element and stored in the PRE internal IEC 61850 data model, even with failed
connection to the remote station.
Initialization of the Connections [Client]

After startup, all parameterized connections with 61850-Client function are reported by the
protocol element as failed (insofar as this is not disabled in the parameters of the connection
definitions) and afterwards the connection is established for every single connection at TCP/IP
level by the 61850-Client.
For failed or unreachable remote stations, a connection setup (attempt) for the connection is
performed cyclic by the 61850-Client.
After complete initialization of a connection, the protocol element with 61850-Client function
will reset the connection failure and starts requesting the data from the basic system element
and initiates a general interrogation to the basic system element.
Initialization of the Connections [Server]

For each connection with 61850-Server function, the protocol element waits for an
establishment of the connection at TCP/IP level by the 61850 Client.

DC0-023-2.12, Edition 06.2017
9.2.4 Acquisition of Events (Transmission of Data Ready to be Sent)
With connection established, the transmission from the master station (Client) to the remote
terminal unit (Server) takes place spontaneously. The transmission from the remote terminal
unit (Server) to the master station (Client) takes place either spontaneous by means of reports
or interrogated by the master station.
For the transmission of data between servers, the "GOOSE" transmission procedure can be
implemented.
9.2.4.1 Data Transmission Server <-> Client
The transmission of data ready to be sent from the master station (61850-Client) to the remote
terminal unit (61850-Server) takes place spontaneously with connection established and for
each connection.
The transmission of data ready to be sent from the remote terminal unit (61850-Server) to the
master station (61850-Client) takes place either spontaneous by means of 61850-Reports or
interrogated by the master station.
With the parameter IEC61850 | client | advanced parameters | IEC61850

service for request it is determined, whether the transmission of the data from the
remote terminal unit (61850-Server) to the master station (61850 Client) is carried out
spontaneously by means of reports or through cyclic interrogation by the master station.
With spontaneous transmission using reports, the spontaneous transmission is activated in

the Report Control Block of the 61850-Server by the protocol element with 61850-Client
function.
With transmission of the data through cyclic interrogation, the data attributes are interrogated
selectively by the protocol element with 61850-Client function (Report Control Block, Reports
and Data Sets are not used here).
The time-scale for the cyclic interrogation of the individual values can be parameterized with
the parameter IEC61850 | client | advanced parameters | acquisition grid
for "single read requests".
The possible 104-blocking for the data transmission between basic system element and
protocol element is not used.
The prioritization of the data ready to be sent by the basic system element (BSE) is of no
significance for the protocol element with 61850-Server function. The data is transferred from
the basic system element, entered in the IEC 61850 organized process image on the protocol
element and prepared for transmission according to IEC 61850.
The prioritization of the data ready to be sent by the basic system element (BSE) is only of
significance for the protocol element with 61850-Client function.

Edition 06.2017, DC0-023-2.12
9.2.4.1.1 Reports/Report Control Block
The spontaneous transmission of data from the 61850-Server to the 61850-Client takes place
by means of reports. The reports are created permanently in the servers and every report has
its own Report Control Block. The characteristics of the respective report are entered in the
Report Control Block. The Report Control Block can be read as well as written by the 61850-
Client.
The following information are stored in the Report Control Block: (extract-wise)
· Reference to the associated DataSet

· Trigger for the transmission (spontaneous, general interrogation,…)
· DataSet Name
· …
9.2.4.1.2 Unbuffered/Buffered Reports
For the reports, a distinction is made between Buffered Reports and Unbuffered Reports. This
function is determined by the 61850 device. With the Buffered Reports, changes are stored
after a connection failure.
After startup or going connection fault all the present Unbuffered/Buffered Control Blocks are
interrogated and the belonging Dataset is read (attribute “DatSet”). Predominantly, the
Unbuffered Control Block is used, only if no Unbuffered Control Blocks are present, Buffered
Control Blocks are used.
In the handling of the reports, on reception no distinction is made between Buffered reports
and Unbuffered reports by the SICAM RTUs protocol element with 61850 Client function.
As of 61850 Ed.2 the selection of reports can be defined with the parameter connection
definitions | Reports. With “unbuffered, buffered” and “buffered, unbuffered” both are
used with priority to the first selection. With “unbuffered”, “buffered” and “single read requests”
only the parameterized reports are used.
With the parameter connection definitions | Timeout buffered reports (s) a

time can be defined during that the “Buffered Report” will not be deleted after a connection
failure.
As of 61850 Ed.2, the automatic search of reports will be overruled with the table IEC61850
| client | advanced parameters | report definition.
Parameter Description
Station 0…99 (internal SICAM station)
Report name Name of the report (e.g. IEDPROT/LLN0$RP$urcb01
Note
The protocol element with 61850 Server function only supports “Unbuffered Reports”.

DC0-023-2.12, Edition 06.2017
9.2.4.1.3 Static/Dynamic Datasets
In the datasets, all information is contained that can be transmitted spontaneously from the
61850 Server to the 61850 Client. Required values that are not contained in the datasets,
must be read out from the 61850 Client by cyclic interrogation of the attributes.
Static datasets are predefined by the 61850 device and are created in the device by the
61850 Server function itself.
In SICAM RTUs devices, the static datasets are generated by the protocol element with 61850
Server function from the data of the SIP message address conversion in transmit direction.
Dynamic datasets must be created by the 61850 Client in the 61850 Server. In the
initialization phase, the protocol element with 61850 Client function reads out the information
from those devices with 61850 Server function, whether dynamic datasets are supported.
Dynamic datasets are generated by the protocol element with 61850 Server function from the
data of the SIP message address conversion in receive direction and created in the devices
with 61850 Server function.
With the parameter IEC61850 | client | advanced parameters | dataset it is

determined how the dynamic datasets are to be created.
The datasets can be created as follows:
· For each logical node

· For each logical device
As of 61850 Ed.2, the parameter connection definitions | dynamic datasets defines

whether the 61850 Server supports dynamic datasets. The count of elements for dynamic
datasets is defined with the parameter connection definitions | Elements for
datasets (typical: 60).
Note
The protocol element with 61850 Server function only supports static datasets.
Siemens protection devices of the SIPROTEC series support only dynamic datasets.
Protection devices of other manufacturers mostly support only static datasets.
9.2.4.1.4 Setting Group Control Model
Only with Logical Device “Protection” and Logical Node “LLN0” setting groups are supported.
Values of a SGCB are not transmitted spontaneously, but interrogated cyclically.
Attention:
Only a group switchover is possible (SelectActiveSG), no parameter settings.

Edition 06.2017, DC0-023-2.12
9.2.4.2 Data Transmission Server <-> Server with "GOOSE" [Server only]
The Generic Object Oriented Substation Events (GOOSE) is a transmission service of IEC
61850 for generic status events, that can be sent simultaneously per Multicast to multiple
devices in order to satisfy high real-time requirements. Typical cases of application are the
spontaneous transmission of state of switching device in the decentral interlocking of
switching commands in substations. GOOSE messages use the Ether type specification for
VLAN, the prioritization and are represented directly on the Ethernet layer.
With GOOSE messages according to standard part IEC 61850-8-1, data is exchanged
between IEC 61850 devices (servers).
Range for the Multicast address for GOOSE:
From To
MAC Address 01-0C-CD-01-00-00 01-0C-CD-01-01-FF
Max. 100 different GOOSE messages can be supported, whereby the number applies
conjointly in send and receive direction.
For the GOOSE data transmission, the IEC 61850 protocol element supports only basic types
(single elements) – data structures are not supported!
The GOOSE data transmission is supported by the server function of the protocol element in
transmit direction "Publisher" (transmitter) and also in receive direction "Subscriber" (receiver).
The datasets to be transmitted are defined with the process-technical parameterization of the
SIP message address conversion. The datasets must consist of data of the MMS directories.
The internal station number (from SSE to BSE) of the received GOOSE messages is 254
(own SSE). Hence results that Publish messages must be included in the send routing, and
Subscribe message in the receive routing.
GOOSE messages are transmitted with high priority by the switches implemented in 61850
networks. For this the switches must support the standard IEEE802.1Q (prioritization of
messages).
GOOSE Transmission Procedure

The GOOSE data transmission is a cyclic multicast transmission. A GOOSE message is
thereby transmitted from one device as "Publisher" (transmitter) and received by multiple
devices "Subscribers" (receivers).
With the GOOSE data transmission, the GOOSE message is transmitted spontaneously
immediately with change and then cyclic with changed cycle time (repeat time). The data
transmission is not acknowledged, the reception of the current state is ensured through the
repeat procedure.
The initial repeat time after a spontaneous GOOSE data transmission is 20 ms. This time is
doubled with each transmission until the parameterized maximum repeat time is reached.
The maximum repeat time for GOOSE messages is to be parameterized with the parameter
IEC61850 | server | Goose | max. repeat time for GOOSE messages.

DC0-023-2.12, Edition 06.2017
Settable Settable
20ms 40ms 80ms 160ms time scale time scale
Time scale
Send
GOOSE
Change
Spontaneous data change #1

in GOOSE data set
Settable Settable
20ms 40ms 80ms xx ms 20ms 40ms 80ms time scale time scale
Time scale
Send
GOOSE
Change
Spontaneous data change #1 Spontaneous data change #2

in GOOSE data set im GOOSE Dataset
Failure Monitoring
The failure monitoring for GOOSE messages in receive direction (Subscriber) is derived from
the current HOLD-Time (repeat time) per GOOSE application. The current HOLD-Time is also
included in every message of a GOOSE message.
The time for the failure monitoring is the current HOLD-Time multiplied by the parameterized
maximum number of retries for GOOSE. The maximum number of retries for GOOSE
messages is to be parameterized with the parameter IEC61850 | server | Goose |
Retry count for GOOSE.
After a failure is detected, the data concerned can be emulated by the protocol element to the
basic system element as failed ("not topical").
The selection of whether the data is to be emulated as failed, is set with the parameter
IEC61850 | server | Goose | Mark data invalid after GOOSE failure.
Note
If the emulation of the data concerned is deactivated on failure, the monitoring by the user function must
be ensured.

Edition 06.2017, DC0-023-2.12
Parameters for GOOSE Data
The configuration of GOOSE-data must be done exclusively using SICAM TOOLBOX II.
Only existing projects using GOOSE-data should be configured using process-technical
parameter setting of protocol element.
Data of the process-technical parameter setting (SIP message address conversion in

transmit/receive direction) can be selected for the GOOSE data transmission. All data with the
same "Goose-Index" are assigned to one GOOSE application.
The detail parameters for each GOOSE application (GOOSE-Index) are to be parameterized
in the system-technical parameters in the spreadsheet IEC61850 | server | Goose |
Goose Definition.
All data of a GOOSE application are transmitted with the parameterized multicast address.
The following parameters can be set in the goose definitions:
· "Enable"
A parameterized GOOSE application can be activated/deactivated with the parameter
IEC61850 | server | Goose | Goosedefinition | Enable.
e.g. this way GOOSE applications can be prepared, that are first activated at a later time
by means of parameterization.
· "Goose Index"
With the GOOSE Index, the data of the SIP message address conversion are assigned to
the GOOSE application.
The GOOSE Index is only used SICAM RTUs internal and is parameterized for each
GOOSE application with the parameter IEC61850 | server | Goose |
Goosedefinition | Goose Index.
· "Goose Control Block (gocbref)"
With the parameter IEC61850 | server | Goose | Goosedefinition | Goose
Control Block (gocbref) the reference to the GOOSE Control Block is
parameterized.
The GOOSE Control Block is generated by the protocol element for each GOOSE
application from the parameters of the goose definitions and can be read by the Client.
With the integrated web server, the GOOSE Control Block can be read out in the directory
of the server under the Functional Constraint "GO".
· "Goose Id (goid)
With the parameter IEC61850 | server | Goose | Goosedefinition | Goose Id
(goid) an unambiguous GOOSE identification is parameterized. The GOOSE
identification must be unambiguous in the network and is transmitted with the GOOSE
message.
· "Dataset Reference"
For every GOOSE application a specific dataset is created in the SICAM RTUs Server.
With the parameter IEC61850 | server | Goose | Goosedefinition | Dataset
Reference the reference to the dataset is to be parameterized for each GOOSE
application.
· "MAC-address"
Every GOOSE application is transmitted with Multicast to multiple devices as GOOSE
message. With the parameter IEC61850 | server | Goose | Goosedefinition |
MAC-address the multicast address (=MAC-address) is to be parameterized for each
GOOSE application.
The MAC-address is to be parameterized as character string without separating character.
Example: The multicast address 01-0C-CD-01-01-FF is to be parameterized with the
character string 010CCD0101FF.
· "AppId"
With the parameter IEC61850 | server | Goose | Goosedefinition | AppId the
application identification (AppId) of the GOOSE application is to be parameterized.

DC0-023-2.12, Edition 06.2017
· "configRev"
With the parameter IEC61850 | server | Goose | Goosedefinition |
configRev an unambiguous revision identifier of the GOOSE application is to be
parameterized. This revision identifier should be changed when the dataset of the GOOSE
application changes, so that no malfunction occurs in connected devices with incompatible
parameter setting.
Note: The check of the revision identifier can be switched on and off with a system-
technical parameter.
· "VLAN Vid"
With the parameter IEC61850 | server | Goose | Goosedefinition | VLAN Vid
the VLAN-ID (unambiguous number of the virtual LAN’s) is to be parameterized.
With virtual LAN's (VLAN's), on a physical LAN several virtual LAN’s are defined, which do
not mutually hinder each other and which also cannot receive or listen to the data traffic of
the other respective VLANs on the physical Ethernet phase.
To be able to screen and if necessary prioritize the data traffic of a virtual LAN against the
other network parties, the data packets must have a corresponding identification. For this,
the MAC-Frames are expanded with an additional feature (a “tag”). The corresponding
procedure is therefore also called “Frame-Tagging”.
The Tagging is realized with an additional field in the MAC-Frame.
In this field, two items of information essential for the virtual LAN are contained:
VLAN-ID: The virtual LAN is identified with an unambiguous number.
This ID determines the association of a data packet to a logical (virtual) LAN.
With this 12-bit value, up to 4094 different VLAN's can be defined
(the VLAN-IDs “0” and “4095” are reserved or not allowed).
Priority: The priority of a VLAN-identified data packet is flagged with a 3-bit value.
Thereby “0” stands for the lowest priority, the “7” for highest priority.
Data packets without VLAN-Tag are handled with the priority “0”.
· "VLAN priority"
With the parameter IEC61850 | server | Goose | Goosedefinition | VLAN
priority the priority for the data packets in the VLAN is to be parameterized.
General Notes to GOOSE
Attribute unambigous per

Network Device
GoCBRef ü ü
GoId ü ü
Dataset ü
MAC Address ü
AppId ü
configRev
VLAN Vid
VLAN Priority
The combination GoCBRef and GoId must be unambigous in the network.

Edition 06.2017, DC0-023-2.12
The Logical Nodes of the Goose receiver should be of the type GGIO:
Goose Publish: VL.C01/Q0CSWI1.Pos.stVal

VL.C01/Q0CSWI1.Pos.q
Goose Subscribe: VL.C02/Q0GGIO1.DPCSO1.stVal

VL.C02/Q0GGIO1.DPCSO1.q
Q0CSWI.Pos.stVal and Q0GGIO1.DPCSO1.stVal are both of the typa double-point

information. At the receiver (subscribe) a new data point is created (VL.C02). The quality
should be always transmitted.
Example of a valid GOOSE parameterization:
GoCBReg Go Dataset MAC AppId config VLAN VLAN

Id Rev Vid Priority
VL.C01/LLN0$GO$gcb01 1 VL.C01/LLN0$ds1 010CCD010000 1 1 1 4
VL.C01/LLN0$GO$gcb02 2 VL.C01/LLN0$ds2 010CCD010001 2 1 1 4
By means of this parameterization, in the VL.C01/LLN0 Logical Node a respective Goose

Control Block with the name gcb01 and gcb02 is created automatically, as far as they are
publish. Write accesses to the Goose Control Block do not have effect on the function of the
Goose messages. As well the created dataset is not readable.
According to the following table the attributes of the GGIOs must be assigned:
Basic Type Used as GGIO Attribute

BOOLEAN Single-point information SPCSO.stVal
CODED ENUM Double-point information DPCSO.stVal
FLOAT32 Measured value AnIn.mag.f
Quality Quality 1)
TimeStamp Real time 2)
1) additional attribute to single-point information, double-point information, measured value
2) additional attribute to single-point information, double-point information, measured value
station after the initialization of the connection or after the master station has detected a loss
of information.
connection) to the protocol element (server or client) and replied to by this directly from the
internal process image of the protocol element with the current time.
Handling of the General Interrogation in the 61850 Client

A general interrogation is only sent to the server by the protocol element with 61850 Client
function after startup or after going communication failure (connection failure) (GI-Bits in the
"Unbuffered Control Blocks").
Handling of the General Interrogation in the 61850 Server

The protocol element with 61850 Server function does not perform any general interrogation
towards the basic system element. A general interrogation triggered by the 61850 Client is
replied to by the protocol element with 61850 Server function directly from the internal process
image of the protocol element by means of "Unbuffered Reports".

DC0-023-2.12, Edition 06.2017
In networks and in systems with time-critical applications, a precise time is essential.
The clock synchronization for IEC 61850 can be performed in the following ways:
· Network Time Protocol (NTP V3) according to RFC 1305

· Simple Network Time Protocol (SNTP V3, V4)
Messages that are transmitted after a startup contain the
· current time, if the automation unit already has been synchronized previously
· relative time from startup (reference date), if the automation unit already has never been
synchronized
Reference date for SICAM RTUs: 1.1.2001
Reference date for Ax1703: 1.1.1997
In both cases, the time tag is marked as invalid until the first reception of the synchronizing
event.
9.2.6.1 Network Time Protocol (NTP)
For further details refer to chapter 12, NTP/SNTP.

Edition 06.2017, DC0-023-2.12
For the transmission of commands, the Common Data Classes expanded in the IEC 61850-8-
1 standard are used (see 9.6.2.5.1, Extended Common Data Classes). These expanded
Common Data Classes consist of several attributes that are all transmitted in one 61850
message.
The protocol element with 61850-Client function describes the attribute "Check" as last
attribute during the preparation of the command. The protocol element with 61850-Server
function only then processes the command further if the attribute "Check" is set.
Exception: With abortion of the command ("Cancel"), instead of the attribute "Check" the
attribute "Test" is used.
At the same time a maximum of 10 different commands can be executed simultaneously by

the protocol element with 61850 Client or Server function.
The transmission of commands for IEC 61850 is defined in the "Control Models" (settable in
the detailed routing):
IEC 61850 Control Model Data Attributes without Note

TimeActivatedOperate 2)
Direct with normal security Oper Only EXECUTE-command
Direct with enhanced security Oper Only EXECUTE-command
Select before operate with normal Select before operate (SBO) Only SELECT/EXECUTE-
security 1) Oper commands
Cancel
Select before operate with Select before operate (SBOw) Only SELECT/EXECUTE-
enhanced security Oper commands
Cancel
1) is not supported by the SICAM RTUs protocol element!
2) "Data Attributes with Time Activated Operate" are not supported by the protocol element!
The "Control Model" (ctlmodel) is determined by the 61850-Server and read out by the 61850-
Client in the startup phase.
With the Control Models "Direct With Enhanced Security" and "SBO With Enhanced Security"
the Termination is also transmitted and the Termination for IEC 60870-5-101/104 is derived
from this. With the other Control Models the Termination for IEC 60870-5-101/104 is derived
from the return information.
IEC 61850-7-2 Model/Services:
IEC 61850-7-2 Model IEC 61850-7-2 Service Note

Control Select
SelectWithValue
Cancel
Operate
CommandTermination
TimeActivatedOperate *)
*) is not supported by the SICAM RTUs protocol element!
The SICAM RTUs protocol element for 61850 performs the adaptation ("Mapping") of the
various command modes from IEC 60870-5-101/104 ó IEC 61850.
SICAM RTUs internal, the protocol element with 61850-Server function requests the
information ACTCON, ACTTERM and the return information with the cause of transmission =
"Return information caused by a remote command" (COT=11) for every command.

DC0-023-2.12, Edition 06.2017
A command is sent with the following attributes and sequence:
IEC 61850 Attribut Description

ctlVal Command status
origin.orCat Refer to 9.2.7.1.2, Causes of Transmission
(origin)
origin.orIdent
ctlNum Ascending number
T Current time
Test abhängig vom Test-Bit IEC 60870-5-101/104
Check Refer to the following table
9.2.7.1 Control Model
9.2.7.1.1 Command Output Time (QU)
Client
IEC 60870-5-101/104 QU IEC 61850 Check Meaning

9 00
0, all others 01 interlocking
10 10 synchrocheck
11 11 synchrocheck + interlocking
All commands with short, long and without definition are sent with "interlocking". Commands
that are generated from return information items are always sent without interlocking and
without synchrocheck ("00").
Optionally, the following transfer table can be implemented with the parameter advanced
parameters | compatibility mode = RWE:
IEC 60870-5-101/104 QU IEC 61850 Check Meaning

11 00
10, all others 01 interlocking
9 10 synchrocheck

Edition 06.2017, DC0-023-2.12
Server
IEC 61850 Check IEC 60870-5-101/104 QU Meaning

00 9
01 0 interlocking *)
10 10 synchrocheck
*) this is the typical command; the meaning of QU = 0 corresponds "without additional definition"
Optionally, the following transfer table can be implemented with the parameter advanced
parameters | compatibility mode = RWE:
IEC 61850 Check IEC 60870-5-101/104 QU Meaning

00 11
01 10 interlocking
10 9 synchrocheck
9.2.7.1.2 Causes of Transmission (origin)
Client
The causes of transmission are derived according to the following table.
IEC 61850 origin.orCat IEC 60870-5-101/104 COT

Not supported Spontaneous (3)
Bay control Local (12)
Station control Remote (11)
Remote control Remote (11)
Automatic bay Spontaneous (3)
Automatic station Spontaneous (3)
Automatic remote Spontaneous (3)
Process Spontaneous (3)
If a return information is transmitted without origin.orCat and if this is in a running command

sequence, even though the cause Remote (COT:=11) is enclosed.
Edition 1: Commands from Client to the Server are sebt with "remote control".
Edition 2: Commands from Client to the Server are sebt with "remote control", if the origin
address is < 128 and with "station control", if the origin address is >= 128.
The attribute orIdent is sent with the value "ET03: nnn.nnn.nnn.nnn Rxxx Kyyy Origin:zzz".
nnn.nnn.nnn.nnn = IP address
Rxxx = region number
Kyyy = component number
zzz = origin address from IEC 60870-5-101/104
The IEC 60870-5-101/104 origin address in receive direction is then set, if the orIdent attribute
contains the string "ET03" or "SAT 200" (value of Origin).

DC0-023-2.12, Edition 06.2017
Server
If a command was transmitted in direction Ax 1703 system, a timeout is started (parameter-
settable), and with arrival of the corresponding return information, the cause of transmission
(origin) is copied from CO to ST. With the next information report this is reported to the Client.
For this function a correlation between command aqnd return information is created via the
IEC 61850 address (detailed routing).
Status Behavior
Command running (no timeout) and return Copying of ctlNum, origin.orCat,
information has the cause 11 (remote) origin.orIdent
Return information has not the cause 11 origin.orCat = process
(remote) and not the cause 12 (local) origin.orIdent
Return information has the cause 12 (local) origin.orCat = bay-control
origin.orIdent
The IEC 60870-5-101/104 origin address is taken in receive direction from the origin.orIdent,
as far as this corresponds to the firmware of the 61850 protocol element (see 9.6.2.3.4, IEC
61850: Originator).
9.2.7.1.3 Command Termination
Client
For commands with "Enhanced Security", for the transmission of the information "Command
Termination" of the temporary information report "Command Termination" is used.
IEC61850 | client | advanced parameters | Terminations for commands (as of
61850 Ed.2: connection definitions | Termination) it can be selected whether the
"Termination of Activation" is to be derived from the "Command Termination" of 61850 or from
the return information itself for the conversion to IEC 60870-5-101/104.
For the evaluation/generation of the termination, a correlation is established by the protocol

element between command and return information via the 61850 address from the
parameters of the SIP message address conversion (ctlVal, stVal).
IEC61850 | client | Timeout IEC61850 Services (as of 61850 Ed.2: connection
definitions | Timeout IEC61850 Services) the monitoring time for 61850 Services
(e.g.: Read/Write) can be set. For commands, this monitoring time is extended to the time that
can be set with the parameter IEC61850 | Timeout Confirmation -> Termination (as
of 61850 Ed.2: connection definitions | Timeout CON → TERM (s)).
Server
For commands with enhanced security for Command Termination- the temporary information
report "Command Termination" is used.
The elements of the Command Termination- are "LastApplError" and "Oper". A Command
Termination+ contains only the element "Oper".

Edition 06.2017, DC0-023-2.12
9.2.7.1.4 1-Out-Of-n Check [Server only]
With 1-out-of-n check activated, only 1 command output procedure may be performed at one
time.
The SICAM RTUs protocol element with 61850-Server function can perform a 1- out-of-n
check either per connection (=station-selective) or per LAN interface (= globally for the LAN
interface).
The 1-out-of-n check is activated on the protocol element with 61850-Server function with the
parameter IEC61850 | server | 1 of n control.
9.2.7.1.5 Converting EXECUTE (104) à SELECT/EXECUTE (61850) [Client only]
The protocol element with 61850-Client function can convert IEC 60870-5-101/104 commands
with "direct command transmission" (EXECUTE only) for the transmission to the 61850
remote station to a "Select Before Operate with enhanced security" command. This is
necessary if no Select/Execute commands can be sent by the control system.
This function is activated on the protocol element with the parameter IEC61850 | client |
Convert commands EXE to SEL/EXE (as of 61850 Ed.2: connection definition |
Convert commands EXE to SEL/EXE).
With function activated the SELECT-command is transmitted immediately to the remote

station. After reception of the confirmation for the SELECT-command, the EXECUTE-
command is transmitted to the remote station after a settable delay. The delay time can be set
with the parameter IEC61850 | client | Delay between SEL CON - EXE ACT (as of
61850 Ed.2: connection definition | Delay SEL/EXE (ms)).
Note
SELECT/EXECUTE-commands (IEC 60870-5-101/104) cannot be converted to "Direct with normal
security" or "Direct with enhanced security" by the protocol element for the transmission to IEC 61850!
Step IEC 60870-5-101 Direction IEC 61850 ASCI Service

1 Execute Activation ® Select
2 ¬ Select Confirmation
3 ® Execute
4 Execute Confirmation ¬ Execute Confirmation
5 Execute Termination ¬ Execute Termination
Between step 2 and 3 a delay time can be parameterized (default = 0).

DC0-023-2.12, Edition 06.2017
9.2.7.1.6 LastApplError [Server only]
For commands with enhanced security for Res- a temporary information report
"LastApplError" is used. This information report is sent before the actual Res-.
Attribute Name Type Values

CntrlObj STRING65 *)
Error ENUMERATED · No Error

· Unknown
· Timeout Test Not OK
· Operator Test Not OK
Origin Originator
ctlNum INT8U
AddCause ENUMERATED · Unknown
· Not supported (Service Error)
· Blocked by switching hierarchy
· Select failed
· Invalid position
· Position reached
· Parameter change in execution
· Step limit
· Blocked by mode
· Blocked by process
· Blocked by interlocking
· Blocked by synchrocheck
· Command already in execution
· Blocked by health
· 1 of n control
· Abortion by cancel
· Time limit over
· Abortion by trip
· Object not selected
*) MMS name of the Control Object (e.g.: VL.C01/XCBR1$Mod$Oper)

Edition 06.2017, DC0-023-2.12
9.2.7.1.7 Monitoring
Client
The protocol element with 61850-Client function performs the following checks and monitoring
during the conversion of the commands from IEC 60870-5-101/104 ó IEC 61850.
· Timeout SELECT – EXECUTE

For SELECT/EXECUTE-commands, the protocol element with IEC 61850 Client function
monitors the time between IEC 60870-5-101/104 SELECT-command and the
IEC 60870-5-101/104 EXECUTE-command at the interface from the basic system
element. The monitoring time can be set with the parameter IEC61850 | Timeout
Select -> Execute (as of 61850 Ed.2: connection definition | Timeout SEL -
> EXE (s)).
If the monitoring time expires, a "negative confirmation of activation" (ACTCON-) is
transmitted to the basic system element by the protocol element for the IEC 60870-5-
101/104 EXECUTE-command and the command is not transmitted.
· Timeout ACTIVATION – CONFIRMATION
For commands, the protocol element with IEC 61850 Client function monitors the time
between the command transmitted to the 61850 remote station [Server] and the
CONFIRMATION received from the 61650 remote station. The monitoring time can be set
with the parameter IEC61850 | Timeout Activation -> Confirmation (as of
61850 Ed.2: connection definition | Timeout ACT -> CON (s)).
transmitted to the basic system element by the protocol element.
· Timeout CONFIRMATION – TERMINATION
For commands, the protocol element with IEC 61850 Client function monitors the time
between the CONFIRMATION received from the 61850 remote station [Server] for the
transmitted command and the TERMINATION received from the 61650 remote station.
The monitoring time can be set with the parameter IEC61850 | Timeout
Confirmation -> Termination (as of 61850 Ed.2: connection definition |
Timeout CON -> TERM (s)).
If the monitoring time expires, a "negative termination of activation" (ACTTERM-) is
transmitted to the basic system element by the protocol element.

DC0-023-2.12, Edition 06.2017
Server
The protocol element with 61850-Server function performs the following checks and
monitoring during the conversion of the commands from IEC 61850 ó IEC 60870-5-101/104.
· Timeout SELECT – EXECUTE

For "Select Before Operate" commands, the protocol element with IEC 61850 Server
function monitors the time between the SELECT-command received via IEC 61850 and
converted to IEC 60870-5-101/104 and the IEC 60870-5-101/104 EXECUTE (Operate)-
command.
The monitoring time can be set with the parameter IEC61850 | Timeout Select ->
Execute.
If the monitoring time expires, the EXECUTE-command is discarded by the protocol
element and a "negative confirmation of activation" (ACTCON-) is transmitted to the 61850
client.
· Timeout ACTIVATION – CONFIRMATION
For commands that have been converted from IEC 61850 to IEC 60870-5-101/104, the
protocol element with IEC 61850 Server function monitors that time between the
"Activation" (ACT) and the "Confirmation of Activation" (ACTCON) at the interface to/from
The monitoring time can be set with the parameter IEC61850 | Timeout Activation
-> Confirmation.
transmitted to the 61850 client by the protocol element.
· Timeout CONFIRMATION – TERMINATION
For commands that have been converted from IEC 61850 to IEC 60870-5-101/104, the
protocol element with IEC 61850 Server function monitors that time between the
"Confirmation of Activation" (ACTCON+) and the "Termination of Activation" (ACTTERM)
at the interface from the basic system element.
The monitoring time can be set with the parameter IEC61850 | Timeout
Confirmation -> Termination.
If the monitoring time expires, a "negative termination of activation" (ACTTERM-) is
transmitted to the 61850 client by the protocol element.

Edition 06.2017, DC0-023-2.12
9.2.7.1.8 Direct Control with Normal Security
Client

1 Command Execute, COT = 6 ® Operate Req.
2 Command Execute, COT = 7, PN = 0,1 ¬ Operate Res ±
3 Command Execute, COT = 10
The following steps are performed:
With reception of the command (COT:=6) on the protocol a timeout is started.
Check Behavior
More than 10 commands simultaneously Confirmation neg. (COT = 7, PN = 1)
Command already running Confirmation neg. (COT = 7, PN = 1)
"ctlModel" unequal 1,3 Confirmation neg. (COT = 7, PN = 1)
No Execute command Confirmation neg. (COT = 7, PN = 1)
If all checks are successful, the command is sent and a timeout for the Confirmation is started.
Evaluation for the Confirmation:
Check Behavior
Operate Res+ Confirmation pos. (COT = 7, PN = 0)
Operate Res- Confirmation neg. (COT = 7, PN = 1)
Timeout Confirmation neg. (COT = 7, PN = 1)
If a pos. Confirmation was generated, a timeout for the Termination is started.
If a return information was not parameterized, a pos. Termination is sent instantly after the
pos. Confirmation.
Evaluation for the Termination:
Check Behavior
belonging "stVal" changes Termination pos. (COT = 10, PN = 0)
Timeout Termination neg. (COT = 10, PN = 1)

DC0-023-2.12, Edition 06.2017
Server
Step IEC 61850 ASCI Service Direction IEC 60870-5-101/104

1 Operate Req ® Befehl Execute, COT = 6
2 Operate Res ± ¬
Check Behavior
Attribute not "Oper" Operate Res-
Command already running Operate Res-
1-out-of-n check Operate Res-
More than 10 commands simultaneously Operate Res-
xxx.Beh.stVal unequal 1, 3, 5 Operate Res-
The "Access Result" with Operate Res- is always "object-access-denied".
If all checks are successful, an Operate Res+ is sent and the command is forwarded
(COT:=6). The transmission of the actual command return information takes place after
step 2.
9.2.7.1.9 Direct Control with Enhanced Security
Client

3 Command Execute, COT = 10, PN = 0,1 ¬ Command Termination
Check Behavior
"ctlModel" unequal 1,3 Confirmation neg. (COT = 7, PN = 1)
Check Behavior
Operate Res+ Confirmation pos. (COT = 7, PN = 0)
Operate Res- Confirmation neg. (COT = 7, PN = 1)

Edition 06.2017, DC0-023-2.12
Check Behavior
Command Termination + Termination pos. (COT = 10, PN = 0)
Command Termination - Termination neg. (COT = 10, PN = 1)
Some devices do not send the Command Termination and the command return information in
the correct sequence, what results in a wrong command sequence according to
IEC 60870-5-101/104 (Termination, return information). To prevent this, by means of a
parameter can be defined that the Termination is generated by the command return
information and not by the Command Termination.
Server

1 Operate Req ® Command Execute, COT = 6
2 Operate Res± ¬ Command Execute, COT = 7, PN =
0,1
3 Command Termination± ¬ Command Execute, COT = 10, PN =
0,1
The Confirmation and Termination is monitored in each case with a parameter-settable

timeout.
Check Behavior
Attribute not "Oper" LastApplError Error = Operator Test Not OK
AddCause = Service Error
Operate Res-
1-out-of-n check LastApplError Error = Operator Test Not OK
AddCause = 1 of n control
Operate Res-
More than 10 commands simultaneously LastApplError Error = Unknown
Operate Res-
Command already running LastApplError Error = Operator Test Not OK
AddCause = Command already in execution
Operate Res-
xxx.Beh.stVal unequal 1, 3, 5 LastApplError Error = Operator Test Not OK
AddCause = Blocked by Mode
Operate Res-
If all checks are successful, the command is forwarded (COT = 6).

DC0-023-2.12, Edition 06.2017
For the evaluation of the Confirmation the entire MMS packet is temporarily stored and held
back as long as a pos. or neg. Confirmation is received from the BSE or a parameter-settable
timeout expires.
Check Behavior
Confirmation neg. (COT = 7, PN = 1) LastApplError Error = Operator Test Not OK
AddCause = Blocked by process
Operate Res-
Timeout LastApplError Error = Operator Test Not OK
AddCause = Time Limit Over
Operate Res-
Confirmation pos. (COT = 7, PN = 0) Operate Res+
The "Access Result" with Operate Res- is always "oject-access-denied".
The Command Termination± is created by the Termination (COT = 10):
Check Behavior
Termination neg. (COT = 10, PN = 1) LastApplError Error = Operator Test Not OK
Termination pos. (COT = 10, PN = 0) Command Termination+
The transmission of the actual command return information takes place between step 2 and 3.
9.2.7.1.10 SBO Control with Enhanced Security
Client

1 Command Select, COT = 6 ® Select with Value Req.
2 Command Select, COT = 7, PN = 0,1 ¬ Select with Value Res ±
5 Command Execute, COT = 10, PN = 0,1 ¬ Command Termination ±
Check Behavior
"ctlModel" unequal 4 Confirmation neg. (COT = 7, PN = 1)

Edition 06.2017, DC0-023-2.12
Check Behavior
Select with Value Res + Confirmation pos. (COT = 7, PN = 0)
Select with Value Res - Confirmation neg. (COT = 7, PN = 1)
If a pos. Confirmation was generated, a timeout for the Execute command is started.
Evaluation for the Execute command:
Check Behavior
Execute command has unequal address as the Confirmation neg. (COT = 7, PN = 1)
Select command
Timeout Enable command in the memory
Check Behavior
Operate Res + Confirmation pos. (COT = 7, PN = 0)
Operate Res - Confirmation neg. (COT = 7, PN = 1)
Check Behavior
Command Termination + Termination pos. (COT = 10, PN = 0)
Command Termination - Termination neg. (COT = 10, PN = 1)
Some devices do not send the Command Termination and the command return information in
the correct sequence, what results in a wrong command sequence according to
IEC 60870-5-101/104 (Termination, return information). To prevent this, by means of a
parameter can be defined that the Termination is generated by the command return
information and not by the Command Termination.
Termination of the Command (Deactivation COT = 8)
Check Behavior
Command is not running Deactivate Confirmation neg. (COT = 9, PN = 1)

DC0-023-2.12, Edition 06.2017
Server
Es wird nur ein SBO with Value (SBOw) supported.

1 Select with Value Req ® Command Select, COT = 6
2 Select with Value Res ± ¬ Command Select, COT = 7, PN =
0,1
3 Operate Req ® Command Execute, COT = 6
4 Operate Res ± ¬ Command Execute, COT = 7, PN
= 0,1
5 Command Termination ± ¬ Command Execute, COT = 10, PN
= 0,1
The Confirmation and Termination is monitored in each case with a parameter-settable

timeout. For Cancel exist an own Timeout+ counter.
The following steps are performed, if the written attribute is "SBOw":
Check Behavior
1-out-of-n check LastApplError Error = Operator Test Not OK
AddCause = 1 of n control
Operate Res-
Operate Res-
Command already running LastApplError Error = Operator Test Not OK
Operate Res-
Operate Res-
If all checks are successful, the command (Select) is forwarded (COT = 6).
timeout expires.
Check Behavior
AddCause = Select Failed
Operate Res-
Operate Res-

Edition 06.2017, DC0-023-2.12
The following steps are performed, if the written attribute is "Oper":
Check Behavior
more than 10 commands simultaneously LastApplError Error = Unknown
Operate Res-
Command not running LastApplError Error = Operator Test Not OK
AddCause = Object not selected
Operate Res-
Select forwarded and also already the Execute LastApplError Error = Operator Test Not OK
Operate Res-
Operate Res-
SBOw.ctlVal and Oper.ctlVal not equal LastApplError Error = Operator Test Not OK
Operate Res-
If all checks are successful, the command (Execute) is forwarded (COT = 6).
timeout expires.
Check Behavior
Operate Res-
Operate Res-
The Command Termination± is created by the Termination (COT = 10):
Check Behavior
Termination neg. (COT = 10, PN = 1) LastApplError Error = Operator Test Not OK
Termination pos. (COT = 10, PN = 0) Command Termination+
The transmission of the actual command return information takes place between step 4 and 5.

DC0-023-2.12, Edition 06.2017
The following steps are performed, if the written attribute is "Cancel":
Check Behavior
Operate Res-
Command not running LastApplError Error = Operator Test Not OK
AddCause = Object not selected
Operate Res-
Operate Res-
If all checks are successful, the command Deactivate Select is forwarded (COT = 8).
timeout expires.
Check Behavior
Operate Res-
Operate Res-
9.2.7.2 Control Location [Client only]
master station are only then transmitted to the remote terminal unit (remote station) if the
command format <TI:=45> which is converted on the basic system element to a PRE control
message (function 242: set control location) by the protocol control function. The control
location to be enabled/disabled is taken from the originator of the command message.

Edition 06.2017, DC0-023-2.12
9.2.7.2.1 Control Location Check
authority.
correspond with the control locations previously set.

the PRE.
9.2.7.2.2 Set Control Location

0 Not defined
Note
The selection of the control location and the generation of the spontaneous information object "Control
location" must be programmed in an application program of the open-/closed-loop control function.
enabled").
Due to an information object "Control location" with the single command state "OFF", all
originator addresses are deleted from the list of enabled control locations (="All control
locations not enabled").

DC0-023-2.12, Edition 06.2017

IEC 61850 does not define any counter concepts like IEC 60870-5-101/104. With IEC 61850
integrated totals can be transmitted as measured values. The transmission can be performed
either spontaneously with reports or through interrogation of the selective attributes.
9.2.9 File Transfer (Disturbance Records)
In 61850 protection equipment [Server] disturbance records are recorded and stored in the
protection equipment as files in IEEE-Comtrade format.
These files can be read out by the protocol element of the master station [Client] with the
procedures defined in IEC 61850 (ASCI-Service: File Transfer Model) and transferred to
SICAM DISTO for storage/evaluation.
The definition is done with the with the parameter IEC 61850 | Server | Disturbance
record | Disturbance record type (default IEC 61850).
In the system SICAM BC this parameter must be set to “IEC 60870-5-103”.
The transmission of disturbance records can be blocked, if the connected Server does not
support a file transfer (as of 61850 Ed.2: parameter connection definition | File
transfer).
Attention
A transmission of the disturbance records from the protocol element of the master station to a central
control system according to IEC 60870-5-101/104 "Transmission of files in monitoring direction
(disturbance record transmission of one protective device)" is presently not supported!
According to IEC 61850 the disturbance records are stored in the server in the file directory
"COMTRADE".
For each disturbance record the following files are created in this directory:
· Header-File (File-Extension .HDR)

general information about the station (ASCII)
· Configuration-File (File-Extension .CFG)
general info about the disturbance record (ASCII)
· Data-File (File-Extension .DAT)
Information of analog, digital channels (BINARY)
or optionally
· ZIP-File (File-Extension .ZIP)

all files of a disturbance record as ZIP-File (for each disturbance event a separate ZIP-file)

Edition 06.2017, DC0-023-2.12
The filename of the disturbance record file is not fixed, but normally contains the fault number
and possibly additional information for the identification of the fault or the station.
IEC 61850-7-2 Model IEC 61850-7-2 Service Note

FILE transfer GetFile
SetFile
DeleteFile
GetFileAttributeValues
9.2.9.1 Transfer of Disturbance Records to SICAM DISTO
With the 61850 protocol element [Client] disturbance records can be read out from 61850
devices [Server] and transferred to SICAM DISTO for storage/evaluation. Disturbance records
are stored by SICAM DISTO in the format transmitted by the protocol element either as single
files in IEEE Comtrade format (*.HDR, *,CFG, *.DAT) or as file in zipped format (*.ZIP).
The data transmission between the protocol element and SICAM DISTO is carried out with a
proprietary procedure for the transmission of files. The transmission of all necessary
information takes place with SICAM RTUs user data containers <TI:=142> in the private range
of IEC 60870-5-101/104.
For the transmission of disturbance records, a separate "channel“ is defined between the
protocol element and SICAM DISTO for every client with SICAM RTUs user data containers
(="disturbance record containers"). For each channel a SICAM RTUs user data container
(disturbance record container) in transmit direction (to SICAM DISTO) and a SICAM RTUs
user data container (disturbance record container) in receive direction (from SICAM DISTO) is
to be defined.
The assignment of the IEC 60870-5-101/104 message address for the spontaneous
information object "disturbance record container" is carried out in the OPM II in the master
station in the process-technical parameterization in transmit direction (to SICAM DISTO) with
the category firmware / Fault_record_Trans_IEC61850 and in receive direction (from SICAM
DISTO) with the category firmware / Fault_record_Rec_IEC61850.
Attention
Redundant configurations with SICAM DISTO are not supported!

DC0-023-2.12, Edition 06.2017
Configurations with SICAM DISTO
Control Center System

(host system) with SICAM DISTO
Data in 104 container (103 format)

AK driver/pko 61850 driver
IEC 60870-5-104 61850 file transfer (61850 format)

Station control device (proprietary mechanism)
SICAM AK or
SICAM TM
61850 file transfer (61850 format)
IEC 61850 IEC 61850

IEC 60870-5-103
Data in 103 format Data in 103 format
1 1 2 1 1 4
3 4
IEC 60870-5-103 IEC 60870-5-103
Parameterization in SICAM DISTO:

IEC 60870-5-103 or
1 IEC 60870-5-103 event list
2 IEC 61850 via IEC 60870-5-104 gateway
3 IEC 61850 file transfer

IEC 60870-5-103 via IEC 61850 file transfer or
4 IEC 60870-5-103 event list via IEC 61850 file transfer
9.2.9.1.1 Sequence of the Disturbance Record Transmission (between Client and

Server)
The file directory in the server is interrogated cyclic (every 3 minutes) by the protocol element
[Client] or spontaneously with a request from SICAM DISTO (e.g. with restart of SICAM
DISTO).
If the attribute "RcdMade" (RecordMade = "disturbance record has been created") of the
Logical Node "RDRE" (Disturbance Recorder Function) is available in the server, this can be
entered in the SIP message address conversion in receive direction.
With a change of the attribute to "TRUE" or with a change of the time, the protocol element
spontaneously executes an interrogation of the file directories of the server – as a result newly
stored disturbance records can be interrogated quickly and transmitted.
So that the transmission of spontaneous information is not delayed during a fault by the
transmission of disturbances records, the interrogation of the file directories by the protocol
element first takes place after a delay of 10 seconds.
After the transmission of a disturbance record has concluded or with cancelation of the
disturbance record transmission to SICAM DISTO, a renewed interrogation of the file
directories is performed automatically by the protocol element.

Edition 06.2017, DC0-023-2.12
IEC 61850 Protocol Communication

SICAM DISTO
element [Client] services
… cyclic or spontaneous
query of the file directory in
the server
… in case of a change in the

Dir ectory (Ty
file directory of the server pe=0)
File ready for
transmission
pe=4) Fetch selected file

Fetch file (Ty
File segment is read out from
the server File segmen
t (Type=1)
File segment
(Type=1)
Last segment
„Segment end
“ (Type=2)
nt (Type=5)
ement segme
Ackno wledg
Next file segment is read out
from ther server File segment
(Type=1)
File segment
(Type=1)
Last segment
„Se gment end“ (Ty
pe=2)
nt (Type=5)
ement segme
Acknowledg
Last file segment is read out
from ther server File segment
(Type=1)
File segment
(Type=1)
Last segment
„Se gment end“
(Type=3)
nt (Type=5) File completely transmitted

ment segme
Acknowledge
File transfer between protocol element and SICAM DISTO
9.2.9.2 Transmission of Disturbance Records [SICAM RTUs = Server]
Attention
The protocol element for 61850 [Server] does not presently support any transfer of disturbance records
according to IEC 61850!

DC0-023-2.12, Edition 06.2017

Routes
designed redundant.
In this section, not the possible redundancy concepts themselves that can be realized are
described, rather only those functions supported by the protocol element for the support of
redundant systems or communication routes.
The following redundancy modes are supported:
· Redundancy Mode "1703-Redundancy"

· Server Redundancy
· GOOSE Redundancy
All redundancy modes can use the additional functionality of dual-LAN interface (DNIP):
· Switch Mode
· Line Mode (Siemens specific)
· RSTP Mode
Using "Line Mode" or "RSTP" of dual-LAN interface (DNIP), redundancy concepts on Ethernet
level can be realized.
With the redundancy mode “1703-redundancy”, one remote terminal unit is connected with
one or several master stations over several logical connections. The data transmission takes
place over all connections.
Redundancy function of the standard redundancy mode:
· When using GOOSE in transmit direction (Publisher) special functions will be executed
during redundancy switchover to avoid failures in the connected devices (Subscriber).
(see section GOOSE Data Transmission [Server only] / GOOSE Redundancy)
· All data received from the LAN protocol element in the redundancy state "PASSIVE" are
marked by the basic system element in the message status with the redundancy status
"passive".
· The switchover to "PASSIVE" takes place globally per LAN protocol element and not
selectively per connection
Attention
Redundant configurations with SICAM DISTO are not supported!

Edition 06.2017, DC0-023-2.12
9.3.2 Server Redundancy
Special functions are implemented in the protocol element for the support of redundant
configurations of SICAM RTUs devices with 61850 Server function.
So that a fast switchover between the servers can be performed during redundancy
switchover from "PASSIVE ð ACTIVE", the connection to both 61850-Servers must be
established and the 61850-communication must be completely initialized.
The 61850-Client has no information about which 61850-Server is "ACTIVE". The

transmission of spontaneous data (Reports) is only carried out by the "ACTIVE" 61850-
Server.
After initialization is complete, the spontaneous transmission of data (Reports) is deactivated

by the protocol element of the "PASSIVE" 61850-Server.
Functions in the redundancy state "PASSIVE":
· Data in transmit direction continue to be received from the basic system and are entered
into the internal process image of the protocol element
· Spontaneous data and GI-data in transmit direction (Reports) are no longer transmitted by
the protocol element
· Data in receive direction continue to be passed on from the protocol element to the basic
system element and identified by this with the "PASSIVE-Bit".
Functions during the switchover from the redundancy state "PASSIVE" à "ACTIVE":
· The spontaneous transmission of data in transmit direction (Reports) is activated

· A general interrogation is carried out to the basic system element
Limitation:
The cyclic interrogation of attributes must not be used with server redundancy (this can lead to
inconsistent states in the client)!
The server redundancy is to be activated in the protocol element of the SICAM RTUs
component with 61850-Server function with the parameter IEC61850 | server |
Redundancy for Server.

DC0-023-2.12, Edition 06.2017
9.3.3 GOOSE Redundancy
For the support of redundant configurations of SICAM RTUs components with 61850 Server
function, special functions are implemented in the protocol element for the GOOSE message
transfer during transmission (Publisher), which prevent a possible failure of the GOOSE
messages at the receivers (Subscriber) in the connected devices during redundancy
switchover.
These functions are then required, if the same GOOSE applications are sent in the redundant
SICAM RTUs components.
GOOSE Application
Server Server Server Server

Publish Publish Subscribe Subscribe
Redundant Servers
For redundant devices with GOOSE Publisher function and the same parameterized GOOSE
applications (i.e. same MAC-address is used by different devices) always only 1 device may
be active at one time. The passive device stops the transmission of GOOSE messages.
The special functions for GOOSE redundancy are to be enabled with the parameter
IEC61850 | server | Goose | Redundancy for goose (Publish).
control messages.
Functions during the switchover from the redundancy state "ACTIVE" à "PASSIVE":
· All GOOSE applications are transmitted again by the server becoming passive (Publisher)
before the switchover with the "hold time in the message" (= 10 seconds), in order that all
Subscribe Servers do not detect a failure during a switchover. After that, the GOOSE
applications are switched off (Publish). As a result the failure monitoring time for GOOSE
applications is retriggered again in the connected devices before the switchover.
Functions in the redundancy state "PASSIVE":
· Transmission of GOOSE messages is stopped.

· 61850 Server + Client functions continue to be executed.

Edition 06.2017, DC0-023-2.12
Functions during the switchover from the redundancy state "PASSIVE" à "ACTIVE":
· After switchover, all GOOSE applications are only transmitted by the "ACTIVE" Server
(Publisher) after a delay time of 2 seconds.
Note
The "State Number" in the GOOSE message (change counter) is not synchronized between the redundant
devices. As a result, during redundancy switchover (without change of the data state) a change in
connected devices can be detected.
The "State Number" is not evaluated by the SICAM RTUs protocol element!
Procedure: switch passive/switch active
Basic System Element IEC 61850 Protocol Element
switch pa all GOOSE messages

ss ive
are sent
holdtime 10 s
ent
ledgem
acknow assive
p
switch
switch a
ctive
ent
ledgem
acknow ctive
a
general interrogation switch 2s
all GOOSE messages
are sent

DC0-023-2.12, Edition 06.2017
9.4 Dual-LAN interface (DNIP)
The dual-LAN interface (DNIP) is supported only by selected protocol element firmwares and
has a integrated "switch functionality" with 2 Ethernet interfaces (Port-0, Port-1).
The protocol element for dual-LAN interface (DNIP) can be used for specific configurations
(e.g. redundancy on Ethernet).
The dual-LAN interface (DNIP) can also be used as single LAN-Interface (e.g. as a
preparation for later use with Line- or RSTP-Mode).
Note
The dual-LAN interface has only 1 IP-address (the ports P0, P1 of the integrated switch do not have an
own IP-address).
When using dual-LAN interface (DNIP) there is only one protocol element (IEC 61850) supporting either
P0 interface or P1 interface (but not both at the same time)! That means, that the dual-LAN interface can
be used only in specified supported configurations, bot not be used for IEC 61850 with 2 independent
parallel working interfaces!
Schematic configuration of dual-LAN interfaces (DNIP):
P0 P1
Switch
MAC-address
LAN/WAN protocol elelemt
The operating mode for the dual-LAN interface (DNIP) can be set with the parameter
advanced parameters | DNIP (Dual Ethernet NIP) | operation mode.
Operation modes for dual-LAN Interface (DNIP):
· Switch Mode [Default] *)

· Line Mode *)
· RSTP Mode *)
· Single Mode
· Single + Service Mode
*) see also section 9.3, Function for the Support of Redundant Communication Routes
on the Ethernet is to be determined for each individual port for all operation modes using dual-
LAN interface (Dual Ethernet NIP) with the parameter advanced parameters | DNIP
(Dual Ethernet NIP) | Ethernet speed and duplex | Port# ethernet speed
and duplex.

Edition 06.2017, DC0-023-2.12
Requirements for configuration of protocol elements on BSE:
PRE Note
SSE = 129 Protocol element (IEC 61850) using dual-LAN interface (Port-0 + Port-1)
SSE = 131 Protocol element (IEC 61850) using dual-LAN interface (Port-0 + Port-1)
*) the dual-LAN interface (DNIP) use both RJ45 interface connectors – therefore no additional serial
interface using SM-0551 can be used in combination with DNIP
Cross Over
For the operating mode Switch or RSTP mode, each port of the DNIP can be set individually
to "Cross Over" by the protocol element. So standard network cables (LAN) can be used for
connecting to the next device (…it is not necessary to use Cross Over cables!)
The Function for "Cross Over" can be set with the parameter advanced parameters |
DNIP (Dual Ethernet NIP) | Crossover | Port# crossover.
The default setting is "standard" (=no Cross Over).
9.4.1 Switch Mode
The dual-LAN interface (DNIP) with operating mode "Switch Mode" will be used often in
configurations where only one additional device has to be connected to LAN network. When
using DNIP in 1703, no additional external switch is required in this configurations.
Switch
Network
P0 P1
DNIP 3rd Party

device
1703
In the operation mode "Switch Mode" all Ethernet frames will forwarded to all ports of DNIP
(also internal port to protocol element) and in all directions by the integrated switch.
Switch Mode (overview):
· Received Ethernet frames including the MAC-address of the DNIP will be forwarded to
DNIP for processing
· Received Ethernet frames not including the MAC-address of the DNIP will be forwarded to
the other port by integrated switch
· Ethernet frames to be sent by DNIP will be sent from the integrated switch via the port
which has already learned the MAC-address of the remote station
· Received Ethernet frames (BROADCAST) will be forwarded by integrated switch to DNIP
for processing and retransmitted on the other port
· Ethernet frames (BROADCAST) to be send from DNIP will be sent from the integrated
switch via all ports

DC0-023-2.12, Edition 06.2017
Note
The forwarding of the data to the ports will by done by the DNIP's integrated switch hardware and not by
the firmware of the protocol element.
The status of the ports in "Switch Mode" can be monitored with the integrated web server.
Status information for Switch Mode:

· "Autonegotiation"
Automatic negotiation of the speed of the link (10/100 Mbit) and full-/half-duplex.
· "Link"
· "Speed"
10 Mbit or 100 Mbit
· "Duplex-Mode"

Edition 06.2017, DC0-023-2.12
9.4.2 Line Mode (Siemens specific)
The dual-LAN Interface (DNIP) with the operation mode "Line Mode" will be used in
redundancy configurations on Ethernet level. The protocol element controls the function of the
integrated switch – only one port of the DNIP will be switched to "Forwarding".
Line Mode (overview):
· Data-link-layer (layer-2) is always established for both port's.

· The forwarding of the Ethernet frames will be done only on the port set to "forwarding".
The other Ethernet port is set to "blocking".
· The protocol element controls the function of the ports for the forwarding of the Ethernet
packages:
- "blocking"
- "forwarding"
(default settings: port-0 = "forwarding", port-1 = "blocking")
In case of failure of the Ethernet connection ("link down" of the port set to "forwarding") the
protocol element will set immediately the failed port to "blocking" and the other port to
"forwarding".
Switch
Switch
Network
Switch
Switch
Control of the Switches i LAN with RSTP

P0 P1
logical connection for P0+P1 = OK
DNIP
logical connection for P0 = NOK
1703 LAN by switch „opened“
(controled by RSTP)
After the activation of a port of the DNIP-interface (= switch to "forwarding"), specific Ethernet
frames will be sent by protocol element to enable a fast learning of the new route to access
the MAC-address of the DNIP for the switches in the network. The used procedure is Siemens
specific (proprietary) with special Ethertype for Ethernet frames.

DC0-023-2.12, Edition 06.2017
The actual status of the ports in "Line Mode" can be monitored with the integrated web server.
Status information for Line Mode:

· "Autonegotiation"
Automatic negotiation of the speed of the link (10/100 Mbit) and full-/half-duplex.
· "Link"
· "Speed"
10 Mbit or 100 Mbit
· "Duplex-Mode"
· "Port Status"
Forwarding ………Forwarding of Ethernet frames is enabled
Blocking ………… Forwarding of Ethernet frames is blocked
9.4.3 RSTP Mode
The Rapid Spanning Tree Protocol (RSTP) is a standardized network protocol for redundancy
control of backup links in network with fast enabling/disabling of backup links.
The RSTP protocol is used for disabling redundant backup links in local network and if
necessary to enable backup links in case of failure of a link. .
The maximum number of switches in a network will be calculated on the basis of the RSTP
timer for "max age": max. number of switches = max age - 1. This means that in a ring
topology maximal 39 devices can be connected.
The RSTP-Protocol is defined in the standard IEEE 802.1D, Edition 2004.

Edition 06.2017, DC0-023-2.12
9.4.4 Single Mode
The DNIP operating mode "single" use only LAN-interface with port-0 for the communication
with other remote systems.
The LAN-Interface with Port-1 will be deactivated by the protocol element and can not be used
(no monitoring / no diagnostic / no LED's for LAN-Interface Port-1!).
Note
The dual-LAN interface (DNIP) with operating mode "Single Mode" can be used as a preparation for later
use with Line, Switch or RSTP Mode.
9.4.5 Single + Service Mode
The DNIP operating mode "Single + Service Mode" use only LAN-interface with port-0 for the
communication with other remote systems.
The LAN-Interface with Port-1 can be used only as connector for network service access; also
analyzing of network data transfer on Port-0 using WireShark is supported (data from Port-0
will "mirrored" to Port-1) (no monitoring / no diagnostic for LAN-Interface Port-1 (Link down);
LED's will be displayed)!
Note
The dual-LAN interface (DNIP) with operating mode "Single + Service Mode" can be used as a
preparation for later use with Line, Switch or RSTP-Mode.

DC0-023-2.12, Edition 06.2017

· ---
Block Diagram
Protocol element
control
Internal
Transmission route
function
Protocol element


Edition 06.2017, DC0-023-2.12
system element enables specific functions of the protocol elements to be controlled. The
specific functions are determined by the protocol element implemented.
message.
Possible Client functions

SF Station Z-Par Fl
START connection to server
START connection to
128 0 – 99 - (“Initiate“) controlled by
server (Initiate)
61850 client à 61850 server
STOPT connection to server
(“conclude“) controlled by
STOP connection to 61850 client à 61850 server.
129 0 – 99 -
server (conclude) Note:
present station fault will not be
changed.
Send (general)
240 - - system message and not using PRE-
control message! CASDU =
BROADCAST
Send (general) This function is processed on the BSE
interrogation command and not sent to the protocol element as
for GI-group to own BSE 241 - - PRE-control message!
(=simulate received general
interrogation command for GI
group) 1)

65535
(all stations)
125
65535
(HKA) (all stations)
65535
(selective station)
0…99
65535
(HKA) (selective station)
Send (general) and sent to the protocol element as
244 - CASDU
interrogation command system message and not using PRE-
control message! CASDU = selective

DC0-023-2.12, Edition 06.2017

- Set control location function requires “additional parameter_(PRE)” (=Z-Par) = 65535 in
BSE’s PST-detail routing.
- If a PRE-control message for "set control location" is included in the PST-detailed routing on the
BSE, the BSE will send a PRE-control message "Set control location" with
additional parameter = 65535 after startup of the PRE to enable control location function on
PRE.
- The control location (HKA) to be enabled/disabled is taken by the BSE firmware from the
originator of the command message used as PST control message and sent to PRE as
PRE control message with additional parameter set as follows:

Legend:

0 – 99 = station 0 - 99 of the selected protocol element
125 = all station of the selected protocol element (=GLOBAL)
Z-Par.......... Additional parameter_(PRE)
Fl ................ Edge

Edition 06.2017, DC0-023-2.12
Presently the LAN protocol element does not support any protocol return information
messages!

DC0-023-2.12, Edition 06.2017
9.6.1 General
Data in control direction are transferred from the basic system element to the protocol element
in the SICAM RTUs internal IEC 60870-5-101/104 format (unblocked). These are entered by
the protocol element in the internal IEC 61850 data model. The data transmission from this
data model takes place according to IEC 61850.
Data in monitoring direction are received by the protocol element according to the IEC 61850
transmission procedure and converted by the protocol element to the internal
IEC 60870-5-101-/104 format and then passed on to the basic system element.
The address conversion from IEC 60870-5-101/104 ó IEC 61850 (address and message
format) takes place in the SICAM TOOLBOX II with the "SIP Message Address Conversion".
The "Mapping" of IEC 61850 attributes to IEC 60870-5-101/104 type identifications takes
place through the parameterization of the address conversion.
In the SIP message address conversion the following categories are available:
SICAM RTUs Protocol Element with 61850 Client Function

firmware / ET03/Client_Trans_IEC61850
firmware / ET03/Client_Rec_IEC61850
firmware / ET03/Fault_record_Trans_IEC61850
firmware / ET03/Fault_record_Rec_IEC61850
SICAM RTUs Protocol Element with 61850 Server Function

firmware / ET03/Server_Trans_IEC61850
firmware / ET03/Server_Rec_IEC61850
firmware / ET03/Server_Trans_Goose_IEC61850 *)
firmware / ET03/Server_Rec_Goose_IEC61850 *)
firmware / ET03/Server_Trans_default_value_IEC61850 *)
*) only Edition 1
Client
In receive direction, with a change of state/time/quality, data is converted from IEC 61850 to
IEC 60870-5-101/104 and transferred to the basic system element.
On reception of data, the following time information is taken for the message conversion:
· Time of the ".t" attribute has changed since the last transmission
à Time of the ".t" attribute is applied
· Time of the ".t" attribute has not changed since the last transmission, time of the report is
available (=time of the creation of the report in the server)
à Time of the report is applied
· Time of the ".t" attribute has not changed since the last transmission, time of the report is
not available (=time of the creation of the report in the server)
à Current time is applied

Edition 06.2017, DC0-023-2.12
Note
A general interrogation is always replied to by the protocol element from the internal process image of the
protocol element with the actual time.
Server
When data change, with IEC 61850 all attributes of the same "Functional Constraint" group
are always transmitted. If for instance the binary information state "stVal" changes from Pos,
then the other data attributes of the same Functional Constraint (ST = Status Information)
such as for instance "q" and "t" are also transmitted, even if these have not changed.
9.6.2 Conversion IEC 60870-5-101/104 ↔ IEC 61850
9.6.2.1 IEC 61850: Basic Types
Name Range
BOOLEAN TRUE (1), FALSE (0)
INT8 -128 to +127
INT16 -32768 to + 32767
INT24 -8388608 to +8388607
INT32 -2147483648 to +2147483647
127 127
INT128 -2 to + 2 -1
INT8U 0 to 255
INT16U 0 to 65535
INT24U 0 to 16777215
INT32U 0 to 4294967295
FLOAT32 IEEE 754
FLOAT64 IEEE 754
ENUMERATED Enumeration
CODED ENUM Enumeration
OCTET STRING String
VISIBLE STRING String

DC0-023-2.12, Edition 06.2017
9.6.2.2 IEC 61850: Common ACSI Types
9.6.2.2.1 IEC 61850: Time Quality
IEC 61850 IEC 60870-5-101/104 Supported

Attribute Name Type Values Ed.1 Ed.2
LeapSecondsKnown BOOLEAN 1)
ClockFailure BOOLEAN CP56Time2a IV ü ü

ClockNot BOOLEAN CP56Time2a IV ü ü 2)
Synchronized
TimeAccuracy CODED ENUM significant bits in 1 ms resolution matches ü ü
FractionOfSeconds approx. 10 bits
1) applies only for Server
2) applies only in receive direction
Edition 2: applies only for Client
9.6.2.2.2 IEC 61850: Time Stamp

SecondsSinceEpoch INT32 Seconds since CP56Time2a ü ü
01.01.1970 00:00
FractionOfSeconds INT24U 1 / 16777215 second CP56Time2a ü ü
fraction
TimeQuality TimeQuality ü ü
The time format is UTC time. Weekday and daylight-saving time flag (SU) are not considered.

Edition 06.2017, DC0-023-2.12
9.6.2.3 IEC 61850: Common Data Attribute Types
9.6.2.3.1 IEC 61850: Quality

validity CODED ENUM good NT = 0 ü ü
invalid NT = 1
reserved
questionable IV
detailQual PACKED LIST
overflow BOOLEAN OV 1) 2) ü ü
outOfRange BOOLEAN 3) ü ü
badReference BOOLEAN
oscillatory BOOLEAN
failure BOOLEAN
oldData BOOLEAN
inconsistent BOOLEAN
inaccurate BOOLEAN
source CODED ENUM · process SB = 0 ü ü
· substituted SB = 1
test BOOLEAN T ü ü
operatorBlocked BOOLEAN BL ü ü
1) applies only for Client: CY with TI 37; if only the OV bit of detailQuality is set, then the NT resp. IV bit is reset;
further the OV bit is set with TI 34, TI 35, if the value is out of the valid range of the respective type identification
(TI 34: -1 to +1, TI 35: -32768 to +32767)
2) applies only for Server: with OV = 1 validity is set to invalid additionally
3) applies only for Client: all these bits are ORed to the IV bit
9.6.2.3.2 IEC 61850: AnalogueValue

i INT32 ü
f FLOAT32 ü ü
9.6.2.3.3 IEC 61850: Vector

mag AnalogueValue ü ü
ang AnalogueValue

DC0-023-2.12, Edition 06.2017
9.6.2.3.4 IEC 61850: Originator

orCat ENUMERATED not-supported see Common Data ü ü
bay-control Classes
station-control
remote-control
automatic-bay
automatic-station
automatic-remote
process
orIndent STRING64 see Text ü 1) ü
D 2)
1) applies only for Client
Description of the originator: refer to Error! Reference source not found..
Server
The attribute "orIndent" is set to the fixed value "ET03: nnn.nnn.nnn.nnn Rxxx Kyyy
Origin:zzz" upon change of the datapoint due to a event (spontaneous).
nnn.nnn.nnn.nnn = IP address
Rxxx = Region number
Kyyy = Component number
zzz = Origin address from IEC 60870-5-101/104
Logging of the Remote Commands in the Local Control:
In order to log remote commands in the local control, all remote commands must be sent
additionally to the local control. However, this is according to IEC 61850 (Client/Server) not
possible.
To be able to use this function anyway, the orIdent attribute of the return information is used
thereto. This function is only then possible, if commands have a return information (coherence
between ctlVal and stVal).
Example: VL.C01/XCBR1.Pos.ctlVal (command)

VL.C01/XCBR1.Pos.stVal (return information)
All Activation, Confirmation, Termination messages are indirectly via a change of the orIdent
attribute spontaneous transmitted, whereby the state, the quality and the time of the return
information do not change (no change of the information state).
ET03LOG: COT:cccb Value:d Origin:zzz
ccc = Cause of transmission (6, 7, 10)

b = "P" for positive, "N" for negative
d = Data TI 45, 46: "0" = OFF, "1" =ON
TI 47: "0" = LOWER, "1" = HIGHER
TI 49, 50: decimal value (- 12, 12.3, 1.2E-2)
zzz = Origin address of the command

Edition 06.2017, DC0-023-2.12
Note
This function is for CDC's of the type INC (Ed.1) or ENC (Ed.2) (e.g. Mod.ctlVal) not available if the single
states are not splitted to different single resp. double commands. In this case the first found command is
used in the SIP message address conversion for the logging.
Example:
Remote Control Client Local Control Client
2, 3, 4, 5, 6, 7 2, 4, 5, 7
Bay Server
1...Remote command activation

2...Logging remote command activation
3...Remote command confirmation
4...Logging remote command confirmation
5...Return information
6...Remote command termination
7...Logging remote command termination
9.6.2.3.5 IEC 61850: Step position with transient indication

posVal INT8 -64…+63 VTI ü ü
transInd BOOLEAN VTI ü ü *)
*) for transInd a single-point information (TI 30) can be generated in the Client

DC0-023-2.12, Edition 06.2017
9.6.2.4 Common Data Classes
Client Transmit Direction → Server Receive Direction

Server Transmit Direction ← Client Receive Direction
The IEC 60870-5-101/104 cause of transmission (COT) is not considered with the conversion
to Common Data lasses. Controllable Common Data Classes are thereby an exception and
the conversion is described there.
In the column “Rout” (routing SICAM TOOLBOX II) is marked which attribute must be used for
the routing. Thereby, upon ambiguousness the corresponding IEC 60870-5-101/104 type
identifications are given.
Client Receive Direction ← Server Transmit Direction

All messages in direction IEC 61850 → IEC 60870-5-101/104 are transmitted to the Ax 1703
system with COT = 3 (SPONTANEOUS). The origin address is set to 0.
If data is received, with that the time is not written, this data is time tagged with the
SICAM RTUs time.
Server Receive Direction ← Client Transmit Direction

All messages in direction IEC 61850 → IEC 60870-5-101/104 are transmitted to the Ax 1703
system with COT = 6 (ACT), as far as they are CO (otherwise COT = 3). The origin address is
set to 0, except the Client runs the same firmware.
If data is received, with that the time is not written, this data is time tagged with the
SICAM RTUs time.

Edition 06.2017, DC0-023-2.12
Overview of the Supported Formats
IEC 61850 Common Data Class FC IEC 60870-5-101/104 1) Cs Sr Cr Ss SsG SrG

[CDC]
<TI=30> Single-point information
ü ü
CO
Controllable Single <TI=45> Single command
SPC ü ü
Point <TI=46> Double command
ST <TI=30> Single-point information
ü ü ü ü
ü ü
CO
Controllable Double <TI=45> Single command
DPC ü ü
Point <TI=46> Double command
ü ü ü ü
ü
<TI=45> Single command
ü ü
CO <TI=46> Double command
<TI=49> Setpoint command, scaled 2)
Controllable Integer
INC <TI=50> Setpoint command, floating ü ü
Status
point 2)
ü ü ü
ST
<TI=35> Measured value, scaled 2)
ü ü ü
<TI=36> Measured value, floating point 2)
ü 3)
<TI=45> Single command
ü 3)
CO <TI=46> Double command
Controllable
ENC <TI=50> Setpoint command, floating ü 3)
Enumerated Status
point 2)
ü 3)
ST
ü 3)
CO <TI=50> Setpoint command, floating ü 3) ü 3)
Controllable point 2)
APC
Enumerated Status
ST ü 3) ü 3)
SPS Single-Point Status ST <TI=30> Single-point information ü ü ü ü
DPS Double-Point status ST <TI=31> Double-point information ü ü ü ü
ü ü ü
INS Integer Status ST
ü ü ü
ü 3) ü 3) ü 3)
ENS Enumerated Status ST
ü 3) ü 3) ü 3)

DC0-023-2.12, Edition 06.2017

[CDC]
ST <TI=30> Single-point information ü ü ü ü
<TI=38> Protection event
Protection Activation <TI=39> Blocked activation of the
ACT
Information protection ü ü ü ü
<TI=40> Blocked triggering of the
protection
ST <TI=30> Single-point information ü ü ü ü
<TI=31> Double-point information ü
Directional Protection <TI=38> Protection event
ACD
Activation Information <TI=39> Blocked activation of the
protection ü ü ü ü
<TI=40> Blocked triggering of the
protection
ü ü ü
ü ü
Setting Group Control
SGCB SP <TI=45> Single command
Block ü ü
<TI=46> Double command
<TI=50> Setpoint command, floating ü ü
point 2)
BCR Binary Counter Reading ST <TI=37> Integrated totals ü ü
Binary Controlled Step ü ü
BSC <TI=32> Step position information 2)
Position
CO <TI=47> Regulating step command ü ü
ü ü
<TI=32> Step position information 2)
Integer Controlled Step
ISC <TI=49> Setpoint command, scaled 2)
Position
CO <TI=50> Setpoint command, floating ü ü
point 2)
ü ü 3)
<TI=36> Measured value, floating point
ASG Analogue Setting SP <TI=49> Setpoint command, scaled 2)
<TI=50> Setpoint command, floating ü ü 3)
point 2)
ü ü 3)
ING Integer Setting SP <TI=49> Setpoint command, scaled 2)
<TI=50> Setpoint command, floating ü ü 3)
point 2)
<TI=34> Measured value, normalized
MV Measured Value MX <TI=35> Measured value, scaled ü ü ü ü
Complex Measured
CMV MX <TI=35> Measured value, scaled ü ü ü ü
Value
SAV Sampled Value MX <TI=35> Measured value, scaled ü ü ü ü
Collection Of
WYE MX <TI=35> Measured value, scaled ü ü ü ü
Measurands
DEL Delta MX <TI=35> Measured value, scaled ü ü ü ü

Edition 06.2017, DC0-023-2.12

[CDC]
SEQ Sequence MX <TI=35> Measured value, scaled ü ü ü ü
DPL Device Name Plate only used on the protocol firmware ü
Logical Node Name only used on the protocol firmware
LPL ü
Plate
1) all with time mark CP56Time2a; only TI 30 and TI 31 are GI capable
2) for this values a measured value adaption (scaling) is not supported
3) applies only for Edition 2
Legend:
FC ........ Functional constraint

Cs ........ Client transmit direction
Sr ......... Server receive direction
Cr ......... Client receive direction
Ss ........Server transmit direction
SsG ...... GOOSE Server transmit direction
SrG ....... GOOSE Server receive direction
Note
As shown in the following tables, edition 2 applies only for the IEC 61850 Client.

DC0-023-2.12, Edition 06.2017
9.6.2.4.1 IEC 61850: Controllable Single Point (SPC)
IEC 61850 IEC 60870-5-101/104 Supported Rout

Attribute name Type FC Values Ed.1 Ed.2
ctlVal BOOLEAN CO TI 30: SPI 1) ü ü TI 30
TI 31: DPI 1) TI 31
TI 45: SCS 1) TI 45
TI 46: DCS 1) TI 46
operTim TimeStamp CO
origin Originator CO refer to 9.2.7.1.2, ü ü
ST Causes of
Transmission (origin)
ctlNum INT8U CO ü ü
ST
stVal BOOLEAN ST TI 30: SPI 2) 3) ü ü TI 30
TI 31: DPI 2) 3) TI 31
q Quality ST TI 30: SIQ 2) 3) ü ü
TI 31: DIQ 2) 3)
t TimeStamp ST CP56Time2a 2) 3) ü ü
stSeld BOOLEAN ST TI 30: SPI 2) ü TI 30
subEna BOOLEAN SV
subVal BOOLEAN SV
subQ Quality SV
subID STRING64 SV
pulseConfig PulseConfig CF
ctlModel ENUMERATED CF status-only 4) settable in the detailed ü
direct-with- routing 5)
normal-security
direct-with-
enhanced-sec.
sbo-with-
enhanced-sec.
sboTimeout INT32U CF
sboClass STRING256 CF
d STRING256 DC
dU USTRING256 DC
cdcNs STRING256 EX
cdcName STRING256 EX
dataNs STRING256 EX
1) applies only for Client in transmit direction und Server in receive direction
2) applies only for Client in receive direction und Server in transmit direction
3) receive direction: from these attributes a single-point information (TI 30) or double-point information (TI 31) can
be generated; the double-point information has only the state ON or OFF
4) Server in transmit direction: status only is only then set, if no CO is present

Edition 06.2017, DC0-023-2.12
9.6.2.4.2 IEC 61850: Controllable Double Point (DPC)

ctlVal BOOLEAN CO TI 30: SPI 1) ü ü TI 30
TI 31: DPI 1) TI 31
TI 45: SCS 1) TI 45
TI 46: DCS 1) TI 46
ST Causes of
ST
stVal BOOLEAN ST TI 30: SPI 2) 3 4) ü ü TI 30
TI 31: DPI 2) 3 TI 31
q Quality ST TI 30: SIQ 2) 3 ü ü
TI 31: DIQ 2) 3
t TimeStamp ST CP56Time2a 2) 3) ü ü
subEna BOOLEAN SV
subVal BOOLEAN SV
subQ Quality SV
subID STRING64 SV
pulseConfig PulseConfig CF
normal-sec.
direct-with-
enhanced-sec.
sbo-with-
enhanced-sec.
d STRING256 DC
dU USTRING256 DC
cdcNs STRING256 EX
dataNs STRING256 EX
3) receive direction: from these attributes a single-point information (TI 30) or double-point information (TI 31) can
be generated; with a single-point information the status DIFF and FAULT is not converted
4) with parameter IEC61850 value, from the AddCauses included in the neg. command termination, single-point
information items (TI 30) can be generated (only “coming” information); IEC61850 value = 100 + AddCause
5) Server transmit direction: status only is only then set, if no CO is present

DC0-023-2.12, Edition 06.2017
9.6.2.4.3 IEC 61850: Controllable Integer Status (INC)

ctlVal INT32 CO TI 30: SPI 3) ü ü TI 30
TI 31: DPI 3) TI 31
TI 45: SCS 1) 4) 5) ü ü TI 45
TI 46: DCS 1) 4) 5) TI 46
TI 49: SVA 1) TI 49
TI 50: R32-IEEE 1) TI 50
ST Causes of
ST
stVal INT32 ST TI 30: SPI 2) 4) 5) ü ü TI 30
TI 31: DPI 2) 4) 5) TI 31
TI 35: SVA 2) TI 35
TI 36: R32-IEEE 2) TI 36
q Quality ST TI 30: SIQ 2) ü ü
TI 31: DIQ 2)
TI 35: QDS 2)
TI 36: QDS 2)
t TimeStamp ST CP56Time2a 2) ü ü
subEna BOOLEAN SV
subVal INT32 SV
subQ Quality SV
subID STRING64 SV
normal-security
direct-with-
enhanced-sec.
sbo-with-
enhanced-sec.
minVal INT32 CF
maxVal INT32 CF
stepSize INT32U CF
d STRING256 DC
dU USTRING256 DC
cdcNs STRING256 EX
dataNs STRING256 EX
3) applies only for Client in transmit direction
4) transmit direction: for the ON state the parameterized IEC 61850 value is used
5) receive direction: for the parameterized IEC 61850 value the ON command is generated

Edition 06.2017, DC0-023-2.12
9.6.2.4.4 IEC 61850: Controllable Enumerated Status (ENC)

ctlVal INT32 CO TI 30: SPI 3) ü TI 30
TI 31: DPI 3) TI 31
TI 45: SCS 1) 4) 5) ü TI 45
TI 46: DCS 1) 4) 5) TI 46
TI 49: SVA 1) TI 49
TI 50: R32-IEEE 1) TI 50
origin Originator CO refer to 9.2.7.1.2, ü
ST Causes of
ctlNum INT8U CO ü
ST
stVal INT32 ST TI 30: SPI 2) 4) 5) ü TI 30
TI 31: DPI 2) 4) 5) TI 31
TI 35: SVA 2) TI 35
TI 36: R32-IEEE 2) TI 36
q Quality ST TI 30: SIQ 2) ü
TI 31: DIQ 2)
TI 35: QDS 2)
TI 36: QDS 2)
t TimeStamp ST CP56Time2a 2) ü
stSeld BOOLEAN ST TI 30: SPI 2) TI 30
subEna BOOLEAN SV
subVal INT32 SV
subQ Quality SV
subID STRING64 SV
ctlModel ENUMERATED CF status-only 6) settable in the detailed
normal-security
direct-with-
enhanced-sec.
sbo-with-
enhanced-sec.
minVal INT32 CF
maxVal INT32 CF
stepSize INT32U CF
d STRING256 DC
dU USTRING256 DC
cdcNs STRING256 EX
dataNs STRING256 EX

DC0-023-2.12, Edition 06.2017
9.6.2.4.5 IEC 61850: Controllable Integer Status (APC)

ctlVal AnalogueValue CO TI 49: SVA 1) ü TI 49
TI 50: R32-IEEE 1) TI 50
origin Originator CO refer to 9.2.7.1.2, ü
ST Causes of
ctlNum INT8U CO ü
ST
mxVal AnalogueValue ST TI 35: SVA 2) ü TI 35
TI 36: R32-IEEE 2) TI 36
q Quality ST TI 30: SIQ 2) ü
TI 31: DIQ 2)
TI 35: QDS 2)
TI 36: QDS 2)
t TimeStamp ST CP56Time2a 2) ü
stSeld BOOLEAN ST TI 30: SPI 2) TI 30
subEna BOOLEAN SV
subVal AnalogueValue SV
subQ Quality SV
subID STRING64 SV
normal-security
direct-with-
enhanced-sec.
sbo-with-
enhanced-sec.
minVal INT32 CF
maxVal INT32 CF
stepSize INT32U CF
d STRING256 DC
dU USTRING256 DC
cdcNs STRING256 EX
dataNs STRING256 EX

Edition 06.2017, DC0-023-2.12
9.6.2.4.6 IEC 61850: Single Point Status (SPS)

stVal BOOLEAN ST TI 30: SPI ü ü TI 30
q Quality ST TI 30: SIQ ü ü
t TimeStamp ST CP56Time2a ü ü
subEna BOOLEAN SV
subVal BOOLEAN SV
subQ Quality SV
subID STRING64 SV
d STRING256 DC
dU USTRING256 DC
cdcNs STRING256 EX
dataNs STRING256 EX
Server in Receive Direction:

The cause of transmission is fixed set to 3 (SPONTANEOUS).
Binary information is forwarded only upon change of stVal or q.

DC0-023-2.12, Edition 06.2017
9.6.2.4.7 IEC 61850: Double Point Status (DPS)

stVal CODED ENUM ST intermediate- TI 31: DPI ü ü TI 31
state
off
on
bad-state
q Quality ST TI 31: DIQ ü ü
subEna BOOLEAN SV
subVal CODED ENUM SV
subQ Quality SV
subID STRING64 SV
d STRING256 DC
dU USTRING256 DC
cdcNs STRING256 EX
dataNs STRING256 EX

The cause of transmission is fixed set to 3 (SPONTANEOUS).
Binary information is forwarded only upon change of stVal or q.

Edition 06.2017, DC0-023-2.12
9.6.2.4.8 IEC 61850: Integer Status (INS)

stVal INT32 ST TI 30: SPI*) ü ü TI 30
TI 31: DPI *) TI 31
TI 35: SVA TI 35
TI 36: R32-IEEE TI 36
TI 31: DIQ
TI 35: QDS
TI 36: QDS
subEna BOOLEAN SV
subVal INT32 SV
subQ Quality SV
subID STRING64 SV
d STRING256 DC
dU USTRING256 DC
cdcNs STRING256 EX
dataNs STRING256 EX
*) for the respective ON state the parameterized IEC 61850 value is used
9.6.2.4.9 IEC 61850: Enumerated Status (ENS)

stVal INT32 ST TI 30: SPI*) ü TI 30
TI 31: DPI *) TI 31
TI 35: SVA TI 35
q Quality ST TI 30: SIQ ü
TI 31: DIQ
TI 35: QDS
TI 36: QDS
t TimeStamp ST CP56Time2a ü
subEna BOOLEAN SV
subVal INT32 SV
subQ Quality SV
subID STRING64 SV
d STRING256 DC
dU USTRING256 DC
cdcNs STRING256 EX
dataNs STRING256 EX
*) for the respective ON state the parameterized IEC 61850 value is used

DC0-023-2.12, Edition 06.2017
9.6.2.4.10 IEC 61850: Protection Activation Information (ACT)

general BOOLEAN ST TI 30: SPI ü ü TI 30
TI 38: ES TI 38
TI 39: GS TI 39
TI 40: GC TI 40
phsA BOOLEAN ST TI 30: SPI ü ü TI 30
TI 38: ES TI 38
TI 39: SL1
TI 40: CL1
phsB BOOLEAN ST TI 30: SPI ü ü TI 30
TI 38: ES TI 38
TI 39: SL2
TI 40: CL2
phsC BOOLEAN ST TI 30: SPI ü ü TI 30
TI 38: ES TI 38
TI 39: SL3
TI 40: CL3
neut BOOLEAN ST TI 30: SPI ü ü TI 30
TI 38: ES TI 38
TI 39: SIE
TI 38: SEP
TI 39: QDP
TI 40: QDP
operTim STRING256 CF
d STRING256 DC
dU USTRING256 DC
cdcNs STRING256 EX
dataNs STRING256 EX
Client in Receive Direction:

With TI 38 the runtime is 0.
Server in Transmit Direction:

If single-point information (TI 30) or protection event (TI 38) is used, then in the detailed
routing must be also the attribute name specified. The quality (q) is then generated from an
OR logic of all single messages.

Binary information is forwarded only upon change of general, phsA, phsB, phsC, neut and q.

Edition 06.2017, DC0-023-2.12
9.6.2.4.11 IEC 61850: Directional Protection Activation Information (ACD)

general BOOLEAN ST TI 30: SPI ü ü TI 30
TI 31: DPI 1) TI 31
TI 38: ES TI 38
TI 39: GS TI 39
TI 40: GC TI 40
dirGeneral ENUMERATED ST unknown fixed “unknown” 2) ü 3) ü 3)
forward
backward
both
phsA BOOLEAN ST TI 30: SPI ü ü TI 30
TI 31: DPI 1) TI 31
TI 38: ES TI 38
TI 39: SL1
TI 40: CL1
dirPhsA ENUMERATED ST unknown fixed “unknown” 2) ü 3) ü 3)
forward
backward
both
phsB BOOLEAN ST TI 30: SPI ü ü TI 30
TI 31: DPI 1) TI 31
TI 38: ES TI 38
TI 39: SL2
TI 40: CL2
dirPhsB ENUMERATED ST unknown fixed “unknown” 2) ü 3) ü 3)
forward
backward
both
phsC BOOLEAN ST TI 30: SPI ü ü TI 30
TI 31: DPI 1) TI 31
TI 38: ES TI 38
TI 39: SL3
TI 40: CL3
dirPhsC ENUMERATED ST unknown fixed “unknown” 2) ü 3) ü 3)
forward
backward
both
neut BOOLEAN ST TI 30: SPI ü 4) ü 4) TI 30
TI 31: DPI 1) TI 31
TI 38: ES TI 38
TI 39: SIE
dirNeut ENUMERATED ST unknown fixed “unknown” 2) ü 3) ü 3)
forward
backward
both
TI 31: DIQ 1)
TI 38: SEP
TI 39: QDP
TI 40: QDP
operTim STRING256 CF
d STRING256 DC
dU USTRING256 DC
cdcNs STRING256 EX

DC0-023-2.12, Edition 06.2017

dataNs STRING256 EX
1) applies only for Client in receive direction
2) applies only for Server in transmit direction
3) applies for Client in receive direction: if TI 31 is used
4) does not apply for TI 31

With TI 38, TI 39, TI 40 the runtime is 0.
The status (general, phsA, phsB, phsC, neut) and the direction information (dirGeneral,
dirPhsA, dirPhsB, dirPhsC, dirNeut) is converted according tot he following table:
IEC 61850 IEC 60870-5-101/104

Status Direction information TI 31: DPI
AUS (0) unknown (0) DIFF (00)
forward (1) DIFF (00)
backward (2) DIFF (00)
both (3) DIFF (00)
EIN (1) unknown (0) ON (10)
forward (1) ON (10)
backward (2) OFF (01)
both (3) FAULT (11)
An intermediate resp. faulty position suppression is not performed.
If TI 30, TI 38 is used:
By means use of the field ON_info_on_IEC61850_value that is included in the detailed

routing, in each case a seperate single-point information can be derived from the status +
direction information (max. 4 single-point information items).
IEC 61850 direction ON info on

information IEC61850 value
unknown (0) 2
forward (1) 3
backward (2) 4
both (3) 5

If single-point information (TI 30) or protection event (TI 38) is used, then in the detailed
routing must be also the attribute name specified. The quality (q) is then generated from an
OR logic of all single messages.
The respective direction attributes are only then present, if also the belonging states are
present.

Binary information is forwarded only upon change of general, phsA, phsB, phsC, neut and q.

Edition 06.2017, DC0-023-2.12
9.6.2.4.12 IEC 61850: Setting Group (SGCB)

NumOfSG INT8U TI 35: SVA 1) ü ü TI 35
TI 36: R32-IEEE 1) TI 36
ActSG INT8U TI 30: SPI 1) 3) 4) ü ü TI 30,
TI 31: DPI 1) 3) 4) TI 31
TI 35: SVA 1) TI 35
TI 36: R32-IEEE 1) TI 36
TI 45: SCS 2) 4) 5) ü 6) ü 6) TI 45,

TI 46: DCS 2) 4) 5) TI 46
TI 49: SVA 2) TI 49
TI 50: R32-IEEE 2) TI 50
EditSG INT8U
CnfEdit BOOLEAN
LActTm TimeStamp CP56Time2a 1) ü ü
3) applies also for Client in transmit direction
6) transmit direction: no SEL/EXE permissible, but only EXE
Refer to section 9.2.4.1.4, Setting Group Control Model.

The Setting Group Control Block (SGCB) exists only if it is parameterized in the detailed
routing. It can appear only with LLN0 (e.g.: VL.C01/LLN0.SGCB).
Values of the SGCB are not assigned to a dataset resp. Unbuffered Control Block (no
spontaneous transmission).

Command output time (QU): 0 = without additional definition.
For Setting Groups no Confirmation, Termination messages are required. Also on the
IEC 61850 side the Write command is instantly confirmed positive.

DC0-023-2.12, Edition 06.2017
9.6.2.4.13 IEC 61850: Binary Counter Reading (BCR)

actVal INT128 ST TI 37: BCR 1) ü ü TI 37
frVal INT128 ST TI 37: BCR 2) ü ü TI 37
frTm TimeStamp ST CP56Time2a 2) ü ü
q Quality ST IV 1) 2) ü ü
units Unit CF
pulsQty FLOAT 32 CF
frEna BOOLEAN CF
strTm TimeStamp CF
frPd INT32 CF
frRs BOOLEAN CF
d STRING 256 CF
dU USTRING 256 CF
cdcNs STRING 256 CF
cdcName STRING 256 CF
dataNs STRING 256 CF
1) is used with use of the attribute "actVal"
2) is used with use of the attribute "frVal"

In the IEC 60870-5-101/104 message only a 31 bit binary value + sign can be represented. An
initial overflow of the value causes the CY bit which is reset afterwards. Only the less
significant 31 bits are used. The sequence number is 0.
Integrated totals are always transmitted spontaneous upon change. Counter interrogations are
not possible.

Edition 06.2017, DC0-023-2.12
9.6.2.4.14 IEC 61850: Binary Controlled Step Position Information (BSC)

ctlVal CODED_ENUM CO stop TI 47: RCO 1) 3) ü ü TI 47
lower
higher
ST Causes of
ST
valWTr ValWithTrans ST TI 32: VTI 2) ü ü TI 32
q Quality ST QDS 2) ü ü
stSeld BOOLEAN ST
subEna BOOLEAN SV
subVal BOOLEAN SV
subQ Quality SV
subID STRING64 SV
persistent BOOLEAN CF
normal-security
direct-with-
enhanced-sec.
sbo-with-
enhanced-sec.
minVal INT8 CF
maxVal INT8 CF
stepSize INT8U CF
d STRING256 DC
dU USTRING256 DC
cdcNs STRING256 EX
dataNs STRING256 EX
2) applies only for Client in receive direction and Server in transmit direction
3) the status "stop" is generated with the not permissible value "00" acc. to IEC 60870-5-101/104

DC0-023-2.12, Edition 06.2017
9.6.2.4.15 IEC 61850: Integer Controlled Step Position Information (ISC)

ctlVal INT8 CO -64…+63 2) 3) TI 49: SVA 1) 3) ü ü TI 49
TI 50: R32 – IEEE 1) 4) TI 50
ST Causes of
ST
valWTr ValWithTrans ST TI 32: VTI 2) ü ü TI 32
q Quality ST QDS 2) ü ü
stSeld BOOLEAN ST
subEna BOOLEAN SV
subVal BOOLEAN SV
subQ Quality SV
subID STRING64 SV
persistent BOOLEAN CF
normal-security
direct-with-
enhanced-sec.
sbo-with-
enhanced-sec.
minVal INT8 CF
maxVal INT8 CF
stepSize INT8U CF
d STRING256 DC
dU USTRING256 DC
cdcNs STRING256 EX
dataNs STRING256 EX
1 applies only for Client in transmit direction und Server in receive direction
2) applies only for Client in receive direction and Server in transmit direction
3) in contrast to the standard the maximum values can be in the range -128… +127

Edition 06.2017, DC0-023-2.12
9.6.2.4.16 IEC 61850: Analogue Setting (ASG)

setMag Analogue Value SP TI 49: SVA 1) ü ü TI 49
TI 50: R32-IEEE 1) TI 50
TI 35: SVA 2) ü ü TI 35
TI 36: R32-IEEE 2) TI 36
units Unit CF
sVC Select Value CF
Config
minVal Analogue Value CF
maxVal Analogue Value CF
stepsize Analogue Value CF
d STRING256 DC
dU STRING256 DC
cdcNs STRING256 EX
dataNs STRING256 EX

With writing of the value no Setting Group setting is performed, however, a simple write
process.

DC0-023-2.12, Edition 06.2017
9.6.2.4.17 IEC 61850: Integer Setting (ING)

setVal INT32 SP TI 49: SVA 1) ü ü TI 49
TI 50: R32-IEEE 1) TI 50
TI 35: SVA 2) ü ü TI 35
TI 36: R32-IEEE 2) TI 36
setVal INT32 SG,
SE
minVal INT32 CF
maxVal INT32 CF
stepsize INT32 CF
d STRING256 DC
dU STRING256 DC
cdcNs STRING256 EX
dataNs STRING256 EX
Client in in Transmit direction:

With writing of the value no Setting Group setting is performed, however, a simple write
process.

Edition 06.2017, DC0-023-2.12
9.6.2.4.18 IEC 61850: Measured Value (MV)

instMag AnalogueValue MX
mag AnalogueValue MX TI 34: NVA ü ü TI 34
TI 35: SVA TI 35
range ENUMERATED MX - normal
- high
- ...
q Quality MX QDS ü ü
t TimeStamp MX CP56Time2a ü ü
subEna BOOLEAN SV
subMag AnalogueValue SV
subQ Quality SV
subID STRING64 SV
units Unit CF
db INT32U CF
zeroDb INT32U CF
sVC ScaledValueCon CF
fig
rangeC RangeConfig CF
smpRate INT32U CF
d STRING256 DC
dU USTRING256 DC
cdcNs STRING256 EX
dataNs STRING256 EX

DC0-023-2.12, Edition 06.2017
9.6.2.4.19 IEC 61850: Complex Measured Value (CMV)

instCVal Vector MX
cVal Vector MX TI 34: NVA ü ü TI 34
TI 35: SVA TI 35
range ENUMERATED MX - normal
- high
- ...
subEna BOOLEAN SV
subCVal Vector SV
subQ Quality SV
subID STRING64 SV
units Unit CF
db INT32U CF
zeroDb INT32U CF
rangeC RangeConfig CF
magSVC ScaledValueCon CF
fig
angSVC ScaledValueCon CF
fig
angRef ENUMERATED CF -V
-A
- ...
smpRate INT32U CF
d STRING256 DC
dU USTRING256 DC
cdcNs STRING256 EX
dataNs STRING256 EX

Edition 06.2017, DC0-023-2.12
9.6.2.4.20 IEC 61850: Sampled Value (SAV)

instMag AnalogueValue MX TI 34: NVA ü ü TI 34
TI 35: SVA TI 35
units Unit CF
sVC ScaledValueCon CF
fig
min AnalogueValue CF
max AnalogueValue CF
d STRING256 DC
dU USTRING256 DC
cdcNs STRING256 EX
dataNs STRING256 EX
9.6.2.4.21 IEC 61850: Collection Of Measurands (WYE)

phsA CMV TI 34: NVA ü ü TI 34
TI 35: SVA TI 35
phsB CMV TI 34: NVA ü ü TI 34
TI 35: SVA TI 35
phsC CMV TI 34: NVA ü ü TI 34
TI 35: SVA TI 35
neut CMV TI 34: NVA ü ü TI 34
TI 35: SVA TI 35
net CMV TI 34: NVA ü ü TI 34
TI 35: SVA TI 35
res CMV TI 34: NVA ü ü TI 34
TI 35: SVA TI 35
angRef ENUMERATED CF
d STRING256 DC
dU USTRING256 DC
cdcNs STRING256 EX
dataNs STRING256 EX

DC0-023-2.12, Edition 06.2017
9.6.2.4.22 IEC 61850: Delta (DEL)

phsAB CMV TI 34: NVA ü ü TI 34
TI 35: SVA TI 35
phsBC CMV TI 34: NVA ü ü TI 34
TI 35: SVA TI 35
phsCA CMV TI 34: NVA ü ü TI 34
TI 35: SVA TI 35
angRef ENUMERATED CF
d STRING256 DC
dU USTRING256 DC
cdcNs STRING256 EX
dataNs STRING256 EX
9.6.2.4.23 IEC 61850: Sequence (SEQ)

c1 CMV TI 34: NVA ü ü TI 34
TI 35: SVA TI 35
TI 35: SVA TI 35
TI 35: SVA TI 35
seqT ENUMERATED MX - pos-neg-zero fix pos-neg-zero ü
- dir-quad-zero
phsRef ENUMERATED CF -A
-B
-C
-…
d STRING256 DC
dU USTRING256 DC
cdcNs STRING256 EX
dataNs STRING256 EX

Edition 06.2017, DC0-023-2.12
9.6.2.4.24 IEC 61850: Device Name Plate (DPL)

vendor STRING256 DC fix "SIEMENS" ü
hwRev STRING256 DC ü
swRev STRING256 DC Revision ETxx *) ü
serNum STRING256 DC ü
model STRING256 DC
location STRING256 DC
cdcNs STRING256 EX
dataNs STRING256 EX
*) xx = 03, 83 (dependent on the respective firmware)
9.6.2.4.25 IEC 61850: Logical Node Name Plate (LPL)

vendor STRING256 DC fix "SIEMENS" ü
swRev STRING256 DC Revision ETxx 1) ü
d STRING256 DC 2) ü
dU USTRING256 DC
configRev STRING256 DC fix 0 3) ü
ldNs STRING256 EX fix "IEC 61850-7-4: ü
2002" 3)
lnNs STRING256 EX
cdcNs STRING256 EX
dataNs STRING256 EX
1) xx = 03, 83 (dependent on the respective firmware)
2) this value is taken from the detailed routing "Logical Node Name Description"; if there is no Logical Node Name
Description included in the detailed routing, then the Logical Node Name is entered here (e.g.
VL.C01/Q0XCBR1)
3) only with LNN0

DC0-023-2.12, Edition 06.2017
9.6.2.5 Mapping IEC 61850 ® MMS
By means of the mapping from IEC 61850 to MMS, new “Extended Common Data Classes”
result.
Attention:
The “Extended Common” Data Classes serve only for the transmission on the line.
9.6.2.5.1 Extended Common Data Classes
Select with Value (SBOw), Operate (Oper), Cancel (Cancel)
Attribute name Type Supported

Ed.1 Ed.2
ctlVal 1) ü ü
setMag
operTm TimeStamp
origin Originator ü ü
ctlNum INT8U ü ü
T TimeStamp 2) ü ü
Test BOOLEAN ü ü
Check PACKED LIST 2) 3) ü ü
1) is adopted from the Basis Common Data Class
2) is not evaluated
3) for Cancel not present
9.6.3 Datapoint Settings in the Detailed Routing
All detailed routings in the process technique are "SIP Message Address Conversion". The
category is seperate for send direction and receive direction.
It is necessary that in the OPM II the detailed routing is filled out including data attribute.
Thereby it is to be considered that for CDCs always only one certain attribute can/must be
routed. Certain attributes (e.g. q, t) are added automatically. The attributes that must be
routed are listed with the CDCs.
Further, there are CDCs that consist of several IEC 60870-5-101/104 messages
(unambiguous/ambiguous).

Edition 06.2017, DC0-023-2.12
9.6.3.1 Client in Send Direction
Routing element Description Expert

parameter
CASDU1 Address of the datapoint
CASDU2
IOA1
IOA2
IOA3
IEC61850_Address 68 bytes ASCII characters (as of IEC 61850
Ed.2: 128 byte)
IEC61850_Station Station 0…99, 255 = not used
Measured_val_adap_X_0% Value adaptation limits
Measured_val_adap_X_100%
Measured_val_adap_Y_0%
TI 30 = Single-point information
31 = Double-point information
45 = Single command
46 = Double command
47 = Regulating step command
49 = Setpoint command, scaled
50 = Setpoint command, floating point
CDC Common Data Class 1)
12 = SPC
13 = DPC
14 = INC
20 = SGCB
21 = BSC
22 = ISC
23 = ASG
24 = ING
25 = APC
27 = ENC
IEC61850_command_qualifier 0 = via IEC 60870-5-101/104 ü
command_qualifier 2)
1 = without interlocking/without synchro
check
2 = with interlocking/without synchro check
3 = without interlocking/with synchro check
4 = with interlocking/with synchro check
5 = without interlocking/with synchro check
only with ON
6 = with interlocking/with synchro check
only with ON
IEC61850_value_at_TI45/46_ON 3) ü
IEC61850_value_at_TI45/46_OFF 3) ü
TIO Con->Term without syncrocheck 4) ü
TIO Con->Term with syncrocheck 4) ü
IM_CASDU1_ON Address of the interlocking information for ü
IM_CASDU2_ON the ON command 5)
IM_IOA1_ON
IM_IOA2_ON
IM_IOA3_ON
IM_CASDU1_OFF Address of the interlocking information for ü
IM_CASDU2_OFF the OFF command 5)
IM_IOA1_OFF
IM_IOA2_OFF
IM_IOA3_OFF
1) The belonging CDC must be parameterized here. Always the hierarchical most significant CDC
must be parameterized.
Example: VL.C01/CSWI1.Pos.ctlVal = DPC (Pos = DPC)
VL.C01/MMXU1.A.phsA.cVal.mag.f (A = WYE)

DC0-023-2.12, Edition 06.2017
2) The attribute "Check" is affected by means of that. The default entry is 0 (control by the
IEC 60870-5-101/104 command qualifier, refer to 9.2.7.1.1, Command Output Time (QU)).
3) This value is transmitted instead of ON (1) and can be used for the CDCs "INS", "INC" and
"SGCB"; as off 61850 Ed.2: "ENS", "ENC". By means of that, e.g. for the activation of the health
state (value range 1…3) respectively one single-point information can be used, whereby the
respective ON state of the command is converted to the corresponding value.
The OFF command is not evaluated.
4) The station-selective timeout for confirmation -> termination can be substituted with a command-
selective timeout for with and without syncrocheck. At value "0" the station-selective timeout
applies.
5) By means of respectively one single-point information (TI 30) for the ON resp. the OFF command
an overlapping interlocking operation can be implemented by means of a CAExplus project. If the
corresponding information is ON, the command is locked and is rejected with a neg. Confirmation.
By means of this function the same procedure of interlocking as to SICAM RTUs peripheral
elements can be applied.
IEC 60870-5-101/104 Interlocking information check

TI 45 Single command ON
TI 46 Double command ON, OFF
TI 47 Regulating step command ON (matches HIGHER),OFF (matches LOWER)
TI 49 Setpoint command, scaled ON
TI 50 Setpoint command, floating point ON

Edition 06.2017, DC0-023-2.12
9.6.3.2 Client in Receive Direction

parameter
CASDU2
IOA1
IOA2
IOA3
IEC61850_Address 68 bytes ASCII characters (as of 61850
Ed.2: 128 bytes)
IEC61850_Station Station 0…99, 255 = not used
Thresh_uncond Absolute value 1)
Thresh_additive Absolute value 1)
32 = Step position information
34 = Measured value, normalized
35 = Measured value, scaled
36 = Measured value, floating point
38 = Protection event
39 = Blocked start events of protection
40 = Blocked tripping of protection
CDC Common Data Class 2)
0 = Standard
1 = SPS
2 = DPS
3 = INS
4 = ACT
5 = ACD
6 = MV
7 = CMV
8 = SAV
9 = WYE
10 = DEL
11 = SEQ
12 = SPC
13 = DPC
14 = INC
19 = BCR
20 = SGCB
21 = BSC
22 = ISC
23 = ASG
24 = ING
25 = APC
26 = ENS
27 = ENC
ON-info_on_IEC61850_value 3) ü
Usage_on_information_IEC61850_ 0 = event ü
1 = IEC61850 value bit 0
Type_of_binary_information coming/going 4) ü
coming
1) The measured value change monitoring occurs on the raw value (= received value from the
Server).

DC0-023-2.12, Edition 06.2017
2) Here the belonging CDC must be parameterized. Always the hierarchical most significant CDC
must be parameterized.
Example: VL.C01 / XCBR1.Pos.stVal = DPC (Pos = DPC)
VL.C01 / MMXU1.TotW.mag.f = MV (TotW = MV)
VL.C01 / MMXU1.A.phsA.cVal.mag.f = WYE (A = WYE)
3) With the value for TI 30/31 can be parameterized, at which IEC 61850 value the ON info is to be
generated. The corresponding OFF info is generated automatically by the firmware as soon as
another value is received (applies only for the CDCs "INC", "INS", "SGCB"; as of 61850 Ed.2:
"ENS", "ENC").
For the CDC “ACD” the direction information can be evaluated with the values 2, 3, 4, 5
(9.6.2.4.11, IEC 61850: Directional Protection Activation Information (ACD)
4) This applies only for single-point information items (TI 30). By means of the setting "coming" is the
going edge automatically emulated (1 ms time difference to the comin edge).
9.6.3.3 Client – Disturbance Record in Transmit Direction

parameter
CASDU2
IOA1
IOA2
IOA3
TI 142 = user data container
File transfer mode Client
9.6.3.4 Client – Disturbance Record in Receive Direction

parameter
CASDU2
IOA1
IOA2
IOA3
TI 142 = user data container
File transfer mode Client

Edition 06.2017, DC0-023-2.12
9.6.3.5 Server in Transmit Direction

parameter
CASDU2
IOA1
IOA2
IOA3
IEC61850_Address 68 bytes ASCII characters

Selectivity To all remote stations/selective
CDC 0 = Standard
1 = SPS
2 = DPS
3 = INS
4 = ACT
5 = ACD
6 = MV
7 = CMV
8 = SAV
9 = WYE
10 = DEL
11 = SEQ
12 = SPC
13 = DPC
14 = INC
19 = BCR
20 = SGCB
21 = BSC
22 = ISC
23 = ASG
24 = ING
25 = APC
26 = ENS
Usage_IEC61850_value_off 0 = IEC61850 value at TI30/31 OFF not ü

used
1 = IEC61850 value at TI30/31 OFF used
Goose_Attr1_Datasetpos 3) Selection 0…255 ü
Goose_Attr2_Datasetpos 3)

DC0-023-2.12, Edition 06.2017

parameter
Goose_Attrib1 3) Goose attribute (refer to 9.6.3.8.1, GOOSE ü
Goose_Attrib2 3) Attributes)
Goose_Attrib3 3)
Goose_Attrib4 3)
Goose_Attrib5 3)
Goose_Idx 3) Selection 0…255 ü
1) This value is transmitted instead of ON (1) and can be used for the CDCs "INC", "INS" (Ed.1) or
“ENC“, “ENS“ (Ed.2) and "SGCB". By means of that, e.g. for the health status (value range 1…3)
a single-point information can be used respectively for the activation, whereby the respective ON
status of the information is converted to the corresponding value. The OFF information is not
evaluated.
2) This value is transmitted instead of OFF and can be used for the CDCs "INC", "INS" (Ed.1) or
“ENC“, “ENS“ (Ed.2) and "SGCB". This value is only then used, if all information items that have
the same IEC 61850 address have the status OFF.
3) only Edition 2

Edition 06.2017, DC0-023-2.12
9.6.3.6 Server in Receive Direction

parameter
CASDU2
IOA1
IOA2
IOA3
Controltype - Direct control with normal security
- Direct control with enhanced security
- SBO control with enhanced security

45 = Single command
46 = Double command
CDC 0 = Standard
12 = SPC
13 = DPC
14 = INC
21 = BSC
22 = ISC
23 = ASG
24 = ING
25 = APC
27 = ENC
ON-command_on_IEC61850_value 1) ü
Goose_Attr1_Datasetpos 2) Selection 0…255 ü

Goose_Attrib1 2) Goose attribute (refer to 9.6.3.8.1, GOOSE ü

Goose_Attrib2 2) Attributes)
Goose_Attrib3 2)
Goose_Attrib4 2)
Goose_Attrib5 2)
Goose_Idx 2) Selection 0…255 ü
1) With the value for TI 45/46 can be parameterized, at which IEC 61850 value the ON command is
to be generated. The corresponding OFF command is generated automatically by the firmware as
soon as another value is received (applies only for the CDCs "INC", "INS" (Ed.1) or “ENC“, “ENS“
(Ed.2) and "SGCB").
By means of this function can be derived a command from each status e.g. due to a Controllable
Integer Status (INC/ENC), whereby the current status result in an ON command and all other with
the same IEC 61850 address in an OFF command. The originator address iss et fixed to 0.
2) only Edition 2

DC0-023-2.12, Edition 06.2017
9.6.3.7 Server in Transmit Direction + Goose [only Edition 1]

parameter
CASDU2
IOA1
IOA2
IOA3
IEC61850_Address 68 bytes ASCII character
39 = blocked start events of protection
40 = blocked tripping of protection
CDC 0 = Standard
1 = SPS
2 = DPS
3 = INS
4 = ACT
5 = ACD
6 = MV
7 = CMV
8 = SAV
9 = WYE
10 = DEL
11 = SEQ
12 = SPC
13 = DPC
14 = INC
19 = BCR
21 = BSC
22 = ISC
23 = ASG
24 = ING
25 = APC
26 = ENS
27 = ENC
Goose_Attr1 Goose attribute (refer to 9.6.3.8.1, GOOSE
Goose_Attr2 Attributes)
Goose_Attr3
Goose_Attr4
Goose_Attr5
Goose_Index_A Goose Index in der Systemtechnik 0…255
Goose_Index_B
Goose_Index_C

Edition 06.2017, DC0-023-2.12

parameter
Goose_Attr1_Datasetpos_Index_A Dataset Position 0…255 3) ü
Goose_Attr1_Datasetpos_Index_B
Goose_Attr1_Datasetpos_Index_C
Goose_Attr2_Datasetpos_Index_A
Station_A Selection station 0…99 ü
Station_B 255 = to all stations
Station_C
Station_D
Station_E
Station_F
Station_G
Station_H
Station_I
Station_J
Usage_IEC61850_value_off 0 = IEC61850 value at TI30/31 OFF not ü
used
1 = IEC61850 value at TI30/31 OFFused
1) This value is transmitted instead of ON (1) and can be used for the CDCs "INC", "INS" (Ed.1) or
“ENC“, “ENS“ (Ed.2) and "SGCB". By means of that, e.g. for the health status (value range 1…3)
a single-point information can be used respectively for the activation, whereby the respective ON
status of the information is converted to the corresponding value. The OFF information is not
evaluated.
2) This value is transmitted instead of OFF and can be used for the CDCs "INC", "INS" (Ed.1) or
“ENC“, “ENS“ (Ed.2) and "SGCB". This value is only then used, if all information items that have
the same IEC 61850 address have the status OFF.
3) The dataset position must be parameterized ascending from 0 and must not have breaks.

DC0-023-2.12, Edition 06.2017
9.6.3.8 Server in Receive Direction + Goose [only Edition 1]

parameter
CASDU2
IOA1
IOA2
IOA3
Controltype - Direct control with normal security
- Direct control with enhanced
security
- SBO control with enhanced security
IEC61850_Address 68 bytes ASCII character
Thresh_uncond Absolute value 1)
Thresh_additive Absolute value 1)
39 = blocked start events of protection
40 = blocked tripping of protection
45 = Single command
46 = Double command
CDC 0 = Standard
12 = SPC
13 = DPC
14 = INC
21 = BSC
22 = ISC
23 = ASG
24 = ING
25 = APC
27 = ENC
ON-command_on_IEC61850_value 2) ü
Goose_Attr1 Goose attribute (refer to 9.6.3.8.1, GOOSE
Goose_Attr2 Attributes)
Goose_Attr3
Goose_Attr4
Goose_Attr5
Goose_Index_A Goose index in the System Technique
0…255
Goose_Attr1_Datasetpos_Index_A Dataset position 0…255 3) ü

Edition 06.2017, DC0-023-2.12

parameter
Station_C
Station_D
Station_E
Station_F
Station_G
Station_H
Station_I
Station_J
1) The measured value change monitoring occurs on the raw value (= received value)
2) With the value for TI 45, TI 46 can be parameterized, with which IEC 61850 value the ON
command is to be generated. The corresponding OFF command is generated automatically by
the firmware as soon as another value is received (applies only for the CDCs "INC", "INS" (Ed.1)
or “ENC“, “ENS“ (Ed.2) and "SGCB").
3) The dataset position must be parameterized ascending from 0 and must not have breaks.

DC0-023-2.12, Edition 06.2017
9.6.3.8.1 GOOSE Attributes
Goose Attribut Common Data Class (CDC)
stVal SPS, DPS, INS, SPC, DPC, INC

q SPS, DPS, INS, ACT, ACD, MV, CMV, SAV, SPC, DPC, INC
t SPS, DPS, INS, ACT, ACD, MV, CMV, SAV, SPC, DPC, INC
general ACT, ACD
phsA ACT, ACD
phsB ACT, ACD
phsC ACT, ACD
neut ACT, ACD
mag.f MV
cVal.mag.f CMV
inst Mag.f SAV
phsA.cVal.mag.f WYE
phsB.cVal.mag.f WYE
phsC.cVal.mag.f WYE
neut.cVal.mag.f WYE
net.cVal.mag.f WYE
res.cVal.mag.f WYE
phsA.q WYE
phsA.t WYE
phsB.q WYE
phsB.t WYE
phsC.q WYE
phsC.t WYE
neut.q WYE
neut.t WYE
net.q WYE
net.t WYE
res.q WYE
res.t WYE
phsAB.cVal.mag.f DEL
phsBC.cVal.mag.f DEL
phsCA.cVal.mag.f DEL
phsAB.q DEL
phsAB.t DEL
phsBC.q DEL
phsBC.t DEL
phsCA.q DEL
phsCA.t DEL
c1.cVal.mag.f SEQ
c2.cVal.mag.f SEQ
c3.cVal.mag.f SEQ
c1.q SEQ
c1.t SEQ
c2.q SEQ
c2.t SEQ
c3.q SEQ
c3.t SEQ
Pos.origin.orCat DPC
Pos.origin.orIdent DPC
stSeld DPC
Pos.Oper.origin.orCat DPC
Pos.Oper.origin.orIdent DPC

Edition 06.2017, DC0-023-2.12
9.6.3.9 Server in Transmit Direction – Default Values

parameter
Station_C
Station_D
Station_E
Station_F
Station_G
Station_H
Station_I
Station_J
Value Default value (30 characters)
With this routing the Data Attribute Name must be named always.
For the following Basic Types (refer to 9.6.2.1, IEC 61850: Basic Types) a default value can
be parameterized, whereby the values must be parameterized in ASCII:
Basic type
BOOLEAN
INT 8
INT 16
INT 24
INT 32
INT 128
INT 8U
INT 16U
INT 24U
INT 32U
FLOAT 32
FLOAT 64
VISIBLE STRING

DC0-023-2.12, Edition 06.2017
9.6.3.10 GOOSE Properties (System Technique)
Routing element Description

GOOSE Index 0…99
GoCBRef 65 bytes ASCII 1)
GoID 65 bytes ASCII 2)
DataSet 68 bytes ASCII 3)
MAC Address 12 bytes ASCII 4)
AppID 0…3FFF 5)
configRev 0…4294967295 6)
VLAN Vid 0…4096 7)
VLAN Priority 0…7 8)
1) reference to the GOOSE Control Block, e.g.: VL.C01/LLN0.gcST
2) unambiguous identification of the GOOSE message
3) name of the Data Set, e.g.:VL.C01/ds2
4) refer to section 9.2.4.2, Data Transmission Server <-> Server with "GOOSE" [Server only]
5) should be unambigousg over all GOOSE messages and unequally 0 (attention: HEX)
6) 32 bit value, the SICAM TOOLBOX II supports only a 16 bit value (0…65535)
7) should be unequally 0
8) default 4
For the coupling of devices with the IEC 61850 protocol, if necessary the following special
functions can be activated for the adaptation of the message conversion:
· Conversion of the time information

· Signaling / measured value disabling
· Emulation of the going binary information
· Emulation of the data on reception of the attribute Beh.stVal="OFF" and
Beh.stVal = "BLOCKED"
· Technological adaptation for measured values
· Logging of the remote commands at the local control centre
· Remote parameterization/diagnostic of SICAM RTUs components via 61850

Edition 06.2017, DC0-023-2.12
9.6.4.1 Conversion of the Time Information
As time format, as standard IEC 61850 defines the UTC-Format (Universal Time Coordinated
= "coordinated universal time").
For the message conversion, the SICAM RTUs internal time format can be determined with
the parameter advanced parameters | Time format in transmit direction and
with the parameter advanced parameters | Time format in receive direction.
Possible time formats:
IEC 61850 Time Format (on the line) IEC 60870-5-101/104 Time Format (SICAM RTUs
internal)
UTC (Universal Time Coordinated) Local time with daylight-saving / normal time
UTC (Universal Time Coordinated) Local time with normal time (winter time)
UTC (Universal Time Coordinated) UTC (Universal Time Coordinated)
Local time Local time
9.6.4.2 Signaling / Measured Value Disabling [Client only]
The signaling / measured value disabling is a function of the protection equipment and can be
activated globally (for binary information and measured values together) for example by
means of a key lock switch or by means of a control input in the protection equipment.
Through the signaling / measured value disabling function the spontaneous transmission
(Reporting) is deactivated.
With activation/deactivation of the signaling / measured value disabling, for each logical
device the binary information "Behavior" is transmitted spontaneously to the client. The
signaling / measured value disabling is transmitted as last signal with activation and as first
signal with deactivation.
So that the functions for the emulation of the data can be executed by the protocol element
with signaling / measured value disabling, the attribute "Beh.stVal" for signaling / measured
value disabling of the affected logical node or the logical node LLN0 must be entered in the
SIP message address conversion in receive direction. The protocol element evaluates the
attribute of the respective logical node with higher priority than the attribute of the logical node
LLN0.
If only the attribute "Beh.stVal" of the logical node LLN0 is entered, on reception of the
attribute "Beh.stVal = BLOCKED" the data of all affected logical nodes is emulated.
If the attribute "Beh.stVal" of a selective logical node is entered, on reception of the attribute
"Beh.stVal = BLOCKED" only the data of the selective logical node is emulated.
The emulation of the data concerned (with activation of the signaling / measured value
disabling) by the protocol element with 61850 Server function to the internal
IEC 60870-5-101/104 format can be selected with the parameter IEC61850 | client |
advanced parameters | behavior of Beh.stVal=2 (blocked) (as of 61850 Ed.2:
connection definition | Beh.stVal=2 (blocked)).
Possible emulation of the data with Beh.stVal = BLOCKED:
· No emulation
· Emulation of the data with "BL = 1" (blocked)

DC0-023-2.12, Edition 06.2017
On deactivation of the signaling / measured value disabling, in the following cases all data
concerned are read out again by the SICAM RTUs protocol element with 61850 Server
function from the 61850 clients and the data transferred spontaneously:
· Change of the attribute Beh.StVal from "BLOCKED" à "ON"

· Change of the attribute Beh.StVal from "BLOCKED" à "TEST"
· Change of the attribute Beh.StVal from "BLOCKED" à "TEST-BLOCKED"
Note
- In the SICAM RTUs protocol element with 61850 Server function, no special functionality is
implemented for the signaling / measured value disabling!
- For counts that are transmitted as measured values, no emulation is performed!
- With signaling / measured value disabling activated, also no (possible) parameterized cyclic
interrogation of the data points concerned is performed.
- SICAM RTUs internal, on activation of the signaling / measured value disabling, all
signals/measured values are generated with the status "spontaneous + blocked" and
transmitted via 61850 to the client. On deactivation of the signaling / measured value
disabling, all signals/measured values are transmitted spontaneously with the status
"spontaneous".
9.6.4.3 Emulation of the Going Binary Information [Client only]
With IEC 61850, protection signals are only transmitted with the state "ON" (coming).
For IEC 60870-5-101/104, the "coming/going state" is always required for every signal.
The protocol element with 61850 Client function can emulate the "Going Signal" automatically
for selected signals in receive direction. The "Going Signal" is fixed emulated with the time of
the coming signal + 10 milliseconds.
The emulation of the going signal can be parameterized in the SIP message address
conversion in receive direction in the category firmware / Client_Rec_IEC61850 for each signal
in the field type_of_binary_information.
9.6.4.4 Emulation of the Data on Reception of the Attribute

Beh.stVal = "OFF" [Client only]
On reception of the attribute "Beh.stVal" with the state "OFF" for a selective logical node or
the logical node LLN0 (per logical device), the emulation of the data concerned by the protocol
element with 61850 Server function to the internal IEC 60870-5-101/104 format can be
selected with the parameter IEC61850 | client | advanced parameters | behavior
of Beh.stVal=5 (OFF) (as of 61850 Ed.2: connection definition | Beh.stVal=5
(OFF)).
Possible emulation of the data with Beh.stVal = OFF:
· No emulation
· Emulation of the data with "NT=1" (not topical)
· Emulation of the data with "IV=1" (invalid)
So that the functions for the emulation of the data can be performed by the protocol element,
the attribute "Beh.stVal" must be entered in the SIP message address conversion in receive
direction. The protocol element evaluates the attribute of the respective logical node with
higher priority than the attribute of the logical node LLN0.

Edition 06.2017, DC0-023-2.12
If only the attribute "Beh.stVal" of the logical node LLN0 is entered, on reception of the
attribute "Beh.stVal = OFF" the data of all affected logical nodes is emulated.
If the attribute "Beh.stVal" of a selective logical node is entered, on reception of the attribute
"Beh.stVal = OFF" only the data of the selective logical node is emulated.
Note
For counts that are transmitted as measured values, no emulation is performed!
On reception of the attribute Behavior (Beh.stVal) with the state ≠ "OFF", in the following
cases all affected data points are read out again by the SICAM RTUs protocol element with
61850 Server function from the 61850 clients and the data transferred spontaneously:
· Change of the attribute “Beh.StVal” from "OFF" à "ON"

· Change of the attribute “Beh.StVal” from "OFF" à "TEST"
· Change of the attribute “Beh.StVal” from "OFF" à "TEST-BLOCKED"
9.6.4.5 Technological Adaptation for Measured Values
The technological adaptation enables the measured value supplied by the connected devices
to be transformed into a technological or normalized value. Into which value conversion can
take place, is dependent on the format of the spontaneous information object to be
transferred.
Type Spontaneous Value Range Meaning

Identification Information Object
(IEC 60870-5-104)
-15
<TI:=34> Measured value, - 1 ... + 1-2 normalized, percental
normalized value representation
<TI:=35> Measured value, scaled - 32768 technological, integer
value ...
+ 32767
-37
<TI:=36> Measured value, short - 8,43 * 10 technological, floating point
floating point ...
38
+ 3,37 * 10
The parameters for the technological adaptation are parameterized for each measured value
as
· adaptation line with 2 interpolation points (X_0%, X_100%, Y_0%, Y_100%)
The received measured value is adapted linear according to the parameter setting by the
protocol element before transfer to the basic system element.
The adaptation line with 2 interpolation points is to be parameterized for each measured value
with the parameters Measured_val_adap_X_0%, Measured_val_adap_X_100%,
Measured_val_adap_Y_0% and Measured_val_adap_Y_100% in the technological
parameters of the protocol element. For this, the technological value Y0 is parameterized for
the lower limit of the measuring range X0 and the technological value Y100 for the upper limit
of the measuring range X100.

DC0-023-2.12, Edition 06.2017
Bipolar measured values without zero-range suppression and plausibility check
Example: Value Meaning Parameter

X0 -2000 lower boundary of the measuring range Measured value
(set by parameter) adaptation_X_0%
X100 +2000 upper boundary of the measuring range Measured value
(set by parameter) adaptation_X_100%
Y0 -1 technological value at X0 Measured value
adaptation_Y_0%
Y 100 +1 technological value at X100 Measured value
adaptation_Y_100%
Y100 Normalized value
X0 X100
Y0
Data point quality descriptor
IV
OV

Edition 06.2017, DC0-023-2.12
9.6.4.6 Measured Value Change Monitoring
Measured values are transmitted from some protection equipment with the smallest changes
in measured value or even cyclic.
So as not to load the following transmission facilities unnecessarily, the measured value is
monitored for change in accordance with the following rules:
· The first value received after startup is transmitted immediately

· Every change of the quality descriptors blocked, invalid or overflow triggers an immediate
transmission
· Change monitoring in accordance with the method of the additive threshold value
procedure
Additive threshold value procedure

In the parameterized processing grid the measured value is monitored for change. If the
deviation from the last spontaneously transmitted measured value is greater than the
parameter-settable thresh_uncond, the new measured value is transmitted immediately.
Otherwise, in the parameterized processing grid the deviations from the last spontaneously
transmitted measured value are totalled according to the polarity sign. Only when the amount
of this total exceeds the parameter-settable thresh_additive is the current measured
value spontaneously transmitted.
thresh thresh Processing

uncond additive
0 0
value will be sent to BSE immediately after change
0 ≠0
≠0 0 value will be sent to BSE immediately after change during next
processing grid
≠0 ≠0 · change of value greater or equal than thresh_uncond
− value will be sent to BSE immediately after change during next
processing grid
· change of value less than thresh_additive
− additive threshold value procedure
A transmission of the measured value due to a general interrogation does not influence the
threshold value procedure.
By means of parameterization it is established:

─ Processing grid 0.1s…25.5 s
─ Thresh_Uncond 1.17 * 10-38 … 3.40 * 10+38
─ Thresh_Additive 1.17 * 10-38 … 3.40 * 10+38
The values for the parameters thresh_additive and thresh_uncond are absolute
values and always refer to the received non-linearized value.
The processing grid is parameterized for all measured values together with the parameter
IEC61850 | Grid for measurands change monitoring.
The thresholds are to be parameterized for every measured value with the parameter
thresh_additive and the parameter thresh_uncond in the technological parameters for
protocol element.

DC0-023-2.12, Edition 06.2017
The following example describes a standard case, in which the adaptation line goes through
the zero point (origin) (Yat X=0 = 0).
Examples
Technological value Y100 4000
Processing grid 0.1 s
Thresh_uncond 80.00 (represents a change of the received value by 80)
Thresh_additive 6000.00 (represents an additive sum of 6000)
constant. The measured value is transmitted after 7.5 seconds.
0.0 s 0.1 s 0.2 s 0.3 s 0.4 s 0.5 s 0.6 s 0.7 s 0.8 s ... 7.4 s 7.5 s
Measured value 300 379 379 379 379 379 379 379 379 ... 379 379
Difference >80 79 79 79 79 79 79 79 79 ... 79 79
Additive total 0 79 158 237 316 395 474 553 632 ... 5925 6004
Transmission x x
constant. The measured value is transmitted after 10 minutes.
0.0 s 0.1 s 0.2 s 0.3 s 0.4 s 0.5 s 0.6 s 0.7 s 0.8 s ... 599.9 600 s
Measured value 300 301 301 301 301 301 301 301 301 ... 301 301
Difference >80 1 1 1 1 1 1 1 1 ... 1 1
Additive total 0 1 2 3 4 5 6 7 8 ... 5999 6000
Transmission x x
Example 3: After transmission due to the exceeding of the large threshold, the value
continually changes by ±1. The measured value is not transmitted.
0.0 s 0.1 s 0.2 s 0.3 s 0.4 s 0.5 s 0.6 s 0.7 s 0.8 s ... 7.4 s 7.5 s
Measured value 300 301 300 299 300 301 300 301 299 ... 300 301
Difference >80 1 0 -1 0 1 0 1 -1 ... 0 1
Additive total 0 1 0 1 0 1 0 1 1 ... 0 1
Transmission x

Edition 06.2017, DC0-023-2.12
9.6.4.7 Monitoring Intermediate and Faulty Positions of Double Point

Information [Client only]
Double-point information that are transmitted from the connected 61850 devices, can be
monitored by the protocol element for intermediate and faulty position (in most cases
protection equipment do not have any monitoring for intermediate and faulty position
implemented).
Thereby, the transfer of an intermediate position (neither ON- nor OFF binary information
exists) or a faulty position (both ON- as well as OFF binary information exists) is suppressed
by the protocol element for a parameter-settable time.
On reception of double-point information with intermediate or faulty position, a monitoring time

is started and the double-point information is not transferred. If during the monitoring time the
double-point information is received with valid binary information state (ON or OFF), the
monitoring time is stopped and the double-point information is transferred with the valid binary
information state.
On expiry of the monitoring time, the double-point information with the state "intermediate or
faulty position" is transferred with the received time.
The assignment of the message address for the spontaneous information object "Double-point
information" is carried out in the OPM II with the category SIP message address conversion /... /
firmware / ....
For the suppression of the intermediate and faulty position, a suppression time for
intermediate position and a suppression time for faulty position is to be parameterized for all
double-point information together.
The suppression time for intermediate position is to be parameterized with the parameter
IEC61850 | client | intermediate position suppression time (as of 61850 Ed.2:
connection definition | intermediate position suppression time (s)).
The suppression time for faulty position is to be parameterized with the parameter IEC61850
| client | faulty position suppression time (as of 61850 Ed.2: connection
definition | faulty position suppression time (s)).

DC0-023-2.12, Edition 06.2017
9.6.4.8 Logging of the Remote Commands at the Local Control Centre

[Server only]
For documentation or traceability, a logging of operator inputs to an existing local control

centre is often required.
So that remote commands can be logged at a local control centre connected in the 61850
network, the remote commands must also be sent to the local control centre. However with
IEC 61850, due to the Server/Client communication this is not possible without additional
measures!
For configurations with SICAM RTUs components as 61850-Client and the control centre
system SICAM 230 as local control centre, the logging of remote commands via IEC 61850 is
possible by means of a proprietary (non-compatible) procedure, if an unambiguously assigned
return information is available for every remote command (assignment: ctlVal ó stVal).
With function activated, the protocol element with 61850 Server function sends the return
information to the control point and to the local control centre with the information required for
the logging in the attribute "orIdent" (Originator Identification).
The following items of information are entered in the attribute "orIdent" as ASCII-Text (max. 64
characters):
· IP Address
· Region number
· Component number
· Cause of transmission
· Positive/Negative identifier
· Data (On/Off, Lower/Higher,…)
· Originator address
The function can be activated with the parameter IEC61850 | server | advanced
parameters | log remote commands on local SCADA system.
9.6.4.9 Remote Parameterization/Diagnostic of SICAM RTUs

Components via IEC 61850
If SICAM RTUs components are used as 61850-Client and as 61850-Server, then a remote
parameterization/diagnostic of the SICAM RTUs components can be performed over the LAN
connection and the 61850 protocol element.
The remote parameterization/diagnostic is activated automatically by the 61850 protocol

element, as soon as the connection is established and a SICAM RTUs component with 61850
protocol element has been detected as remote station.
For this a proprietary procedure is implemented over the TCP/IP connection of the LAN-link,
which can only be used between SICAM RTUs components and is not defined in IEC 61850
or IEC 60870-5-104 respectively.
The automatic detection/activation and the transmission of all messages required for the
remote parameterization/diagnostic takes place over TCP/IP with messages defined
especially for this purpose.

Edition 06.2017, DC0-023-2.12
9.7 Web Server
9.7.1 IEC 61850 Edition 1 [Client + Server]
This information can be read out with a common Web Browser, as for instance Microsoft
Internet Explorer ®. For the access to the web server the communications protocol "HTTP
With SICAM AK 3, the integrated web server for the protocol elements PRE0,1 can be
reached as follows (example):
https://10.9.19.32/pre1 (pre…0,1)
http://10.9.19.32/pre1 (pre…0,1)
By default the integrated web server is deactivated for security reasons. If needed, it can be
enabled for access by the user with the parameter advanced parameters | Webserver.
Note

DC0-023-2.12, Edition 06.2017
· General information (Home)

· Diagnostic information
─ Triggering a Ping command (Diagnosis | Send Ping)
─ Display of the connection information (Diagnosis | Connections)
─ Display of the Detail Routing Parameters for the server function in transmit direction
(Diagnosis | Detail rout. Server TRA)
─ Display of the Detail Routing Parameters for the server function in receive direction
(Diagnosis | Detail rout. Server REC)
─ Display of the Detail Routing Parameters for the client function in transmit direction
(Diagnosis | Detail rout. Client TRA)
─ Display of the Detail Routing Parameters for the client function in receive direction
(Diagnosis | Detail rout. Client REC)
─ Display of the control locations with command authority (Diagnosis | Control
location)
─ Display of the directories in SICAM RTUs components with server function
(Diagnosis | Directories Server)
─ Display of the GOOSE information (Diagnosis | Goose)
· System-internal data for development specialists
· Switch (DNIP only)
─ Display statistic information (Switch | Statistic)
─ Display RSTP information (Switch | RSTP)
General Information
On the start page of the web server, general information about the protocol element and the
network-specific settings is displayed.

Edition 06.2017, DC0-023-2.12
General Information:
· Reg#, Comp#, BSE#, SSE#, IP Address, Subnet Mask, Default Router, Actual Link,
Speed, Duplex
The parameterized or current values are displayed next to the respective fields.
· IED Name [Server only]
The displayed "IED Name" (= Intelligent Electronical Device Name or Physical Device
Name) is parameterized with the parameter IEC61850 | server | IED name.
This IED Name is only used for the ICD file import (as of 61850 Ed.2).
The IED Name required for IEC 61850 is only taken by the protocol element from the data
of the SIP message address conversion in transmit/receive direction.
· Firmware
The status of the firmware is displayed next to the field "Firmware".
OK ……………………..……..Firmware is running error-free
KILL, No: #### (0x####)……A serious error has occurred → notify manufacturer!
The number displayed (decimal and HEX) supply the
developer with more specific information about the cause of
the error.
· Redundancy
The current redundancy state of the protocol element is displayed next to the field
"Redundancy".
Firmware active ……..……...The redundancy state of the protocol element is "ACTIVE"
Firmware passive …..………The redundancy state of the protocol element is "PASSIVE"
· LLN0.configRev
The current revision of the SICAM RTUs internal IEC 61850 specific parameters is
displayed here.
This revision can parameterized either with the parameter IEC61850 | server |
advanced parameters | LLN0.configRev or with corresponding setting of the
parameter IEC61850 | server | advanced parameters | LLN0.configRev
setting the parameter revision generated automatically by the
SICAM TOOLBOX II is displayed for the relevant parameter blocks.
Note
The "configRev" is the unambiguous identifier of the parameter status of a 61850 device and for
SICAM RTUs components is listed for each Physical Device (all logical devices of a physical device have
the same revision).
Attention
61850 devices of some manufacturers check that revision of the parameter status (configRev) imported
from the ICD-File for connected 61850 devices with that parameter status used in the connected 61850
device (configRev is read out and compared).
à IEC 81850 devices of some manufacturers terminate the complete function if the configRev
no longer corresponds!
Note
The SICAM RTUs protocol element for IEC 61850 does not terminate the function with different
configRev's – correctly parameterized data is converted, the remaining data is not converted.

DC0-023-2.12, Edition 06.2017
Triggering a Ping command ("Send Ping")

On the web page Diagnosis | Send Ping a PING command can be transmitted from the
LAN protocol element to the remote station.
This function can be used by the user in order to be able to check the reachability of a
connected 61850 remote station.
The advantage of this function is that the PING command is really transmitted from the
protocol element, thus from the source.
The results of the PING command are displayed in a separate window.
Connection Information ("Connections")

On the web page Diagnosis | Connections the status information of the parameterized
connections is displayed.

Edition 06.2017, DC0-023-2.12
Connection-specific status information:
· Station (SICAM RTUs internal station number)

reference for that connection to which an IP address is assigned.
· IP Address
The field "IP Address" displays the IP address of the remote station parameterized in the
parameters for connection definition. An IP address marked red signifies that this is
presently not reachable.
By clicking the mouse button on the IP address, via a link the web page of a web server
possibly implemented in the remote station is displayed.
· Dir Ind. [Server only]
The field "Dir Ind." (Directory Index) is only used for SICAM RTUs components with
61850-Server function and is an index number for a directory created in the server (data
model). The "Dir Ind" is unambiguous within a device.
By clicking the mouse button on the registered "Dir Ind." of a station, the assigned data
model of the 61850-Station (remote station) is displayed.
· Dir ID [Server only]
The field "Dir ID" (Directory ID) is only used for SICAM RTUs components with 61850-
Server function and is an unambiguous identification number for a directory created in the
server (data model).
By clicking the mouse button on the registered "Dir ID" of a station, the assigned data
model of the 61850-Station (remote station) is displayed.
· TCP Conn. [Client only]
The field "TCP Conn. (TCP connection) indicates the status of the connected at TCP level
(OK = Connected established at TCP level)
· MMS Conn. [Client only]
This field indicates the status of the connection at MMS level (OK = Connection is
established at TCP level and MMS level, datasets are created and spontaneous
transmission is possible)
· Data [Client only]
The field "Data" is OK if all 61850-Data (transmit/receive direction) parameterized in the
SIP message address conversion also exist in the remote station.
If NOK, this link can be used to display the missing data.
· ET03 is
This field displays the set parameters connection definition | own mode as the
role of the own station for every connection.
· Server (Vendor/Model/Version) [Client only]
This field displays the manufacturer information of the connected 61850 device (Server)
read out by the Client.
· Req. Dir. (NV) (Request Directory Named Variables) [Client only]
By clicking the mouse button on the link "Request’ registered in the field "Req. Dir. (NV)",
the Directory (data model) of all "Named Variables" is read out and displayed.
· File Dir. [Client only]
By clicking the mouse button on the link "Request" registered in the field "File Dir.", the File
Directory is read out and displayed.
Displayed are e.g. files of recorded disturbance records in IEEE Comtrade format.

DC0-023-2.12, Edition 06.2017
Named Variables Directory of the Station [Client only]

Via the web page Diagnosis | Connections | Req. Dir. (NV) of the 61850-Client, the
Named Variables Directory of the 61850 remote station (Server) can be read out and
displayed.
The NV Directory contains the following information:
· “Domains (Logical Devices)”

Listing of all Logical Devices of the IEC 61850 Station.
e.g. CTRL Control
DR Disturbance Recording
EXT Extras
MEAS Measured Value Acquisition,
PROT Protection.
· “NVL (Datasets)”
Listing of the NVL (Named Variable Lists) per Logical Device.
· “NV (Data)”
Listing of all NV (Named Variables) per Logical Device.
The current states of the data attributes of the Named Variables ("Data Attribute Reference")
can be read out directly from the 61850 remote station (Server) with "Read" via the web page
in the 61850 Client.
The readout is only supported for basic types! The readout of higher-level structures "Data
References" is not supported. With an attempt to read out a higher-level structure, the error
message "structure. Please use a single leaf" is displayed!
The current state of the selected data attribute is displayed in the window (below). Through
the readout, data in the 61850 device cannot be deleted unintentionally.

Edition 06.2017, DC0-023-2.12
File Directory of the Station [Client only]

On the web page Diagnosis | Connections | File Dir. the File Directory of the 61850
remote station (Server) can be displayed in the 61850-Client.
A file can be displayed by clicking the left mouse button on the link stored in the filename or
saved on the local PC by clicking the right mouse button and selecting the function "Save file
as…". The readout and saving of the file is controlled by the protocol firmware.
The files read out via the web server are not deleted in the 61850 remote station.
Detail Routing Client TRA, Detail Routing Client REC [Client only]
The address conversion from SICAM RTUs internal IEC 60870-5-101/104 format to the
IEC 61850 format in transmit direction and the address conversion from IEC 61850 format to
the SICAM RTUs internal IEC 60870-5-101/104 format in receive direction is parameterized
with the TOOLBOX-II in the OPM and generated with the function SIP message address
conversion.
On the web page Diagnosis | Detail Routing Client TRA all routing information
generated for the protocol element in transmit direction are displayed.

DC0-023-2.12, Edition 06.2017
On the web page Diagnosis | Detail Routing Client REC all routing information
converted for the protocol element in receive direction are displayed.
A separate line is created in the routing information for every IEC 60870-5-101/104 data point.
Entries with incorrect parameter setting are indicated red (e.g. wrong TI, …).
Entries with data points that do not exist in the server are indicated blue.
With incorrect IEC 61850 address an error message is displayed in the field "Error". The
61850 address is checked by the protocol firmware after startup for all routing information
from the designation "Logical Node" on.
· Type
SICAM RTUs internal defined/unambiguous number for the detailed routing record type.
· TI, CASDU1, CASDU2, IOA1, IOA2, IOA3
5-stage address and type identification according to IEC 60870-5-101/104.
· Value
Additional attribute for the differentiation of multiple equal IEC 61850 addresses with
different IEC 60870-5-101/104 addresses (e.g. Mod.ctlVal from single commands).
· Ctrltype [Client only]
In this field, the Control Type (Ctrltype) for the data point read out from the 61850 Server is
displayed. The possible Control Types are also displayed on the web page.
· Internal
In the field "Internal" a internal status information is displayed for every data point.
The internal status information is formed from individual internal binary states and
displayed as a number.
The following status numbers are of significance for the user:
01…Data point exists in directory / no spontaneous transmission (is interrogated cyclic)
05…Data point exists in directory / spontaneous transmission
09…Data point exists in directory / spontaneous transmission

Edition 06.2017, DC0-023-2.12
· IM
In the field "IM" (Interlocking Messaging) the current state of the command enabling for
this data point is displayed. The command enabling can be controlled by binary
information and is used for "overlapping command interlocks".
· Attrib
In the field "Attrib", internal information is displayed which is only of significance for the
development experts.
· IEC61850 Address
In this field the parameterized IEC 61850 address of the data point is displayed. A basic
type ("Data Attribute Reference") must always be specified as IEC 61850 address.
· Error
In the field "Error" an error information is displayed for incorrectly parameterized
IEC 61850 address.
· Data
In this field the current status of the IEC 60870-5-101/104 data point including the quality
bits and the time information is displayed.
Detail Routing Server TRA, Detail Routing Server REC [Server only]
The address conversion from SICAM RTUs internal IEC 60870-5-101/104 format to the IEC
61850 format in transmit direction and the address conversion from IEC 61850 format to the
SICAM RTUs internal IEC 60870-5-101/104 format in receive direction is parameterized with
the SICAM TOOLBOX II in the OPM II and generated with the function SIP message address
conversion.
On the web page Diagnosis | Detail Routing Server TRA all routing information
converted for the protocol element in transmit direction are displayed.
On the web page Diagnosis | Detail Routing Server REC all routing information
converted for the protocol element in receive direction are displayed.
A separate line is created in the routing information for each IEC 60870-5-101/104 data point.
Routing entries with incorrect parameter setting are indicated red (e.g. wrong TI, …).
Routing entries with data points that do not exist in the server are indicated blue.

DC0-023-2.12, Edition 06.2017
With incorrect IEC 61850 address an error message is displayed in the field "Error". The
61850 address is checked by the protocol firmware after startup for all routing information
from the designation "Logical Node" on.
· Type
SICAM RTUs internal defined/unambiguous number for the detailed routing record type.
· Sel. (Station-selective/Global)
In the field "Sel." (selective) it is displayed whether the routing of the data point is
applicable for selected selective stations (Connections) or globally for all connections with
server function (Sel: 0=global / 1=selective).
With selective assignment, up to 10 different station numbers can be specified for each
data point.
· SA, SB, SC, SD, SE, SF, SG, SH, SI, SJ (SICAM RTUs internal station number)
In the fields "SA", .. "SJ" for each data point the selected station numbers (connections)
are displayed to which the data point has been assigned.
· IEC61850 Address
In this field the parameterized IEC 61850 address of the data point is displayed.
A basic type ("Data Attribute Reference") must always be specified as IEC 61850 address.
· Error
In the field "Error" an error information is displayed for incorrectly parameterized
IEC 61850 address.
· Data
In this field the current status of the IEC 60870-5-101/104 data point is displayed.
Control Location [Client only]

On this web page the control locations set for the client are displayed.
If the function "control location" is activated, commands from the protocol element with the
“Client” function are only then transmitted to the addressed station (61850 remote station) if
the command has been sent from an enabled control location (originator address).
The control location can be set globally for all connections or selectively per connection by
means of protocol control messages.
The control location (originator address) is a definition according to IEC 60870-5-101/104 and
is supported by the protocol element. For details about the function "Control Location" refer to
section "Command Transmission/Control Location".

Edition 06.2017, DC0-023-2.12
Directories Server [Server only]

On this web page the directories created in the server are displayed.
The directories for the 61850 Server are generated by the protocol element from the process-
technical parameters (=SIP message address conversion) for the 61850 interface.
The time required by the protocol element for the generation and checking of the directories is
displayed on the web page in the field “Time to check/create Directory (mm:ss)”. The
measurement of the time begins after startup of the protocol element.
The data in the directories can be displayed in the following ways:
· “Plain Directories”
In this directory all data is displayed in alphabetical order.
· “Hierarchical Directories”
In this directory all data is displayed in hierarchically structured form.
Directory-specific information:
· Directory Index
The field "Directory Index" is only displayed for SICAM RTUs components with 61850-
Server function and is an index number to a directory created in the server (data model).
Index numbers with the same value point to the same directory.
By clicking the mouse button on the registered "Directory Index" the data model of the
selected directories is displayed.
· Directory ID
The field "Directory ID" (directory identification number) is only displayed for SICAM RTUs
components with 61850-Server function and is an unambiguous identification number for a
directory created in the server (data model). The "Directory ID" is unambiguous within a
device.
By clicking the mouse button on the registered "Directory ID", the assigned data model of
the 61850-Station (remote station) is displayed.
· Directory Info
The field "Directory Info" (Directory Information) is only displayed for SICAM RTUs
components with 61850-Server function.
By clicking the mouse button on "Show" in the field "Directory Info", detailed information of
the 61850 server is displayed for the generated data model of the selected directories.
· Station
The field "Station" displays all internal station numbers (connection numbers) which use
this directory.
Note: If several remote stations use exactly the same data model (in transmit and in
receive direction), internally only 1 directory is created for this by the protocol element.

DC0-023-2.12, Edition 06.2017
· Error
During the generation of the directories, the protocol element performs extensive checks.
In the field "Error", an error information is entered for fatal errors (e.g. no memory
available).
Here, "Success" must always be entered, otherwise the protocol element does not run!
In the event of an error, the parameters of the plant must be transferred to the protocol
experts for analysis.
Directory Server "Plain" [Server only]

On this web page the selected directory of the server is displayed in alphabetical order.
Directory-specific Information:
· “Named Variable Lists (NVL)”

In the list "Named Variable Lists (NVL)" all datasets generated for the selected server
directory are displayed.
Datasets are only created for those data, that are to be transmitted from one 61850 Server
to one 61850 Client.
For data in the direction 61850-Server → 61850-Client, no data sets are created.
· “Named Variables (NV)”
In the list "Named Variables (NV)" all attributes of the entire directories are displayed.
The directory (=MMS Directory) contains the assigned datasets (data from Server →
Client) and all data from Client → Server.

Edition 06.2017, DC0-023-2.12
Directory Server "Hierarchical" [Server only]

On this web page, the selected server directory is displayed in hierarchically structured form.
Directory Information [Server only]

On this web page, detailed information of the data model generated for the selected directory
of the 61850 server is displayed.
The data model is generated during startup by the protocol element from the process-
technical parameters (SIP message address conversion). The data model forms the directory
(=MMS Directory) for the communication according to IEC 61850.
The following information is displayed for each "Logical Device":
· Index
The field displays only a consecutive number that is assigned by the protocol element for
the parameterized logical devices and is of no further significance.
· Domain (LD)
In the field "Domain (LD)" (Domain Logical Device) the Logical Devices created in the
server directory are displayed.
· CntLN
In the field "CntLN" (Count Logical Nodes) the number of Logical Nodes generated per
logical device is displayed.
· Cnt NVL (Datasets)
In the field "Cnt NVL (Datasets)" (Count Named Variable Lists) the number of "Named
Variable Lists (Dataset)" generated per Logical Device is displayed.
· Cnt Attrib
In the field "Cnt Attrib" (Count Attributes) the number of Attributes generated per logical
device is displayed.

DC0-023-2.12, Edition 06.2017
GOOSE [Server only]

On this web page, details of the GOOSE header information are displayed. The datasets for
the GOOSE applications are generated from the process-technical parameters (SIP message
address conversion) during startup.
The sum of the transmitted/received GOOSE applications from startup of the protocol element
is displayed on the web page.
The following information is displayed for each GOOSE application:
· Index
The field "Index" displays the parameterized number for the respective GOOSE
application. This index is only required for the SICAM RTUs protocol element and is not
transmitted.
· Error
In the field "Error" a detailed error information is displayed for each Goose application
(since startup of the own device). Possible error information:
Blank field ……….. OK
Timeout ………….. GOOSE application has already been received once, but presently
this is no longer received.
Data Set Wrong … The structure of the dataset received for the GOOSE application
does not correspond with the parameter setting in the own device.
Never Received … The dataset for the parameterized GOOSE application has never
been received.
· Dir
In the field "Dir" (Direction) the transmission direction of the respective GOOSE application
is displayed.
REC = Subscriber (receiver)
TRA = Publisher (transmitter)
· GoCBRef
In the field "GoCBref" the GOOSE Control Block Reference is displayed. This is
unambiguous in the device and the network.
· goID
In the field "goID" an unambiguous GOOSE identification reference is displayed. This
identifier is unambiguous for each device and for each network and is also transmitted with
GOOSE.
· dsRef
A specific dataset is created in the SICAM RTUs server for every GOOSE application.
In the field "dsRef" the Dataset Reference per device is displayed.

Edition 06.2017, DC0-023-2.12
· MAC Goose
In the field "MAC Goose" (MAC-address) the parameterized MAC-address of the GOOSE
application is displayed.
The MAC-address is a "Multicast MAC-address" – several different remote stations can
receive data from one MAC-address.
· MAC Source
In the field "MAC Source" (MAC-address) the unambiguous MAC-address of that device
which has transmitted the GOOSE application is displayed.
Note:
If due to an incorrect parameter setting, an unambiguous GOOSE application is to be transmitted from
several devices (e.g. through the copying of parameters), the MAC-addresses of the devices are
displayed alternating in the field "MAC Source".
· configRev
In the field "configRev" an unambiguous revision identifier of the GOOSE application is
entered.
Note: The revision identifier is generally not used presently and by default is assigned with
"1" !
· VLAN_VID
In the field "VLAN_VID" the parameterized VLAN identification is displayed.
· VLAN_Prio
In the field "VLAN-Prio" the parameterized VLAN priority is displayed.
· Cnt TRA/REC
In the field "CntTRA/REC" it is displayed how often the GOOSE application has been
received or transmitted by the protocol element since startup.
· Cnt DS wrong
In the field "Cnt DS wrong" it is displayed how often a GOOSE application has been
received with wrong data set by the protocol element since startup.
· Cnt timeout
In the field "Cnt timeout" it is displayed how often a timeout has been detected by the
protocol element during reception of a GOOSE application since startup.
· Max timeout
In the field "Max timeout", the maximum TIMEOUT presently applicable for the expected
reception of the respective GOOSE application is displayed.

DC0-023-2.12, Edition 06.2017
The structure of the GOOSE datasets is displayed for each GOOSE-Index (GOOSE
application) as follows.
Example: "GOOSE Application Index-1,2,4"
GOOSE Application Index-1,2,4:
In the field "GoCBRef" the parameterized GOOSE Control Block Reference (=MMS address)
is displayed.
The GOOSE Control Block is generated by the protocol element for each GOOSE application
from the parameters of the goose definitions and can be read by the Client but not written.
With the integrated web server, the GOOSE Control Block can be read out in the directory of
the server under the Functional Constraint "GO".

Edition 06.2017, DC0-023-2.12
Example: "GoCBRef" = MEAS/LLN0$GO$gcb01
à GOOSE Control Block
Developer Information
On these websites, system-internal data of the protocol firmware for the software development
specialists can be read out for troubleshooting.
The description of these sites is not subject to this manual.

DC0-023-2.12, Edition 06.2017
9.7.2 IEC 61850 Edition 2 [Client + Server]
This information can be read out with a common Web Browser, as for instance Microsoft
Internet Explorer ®. For the access to the web server the communications protocol "HTTP
By default the integrated web server is deactivated for security reasons. If needed, it can be
enabled for access by the user with the parameter HTTP web server.
Protocol elements for IEC 61850 Edition 2 use websites with a renewed design.
Note

Edition 06.2017, DC0-023-2.12
· Overview
· Connection information (Connections)
· Client information
─ Display of the Routing information for the client function in transmit direction
(Client | Routing transmit)
─ Display of the Routing information for the client function in receive direction
(Client | Routing receive)
─ Display of the control locations with command authority (Client | Control location)
─ Display of the information for the disturbance record transmission
(Client | File transfer)
─ Display of the last commands (Client | Command log)
· Server information
─ Display of the Routing information for the client function in transmit direction
(Server | Routing transmit)
─ Display of the Routing information for the client function in receive direction
(Server | Routing receive)
─ Display of the directory data on the server (Server | Directory)
─ Display of the information for the GOOSE function (Server | GOOSE)
─ Display of the own COD file (Server | CID File)
─ Display of the last commands (Server | Command log)
· System-internal data for development specialists

DC0-023-2.12, Edition 06.2017
Overview
This web page is the start page of the web server.
In the Overview the following information is displayed:
· Firmware
Designation of the used firmware
· Revision
Current revision level
· Hardware
Name of the interface module
· Firmware number
Number of the used firmware
· Date and Time
System time in the BSE
· Region number, Component number, BSE, ZSE, IP address, Default gateway, Subnet
mask, MAC address
The parameterized or current values are displayed next to the respective fields.
· Redundancy
The current redundancy state of the protocol element is displayed next to the field
"Redundancy".
Firmware active ……..……..The redundancy state of the protocol element is "ACTIVE"
Firmware passive …..……..The redundancy state of the protocol element is "PASSIVE"
· Firmware status
The status of the firmware is displayed next to the field "Firmware".
OK ……………………..……..Firmware is running error-free
KILL, No: #### (0x####)……A serious error has occurred → notify manufacturer!
The number displayed (decimal, and HEX) supply the
developer with more specific information about the cause of
the error.

Edition 06.2017, DC0-023-2.12
Connections
On this web page the status information of the parameterized connections is displayed.

· IP address"
The field "IP Address" displays the IP address of the remote station parameterized in the
parameters for connection definition. An IP address marked red signifies that this is
presently not reachable.
By clicking the mouse button on the IP address, via a link the web page of a web server
possibly implemented in the remote station is displayed.
· conn
The field "conn" (TCP connection) indicates the status of the connected at TCP level (OK
= Connected established at TCP level).
· TCP conn [Client only]
The field "TCP Conn." (TCP connection) indicates the status of the connected at TCP level
(OK = Connected established at TCP level)
· MMS conn [Client only]
Indicates the status of the connection at MMS level (OK = Connection is established at
TCP level and MMS level, datasets are created and spontaneous transmission is possible)
· Data [Client only]
The field "Data" is OK if all 61850-Data (transmit/receive direction) parameterized in the
SIP message address conversion also exist in the remote station.
If NOK, then the corresponding missing addresses can be filtered in the web page “Client
– Routing transmit”/”Client – Routing receive”.
· Server (Vendor/Model/Version) [Client only]
This field displays the manufacturer information of the connected 61850 device (Server)
read out by the Client.
· Request NV (Request Directory Named Variables) [Client only]
By clicking the mouse button on the link "Request’ registered in the field, the Directory
(data model) of all "Named Variables" is read out and displayed.
· Request files [Client only]
By clicking the mouse button on the link "Request” registered in the field, the File Directory
is read out and displayed.
Displayed are e.g. files of recorded disturbance records in IEEE Comtrade format.
Entries of failed connections (MMS and TCP level) are indicated with red color █.
If the connection is established on TCP level, but not on MMS level, then these entries are
indicated with blue color █.

DC0-023-2.12, Edition 06.2017
Client - Named Variables Directory of the Station

Via this web page of the 61850-Client, the Named Variables Directory of the 61850 remote
station (Server) can be read out and displayed.
The NV Directory contains the following information:
· "Domain / Logical Device"

Listing of all Logical Devices of the IEC 61850 Station
e.g. CTRL Control
DR Disturbance Recording
MEAS Measured Value Acquisition,
PROT Protection.
· "Named Variable List (NVL) / Dataset"
Listing of the NVL per Logical Device
· "Named Variable (NV) / Data Object"
Listing of all NV per Logical Device
The current states of the data attributes of the Named Variables ("Data Attribute Reference")
can be read out directly from the 61850 remote station (Server) with Read via the web page in
the 61850 Client.

Edition 06.2017, DC0-023-2.12
The readout is only supported for basic types! The readout of higher-level structures "Data
References" is not supported. With an attempt to read out a higher-level structure, the error
message "structure. Please use a single leaf" is displayed!
The current state of the selected data attribute is displayed in the window at the bottom.
Through the readout, data in the 61850 device cannot be deleted unintentionally.
Client - File Directory of the Station

On this web page the File Directory of the 61850 remote station (Server) can be displayed in
the 61850-Client.
A file can be displayed by clicking the left mouse button on the link stored in the filename or
saved on the local PC by clicking the right mouse button and selecting the function Save
target as.... The readout and saving of the file is controlled by the protocol firmware.
The files read out via the web server are not deleted in the 61850 remote station.

DC0-023-2.12, Edition 06.2017
Client - Routing Transmit, Client - Routing Receive

conversion.
On the web page Client - Routing transmit all routing information generated for the
protocol element in transmit direction are displayed.
On the web page Client - Routing receive all routing information converted for the
protocol element in receive direction are displayed.

Edition 06.2017, DC0-023-2.12
Entries with incorrect parameter setting are marked red █ (e.g. wrong TI, …).
Entries with data points that do not exist in the server are marked blue █.
With incorrect IEC 61850 address, an error message is displayed in the field "Error".
If needed, the display can be filtered by means of selection
─ all
─ in server database
─ not in server database
─ error
· Error
In this field an error information is displayed for incorrectly parameterized IEC 61850
address.
· Value
· IEC61850 Address
· CDC
In this field the parameterized IEC 61850 Common Data Class of the data point is
displayed.
· Kind
In this field the kind of transmission is displayed:
spont … data point is transmitted spontaneously per Report
poll …… data point is interrogated cyclically
· Ctrltype
displayed.
The possible Control Types are also displayed on the web page.
· Blocked
In this field the current state of the command enabling for this data point is displayed. The
command enabling can be controlled by binary information and is used for "overlapping
command interlocks" (interlocking information for the ON/OFF state: BL_ON, BL_OFF).
· Data
· Quality
In this field the quality identification is displayed (NT, IV, BL, SB, EI, OV).
· Time
In this field the time tag of the data point is displayed.

DC0-023-2.12, Edition 06.2017
Client - Control Location

On this web page the control locations set for the client are displayed.
If the function "control location" is activated, commands from the protocol element with the
“Client” function are only then transmitted to the addressed station (61850 remote station) if
the command has been sent from an enabled control location (originator address).
The control location (originator address) is a definition according to IEC 60870-5-101/104 and
is supported by the protocol element. The control location can be set globally for all
connections or selectively per connection by means of protocol control messages.
For details on the function "Control Location" refer to section 9.2.7.2, Control Location [Client
only].
Client - File Transfer

On this web page the information for the disturbance record transmission to SICAM DISTO is
displayed, if this is parameterized.
Information on the transmitted user data containers:
· Direction
In this field the transmission direction of the container is displayed.
The display below describes the state of the last/current data transmission.
For details on the function “File Transfer” refer to section 9.2.9, File Transfer (Disturbance
Records).

Edition 06.2017, DC0-023-2.12
Client - Command Log

On this web page the record of the respective last commands (ACT, CON, TERM) in context
with IEC 60870-5-101/104 and IEC 61850 is displayed.
Command-specific status information:
· Time
In this field the time tag of the command is displayed.
· Direction
In this field the command direction and the command kind are displayed.
· Reason
In this field the identification “pos”/”neg” of the command is displayed.
5-stage address and type identification acc. to IEC 60870-5-101/104.
· IEC61850 Address
· Origin
In this field the control location (originator address) acc. to IEC 60870-5-101/104 is
displayed.
· AddCause
In this field the cause for a negative command termination is displayed.
· Data
· QU
In this field the command output qualifier is displayed.

DC0-023-2.12, Edition 06.2017
Server - Routing Transmit, Server - Routing Receive

conversion.
On the web page Client - Routing transmit all routing information generated for the
protocol element in transmit direction are displayed.
On the web page Client - Routing receive all routing information converted for the
protocol element in receive direction are displayed.

Edition 06.2017, DC0-023-2.12
Entries with incorrect parameter setting are marked red █ (e.g. wrong TI, …).
Entries with data points that do not exist in the server are marked blue █.
With incorrect IEC 61850 address an error message is displayed in the field "Error".
If needed, the display can be filtered by means of selection
─ all
─ error
· Error
In this field an error information is displayed for incorrectly parameterized IEC 61850
address.
· ValOFF
Value for the binary information state OFF
· ValON
Value for the binary information state ON
· Value
· IEC61850 Address
· CDC
In this field the parameterized IEC 61850 Common Data Class of the data point is
displayed.
· Ctrltype
displayed.
The possible Control Types are also displayed on the web page.
· Goose
In this field the GOOSE index is displayed.
· Data
· Quality
In this field the quality identification is displayed (NT, IV, BL, SB, EI, OV).
· Time
In this field the time tag of the data point is displayed.

DC0-023-2.12, Edition 06.2017
Server - Directory
On this web page, detailed information of the data model generated for the selected directory
of the 61850 server is displayed.
The data model is generated during startup by the protocol element from the process-
technical parameters (SIP message address conversion). The data model forms the directory
for the communication according to IEC 61850.
The following information is displayed:
· IED name
In this field the Logical Device created in the directory of the Server is displayed.
· Count logical devices
In this field the number of Logical Nodes generated per Logical Device is displayed.
· Count datasets
In this field the number of "Named Variable Lists (Dataset)" generated per Logical Device
is displayed.
· Count attributes
In this field the number of Attributes generated per Logical Device is displayed.
· Count reports unbufferd
In this field the number of Unbuffered Reports generated per Logical Device is displayed.
· Count reports bufferd
In this field the number of Buffered Reports generated per Logical Device is displayed.
The data in the directories can be displayed in the following ways:
· Show directory plain

In this directory all data is displayed in alphabetical order.
· Show directory tree
In this directory all data is displayed in hierarchically structured form.

Edition 06.2017, DC0-023-2.12
Server - Directory plain view

On this web page the selected directory of the server is displayed in alphabetical order.
In the list "Datasets" all datasets generated for the selected server directory are displayed.
Datasets are only created for that data which is to be transmitted from one 61850 Server to
one 61850 Client. For data in the direction 61850-Server à 61850-Client, no datasets are
created.
The following information is displayed:
· Nr
In this field the consecutive number created in the directory of the Server is displayed.
· Nr LD
In this field the number of the Logical Device is displayed.
· Logical device
In this field the parameterized name of the Logical Device is displayed.
· Nr DS
In this field the number of Datasets is displayed.
· Dataset
In this field the parameterized name of the Dataset is displayed.
· Nr DO
In this field the number of Data Object is displayed.
· Data object
In this field the parameterized name of the Data Object is displayed.

DC0-023-2.12, Edition 06.2017
Server - Directory tree view

On this web page, the selected server directory is displayed in hierarchically structured form.
Server - Goose
On this web page details of the GOOSE-Header information are displayed. The datasets for
the GOOSE applications are generated from the process-technical parameters (SIP message
address conversion) during startup.
· “Goose publish”
In the list “Goose publish” the sum of transmitted GOOSE applications since startup of the
protocol element is displayed
· “Goose subscribe”
In the list “Goose subscribe” the sum of received GOOSE applications since startup of the
protocol element is displayed

Edition 06.2017, DC0-023-2.12
The following information is displayed for each GOOSE application:
· Index
The field "Index" displays the parameterized number for the respective GOOSE
application. This index is only required for the SICAM RTUs protocol element and is not
transmitted.
· Error
In the field "Error" a detailed error information is displayed for each Goose application
(since startup of the own device). Possible error information:
Blank field ……….. OK
Timeout ………….. GOOSE application has already been received once, but presently
this is no longer received.
Data Set Wrong … The structure of the dataset received for the GOOSE application
does not correspond with the parameter setting in the own device.
Never Received … The dataset for the parameterized GOOSE application has never
been received.
· GoCBRef
In the field "GoCBref" the GOOSE Control Block Reference is displayed. This is
unambiguous in the device and the network.
· goID
In the field "goID" an unambiguous GOOSE identification reference is displayed. This
identifier is unambiguous for each device and for each network and is also transmitted with
GOOSE.
· MAC address
In the field "MAC Goose" (MAC-address) the parameterized MAC-address of the GOOSE
application is displayed.
The MAC-address is a "Multicast MAC-address" – several different remote stations can
receive data from one MAC-address.
· Src MAC address
In the field "Src MAC address" the unambiguous MAC-address of that device which has
transmitted the GOOSE application is displayed.
Note:
If due to an incorrect parameter setting, an unambiguous GOOSE application is to be transmitted from
several devices (e.g. through the copying of parameters), the MAC-addresses of the devices are
displayed alternating in the field "MAC Source".
· AppID (HEX)
In the field "AppID" the parameterized identification of the GOOSE application is displayed.
· configRev
In the field "configRev" an unambiguous revision identifier of the GOOSE application is
entered.
Note: The revision identifier is generally not used presently and by default is assigned with
"1" !
· VLAN_VID
In the field "VLAN_VID" the parameterized VLAN identification is displayed.
· VLAN_Prio
In the field "VLAN-Prio" the parameterized VLAN priority is displayed.
· St#
In the field "St#" the state number is displayed.
· Sq#
In the field "Sq#" the sequence number is displayed.
· Min. time
In the field "Min. time" the minimal repetition time is displayed.
· Max. time
In the field "Max. time" the maximal repetition time is displayed.

DC0-023-2.12, Edition 06.2017
· Hold time
In the field "Hold time" the current repetition time is displayed.
· Last change
In the field "Last change" the time of the latest change of the GOOSE application is
displayed.
· Test
In the field "Test" the additional attribute “GOOSE generated by means of test” is
displayed.
· nds Com
In the field "nds Com" the additional attribute “GOOSE generated by means of
commissioning” is displayed.
Server – CID File

On this web page the own CID file is displayed.

Edition 06.2017, DC0-023-2.12
Server – Command log

On this web page the record of the respective last commands (ACT, CON, TERM) in context
with IEC 60870-5-101/104 and IEC 61850 is displayed.
Command-specific status information:
· Time
In this field the time tag of the command is displayed.
· Direction
In this field the command direction and the command kind are displayed.
· Reason
In this field the identification “pos”/”neg” of the command is displayed.
5-stage address and type identification acc. to IEC 60870-5-101/104.
· IEC61850 Address
· Origin
In this field the control location (originator address) acc. to IEC 60870-5-101/104 is
displayed.
· AddCause
In this field the cause for a negative command termination is displayed.
· Data

DC0-023-2.12, Edition 06.2017
Developer Information
On these web pages, system-internal data of the protocol firmware for the software
development specialists can be read out for troubleshooting.
The description of these sites is not subject to this manual.

Edition 06.2017, DC0-023-2.12
10 SNMPv3 Agent
Contents
10.1 Introduction .................................................................................................. 582

10.2 SNMP .......................................................................................................... 585
10.3 SNMP MIB – Management Information Base ................................................ 589
10.4 SNMP Variables ........................................................................................... 591
This chapter describes the protocol SNMPv3 Agent which is integrated in the firmware of the

DC0-023-2.12, Edition 06.2017
SNMPv3 Agent
10.1 Introduction
SNMP (Simple Network Management Protocol) is a network protocol used to monitor or

control network components (e.g. Router, Switches, Server or Automation units (PLC, RTUs))
from a central station. The protocol controls the communication between the monitored
devices (SNMP-Agents) and the monitoring station (SNMP-Manager).
Due to the integration of a SNMPv3 Agent in SICAM RTUs it is possible to read out “SNMP
Variables“ (stored in the MIB = Management Information Base) via network with a standard
network management software (“SNMP Manager“). The information and data transmitted with
SNMP are displayed according to their functionality in the SNMP Manager in some kind of
tree structure.
The following firmwares are available for the different systems:
Firmware Standard and function System
CP-8000/CPC80 Central processing/communication A8000 CP-8000
CP-2016/CPCX26 Central processing/communication SICAM AK3

Edition 06.2017, DC0-023-2.12
SNMPv3 Agent
10.2 Features and Functions
(CP-8000/CP-802x)
A8000 Series
SICAM AK 3
SICAM 230
Common functions
(CP-2016)
3 party
rd
· SNMP
− SNMPv2 ü ü
− SNMPv3 ü ü
- Users 4 4
− SNMP Manager ü ü
− SNMP Agent ü ü
· Supported ports
− Port 161/ UDP ü ü
− Port 162/ UDP (TRAPs) ü ü
· SNMP functions
− GET ü ü
to request a management data record
− GETNEXT ü ü
to request the subsequent data record (to pass through tables)
− GETBULK ü ü
to request several data records at once, e.g. several rows of a table (available from SNMPv2)
− SET 1) 1)
write of SNMP variables
− RESPONSE ü ü
reply on GET, GETNEXT, GETBULK
− TRAP
spontaneous data from SNMP Agent to SNMP Manager
ü2) ü2)
· Supported MIBs
− sicamRTUs ü ü
− MIB-2 (RFC1213) ü ü 4)
− Ethernet-MIB (RFC3635) ü 3) ü 3) 4)
− Host-Resources-MIB (RFC2790) ü 3) ü 3)
− USM-MIB (RFC2574) ü ü
− VACM-MIB (RFC2575) ü ü
· Supported SNMP variables MCPU (rough overview)
− Plant name ü ü
− System-technical region and component number ü ü
− Firmware revision ü ü
− Uptime ü ü
− Port Status ü ü
− Central error table ü ü
− TRAP “History“ (read back of last sent traps) ü ü
- max. no of stored TRAPs 50 50
- Store TRAP “History“ at Reset/Restart
· Supported SNMP variables CCPUs, PREs, PEs
· SNMPv3: “Security Level“
− noAuthnoPriv
− authNoPriv
− authPriv (communication with authentication and encryption) ü ü
· SNMPv3: “auth Protocol“ (protocol for authentication “user name, password“)
− MD5 (Message Digest Algorithm 5) ü ü

− SHA, SHA1 (Secure Hash Algorithm)

DC0-023-2.12, Edition 06.2017
SNMPv3 Agent
(CP-8000/CP-802x)
A8000 Series
SICAM AK 3
SICAM 230
Common functions
(CP-2016)
3 party
rd
· SNMPv3: “Privacy Protocol“ (protocol for encryption)
− DES-56 Bit (Data Encryption Standard) ü ü

− AES (Advanced Encryption Standard)
− 3-DES (Triple Data Encryption Standard)
· Security: Encrypted storage of passwords ü ü
1) SET is only supported for following SNMP variables of MIB-2:
sysName , sysLocation, sysContact
All other SNMP variables in SICAM AK 3 can only be read and not be changed via SNMP.
2) Traps are sent according SNMP V3 with security Level = “authPriv“ using user name = “Trap“
and parameterized passwords for authentication and encryption.
3) This MIBs are supported only with restricted functionality.
The supported OID’s are defined in MIB’s provided for SICAM RTUs.
4) The port specific OID’s can only be read for X0, X1 of CP-2016.
OID’s for other ports e.g. X2, X3 of CP-2016 or X0-X3 of CP-2019 are not supported.
The port specific OID’s for port X0, X1 of CP-2016 will be shown combined
(no port specific information for this ports).
OSI Layer Model – Including SNMP

Example of OSI layer model including SNMP and IEC 61850 and IEC 60870-5-104.

Mapping Mapping
7 IEC 60870-5-101 <-> IEC 61850 IEC 60870-5-101 <-> IEC 60870-5-104 Remote
Connection
IEC 61850 for
ACSI-Services IEC60870-5-104 SICAM PRE-Status Time
6 Client APDU TOOLBOX II WEB-Server Sync.
Peer-to-Peer Server
MMS APCI NTP SNMP

5 HTTP, HTTPS
SNTP
Sampled Value
Exchange
GOOSE
4 TCP UDP
3 IP
ICMP
2 IP Encapsulation ARP
Priority Tagging
1 (IEEE802.1Q + IEEE802.1p) Ethernet
ADPU Application Protocol Data Unit NTP Network Time Protocol

APCI Application Protocol Control Information SNTP Simple Network Time Protocol
ARP Address Resolution Protocol TCP Transmission Control Protocol
RSTP Rapid Spanning Tree Protocol UDP User Datagram Protocol
HTTP Hyper Text Transfer Protocol MMS Manufacturing Message Specification
HTTPS Hyper Text Transfer Protocol Secure GOOSE Generic Object Oriented Substation Events
SNMP Simple Network Management Protocol
ICMP Internet Control Message Protocol IP Encapsulation RFC 894
IP Internet Protocol

Edition 06.2017, DC0-023-2.12
SNMPv3 Agent
10.3 SNMP
The SNMP function in SICAM RTUs (SNMP Agent) can be enabled on basic system element
(BSE) with the parameter Network settings | SNMP | SNMP agent.
The required SNMP Version SNMPv2 (without security) or SNMPv3 (with security) can be
selected on basic system element (BSE) with the parameter Network settings | SNMP |
SNMP version.
Supported SNMP Versions:
· SNMPv3
─ SNMP requests from SNMP manager according SNMPv3 will be supported only
─ Traps will be sent to one SNMP manager according SNMPv3
Required parameters for security according SNMPv3:
─ security level (=authPriv)
─ authentication protocol (=MD5)
─ privacy protocol (=DES)
─ user name / password
· SNMPv2 + SNMPv3
─ SNMP requests from SNMP manager(s) according SNMPv2 or SNMPv3 will be
supported
─ Traps will be sent only to one SMNP manager according SNMPv3
─ password ”community string“ (for read/write)
─ security level (=authPriv)
─ authentication protocol (=MD5)
─ privacy protocol (=DES)
─ user name / password
10.3.1 SNMPv2
SNMPv2 supports only a “community string (= password)” as security for SNMP requests by
SNMP manager. The “community string“ is sent without encryption and has only low level of
security for SNMP requests.
The password for read community must be parameterized on basic system element (BSE)
with the parameter Network settings | SNMP | SNMPv2 | Password read
community.
The password for write community must be parameterized on basic system element (BSE)
with the parameter Network settings | SNMP | SNMPv2 | Password write
community.
Traps not supported with SNMPv2!

DC0-023-2.12, Edition 06.2017
SNMPv3 Agent
10.3.2 SNMPV3
SNMPv3 agent in SICAM RTUs supports subset of defined protocols in SNMPv3 for
authentication and encryption for SNMP requests by SNMP manager.
The security level for SNMPv3 can be selected on the basic system element (BSE) with the
parameter Network settings | SNMP | SNMPv3 | Security level.
Note: Only security level ”authPriv” is supported today!
SNMPv3 defines following Security Levels:
· authPriv = authentication with encryption

·
*)
noAuthnoPriv = no authentication / no encryption
·
*)
authnoPriv = authentication / no encryption
______
*) Note: This SNMP security level is not supported today!
Authentication protocol
The authentication protocol for SNMPv3 can be selected on the basic system element (BSE)
with the parameter Network settings | SNMP | SNMPv3 | Authentication
protocol.
Note: “MD5” is supported today only as authentication protocol!
SNMPv3 defines following authentication protocols:
· MD5 (Message Digest Algorithm)

·
*)
SHA (Secure Hash Algorithm)
______
*) Note: This authentication protocol is not supported today!
Encryption protocol
The encryption protocol (privacy protocol) for SNMPv3 can be selected on the basic system
element (BSE) with the parameter Network settings | SNMP | SNMPv3 | Privacy
protocol.
Note: “DES” is supported today only as privacy protocol!
SNMPv3 defines following protocols for encryption (privacy protocol):
· DES (Data Encryption Standard)

·
*)
AES (Secure Hash Algorithm)
·
*)
3-DES
______
*) Note: These protocols for encryption are not supported today!

Edition 06.2017, DC0-023-2.12
SNMPv3 Agent
Users
SNMPv3 agent in SICAM RTUs supports following users:
· User 1
· User 2
· User 3
· User 4
· User ”Trap“
Each user can be enabled/disabled individually by parameter.
The parameters for user 1-4 can be selected on the basic system element (BSE) with the
parameters Network settings | SNMP | SNMPv3 | User #.
Parameters for User 1:
· Enable user
· Username
·
*)
Password for authentication or Password for authentication PSK
·
*)
Password for encryption or Password for encryption
· Enable write access for user
The modification of the SNMP variables sysName, sysLocation, sysContact (defined in
MIB-2) using SNMP SET can be enabled with this parameter.
______
*) PSK “Pre Shared Keys” only supported with Secure Password Storage enabled (parameter
settings for security)
Parameters for Users 2-4:

· Enable user
· Username
·
*)
Password for authentication PSK
·
*)
Password for encryption PSK
· Enable write access for user
The modification of the SNMP variables sysName, sysLocation, sysContact (defined in
MIB-2) using SNMP SET can be enabled with this parameter.
______
*) PSK “Pre Shared Keys” only supported with secure password storage enabled (parameter

DC0-023-2.12, Edition 06.2017
SNMPv3 Agent
SNMPv3 Traps
Selected SNMP variables can be sent spontaneous in case of change to one selected SNMP
Manager (see SNMP variables).
The sending of traps can be enabled on basic system element (BSE) with the parameter
Network settings | SNMP | SNMPv3 | Traps | Enable traps.
The parameters for traps can be set on basic system element (BSE) with the parameters
Network settings | SNMP | SNMPv3 | Traps.
Parameters for Traps:

· Enable traps
· Username = “Trap”
The username for function traps is fixed with “Trap” and cannot be modified.
· IP-Address for SNMP manager (traps)
Traps will be sent to SNMP manager with this IP address only.
·
*)
Password for authentication PSK
Password for authentication used for sending traps.
·
*)
Password for encryption PSK
Password for encryption used for sending traps.
Diagnosis traps
The sending of diagnostic information as traps can be enabled/disabled with this
parameter.
______
*) PSK “Pre Shared Keys” only supported with secure password storage enabled (parameter
SNMPv3 TRAP History

For selected SNMP Traps a limited number of last sent SNMP Traps can be read as “Trap
History“. The last 50 sent Traps provided as SNMP table can be read using GET / GETBULK /
GETNEXT (see SNMP variables).
Note: TRAP history will be deleted in case of reset or power up!

Edition 06.2017, DC0-023-2.12
SNMPv3 Agent
10.4 SNMP MIB – Management Information Base
The management information base describes the information, which can be retrieved or
modified via a network management protocol (e.g. SNMP). This information’s are named
"Managed Objects". These are description files, in which the single values are listed in table
form. Each component has a specific MIB.
SNMP Manager SNMP Get SNMP Agent

Object Data type OID OID = 1.3.6.1.2.1.1.1.0
Description Text 1.3.6.1.2.1.1.1.1
Object ID OID 1.3.6.1.2.1.1.1.2
SNMP Response
Start time Time 1.3.6.1.2.1.1.1.3
Contact Text 1.3.6.1.2.1.1.1.4 OID = 1.3.6.1.2.1.1.1.0
Name Text 1.3.6.1.2.1.1.1.5 Value = „Router” MIB
Location Text 1.3.6.1.2.1.1.1.6 Data type = Text

DC0-023-2.12, Edition 06.2017
SNMPv3 Agent
10.4.1 Structure of the SICAM RTUs MIB
iso.org.dod.internet.private.enterprise.SIEMENS.SICAMRTUs (1.3.6.1.4.1.22638.7)
CCITT ISO ISO-CCITT

0 1 2
standard registr. authority member body organization

0 1 2 3
DoD
6
Internet
1
directory management experimental private security SNMPv2 mail

1 2 3 4 5 6 7
MIB-2 enterprises
1 1
SIEMENS
22638
SIPROTEC 2010 products CS products Station unit Sentron SICAM sicamRTUs SICAM FRTU AMIS
1 2 3 4 5 6 7 8 9
generalInfo diagnostic History

1 10 11
auConfigurationOverview
1 sumDiagnosticTable SumDiagnosticTraps TrapHistoryTable
1 10 1
plant
1 classInternal diagnosticEvent trapHistoryEntry
1 1 1
plantID
2 classExternal diagnosticClass trapHistoryIndex
2 2
1
region
3 classCommunication diagnosticCondition trapHistoryTrapDate
3 3
2
component
4 classTest diagnosticDate trapHistoryTrapOID
4 4
3
classWarning trapHistoryTrapState
5
4
2
classBoardFailure trapHistoryTrapArg1
6 5
firmwareRevisionTable classFailure
1 trapHistoryTrapArg2
7 6
classStartUp trapHistoryTrapArg3
8 7
1
rIndex
1
rInstance
2
rName
3
rRevision
4
rDescription
5
rBseSse
6
rHwNr
7
rFwNr
8

Edition 06.2017, DC0-023-2.12
SNMPv3 Agent
10.5 SNMP Variables
The actual state of the SNMP variables can be read by the SNMP Manager using SNMP
Services GET / GETNEXT / GETBULK.
SICAM RTUs SNMP Agent supports SNMP requests from different SNMP Managers having
different IP addresses. The SNMP response will be sent back to the SNMP Manager who has
sent the SNMP request (GET / GETBULK / GETBULK).
SNMP variables of following MIB files will be supported:
· MIB-2 (RFC1213) 2)
· sicamRTUs
· Ethernet-MIB (RFC3635) 1) 2)
· Host-Resources-MIB (RFC2790) 1)
· USM-MIB (RFC2574)
· VACM-MIB (RFC2575)
______
1) These MIBs are supported only with restricted functionality.
The supported OIDs are defined in MIBs provided for SICAM RTUs.
2) SICAM AK 3:
The port specific OIDs can only be read for X0, X1 of CP-2016.
OIDs for other ports e.g. X2, X3 of CP-2016 or X0-X3 of CP-2019 are not supported.
The port specific OIDs for port X0, X1 of CP-2016 will be shown combined
(no port specific information for this ports).

DC0-023-2.12, Edition 06.2017
SNMPv3 Agent
10.5.1 SNMP Variables of MIB-2
Selected SNMP variables of MIB-2 can be set via SNMP SET.

After 1st startup this variables will be initialized with defined default values.
These variables can be modified by SNMP manager if required. This variables will be stored
power fail safe on SD card with actual state will be available also after reset/startup of SICAM
RTUs device.
The modification of the SNMP variables sysName, sysLocation, sysContact (defined in MIB-2)
using SNMP SET can be enabled with the parameter Network settings | SNMP |
SNMPv3 | User # | Enable write access for user.
SNMP variables of MIB-2 can be modified via SNMP SET:
GET NEXT / Response

GETBULK / Response
<RFC1213-MIB>
GET / Response
TRAP
SET
SNMP-address Data
Object Identifier (OID) Object Description Type
1.3.6.1.2.1.1.4 sysContact Text
ü ü ü
default = [email protected]
1.3.6.1.2.1.1.5 sysName Text ü ü ü

default = SICAM RTUs
1.3.6.1.2.1.1.6 sysLocation Text ü ü ü

default = Humboldstrasse 59, 90459 Nuernberg, Germany
Note
All supported SNMP variables of RFC1213-MIB can be read via SNMP, but only selected SNMP variables
cannot be changed via SNMP.
SNMP variables cannot be read/modified by the SICAM TOOLBOX II.

Edition 06.2017, DC0-023-2.12
SNMPv3 Agent
10.5.2 SNMP Variables for SICAM RTUs
GET NEXT / Response

GETBULK / Response
<sicamRTUs.MIB>
GET / Response
TRAP
SNMP-address Data
1.3.6.1.4.1.22638.7.1 SICAM RTUs – General information ü ü
1.3.6.1.4.1.22638.7.1.1 SICAM RTUs – General information -
ü ü
device-specific
1)
1.3.6.1.4.1.22638.7.1.1.1 Plant name Text ü ü
1.3.6.1.4.1.22638.7.1.1.2 Plant ID Text ü ü
1.3.6.1.4.1.22638.7.1.1.3 System-technical region number Integer ü ü
1.3.6.1.4.1.22638.7.1.1.4 System-technical component number Integer ü ü
1.3.6.1.4.1.22638.7.1.2 SICAM RTUs – Firmware Revision ü ü
1.3.6.1.4.1.22638.7.1.2.1.1.2 Firmware instance Text ü ü
1.3.6.1.4.1.22638.7.1.2.1.1.3 System element name Text ü ü
1.3.6.1.4.1.22638.7.1.2.1.1.4 Firmware revision Text ü ü
1.3.6.1.4.1.22638.7.1.2.1.1.5 System element description Text ü ü
1.3.6.1.4.1.22638.7.1.2.1.1.6 System element address Text ü ü
1.3.6.1.4.1.22638.7.1.2.1.1.7 Hardware number Text ü ü
1.3.6.1.4.1.22638.7.1.2.1.1.8 Firmware number Text ü ü
1.3.6.1.4.1.22638.7.10 SICAM RTUs – diagnostic information ü ü
1.3.6.1.4.1.22638.7.10.1 SICAM RTUs – diagnostic inform. – central
ü ü
error table
1.3.6.1.4.1.22638.7.10.1.1 Sum diagnosis table | Fault 1 “Class Text
ü ü
internal”
ü ü
extern”
ü ü
communication”
ü ü
test”
ü ü
warning”
ü ü
module failure”
ü ü
Failure”
ü ü
startup”
1.3.6.1.4.1.22638.7.11 SICAM RTUs – History ü ü
1.3.6.1.4.1.22638.7.11.1 SICAM RTUs – History – TRAP-History ü
1) This SNMP variable is equal with the parameter M: AU common settings | Plant.
Note:
All SNMP variable of sicamRTUs.MIB are read only via SNMP (cannot be changed via SNMP).
The central error table is called sum diagnosis table in SICAM RTUs.

DC0-023-2.12, Edition 06.2017
SNMPv3 Agent
Example: SNMP GET for OID: 1.3.6.1.4.1.22638.7.10.1.1 Sum diagnosis table | Fault 1 “Class
internal“
Example for firmware revision interrogation table (retrieved with ManageEngine MIB browser:

Edition 06.2017, DC0-023-2.12
SNMPv3 Agent
10.5.3 SNMP Variables for SICAM RTUs - Traps
The following diagnostic information items can be sent to the SNMP Manager as SNMP
Traps:
<sicamRTUs.MIB>
GET NEXT / Response

GETBULK / Response
GET / Response
TRAP
SNMP-address Data
1.3.6.1.4.1.22638.7.10.10 SICAM RTU Traps (Sum Diagnosis Traps)
1.3.6.1.4.1.22638.7.10.10.1 SICAM RTUs Event = Diagnostic Events ü
1.3.6.1.4.1.22638.7.10.10.2 Diagnostics Error Group: Error 1 - 8 Integer
(corresponding error groups à see error ü
classes in sum diagnosis table above)
1.3.6.1.4.1.22638.7.10.10.3 Diagnostic Condition: 0 = going, 1 = coming Integer ü
1.3.6.1.4.1.22638.7.10.10.4 Diagnostic Date: Date and time of trap event Date+Time ü
Note:
The following status information items can be sent to the SNMP Manager as SNMP Traps:
<SNMPv2-MIB>
GET NEXT / Response

GETBULK / Response
GET / Response
TRAP
SNMP-address Data
1.3.6.1.6.3.1.1.5.1 ColdStart trap ü
1.3.6.1.6.3.1.1.5.3 linkDown trap ü
1.3.6.1.6.3.1.1.5.4 linkUp trap ü
Note:

DC0-023-2.12, Edition 06.2017
SNMPv3 Agent
Example: SNMP “TRAPs“
Example: SNMP “TRAP Details“

Edition 06.2017, DC0-023-2.12
SNMPv3 Agent
10.5.4 SNMP Variables for SICAM RTUs - Traps History
The following status information items can be sent to the SNMP Manager as SNMP Traps:
GET NEXT / Response

GETBULK / Response
<sicamRTUs.MIB>
GET / Response
TRAP
SNMP-address Data
1.3.6.1.4.1.22638.7.11.1 SNMP Table with up 50 last sent traps ü
Note:
SNMP variables cannot be read/modified by TOOLBOX II.
The following Traps are recorded in the TRAP history:
GET NEXT / Response

GETBULK / Response
<sicamRTUs.MIB>
GET / Response
TRAP
SNMP-address Data
1.3.6.1.6.3.1.1.5.1 ColdStart trap ü
1.3.6.1.6.3.1.1.5.3 linkDown trap ü
1.3.6.1.6.3.1.1.5.4 linkUp trap ü
1.3.6.1.4.1.22638.7.10.1.1 Sum diagnosis table | Fault 1 “Class
ü
internal”
ü
extern”
ü
communication”
ü
test”
ü
warning”
ü
module failure”
ü
failure”
ü
startup”
Note:
SNMP variables cannot be read/modified by TOOLBOX II.

DC0-023-2.12, Edition 06.2017
SNMPv3 Agent
Example: Interrogation of the SNMP “TRAP History”
Example: SNMP “TRAP History” table

Edition 06.2017, DC0-023-2.12
11 PRP
Contents
11.1 Introduction .................................................................................................. 600

11.2 Configuration ................................................................................................ 602
This chapter describes the protocol PRP which is integrated in the firmware of the basic
system element.

DC0-023-2.12, Edition 06.2017
PRP
11.1 Introduction
The Parallel Redundancy Protocol (PRP) is a redundancy protocol which supports seamless
redundancy (=no reconfiguration times in case of a network failure). It is standardized in
IEC 62439-3. It is a layer 2 redundancy procedure which is independent from higher layers.
PRP was developed for automation networks which require a continuous operation
functionality and high availability.
Supported Standard Description
IEC 62439-3 Industrial communication networks - High availability automation networks -

Edition 2.0 (2012-07) Part 3: Parallel Redundancy Protocol (PRP) and High-availability Seamless
Redundancy (HSR)
In a PRP structure all data are transmitted at the same time via 2 independent networks (LAN
A and LAN B). Topology, performance and latency can be different in both networks, but
latency may only differ within a certain range. As shown in the following picture, both networks
may not be connected together.
The advantage of PRP over other protocols is, that in the case of a communication failure
within one network, there is a bumpless switch over and hence no loss of data.
Disadvantage of PRP is the operation of 2 independent networks.
Depending on the connection PRP distinguishes the following device types:
· Dual Attached Nodes (DAN)

Devices which are connected with both networks. There is a separate interface for each
network connection.
· Single Attached Nodes (SAN)
Devices which are connected with just one network.
· Virtual Double Attached Nodes (VDAN)
VDANs are devices with just one interface, but which are connected with both networks
via a redundancy box (RedBox).
DAN DAN
SAN SAN
LAN A LAN B
RedBox
DAN DAN DAN DAN
VDAN VDAN VDAN VDAN

Edition 06.2017, DC0-023-2.12
PRP
CP-2016/CPCX26 SICAM AK 3 Central processing and communication
CP-2019/PCCX26 SICAM AK 3 Central processing and communication
SICAM 230
3 party
CPCX26
PCCX26
CPC80
General Functions
rd
· Duplicate discard ü ü
− Supervision ü ü
Supported Protocols for PRP:
Firmware Protocol Function
ET24 IEC60870-5-104 Controlling station, controlled station
ET25 IEC61850 Client, Server
CP-2016/CPCX26 NTP, SNTP Network Time Protocol

CP-2016/PCCX26 Simple Network Time Protocol
CP-2016/CPCX26 SNMP Simple Network Management Protocol

CP-2016/PCCX26
CP-2016/CPCX26 http/https WEB server

CP-2016/PCCX26 remote operation
· PRP enabled is always for PRE0 + PRE1

· Data from PRE0 and PRE1 will be sent always to both networks
· Same MAC address will be used on interface X0 + X1 for PRP
· Redundant PRE’s in combination with PRP will not be supported
· Required parameter setting for PRP:
mode of Ethernet ports = 1 IP address (connected ports in switch mode)
CP-2016/CP-2019
SM-2558
SM-0551
PRE0 PRE1 PRE2 PRE3
X0 X1 X2 X3
PRP LAN “A“
PRP LAN “B“
serial
LAN
Red Box

DC0-023-2.12, Edition 06.2017
PRP
11.2 Configuration
SICAM TOOLBOX II
PRP can only be used with the integrated/local interfaces (PRE0 and PRE1 = X0 and X1) on
the SICAM AK 3 basic system elements CP-2016/CPCX26 and CP2019/PCCX26.
Following parameter must be set on the basic system element:
Parameter value Description

Network settings | Redundancy | PRP Network redundancy
Network redundancy activated
NO no network redundancy
SWITCH
· The used switches must be configured for the support of "Jumbo Frames".

Edition 06.2017, DC0-023-2.12
12 NTP/SNTP
Contents
12.1 Introduction .................................................................................................. 604

12.2 NTP/SNTP Client ......................................................................................... 605
12.3 Integrated NTP Server.................................................................................. 608

DC0-023-2.12, Edition 06.2017
NTP/SNTP
12.1 Introduction
The NTP (Network Time Protocol) or SNTP (Simple Network Time Protocol) is a standard for
the synchronization of clocks in systems over IP communication networks. The NTP/SNTP
protocol is a Client/Server protocol. NTP/SNTP clients can request the time from NTP servers.
While a full featured NTP server or -client reaches a very high level of accuracy and avoids
abrupt timesteps as much as possible by using different mathematical and statistical methods
and smooth clock speed adjustments, SNTP can only be recommended for simple
applications, where the requirements for accuracy and reliability are not too demanding.
By disregarding drift values and using simplified ways of system clock adjustment methods
(often simple time stepping), SNTP achieves only a low quality time synchronization when
compared with a full NTP implementation.
NTP is a hierarchical protocol over which time servers can determine a common time amongst
each other. The NTP protocol determines the delay of packets in the network and
compensates these for the clock synchronization. The NTP/SNTP protocol uses port number
123.
The Network Time Protocol (NTP) uses the connectionless network protocol UDP. It has been
developed especially to enable a reliable time tagging over networks with variable packet
delay.
The time tags in NTP are 64 bits long. 32 bits encode the seconds since the 1st January 1900
32
00:00:00 hour, the other 32 bits are the fraction of seconds. In this way, a time period of 2
−32
seconds (about 136 years) can be represented with a resolution of 2 seconds (about 0.25
nanoseconds).
NTP uses a UTC time scale and supports switching seconds, but not daylight-saving time and
winter time.
NTP uses a hierarchical system of different strata (levels). The stratum specifies how far the
NTP server is from an external time source. As time source an atomic clock, a DCF77
receiver or a GPS receiver can be used.
A stratum-1 server is connected directly with a time source and uses this as reference for its
time. A stratum-2 server uses a stratum-1 server as reference and synchronizes itself with
other servers on its level if the connection to the higher level fails. The highest level is 16 and
signifies that this NTP server has not yet calibrated itself with other servers. As a rule no more
than 4 levels exist, since otherwise the time would deviate too much.

Edition 06.2017, DC0-023-2.12
NTP/SNTP
12.2 NTP/SNTP Client
For the clock synchronization of a component over LAN, the time information can be
requested from one or several NTP servers in the network by the protocol element's
integrated NTP/SNTP-Client function. The NTP servers themselves are synchronized either
directly with DCF77 or GPS receiver, or by interrogating the time information from other NTP
servers.
General Functions NTP/SNTP Client
ETA3
ETA2
ETA4
ETA5
ET03
ET83
ET84
ET24
ET25
ET85
Function
Clock synchronization with ü ü ü 1) ü ü ü 1) ü ü 1) ü 1) ü 1)

NTP servers 2)
Number of supported NTP 4 4 4 1) 4 4 4 1) 4 4 1) 4 1) 4 1)

servers ( for redundancy)
Cyclic time interrogation of ü ü ü 1) ü ü ü 1) ü ü 1) ü 1) ü 1)

the NTP servers, settable in
seconds grid (self-adapting)
Possible accuracy approx. 3 ms 3)
Protocol NTP V3 ü ü ü 1) ü ü ü 1) ü ü 1) ü 1) ü 1)
according to RFC 1305
Protocol SNTP V4 ü ü 1) ü ü 1) ü ü 1) ü 1) ü 1)
1) In CP-8000/CP-802x, or SICAM AK3 with local PRE (PRE without NIP) this function is integrated
on the basic system element
2) The external NTP servers will be synchronized via GPS (or via DCF77 on request);
an external NTP server can handle several automation units
3) Possible accuracy dependent on the quality of the IP network.
If the clock synchronization with NTP is activated on a LAN/WAN protocol element, the
transfer of a received clock synchronization command with <TI:=103> to the basic system
element is disabled.

DC0-023-2.12, Edition 06.2017
NTP/SNTP
Parameters for NTP time synchronization

· NTP Time Synchronization
The time synchronization by means of NTP/SNTP is enabled with the parameter
NTP/SNTP time synchronisation client | time synchronisation or
NTP time synchronisation client | NTP time synchronisation.
The other parameters for NTP time synchronization are only displayed after the function
has been enabled.
· NTP Server 1 IP address
NTP Server 2 IP address
The protocol firmware supports max. 4 different redundant NTP servers. The time is
always requested from all parameterized NTP servers. The time for the synchronization is
determined by means of a defined algorithm from the times received from the NTP
servers.
For every NTP server the unambiguous IP address of the NTP server is to be
parameterized in the format IPv4 (32 Bit) in dotted decimal notation.
Example: 192.168.122.195
The IP addresses of the NTP servers are to be set with the parameters
NTP/SNTP time synchronisation client | NTP server # IP address or
NTP time synchronisation client | NTP server # IP address.
· max. Stratum
If the received stratum number from the NTP server is greater or equal as a parameterized
limit, a warning is indicated. With this monitoring function an non synchronized NTP server
can be detected (e.g. defect or disconnected antenna). If all NTP servers are not
synchronized, the NTP time is not longer synchronous with the world time. In this case the
time of the NTP servers will drift with the quality of the local time of the NTP servers.
The limit of the stratum number for generating a warning is to be parameterized with the
parameter NTP/SNTP time synchronisation client | advanced parameters |
max. Stratum with the parameter NTP time synchronisation client | max.
Stratum.
· Suppress Stratum-error
If a 1703 system will be synchronized via several NTP servers, the stratum number may
only differ by 1. If the difference of the stratum number is greater than 1, the protocol
element will generate an error indication "no valid time from server, stratum number
invalid" for the NTP servers with higher stratum number.
If different NTP servers will be used in a project from different providers, the requirement
for the tolerated difference in stratum number can not be guaranteed.
The generation of error can be suppressed with the parameter NTP/SNTP time
synchronisation client | advanced parameters | Suppress stratum error
or with the parameter NTP time synchronisation client | Suppress stratum
error.
Note:
NTP-Server with higher stratum number (= less accuracy) will not be included in the
processing. Only when NTP servers with lower stratum number will fail, the next NTP
servers will be included in processing. Based on this handling an error indication can be
displayed for a short time.

Edition 06.2017, DC0-023-2.12
NTP/SNTP
Advanced Parameters for NTP time synchronization

The advanced parameters for optimizing NTP time synchronization are preset with default
values and can be modified in protocol firmware if parameters are supported.
Parameter Default
max. time deviation 3 ms
NTP minimal cycle time 4s *)
NTP maximal cycle time 128 s *)
NTP cycle time until synchronized 4s *)
Delay error signalization 0

*) these time settings must not be changed!
· NTP Maximum Time Deviation

If the deviation of the time between the own component and the NTP server is greater
than the parameterized value, an error is signaled.
The maximum time deviation is to be set with the parameter NTP/SNTP time
synchronisation client | advanced parameters | NTP maximum time
deviation or with the parameter NTP time synchronisation client | NTP
optimization | max. time deviation.
· NTP Minimum Cycle Time
· NTP Maximum Cycle Time
· NTP Cycle Time until synchronized
Until the 1st synchronization, the interrogation of the time from the NTP servers (NTP-
Requests) can be carried out in a shorter time scale.
After successful synchronization, the interrogation of the time from the NTP server (NTP
Request) is carried out cyclically in a time scale between "NTP Minimal Cycle Time" and
"NTP Maximum Cycle Time".
Note:
With the communication over GPRS the cycle time must not be set too short, since due to
the cyclic time request, corresponding transmission charges accumulate.
· Error Signalization Delay
For problems during the interrogation of the time from NTP servers, the signalization of the
error "No valid time from NTP server" can be delayed with the parameter NTP/SNTP time
synchronisation client | advanced parameters | Delay error
signalization or with the parameter NTP time synchronisation client | NTP
optimization | Delay error signalization.
Through this, short-term faults or load problems in the network do not lead to any error.

DC0-023-2.12, Edition 06.2017
NTP/SNTP
12.3 Integrated NTP Server
In configurations with less demand on the accuracy for time synchronization, the LAN protocol
firmware in the SICAM RTUs component provides an integrated NTP server for other
systems.
This function is helpful if the clock synchronization of the remote terminal unit is carried out by
means of DCF77 receiver, over a serial interface or NTP-Synchronization via separate LAN,
and in this remote terminal unit other devices are connected over LAN, which requires a time
synchronization with NTP or SNTP. Thereby, the additional procurement of an NTP server for
the subnet in the remote terminal unit is not necessary.
The time of the integrated NTP server is controlled by the local time of the component. The
accuracy is therefore dependent on the accuracy of the clock synchronization of the
component itself.
General Functions NTP Server

ETA3
ETA2
ETA4
ETA5
ET03
ET83
ET84
ET24
ET25
ET85
Function
Integrated NTP server for ü ü ü 5) ü ü ü 5) ü ü 5) ü 5) ü 5)

clock synchronization of one
or several NTP/SNTP clients
1)
max. number of NTP clients 100 2) 30 2) 100 2) 30 2) 100 2) 100 2) 100 2) 30 2)

with 1 time interrogation per
minute
Stratum 3 3) 3 3) 3 3) 3 3) 3 3) 3 3) 3 3) 3 3) 3 3) 3 3)
Achievable accuracy 4) 4) 4) 4) 4) 4) 4) 4) 4) 4)
Reaction time (transmission typically 300…900 μs

of the requested time by the
protocol firmware)
Protocol NTP V3 ü ü 5) ü ü 5) ü 5) 5) 5)
Protocol SNTP V4 ü ü 5) ü ü 5) ü 5) 5) 5)
(Simple Network Time
Protocol) according to
RFC 2030 6)
1) NTP server supports only the request of the time (broadcast transmission of the time is not
supported by the integrated NTP server)
2) experimental value (the limit results from the system load utilization)
3) based on the achievable accuracy with remote synchronization over serial communication line
4) dependent on the accuracy of the clock synchronization of the component
5) function is integrated on the basic system element
6) time interrogations to the integrated NTP server can be performed with SNTP or NTP protocol

Edition 06.2017, DC0-023-2.12
NTP/SNTP
Parameters for NTP time synchronization

· NTP Server
The integrated NTP server function of the LAN/WAN communications firmware is enabled
with the parameter NTP time synchronization server | NTP Server
· Synchronization before the first time-setting
With function enabled, with the parameter NTP time synchronization server |
Synchronization before first time set NTP reply messages are also sent, if the
time of the SICAM RTUs component is not yet set
· Synchronization with invalid time
With function enabled, with the parameter NTP time synchronization server |
Synchronization also with invalid time NTP reply messages are also sent, if the
time of the SICAM RTUs component is not set

DC0-023-2.12, Edition 06.2017
NTP/SNTP

Edition 06.2017, DC0-023-2.12
13 Remote Operation for SICAM TOOLBOX II
(LAN/WAN)
Contents
13.1 Introduction .................................................................................................. 612

13.2 Remote Operation via TCP/IP + HTTP/HTTPS ............................................. 613
13.3 Remote Operation via integrated Terminal Server......................................... 614
13.4 Remote Operation via external Terminal Server............................................ 615

DC0-023-2.12, Edition 06.2017
Remote Operation for SICAM TOOLBOX II (LAN/WAN)
13.1 Introduction
The remote maintenance of SICAM RTUs components via LAN/WAN can be performed using
"remote operation":
· Remote operation via TCP/IP HTTP/HTTPS

· Remote operation via integrated Terminal Server
· Remote operation via external Terminal Server (connection to M-CPU with TIAX00)
Note
(only valid with IEC 60870-5-104)
During activated connection with remote operation via TCP/IP HTTP/HTTPS or with remote connection via
integrated Terminal Server a reset process command <TI:=105> will not be accepted and rejected by
protocol element with “ACTCON negative”.

Edition 06.2017, DC0-023-2.12
13.2 Remote Operation via TCP/IP + HTTP/HTTPS
For the remote maintenance of SICAM RTUs components using "remote operation" a
transparent connection is established over TCP/IP + HTTP/HTTPS between the
SICAM TOOLBOX II and the SICAM RTUs component via the protocol element.
For “remote operation" with SICAM TOOLBOX II a proprietary Client-Server protocol is used
for remote maintenance and remote diagnostics of SICAM RTUs components working through
firewalls, NAT and Proxy-Server.
For outgoing connections the SICAM TOOLBOX II uses the standard port 80 for HTTP or
standard port 443 for HTTPS. Therefore no adaption of firewall is required if internet access is
enabled.
The connection for "remote operation" is always established by the SICAM TOOLBOX II.
The SICAM TOOLBOX II thereby always takes over the client function, the SICAM RTUs
component always the server function.
If several SICAM TOOLBOX II applications attempt to setup a connection at the same time,
the first SICAM TOOLBOX II wins, the rest are rejected.
If an error is detected during the remote maintenance of SICAM RTUs components using
"remote operation", then the TCP/IP connection is terminated.
For the "remote operation", a connection is to be set up on the SICAM TOOLBOX II for every
remote station with the following parameters:
· Transmission medium = terminal server, TCP/IP

· IP address of the remote station (IP address or Host ID of the terminal server of the
remote station)
· Port number = 80 (auto detection)
· Delay time
For security reasons the "remote operation" for SICAM TOOLBOX II can be deactivated with
the parameter advanced parameters | remote operation | remote operation.
With "remote operation" activated for SICAM TOOLBOX II the “remote operation” can
optionally be enabled/disabled via a protocol element control message. At startup the "remote
operation" will be initialized as disabled (if the protocol element control message is entered in
the process technique) and can then be enabled/disabled via the protocol element control
message. In case of "remote operation" is enabled and a connection with SICAM TOOLBOX II
is established and then the “remote operation" is disabled, then the existing connection to the
SICAM TOOLBOX II will be aborted immediately.
The actual state of "remote operation" (enabled/disabled) will be indicated via protocol
element return information message.
Note:
- the protocol element control message/protocol element return information message can be converted to selected
process data message in protocol element control function on the basic system element.
With connection established for the remote maintenance, a warning is generated in the
SICAM RTUs component. If necessary, this warning can be deactivated with the parameter
advanced parameters | remote operation | warning remote operation.
So that a secure point-to-point is ensured, a communications protocol based on

IEC 60870-5-1 and IEC 60870-5-2 "Balanced" is implemented between the
SICAM TOOLBOX II and the LAN/WAN communications protocol firmware on the application
layer. Terminal Server is thereby used as transport protocol.
The service message formats between SICAM TOOLBOX II and the SICAM RTUs component
are prepared accordingly on the LAN/WAN communications protocol firmware (conversion
from SICAM RTUs internal format and format for SICAM TOOLBOX II) and transferred to the
master service function of the SICAM RTUs component for further processing.

DC0-023-2.12, Edition 06.2017
13.3 Remote Operation via integrated Terminal Server
For the remote maintenance of SICAM RTUs components using "remote operation" over
external, a transparent connection is established over Ethernet between the
SICAM TOOLBOX II and the integrated terminal server of the protocol element.
The Terminal Server protocol for "remote operation" is based on TCP/IP and is a Client-
Server protocol. The SICAM TOOLBOX II thereby always takes over the client function, the
SICAM RTUs component always the server function.
The connection for "remote operation" is always established by the SICAM TOOLBOX II.
For the Terminal Server protocol a TCP/IP connection must be set up. With the
SICAM TOOLBOX II interfacing, the SICAM TOOLBOX II is Connector and the NIP is
Listener. The Listener-Port number to be used is 2001. If several SICAM TOOLBOX II
applications attempt to setup a connection at the same time, the first SICAM TOOLBOX II
wins, the rest are rejected.
If an error is detected during the remote maintenance of SICAM RTUs components using
"remote operation", then the TCP/IP connection is terminated.
For the "remote operation", a connection is to be set up on the SICAM TOOLBOX II for every
remote station with the following parameters:
· Transmission medium = terminal server, TCP/IP

· IP address of the remote station (IP address or Host ID of the terminal server of the
remote station)
· Port number = 2001
· Delay time
For security reasons the "remote operation" for SICAM TOOLBOX II can be deactivated with
the parameter advanced parameters | remote operation | remote operation. With
"remote operation" deactivated, the Terminal Server protocol over Port 2001 is no longer
handled.
With connection established for the remote maintenance, a warning is generated in the
SICAM RTUs component. If necessary, this warning can be deactivated with the parameter
advanced parameters | remote operation | warning remote operation.
Functionally, the "remote operation" via integrated Terminal Server thereby corresponds with
the interfacing with external terminal server (and TIAX00), only with this solution the
functionality of the terminal server is integrated in the SICAM TOOLBOX II and in the
LAN/WAN communications protocol element.
So that a secure point-to-point connection via integrated Terminal Server protocol is ensured,
a communications protocol based on IEC 60870-5-1 and IEC 60870-5-2 "Balanced" is
implemented between the SICAM TOOLBOX II and the LAN/WAN communications protocol
firmware on the application layer. Terminal Server is thereby used as transport protocol.
The service message formats between SICAM TOOLBOX II and the SICAM RTUs component
are prepared accordingly on the LAN/WAN communications protocol firmware (conversion
from SICAM RTUs internal format and format for SICAM TOOLBOX II) and transferred to the
master service function of the SICAM RTUs component for further processing.

Edition 06.2017, DC0-023-2.12
13.4 Remote Operation via external Terminal Server
For the remote maintenance of Ax 1703 components using "remote operation" over external
terminal server, the serial interface of the SICAM TOOLBOX II is connected with a selected
SICAM RTUs component over Ethernet. An external terminal server (=serial to Ethernet
converter) is thereby implemented at the SICAM TOOLBOX II side and at the SICAM RTUs
component side. At SICAM RTUs component side the serial interface of the external Terminal
Server is connected to M-CPU via TIAX00.
The IP address of the selected SICAM RTUs component and the SICAM TOOLBOX II are to
be parameterized in the external terminal servers. All components that can be reached via the
selected SICAM RTUs component can thus be reached for the remote maintenance.
In the SICAM RTUs component and in the SICAM TOOLBOX II, no special parameter settings
are required.
If SICAM RTUs components are used in different LAN/WAN networks, a specific external
terminal server must be used at the SICAM TOOLBOX II side for each LAN/WAN network or
the external terminal server must be re-parameterized accordingly with the programs provided
for this purpose.
A communications protocol based on IEC 60870-5-1 and IEC 60870-5-2 "Balanced" is used
between the SICAM TOOLBOX II and the LAN/WAN communications protocol element.
Here, the "remote operation" over external terminal server is only mentioned for the sake of
completeness, it is not however any special functionality of the LAN/WAN communications
protocol element. This solution is now rarely used (actually used only in older plants).
In new plants, now in most cases the "remote operation" for SICAM TOOLBOX II is carried
out via "remote operation" with the integrated terminal server of the SICAM TOOLBOX II and
the LAN/WAN communications protocol element.

DC0-023-2.12, Edition 06.2017

Edition 06.2017, DC0-023-2.12
A Internet Protocol Family
Inhalt
A.1 Internet Protocol (IP) .................................................................................... 618

A.2 Transmission Control Protocol (TCP)............................................................ 619
A.3 User Datagram Protocol (UDP)..................................................................... 622
A.4 Hyper Text Transfer Protocol (HTTP)............................................................ 623

DC0-023-2.12, Edition 06.2017
Internet Protocol Family
A.1 Internet Protocol (IP)
The Internet Protocol (IP) is that network protocol used almost exclusively in computer
networks. With the protocol, single packets are transmitted throughout the entire network. It is
part of the Internet protocol family, the basis of the Internet, and is located in layer 3 of the
OSI reference model.
IP forms the first layer of the Internet protocol family independent of the transmission medium.
That means, that using IP address and subnet mask computers within a network can be
grouped into logical units, so-called subnets. On this basis it is possible to address computers
in larger networks and establish connections to them, since logical addressing is the basis for
routing (route selection and transfer of network packets). The Internet Protocol represents the
basis of the Internet.

Edition 06.2017, DC0-023-2.12
A.2 Transmission Control Protocol (TCP)
The Transmission Control Protocol (TCP) is a reliable, connection-orientated transport

protocol in computer networks and is supported by all operating systems for modern
computers. It is part of the Internet protocol family, the basis of the Internet, and is located in
layer 4 of the OSI reference model.
The protocol can be implemented on networks from 1200Bit/s up to several Gbit/s.
In contrast to the connectionless UDP (User Datagram Protocol), TCP establishes a virtual
channel (connection) between two terminals of a network connection (Sockets). On this
channel, data can be transmitted in both directions. In all practical cases, TCP is based on the
IP (Internet Protocol), which is why one also speaks of „TCP/IP Protocol“.
Due to its many pleasing characteristics – data losses are detected and remedied
automatically, data transmission is possible in both directions, can be used on many different
media – the TCP/IP is a widespread protocol for data transmission.
TCP is basically a point-to-point connection in full duplex, which permits the transmission of
the information in both directions at the same time. The data in the reverse direction can
thereby contain additional control information. The management of this connection as well as
the data transmission is carried out by the TCP Software.
Every TCP connection is identified unambiguously by two terminals. A terminal represents an

assigned pair consisting of IP address and port. Such a pair forms a bidirectional software
interface, and is known as a Socket. With the help of the IP addresses, the systems
participating on the connection are identified; with the help of the ports, the two programs
communicating with each other on the two participating systems are then identified. By using
port numbers at both sides of the connection, it is possible for example, that one Web server
on one port (normally Port 80) can have several connections open to another system at the
same time. The ports are 16-Bit numbers (port numbers) and range from 0 to 65535. Ports
from 0 to 1023 are reserved (English: well known ports[1]) and are assigned by the IANA, e.g.
Port 80 is reserved for the HTTP protocol used in the WWW.
A typical TCP packet has a maximum size of 1500 Bytes. It may only be so large, that it fits in
the transmission layer situated below, the Internet protocol IP. The IP packet is specified
theoretically up to 65535 Bytes (64 kB), but this is mostly transmitted over Ethernet, and there
the frame size is fixed at 1500 Bytes. TCP and IP protocols each define a header of 20 Bytes
size. Therefore 1460 bytes are left over for the user data in a TCP/IP packet.

DC0-023-2.12, Edition 06.2017
Connection Setup
A Web server which offers its service generates a terminal with the port number assigned to
the application and its IP address. This is known as “passive open” or also as “listen”.
If a client wishes to establish a connection, it generates its own terminal from its IP address
and a still free port number. With the help of the port number of the application and the IP
address of the server, a connection can then be set up.
During the data transmission phase (active open) the roles of Client and Server (from TCP
perspective) are completely symmetrical. In particular, each of the two participating systems
can initiate a connection setup.
For the establishment of a TCP connection, the so-called three-way handshake is

implemented. The system which wishes to establish the connection sends the other a SYN
packet (from the English word synchronize) with a sequence number x. The sequence
numbers are thereby important for the assurance of a complete transmission in the correct
order and without duplicates. It therefore concerns a packet, whose SYN-Bit is set in the
packet header (see TCP-Header). The start sequence number is optional and is generated by
the respective operating system according to a random algorithm.
TCP/IP – Communication
Client services Server
TCP/IP – Initiate connection

setup syn seq=x
, seq=y
syn ack = x+1
ack = y+1, seq

=x+1
TCP/IP – connection setup
[data]
TCP/IP Handshake
The remote station (see sketch) receives the packet and as counter move sends its start
sequence number y in its own SYN packet. At the same time, it confirms the reception of the
first SYN packet, by increasing the sequence number x by one and sending it back in the ACK
part (from the English word acknowledgement = confirmation) of the header.
The client finally confirms the reception of the SYN/ACK packet by sending its own ACK
packet with the sequence number y+1. This procedure is also called `Forward
Acknowledgement´. The server receives this ACK segment, the ACK segment is identified by
the set ACK-Flag. The connection is thereby established.
SYN-SENT è <SEQ=100><CTL=SYN> è SYN-

RECEIVED
SYN/ACK-SENT ç <SEQ=300><ACK=101><CTL=SYN,ACK> ç SYN/ACK-
RECEIVED
ACK-SENT è <ACK=301><CTL=ACK> è ESTABLISHED

Edition 06.2017, DC0-023-2.12
Connection release
The controlled connection release takes place similar to the connection setup. Instead of the
SYN-Bit, the FIN-Bit (from the English word finish = end, conclusion) is used, which indicates
that no more data is coming from the transmitter. The reception of the packet is again
confirmed with ACK. The recipient of the FIN packet finally sends its FIN packet, which is also
confirmed to it.
TCP/IP – Communication
Client or Server services Remote station

release fin, seq=x

ack = x+1
release
fin, seq=y
TCP/IP – connection
released
ack =y+ 1
TCP/IP – connection
released
TCP/IP Teardown
Although four ways are actually used, with connection release it also concerns a three-way
handshake, since the ACK and FIN operations from the server to the client are evaluated as
one way. In addition, a shortened procedure is possible, in which the FIN and ACK are
accommodated in the same packet just as with the connection setup. The maximum segment
lifetime (MSL) is the maximum time that a segment can stay in the network before it is
discarded. After sending the last ACK's, the client switches to a waitstate lasting two MSL in
which all delayed segments are discarded. As a result it is ensured, that no delayed segments
can be wrongly interpreted as part of a new connection. Apart from this a correct connection
termination is ensured. If ACK y+1 is lost, the timer at the server expires and the LAST_ACK
segment is transmitted again.
However, SICAM RTUs protocol elements do not use the controlled connection release. A
connection is normally only released with a Link failure, consequently an acknowledgement at
TCP/IP level cannot be expected. The SICAM RTUs protocol firmware therefore uses the
RST-bit in the RST packet for the immediate release of the connection. No acknowledgement
is expected for this packet.

DC0-023-2.12, Edition 06.2017
A.3 User Datagram Protocol (UDP)
The User Datagram Protocol (UDP) is a minimal, connectionless (unacknowledged) network

protocol, which belongs to the transport layer of the Internet protocol family. It provides no
guarantee that transmitted packets also arrive or that packets arrive in the same order in
which they have been sent. An application that uses the UDP must therefore be insensitive to
lost, unsorted or duplicated packets or itself contain corresponding correction measures.
The task of UDP is to allow data that are transmitted over the Internet to reach the correct
application.
In order to allow the data that are sent with UDP to reach the correct program on the
destination system, ports are used for UDP, just as for TCP. For this, with UDP the port
number of the service which is to receive the data is also sent.
Since a connection does not have to be established first before the beginning of transmission,
the hosts can begin faster with the exchange of data.

Edition 06.2017, DC0-023-2.12
A.4 Hyper Text Transfer Protocol (HTTP)
The HyperText Transfer Protocol (HTTP) is a protocol for the transmission of data over a
network. It is used mainly to load web pages and other data from the World Wide Web
(WWW) or from a web browser integrated in a system.
In the automation technique, parameter settings or diagnostic information of systems are

realized more and more frequently with web technology. With this technique a web server is
implemented in the device – the data is displayed on web pages.
The HTTP forms the so-called application layer, over which the models provide no other
layers. The application layer is addressed by the user programs, in the case of HTTP, in most
cases this is the Web Browser, the normal user is therefore presented with this layer when he
enters a web address. In the ISO/OSI layer model, the application layer corresponds with
layer 7. The TCP/IP reference models implemented in the Internet sees the application layer
in layer 4.
In the core, HTTP is a stateless protocol. That also means, that after successful data
transmission, the connection between the two communication partners does not need to be
maintained. If then further data is to be transmitted, firstly another connection must be
established.
However through expansion of its interrogation methods, header information and status
codes, the HTTP is not restricted to HyperText, rather is used increasingly for the exchange of
any arbitrary data. For the communication, HTTP is dependent on a reliable transport
protocol. In all practical cases, TCP is used for this.

DC0-023-2.12, Edition 06.2017

Edition 06.2017, DC0-023-2.12
Literature
SICAM RTUs • Ax 1703 Common Functions System- and Basic System DC0-015-2
Elements
SICAM RTUs • Ax 1703 Common Functions Peripheal Elements DC0-011-2
according to IEC 60870-5-101/104
SICAM RTUs IEC 60870-5-101/104 Interoperability DC0-013-2
SICAM RTUs IEC 60870-5-103 Interoperability DC0-026-2
SICAM AK 3 System Description MC2-025-2
SICAM AK System Description MC2-021-2
SICAM TM System Datasheet MC6-007-2
SICAM A8000 Series CP-8000, CP-8021, CP-8022 Manual DC8-037-2
SICAM BC System Manual DC5-014-2
International Standards
IEC 60870-5-101
Telecontrol Equipment and Systems
Part 5: Transmission Protocols
Section 101: Companion standard for basic telecontrol tasks
IEC 60870-5-103
Telecontrol Equipment and Systems
Part 5: Transmission Protocols
Section 103: Companion standard for the informative interface of protection equipment
IEC 60870-5-104
Telecontrol equipment and systems
Part 5: Transmission protocols
Section 104: Network access for IEC 60870-5-101 using standard transport profiles
IEC 61850-1
Introduction and Overview
- Introduction and overview of the standards of the IEC 61850 series
IEC 61850-2
Dictionary
- Collection of terms
IEC 61850-3
General Requirements
- Quality requirements (reliability), maintainability, system availability, portability,
IT security)
- Environmental conditions
- Auxiliary services
- Other standards and other rules of engineering
IEC 61850-4
System and Project Management
- Engineering service requirements (classification of parameters, technical work
tools, documentation)
- System utilization cycle (product versions, production settings, support after
production setting)
- Quality control (responsibilities, test equipment, type tests, system tests,
factory acceptance tests "FAT" and location acceptance tests "SAT)
IEC 61850-5
Communication Requirements for Functions and Device Models
- Principle of the logical nodes
- Logical communication links
- Concept of assigned information elements for the communication (PICOM)
- Logical nodes and assigned PICOM
- Functions
- Performance requirements (response times etc.)
- „Dynamic Scenarios“ (requirements on the information flow under various
operating conditions)

DC0-023-2.12, Edition 06.2017
Literature
IEC 61850-6
Language for the configuration of station automation systems
- formal description of the single-pole scheme, of devices and system structure
and their assignment to the single-pole scheme
IEC 61850-7-1
Basic communication structure for station and bay-related secondary technology equipment – principles
and models
- Introduction into IEC 61850-7
- Communication principles and models
IEC 61850-7-2
Basic communication structure for station and bay-related secondary technology equipment – Abstract
Communication Services Interface (ACSI)
- Description of the abstract communication services interface (ACSI)
- Specification of the abstract communication services
- Model of the server database
IEC 61850-7-3
basic communication structure for station and bay-related secondary technology equipment – Common
Data Classes
- Abstract common data classes and attribute definitions
IEC 61850-7-4
Basic communication structure for station and bay-related secondary technology equipment –
Compatible Logical Nodes and Data Classes
- Definition of logical nodes, data objects and their logical addressing
IEC 61850-8-1
Specific Communication Services Modeling (SCSM) – Modeling for MMS (according to ISO/IEC 9501-1
and -2) and ISO/IEC 9501-3
- Modeling for the communication within the entire station (Client-Server
communication and "GOOSE" messages)
IEC 61850-9-1
Specific Communication Services Modeling (SCSM) – Scanned values over serial Simplex-Multiple-
Point-to-Point connection
- Modeling for the Point-to-Point-type, unidirectional communication of scanned
values of the transformer (with and without Merging Unit)
IEC 61850-9-2
Specific Communication Services Modeling (SCSM) – Scanned values over ISO/IEC 8802-3
- Modeling for the bus-type, flexible communication of scanned values of the
transformer (with and without Merging Unit)
IEC 61850-10
Conformity check
- Procedure for the conformity check

Edition 06.2017, DC0-023-2.12

GF Pre Acp Eng PDF

Uploaded by

Copyright:

Available Formats

GF Pre Acp Eng PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

GF Pre Acp Eng PDF

Uploaded by

Copyright:

Available Formats

Preface, Table of Contents

Disclaimer of Liability Copyright

This document is applicable to the following product(s):

Purpose of this manual

Target Group and Safety Instructions

Unrestricted SICAM RTUs • Ax 1703, Common Functions Protocol Elements 3

In this document, reference is often made to important information, notifications and

<parameter group> | <parameter Parameter (qualified reference, includes

Time management | Daylight saving

Time management | Daylight saving

Daylight saving time enabling

Daylight saving time

PRE# … PRE0, PRE1

Unrestricted 4 SICAM RTUs • Ax 1703, Common Functions Protocol Elements

Several fundamental terms

Spontaneous A spontaneous information object is an object, which with change is

Message A message is used for the spontaneous transmission of process-

Placement in the Information Landscape

Document Item Number

Unrestricted SICAM RTUs • Ax 1703, Common Functions Protocol Elements 5

Unrestricted 6 SICAM RTUs • Ax 1703, Common Functions Protocol Elements

1.1 Overview ........................................................................................................ 20

2 Architecture and Data Flow ........................................................................................ 21

2.1 Protocol Structure........................................................................................... 22

3 Point-to-Point Traffic (BPP) ........................................................................................ 27

3.1 Introduction .................................................................................................... 28

Unrestricted SICAM RTUs • Ax 1703, Common Functions Protocol Elements 7

3.5.2.5 Data Throughput Limitation................................................................... 65

4 Multi-Point Traffic (UMP)............................................................................................. 83

4.1 Introduction .................................................................................................... 84

Unrestricted 8 SICAM RTUs • Ax 1703, Common Functions Protocol Elements

4.7.2 Routing Method ....................................................................................... 127

5 Interfacing of Protective Devices (103) .................................................................... 153

5.1 Introduction .................................................................................................. 154

Unrestricted SICAM RTUs • Ax 1703, Common Functions Protocol Elements 9

5.2.5 Clock Synchronization ............................................................................. 167

6 SICAM RTUs Field Bus (SFB) ................................................................................... 233

6.1 Introduction .................................................................................................. 234

Unrestricted 10 SICAM RTUs • Ax 1703, Common Functions Protocol Elements

6.2.1.1 Continuous Interrogation of a Remote Terminal Unit ........................... 238

7 Dial-Up Traffic (DIA) .................................................................................................. 255

7.1 Introduction .................................................................................................. 256

Unrestricted SICAM RTUs • Ax 1703, Common Functions Protocol Elements 11

Unrestricted 12 SICAM RTUs • Ax 1703, Common Functions Protocol Elements

8 LAN Communication (104) ........................................................................................ 325

8.1 Introduction .................................................................................................. 326

Unrestricted SICAM RTUs • Ax 1703, Common Functions Protocol Elements 13

8.5.2.5.3 Profile Definition: “SICAM RTUs – IEC104” .................................... 388

9 LAN Communication (61850) .................................................................................... 411

9.1 Introduction .................................................................................................. 412

Unrestricted 14 SICAM RTUs • Ax 1703, Common Functions Protocol Elements

9.2.7.1.4 1-Out-Of-n Check [Server only] ..................................................... 459

Unrestricted SICAM RTUs • Ax 1703, Common Functions Protocol Elements 15

9.6.2.4.2 IEC 61850: Controllable Double Point (DPC) ................................. 501

Unrestricted 16 SICAM RTUs • Ax 1703, Common Functions Protocol Elements

9.6.4.5 Technological Adaptation for Measured Values................................... 539

10 SNMPv3 Agent........................................................................................................... 581

10.1 Introduction .................................................................................................. 582

11 PRP ............................................................................................................................ 599