Manual CP-8000 CP-802x ENG DC8-037-2.06

Preface
Open Source Software
Table of Contents
SICAM A8000 Series General Information 1

CP-8000, CP-8021, System Overview 2
CP-8022
Function Packages 3
Ambient Conditions 4
System Components and Technical Data 5
Manual
Installation and Circuitry 6
Preparing Engineering 7
Engineering via SICAM TOOLBOX II 8
Engineering via SICAM WEB 9
Engineering via SICAM Device Manager 10
Service 11
Communication Protocols 12
Ordering Information A
Examples of Instruction Lists (IL) B
Error Handling C
DC8-037-2
Setting Up a Dial-Up Connection D
Use Cases E
NOTE
i For your own safety, observe the warnings and safety instructions contained in this document, if available.
Disclaimer of Liability Copyright

Subject to changes and errors. The information given in Copyright © Siemens 2020. All rights reserved.
this document only contains general descriptions and/or The disclosure, duplication, distribution and editing of this
performance features which may not always specifically document, or utilization and communication of the content
reflect those described, or which may undergo modifica- are not permitted, unless authorized in writing. All rights,
tion in the course of further development of the products. including rights created by patent grant or registration of a
The requested performance features are binding only when utility model or a design, are reserved.
they are expressly agreed upon in the concluded contract.
Document version: DC8-037-2.06 Trademarks
Edition: 11.2020
SIPROTEC, DIGSI, SIGRA, SIGUARD, SIMEAS SAFIR, SICAM,
Version of the product described: and MindSphere are trademarks of Siemens. Any unauthor-
ized use is prohibited.
Preface
Purpose of the Manual
This manual describes the features and functions of following products:
• CP-8000
• CP-8021
• CP-8022 (GPRS)
Target Audience
This manual is addressed to personnel and customers who are responsible for evaluation, conceptual design,
configuration, and technical system maintenance.
It provides hints on how to get information or files via the website http://www.siemens.com/sicam. If you do
not have access to this website, contact your project manager at Siemens.
Scope
This manual is valid for the SICAM A8000 series.
SICAM A8000 Series, CP-8000, CP-8021, CP-8022, Manual 3

DC8-037-2, Edition 11.2020
Preface
Indication of Conformity
The product described conforms to the regulations of the following European Direc-
tives:
• 2014/30/EU
Directive of the European Parliament and of the Council of 26 February 2014 on
the harmonization of the laws of the Member States relating to electromagnetic
compatibility; Official Journal of the EU L96, 29/03/2014, p. 79–106
• 2014/35/EU
Directive of the European Parliament and of the Council of 26 February 2014 on
the harmonization of the laws of the Member States relating to the making avail-
able on the market of electrical equipment designed for use within certain voltage
limits; Official Journal of the EU L96, 29/03/2014, p. 357–374
• 2014/53/EU (applies for CP-8022)
Directive of the European Parliament and of the Council of 16 April 2014 on the
harmonisation of the laws of the Member States relating to the making available
on the market of radio equipment and repealing Directive 1999/5/EC; Official
Journal of the EC L153, 22/05/2014, p. 62–106
• 2011/65/EU
Directive of the European Parliament and of the Council of 8 June 2011 on the
restriction of the use of certain hazardous substances in electrical and electronic
equipment; Official Journal of the EU L174, 01/07/2011, p. 88-110
The conformity of the product with the above mentioned regulations is proven through
the observance of the following harmonized standards:
• EN 60870-2-1:1996 for 2014/30/EU

• EN 61010-1:2010 and EN 61010-2-201:2013 for 2014/35/EU;
EN 61010-2-030:2010 (only AI-8510, AI-8511, CM-8820)
• EN 301489-1:2017, EN 301489-52:2016 and EN 301511:2017 for 2014/53/EU
• EN IEC 63000:2018 for 2011/65/EU
This declaration certifies the conformity with the specified directives, but is not an
assurance of characteristics in the sense of the product liability law.
The product is intended exclusively for use in an industrial environment.
FCC Conformity Information

This device complies with part 15 of the FCC rules and the operation is subject to the following two condi-
tions: (1) This device may not cause harmful interference, and (2) this device must accept any interference
received, including Interference that may cause undesired operation.
NOTE
i Any changes or modifications not expressly approved by the party responsible for compliance could void
the user's authority to operate this equipment.
! CAUTION
Injurious to health
² Install and operate the equipment with a minimum distance of 20 cm between the radiator and your
body.
Part 15B compliance statements for digital devices: This equipment has been tested and found to comply with
the limits for a Class A digital device, pursuant to part 15 of the FCC rules. These limits are designed to provide
4 SICAM A8000 Series, CP-8000, CP-8021, CP-8022, Manual

DC8-037-2, Edition 11.2020
Preface
reasonable protection against harmful interference in a residential installation. This equipment generates,
uses and can radiate radio frequency energy and, if not installed and used in accordance with the instructions,
may cause harmful interference to radio communications. However, there is no guarantee that interference
will not occur in a particular installation.
If this equipment does cause harmful interference to radio or television reception, which can be determined
by turning the equipment off and on, the user is encouraged to try to correct the interference by one or more
of the following measures:
• Reorient or relocate the receiving antenna.
• Increase the separation between the equipment and receiver.
• Connect the equipment into an outlet on a circuit different from that to which the receiver is connected.
• Consult the dealer or an experienced radio/TV technician for help.
IC Conformity Information
This Class A digital apparatus complies with the Canadian ICES-003 standard.
This device complies with the Industry Canada license-exempt RSS standard(s). Operation is subject to the
following two conditions: 1) This device may not cause interference, and 2) This device must accept any inter-
ference, including interference that may cause undesired operation of the device.
This equipment complies with radio frequency exposure limits set forth by Industry Canada for an uncon-
trolled environment.
! CAUTION
Injurious to health
² Install and operate the equipment with a minimum distance of 20 cm between the device and the
user or bystanders.
This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to
part 15 of the FCC rules. These limits are designed to provide reasonable protection against harmful interfer-
ence in a residential installation. This equipment generates uses and can radiate radio frequency energy and, if
not installed and used in accordance with the instructions, may cause harmful interference to radio communi-
cations. However, there is no guarantee that interference will not occur in a particular installation.
If this equipment causes harmful interference to radio or television reception, which can be determined by
turning the equipment off and on, the user is encouraged to try to correct the interference by one or more of
the following measures:
• Reorient or relocate the receiving antenna.
• Increase the separation between the equipment and receiver.
• Connect the equipment into an outlet on a circuit different from that to which the receiver is connected.
• Consult the dealer or an experienced radio/TV technician for help.
Standards
This product is UL-certified based on the Technical data:

UL 61010-2-201 incl. UL 61010-1; UL 61010-2-030
CAN/CSA-C22.2 No.61010-1, CAN/CSA-C22.2 No.61010-2-030 and CAN/CSA-C22.2 No.61010-2-201
IND. CONT. EQ.
E486146
E496940
For further information see UL database in the internet: http://ul.com.

Select Online Certifications Directory and insert E486146 or E496940 under UL File Number.

DC8-037-2, Edition 11.2020
Preface
NOTE
i The UL approval does not apply to CP-8000.
Additional Support
For questions about the system, contact your Siemens sales partner.
Customer Support Center

Our Customer Support Center provides a 24-hour service.
Siemens AG
Smart Infrastructure – Digital Grid
Customer Support Center
Tel.: +49 911 2155 4466
E-Mail: energy.automation@siemens.com
Training Courses
Inquiries regarding individual training courses should be addressed to our Training Center:
Siemens AG Phone: +49 (911) 433-7415
Siemens Power Academy TD Fax: +49 (911) 433-7929
Humboldtstrasse 59 E-mail: poweracademy@siemens.com
90459 Nuremberg Internet: www.siemens.com/poweracademy
Germany
Notes on Safety
This document is not a complete index of all safety measures required for operation of the equipment (module
or device). However, it comprises important information that must be followed for personal safety, as well as
to avoid material damage. Information is highlighted and illustrated as follows according to the degree of
danger:
! DANGER
DANGER means that death or severe injury will result if the measures specified are not taken.
² Comply with all instructions, in order to avoid death or severe injuries.
! WARNING
WARNING means that death or severe injury may result if the measures specified are not taken.
² Comply with all instructions, in order to avoid death or severe injuries.
! CAUTION
CAUTION means that medium-severe or slight injuries can occur if the specified measures are not taken.
² Comply with all instructions, in order to avoid moderate or minor injuries.

DC8-037-2, Edition 11.2020
Preface
NOTICE
NOTICE means that property damage can result if the measures specified are not taken.
² Comply with all instructions, in order to avoid property damage.
NOTE
i Important information about the product, product handling or a certain section of the documentation
which must be given attention.
Qualified Electrical Engineering Personnel

Only qualified electrical engineering personnel may commission and operate the equipment (module, device)
described in this document. Qualified electrical engineering personnel in the sense of this document are
people who can demonstrate technical qualifications as electrical technicians. These persons may commission,
isolate, ground and label devices, systems and circuits according to the standards of safety engineering.
Proper Use
The equipment (device, module) may be used only for such applications as set out in the catalogs and the
technical description, and only in combination with third-party equipment recommended and approved by
Siemens.
Problem-free and safe operation of the product depends on the following:
• Proper transport
• Proper storage, setup and installation
• Proper operation and maintenance

When electrical equipment is operated, hazardous voltages are inevitably present in certain parts. If proper
action is not taken, death, severe injury or property damage can result:
• The equipment must be grounded at the grounding terminal before any connections are made.
• All circuit components connected to the power supply may be subject to dangerous voltage.
• Hazardous voltages may be present in equipment even after the supply voltage has been disconnected
(capacitors can still be charged).
• Operation of equipment with exposed current-transformer circuits is prohibited. Before disconnecting the
equipment, ensure that the current-transformer circuits are short-circuited.
• The limiting values stated in the document must not be exceeded. This must also be considered during
testing and commissioning.
• The device does not represent a safety-oriented application; it does not provide fault protection. Any fault
protection must be provided by protection relays or other suitable means.
Selection of Used Symbols on the Device
Nr. Symbol Description
1 Direct current, IEC 60417, 5031
2 Alternating current, IEC 60417, 5032
3 Direct and alternating current, IEC 60417, 5033
4 Earth (ground) terminal, IEC 60417, 5017

DC8-037-2, Edition 11.2020
Preface
Nr. Symbol Description
5 Protective conductor terminal, IEC 60417, 5019
6 Caution, risk of electric shock
7 Caution, risk of danger, ISO 7000, 0434
8 Protective Insulation, IEC 60417, 5172, Safety Class II devices
9 Guideline 2002/96/EC for electrical and electronic devices
10 Guideline for the Eurasian Market

DC8-037-2, Edition 11.2020
Open Source Software
The product contains, among other things, Open Source Software developed by third parties. The Open
Source Software used in the product and the license agreements concerning this software can be found in the
Readme_OSS. These Open Source Software files are protected by copyright. Your compliance with those
license conditions will entitle you to use the Open Source Software as foreseen in the relevant license. In the
event of conflicts between Siemens license conditions and the Open Source Software license conditions, the
Open Source Software conditions shall prevail with respect to the Open Source Software portions of the soft-
ware. The Open Source Software is licensed royalty-free. Insofar as the applicable Open Source Software
License Conditions provide for it you can order the source code of the Open Source Software from your
Siemens sales contact – against payment of the shipping and handling charges – for a period of at least
3 years after purchase of the product. We are liable for the product including the Open Source Software
contained in it pursuant to the license conditions applicable to the product. Any liability for the Open Source
Software beyond the program flow intended for the product is explicitly excluded. Furthermore, any liability
for defects resulting from modifications to the Open Source Software by you or third parties is excluded. We
do not provide any technical support for the product if it has been modified.

DC8-037-2, Edition 11.2020
DC8-037-2, Edition 11.2020
Table of Contents
Preface.......................................................................................................................................................... 3
Open Source Software..................................................................................................................................9
1 General Information................................................................................................................................... 33
1.1 CP-8000, CP-8021, CP-8022 Base Units..............................................................................34
1.1.1 High Performing.......................................................................................................... 34
1.1.2 Different Fields of Application......................................................................................35
1.1.3 Mechanical Design...................................................................................................... 36
1.1.4 Local Operation (CP-8000)...........................................................................................37
1.1.5 Versatile Communication, Integrated Node Functionality............................................. 37
1.1.6 Expandibility................................................................................................................39
1.1.7 Data Storage on SD Card..............................................................................................40
1.1.8 Compatibility............................................................................................................... 40
1.2 Performance Properties..................................................................................................... 41
1.3 System Architecture.......................................................................................................... 42
1.3.1 CP-8000...................................................................................................................... 42
1.3.2 CP-8021 and CP-8022.................................................................................................. 42
2 System Overview........................................................................................................................................ 45
2.1 Modules............................................................................................................................46
2.1.1 Power Supply.............................................................................................................. 46
2.1.1.1 CP-8000.................................................................................................................46
2.1.1.2 CP-8021 and CP-8022............................................................................................ 46
2.1.2 Master Module............................................................................................................ 47
2.1.3 I/O Master Modul......................................................................................................... 49
2.1.4 I/O Modules................................................................................................................. 50
2.1.4.1 Internal I/O Modules...............................................................................................51
2.1.4.2 External SICAM I/O Modules................................................................................... 51
2.1.4.3 External SICAM TM I/O Modules..............................................................................52
2.1.4.4 Configuration Rules for I/O Modules....................................................................... 53
2.2 Communication................................................................................................................ 55
2.2.1 Protocol Elements........................................................................................................55
2.2.2 Interfaces.................................................................................................................... 56
2.2.3 Transmission Facilities................................................................................................. 58
2.2.4 Configuration Examples...............................................................................................59
2.3 Firmware Structure and Data Flow.................................................................................... 61
2.4 Engineering...................................................................................................................... 62
2.4.1 SICAM TOOLBOX II.......................................................................................................62
2.4.2 SICAM WEB for simple Applications.............................................................................. 63
2.4.3 Differences with the Engineering Tools........................................................................ 63

DC8-037-2, Edition 11.2020
Table of Contents
3 Function Packages...................................................................................................................................... 65
3.1 System Services................................................................................................................ 66
3.1.1 Communication with the Engineering System (SICAM TOOLBOX II).............................. 66
3.1.2 Simplified Engineering via SICAM WEB......................................................................... 67
3.1.3 Data-Flow Control....................................................................................................... 67
3.1.3.1 Messages with Process Information........................................................................ 68
3.1.4 Addressing.................................................................................................................. 68
3.1.4.1 Addressing of Automation Units............................................................................. 68
3.1.4.2 Addressing of the Process Information....................................................................68
3.1.5 Time Management...................................................................................................... 68
3.1.5.1 Clock..................................................................................................................... 68
3.1.5.2 Time Setting and Synchronization.......................................................................... 69
3.1.6 General Interrogation.................................................................................................. 69
3.1.7 Monitoring Functions.................................................................................................. 69
3.1.8 Failure Management................................................................................................... 70
3.1.9 Diagnostics and Signaling............................................................................................ 70
3.1.10 Autonomy................................................................................................................... 70
3.1.11 Storage of Application Data......................................................................................... 70
3.1.12 Storage of Firmware.................................................................................................... 71
3.1.13 Role Based Access Control............................................................................................71
3.1.14 IPSec VPN.................................................................................................................... 71
3.1.15 Security Logging..........................................................................................................71
3.2 Telecontrol....................................................................................................................... 72
3.2.1 Communication with Other Stations............................................................................ 72
3.2.1.1 Protocol Elements.................................................................................................. 72
3.2.1.2 Automatic or Selective Data Flow Routing...............................................................72
3.2.1.3 Data Storage.......................................................................................................... 73
3.2.1.4 Priority Control.......................................................................................................74
3.2.2 Communication within the Automation Unit................................................................ 74
3.2.3 Protocol Element Control and Return Information........................................................ 74
3.2.4 Decentralized Archive.................................................................................................. 74
3.2.5 Process Data Archive....................................................................................................75
3.2.6 Test Functions via SICAM WEB..................................................................................... 75
3.2.7 Process Data Input and Output ....................................................................................75
3.3 Automation...................................................................................................................... 76
3.3.1 Telecontrol Interface....................................................................................................76
3.3.1.1 Transfer of Messages with Process Information.......................................................76
3.3.1.2 Change Monitoring and Generation of Messages with Time Tag..............................77
3.3.2 Open/Closed-Loop Control Function.............................................................................77
3.3.2.1 Non-Volatile Storage.............................................................................................. 78
3.3.2.2 Task Management..................................................................................................78
3.3.2.3 Loading Application Program..................................................................................78
3.3.2.4 Test Functions........................................................................................................78
3.3.3 Process Data Input and Output.....................................................................................80
4 Ambient Conditions....................................................................................................................................81
4.1 Protection Type.................................................................................................................82
4.2 Mechanical Ambient Conditions........................................................................................ 83
4.3 Climatic Ambient Conditions............................................................................................. 84

DC8-037-2, Edition 11.2020
Table of Contents
4.4 Electromagnetic Compatibility...........................................................................................85

4.4.1 System Properties........................................................................................................ 85
4.4.2 Power Supply.............................................................................................................. 85
4.4.3 Digital I/Os...................................................................................................................87
4.4.4 Analog I/Os..................................................................................................................88
4.4.5 Communication with Insulation: RS-485/RS-232...........................................................89
4.4.6 Communication without Insulation: RS-232................................................................. 89
4.4.7 Communication with Insulation: LAN........................................................................... 90
4.5 Storage and Transport.......................................................................................................91
5 System Components and Technical Data................................................................................................... 93

5.1 Power Consumption of Total System................................................................................. 94
5.1.1 Master Module without External Consumers................................................................ 94
5.1.2 Master Module with External Consumers..................................................................... 94
5.2 Master Modules................................................................................................................ 95
5.2.1 CP-8000...................................................................................................................... 95
5.2.1.1 Position of the Interfaces........................................................................................96
5.2.1.2 Technical Data....................................................................................................... 97
5.2.1.3 Pin Assignment...................................................................................................... 99
5.2.1.4 Block Diagram and External Circuitry.................................................................... 101
5.2.2 CP-8021 and CP-8022................................................................................................ 101
5.2.2.1 Technical Data..................................................................................................... 101
5.2.2.2 Pin Assignment.................................................................................................... 105
5.3 Power Supply Modules.................................................................................................... 108
5.3.1 PS-8630 (Internal to CP-8000)................................................................................... 108
5.3.1.1 Technical Data..................................................................................................... 108
5.3.1.2 Pin Assignment.................................................................................................... 109
5.3.2 PS-8620, PS-8622...................................................................................................... 110
5.3.2.1 Technical Data..................................................................................................... 111
5.3.2.2 Pin Assignment.................................................................................................... 112
5.3.3 PS-8640, PS-8642...................................................................................................... 113
5.3.3.1 Technical Data..................................................................................................... 114
5.3.3.2 Pin Assignment.................................................................................................... 115
5.4 SICAM I/O Modules..........................................................................................................117
5.4.1 DI-8100 (Internal to CP-8000).................................................................................... 117
5.4.1.1 Features...............................................................................................................117
5.4.1.2 Functions.............................................................................................................117
5.4.1.3 Technical Data..................................................................................................... 119
5.4.1.4 Pin Assignment.................................................................................................... 119
5.4.2 DI-8110.....................................................................................................................122
5.4.2.1 Features...............................................................................................................122
5.4.2.2 Functions.............................................................................................................122
5.4.2.3 Technical Data..................................................................................................... 124
5.4.2.4 Pin Assignment and Display..................................................................................125
5.4.3 DI-8111.....................................................................................................................128
5.4.3.1 Features...............................................................................................................128
5.4.3.2 Functions.............................................................................................................128

DC8-037-2, Edition 11.2020
Table of Contents
5.4.3.3 Technical Data..................................................................................................... 130

5.4.4 DI-8112..................................................................................................................... 134
5.4.4.1 Features...............................................................................................................134
5.4.4.2 Functions.............................................................................................................134
5.4.4.3 Technical Data..................................................................................................... 136
5.4.5 DI-8113..................................................................................................................... 140
5.4.5.1 Features...............................................................................................................140
5.4.5.2 Functions.............................................................................................................140
5.4.5.3 Technical Data..................................................................................................... 142
5.4.6 DO-8203 (Internal to CP-8000).................................................................................. 145
5.4.6.1 Features .............................................................................................................. 145
5.4.6.2 Functions.............................................................................................................145
5.4.6.3 Technical Data..................................................................................................... 147
5.4.6.4 Pin Assignment.................................................................................................... 148
5.4.7 DO-8212................................................................................................................... 152
5.4.7.1 Features...............................................................................................................152
5.4.7.2 Functions.............................................................................................................152
5.4.7.3 Technical Data..................................................................................................... 154
5.4.8 AI-8310..................................................................................................................... 160
5.4.8.1 Features...............................................................................................................160
5.4.8.2 Functions.............................................................................................................160
5.4.8.3 Technical Data..................................................................................................... 162
5.4.9 AI-8320..................................................................................................................... 166
5.4.9.1 Features...............................................................................................................166
5.4.9.2 Functions.............................................................................................................166
5.4.9.3 Technical Data..................................................................................................... 167
5.4.10 AI-8510..................................................................................................................... 171
5.4.10.1 Features...............................................................................................................171
5.4.10.2 Functions.............................................................................................................172
5.4.10.3 Technical Data..................................................................................................... 173
5.4.10.5 Block Diagram......................................................................................................177
5.4.10.6 External Circuitry..................................................................................................178
5.4.11 AI-8511..................................................................................................................... 184
5.4.11.1 Features...............................................................................................................184
5.4.11.2 Functions.............................................................................................................185
5.4.11.3 Technical Data..................................................................................................... 186
5.4.11.5 Block Diagram......................................................................................................190
5.4.12 CM-8820................................................................................................................... 194
5.4.12.1 Features...............................................................................................................194
5.4.12.2 Functions.............................................................................................................194

DC8-037-2, Edition 11.2020
Table of Contents
5.4.12.3 Technical Data..................................................................................................... 195

5.4.12.4 Pin Assignment.................................................................................................... 197
5.4.12.5 Block Diagram......................................................................................................198
5.4.13 AO-8380................................................................................................................... 200
5.4.13.1 Features...............................................................................................................201
5.4.13.2 Functions.............................................................................................................201
5.4.13.3 Technical Data..................................................................................................... 201
5.4.14 CM-8830................................................................................................................... 205
5.4.14.1 Features...............................................................................................................205
5.4.14.2 Functions.............................................................................................................205
5.4.14.3 Technical Specifications....................................................................................... 207
5.4.14.4 Block Diagram......................................................................................................207
5.5 SICAM TM I/O Modules.................................................................................................... 208
5.5.1 DI-6100, DI-6101, DI-6104.........................................................................................208
5.5.1.1 Functions.............................................................................................................208
5.5.2 DI-6102, DI-6103.......................................................................................................209
5.5.2.1 Functions.............................................................................................................209
5.5.3 DO-6200................................................................................................................... 211
5.5.3.1 Functions.............................................................................................................211
5.5.4 DO-6212................................................................................................................... 212
5.5.4.1 Functions.............................................................................................................212
5.5.5 DO-6220, DO-6222, DO-6230....................................................................................213
5.5.5.1 Functions.............................................................................................................213
5.5.6 AI-6300, AI-6307, AI-6308......................................................................................... 214
5.5.6.1 Functions.............................................................................................................214
5.5.7 AI-6310..................................................................................................................... 215
5.5.7.1 Functions.............................................................................................................215
5.5.8 AO-6380................................................................................................................... 216
5.5.8.1 Functions.............................................................................................................216
5.5.9 TE-6430.................................................................................................................... 216
5.5.9.1 Functions.............................................................................................................216
5.6 MTBF Data...................................................................................................................... 217
5.6.1 MTBF Values of the SICAM A8000 Modules................................................................ 217
5.6.2 MTBF Values of SICAM TM I/O Modules...................................................................... 217
6 Installation and Circuitry.......................................................................................................................... 219

6.1 Mechanical Design.......................................................................................................... 220
6.1.1 CP-8000.................................................................................................................... 220
6.1.1.1 Locking Hook....................................................................................................... 221
6.1.1.2 Type Plate............................................................................................................ 222
6.1.2 CP-802x.................................................................................................................... 223
6.1.2.1 Locking Hook....................................................................................................... 223
6.1.2.2 Type Plate............................................................................................................ 224
6.1.3 SICAM I/O Modules.................................................................................................... 224
6.1.3.1 Labeling...............................................................................................................224
6.1.3.2 Screw Terminal Types...........................................................................................225
6.2 Dimensions.....................................................................................................................226
6.2.1 CP-8000 Front View...................................................................................................226
6.2.2 CP-8000 Side View.....................................................................................................227

DC8-037-2, Edition 11.2020
Table of Contents
6.2.3 CP-802x Front and Side View..................................................................................... 228

6.2.4 SICAM I/O Module Front and Side View...................................................................... 229
6.3 Installation Location and Position.................................................................................... 230
6.3.1 DIN Rail (TS35 Rail).................................................................................................... 230
6.3.2 Cable Duct.................................................................................................................230
6.4 Assembly of CP-8000 ..................................................................................................... 232
6.4.1 Space Requirement for the Basic Device..................................................................... 232
6.4.2 Space Requirement with SICAM I/O Modules.............................................................. 233
6.4.3 Space Required with SICAM TM I/O Modules...............................................................233
6.4.4 Mounting of the Basic Device.....................................................................................235
6.4.5 Removal of the Basic Device.......................................................................................237
6.4.6 Assembly of External SICAM I/O Modules....................................................................238
6.4.6.1 Mounting of the Coupling Module for SICAM I/O Modules.....................................238
6.4.6.2 Mounting of the Bus Connector for SICAM I/O Modules.........................................239
6.4.6.3 Mounting of the SICAM I/O Modules..................................................................... 240
6.4.6.4 Removal of the SICAM I/O Modules....................................................................... 240
6.4.7 Assembly of External SICAM TM I/O Modules.............................................................. 241
6.4.7.1 Mounting of the Coupling Module for SICAM TM I/O Modules............................... 241
6.4.7.2 Mounting of the SICAM TM I/O Modules............................................................... 242
6.4.7.3 Removal of the SICAM TM I/O Modules................................................................. 243
6.4.8 Separating of Basic Device and I/O Coupling Module.................................................. 243
6.5 Assembly of CP-802x.......................................................................................................245
6.5.1 Space Requirement for the Basic Device with Power Supply........................................ 245
6.5.2 Space Requirement CP-802x with SICAM I/O Modules.................................................246
6.5.3 Space Required for CP-802x with SICAM TM I/O Modules............................................ 246
6.5.4 Mounting of a SICAM A8000 Module......................................................................... 247
6.5.5 Removal of a SICAM A8000 Module........................................................................... 249
6.5.6 Mounting of the Power Supply Module...................................................................... 250
6.5.7 Assembly of External SICAM I/O Modules....................................................................251
6.5.7.1 Mounting of the Bus Connector for SICAM I/O Modules.........................................252
6.5.7.2 Mounting of the SICAM I/O Modules .................................................................... 252
6.5.7.3 Removal of the SICAM I/O Modules....................................................................... 253
6.5.8 Assembly of External SICAM TM I/O Modules.............................................................. 253
6.5.8.1 Mounting of the Coupling Module for SICAM TM I/O Modules............................... 254
6.5.8.2 Mounting of the SICAM TM I/O Modules............................................................... 254
6.5.8.3 Removal of the SICAM TM I/O Modules................................................................. 255
6.6 Memory Cards.................................................................................................................256
6.6.1 SD Card..................................................................................................................... 256
6.6.1.1 Inserting the SD Card........................................................................................... 256
6.6.1.2 Removing the SD Card..........................................................................................256
6.6.2 SIM Card (CP-8022 only)............................................................................................ 256
6.6.2.1 Inserting the SIM Card.......................................................................................... 257
6.6.2.2 Removing the SIM Card........................................................................................ 257
6.7 Wiring.............................................................................................................................258
6.7.1 Power Supply............................................................................................................ 258
6.7.2 Process Peripherals.................................................................................................... 258
6.7.3 Shielding................................................................................................................... 259
6.7.4 Protective Earth/Ground.............................................................................................259
6.8 Switching the Device On and Off..................................................................................... 260

DC8-037-2, Edition 11.2020
Table of Contents
6.9 Setup of External Communication Connections............................................................... 261

6.9.1 Serial Communication............................................................................................... 262
6.9.1.1 Communication via Interface Converter................................................................262
6.9.1.2 Multi-Point Traffic via Leased Line Modem/VFT Channel Modem........................... 265
6.9.1.3 Multi-Point Traffic via Glass Fiber Optic................................................................. 268
6.9.1.4 Dial-Up Traffic Analog with Westermo TD-36 (TDW-33)......................................... 283
6.9.1.5 Dial-Up Traffic ISDN with Westermo IDW-90..........................................................284
6.9.1.6 Dial-Up Traffic GSM; SMS Sender/Receiver............................................................ 285
6.9.1.7 Point-to-Point Traffic with Other AU......................................................................287
6.9.2 Ethernet TCP/IP.......................................................................................................... 290
6.9.2.1 Communication via LAN/WAN...............................................................................290
6.9.2.2 Communication via GPRS..................................................................................... 291
7 Preparing Engineering..............................................................................................................................293
7.1 Engineering Tools........................................................................................................... 294
7.1.1 Differences................................................................................................................294
7.1.2 Interlocking............................................................................................................... 294
7.2 Engineering Software......................................................................................................295
7.2.1 SICAM TOOLBOX II.....................................................................................................295
7.2.1.1 Prerequisites........................................................................................................ 295
7.2.2 SICAM WEB................................................................................................................296
7.2.2.1 Prerequisites........................................................................................................ 297
7.2.2.2 Program Sicam_First_Startup ...............................................................................297
7.2.3 SICAM Device Manager.............................................................................................. 298
7.2.3.1 Prerequisites........................................................................................................ 298
7.3 Loadable Firmwares........................................................................................................ 299
7.4 Memory Cards.................................................................................................................301
7.4.1 SD Card..................................................................................................................... 301
7.4.1.1 Configurable SD Card Usage................................................................................. 301
7.4.1.2 SD Card Reader/Writer.......................................................................................... 301
7.4.2 SIM Card (only CP-8022)............................................................................................ 302
7.5 Communication Interfaces.............................................................................................. 303
7.5.1 Required Accessories................................................................................................. 303
7.6 Connect Engineering PC with the Target System.............................................................. 304
7.6.1 SICAM TOOLBOX II.....................................................................................................304
7.6.1.1 Physical Connection............................................................................................. 304
7.6.2 SICAM WEB................................................................................................................311
7.6.2.1 Physical Connection............................................................................................. 311
7.6.2.2 Communication with the Target Device................................................................ 315
7.7 Interaction with Engineering Tool....................................................................................322
7.7.1 SICAM TOOLBOX II.....................................................................................................322
7.7.1.1 Structure..............................................................................................................322
7.7.2 SICAM WEB................................................................................................................323
7.7.2.1 Dashboard........................................................................................................... 323
7.7.2.2 General Buttons................................................................................................... 324
7.7.2.3 Parameter Entry................................................................................................... 326
7.7.2.4 Automatic Restart Request................................................................................... 332
7.7.2.5 SICAM TOOLBOX II Locking ..................................................................................333
7.7.2.6 Language Versions............................................................................................... 333
7.7.2.7 Navigation with the Web Browser.........................................................................333
7.7.2.8 Session Monitoring.............................................................................................. 334
7.7.2.9 Exceptions with Engineering via SICAM WEB.........................................................334

DC8-037-2, Edition 11.2020
Table of Contents
8 Engineering via SICAM TOOLBOX II..........................................................................................................337

8.1 Telecontrol..................................................................................................................... 338
8.1.1 Presets...................................................................................................................... 340
8.1.1.1 Users and Rights.................................................................................................. 340
8.1.1.2 Password............................................................................................................. 340
8.1.1.3 Language.............................................................................................................341
8.1.1.4 Role Based Access Control.................................................................................... 341
8.1.2 Project Access............................................................................................................343
8.1.2.1 Logon.................................................................................................................. 343
8.1.2.2 Logoff..................................................................................................................343
8.1.2.3 Change Password.................................................................................................343
8.1.3 Plant Configuration....................................................................................................343
8.1.4 Import Firmware........................................................................................................344
8.1.5 Configuration and Settings for Telecontrol................................................................. 344
8.1.5.1 Hardware Configuration....................................................................................... 344
8.1.5.2 System-Technical Settings.................................................................................... 345
8.1.5.3 Process-Technical Settings....................................................................................346
8.1.5.4 Decentralized Archive (DEAR)............................................................................... 348
8.1.6 Transform Parameters............................................................................................... 348
8.1.7 Import, Export and Backup of Engineering Data..........................................................348
8.1.8 Documentation......................................................................................................... 348
8.1.8.1 Hardware Configuration....................................................................................... 349
8.1.8.2 Assembly Technique............................................................................................ 349
8.1.8.3 Interface to ELCAD............................................................................................... 349
8.1.8.4 Telecontrol Function............................................................................................ 349
8.1.9 Commissioning and Test............................................................................................350
8.1.9.1 Loading Engineering Data.................................................................................... 350
8.1.9.2 Parameter Comparison......................................................................................... 351
8.1.9.3 Test Functions......................................................................................................351
8.1.9.4 Displaying Decentralized Archive (DEAR).............................................................. 355
8.2 Automation.................................................................................................................... 356
8.2.1 Creation of a Function Diagram with CAEx plus........................................................ 356
8.2.1.1 Restrictions when Creating a Function Diagram.................................................... 357
8.2.1.2 Configuring External Signals.................................................................................358
8.2.1.3 Program Code Generation.................................................................................... 359
8.2.2 Documentation......................................................................................................... 360
8.2.2.1 Cross Reference List............................................................................................. 360
8.2.2.2 Open-/Closed-Loop Control Function.................................................................... 360
8.2.3.1 Loading Program Code......................................................................................... 361
8.2.3.2 Test Functions......................................................................................................361
9 Engineering via SICAM WEB..................................................................................................................... 363

9.1 Telecontrol..................................................................................................................... 364
9.1.1 Starting and Finishing a Session.................................................................................365
9.1.1.1 Logon.................................................................................................................. 365
9.1.1.2 Logoff..................................................................................................................366
9.1.1.3 Initial Login on the Target Device with SICAM WEB............................................... 367
9.1.1.4 Creating a Local User............................................................................................368
9.1.2 Basic Settings............................................................................................................ 369
9.1.2.1 Authentication Procedure.....................................................................................370
9.1.2.2 Change Web Server Password...............................................................................372
9.1.2.3 Differentiation Secure/Non-Secure Passwords....................................................... 373
9.1.2.4 Set IP Addresses................................................................................................... 376

DC8-037-2, Edition 11.2020
Table of Contents
9.1.2.5 Security Settings for Internet Security (IPSec)........................................................379

9.1.2.6 Settings for Internal GPRS Modem (CP-8022)........................................................ 379
9.1.2.7 Autoconfiguration................................................................................................381
9.1.3 Common Settings...................................................................................................... 384
9.1.3.1 Configuration of the Target Device....................................................................... 384
9.1.3.2 Topology............................................................................................................. 385
9.1.3.3 Failure Behavior upon Fault.................................................................................. 385
9.1.4 Configuring Optional Modules................................................................................... 385
9.1.4.1 Overview............................................................................................................. 385
9.1.4.2 Protocol Elements................................................................................................ 387
9.1.4.3 I/O Master Module................................................................................................387
9.1.5 Configuring Time Management................................................................................. 389
9.1.5.1 Time Synchronization...........................................................................................389
9.1.5.2 Daylight Saving Time Rule.................................................................................... 392
9.1.6 Local Time Setting..................................................................................................... 393
9.1.7 Configuring Communication......................................................................................393
9.1.7.1 Common Settings................................................................................................ 394
9.1.7.2 Interfaces for Communication.............................................................................. 394
9.1.7.3 Selection of the Transmission Facility................................................................... 397
9.1.7.4 Settings for Messages.......................................................................................... 397
9.1.7.5 Data Management and Priority Control................................................................. 398
9.1.8 Configuration of the Decentralized Archive................................................................ 399
9.1.9 Configuration of the Process Data Archive..................................................................401
9.1.10 Configuration of the Local Process Data Display (CP-8000 Only)................................. 402
9.1.11 Configuring Periphery and Internal Signals................................................................. 402
9.1.11.1 Defining Signals................................................................................................... 403
9.1.11.2 Assigning Signals to the Master Module................................................................408
9.1.11.3 Assigning Signals to the I/O Master Module ..........................................................422
9.1.11.4 Assigning Signals to the I/O Module......................................................................426
9.1.11.5 Signal Wiring........................................................................................................456
9.1.11.6 Importing and Exporting a Signal List................................................................... 465
9.1.12 Using CP-8000/CP-802x as SICAM PAS I/O...................................................................467
9.1.12.1 Synchronization of the I/O Configuration in SICAM PAS......................................... 469
9.1.13 Test Functions........................................................................................................... 469
9.1.13.1 Supported Signal Types........................................................................................ 470
9.1.13.2 Display Process Values..........................................................................................471
9.1.13.3 Changing Process Values...................................................................................... 475
9.1.14 Logging.....................................................................................................................479
9.1.14.1 Show Event List....................................................................................................479
9.1.14.2 Show Alarm List................................................................................................... 482
9.2 Automation.................................................................................................................... 485
9.2.1 Creating an Instruction List........................................................................................ 485
9.2.1.1 Structure of the Instruction List............................................................................ 486
9.2.1.2 Syntax for Instructions......................................................................................... 486
9.2.1.3 Instruction Comments..........................................................................................488
9.2.1.4 Settings in the Application Program......................................................................488
9.2.1.5 System Information..............................................................................................491
9.2.1.6 Command Processing According to IEC 60870-5-101/104..................................... 492
9.2.1.7 Generation of Integrated Totals............................................................................ 493
9.2.2.1 Common Functions.............................................................................................. 494
9.2.2.2 Test Functions......................................................................................................497
9.3 Administrative Functions.................................................................................................508
9.3.1 Restart Device............................................................................................................508

DC8-037-2, Edition 11.2020
Table of Contents
9.3.2 Download Device Settings......................................................................................... 510

9.3.3 Restoring Device Settings...........................................................................................511
9.3.3.1 Loading Device Settings Offline............................................................................ 512
9.3.4 Uploading ICD/IID Files...............................................................................................514
9.3.5 Downloading SICAM PAS IO Configurations................................................................516
9.3.6 Download Process Data Archive................................................................................. 521
9.3.7 Update Firmware.......................................................................................................523
9.3.8 Updating SICAM WEB.................................................................................................525
9.3.9 Installing the Language Package................................................................................ 526
10 Engineering via SICAM Device Manager.................................................................................................. 529

10.1 General Information........................................................................................................530
11 Service...................................................................................................................................................... 531
11.1 Maintenance, Cleaning, and Waste Disposal.................................................................... 532
11.2 Environmental Protection Hints....................................................................................... 533
11.3 Control and Display Elements.......................................................................................... 534
11.3.1 Master Module CP-8000............................................................................................ 534
11.3.2 Master Module CP-802x.............................................................................................536
11.3.3 Power Supply Modules...............................................................................................538
11.3.4 SICAM A8000 I/O Modules......................................................................................... 540
11.3.5 LED Module............................................................................................................... 541
11.3.6 LCD Display (CP-8000 only)........................................................................................544
11.3.6.1 Navigation........................................................................................................... 544
11.3.6.2 Device Information...............................................................................................545
11.3.6.3 Configuration.......................................................................................................548
11.3.6.4 Monitoring...........................................................................................................551
11.4 Checks and System Displays............................................................................................ 558
11.4.1 Checks during Startup................................................................................................558
11.4.2 Checks after Startup.................................................................................................. 560
11.4.3 Behavior of the Process Outputs upon Startup and Failure.......................................... 560
11.5 Diagnostics..................................................................................................................... 562
11.5.1 Distinction of the Error Types..................................................................................... 562
11.5.2 SICAM TOOLBOX II.....................................................................................................563
11.5.2.1 Connection Possibilities for the Diagnosis............................................................. 563
11.5.2.2 Diagnosis Overview..............................................................................................565
11.5.2.3 System Performance............................................................................................ 567
11.5.2.4 Diagnosis of the Open-/Closed-Loop Control Function...........................................568
11.5.3 SICAM WEB................................................................................................................569
11.5.3.1 Connection Options for the Diagnosis...................................................................569
11.5.3.2 Diagnosis Overview..............................................................................................571
11.5.3.3 Device Information...............................................................................................572
11.5.3.4 Diagnostics.......................................................................................................... 573
11.5.3.5 Time Diagnostics..................................................................................................581
11.5.3.6 Diagnostics of the Open/Closed-Loop Control Function......................................... 581
11.6 Maintenance of the Hardware......................................................................................... 582
11.6.1 Identifying Hardware Errors....................................................................................... 582
11.6.1.1 Modules...............................................................................................................582
11.6.1.2 SD Card................................................................................................................582
11.6.2 Replacement of a Module.......................................................................................... 583

DC8-037-2, Edition 11.2020
Table of Contents
11.6.3 Adapting Newly Installed I/O Modules in the Parameter Setting.................................. 584
11.6.3.1 Adding I/O Modules..............................................................................................584
11.6.4 Replacing the SD Card................................................................................................584
11.6.4.1 Initialization of the Firmware................................................................................585
11.6.5 Replacement of the SIM Card (only CP-8022)............................................................. 585
11.7 Firmware Update............................................................................................................ 586
11.7.1 SICAM TOOLBOX II.....................................................................................................586
11.7.1.1 Interrogation of the Firmware Revision................................................................. 586
11.7.1.2 Importing Master Data into the SICAM TOOLBOX II............................................... 586
11.7.1.3 Loading Firmware Codes into the Target Device....................................................587
11.7.2 SICAM WEB................................................................................................................587
11.7.2.1 Loading Firmware to the Target Device.................................................................587
11.7.3 Errors with Loading of Firmware ............................................................................... 588
11.8 Resetting Device to Factory Settings................................................................................ 589
11.9 Remote Servicing............................................................................................................ 591
11.9.1 Configuration of Server and Clients............................................................................591
12 Communication Protocols........................................................................................................................ 593

12.1 Introduction....................................................................................................................594
12.1.1 Overview...................................................................................................................594
12.1.2 Limits of the Communication Protocols...................................................................... 594
12.1.3 Common Functions................................................................................................... 595
12.1.3.1 Control location function for commands and setpoint values................................ 595
12.1.3.2 Data Management on the BSE for Communication Protocols................................. 600
12.2 IEC 60870-5-101 (Dial-Up Communication)..................................................................... 604
12.2.1 Introduction.............................................................................................................. 604
12.2.2 General Functions..................................................................................................... 604
12.2.3 Operating Modes.......................................................................................................605
12.2.4 Communication.........................................................................................................606
12.2.5 Controlling Connection Establishment and Disconnection.......................................... 606
12.2.5.1 Security for Dial-Up Traffic....................................................................................607
12.2.5.2 Connection Establishment spontaneously and cyclically, Controlling Station
↔ Controlled Station............................................................................................610
12.2.5.3 Connection Setup Control via Modem Commands................................................ 617
12.2.5.4 Access Control (LOGIN with Password + Access Key)............................................. 620
12.2.5.5 Disconnection Control..........................................................................................621
12.2.6 Communication according to IEC 60870-5-101.......................................................... 623
12.2.6.1 Data Acquisition by Polling (Station Interrogation)................................................ 623
12.2.6.2 Station Initialization............................................................................................. 626
12.2.6.3 Acquisition of Events (transmission of data ready to be sent)................................ 626
12.2.6.4 General Interrogation, Outstation Interrogation....................................................626
12.2.6.5 Clock Synchronization.......................................................................................... 627
12.2.6.6 Command Transmission....................................................................................... 628
12.2.6.7 Transmission of Integrated Totals......................................................................... 629
12.2.6.8 Acquisition of Transmission Delay.........................................................................629
12.2.7 SMS Messages........................................................................................................... 630
12.2.8 Coordination of Several Masters in Multi-Master Mode............................................... 630
12.2.9 Standby Transmission Line(s) over Standby Telephone Number(s)..............................631
12.2.10 Multi-Hierarchical Configurations...............................................................................631
12.2.11 Standby Transmission Line via Dial up Traffic..............................................................632

DC8-037-2, Edition 11.2020
Table of Contents
12.2.12 Optimized Parameters for Selected Transmission Facilities..........................................633

12.2.12.1 Supported Combinations for Dial-Up Modems.......................................................641
12.2.12.2 ASCII Mode.......................................................................................................... 642
12.2.12.3 CRC Generator Polynomial....................................................................................643
12.2.13 Toll-Saving Transmission Strategies............................................................................643
12.2.14 Having a Telephone Set Connected in Parallel............................................................ 644
12.2.15 Functions for the Support of Redundant Communication Routes................................ 644
12.2.15.1 Redundancy Mode PRE Redundancy (applies only for Remote Station =
Central Station)....................................................................................................644
12.2.16 Message Conversion.................................................................................................. 644
12.2.16.1 Blocking...............................................................................................................645
12.2.16.2 Class 1, 2 Data..................................................................................................... 645
12.2.17 Protocol Element Control and Return Information...................................................... 645
12.2.17.1 Protocol Element Control..................................................................................... 646
12.2.17.2 Protocol Element Return Information....................................................................650
12.3 IEC 60870-5-101 (Point-to-Point Traffic).......................................................................... 655
12.3.1 Introduction.............................................................................................................. 655
12.3.2 Functions.................................................................................................................. 655
12.3.3 Modes of Operation...................................................................................................657
12.3.4 Communication.........................................................................................................658
12.3.5.1 Basic Configuration.............................................................................................. 658
12.3.5.2 Data Transmission Procedure................................................................................659
12.3.5.4 Acquisition of events (transmission of data ready to be sent)................................ 661
12.3.5.5 General interrogation, Outstation interrogation....................................................661
12.3.5.7 Command transmission........................................................................................662
12.3.5.9 File Transfer......................................................................................................... 662
12.3.5.10 Acquisition of Transmission Delay.........................................................................663
12.3.6 Optimized Parameters for selected Transmission Facilities.......................................... 663
12.3.7 Function for the Support of Redundant Communication Routes..................................666
12.3.7.1 PRE-Redundancy.................................................................................................. 667
12.3.7.2 NUC-Redundancy................................................................................................. 668
12.3.7.3 Port-Redundancy (deactivation of Interface)......................................................... 669
12.3.8.1 Blocking...............................................................................................................669
12.3.8.2 Special functions..................................................................................................670
12.3.9.1 Protocol element control...................................................................................... 689
12.3.9.2 Protocol Element Feedback.................................................................................. 689
12.3.10 Interoperability IEC 60870-5-101 (BPP)...................................................................... 690
12.3.10.1 System or device function.................................................................................... 690
12.3.10.2 Network configuration......................................................................................... 691
12.3.10.3 Physical layer....................................................................................................... 691
12.3.10.4 Link Layer............................................................................................................ 692
12.3.10.5 Application Layer................................................................................................. 693
12.3.10.6 Basic application functions................................................................................... 699
12.4 IEC 60870-5-101 (Multi-Point Traffic).............................................................................. 703
12.4.1 Introduction.............................................................................................................. 703
12.4.2 Functions.................................................................................................................. 703

DC8-037-2, Edition 11.2020
Table of Contents
12.4.4 Communication.........................................................................................................708
12.4.5.3 Acquisition of events (transmission of data ready to be sent)................................ 714
12.4.5.7 Transmission of integrated totals..........................................................................717
12.4.5.8 Acquisition of transmission delay......................................................................... 717
12.4.6 Optimized Parameters for Selected Transmission Facilities..........................................717
12.4.7 Standby transmission line over the public telephone network (PSTN)......................... 721
12.4.8 Data Transmission using Time Slot Radio....................................................................724
12.4.9 Data Transmission in Relay Operation Mode (Multi-Point Traffic with Routing)............ 725
12.4.9.1 Main and Standby Transmission Line.................................................................... 728
12.4.9.2 Routing Method................................................................................................... 729
12.4.10.1 PRE-Redundancy.................................................................................................. 732
12.4.10.2 NUC-Redundancy................................................................................................. 734
12.4.11.1 Blocking...............................................................................................................735
12.4.11.2 Class 1, 2 Data..................................................................................................... 736
12.4.11.3 Special Functions................................................................................................. 736
12.4.12.1 Protocol element control messages...................................................................... 742
12.4.12.2 Protocol element return information.................................................................... 743
12.4.13 Interoperability IEC 60870-5-101 (UMP).....................................................................744
12.4.13.3 Physical layer....................................................................................................... 745
12.4.13.4 Link Layer............................................................................................................ 746
12.5 IEC 60870-5-103.............................................................................................................758
12.5.1 Introduction.............................................................................................................. 758
12.5.2 Functions.................................................................................................................. 758
12.5.4 Communication.........................................................................................................761
12.5.5.4 General Interrogation, Outstation Interrogation....................................................768
12.5.5.8 File Transfer......................................................................................................... 770
12.5.6 Transfer of Parameters for Reyrolle Protection Equipment.......................................... 777
12.5.7 Optimized Parameters for selected Transmission Facilities.......................................... 781
12.5.8.1 PRE-Redundancy.................................................................................................. 786
12.5.8.2 Ring Redundancy................................................................................................. 786
12.5.8.3 Port-Redundancy..................................................................................................788

DC8-037-2, Edition 11.2020
Table of Contents

12.5.9.1 Message Conversion IEC 60870-5-101 ↔ IEC 60870-5-103...................................789
12.5.9.2 Message Conversion IEC 60870-5-101 ↔IEC 60870-5-101....................................809
12.5.9.3 Message Conversion IEC 60870-5-101 ↔ IEC 60870-5-103 (101)......................... 809
12.5.9.4 Blocking...............................................................................................................810
12.5.9.5 Class 1, 2 Data..................................................................................................... 811
12.5.10.2 Protocol element return information.................................................................... 821
12.5.11 Interoperability IEC 60870-5-103............................................................................... 823
12.5.11.1 Physical layer....................................................................................................... 823
12.5.11.2 Link Layer............................................................................................................ 823
12.5.11.4 Selection of standard-ASDU in monitor direction...................................................824
12.5.11.5 Selection of standard-ASDU in control direction.................................................... 824
12.5.11.6 Selection of standard information numbers in monitor direction........................... 825
12.5.11.7 Selection of standard information numbers in control direction............................ 829
12.5.11.9 Miscellaneous...................................................................................................... 830
12.6 IEC 60870-5-104.............................................................................................................832
12.6.1 Introduction.............................................................................................................. 832
12.6.2 Functions.................................................................................................................. 833
12.6.4 Communication.........................................................................................................835
12.6.5 Communication via Ethernet TCP/IP according to IEC 60870-5-104............................. 836
12.6.5.1 Ethernet interface................................................................................................ 836
12.6.5.2 Definition of the Connections...............................................................................836
12.6.5.8 Transmission of integrated totals..........................................................................852
12.6.6.1 104-Redundancy.................................................................................................. 853
12.6.6.2 104 redundancy „Controlling“ ..............................................................................854
12.6.6.3 PRE-Redundancy.................................................................................................. 856
12.6.6.4 Port-Redundancy (deactivation of Interface)......................................................... 858
12.6.6.5 PSI-Redundancy (Synchronous Connections)........................................................ 858
12.6.7.1 Blocking...............................................................................................................861
12.6.8.2 Protocol Element Return Information....................................................................884
12.6.9 Interoperability IEC 60870-5-104............................................................................... 885
12.6.9.3 Physical layer....................................................................................................... 886
12.6.9.4 Link Layer............................................................................................................ 887
12.7 IEC 61850....................................................................................................................... 900
12.7.1 Introduction.............................................................................................................. 900

DC8-037-2, Edition 11.2020
Table of Contents
12.7.2 Functions.................................................................................................................. 901

12.7.4 Communication- ET85 Client .....................................................................................906
12.7.5 Communication - ET85 Server....................................................................................907
12.7.6 Communication via Ethernet TCP/IP according to IEC 61850....................................... 907
12.7.6.1 Objects and Data..................................................................................................912
12.7.6.2 Definition of the Connections...............................................................................930
12.7.6.4 Recording events (transferring data ready for sending)......................................... 936
12.7.6.6 Clock synchronization.......................................................................................... 942
12.7.6.9 File Transfer (Disturbance Records).......................................................................955
12.7.7.1 SICAM RTUs Redundancy...................................................................................... 959
12.7.7.2 Server Redundancy.............................................................................................. 959
12.7.7.3 GOOSE Redundancy............................................................................................. 960
12.7.8.1 General................................................................................................................962
12.7.8.2 Conversion IEC 60870-5-101/104 ↔ IEC 61850.................................................... 963
12.7.8.3 Datapoint Settings in the Detailed Routing............................................................990
12.7.8.4 Special Functions............................................................................................... 1005
12.7.9 Protocol Element Control and Return Information.................................................... 1018
12.7.9.1 Protocol Element Control................................................................................... 1019
12.7.9.2 Protocol Element Return Information..................................................................1020
12.7.10 Web Server.............................................................................................................. 1021
12.7.10.1 IEC 61850 Edition 1 [Client + Server].................................................................. 1021
12.7.10.2 IEC 61850 Edition 2 [Client + Server].................................................................. 1036
12.8 Modbus RTU................................................................................................................. 1058
12.8.1 Introduction............................................................................................................ 1058
12.8.2 Functions................................................................................................................ 1059
12.8.3 Modes of Operation.................................................................................................1066
12.8.4 Communication.......................................................................................................1066
12.8.5 Communication according to Modbus RTU............................................................... 1068
12.8.6 Message Conversion................................................................................................ 1078
12.8.6.1 Overview........................................................................................................... 1078
12.8.6.2 MASTER: Telegram Conversion in Transmit Direction (Master → Slave)............... 1080
12.8.6.3 MASTER: Message Conversion in Receive Direction (Master ← Slave) ................. 1098
12.8.6.4 SLAVE: Message Conversion in Transmit Direction (Slave → Master)................... 1112
12.8.6.5 SLAVE: Message Conversion in Receive Direction (Slave ← Master) .................... 1124
12.8.7 Interoperability Modbus RTU....................................................................................1135
12.8.7.1 Interoperability Modbus RTU Master................................................................... 1135
12.8.7.2 Interoperability Modbus RTU Slave..................................................................... 1143
12.8.8 Modbus data formats...............................................................................................1151
12.9 Modbus TCP..................................................................................................................1166
12.9.1 Introduction............................................................................................................ 1166
12.9.2 Functions................................................................................................................ 1167
12.9.4 Communication.......................................................................................................1174
12.9.5 Communication according to Modbus TCP............................................................... 1176

DC8-037-2, Edition 11.2020
Table of Contents

12.9.6.1 Overview........................................................................................................... 1188
12.9.6.2 MASTER: Telegram Conversion in Transmit Direction (Master → Slave)............... 1190
12.9.6.3 MASTER: Message Conversion in Receive Direction (Master ← Slave) ................. 1206
12.9.6.4 SLAVE: Message Conversion in Transmit Direction (Slave → Master)................... 1218
12.9.6.5 SLAVE: Message Conversion in Receive Direction (Slave ← Master) .................... 1231
12.9.7 Interoperability Modbus TCP.................................................................................... 1242
12.9.7.1 Interoperability Modbus TCP Master “Client“....................................................... 1242
12.9.7.2 Interoperability Modbus TCP Slave “Server“......................................................... 1248
12.9.8 Modbus data formats...............................................................................................1254
12.9.9 Web Server.............................................................................................................. 1269
12.9.9.1 Overview........................................................................................................... 1271
12.9.9.2 Connections.......................................................................................................1273
12.9.9.3 Routing Transmit................................................................................................1273
12.9.9.4 Routing Receive................................................................................................. 1277
12.9.9.5 Developer Information – Dataflow Test...............................................................1280
12.9.9.6 Developer Information – Diagnosis (IDR)............................................................ 1283
12.9.9.7 Developer Information – Diagnosis (IDE)............................................................ 1285
12.10 DNP3............................................................................................................................ 1288
12.10.1 Introduction............................................................................................................ 1288
12.10.2 Functions................................................................................................................ 1290
12.10.4 Communication.......................................................................................................1292
12.10.5 Communication according to DNP3..........................................................................1294
12.10.6 Parameters and Properties....................................................................................... 1299
12.10.6.1 Parameter and Functions DNP3 Slave serial.........................................................1299
12.10.6.2 Parameter and Functions DNP3 Slave TCP/IP....................................................... 1310
12.10.7.1 Overview........................................................................................................... 1316
12.10.7.2 Message Conversion in Transmit Direction (Slave → Master)...............................1318
12.10.7.3 Message Conversion in Receive Direction (Slave ← Master).................................1320
12.10.8 Interoperabilität (DNP3 Device Profile Document).................................................... 1323
12.10.9 Web Server.............................................................................................................. 1388
12.10.9.1 Web Server........................................................................................................ 1389
12.10.9.2 Overview........................................................................................................... 1389
12.10.9.3 Connections.......................................................................................................1390
12.10.9.5 Routing Receive................................................................................................. 1393
12.10.9.6 Developer Information - Freespace..................................................................... 1395
12.11 SINAUT ST1...................................................................................................................1400
12.11.1 Introduction............................................................................................................ 1400
12.11.2 Functions................................................................................................................ 1400
12.11.3 Operating Modes.....................................................................................................1401
12.11.4 Communication.......................................................................................................1401
12.11.5 Protocol Description................................................................................................ 1402
12.11.5.1 Technical Specifications..................................................................................... 1402
12.11.5.2 PCMBA Modulation Method................................................................................1403
12.11.5.3 Interface Lines Used........................................................................................... 1404
12.11.5.4 Optimized Parameters for Selected Transmission Facilities.................................. 1404
12.11.6 Communication according to SINAUT ST1................................................................ 1408
12.11.6.1 Data Acquisition by Polling (Station Interrogation).............................................. 1408

DC8-037-2, Edition 11.2020
Table of Contents
12.11.6.2 Acknowledgement Procedure.............................................................................1408

12.11.6.3 Failure Monitoring in the Substation...................................................................1408
12.11.6.4 Station Initialization........................................................................................... 1408
12.11.6.5 Acquisition of Events (Transferring Data Ready for Sending)............................... 1408
12.11.6.6 General Interrogation (Substation Interrogation)................................................ 1408
12.11.6.7 Time Synchronization.........................................................................................1409
12.11.6.8 Command Transmission..................................................................................... 1409
12.11.6.9 Transmission of Integrated Totals....................................................................... 1409
12.11.7 Message Description................................................................................................1409
12.11.7.1 Message Structure............................................................................................. 1409
12.11.7.2 SINAUT ST1 Function Fields................................................................................ 1413
12.11.9 Message Conversion In Transmit Direction (SICAM A8000 → ST1)............................ 1418
12.11.9.1 Binary information............................................................................................. 1418
12.11.9.2 Measured Values (Analog Values).......................................................................1421
12.11.9.3 Integrated Totals................................................................................................ 1427
12.11.10 Message Conversion In Receive Direction (SICAM A8000 ← ST1).............................. 1430
12.11.10.1 Commands........................................................................................................ 1430
12.11.10.2 Setpoint Values.................................................................................................. 1432
12.11.11 Organizational Messages (System Messages)........................................................... 1436
12.12 Telegyr TG800.............................................................................................................. 1440
12.12.1 Introduction............................................................................................................ 1440
12.12.2 Functions................................................................................................................ 1441
12.12.3 Operating Modes.....................................................................................................1442
12.12.4 Communication.......................................................................................................1442
12.12.5.1 Technical Data................................................................................................... 1443
12.12.5.4 Transmission protocol and message formats.......................................................1446
12.12.5.5 Length, Address and Function Fields...................................................................1450
12.12.5.6 Addressing of the Information............................................................................ 1455
12.12.6 Communication according to Telegyr TG800............................................................ 1461
12.12.6.1 General..............................................................................................................1461
12.12.6.2 Startup Procedure of TG800 Communication...................................................... 1462
12.12.6.3 Process Image.................................................................................................... 1462
12.12.6.4 Data Transmission Procedure and Preparation.................................................... 1463
12.12.6.5 Multi-Hierarchical Configuration.........................................................................1464
12.12.6.6 Failure Concept.................................................................................................. 1464
12.12.6.7 General..............................................................................................................1467
12.12.6.8 General Interrogation.........................................................................................1468
12.12.6.10 Counter Value (CV) Requests in TG800............................................................... 1470
12.12.6.11 Handling of Process Data with Time Tag............................................................. 1471
12.12.6.12 Measured Values in Monitoring Direction........................................................... 1472
12.12.6.13 Setpoint values.................................................................................................. 1474
12.12.6.14 Measured Values in Command Direction.............................................................1476
12.12.6.15 TELEGYR 800 Radio Spontaneous Mode..............................................................1479
12.12.7 Message Conversion In Transmit Direction (SICAM A8000 → TG800)........................1486
12.12.7.1 Indications (Single/Double-Point Information).....................................................1486
12.12.7.2 Measured Values................................................................................................1491
12.12.7.3 Counter Values, Requested and Archived............................................................ 1495

DC8-037-2, Edition 11.2020
Table of Contents
12.12.7.4 Own Station Number (and GI Request)............................................................... 1500

12.12.8 Message Conversion In Receive Direction (SICAM A8000 ← TG800)......................... 1500
12.12.8.1 Pulse and Permanent Commands....................................................................... 1501
12.12.8.2 Setpoint.............................................................................................................1504
12.12.8.3 Time for Synchronization................................................................................... 1508
12.12.8.4 GI-Instruction..................................................................................................... 1508
12.12.8.5 Counter Value Request (Counter Interrogation).................................................. 1509
12.12.8.6 GI-Anweisung Systemmeldungsblock................................................................. 1509
12.12.8.7 Acknowledgement System Indication Block........................................................ 1510
12.12.8.8 Instruction: Send Own Station Number...............................................................1511
12.12.8.9 Indications in Command Direction...................................................................... 1511
12.12.8.10 Measured Values in Command Direction.............................................................1515
12.12.8.11 PBN Command................................................................................................... 1518
12.12.9 System Indications and Collective System Indications............................................... 1521
12.12.10 Interoperability Telegyr TG800 Master..................................................................... 1523
12.12.10.1 Network Configurations..................................................................................... 1523
12.12.10.2 Physical Layer.....................................................................................................1524
12.12.10.3 Link Layer.......................................................................................................... 1524
12.12.10.4 Application Layer............................................................................................... 1525
12.12.11 Interoperability Telegyr TG800 Slave........................................................................ 1527
12.12.11.1 Network Configurations..................................................................................... 1527
12.12.11.2 Physical Layer.....................................................................................................1527
12.12.11.3 Link Layer.......................................................................................................... 1527
12.12.11.4 Application Layer............................................................................................... 1528
12.13 ASCII SMS..................................................................................................................... 1531
12.13.1 Introduction............................................................................................................ 1531
12.13.2 Features and Functions............................................................................................1531
12.13.3 Operating Modes.....................................................................................................1531
12.13.4 Communication.......................................................................................................1531
12.13.5.1 Overview........................................................................................................... 1532
12.13.5.2 Technical Data................................................................................................... 1533
12.13.5.3 Restrictions........................................................................................................ 1534
12.13.5.4 SMS Alert........................................................................................................... 1534
12.13.5.5 Printer Logging (ASCII)....................................................................................... 1551
12.13.6 Character Sets......................................................................................................... 1560
12.13.6.1 Codepage: Windows 1252 (= Latin 1)................................................................. 1560
12.13.6.2 Codepage: Multilingual...................................................................................... 1561
12.13.6.3 Codepage: Norway.............................................................................................1562
12.13.7 Printer supported for logging................................................................................... 1562
12.14 IEC 62056-21 (Meter Protocol)...................................................................................... 1566
12.14.1 Introduction............................................................................................................ 1566
12.14.2 Functions................................................................................................................ 1566
12.14.3 Operating Modes.....................................................................................................1568
12.14.4 Communication.......................................................................................................1568
12.15 SAT SK 1703................................................................................................................. 1570
12.15.1 Introduction............................................................................................................ 1570
12.15.2 Functions................................................................................................................ 1570
12.15.3 Operating Modes.....................................................................................................1571
12.15.4 Communication.......................................................................................................1571
12.15.5.1 Technical Specifications..................................................................................... 1572

DC8-037-2, Edition 11.2020
Table of Contents

12.15.5.4 Message Structure for SK 1703 Multi-point Traffic.............................................. 1575
12.15.5.5 Message Structure – Radio Relay Mode (IEC 60870-5-2)......................................1591
12.15.6 Communication according to SAT SK 1703...............................................................1593
12.15.6.1 Structure of Message Data in SAT Standard Format.............................................1593
12.15.6.2 Acknowledgement Procedure.............................................................................1597
12.15.6.3 Acknowledgment Method – Wireless Relay Mode (IEC 60870-5-2)...................... 1597
12.15.6.4 Failure Monitoring in the Remote Terminal Unit..................................................1598
12.15.6.5 Acquisition of Events..........................................................................................1598
12.15.6.6 General Interrogation, Substation Interrogation..................................................1598
12.15.6.8 Command Messages Selective to a Substation.................................................... 1603
12.15.6.9 Counter Interrogation Message.......................................................................... 1603
12.15.6.10 Acquisition of Transmission Time........................................................................1604
12.15.6.11 Transmission Facilities “Modems”....................................................................... 1604
12.15.6.12 General..............................................................................................................1608
12.15.6.13 Error messages.................................................................................................. 1609
12.15.6.14 Component X Failure......................................................................................... 1612
12.15.6.15 Measured Values, Setpoint Values...................................................................... 1613
12.15.7 Message Conversion In Transmit Direction (SICAM A8000 → SAT SK 1703).............. 1616
12.15.7.1 Commands........................................................................................................ 1617
12.15.7.2 Binary Information, Values (Measured Values, Integrated Totals)........................ 1618
12.15.7.3 Two Data Streams (NRT + RT) in Transmit Direction.............................................1619
12.15.8 Message Conversion In Receive Direction (SICAM A8000 ← SAT SK 1703)................ 1619
12.15.8.1 Commands........................................................................................................ 1620
12.15.8.2 Binary Information, Measured Values................................................................. 1620
12.15.9 Message Format Conversion SAT SK 1703 ⇔ IEC 60870-5-101/104.......................... 1622
12.16 ABB RP570/571............................................................................................................. 1632
12.16.1 Short Description.....................................................................................................1632
12.16.2 Functions................................................................................................................ 1632
12.16.3 Operating Modes.....................................................................................................1632
12.16.4 Communication.......................................................................................................1633
12.16.5.1 Technical Data................................................................................................... 1634
12.16.5.2 Transmission protocol........................................................................................ 1635
12.16.5.3 Length-, Address- and Function Field.................................................................. 1638
12.16.5.6 Traffic Management...........................................................................................1645
12.16.6 Communication according to ABB RP570/571...........................................................1646
12.16.6.1 Process Image.................................................................................................... 1646
12.16.6.2 Data Transmission Procedure and Preparation.................................................... 1646
12.16.6.3 General Interrogation.........................................................................................1651
12.16.6.4 QOC Preadjustment Commands......................................................................... 1652
12.16.6.5 Terminal Status Message (TSTA)......................................................................... 1653
12.16.6.6 Terminal Event Message (TEV)............................................................................1654
12.16.6.7 Activation of the Substation............................................................................... 1654
12.16.6.8 Conversion of Measured Values..........................................................................1655
12.16.7 Message Conversion In Transmit Direction (SICAM A8000 → RP570/571)................. 1657
12.16.7.1 Response........................................................................................................... 1659
12.16.7.2 Process Information........................................................................................... 1665
12.16.7.3 System messages............................................................................................... 1684
12.16.8 Message Conversion In Receive Direction (SICAM A8000 ← RP570/571)................... 1688
12.16.8.1 Data Request Messages...................................................................................... 1690

DC8-037-2, Edition 11.2020
Table of Contents
12.16.8.2 System commands............................................................................................. 1691

12.16.8.3 Process information........................................................................................... 1699
12.17 Benning MCU................................................................................................................1710
12.17.1 Introduction............................................................................................................ 1710
12.17.2 Functions................................................................................................................ 1712
12.17.3 Operating Modes.....................................................................................................1715
12.17.4 Communication.......................................................................................................1715
12.17.5.1 Address Field (Substation or Device Address)...................................................... 1716
12.17.6 Communication according to Benning MCU............................................................. 1719
12.17.6.1 Data Acquisition by querying.............................................................................. 1719
12.17.6.2 General interrogation, Outstation interrogation..................................................1720
12.17.6.3 Time synchronization......................................................................................... 1720
12.17.6.4 Command Transmission..................................................................................... 1721
12.17.6.5 Count Value Transmission.................................................................................. 1722
12.17.7 Function for the Support of Redundant Communication Routes................................1722
12.17.8 Message Formats.....................................................................................................1722
12.17.8.1 Command Message............................................................................................1722
12.17.8.2 Acknowledgment Message.................................................................................1724
12.17.8.3 Data Message “Protocol”.....................................................................................1724
12.17.8.4 Address Field (Substation or Device Address)...................................................... 1729
12.17.8.5 Message Protection............................................................................................ 1729
12.17.9.1 Overview........................................................................................................... 1730
12.17.9.2 Message Conversion in Transmit Direction (Central Station → Substation).......... 1731
12.17.9.3 Message Conversion in Receive Direction (Central Station ← Substation)............ 1736
12.17.11 ASCII Table (MS-DOS Code Page 437).......................................................................1744
12.18 AGP (Power Distributor Branch Specific Test Equipment)................................................1746
12.18.1 Introduction............................................................................................................ 1746
12.18.2 Functions................................................................................................................ 1746
12.18.4 Communication.......................................................................................................1748
12.18.5 Communication according to AGP............................................................................1748
12.18.5.1 Data transmission from/to AGP........................................................................... 1753
12.18.5.2 Function for the Support of Redundant Communication Routes.......................... 1753
12.18.6 Parameter and Setting............................................................................................. 1754
12.18.7.1 Message Conversion in Transmit Direction (Master → Slave)...............................1758
12.18.7.2 Message Conversion in Receive Direction (Master ← Slave).................................1763
12.18.8 Web Server.............................................................................................................. 1771
12.18.8.1 Web Server........................................................................................................ 1772
12.18.8.2 Overview........................................................................................................... 1773
12.18.8.3 Connections.......................................................................................................1773
12.18.8.5 Routing Receive................................................................................................. 1777
12.18.8.6 Developer Information – Freespace.................................................................... 1781

DC8-037-2, Edition 11.2020
Table of Contents
12.18.8.9 Developer Information – Diagnosis (IDH)............................................................ 1784

12.18.8.10 Developer Information – Diagnosis.....................................................................1785
12.18.8.11 Developer Information – Diagnosis (IDE)............................................................ 1788
12.19 IOT............................................................................................................................... 1792
12.19.1 Introduction............................................................................................................ 1792
12.19.2 Functions................................................................................................................ 1793
12.19.4 Communication.......................................................................................................1794
12.19.5 Parameters and Properties....................................................................................... 1795
12.19.5.1 Parameter and Properties (OPUPT0)....................................................................1795
12.19.5.2 Parameter and Properties (OPUPT1)....................................................................1800
12.19.6.1 Message Conversion in Transmit Direction (SICAM A8000 → IOT)....................... 1802
12.19.7 Web Server.............................................................................................................. 1807
12.19.7.1 Web Server......................................................................................................... 1807
12.19.7.2 Overview........................................................................................................... 1808
12.19.7.3 Connections.......................................................................................................1809
12.19.7.5 List(s)................................................................................................................ 1811
12.19.7.6 File List(s).......................................................................................................... 1812
12.19.7.7 Asset Information...............................................................................................1813
12.19.7.8 Developer Information - Freespace..................................................................... 1814
12.19.7.9 Developer Information - Duration....................................................................... 1815
12.19.7.10 Developer Information - Connection Log............................................................ 1815
12.20 VLAN............................................................................................................................ 1820
12.20.1 Introduction............................................................................................................ 1820
12.20.2 Sample Applications................................................................................................ 1820
12.20.3 Configuration.......................................................................................................... 1821
12.21 SNMP............................................................................................................................1823
12.21.1 Introduction............................................................................................................ 1823
12.21.2 Functions................................................................................................................ 1823
12.21.3 Configuration.......................................................................................................... 1825
12.21.4 SNMP MIBs – Management Information Base........................................................... 1828
12.21.4.1 Download of the MIB-Files..................................................................................1828
12.21.4.2 Import the MIB files in the MIB Browser.............................................................. 1828
12.21.4.3 MIB: MIB-2 (RFC1213)........................................................................................ 1828
12.21.4.4 sicamRTUs......................................................................................................... 1829
12.21.4.5 MIB: dgpiMIB..................................................................................................... 1830
12.21.5 SNMP Variables....................................................................................................... 1833
12.21.5.1 Introduction.......................................................................................................1833
12.21.5.2 SNMP Variables for MIB: sicamRTUs.................................................................... 1833
12.21.5.3 SNMP variables for MIB: dgpiMIB........................................................................ 1839
A Ordering Information............................................................................................................................. 1841

A.1 Basic Units.................................................................................................................... 1842
A.2 Power Supply Modules.................................................................................................. 1843
A.3 SICAM I/O Modules........................................................................................................1844
A.4 SICAM TM I/O Modules.................................................................................................. 1847
A.5 Interface Modules......................................................................................................... 1851
A.6 Transmission Facilities...................................................................................................1852

DC8-037-2, Edition 11.2020
Table of Contents
A.7 Recommended Upstream Power Supply Devices............................................................ 1855

A.8 Cables and Plugs........................................................................................................... 1856
A.9 Memory Cards...............................................................................................................1859
A.10 IE RJ45 Port Lock........................................................................................................... 1860
A.11 Engineering Tools......................................................................................................... 1861
B Examples of Instruction Lists (IL)............................................................................................................1863

B.1 Transfer an Input to a Signalling Output and to a Command Output...............................1864
B.2 Combine 2 Inputs with AND.......................................................................................... 1865
B.3 Linear Adaptation with Value Selection..........................................................................1866
B.4 Operating Hours Counter.............................................................................................. 1867
B.5 Bounce Suppression...................................................................................................... 1869
B.6 Setpoint Command....................................................................................................... 1871
B.7 Speed Comparison........................................................................................................ 1872
C Error Handling........................................................................................................................................ 1875

C.1 Errors with the Engineering via SICAM WEB................................................................... 1876
D Setting Up a Dial-Up Connection............................................................................................................ 1879

D.1 Settings in Microsoft Windows 8....................................................................................1880
D.2 Settings in Microsoft Windows 7....................................................................................1890
D.3 Settings in Microsoft Windows Vista.............................................................................. 1899
D.4 Restore the Settings for Using the Internet.................................................................... 1908
E Use Cases................................................................................................................................................ 1909

E.1 Usage as Telecontrol Substation.................................................................................... 1910
E.2 Usage as Telecontrol Substation with Node Function (Protocol Converter)..................... 1911
E.3 Usage as Telecontrol Substation with Integrated Switch for External System Connection1912
E.4 Usage as Telecontrol Substation with Integrated Switch for SICAM TOOLBOX II
Connection................................................................................................................... 1913
E.5 Usage with Static Routes............................................................................................... 1914
E.6 Usage with IPSec VPN....................................................................................................1917
E.7 Usage of the Internal GPRS Modem (CP-8022)............................................................... 1921

DC8-037-2, Edition 11.2020
1 General Information
1.1 CP-8000, CP-8021, CP-8022 Base Units 34

1.2 Performance Properties 41
1.3 System Architecture 42

DC8-037-2, Edition 11.2020
General Information
1.1 CP-8000, CP-8021, CP-8022 Base Units
Figure 1-1 CP-8000 Figure 1-2 CP-8021 Figure 1-3 CP-8022
1.1.1 High Performing
With CP-8000/CP-802x you can implement different applications, depending on the requirements: telecontrol
applications and automation solutions. Evidently all applications can be combined with each other.
CP-8000/CP-802x can be deployed universally and is suitable for electrical distribution substations, gas distri-
bution substations, hydropower plants, pipelines, railway power supplies, as well as in object protection or for
alarm signaling.
Additional advantages at a glance:
• Mechanical design for DIN-rail mounting and simple process interfacing
• On-site operation via display and function keys (CP-8000 only)
• Versatile communication, integrated node functionality
• Expandable with external I/O modules
• Configuration, diagnostics and tests via the engineering system SICAM TOOLBOX II, alternatively via a
Web server
• User-friendly through remote maintenance, remote diagnosis and remote parameterization
• Interlocking and local control in compliance with IEC 61131-3 thanks to smart user programs
• Data storage on SD card; plug-and-play for start-up and service
• Use under varied ambient conditions thanks to wide temperature range and extremely high degree of
EMC
NOTE
i Consider the performance features of the system and of its components in chapter 5 System Components
and Technical Data.

DC8-037-2, Edition 11.2020
General Information
1.1.2 Different Fields of Application
Due to their node functionality, CP-8000/CP-802x can be used in a variety of ways:
• Classical small telecontrol unit
• Remote terminal unit with various ways of communication to the central station
• Automation and supervision of local network stations
• Transformer control
• Energy distribution and transmission
• Traction power supply
• Communication gateway
In principle, all functionalities required for this are available. The actual application is defined through the
corresponding configuration and parameterization.
Main Field of Application: Intelligent Local Network Control

With this application, CP-8000/CP-802x enables a three-stage intelligence:
• Supervision
– High availability
– Rapid fault localization
• Telecontrol
– Minimizing downtime
• Load flow control

– Management of distributed infeeds
– Minimizing losses

DC8-037-2, Edition 11.2020
General Information
[dw_A8000_application_overview, 1, en_US]
Figure 1-4 Intelligent Local Network Control
1.1.3 Mechanical Design
The mechanical design is focused on achieving highest ease in handling. As a result, CP-8000/CP-802x is desig-
nated for mounting on a DIN rail (TS35).
[ph_CP-8000_802x_din_rail, 2, --_--]
Figure 1-5 CP-8000/CP-802x – Mounting on DIN Rail
The communication interfaces are designed according to the RJ45 standard or as removable terminals.
Process signals can be connected via removable screw terminals directly to CP-8000 or to additionally
equipped I/O modules. This efficient and simple way of interfacing permits a direct sensor/actuator wiring
without requiring the use of intermediate terminals. As a result of the fact that process signals can be acquired
very close to their point of origin, a wide cabling can be reduced to a minimum.

DC8-037-2, Edition 11.2020
General Information
When the system is exchanged, no connections need to be detached, since the screw terminals carry the
wiring. This makes assembly significantly easier.
Upon delivery, the screw terminals are plugged on the device.
1.1.4 Local Operation (CP-8000)
In addition to status LEDs, CP-8000 provides function keys and a display on the front of the housing.
[ph_CP-8000_front_menu, 1, --_--]
Figure 1-6 CP-8000 Local Operation
1.1.5 Versatile Communication, Integrated Node Functionality
There are several possible means of communicating with the control center:
• LAN/WAN
In the event of communication via LAN/WAN networks, transmission takes place as per the standards
IEC 60870-5-104 or IEC 61850 or DNP(i) or MODBUS – based on Ethernet TCP/IP.
• Multi-point traffic
You can connect external communication modules via the RS-232 or via the RS-485 interface for trans-
mission in multi-point traffic. The standard protocols can be selected freely, for example
IEC 60870-5-101/-103, DNP 3.0, MODBUS RTU. Additional protocols are available on request.
• Dial-Up Traffic
Various connection-oriented transmission media are also supported as standard via dial-up traffic (PSTN,
ISDN, GSM, TETRA).
Further local devices can be connected in a very simple way via the additional communication interfaces in
order to connect them to an entire unit.

DC8-037-2, Edition 11.2020
General Information
[dw_A8000_networked_plant, 1, en_US]
Figure 1-7 Networked Plant

DC8-037-2, Edition 11.2020
General Information
1.1.6 Expandibility
If the scope of signals of a substation should ever be insufficient, additional I/O Modules can be equipped or
further CP-8000/CP-802x can be connected via the communication interfaces. Freely programmable user
programs for local control or regulating functions round out the versatile attributes of the system.
[dw_CP-8000_system_design, 1, en_US]
Figure 1-8 CP-8000 + I/O Modules

DC8-037-2, Edition 11.2020
General Information
1.1.7 Data Storage on SD Card
With the engineering, all data of a device – such as firmware and parameters – are stored centrally on an
exchangeable SD card in a non-volatile manner.
Upon startup of the device, all required data is checked and is - in case of differences to the device settings
automatically transferred from the SD card. The transfer only occurs in case of valid firmware and parameter
signatures. Thus, when the device is exchanged with the same type, no subsequent loading process, this
means, no engineering tool, will be required. The configuration is transferred directly to the replacement
device (plug and play).
1.1.8 Compatibility
CP-8000/CP-802x is in the range of IEC 60870-5-101/103/104, when using standard protocols, compatible
with the existing SICAM RTUs system family (SICAM AK 3, SICAM BC as well as the previous systems SICAM AK,
SICAM TM, SICAM EMIC, SICAM MIC).
CP-8000/CP-802x is, when using external I/Os, compatible with the hitherto existing SICAM TM I/O Modules.

DC8-037-2, Edition 11.2020
General Information
1.2 Performance Properties
1.2 Performance Properties

General Features CP-8000 CP-8021 CP-8022
Maintenance-free, small compact device for mounting on DIN rail ✓ ✓ ✓
Operation via 4 function keys and display ✓ – –
Internal digital inputs for binary information 12 – –
Internal digital outputs for commands and binary information 8 – –
Expandable by external SICAM I/O modules 6 8 8
Expandable by external SICAM TM I/O modules 6 8 8
Combined automation and telecontrol function ✓ ✓ ✓
Freely programmable application programs according to ✓ ✓ ✓
IEC 61131-3
Communication
Ethernet interfaces 10/100BASE-TX with parameter-settable 21 21 21
protocols according to IEC 60870-5-104, IEC 61850 Ed. 2 Client/
Server, DNP3 TCP/IP, MODBUS TCP/IP
Serial interfaces with parameter-settable protocols according to 22 22 323
IEC 60870-5-101/103/104, DNP3, MODBUS and others
Integrated GPRS modem – – ✓
Engineering, diagnosis and test via SICAM TOOLBOX II ✓ ✓ ✓
• SICAM TOOLBOX II connection via LAN/WAN (“remote

connection”)
• Connection via proprietary TCP/IP-based protocol (one SICAM
TOOLBOX II session can be operated at the same time)
Integrated Web server for engineering, diagnosis, and test via ✓ ✓ ✓
Web browser (SICAM WEB application)
• Access to the Web server with standard Web browser via

http(s)
Engineering via SICAM Device Manager ✓ ✓ ✓
Optional autoconfiguration via DHCP service ✓ ✓ ✓
Optional dynamic IP settings via DHCP server ✓ ✓ ✓
Integrated SNMP protocol ✓ ✓ ✓
Time synchronization via NTP server ✓ ✓ ✓
Simplified maintenance thanks to data storage on SD card ✓ ✓ ✓
Optional authentication via RADIUS server ✓ ✓ ✓
Secure password storage ✓ ✓ ✓
Security ✓ ✓ ✓
• BDEW White Paper conformity and integrated crypto chip

• Configurable SD card mode
• IPSec
• Security logging
• Role-based access control
Process signal status display via display ✓ – –
Function and error indication via LEDs ✓ ✓ ✓
1 Common or separate IP address configurable (2 MAC addresses reserved, see name plate of the device)
2 1x RS-232 and 1x RS-485
3 1x selectable RS-232 or RS-485

DC8-037-2, Edition 11.2020
General Information
1.3 System Architecture
1.3.1 CP-8000
The basic system of CP-8000 consists of the following components:
• A Master Module with

– An internal Power Supply Module
– 2 internal I/O Modules
In dependence of the requirements the basic system can be extended:
• Up to 4 optional protocol elements for the communication with higher-level automation units or a
control center system (can be loaded on the Master Module)
• Up to 6 external I/O Modules for the communication with the field process
• A LED Module for the visualization of the process data of the internal I/O Modules and of the external
SICAM I/O Modules
[dw_CP-8000_system_architecture, 1, en_US]
Figure 1-11 CP-8000 System Architecture
1.3.2 CP-8021 and CP-8022
The basic system of CP-8021 and CP-8022 consists each of the following components:
• A Master Module
• An external Power Supply Module

In dependence of the requirements the basic system can be extended:
• A second Power Supply Module (optional for redundancy purpose)
• Up to 4 optional protocol elements for the communication with higher-level automation units or a
control center system (can be loaded on the Master Module)

DC8-037-2, Edition 11.2020
General Information
• Up to 8 external I/O Modules for the communication with the field process
• A LED Module for the visualization of the process data of the external SICAM I/O Modules
[dw_CP-802x_system_architecture, 1, en_US]
Figure 1-12 CP-802x System Architecture

DC8-037-2, Edition 11.2020
DC8-037-2, Edition 11.2020
2 System Overview
2.1 Modules 46
2.2 Communication 55
2.3 Firmware Structure and Data Flow 61
2.4 Engineering 62

DC8-037-2, Edition 11.2020
System Overview
2.1 Modules
2.1 Modules
2.1.1 Power Supply
2.1.1.1 CP-8000
With CP-8000 the supply is carried out via an internal power supply module. This provides the operating
voltage for the internal modules (Master Module and I/O Modules) and for selected transmission facilities with
multi-point traffic and dial-up traffic, as well as for the external I/O Modules.
Features
• Input voltage DC 24 to 60 V
• System output voltages

– DC 5.2/10 V for internal supply and for external modem
– DC 5.2 V for external I/O Modules
– Wiring block for contact wetting
• Monitoring of the output voltage
• Environmental conditions with enhanced electromagnetic compatibility
• Withdrawable screw terminals
• Function display via LED
2.1.1.2 CP-8021 and CP-8022

With CP-8021 and CP-8022, the power supply is carried out by the external PS-862x and PS-864x power supply
modules. These provide the operating voltage for the master module and for selected transmission facilities
with multi-point traffic and dial-up traffic, as well as for the external I/O modules.
[dw_sicam_ps_module_types, 2, --_--]
Figure 2-1 Power Supply Modules
Features PS-86xx
• Different input voltages as according to the following table

– PS-862x: DC voltage input
– PS-864x: AC or DC voltage input

DC8-037-2, Edition 11.2020
System Overview
2.1 Modules
• Output voltages for system-internal use

– DC 5 V/28 V
• Output voltages for external use (only PS-8642)

– DC 24 V
• Monitoring of the output voltages
• Monitoring of the input voltage
• 2 redundant power supply modules possible (not for power enhancement)
• Environmental conditions with enhanced electromagnetic compatibility
• Withdrawable screw terminals
• Function display via LED
Product Overview
Type Designation
PS-8620 Power supply module DC 24 to 60 V, 12 W
PS-8622 DC power supply module, 110 to 220 V, 12 W
PS-8640 DC power supply module, 24 to 60 V, 45 W
PS-8642 Power supply module DC or AC 100 to 240 V, 45 W
2.1.2 Master Module
The Master Module is the central processing unit. Its functionality is provided by means of a loadable and
parameter-settable firmware.
The Master Module integrates the function packages for Telecontrol (spontaneous processing and communi-
cation) and Automation (periodical processing and peripheral functions) into one common device.
Additionally, it serves as centrally coordinating element for all System Services.
Features
• Data node functionality
• Organization of the data flow from and to the communication interfaces

– Ethernet (TCP/IP) for LAN/WAN connections according to IEC 60870-5-104
– RS-232 for multi-point, point-to-point or dial-up traffic according to IEC 60870-5-101 with supply for
an external transmission facility
– RS-485 for multi-point traffic
• Main focus in telecontrol

– Parameter-settable telecontrol function
– Parameter-settable communication protocols
– Time management and time synchronization via SNTP (Simple Network Time Protocol)
– Up to 4 different NTP servers (redundancy)
– Cyclical, can be set in a seconds grid, self-adapting
– Monitoring and simulation of process signals

DC8-037-2, Edition 11.2020
System Overview
2.1 Modules
• Automation
– Freely programmable open-/closed-loop control function according to IEC 61131-3
– Deterministic behavior of the open-/closed-loop control function with guaranteed reaction times
and thereby time-consistent
– Test and diagnosis of the open-/closed-loop control function
• Autonomous behavior (for instance in the case of communication failure)
• Logging and display of events and alarms
• Decentralized archive (DEAR) for the avoidance of data loss during communication fault
• Loadable firmware
• Storage of application data and firmware on SD card
Product Overview
Type Designation
CP-8000 Master Module with I/O
CP-8021 Master Module
CP-8022 Master Module with GPRS
CPC80 Firmware Central Processing and Communication
SWEB00 Firmware SICAM WEB
Sicam_first_startup Initialization tool for the detection of devices and IP address allocation
SD card Memory card for parameters and firmware
NOTE
i In a system of the SICAM A8000 series only 1 Master Module may be used.
The Master Modules in Comparison
CP-8000 CP-8021 CP-8022

Mechanics
Installation Mounting on 35 mm DIN rail
Dimension (H x W x D) 124 x 128 x 123 mm 132 x 30 x 142 mm 132 x 30 x 142 mm
Weight Approx. 800 g Approx. 210 g Approx. 260 g
Connections
Peripheral signals and power Removeable screw – –
supply terminals
Communication via 2x RJ45 socket 2x RJ45 socket 2x RJ45 socket
Ethernet/LAN connector 8-pole, for connector 8-pole, for connector 8-pole, for
connecting cat.5 cable connecting cat.5 cable connecting cat.5 cable
(X1, X4) (X1, X4) (X1, X4)

DC8-037-2, Edition 11.2020
System Overview
2.1 Modules
CP-8000 CP-8021 CP-8022

Communication via RS-232 D-SUB 9-pole, male, with 1x RJ45 socket 8-pole, 1x RJ45 socket 8-pole,
supply output for with supply output for with supply output for
external transmission external transmission external transmission
facility (X2) facility (X2) facility (X2)
1x removable push-in
terminal 8-pole (X6) 4
Communication via RS-485 1x removable screw 1x removable push-in 2x removable push-in
(RS-422) terminal 6-pole (X3) terminal 8-pole (X3) terminal 8-pole (X3, X6)
4
Peripheral bus 5-pole connector for 18-pole connector for 18-pole connector for
SICAM I/O coupling bus connector bus connector
module or SICAM TM I/O
coupling module
Communication via GPRS 5 5 SMA connector (X7)
2.1.3 I/O Master Modul
The virtual I/O Master Module serves for the acquisition or output of process signals and performs the process-
compliant adaptation, monitoring and processing of the process signals at each point of entrance or exit of
the system.
Its functionality is provided by means of the
• loadable and parameter-settable firmware (example: smoothing of measured values, time tagging)
• hardware (example: filter, ADC, 1-out-of-n check, DAC)

Features
• Support of I/O Modules

– CP-8000: 2 internal and up to 6 external I/O Modules (maximal 116 I/Os)
– CP-802x: up to 8 external I/O Modules (maximal 128 I/Os)
• Acquisition and preprocessing of process data according to IEC 60870-5-101/104 with and without time
tag
– Transmission of process information to the telecontrol function (for further distribution) and to the
open-/closed-loop control function (for further processing)
– Single-point and double-point information items
– Count pulses
– Measured values
– Transmission of system information (example: diagnosis data)
• Postprocessing and output of process data according to IEC 60870-5-101/104

– Reception of process information from the telecontrol function and from the open-/closed-loop
control function
– Single-point information items
– Single-point and double-point commands
– Setpoint commands
– Reception of system information (example: parameters)
4 interface can be used optionally for RS-232 or RS-485 communication

5 ext. GPRS modem/router with Ethernet/LAN interface

DC8-037-2, Edition 11.2020
System Overview
2.1 Modules
• Test functions for process signals
• Secured data exchange with the I/O Modules
• Supervision of the I/O Modules and failure handling
• Status for process signals via display (CP-8000 only)
• Error display via LED
Product Overview
Type Designation
USIO80 Firmware Universal Signal Input and Output for the connection of
SICAM TM I/O Modules
USIO81 Firmware Universal Signal Input and Output for the connection of
SICAM I/O Modules
2.1.4 I/O Modules
The I/O modules support the I/O Master module with the input and output of process signals.
The I/O modules communicate with the Master module via an internal bus. This bus transports data of
different classes:
• Spontaneous data for the function package Telecontrol including communication

– Process information and system information that is transmitted acknowledged between the Master
module and the I/O modules within the acquisition and output grid
• Periodical data for the function package Automation

– Information that is transmitted between the Master module and the I/O modules in the cycle of the
open/closed-loop control function
• I/O process data

– I/O process status and I/O process errors that are transmitted from the SICAM I/O modules to the LED
module
Features
• Acquisition of process signals and preprocessing by means of hardware

– Binary inputs
– Analog inputs (current, voltage, temperature)
• Output of process signals and postprocessing by means of hardware

– Binary outputs
– Analog outputs (current, voltage)
• Visualization of I/O process data using the LED module in a SICAM I/O module row without any additional
tools

DC8-037-2, Edition 11.2020
System Overview
2.1 Modules
Types and Field of Operation
CP-8000 CP-8021 CP-8022

System-internal I/O modules 2 – –
External SICAM I/O modules Max. 66 Max. 8 Max. 8
External SICAM TM I/O modules Max. 67 Max. 88 Max. 88
2.1.4.1 Internal I/O Modules

Internal I/O Modules are available only with CP-8000. They are fixed integrated.
Product Overview
Type Designation
DI-8100 Digital Input 12x DC 24 to 60 V, 1 ms
DO-8203 Digital Output Relais 8x DC 24 to 220 V / AC 230 V
2.1.4.2 External SICAM I/O Modules

The external SICAM I/O Modules can be used with all products of the SICAM A8000 series.
• With CP-8000, up to 6 external SICAM I/O Modules can be used,

thereby the additional coupling module CM-8811 is required.
• With CP-8021 and CP-8022, up to 8 external SICAM I/O Modules can be used.
[dw_sicam_io_module_types, 1, --_--]
Figure 2-2 SICAM I/O Modules (Type Overview), LED Module
Product Overview
Type Designation max. power

DI-8110 Digital Input 2x8 DC 24 V 130 mW
DI-8111 Digital Input 2x8 DC 48/60 V 130 mW
6 Connectable via CM-8811 coupling module


DC8-037-2, Edition 11.2020
System Overview
2.1 Modules
Type Designation max. power

DO-8212 Digital Output Relay 8x DC 24 to 220 V/AC 230 V 800 mW
AI-8310 Analog Input 2x2 Pt100/Pt1000 500 mW
AI-8320 Analog Input 4x ±20 mA/±10 V 180 mW
AI-8510 Analog Input 3x U (240 V), 3x I (LoPo) 800 mW
AI-8511 Analog Input 3x U (LoPo), 3x I (LoPo) 800 mW
AO-8380 Analog Output 4x ±20 mA/±10 V 2200 mW
CM-8811 Coupling Module for SICAM I/O modules (only for CP-8000) -
CM-8812 9 Bus Connector for SICAM I/O Modules -
CM-8820 CT-Adapter 3x I 1 A_5 A/225 mV (only for AI-8510) -
CM-8830 SICAM I/O Module LED Unit 500 mW
2.1.4.3 External SICAM TM I/O Modules

If needed, also external SICAM TM I/O Modules can be used. Thereby, a 2-line arrangement is possible with the
TM I/O Modules extension cable CM-6810.
You will find further information in the manual SICAM RTUs SICAM TM I/O Modules.
• With CP-8000, up to 6 external SICAM TM I/O Modules can be used,

• With CP-8021 and CP-8022, up to 8 external SICAM TM I/O Modules can be used,
[dw_sicam_tm_io_module_types, 1, --_--]
Figure 2-3 SICAM TM I/O Modules (Type Overview)
Product Overview
Type Designation Max. power

DI-6100 Digital Input 2x8 DC 24 to 60 V 170 mW
DI-6101 Digital Input 2x8 DC 110/220 V 170 mW
DI-6102 Digital Input 2x8 DC 24 to 60 V, 1 ms 170 mW
DI-6103 Digital Input 2x8 DC 110/220 V, 1 ms 170 mW
DO-6200 Digital Output Transistor 2x8 DC 24 to 60 V 600 mW
DO-6212 Digital Output Relays 8x DC 24 to 220 V/AC 230 V 800 mW
DO-6220 Checked Command Out Basic Module 560 mW
9 supplied with each I/O Module

DC8-037-2, Edition 11.2020
System Overview
2.1 Modules
Type Designation Max. power

DO-6221 Checked Command Out Basic Module Measurement 1380 mW
DO-6230 Checked Command Output Relay Module 130 mW
AI-6300 Analog Input 2x2 ±20 mA/±10 V 480 mW
AI-6307 Analog Input 2x2 ±2,5 mA/±5 mA/±10 V 480 mW
AI-6308 Analog Input 2x2 1 mA/±2 mA/±10 V 480 mW
AI-6310 Analog Input 2x2 Pt100/Ni100 480 mW
AO-6380 Analog Output 4x ±20 mA/±10 mA/±10 V 1900 mW
TE-6430 Counter Input 2x DC 24 to 60 V (only existing plants) 600 mW
CM-6810 TM I/O Modules Extension Cable -
CM-6811 Coupling Module for SICAM TM I/O Modules (only for CP-8000) -
CM-6812 Coupling Module for SICAM TM I/O Modules (only for CP-802x) -
2.1.4.4 Configuration Rules for I/O Modules

If you use external I/O Modules, pay attention to the following rules.
General
• The total power of the external I/O Modules must not exceed the following values:
– CP-8000: 5 W
– CP-802x: 7 W (PS-862x), 8 W (PS-864x)
(when using the fiberoptical interface CM-0847, available with < 1 W)
• The total power consumption of all modules (including supplied data transmission facility) must not
exceed the power provided by the Power Supply Module
• I/O Modules with a power consumption > 800 mW must be mounted directly to the right of the Power
Supply Module (or directly to the right of CP-8000)
Exception: An LED Module is mounted at the first slot
• When using an LED Module in a SICAM A8000 I/O Module row, the module can be mounted at any posi-
tion to the right side of the Power Supply Module
The LED Module can also be mounted before the I/O module with a power consumption > 800 mW
• The combination of current and voltage on a single AI-8320 (AI-630x) is not possible
• The combination of binary information and pulse commands on a single DO module is not possible,
except with usage of the categories DO_SX and DO_DX (for details refer to manual SICAM RTUs Common
Functions Peripheral Elements According to IEC 60870-5-101/104, chapter Binary Information and
Command Output
Following cases explain the mixing of binary information and pulse commands on a single module
DO-820x or DO-821x (DO-621x):
– Mixing of DO_SX, DO_DX, DO_SC_1.5POL and DO_DC_1.5POL possible
– Mixing of DO_SC_1POL and DO_DC_1POL possible
– Mixing of DO_SC_2POL and DO_DC_2POL possible
– Mixing of DO_SX and/or DO_DX with DO_SC_1POL and/or DO_DC_1POL not possible
• For the current measurement of each AI-8510, a CM-8820 must be mounted; CM-8820 must be always
mounted at the end of an I/O row or at a separate I/O row
Option “Assignment of Return Information to Pulse Command”
• With the parameter-settable assignment the sequence of DI modules and DO modules is arbitrary
• With the fixed assignment respectively after a DI-811x (DI-610x) a DO-821x (DO-62xx) must be equipped

DC8-037-2, Edition 11.2020
System Overview
2.1 Modules
For further details refer to section Standard Command Output, Page 460.
Option “Checked Command Output” (applies for SICAM TM I/O Modules)
• Only 1 Command Output Basic Module may be connected, alternatively

– DO-6220, command output according to IC1
– DO-6221, command output according to RC1
• The command output via DO-6220 or DO-6221 without a DO-6230 is not possible
• Up to 6 Command Output Relay Modules DO-6230 may be connected
• The command output via DO-6230 without a DO-6220 or DO-6221 is not possible
• On a DO-6230 either 1-, or 1.5- or 2-pole impulse commands can be assigned (mixture on the same
module is not permitted)
• Additionally, further DO module types can be used

For further details refer to section Standard Command Output, Page 460.

DC8-037-2, Edition 11.2020
System Overview
2.2 Communication
2.2 Communication
2.2.1 Protocol Elements
A protocol element serves for the exchange of data – and thus for the transmission of messages – via a
communication interface to other automation units or process control systems.
The hardware for the protocol elements has been integrated on the Master module, and their functionality is
provided by means of loadable and parameter-settable firmwares.
Via the communication interfaces the Master module is able to communicate with an arbitrary superior or
subordinate automation unit in multi-point, point-to-point or dial-up traffic (with the aid of an external data
transmission facility), or via LAN/WAN.
Supported Protocols
Table 2-1 Protocols and Interfaces supported by CP-8000/CP-802x
CP-8000, CP-8021 CP-8022

LAN RS-232 RS-485 LAN RS-232 RS-485 GPRS
Protocol Firmware RS-422 RS-422
Integrated standard protocols
http/https TOOLBOX II CPC80 X1, X4 – – X1, X4 – – X7
remote operation
SNMP V3 Agent (Simple CPC80 X1, X4 – – X1, X4 – – X7
Network Management
Protocol)
Syslog Client (System CPC80 X1, X4 – – X1, X4 – – X7
Message Logging)
NTP Client + Server CPC80 X1, X4 – – X1, X4 – – X7
(Network Time Protocol)
SNTP Client + Server CPC80 X1, X4 – – X1, X4 – – X7
(Simple Network Time
Protocol)
RADIUS CPC80 X1, X4 – – X1, X4 – – X7
Equipable standard protocols
IEC 60870-5-101 point-to- BPPT0 – X2 X3 10 – X2, X6 X3, X6 –
point traffic 10
IEC 60870-5-101 multi- UMPMT0 – X2 X3 – X2, X6 X3, X6 –

point traffic master
IEC 60870-5-101 multi- UMPST0 – X2 X3 – X2, X6 X3, X6 –
point traffic slave
IEC 60870-5-101 dial-up DIAST0 – X2 – – X2, X6 – –
traffic slave
IEC 60870-5-103 protec- 103MT0 – X2 X3 – X2, X6 X3, X6 –
tion device interfacing
master
IEC 60870-5-104 Ethernet ET84 X1, X4 – – X1, X4 – – X7
TCP/IP 11
10 in RS-422 mode only

11 GPRS communication possible via X1, X4 and external GPRS modem

DC8-037-2, Edition 11.2020
System Overview
2.2 Communication
CP-8000, CP-8021 CP-8022

LAN RS-232 RS-485 LAN RS-232 RS-485 GPRS
Protocol Firmware RS-422 RS-422
IEC 61850 Ethernet TCP/IP ET83 X1, X4 – – X1, X4 – – –
Ed. 1 (Client, Server,
GOOSE) 12
IEC 61850 Ethernet TCP/IP ET85 X1, X4 – – X1, X4 – – –
Ed. 2 (Client, Server,
GOOSE), Ed. 1 (Client)
DNP3 master DNPMT0 – X2 X3 – X2, X6 X3, X6 –
DNP3 slave DNPST0 – X2 X3 – – X3, X6 –
DNP3 TCP master DNPiT2 X1, X4 – – X1, X4 – – –
DNP3 TCP slave DNPiT1 X1, X4 – – X1, X4 – – –
MODBUS RTU master MODMT2 – X2 X3 – X2, X6 X3, X6 –
MODBUS RTU slave MODST0 – X2 X3 – X2, X6 X3, X6 –
MODBUS TCP master MBCiT0 X1, X4 – – X1, X4 – – –
(Client)
MODBUS TCP slave (Server) MBSiT0 X1, X4 – – X1, X4 – – –
IOT Publisher (MQTT) OPUPT0 X1, X4 – – X1, X4 – – –
IOT IOT publisher (Mind- OPUPT1 X1, X4 – – X1, X4 – – –
sphere)
Equipable project-specific protocols
AGP interfacing master AGPMT0 – X2 X3 – X2, X6 X3, X6 –
Benning MCU ASCII BMCUT0 – X2 X3 10 – X2, X6 X3, X6 –
protocol 10
IEC 62056 21 (IEC 1107) COUMT0 – X2 X3 – X2, X6 X3, X6 –

master
SK 1703 PCMBA slave PCBST0 – X2 X3 – X2, X6 X3, X6 –
ABB RP570/571 slave RP5UT1 – X2 X3 – X2, X6 X3, X6 –
ASCII protocol for SMS SMST0 – X2 – – X2, X6 –
alerting
Siemens SINAUT-ST1 slave ST1ST0 – X2 X3 – X2, X6 X3, X6 –
L&G Telegyr 800 slave TG8ST0 – X2 X3 – X2, X6 X3, X6 –
Additional information on interfacing to third-party systems and further protocols is available on request.
2.2.2 Interfaces
CP-8000/CP-802x provides the following interfaces for a number of communication options:
• 2 Ethernet TCP/IP interfaces LAN/WAN (X1 and X4)

Both Ethernet interfaces have either 1 common IP address or 2 independent IP addresses (2 separate
MAC addresses)
• 1 serial interface according to standard RS-232 (X2)
• 1 serial interface according to standard RS-485 (X3)

CP-8022 additionally provides
• 1 serial interface configurable for standard RS-232 or RS-485 (X6)
• 1 GPRS antenna connection for integrated GPRS modem (X7)
12 only if server Ed.1 is required, in any other case use ET85

DC8-037-2, Edition 11.2020
System Overview
2.2 Communication
All interfaces can be operated simultaneously.
[dw_A8000_communication_interfaces, 1, --_--]
Figure 2-4 CP-8000/CP-8021/CP-8022 Communication Interfaces

DC8-037-2, Edition 11.2020
System Overview
2.2 Communication
2.2.3 Transmission Facilities
Table 2-2 Transmission Facilities supported by CP-8000/CP-802x:
Connection Transmission Facility Protocol

Multi-point CE-0700 V.23 Leased line modem 13 PCBST0, RP5UT1, ST1ST0, TG8ST0, UMPMT0,
traffic UMPST0
Point-to-point CE-0701 WT Channel modem 13 PCBST0, RP5UT1, ST1ST0, TG8ST0, UMPMT0,
traffic (serial) UMPST0
CM-0819 Converter RS-232/RS-485 (galvani- 103MT0, DNPST0, MODMT2, ST1ST0,
cally insulated) TG8ST0, UMPMT0
CM-0822 Field bus interface star (4x FO) 103MT0, MODMT2, MODST0, UMPMT0,
UMPST0
CM-0829 Converter RS-232/RS-422;-485 MODST0, PCBST0, RP5UT1
CM-0847 (CM-0827) fiber-optic interface 103MT0, DNPST0, MODMT2, MODST0,
(electrical FO) 14 UMPMT0, UMPST0
SIEMENS 7XV5450 Mini star coupler 103MT0, UMPMT0, UMPST0
SIEMENS 7XV5652 RS-232/FO converter 103MT0, UMPMT0, UMPST0
PHOENIX PSM-ME-RS232/RS485-P 103MT0, UMPMT0, UMPST0, MODMT2,
MODST0, BPPT0
Westermo TD-23 (analog) 15 UMPMT0, UMPST0
SATELLINE 2ASxE PCBST0, ST1ST0, TG8ST0, UMPMT0
TP Radio WDM 8000 UMPST0
Radio digital PCBST0, ST1ST0, TG8ST0, UMPMT0, UMPST0
Radio analog PCBST0, ST1ST0, TG8ST0, UMPMT0, UMPST0
Direct connection RS-232 103MT0, BPPT0, COUMT0, DNPMT0,
DNPST0, MODMT2, MODST0, PCBST0,
RP5UT1, SMST0, ST1ST0, TG8ST0, UMPMT0,
UMPST0
Direct connection RS-422 103MT0, BPPT0, COUMT0, DNPMT0,
DNPST0, MODMT2, MODST0, PCBST0,
RP5UT1, ST1ST0, TG8ST0, UMPMT0, UMPST0
Direct connection RS-485 103MT0, COUMT0, DNPMT0, DNPST0,
MODMT2, MODST0, PCBST0, RP5UT1,
ST1ST0, TG8ST0, UMPMT0, UMPST0
AGP interface adaptor UN1373BiS (RS-232 ↔ AGPMT0
optical)
Dial-up traffic Westermo TD-36, TDW-33 (analog) DIAST0
(serial) Westermo IDW-90 (ISDN) DIAST0
Westermo GDW-11 (GSM) DIAST0
Cinterion MC52iT (dual band GSM) 16 DIAST0
SMS MC Technologies MC55iw Terminal SMST0
13 Supply 5 V via modem cable for CE-070x

14 Supply 5 V via RS-232 interface (in case of CP-8022 as of production level CC)
15 Features RS-232 and RS-485 interface
16 Sending SMS possible

DC8-037-2, Edition 11.2020
System Overview
2.2 Communication
Connection Transmission Facility Protocol

GPRS Integrated GPRS modem (CP-8022) ET84, OPUPT0, OPUPT1
Siemens SCALANCE M874-2 ET84, OPUPT0, OPUPT1
Siemens MD741-1 16 ET84, OPUPT0, OPUPT1
Dr. Neuhaus Tainy EMOD-V2-IO ET84, OPUPT0, OPUPT1
Dr. Neuhaus Tainy EMOD-L1-IO 17 ET84, OPUPT0, OPUPT1
Welotech TK701G, TK704G ET84, OPUPT0, OPUPT1
Ethernet ET84, ET85, DNPiT2, DNPiT1, MBCiT0,
MBSiT0, OPUPT0, OPUPT1
2.2.4 Configuration Examples
[dw_A8000_comm_config_control_center, 1, en_US]
Figure 2-5 Communication CP-8000 - Configuration Example
17 Without IPsec VPN tunnel

DC8-037-2, Edition 11.2020
System Overview
2.2 Communication
[dw_A8000_comm_config_local_devices, 1, en_US]
Figure 2-6 Communication CP-802x - Configuration Example

DC8-037-2, Edition 11.2020
System Overview
2.3 Firmware Structure and Data Flow
2.3 Firmware Structure and Data Flow

The basis for CP-8000/CP-802x is a modular, open, and thus non-technology-dependent system architecture
for processing, communication, and peripherals (single-processor system, firmware).
The adaptation to the specific needs of the application is accomplished by relying on an individual hardware
configuration and by loading standard firmware and parameters. The parameters influence, within their
defined limits, not only the behavior of the firmware functions, but also that of the hardware functions. As a
result, mechanical parameterizations such as the changing of jumpers or loads are no longer necessary on any
of the module types. This permits not only online reconfiguration but also the gapless documentation of set
parameters by the engineering system, as well as simplified inventory management.
Due to the different requirements in terms of functionality, also different data flow concepts are produced:
• Telecontrol
For telecontrol tasks and the distribution of user data in networked plants, the use of spontaneous trans-
mission proves advantageous for optimizing the utilization of the in many cases limited communication
bandwidth. This helps avoid constant burdening of the data sinks with unnecessary data.
• Automation
For the implementation of a freely definable open-/closed-loop control function a deterministic guaran-
teed reaction time is needed. This is achieved by using the consistently periodic concept with regard to
data acquisition, execution of functions, and data transfer, regardless of the number of changing signals.
As interface to the process serve the integrated I/O Modules. The input/output and processing of the process
signals is performed by means of the I/O Master Module.
Internal Data Flow
[dw_A8000_dataflow, 1, en_US]
Figure 2-7 CP-8000/CP-802x - Internal Data Flow

DC8-037-2, Edition 11.2020
System Overview
2.4 Engineering
2.4 Engineering
Engineering, diagnosis and test of CP-8000/CP-802x takes place alternatively via
• SICAM TOOLBOX II (as of Version 6.01)
• SICAM WEB
• SICAM Device Manager
2.4.1 SICAM TOOLBOX II
The integrated engineering system SICAM TOOLBOX II comprises all stages of plant configuration and mainte-
nance, this means data collection, configuring, parameter setting, expanding, changing, testing, system diag-
nosis, and documentation.
[sc_tbii_splash_screen, 1, --_--]
Figure 2-8 SICAM TOOLBOX II Splash Screen
The introduction of object orientation allows project engineers to describe real units and pieces of equipment
in the configuration process (circuit breakers, feeders, etc.). Project engineers can take advantage of these
structural advantages especially in cases where systems are constituted of a plurality of primary units and
pieces of equipment of equal type (for example a transformer substation). This yields enormous streamlining
effects for the engineering process.
The SICAM TOOLBOX II stores all information in one central database. Once a piece of information has been
entered, it will immediately and always be available in its latest updated form to all tools of the SICAM
TOOLBOX II and to all people working on a project.
This reaches from stand-alone terminal solutions all the way to complex network solutions. In networks,
several engineers may work on one or more projects at the same time. Whether on a standalone terminal or in
a network, always the same SICAM TOOLBOX II is used.
Implementation of Application Programs

When configuring via the SICAM TOOLBOX II, application programs (open-/closed-loop control function) can
be created as function diagram (FUD) with the tool “CAEx plus”. Optionally, also an existing instruction list can
be imported into the SICAM TOOLBOX II.
In view of its conformity with IEC 61131-3, “CAEx plus” grants the user access to a well-established and gener-
ally acknowledged standard. This helps shorten staff training times considerably.
By means of the available standard-conformal module libraries and standard-conformal data types, the engi-
neering becomes more transparent and is possible with high application quality.

DC8-037-2, Edition 11.2020
System Overview
2.4 Engineering
2.4.2 SICAM WEB for simple Applications
A top priority was also a simplified engineering possibility.

For the configuration, diagnosis and testing, CP-8000/CP-802x provides an integrated web server that is oper-
ated with a standard web browser. By means of that, no special tools or additional licenses are needed.
[sc_dashboard, 1, en_US]
Figure 2-9 SICAM WEB Dashboard
When configuring via web browser, there are some restrictions in the engineering options. You can find more
details thereto in the following section.
Implementation of Application Programs

Simple application programs can be created with an ASCII text editor as instruction list (IL), based on the
standard IEC 61131-3. Via the web browser, the instruction list can be uploaded into the automation unit for
execution.
2.4.3 Differences with the Engineering Tools
SICAM TOOLBOX II SICAM WEB

License required ✓ –
Interfacing • Directly via RS-232 • Directly via RS-232
• Remotely via Toolbox cable • Via Ethernet
and further SICAM RTUs auto-
mation units
• Via Ethernet
Addressing Via region, component Via IP address

DC8-037-2, Edition 11.2020
System Overview
2.4 Engineering
SICAM TOOLBOX II SICAM WEB

Engineering mode Offline, subsequently transform Online in target system
parameters and load into target
system
Remote maintenance ✓ –
HW configuration I/O Modules must be configured in I/O Modules will be automatically
the OPM II after configuring the I/O acquired after configuration of the
Master Module I/O Master Module and restart
Process-technical parameterization • Images can be created for the • Process signals are configured
instancing of object types individually per hardware I/O
• Bulk edit for the values of the • No automatic protocol param-
images possible eterization
Application program Based on IEC 61131-3, with restric- Based on IEC 61131-3, with restric-
tions (memory) tions (memory)
• Function chart via “CAEx plus” • Instruction list

• Instruction list
Test functions for telecontrol • Data flow test I/O test (with restrictions)
• Topology test
• I/O test
Test of application program • Online test Online test (with restrictions)
• Offline simulation
Diagnosis ✓ With restrictions
Sum diagnosis information ✓ By means of instruction list via
SNMP traps
Read security logbook – ✓
Role-based access control – ✓
Extras – Program Sicam_first_startup (find
all CP-8000/CP-802x devices in a
network and preset IP addresses)

DC8-037-2, Edition 11.2020
3 Function Packages
3.1 System Services 66

3.2 Telecontrol 72
3.3 Automation 76

DC8-037-2, Edition 11.2020
Function Packages
3.1 System Services
3.1 System Services

The function package System Services provides general functions and basic services that are required by other
function packages. It contains:
• Communication with the engineering system
• Integrated webserver
• Data flow control
• Addressing
• Real-time concept
• General interrogation
• Monitoring functions
• Failure management
• Diagnostics and signaling
• Autonomy
• Storage of application data
• Storage of firmware
• Role-based access control
• Factory Reset
• Configurable SD card usage
• IPSec VPN
• Security Logging
3.1.1 Communication with the Engineering System (SICAM TOOLBOX II)
For the communication between the SICAM TOOLBOX II and CP-8000/CP-802x exist different variants:
• Physical connection of the SICAM TOOLBOX II with an automation unit

– Locally by means of a direct cable (RS-232 interface)
– Remotely
– Serial communication link via modems (RS-232 or RS-485 interface)
– Ethernet connection (TCP/IP) and Terminal Server (RS-232 interface)
– Ethernet connection (TCP/IP)
• Logical connection of the SICAM TOOLBOX II with that automation unit, that is the subject of the engi-
neering task:
– Local automation unit
(that is that one, to which the physical connection exists, regardless in which of the previously
mentioned forms)
– Remote automation unit
(automation unit that can be reached via the local automation unit; consistent remote communica-
tion according to IEC 60870-5-101 or -104 is required)

DC8-037-2, Edition 11.2020
Function Packages
3.1 System Services
Except for first-time initialization processes, all tasks are possible in each of the variants listed above:
• Parameter setting
• Diagnostics
• Test
• Load firmware, load parameters
3.1.2 Simplified Engineering via SICAM WEB
For simple engineering tasks a webserver resides on the Master Module. The webserver provides the menus
for the engineering and maintenance designed as websites. The engineering takes place online via a standard
web browser.
The following functions are supported:
• Configuration of I/O Master Module and protocol elements
• System-technical parameter-setting
• Process display, process simulation
• Diagnosis
• Event list, alarm list
• Read security logbook
• Configuration of the role-based access control
• Load firmware
• Load backup file, save backup file
• Application program handling (IL)

– Configuration
– Load code
– Diagnosis
– Online test
3.1.3 Data-Flow Control
The data flow control is that system function which coordinates the communication of messages within the
automation unit.
This function supports:
• Messages with Process Information
• Messages with System Information
For the tracking of messages within an automation unit the following test functions are available:
• Data Flow Test
• Message Simulation

DC8-037-2, Edition 11.2020
Function Packages
3.1 System Services
3.1.3.1 Messages with Process Information

IEC 60870-5 distinguishes between the following classes of messages. The type identification of each message
provides information about the class to which a message belongs and with which methods it is to be
distributed:
• Messages with process information in monitor direction

– binary information, measured values, integrated totals and bit patterns
• Messages with process information in control direction

– commands, setpoint values and bit patterns
The distribution of messages with process information takes place by way of routing (telecontrol function) or
assignment (open/closed-loop control function) based on the message address and type identification in the
message.
Messages with process information, that are to be transmitted to other automation units via protocol
elements, are distributed with the help of the function Automatic Data Flow Routing.
For messages with process information that are to reach sinks within the automation unit (I/O Modules, open-/
closed-loop control function) the routing information or assignments are automatically derived from parame-
ters (datapoint address).
Predominantly used are message formats according to IEC 60870-5-101/104 in the public range with the
exception of user data containers. Therefore, for their part the messages are compatible and interoperable
with many other manufacturers.
Messages with process information have a 5-stage message address. Message addresses must be parameter-
ized at the sources (I/O Modules, open-/closed-loop control function).
3.1.4 Addressing
3.1.4.1 Addressing of Automation Units

Each CP-8000/CP-802x device forms an automation unit and is addressed using
• Region number (0 to 249)
• Component number (0 to 255)

Within a system-technical plant, the automation unit must be uniquely addressed, which means the maximum
size of a system-technical plant can be 64000 automation units.
3.1.4.2 Addressing of the Process Information

Addressing and the structure of the process information to be passed on by CP-8000/CP-802x are consistent
with the IEC 60870-5-101/104 standard. Therefore, the information is in turn compatible and interoperable
with many other vendors.
In the automation network, each data point is addressed by means of
CASDU 1………Common address of ASDU, octet 1
CASDU 2………Common address of ASDU, octet 2
IOA 1……………Information object address, octet 1
TI………………...Type identification
3.1.5 Time Management
3.1.5.1 Clock
Generally, CP-8000/CP-802x supports automatical time tagging for all data. On the Master Module resides the
central clock of the automation unit.

DC8-037-2, Edition 11.2020
Function Packages
3.1 System Services
Time tagging takes place automatically at each point in the system where spontaneous data originates. Data is
transferred priority-controlled, in standard protocols with 7 octet date and time with resolution of 1 ms.
3.1.5.2 Time Setting and Synchronization

For time setting and synchronization, the following possibilities are available:
• via serial communication
• via LAN (Ethernet TCP/IP, SNTP/NTP)
NTP/SNTP Client
Up to 4 different NTP servers can be parameterized for the time setting. The time for the synchronization is
determined via a defined algorithm from the received times of the NTP servers.
Integrated NTP Server

With the integrated NTP server time can be provided to further devices via LAN communication lines.
3.1.6 General Interrogation
During startup and after errors in the system (communication errors, FIFO overflow events), the automation
units involved ensure that operations are resumed automatically in a coordinated manner.
This means that the communication connection is established and all data concerned as well as relevant
system information are transferred from their source all the way to their sink, in order to update the process
images throughout the system (taking a multi-hierarchical network into account). This is done by prompting a
general interrogation of the respective portion of the automation network where the error has occurred.
3.1.7 Monitoring Functions
Monitoring of an automation unit
• Functionality of the processor and of the memories (periodical test of the program, data, and parameter
memories, as well as watchdog function)
• Internal communication capability (periodical internal test messages with monitoring function)
• Data integrity (internally secured data transmission with parity, plausibility check at the internal inter-
faces, identification of data of failing modules)
• Information loss due to a buffer overflow
• Correctness of internal workflow sequences
Monitoring of system environment
• Plausibility of process states
• Plausibility of process sequences
• Availability of process circuits
Monitoring of communication
• Functionality (periodical call messages with monitoring function, monitoring of transmission quality)
• Data integrity (secured transmission, identification through failure of data concerned)

DC8-037-2, Edition 11.2020
Function Packages
3.1 System Services
3.1.8 Failure Management
The failure management system concept implemented in CP-8000/CP-802x ensures the individual identifica-
tion of data of failing system components and the correct system and process behavior in disturbance events.
For this purpose, the failure management function includes
• a system function for failure detection (for instance for modules, communication)
• derived therefrom a system signaling in the form of status information in spontaneous messages and in
the form of special data points for the open-/closed loop control function
• a parameter-settable behavior of I/O Master Modules with output function

This way, the state for each process information is available at all data sinks (peripheral outputs, open /closed
loop control function, process control system), and it is possible - depending on the requirement and function-
ality - to elicit an appropriate counterreaction therefrom.
3.1.9 Diagnostics and Signaling
The diagnostics function manages the system states and error information detected by the various functions
and their watchdogs. It permits the indication of the internal system and error information, and of the process
states by means of the engineering tool.
System and error states are filed in tables as current and saved information. This information can be displayed
in detail locally and from remote locations. The saved information can be acknowledged and can therefore be
updated again. For the sake of better clarity, these tables are divided into various classes.
The internal I/O Modules supply the detected system and error states together with additional information (for
instance cause of error, originator description).
A sum information about the detailed errors is transmitted via the communication to the closest automation
units, where it is managed.
Important detailed and sum information is indicated by means of LEDs, process states via the display at the
front panel.
3.1.10 Autonomy
This system concept ensures that, if central parts succumb to a failure, as much of the functionality as possible
will remain intact. CP-8000/CP-802x is capable of functioning autonomously – this means, it will continue
carrying out its defined local function even where the entire communication is disturbed.
In such events, the system invariably ensures that the failure is detected and signaled. Based thereon, a func-
tional behavior may be defined, if necessary, that is adapted to the disturbance event at hand.
3.1.11 Storage of Application Data
With engineering via the SICAM TOOLBOX II, application data is stored in a data base on the engineering PC.
From there it can be loaded into a target system, or else be written on a suitable SD card.
With engineering via the web browser, application data is written directly on the SD card in the target system.
The application data of a project created via the web browser can be saved in a file on the engineering PC.
With the aid of the program Sicam_first_startup this data can be written on a suitable SD card (for instance
for the duplication of a project).
After putting a written SD card into a target system, the target system transfers changed or added data into its
main memory during a subsequent startup.

DC8-037-2, Edition 11.2020
Function Packages
3.1 System Services
3.1.12 Storage of Firmware
Current firmware revisions for CP-8000/CP-802x can be loaded as binary files
• online into a target system with an equipped SD card
• offline through storage on a suitable SD card

In both cases, the target system unpackes the corresponding files and stores the firmwares in the main
memory during startup.
3.1.13 Role Based Access Control
The “Role Based Access Control” (RBAC) is a process to restrict the access to data or services in a multi user
system. Therefore different roles with different access rights are assigned to the users. Each user is protected
by a password.
The configuration of the local role based access control is done with SICAM WEB (Administration - User). You
have to create local users for each device. That activity can only be done by users which have the corre-
sponding authorization (e.g. the standard user “administrator”). You can assign one or more of the predefined
roles to each local user. Each of these roles has different rights/functions for working with the device. Which
roles are predefined and which rights each has is described in the document SICAM A8000 Series/SICAM RTUs/
SICAM TOOLBOX II – Administrator Security Manual (DC0-115-2), chapter Measures for System Hardening,
section SICAM A8000 Series / SICAM RTUs, section Role-Based Access Control in SICAM A8000 Series.
3.1.14 IPSec VPN
IPSec VPN (Internet Protocol Security – Virtual Private Network) is an extension of the Internet Protocol (IP) for
encryption and authentication mechanisms. IPSec VPN actively establishes a VPN tunnel (initiator), which
guarantees the required confidentiality, authenticity and integrity of data transmission in IP networks. The
termination of the IPSec VPN tunnel takes place in a router. CP-8000/CP-802x supports 2 IPSec VPN tunnels.
Thus, it is for instance possible, to completely secure the IEC 60870-104 communication between CP-8000/
CP-802x and a higher-level control center, even if the connection is running over a public network.
CP-8000/CP-802x uses the IKE protocol (Internet Key Exchange) and the PSK authentification process (Pre-
Shared Key). The used pre-shared key can be set by means of the engineering tool (e.g. SICAM TOOLBOX II)
and is securely stored in SICAM TOOLBOX II and in CP-8000/CP-802x.
3.1.15 Security Logging
CP-8000/CP-802x provides a security logbook which acquires security-relevant events and transmits it by
means of a SysLog client to a SysLog server. One automation unit (AU) can operate several SysLog clients (up
to 20).

DC8-037-2, Edition 11.2020
Function Packages
3.2 Telecontrol
3.2 Telecontrol
The function package Telecontrol includes the following functions:
• Communication with other stations via selectable protocols

– Protocol elements
– Automatic or selective data flow routing
– Data storage
– Priority control
– Monitoring of the communication links upon failure
• Communication within the Automation Unit
• Protocol element control and return information
• Archiving of events (DEAR)
• Process data archive
• Test functions
• Process data input and output
NOTE
i The listed functions are described in detail in the document SICAM RTUs Common Functions System and
Basic System Elements.
3.2.1 Communication with Other Stations
3.2.1.1 Protocol Elements

The communication function controls the transmission of messages via protocol elements to other automa-
tion units or control systems.
A protocol element is based on hardware integrated in the Master Module for serial or LAN/WAN communica-
tion, and supports protocols according to IEC 60870-5-101/103/104, as well as various protocols for the
communication with third-party systems.
Communication in Transmit Direction
• The messages to be transmitted are learned through the automatic data flow routing and stored in the
data storage
• The transfer of the messages from the data storage to the protocol elements takes place via a priority
control in order to optimally utilize the transmission route
Communication in Receive Direction
• Messages with process information are distributed to all functions within the automation unit
• Messages with system information are either processed directly (example: station interrogation) or
distributed further based on their destination address (CASDU) (example: messages for remote mainte-
nance)
3.2.1.2 Automatic or Selective Data Flow Routing

For the data flow routing, a routing of individual process information items is not necessary. Simply only the
direction (monitor direction, control direction, both directions) in which the messages are to be transmitted
must be parameterized.

DC8-037-2, Edition 11.2020
Function Packages
3.2 Telecontrol
The type identification of each message provides information about the class (see3.1.3.1 Messages with
Process Information) to which a message belongs and with which methods it is to be distributed:
• Messages with process information in monitor direction

– For simple applications, the messages can be distributed via an entry in the topology
– For more complex applications, the messages can be distributed selectively by means of data flow
filters
For each communication interface, pass-through filters or blocking filters can be set; since wildcards
can also be used for all address attributes of the message, it is possible to control the data flow very
specifically with simple means.
• Messages with process information in control direction

– The messages are distributed to the destinations determined by their CASDU over interfaces that are
defined in the topology; the CASDU is interpreted as destination address.
3.2.1.3 Data Storage

The messages that are intended for transmission over communication interfaces, are in prin-ciple stored chro-
nologically in rings. There is a process image both before and after a ring. The arrangement, consisting of one
ring and two process images, is called a priority channel (priority channels for transparent data do not have
any process images).
Depending on the data communication mode of the protocol element over which the communication is
processed, priority channels are provided for every priority of the messages to be transmitted and for every
station that can be reached via the protocol element:
• Data communication mode "multi-point" (e.g. multi-point traffic, LAN )

One priority channel for every transmission priority, for every station and for every protocol element
• Data communication mode "single-point"

One priority channel for every transmission priority and for every protocol element
With regard to the data that they transport, priority channels are distinguished as follows:
• Time synchronization
• System information
• Process information in control direction
• Process information in monitor direction priority HIGH with class 1 data
• Process information in monitor direction priority MEDIUM with class 2 data
• Process information in monitor direction priority LOW with class 2 data
• Transparent information
Functions for priority channels:
• State compression for measured values (can be set using parameters) for the reduction of the flood of
messages, that can continuously generate fluctuating measured values
• Behavior with a priority channel overload
• Behavior during a communication failure (transmit direction)
• Monitoring of the dwell time (parameter-settable) of messages with process information in control direc-
tion
Messages that are stored too long in the priority channel are discarded
• Answering of station interrogations
• Behavior during failure of I/O Master Modules, communication interfaces etc.
• Blocking (series of information elements)

DC8-037-2, Edition 11.2020
Function Packages
3.2 Telecontrol
3.2.1.4 Priority Control

The priority controller has the task of selecting messages recorded in the data memories in-dependently and
individually for each interface and station, and to direct the transmission of the messages via the protocol
elements in accordance with their priority. This ensures that with simultaneous existence of several active
information items, the higher-priority, highly important information is transmitted first.
The prioritization does not however represent an absolute priority status, but rather a measure for dividing up
the channel capacity. This ensures that even with continuously available higher-priority data, those of lower
priority can also be transmitted.
3.2.2 Communication within the Automation Unit
Within the automation unit, the Telecontrol function package communicates with the Automation function
package via its telecontrol interface (see3.3.1 Telecontrol Interface).
3.2.3 Protocol Element Control and Return Information
This function is used for the user-specific influencing of the functions of the protocol elements. The main
application lies with protocol elements with multi-point data communication mode and especially for dial-up
traffic configurations.
This function contains two separate independent parts:
• Protocol element control

– Test if stations are reachable
– Suppression of errors with intentionally switched-off stations
• Protocol element return information

– Cost control of telephone charges
– Cost-efficient utilization of the telephone line (for instance command initiation only if a connection
has already been established)
3.2.4 Decentralized Archive
In case of a communication fault, occurring events can be recorded in a decentralized archive. After elimina-
tion of the fault the superior control system can demand the archive of the respective target system. By means
of this function, a possible data loss will be prevented.
• Reconstruction of all process-relevant data during a communication fault
• Transmission of the archive to the control system

– Automatic initiation by the control system
– File transfer acc. to IEC 60870-5-101, section 7.4.11
• Data saving
– Datapoint-specific parameter-settable
– Number of files, memory size parameter-settable
– Spontaneous for binary information items and integrated totals
– Definable cycle for measured values
– Non-volatile on flash card
• Configuration acc. to IEC 60870-5-101/104 (point-to-point, multi-point traffic, dial-up traffic, Ethernet),
also multi-hierarchical configurations possible
• Also multi-hierarchical configurations are possible

DC8-037-2, Edition 11.2020
Function Packages
3.2 Telecontrol
• Reading of the archive via SICAM TOOLBOX II possible
• Front-end: SICAM AK 3, optionally redundant
• Supported by SICAM SCC (also third-party control system possible)

– Update of the archive in the control system
– Own status marking
– Automatic subsequent billing of
– Counter differencies
– Secondary values
– Mean values and extreme values
3.2.5 Process Data Archive
Binary information states, measured values and integrated totals can be recorded in a process data archive.
This archive comprises up to 5.000.000 records over a maximal period of 3 months.
• Data saving
– Datapoint-specific parameter-settable
– Spontaneous for binary information items and integrated totals
– Definable cycle for measured values
– Non-volatile on flash card
• Reading of the archive via SICAM WEB by means of file download possible
3.2.6 Test Functions via SICAM WEB
The test functions provide a status display with the actual process values at each optional I/O Module. Addi-
tionally, process data outputs can be changed manually.
3.2.7 Process Data Input and Output
The process data input and output comprises
• Acquisition and preprocessing of the process data from the process image of the I/O Modules
• Generation and spontaneous transfer of messages with process information to the communication for
further processing
therein included are
– time information (resolution 1 ms)
– processed input signals
– change-monitored conditioned values
– change-monitored derived information
• Spontaneous reception of messages with process information from the communication
• Postprocessing and forwarding of the process data for the output via I/O Modules

DC8-037-2, Edition 11.2020
Function Packages
3.3 Automation
3.3 Automation
The function package Automation contains the following functions:
• Telecontrol interface
– Reception of messages with process information
– Handling of commands according to IEC 60870-5-101/104
– Change management and generation of messages with time tag
• Open-/closed-loop control function

– Test functions
• Process data input and output
3.3.1 Telecontrol Interface
3.3.1.1 Transfer of Messages with Process Information

Reception of messages with process information and transfer to the open-/closed-loop control function for the
purpose of further processing.
Messages with process information in monitor direction:
• Single-point information, double-point information, step position information
• Measured values
• Integrated totals
• Bit string of 32 bit
Messages with process information in control direction
• Single commands, double commands, regulating step commands
• Setpoint commands
Treatment for Commands according to IEC 60870-5-101/104

The treatment for commands serves to check the spontaneous information objects to be processed with the
help of the open-/closed loop control function and transmission of the confirmation for:
• Pulse commands (single commands, double commands, regulating step commands)
• Setpoint values (setpoint command)

Data transfer of the spontaneous information objects to the open-/closed-loop control function for further
processing is dependent on the result of the checks.
The activation of the element or function to be controlled is the task of the function open-/closed-loop control.
For the proper operation of this function, information from the open-/closed-loop control function (for
example, from an interlocking logic) is required to select a positive or negative confirmation.
The treatment for commands can be activated individually for each command via a parameter.

DC8-037-2, Edition 11.2020
Function Packages
3.3 Automation
The treatment for pulse command comprises the following processing functions:
• Prepare command output procedure

– Formal check
– Retry suppression
– 1 out of n check
– Direct command or
– Select and execute command (“select/execute”)
– Control location check
– Command locking
• Initiate command output

– Command to application program
• Monitor pulse duration (only pulse commands)

– Command output time
– Return information monitoring
• Terminate command output procedure
3.3.1.2 Change Monitoring and Generation of Messages with Time Tag

For the generation of messages with process information, the signals in the output process images that are
assigned to an element of a spontaneous information object, are monitored for change.
The change monitoring takes place in the grid of the cycle time of the open-/closed-loop control function, in
which the signal is assigned to a spontaneous information object.
On a change of the state in a corresponding element of the spontaneous information object, the generation of
the message is initiated.
If a spontaneous information object has been activated for transmission due to a change, a message with
process information is generated. The time tag corresponds either cycle-synchronous with the current time
(resolution corresponds with the cycle time) or the time information from an assigned spontaneous informa-
tion object.
3.3.2 Open/Closed-Loop Control Function
The open-/closed-loop control function is used for the management of automation tasks with the help of a
freely programmable application program.
The creation of the application program is carried out by the SICAM TOOLBOX II with the tool “CAEx plus”
predominantly in function diagram technology according to IEC 61131-3. Alternatively, the application
program can be created as instruction list with an ASCII editor.
The application program processes process information (so-called signals) from the connected I/O Modules
and/or from other system elements in the automation network of the specific process-technical plant.
Process images form the interface of the application program to the outside world. It is distinguished between
input process images and output process images.
The exchange of the process information can take place in two ways:
• Transmission of periodical information objects from and to the I/O Master Module (process data input and
output)
• Transmission of spontaneous information objects from and to functions within the automation unit,
other automation units or control systems via the telecontrol interface

DC8-037-2, Edition 11.2020
Function Packages
3.3 Automation
3.3.2.1 Non-Volatile Storage

Variables, signals (input process images for spontaneous information objects) and function blocks can be
saved non-volatile. That means, that after a power failure these variables and signals are immediately avail-
able again with their values before the power failure.
3.3.2.2 Task Management

The open-/closed-loop control function manages the application program in a periodically running task.
Coordination of the Sequences of a Task
• Periodical start in the selected cycle
• Programmable single-run upon change of a signal from the communication or from the I/O Modules (no
hardware interrupt)
• Input handling
• Program processing
• Output handling
Cycle Time
• Within the cycle time, the application programs must process the input handling and the output handling
• The cycle time can be set in the application program
Watchdog Timer
This function monitors the proper sequence of the task within its set cycle time. If the task is not finished with
its input handling, program processing and its output handling within this time, the next cycle for this task is
omitted and a time-out is signaled.
With serious time-outs, for example due to a malfunction, the reliability of the application pro-gram becomes
questionable. A time scale can be defined for such cases, the exceeding of which leads to an error message
and a controlled shutdown of parts or the entire application program as well as all I/O Master Modules
connected.
3.3.2.3 Loading Application Program

The loading of an application program is always associated with a startup.
Fundamentally however, the fault-free operation and consequently the availability of every control or
controller depends on the quality of the program – in other words the measure of how free they are of formal
and logical errors. The loading of error-burdened changes can always lead to interruptions to operation.
3.3.2.4 Test Functions

The entire functionality of the test functions applies to
• the engineering tool (“CAEx plus Online Test” of the SICAM TOOLBOX II or SICAM WEB)
• the online test function of the open-/closed-loop control function of the automation unit
While in the engineering tool all functions of the user interface can be found, the open-/closed-loop control
function provides functions for the execution of the operator inputs.
If for example a value is to be displayed, the selection of the value and its display takes place in the engi-
neering tool. For this purpose, the open-/closed-loop control function is given the task of reading out the
selected value and transmit it to the user interface.
In the following, those functions are listed that the test function of the open-/closed-loop control function
provides.

DC8-037-2, Edition 11.2020
Function Packages
3.3 Automation
Display and Setting of Variables and Signals
• Display of variables and signals
• Single setting of variables (single forcing)

– The value of a variable can change again at any time after setting, due to the function of the
program (“CAEx plus Online Test”)
– The value of a variable remains maintained until the test mode is active (SICAM WEB)
Blocking and Enabling of Messages with Process Information and Periodical Information
The copy operation of messages with process information and periodical information can be blocked and
enabled
• in the input-side process images
• in the output-side process images

This can take place with the following granularity:
• Per message
• All messages
• Per periodical information
• I/O Master Module

Changing the Execution Status of the Open-/Closed-Loop Control Function
• Halt and continue program
• Perform cold start or warm start of the program

Test Means
The available test means are:
(a) Halting of the execution due to a trigger condition (“breakpoint”)
(b) Execution of the task in cycle steps
The function (a) is not supported by SICAM WEB. For the function (a) a trigger condition is defined in the tool
“CAEx plus Online Test”. A trigger conditions consists of up to 4 conditions. The conditions of a trigger condi-
tion are combined equal-ranking with AND or OR.
A condition compares a variable with a constant value to be specified:
Variable of the Type Condition <operator>
BOOL variable <operator> value = <>
INT or REAL variable <operator> value < = <> >
The function “halting the execution due to a trigger condition” halts the task, if the trigger condition is satis-
fied. The trigger condition is evaluated at the end of the task.
Display Statistic Information

The following information on the application program is made available:
• Parameterized cycle time
• Current run time
• Maximum run time
• Number of time-outs that the system has registered
• Used memory space

During the course of the interrogation, the current run time and the number of time-outs can be optionally
reset (does not apply for SICAM WEB).

DC8-037-2, Edition 11.2020
Function Packages
3.3 Automation
3.3.3 Process Data Input and Output
The peripheral functions comprise the process signal input and output.
• Acquisition and preprocessing of the process data from the process image of the I/O Modules
• Periodical transfer of the process information to the open-/closed-loop control function

– Processed input signals
– For processing, operations-relevant error information of the processed input signals (for instance
“binary information faulty”)
• Periodical reception of the process information from the open-/closed-loop control function
– Derived information items
– Processing results
– Operations-relevant error information (for instance “command output fault”)
• Postprocessing and forwarding of the process data for the output via I/O Modules

DC8-037-2, Edition 11.2020
4 Ambient Conditions
NOTE
i The following data applies for CP-8000/CP-802x without external SICAM TM I/O Modules.
If CP-8000/CP-802x is expanded with external SICAM TM I/O Modules, the corresponding data of the SICAM
TM system apply. Refer to SICAM TM System Datasheet; MC6-007-2.
4.1 Protection Type 82

4.2 Mechanical Ambient Conditions 83
4.3 Climatic Ambient Conditions 84
4.4 Electromagnetic Compatibility 85
4.5 Storage and Transport 91

DC8-037-2, Edition 11.2020
Ambient Conditions
4.1 Protection Type
4.1 Protection Type

Operational equipment Protection type acc. to IEC 60529 Protection class acc. to IEC 61140
CP-8000 • Front: IP 40 Class II
CP-8021 • Other sides of housing: IP 20 Protection through double or rein-
CP-8022 (incl. terminals) forced insulation
PS-8620 • Front: IP 40 Class II
PS-8622 • Other sides of housing: IP 20 Protection through double or rein-
PS-8640 (incl. terminals) forced insulation
PS-8642
SICAM I/O Modules • Front: IP 40 Class II 18
SICAM TM I/O Modules • Other sides of housing: IP 20 Protection through double or rein-
(incl. terminals) forced insulation
CM-8830 • Front: IP 40 Class III
• Other sides of housing: IP 20 Extra-low voltage
18 AO-8380: Class III

DC8-037-2, Edition 11.2020
Ambient Conditions
4.2 Mechanical Ambient Conditions
4.2 Mechanical Ambient Conditions

The listed values cover or exceed the required seismic loading according to IEC 60870-2-2 Cl.S3 and
IEC 60255-21-3 Cl.1. The values apply in operation and for storage.
The permitted mechanical stresses during transport depend on the transport packaging. The device packaging
is not a transport packaging.
Harmonic
Parameter Value Test Standard Product Standard Class

Amplitude of the excursion 1 to ±3.0 mm IEC 60068-2-6 IEC 60870-2-2 Bm
9 Hz
Acceleration 9 to 200 Hz 10 m/s2
Acceleration 200 to 500 Hz 15 m/s2
Amplitude 10 to 60 Hz ±0.075 mm IEC 60068-2-6 IEC 60255-21-1 2
Acceleration 60 to 150 Hz 1.0 g
Shock

Acceleration; 11 ms duration 100 m/s² IEC 60068-2-27 IEC 60870-2-2 Bm
(functional capability)
Acceleration; 11 ms duration 15 g IEC 60068-2-27 IEC 60255-21-2 1
(resistivity)
Continuous Shock

Acceleration; 16 ms duration 10 g IEC 60068-2-27 IEC 60255-21-2 1
Seismic harmonic

Amplitude 1 to 8 Hz (horizontal) ±7.5 mm IEC 60068-3-3 IEC 60255-21-3 2
Amplitude 1 to 8 Hz (vertical) ±3.5 mm
Acceleration 8 to 35 Hz (hori- 2g
zontal)
Acceleration 8 to 35 Hz (vertical) 1 g

DC8-037-2, Edition 11.2020
Ambient Conditions
4.3 Climatic Ambient Conditions
4.3 Climatic Ambient Conditions

Parameter Range Test Standard Product Standard Class
Minimum air temperature -25 °C/96 h 19 IEC 60068-2-1 Ad IEC 60870-2-2 C2/C3
(cold) -40 °C/96 h 20 IEC 60654-1 C2/C3
Maximum air temperature 70 °C/96 h IEC 60068-2-2 Bd IEC 60870-2-2 C3
(dry heat) 10% rF IEC 60654-1 C3
Damp heat, cyclic 25 °C to 55 °C for IEC 60068-2-30 – –
144 h
95% rF
Damp heat, steady state 40 °C for 240 h IEC 60068-2-78 – –
93% rF
Temperature gradient ≤30 °C/h – IEC 60870-2-2 C2
IEC 60654-1 C2
Relative air humidity 5 to 95% – IEC 60870-2-2 C1
IEC 60654-1 C1
Absolute air humidity ≤ 35 g/m3 – IEC 60870-2-2 C2
IEC 60654-1 C2
Air pressure 70 to 106 kPa – IEC 60870-2-2 C2
(up to 3000 m) IEC 60654-1 C2
Temperature during storage and -30 to +85 °C – – –
transport
Pollution degree 2 IEC 61010-1 – –
The listed values apply for the use in open-air cabinets for bay devices. The products can be exposed to sun
and heat. They can be exposed as well to air flow caused by draught in buildings, for example, by open
windows or influences of technical processes.
Bedewing is possible for a short time, for example, during the course of maintenance tasks (not in operation).
Condensation, precipitations, water and icing are not permitted in operation.
Heating and cooling is used to maintain the necessary conditions, especially in case of great differences
between indoor and outdoor climate.
The conditions of this class normally occur in normal living and working areas, as well as in production rooms
for electronic and electrotechnical products, telecontrol rooms, storage rooms for valuable and sensitive
devices.
NOTE
i CP-8000: In low temperatures, the display becomes more sluggish and legibility may be impaired
(at –25 °C the response time is 5 s).
NOTE
i Some SICAM TM I/O modules were checked on the basis of deviating values. For more detailed information,
refer to SICAM TM system data sheet.
19 Applies for CP-8000 (6MF21010AB100AA0)

20 Applies for CP-8000 (6MF21011AB100AA0), CP-8021, CP-8022, SICAM I/O modules

DC8-037-2, Edition 11.2020
Ambient Conditions
4.4 Electromagnetic Compatibility
4.4.1 System Properties

Discharge of static electricity 8 kV A IEC 61000-4-2 IEC 60870-2-1 3
(ESD) 6 kV C
Electromagnetic fields 10 V/m IEC 61000-4-3 IEC 60870-2-1 3
80 MHz to 1 GHz
3 V/m
1 to 6 GHz
50 Hz magnetic fields 100 A/m (cont.) IEC 61000-4-8 IEC 60870-2-1 4
1000 A/m (3 s)
Pulse-shaped magnetic fields 1000 A/m IEC 61000-4-9
Radio interference voltage 79 dBμV CISPR22 IEC 60870-2-1 A
approx. peak value (0.15 to 0.5 MHz) CISPR22 A
60 dBμV
(0.5 to 30 MHz)
Radio interference voltage mean 66 dBμV CISPR22 IEC 60870-2-1 A
value (0.15 to 0.5 MHz) CISPR22 A
60 dBμV
(0.5 to 30 MHz)
Radio interference field strength 40 dBμV/m CISPR22 IEC 60870-2-1 A
(10 m) approx. peak value (30 to 230 MHz) CISPR22 A
47 dBμV/m
(0.23 to 2 GHz
The characteristics required according to the standards IEC 61000-6-2 and IEC 61000-6-4 are covered by the
listed values.
NOTE
i This is a class A product. In a domestic environment this product may cause radio interference in which
case the user may be required to take adequate measures.
4.4.2 Power Supply

Dielectric test (50 Hz) 3.0 kVeff 60 s IEC 61010-1 IEC 61010-1 VW3
U ≤ DC 60 V / AC 30 V
DC 60 V / AC 30 V ≤ U ≤ 3.8 kVeff 5 s
DC 286 V / AC 253 V
(DC 220 V + 30 % / AC 230 V +
10 %)
Surge 1.2/50 µs, common 5.0 kVp IEC 60255-27 IEC 60870-2-1 VW3
Surge 1.2/50 µs, normal 5.0 kVp IEC 60255-27 IEC 60870-2-1 VW3

DC8-037-2, Edition 11.2020
Ambient Conditions

Voltage tolerance DC +30/-25 % – IEC 60870-2-1 DC3
IEC 60654-2 DC4
Voltage tolerance AC +10/-15 % – IEC 60870-2-1 AC2
IEC 60654-2 AC3
Harmonic content < 20 % IEC 60870-2-1 IEC 60870-2-1 >H2
IEC 60654-2
Starting current Class S1 IEC 60870-4 – –
Harmonic current – IEC 61000-3-2 IEC 60870-2-1 A=B
Fast transient burst, common 4.0 kVp 5 kHz IEC 61000-4-4 IEC 60870-2-1 4
Fast transient burst (fast repeti- 4.0 kVs 100 kHz IEC 61000-4-4 – –
tion)
Fast transient burst, common 4.0 kV IEEE C37.90.1 – –
Fast transient burst, transverse 4.0 kV IEEE C37.90.1 – –
Surge 1.2/50 µs, common 4.0 kVp IEC 61000-4-5 IEC 60870-2-1 4
Surge 1.2/50 µs, normal 4.0 kVp IEC 61000-4-5 IEC 60870-2-1 >4
Conducted disturbance (induced 10 V 0.15 to 80 MHz IEC 61000-4-6 IEC 60870-2-1 3
HF) 80 % AM 1 kHz
Voltage dips, short-time inter- Dips: (ΔVN) IEC 61000-4-11 IEC 60870-2-1 –
ruption and voltage fluctuations 20 % 5 s IEC 61850-3 Ed.2
on AC input connections
30 % 20 ms
30 % 500 ms
40 % 200 ms
60 % 200 ms
60 % 1 s
70 % 500 ms
Interruptions: (ΔVN)
100 % 10 ms
100 % 20 ms
100 % 50 ms
100 % 100 ms
100 % 1 s
100 % 5 s
Fluctuations: (ΔUN)
±8 % 5 s
Frequency fluctuations, AC 10 % IEC 61000-4-11 IEC 60870-2-1 >F3
Ring waves 100 kHz, common 2.0 kVp IEC 61000-4-12 IEC 60870-2-1 3
Ring waves 100 kHz, normal 2.0 kVp IEC 61000-4-12 IEC 60870-2-1 >3
Conducted, common mode 30 to 3 V IEC 61000-4-16 – –
disturbances (induced LF) 15 Hz to 150 kHz
30 V
16⅔/50/60 Hz 60 s
300 V
16⅔/50/60 Hz 1 s
Voltage ripple, DC 10 % VN IEC 61000-4-17 IEC 60870-2-1 >VR3
Damped oscillatory waves 2.5 kVp IEC 61000-4-18 IEC 60870-2-1 4
1 MHz, common

DC8-037-2, Edition 11.2020
Ambient Conditions

Damped oscillatory waves 2.5 kVp IEC 61000-4-18 IEC 60870-2-1 >4
1 MHz, normal
Damped oscillatory waves 2.5 kVp IEEE C37.90.1 – –
1 MHz, common
1 MHz, transverse
Voltage dip, short-time interrup- Dips: (∆VN) IEC 61000-4-29 IEC 60870-2-1
tion and voltage fluctuations at 30 % 100 ms IEC 61850-3 Ed.2
DC input connections 21
30 % 500 ms
60 % 100 ms
60 % 500 ms
Interruptions: (∆VN)
100 % 10 ms
100 % 50 ms
100 % 100 ms
100 % 500 ms
100 % 5 s
4.4.3 Digital I/Os

U ≤ DC 60 V / AC 30 V
DC 60 V / AC 30 V ≤ U ≤ 3.8 kVeff 5 s
DC 286 V / AC 253 V
(DC 220 V + 30 % / AC 230 V +
10 %)
Surge 1.2/50 µs, common 5.0 kVp IEC 60255-27 IEC 60870-2-1 VW3
Surge 1.2/50 µs, normal 5.0 kVp IEC 60255-27 IEC 60870-2-1 VW3
Fast transient burst, (fast repeti- 4.0 kVp 100 kHz IEC 61000-4-4 – –
tion)
Fast transient burst, common 4.0 kVp IEEE C37.90.1 – –
Fast transient burst, transverse 4.0 kVp IEEE C37.90.1 – –
Surge 1.2/50 µs, normal 4.0 kVp IEC 61000-4-5 IEC 60870-2-1 >4
Conducted disturbances 10 V 0.15 to 80 MHz IEC 61000-4-6 IEC 60870-2-1 3
(induced HF) 80 % AM 1 kHz
Ring waves 100 kHz, normal 2.0 kVp IEC 61000-4-12 IEC 60870-2-1 4
21 Criterion B applies to interruptions/fluctuations > 50 ms: Restart of the device allowed (CP-8000: > 100 ms)

DC8-037-2, Edition 11.2020
Ambient Conditions

30 V
16⅔//50/60 Hz 60 s
300 V
16⅔/50/60 Hz 1 s
Damped sinusoidal oscillatory 2.5 kVp IEC 61000-4-18 IEC 60870-2-1 4
waves 1 MHz, common
Damped oscillatory waves 2.5 kVp IEC 61000-4-18 IEC 60870-2-1 >4
1 MHz, normal
1 MHz, common
1 MHz, transverse
4.4.4 Analog I/Os

Dielectric test (50 Hz) 1.6 kVeff 60 s 1.8 IEC 61010-1 IEC 61010-1 >VW2
U ≤ DC 60 V / AC 30 V kVeff 5 s
Surge 1.2/50 µs, common 2.5 kVp IEC 60255-27 IEC 60870-2-1 >VW2
Surge 1.2/50 µs, normal 2.5 kVp IEC 60255-27 IEC 60870-2-1 >VW2
Fast transient burst, (fast repeti- 4.0 kVp 100 kHz IEC 61000-4-4 – –
tion)
Surge 1.2/50 µs, normal 2.0 kVp IEC 61000-4-5 IEC 60870-2-1 4
Conducted disturbances 10 V 0.15 to 80 MHz IEC 61000-4-6 – –
Conducted, common mode 30 to 3 V 22 IEC 61000-4-16 – –
30 V 23
16⅔/50/60 Hz 60 s
300 V 24
16⅔/50/60 Hz 1 s
1 MHz, common
22 AI-8310: Tested with 10 to 1 V

23 AI-8310: Tested with 10 V
24 AI-8310: Tested with 100 V

DC8-037-2, Edition 11.2020
Ambient Conditions

1 MHz, normal
1 MHz, common
4.4.5 Communication with Insulation: RS-485/RS-232

Dielectric test (50 Hz) 1.5 kVeff 60 s IEC 60255-27 IEC 60870-2-1 >VW2
U ≤ DC 60 V / AC 30 V
Fast transient burst, common 4.0 kVp 5 kHz 25 IEC 61000-4-4 IEC 60870-2-1 3
Fast transient burst, normal 4.0 kVp IEEE C37.90.1 – –
30 V
16⅔/50/60 Hz 60 s
300 V
16⅔/50/60 Hz 1 s
1 MHz, common
1 MHz, common
The listed values are valid for shielded cables.
4.4.6 Communication without Insulation: RS-232
The communication via RS-232 is designed only for distances ≤ 2.5 m. Therefore, this interface does not need
to show an immunity. The immunity and the galvanic insulation are assumed by the external data communi-
cations equipment.
You can find the electrical ambient conditions of data transmission equipment in the related data sheets.
25 CP-8000: Tested with 2.0 kVp

DC8-037-2, Edition 11.2020
Ambient Conditions
4.4.7 Communication with Insulation: LAN

Dielectric test (50 Hz) 1.5 kVeff 60 s IEC 60255-27 IEC 60870-2-1 >VW2
U ≤ DC 60 V / AC 30 V
Fast transient burst, common 4.0 kVp 5 kHz 26 IEC 61000-4-4 IEC 60870-2-1 3
Fast transient burst, normal 4.0 kVp IEEE C37.90.1 – –
Conducted, common mode 30 to 3 V IEC 61000-4-16 IEC 61850-3 Ed.2 –
30 V
16⅔/50/60 Hz 60 s
300 V
16⅔/50/60 Hz 1 s
1 MHz, common
1 MHz, common
The listed values apply to shielded Cat. 5 cables with a length of up to 100 m.
26 CP-8000: Tested with 2.0 kVp

DC8-037-2, Edition 11.2020
Ambient Conditions
4.5 Storage and Transport
4.5 Storage and Transport

Storage
Store the device in dry and clean rooms. The relative humidity must not lead to the formation of either
condensation water or ice.
For storage Siemens recommends that you maintain a limited temperature range of between +10°C and
+35°C, in order to prevent premature ageing of the electrolytic capacitors used.
For a longer storage period Siemens also recommends connecting the device to the supply voltage once a year
for 1 to 2 days, in order to form the electrolytic capacitors used. You should proceed likewise before a planned
use of the device.
Transport
The transport packaging of the devices can be re-used for forwarding. If other packaging is used the observ-
ance of the transport requirements according to ISO 2248 must be ensured. Storage packaging of the indi-
vidual devices is not adequate for transport.

DC8-037-2, Edition 11.2020
DC8-037-2, Edition 11.2020
5 System Components and Technical Data
5.1 Power Consumption of Total System 94

5.2 Master Modules 95
5.3 Power Supply Modules 108
5.4 SICAM I/O Modules 117
5.5 SICAM TM I/O Modules 208
5.6 MTBF Data 217

DC8-037-2, Edition 11.2020
System Components and Technical Data
5.1 Power Consumption of Total System
5.1 Power Consumption of Total System
5.1.1 Master Module without External Consumers
Designation MLFB Power consumption

CP-8000 Master Module with I/O -25 to +70°C 6MF21010AB100AA0 4.3 W 27
CP-8000 Master Module with I/O -40 to +70°C 6MF21011AB100AA0 4.3 W 27
CP-8021 Master Module -40 to +70°C 6MF28021AA00 1.6 W
CP-8022 Master Module with GPRS -40 to +70°C 6MF28022AA00 BB 12 W
6MF28022AA00 CC 6W
5.1.2 Master Module with External Consumers
If a Master Module is expanded with external consumers (modem, I/O Modules), their power consumption
must be added to that of the Master Module.
With the Power Supply Modules (with CP-8000 internal), it must be considered that due to the efficiency
factor (typical 80%; sub-zero temperature 77%) the power consumption values of the external consumers
must be corrected.
Table 5-1 Example: Power consumption CP-8000 with external consumer
Module Power consumption

DO-8212 0.8 W
Addition based on PS efficiency factor 0.2 W
CP-8000 4.3 W
CM-8830 0.5 W
Total 5.8 W
NOTE
i For the power consumption values of the external I/O Modules please refer to the sections 2.1.4.2 External
SICAM I/O Modules and 2.1.4.3 External SICAM TM I/O Modules.
For the values of the used modems see the documentation of the respective modem.
The Master Module CP-8000 provides an internal Power Supply Module, for the Master Modules CP-8021 and
CP-8022 different Power Supply Modules are available, depending on the power consumption of your system:
• PS-8620 Power Supply DC 24 to 60 V
• PS-8642 Power Supply DC or AC 100 to 240 V
Modules Available power for I/O Modules Available total power

PS-8630 (CP-8000) 5W
PS-8620, PS-8622 7W 12 W
PS-8640, PS-8642 8W 45 W
27 including internal periphery

DC8-037-2, Edition 11.2020
5.2 Master Modules
5.2 Master Modules
5.2.1 CP-8000
In addition to the Master Module, CP-8000 also includes the Power Supply Module as well as 2 I/O Modules.
[dw_CP-8000_compact_architecture, 1, en_US]
Figure 5-1 CP-8000 - Compact Architecture

DC8-037-2, Edition 11.2020
5.2 Master Modules
5.2.1.1 Position of the Interfaces

The communication and process interfaces are positioned on the CP-8000 Master Module according to their
use:
[dw_CP-8000_interfaces, 1, en_US]
Figure 5-2 CP-8000 - Position of the Interfaces

DC8-037-2, Edition 11.2020
5.2 Master Modules
5.2.1.2 Technical Data
Processor and Memory
Processor Blackfin BF536

Clock pulse frequency Core clock: approx. 400 MHz
System clock: approx. 133 MHz
Accuracy clock pulse ±3.5 ppm (-40 °C to +80 °C), ± 2 ppm (0 °C to 40 °C)
Internal real-time clock and • Buffered maintenance-free (72 h)
external synchronization
• Automatic daylight-saving time/normal time change
• (S)NTP time server
Free run accuracy 12.6 ms/h
Program memory Flash-PROM 16 MB
Main memory SDRAM 32 MB
Local non-volatile memory FRAM 8 KB
Changeable non-volatile memory SD card up to 2 GB
Max. number of data points 20000 (sum of process images across all 4 interfaces)
Memory for application program 128 KB, 4 KB of which temporary memory for variables
Number of variables for application 512 variables possible, 256 bytes of which are non-volatile (variables:
program BOOL = 1 bit, DINT = 4 bytes, REAL = 4 bytes)
Program sampling • Cyclical 10 to 2000 ms (settable grid 1 ms)
• Spontaneous (settable; run not based on interrupt)
Acquisition grid for digital I/O 10 ms
Decentralized archive Input grid for measured values 1, 2, 3, 5, 10, 15, 30, 60 min, settable
Max. message length of a segment 1 to 200 bytes, settable
Memory configuration, settable
10 files, 1000 records each (= 10000 records)

DC8-037-2, Edition 11.2020
5.2 Master Modules
Communication
2 Ethernet/LAN interfaces (X1, X4) • Ethernet according to IEEE 802.3 (10Base-T or 100Base-TX)
• Galvanically insolated
• Transmission rate 10 Mbit/s or 100 Mbit/s
• Half duplex or full duplex
• Auto-MDI(X)
• Time synchronization via NTP server
• Line lengths up to 100 m
• Rated impulse voltage 2 kV
1 serial interface (X2) • Unbalanced dual-current interchange circuit RS-232, V.24/V.28
• Galvanically not insulated
• ESD protection
• Transmission rate up to 115.2 kbit/s (depending on protocol)
• Line length up to 2.5 m
1 serial interface (X3) • Balanced dual-current interchange circuit RS-422/RS-485
• Galvanically insulated
• ESD protection
• Configuration 4-wire/2-wire with/without terminating resistor
(parameter-settable)
Power Supply
Operating voltage Input DC 5.2 V 1.5 W

Internal operating voltages Logic DC 3.3/2.5/1.2 V
LCD DC 12 V
Optional power supply for external • De-energized (for modem reset)
modem via X2 28 • DC 5.2 V ± 5 % 2.5 W
• DC 12 V ± 5 % 2.5 W
Mechanics and Connections
Ethernet/LAN (X1, X4) RJ45 socket connector 8-pole (IEC 60603-7)

Serial RS-232 (X2) D-sub 9-pole, male (DIN 41652)
Serial RS-485 (X3) Removable screw terminal, 6-pole, with shield interception
28 For specific transmission facilities only

DC8-037-2, Edition 11.2020
5.2 Master Modules
Connection data X3 Locking torque 0.5 Nm

AWG min. 22
max. 12
Conductor cross section, solid min. 0.2 mm²
max. 2.5 mm²
Conductor cross section, stranded min. 0.2 mm²
max. 2.5 mm²
Conductor cross section, stranded with ferrule min. 0.25 mm²
without plastic sleeve max. 2.5 mm²
with plastic sleeve max. 2.5 mm²
2 wires stranded with ferrule without plastic min. 0.25 mm²
sleeve max. 1 mm²
2 wires stranded with ferrule with plastic sleeve min. 0.5 mm²
max. 1.31 mm²
Wire strip length min. 6 mm
max. 7 mm
Length ferrule 10 mm
Dimensions (L x W x H) 124 x 128 x 123 mm (dimensions without DIN rail)
Weight Approx. 800 g
5.2.1.3 Pin Assignment
Connector X1, X4: Ethernet
Pin Signal Meaning

1 TXD+ Transmit Data
2 TXD- Transmit Data
3 RXD+ Receive Data
4 n. c. not connected
6 RXD- Receive Data
Connector X2: RS-232
Pin Signal Meaning

1 DCD (I) Data Carrier Detect (Input)
2 RXD (I) Receive Data (Input)
3 TXD (O) Transmit Data (Output)
4 DTR (O) Data Terminal Ready (Output) (selectable as
voltage output 5 V or 12 V)
5 GND Ground
6 DSR (I) Data Set Ready (Input)
7 RTS (O) Request To Send (Output)
8 CTS (I) Clear to Send (Input)

DC8-037-2, Edition 11.2020
5.2 Master Modules
Connector X3: RS-485 (2-wire)
Pin Signal Meaning

1 shield
4 TXD-/RXD- Transmit Data/Receive Data
5 TXD+/RXD+ Transmit Data/Receive Data
6 GND Ground
Connector X3: RS-422 (4-wire)
Pin Signal Meaning

1 shield
2 RXD- Receive Data
3 RXD+ Receive Data
6 GND Ground
NOTE
i In case of using the RS-485 interface (X3) it is necessary to clamp the shield of the communication cable to
the DIN rail. This shield clamping should be done close to the system.
NOTE
i The assignment of X3 is independent whether a termination is existing or not (termination = resistance

that is connected through parameter in the firmware).

DC8-037-2, Edition 11.2020
5.2 Master Modules
5.2.1.4 Block Diagram and External Circuitry
[dw_CP-8000_block_diagram_ext_circuitry, 1, en_US]
Figure 5-3 CP-8000 - Block Diagram
NOTE
i X1 and X4 are alternatively 1 Ethernet interface (duplicated via an internal switch) or 2 independent
Ethernet interfaces.
5.2.2 CP-8021 and CP-8022
Processor and Memory
Processor Blackfin BF536

Clock pulse frequency Core clock: approx. 400 MHz
System clock: approx. 133 MHz
Clock pulse accuracy ±3.5 ppm (-40 °C to +80 °C), ± 2 ppm (0 °C to 40 °C)
Internal real-time clock and • Buffered maintenance-free (72 h)
external synchronization
• Automatic daylight-saving time/normal time change
• (S)NTP time server

DC8-037-2, Edition 11.2020
5.2 Master Modules
Free run accurcy 12.6 ms/h

Program memory Flash-PROM 16 MB
RAM SDRAM 32 MB
Local non-volatile memory FRAM 8 KB
Changeable non-volatile memory • SD card up to 2 GB
• Standard SIM card (mini SIM) for GPRS communication 29
Max. number of data points 20000 (sum of process images across all 4 interfaces)
Memory for application program 128 KB, 4 KB of which temporary memory for variables
Number of variables for application 512 variables possible, 256 bytes of which are non-volatile (variables:
program BOOL = 1 bit, DINT = 4 bytes, REAL = 4 bytes)
Program sampling • Cyclical 10 to 2000 ms (settable grid 1 ms)
• Spontaneous (settable; run not based on interrupt)
Acquisition grid for digital I/O 10 ms
Decentralized archive Recording grid for measured values 1, 2, 3, 5, 10, 15, 30, 60 min,
settable
Max. message length of a segment 1 to 200 bytes, settable
Memory configuration, settable
Communication
2 Ethernet/LAN interfaces (X1, X4) • Ethernet according to IEEE 802.3 (10Base-T or 100Base-TX)
• Data rate 10 Mbit/s or 100 Mbit/s
• Half duplex or full duplex
• Auto-MDI(X)
• Time synchronization via NTP server
• Line lengths up to 100 m
1 serial interface (X2) • Unbalanced interchange circuit RS-232, V.24/V.28
• Galvanically not insulated
• ESD protection
29 CP-8022 only

DC8-037-2, Edition 11.2020
5.2 Master Modules
1 serial interface (X3) • Balanced interchange circuit RS-422/RS-485

• ESD protection
• Configuration for 4-wire/2-wire with/without terminating resistor
(parameter settable)
1 serial interface (X6) 30 RS-232 mode:
• Unbalanced interchange circuit RS-232, V.28

• ESD protection
RS-485 mode:
• Balanced interchange circuit RS-422/RS-485

• ESD protection
• Configuration for 4-wire/2-wire with/without terminating resistor
(parameter settable)
1 radio interface (X7) 31 GPRS
• Quadband EGSM 850/900/1800/1900 MHz

• GPRS modem (2G radio standard), class 10 (as of production level
CC) 32
• Coding scheme 1 to 4
• Downlink up to 80 kBit/s (production level BB: 60 kBit/s)
• Uplink up to 40 kBit/s (production level BB: 20 kBit/s)
• Maximum transmitted RF power:
– 2 W (33 dBm) for GSM 850 and GSM 900
– 1 W (30 dBm) for GSM 1800 and GSM 1900
• Permissible antenna gain:
– GSM 850 MHz ≤ 6 dBi
– GSM 900 MHz ≤ 6 dBi
– GSM 1800 MHz ≤ 2.25 dBi
– GSM 1900 MHz ≤ 2.25 dBi
• ESD protection
• Licensing RED 2014/53/EU
30 CP-8022 only
31 CP-8022 only
32 for production level BB applies class 4

DC8-037-2, Edition 11.2020
5.2 Master Modules
Power Supply
Operating voltage Input DC 5 V:

DC 4.75 to 5.5 V; 1.5 W
Input DC 28 V:
DC 25.2 to 30.8 V 3.5 W (CP-8021); 5.5 W (CP-8022)
Internal operating voltages Logic DC 3.3/2.5/1.2 V
modem via X2 33 • DC 5.2 V ± 5 % 2.5 W
(CP-8021; CP-8022 with deacti-
• DC 12 V ± 5 % 2.5 W
vated internal GPRS modem 34)
modem via X2 35 • DC 5.2 V ± 5 % 0.75 W
(CP-8022 with activated internal
GPRS modem) 36
Mechanics and Connections
Ethernet/LAN (X1, X4) RJ45 socket 8-pole (IEC 60603-7)

Serial RS-232 (X2) RJ45 socket 8-pole (IEC 60603-7)
Serial RS-485 (X3) Push-in terminal, 8-pole (no shield interception)
Serial RS-232/RS-485 (X6) 37 Push-in terminal, 8-pole (no shield interception)
GPRS (X7) 38 SMA plug
X3, X6 connection data Locking torque 0.5 Nm
AWG min. 24
max. 16
max. 1.31 mm²
max. 1.31 mm²
Conductor cross section, stranded with ferrule with min. 0.21 mm²
plastic sleeve max. 0.75 mm²
2 wires stranded with ferrule without plastic sleeve min. 0.21 mm²
max. 0.51 mm²
2 wires stranded with ferrule with plastic sleeve min. 0.21 mm²
max. 0.51 mm²
max. 10 mm
Dimensions (L x W x H) 132 x 30 x 142 mm (dimensions without DIN rail)
Weight Approx. 210 g (CP-8021), approx. 260 g (CP-8022)
33 for specific transmission facilities only

34 as of production level CC
35 for specific transmission facilities only
36 as of production level CC
37 CP-8022 only
38 CP-8022 only

DC8-037-2, Edition 11.2020
5.2 Master Modules
Connector X1, X4: Ethernet
Pin Signal Meaning

3 RXD+ Receive Data
6 RXD- Receive Data
Pin Signal Meaning

3 VCC (O) Voltage Output (auswählbar 5 V or 12 V)
6 GND Ground
8 DTR (O) Data Terminal Ready (Output)
NOTE
i CP-8022 up to production level BB does not support VCC (O)!

CP-8022 as of production level CC supports VCC (O) (selectable 5 V or 12 V; 12 V is only possible if the
internal GPRS modem is not used).
Connector X3, X6: RS-485 (2-wire)
Pin Signal Meaning

1 TXD-/RXD- Transmit Data/Receive Data
2 TXD+/RXD+ Transmit Data/Receive Data
6 GND Ground
Connector X3, X6: RS-422 (4-wire)
Pin Signal Meaning


DC8-037-2, Edition 11.2020
5.2 Master Modules
Pin Signal Meaning

6 GND Ground
7 RXD- Receive Data
8 RXD+ Receive Data
Pin Signal Meaning

4 DTR (O) Data Terminal Ready (Output)
6 GND Ground
Pins on Connector X3 and X6
[dw_CP-802x_x3_x6_pins, 1, --_--]
Figure 5-4 CP-8021/CP-8022 - Pins on X3 and X6

DC8-037-2, Edition 11.2020
5.2 Master Modules
[dw_CP-802x_block_diagram_ext_circuitry, 1, en_US]
Figure 5-5 CP-8021/CP-8022 - Block Diagram
NOTE
i X1 and X4 are alternatively 1 Ethernet interface (duplicated via an internal switch) or 2 independent

DC8-037-2, Edition 11.2020
5.3 Power Supply Modules
5.3.1 PS-8630 (Internal to CP-8000)
Voltage Input
Input voltage DC 24 to 60 V +15 %/-25 % 39, +30 %/-25 % 40

Input power 34 W
Protection type Double insulation
Rated impulse voltage 4 kV
Voltage Outputs
Output voltage 1 (internal) DC 5.2 V ±3 %

Output voltage 2 (internal) DC 12 V ±30/-5 %
Output voltage 3 (external I/O DC 5.2 V ±3 % (not short-circuit proof and not overload proof)
Modules)
Output voltage for contact wetting Equals input voltage, 3x each 100 mA
protective mechanism is a self resetting fuse (PTC) 41
Output power 1 2.5 W
Output power 2 3W
Output power 3 5W
Guaranteed interruption time 100 ms
39 caused by the connection between input voltage and AUXV0 the input voltage must be < DC 70 V
40 the reliable function of the power supply is guaranteed up to DC 78 V
41 operation voltage: DC 60 V max., switching capacity: < 40 A; ohmic resistance: < 5Ω; permanent floating current after activation of
the fuse: < 1.3 A

DC8-037-2, Edition 11.2020
Connections and Mechanics
Connections Removable screw terminals for direct conductor assembly

Connection data X12, X13 Locking torque 0.5 Nm
AWG min. 22
max. 12
Conductor cross section solid min. 0.2 mm2
max. 2.5 mm2
Conductor cross section stranded min. 0.2 mm2
max. 2.5 mm2
Conductor cross section stranded with ferrule min. 0.25 mm2
without plastic sleeve max. 2.5 mm2
with plastic sleeve max. 2.5 mm2
2 wires stranded with ferrule without plastic min. 0.25 mm2
sleeve max. 1 mm2
2 wires stranded with TWIN ferrule with plastic min. 0.5 mm2
sleeve max. 1.31 mm2
max. 7 mm
Connector X12: Power supply
Pin Signal Meaning

3 BAT+ Input Voltage DC 24 to 60 V
4 BAT- Input Voltage
Connector X13: Contact interrogation
Pin Signal Meaning

1 AUX V0+ Voltage distribution
4 AUX V0- Voltage distribution
5 AUX V0- Voltage distribution
NOTE
i The interfaces X11 and X14 are not connected.

DC8-037-2, Edition 11.2020
[dw_PS-8630_block_diagram_ext_circuitry, 1, en_US]
Figure 5-6 PS-8630 - Block Diagram and External Circuitry
5.3.2 PS-8620, PS-8622
External power supply modules for
• CP-8021
• CP-8022 (as of production level CC)

DC8-037-2, Edition 11.2020
Figure 5-7 PS-8620 Figure 5-8 PS-8622
Voltage input
(The voltage is supplied via the PS-8620 PS-8622

terminal X1)
Input voltage DC 24 to 60 V DC 110 to 220 V
Operating voltage DC 18 to 70 V (78 V 42) DC 82.5 to 253 V (286 V 42)
Input current 0.8 A at DC 24 V 0.16 A at DC 110 V
0.4 A at DC 48 V 0.08 A at DC 220 V
0.3 A at DC 60 V
Reverse voltage protection yes
Overload protection yes
Short-Circuit Protection yes
Can be connected in parallel yes (for redundancy, not for power enhancement) 42
Inrush peak current Specified acc. to IEC 60870-4 (90) class S1
Voltage outputs
Output nominal voltage 1 DC 5.15 V ±2% static, ±3% dynamic

Output nominal current 1 0 to 1.8 A
Output nominal voltage 2 DC 28 V ± 10% static, ± 3% dynamic 43
Output power 1 (Pout 1) 9W
Output power 2 (Pout 2) 12 W - Pout 1 (12 W if Pout 1 = 0 W)
Total output power 12 W
42 from production state CC

43 for the generation of auxiliary voltage for specific transmission facilities

DC8-037-2, Edition 11.2020

Startup time <2s
Sustained short-circuit proof yes
Mechanics and Connectors
Connectors Removable screw terminals, 4-pole (grid size 5.08)

Connection data X1 Locking torque (PHOENIX terminal) 44 0.5 Nm to 0.6 Nm
Locking torque (FCI terminal) 44 0.36 Nm to 0.44 Nm
AWG min. 22
max. 12
max. 2.5 mm2
max. 2.5 mm2
sleeve max. 1 mm2
max. 7 mm
Rated impulse voltage 4.0 kV
Dimension (L x W x H) 124 x 30 x 132 mm (measure without DIN rail)
Weight Approx. 240 g (inkl. bus module 12 g)
Connector X1: Power Supply
Pin Signal Meaning

1 L/+ Input voltage
PS-8620: DC 24 to 60 V
PS-8622: DC 110 to 220 V
2 DNC do not connect
4 N/– Input voltage
44 the respective manufacturer is imprinted at the terminal (see section6.1.3.2 Screw Terminal Types)

DC8-037-2, Edition 11.2020
[dw_PS-862x_block_diagram_ext_circuitry, 2, en_US]
Figure 5-9 PS-8620/PS-8622 – Block Diagram and External Circuitry
NOTE
i The function of the RY LED is described in section 11.3.3 Power Supply Modules.
5.3.3 PS-8640, PS-8642
External power supply modules for
• CP-8021
• CP-8022

DC8-037-2, Edition 11.2020
Figure 5-10 PS-8640 Figure 5-11 PS-8642
Voltage input
(The voltage is supplied via the PS-8640 PS-8642

terminal X1)
Input voltage DC 24 to 60 V DC 100 to 240 V AC 100 to 240 V
Operating voltage DC 18 to 78 V DC 82.5 to 286 V AC 85 to 264 V
(45 to 66 Hz)
Input current 3.05 A at DC 18 V 0.68 A at DC 82.5 V 0.66 A at AC 85 V
2.20 A at DC 24 V 0.55 A at DC 100 V 0.56 A at AC 100 V
Power Consumption 55 W at DC 18 V 55.5 W at DC 82.5 V 55.2 W at AC 85 V
52.9 W at DC 48 V 55.1 W at DC 220 V 55.0 W at AC 100 V
52.5 W at DC 78 V 55.3 W at DC 286 V 54.8 W at AC 264 V
Reverse voltage protection yes
Overload protection yes
Short-Circuit Protection yes
Can be connected in parallel Yes (for redundancy, not to increase power)
Inrush peak current Specified acc. to IEC 60870-4 (90) class S1
Voltage outputs
Output nominal voltage 1 DC 5.15 V ±2% static, ±3% dynamic

Output nominal current 1 0 to 2 A
Output nominal voltage 2 DC 28 V ± 10% static, ± 3% dynamic 45
45 for the generation of auxiliary voltage for specific transmission facilities

DC8-037-2, Edition 11.2020
Output nominal voltage 3 DC 24 V +0%/-15% 46

Output nominal current 3 0.42A 46
Output power 1 (Pout 1) 10 W
Output power 2 (Pout 2) 45 W - Pout 1- PAUX (45 W if Pout 1/AUX= 0 W)
Output power 3 (PAUX) 10 W (30 W peak) 46
Total output power 45 W
Startup time <2s
Sustained short-circuit proof yes
Connectors Removable screw terminals, 4-pole (grid size 5.08)

Connection data X1, X2 Locking torque (PHOENIX terminal) 47 0.5 Nm to 0.6 Nm
AWG min. 22
max. 12
max. 2.5 mm2
max. 2.5 mm2
sleeve max. 1 mm2
max. 7 mm
Dimension (L x W x H) 124 x 30 x 132 mm (measure without DIN rail)
Weight Approx. 400 g (inkl. bus module 12 g)
Connector X1: Power Supply
Pin Signal Meaning

1 L/+ Input voltage
PS-8640: DC 100 to 240 V
PS-8642: DC 100 to 240 V, AC 100 to 240 V
46 applies only for PS-8642


DC8-037-2, Edition 11.2020
Pin Signal Meaning

4 N/– Input voltage
Connector X2: Contact Query
Pin Signal Meaning

1 AUXV0+ Contact query/modem supply
2 AUXV0+ Contact query/modem supply
3 AUXV0– Contact query/modem supply
4 AUXV0– Contact query/odem supply
[dw_PS-864x_block_diagram_ext_circuitry, 2, en_US]
Figure 5-12 PS-8640/PS-8642 – Block Diagram and External Circuitry
NOTE
i The function of the RY LED is described in section 11.3.3 Power Supply Modules.

DC8-037-2, Edition 11.2020
5.4 SICAM I/O Modules
NOTE
i The functions and the belonging mode of action are described in detail in the manual SICAM RTUs Common
Functions Peripheral Elements according to IEC 60870-5-101/104.
In the following listing, footnotes are used to specify the effect of the functions in detail.
f = Telecontrol
The function affects process information which is spontaneously transmitted
f1 = Telecontrol
The function delivers (acquisition) spontaneously transmitted process information or is controlled by such
information (output); partly, periodically transmitted information is also created/required
a = Automation
The function affects process information which is periodically transmitted
b = Calculation
The function affects process information which is used as input for the calculation of calculated (derived)
values
5.4.1 DI-8100 (Internal to CP-8000)
5.4.1.1 Features
Digital input module
• Integrated in CP-8000
• 12 inputs (1 group with 8, 1 group with 4)
• Galvanical insulated via optocouplers
• Each group has a common return
• Nominal voltages DC 24 to 60 V
• Removable screw terminals
5.4.1.2 Functions
Single-point Information
• Acquisition with a resolution of 1 ms f
• Update every 10 ms a (in the cycle of the open-/closed-loop control function, if larger)
• Revision fa
• Power monitoring fa
• Inversion fa
• Firmware filter f
• Bounce suppression f
• Determination of the cause of transmissionf
• Spontaneous transmission of changes f
• Periodical transmissiona

DC8-037-2, Edition 11.2020
Double-point Information
• Revision fa
• Inversion fa
• Monitoring intermediate and faulty positions f
• Determination of the cause of transmission f
• Reporting switching operations in progress f
• Breaker tripping detection f
• Breaker tripping suppression during auto-reclose f
• Periodical transmission a
Integrated Totals via Count Pulsesf1
• Acquisition by firmware with a maximum count frequency of 20 Hz

– Pulse length/pause >2 ms/>2 ms
– Revision
– Power monitoring
– Inversion
– Pulse counting
• Counter value formation

– Count pulse evaluation
– Set counter
• Formation of integrated totals

– Counter request
– Interval control
– Frozen absolute value
– Frozen relative value
• Not power-fail safe
• Integrated total transmission according to IEC 60870-5-101/104
• Spontaneous transmission

DC8-037-2, Edition 11.2020
Digital Inputs
12 digital inputs • 2 groups (with 8 and with 4 inputs)

• Via optocouplers the inputs are galvanically insulated from logical
circuits and ground with double insulation
• Each group is galvanically insulated from the other group, from
logical circuits and from ground with double insulation
• For each group one common return with selectable polarity
• Function and status of the inputs via display
Filter time 1 dedicated input per group: 2 ms
All other inputs: 3 ms
Nominal voltages DC 24/48/60 V
Operating points Logical 0: ≤12 V
Logical 1: ≥18 V
Dynamic suppression of noise typ. 220 nF (for DC 18 to 78 V)
caused by cable capacitance
Rated current 0.6 to 1.5 mA (at DC 18 to 78 V)
Input circuits DC 18 to 78 V (operated by means of an external voltage)
Connectors
Terminals Removable screw terminals (grid size 5.08)

Connection data X31, X32 Locking torque 0.5 Nm
AWG min. 22
max. 12
Conductor cross section solid min. 0.2 mm²
max. 2.5 mm²
Conductor cross section stranded min. 0.2 mm²
max. 2.5 mm²
Conductor cross section stranded with ferrule min. 0.25 mm²
sleeve max. 1 mm²
2 wires stranded with TWIN ferrule with plastic min. 0.5 mm²
sleeve max. 1.31 mm²
max. 7 mm

The process signals must be connected to a 9-pin and to a 5-pin screw terminal. The peripheral connectors are
assigned according to the tables.

DC8-037-2, Edition 11.2020
Connector X31
Pin Signal Meaning

9 COM IN D00 Common supply of group 0
8 IN D07 Digitaler input 7 of group 0
Connector X32
Pin Signal Meaning

5 COM IN D10 Common supply of group 1
NOTE
i The interface X33 is not connected.

DC8-037-2, Edition 11.2020

The following circuitry variants are examples, and do not relate exclusively to the depicted inputs/outputs.
[dw_DI-8100_block_diagram_ext_circuitry, 1, en_US]
Figure 5-13 DI-8100 - Block Diagram and External Circuitry

DC8-037-2, Edition 11.2020
5.4.2 DI-8110
[DI-8110_Oblique_View, 1, --_--]
Figure 5-14 DI-8110
5.4.2.1 Features
• Assembly on 35 mm DIN rail
• 16 inputs (2 groups, 8 inputs each)
• Galvanic insulation by optocouplers
• Signal voltage DC 24 V
• Function indication via LED
5.4.2.2 Functions
Single-point informations
• Revision fa
• Inversion fa

DC8-037-2, Edition 11.2020
• Spontaneous transmission upon change f
Double-point informations
• Revision fa
• Inversion fa
• Breaker tripping suppression during automatic reclosure f
Integrated Totals via Count Pulses f1

– Revision
– Inversion
– Pulse counting

– Set Counter
• Integrated total formation

– Counter request

DC8-037-2, Edition 11.2020
NOTE
i The above mentioned functions are described in detail in the document SICAM RTUs Common Functions
Peripheral Elements according to IEC 60870-5-101/104.
Digital Inputs
16 digital inputs • 2 groups with 8 inputs each

• Galvanical insulation
• For each group, one common return with selectable polarity
Filter time 3 ms
(if the sensor voltage of a group of digital inputs is monitored for failures
(Parameter SVM_monitoring), there is a dedicated binary input for each
group (IN D07 and IN D17), this input has a filter time of 2 ms)
Nominal voltage DC 24 V
Operating points ≤ 12 V (logical “0”)
≥ 18 V (logical “1”)
Input circuits DC 18 to DC 31.2 V
The circuits are operated by means of an external voltage.
Current consumption 0.9 to 4.8 mA at 18 to 31.2 V
Power Supply
Operating voltage DC 4.75 to DC 5.5 V

The voltage is picked off from the bus
Power consumption 130 mW

Rated impulse voltage 4 kV (category III / AC 230 V)

DC8-037-2, Edition 11.2020

AWG min. 22
max. 12
max. 2.5 mm²
max. 2.5 mm²
2 stranded conductors with ferrule without min. 0.33 mm²
plastic sleeve max. 1 mm²
2 stranded conductors with ferrule with plastic min. 0.5 mm²
max. 7 mm
Ferrule length 10 mm
Dimensions (L x W x H) 124 x 30 x 132 mm (L x W x H, dimensions without DIN rail)
Weight 249 g (incl. bus module 12 g)
5.4.2.4 Pin Assignment and Display

The process signals must be connected to two 10-pin screw terminals. The peripheral connectors are assigned
according to the tables.
[DI-8110_Front, 1, --_--]
Figure 5-15 DI-8110 Front
Connector X1
Pin Signal Meaning

10 COM00 common supply of group 0
48 the respective manufacturer is imprinted at the terminal (see section 6.1.3.2 Screw Terminal Types)

DC8-037-2, Edition 11.2020
Pin Signal Meaning

8 IN D07 digital input 7 of group 0
Connector X2
Pin Signal Meaning

10 COM10 common/supply of group 1
Display
LED Meaning
RY Readiness

DC8-037-2, Edition 11.2020

The following circuitry variant is an example, and does not relate exclusively to the depicted inputs/outputs.
[DI-811x_Block_Diagram_External_Circuitry, 1, en_US]
Figure 5-16 DI-811x block diagram and external circuitry variant

DC8-037-2, Edition 11.2020
5.4.3 DI-8111
Figure 5-17 DI-8111
5.4.3.1 Features
• Signal voltage DC 48/60 V
5.4.3.2 Functions
• Revision fa
• Inversion fa

DC8-037-2, Edition 11.2020
• Revision fa
• Inversion fa

– Revision
– Inversion
– Pulse counting

– Set Counter

– Counter request

DC8-037-2, Edition 11.2020
NOTE
Digital Inputs

Filter time 3 ms
Nominal voltage DC 48/60 V
≥ 36 V (logical “1”)
Input circuits DC 36 to DC 78 V
Current consumption 0.5 to 2.5 mA at 36 to 78 V
Power Supply



DC8-037-2, Edition 11.2020

AWG min. 22
max. 12
max. 2.5 mm²
max. 2.5 mm²
max. 7 mm

[DI-8111_Front, 1, --_--]
Connector X1
Pin Signal Meaning


DC8-037-2, Edition 11.2020
Pin Signal Meaning

Connector X2
Pin Signal Meaning

Display
LED Meaning
RY Readiness

DC8-037-2, Edition 11.2020


DC8-037-2, Edition 11.2020
5.4.4 DI-8112
Figure 5-20 DI-8112
5.4.4.1 Features
5.4.4.2 Functions
• Revision fa
• Inversion fa

DC8-037-2, Edition 11.2020
• Revision fa
• Inversion fa

– Revision
– Inversion
– Pulse counting

– Set Counter

– Counter request

DC8-037-2, Edition 11.2020
NOTE
Digital Inputs

Filter time 3 ms
≥ 82.5 V (logical “1”)
Input circuits DC 82.5 to DC 143 V
Current consumption 0.4 to 1.4 mA at 82.5 to 143 V
Power Supply



DC8-037-2, Edition 11.2020

AWG min. 22
max. 12
max. 2.5 mm²
max. 2.5 mm²
max. 7 mm
NOTE
i Above an ambient temperature of +65 °C (horizontal mounting) / +45 °C (vertical mounting) a derating
occurs. In this case, only a maximum of 13 inputs may be operated simultaneously.

The process signals must be connected to 2 pieces 10-pin screw terminals. The pin assignment of the periph-
eral connectors is described in the following table.
[DI-8112_Front, 1, --_--]

DC8-037-2, Edition 11.2020
Connector X1
Pin Signal Meaning

10 COM00 Common supply of group 0
8 IN D07 Digital input 7 of group 0
Connector X2
Pin Signal Meaning

Display
LED Meaning
RY Readiness

DC8-037-2, Edition 11.2020


DC8-037-2, Edition 11.2020
5.4.5 DI-8113
Figure 5-23 DI-8113
5.4.5.1 Features
5.4.5.2 Functions
• Revision fa
• Inversion fa

DC8-037-2, Edition 11.2020
• Revision fa
• Inversion fa

– Revision
– Inversion
– Pulse counting

– Set Counter

– Counter request

DC8-037-2, Edition 11.2020
NOTE
Digital Inputs

Filter time 3 ms
≥ 165 V (logical “1”)
Input circuits DC 165 to DC 253 V
Current consumption 0.3 to 0.7 mA at 165 to 253 V
Power Supply



DC8-037-2, Edition 11.2020

AWG min. 22
max. 12
max. 2.5 mm²
max. 2.5 mm²
max. 7 mm
NOTE
i Above an ambient temperature of +65 °C (horizontal mounting) / +45 C (vertical mounting) a derating
occurs. In this case, only a maximum of 13 inputs may be operated simultaneously.

The process signals must be connected to 2 pieces 10-pin screw terminals. The pin assignment of the periph-
eral connectors is described in the following table.
[DI-8113_Front, 1, --_--]

DC8-037-2, Edition 11.2020
Connector X1
Pin Signal Meaning

Connector X2
Pin Signal Meaning

Display
LED Meaning
RY Readiness

DC8-037-2, Edition 11.2020

5.4.6 DO-8203 (Internal to CP-8000)
5.4.6.1 Features
Digital output module
• Integrated in CP-8000
• 8 relay outputs (4 groups with 2 each)
• Switching voltage DC 24 to 220 V/AC 230 V
• The outputs can be used for switching of direct voltage or also alternating voltage
5.4.6.2 Functions
Pulse Commands f1
• Secured output of pulse commands

– 1 pole, 1½ pole, 2 pole
– Cannot be mixed

DC8-037-2, Edition 11.2020
• Single, double and regulating step commands
• Command output (OC)
• Application functions and procedures according to IEC 60870-5-101/104

– Formal check
– Direct command
– Select and execute command
• Retry suppression
• 1 out of n check
• Control location check
• Command locking
• Synchronization
• Revision
• Command output time

– Settable
– Dependent on the process
• Return information monitoring
• Command prolongation
• Switching sequences
• Command output for the auto-reclose function
• If outputs are used for pulse commands, no outputs can be used for binary information output
Binary Information
• Selectable behavior on communication failure fa (deactivation or retention)
• Deactivation on module failure fa
• Spontaneous transmission f or
• If outputs are used for binary information output, no outputs can be used for pulse commands
• Usage as watchdog realizable by means of application program (categories DO_EX and DO_DX must be
used)
Binary Information and Command Output
• Settable output of the categories DO_EX and DO_DX

– Mixed output of binary information items and commands on 1 DO module possible
– Output of pulse commands or persisting commands
NOTE
i The previously mentioned functions are described in detail in the document SICAM RTUs Common Func-
tions Peripheral Elements according to IEC 60870-5-101/104 (DC0-011-2).

DC8-037-2, Edition 11.2020
Digital outputs
8 digital outputs (relay) • 4 groups with 2 outputs each

• Each relay has a 1-pole normally-open contact
• The outputs are galvanically insulated from logic circuits and
ground by monostable relays with double insulation
• Each group is galvanically insulated from the other groups, logic
circuits and ground with double insulation
• Within the groups the outputs are galvanically insulated with
operational insulation (250 kV)
• The outputs can be used for switching of direct voltage or also
alternating voltage
• Function and status of the outputs via display
Nominal voltage DC 24/48/60/110/220 V
AC 110/230 V
Maximum continuous current Standard circuitry
• 8 outputs max. 2 A each (5 A/1 min)

Circuitry with derating at 5 A
• 1 output max. 5 A each

• 7 outputs max. 1 A each
or

• 6 outputs max. 0 A (relay must not be activated)
Circuitry with derating resp. for switching load 6 A 52

Switching capacity DC voltage
• min. 50 mW at DC 5 V
• max. acc. to diagram
AC voltage
• max. 1250 VA (5 A/AC 250 V), resistive load

• max. 500 VA (2 A/AC 250 V), cosϕ = 0.4
Switching cycles 3⋅104
Output circuits max. DC 250 V/AC 253 V (operated with an external voltage)
52 with parallel connection

DC8-037-2, Edition 11.2020
Connectors

Connection data X21, X22, X23, Locking torque 0.5 Nm
X24 AWG min. 22
max. 12
Conductor cross section solid min. 0.2 mm²
max. 2.5 mm²
Conductor cross section stranded min. 0.2 mm²
max. 2.5 mm²
sleeve max. 1 mm²
2 wires stranded with TWIN ferrule with plastic min. 0.5 mm²
max. 7 mm
• For power augmentation 2 relays may be connected parallel, this must happen within one group (applies
only for I < 6 A → 2 x 3 A)
• Groups with parallel connection must not be next to another
• Next to a group with parallel connection outputs may be loaded only with ≤ 2 A
• Outputs that are loaded with > 3 A must not be next to another
exception: with power augmentation the outputs of one group must be used
• Groups that are loaded with > 2 A must not be next to another
example: 3 A-3 A-1 A-1 A-3 A-3 A-1 A-1 A instead of 3 A-3 A-3 A-3 A-1 A-1 A-1 A-1 A

The process signals must be connected to 4 pieces 4-pin screw terminals. The peripheral connectors are
Connector X21
Pin Signal Meaning

4 COM OUT D01 Common supply output 1 of group 0
2 OUT D01 Digital output 1 of group 0
Connector X22
Pin Signal Meaning


DC8-037-2, Edition 11.2020
Connector X23
Pin Signal Meaning

Connector X24
Pin Signal Meaning


NOTE
i The module is monitoring autonomously the communication to the Master Module. With communication
failure (> 150 ms) the parameterized failure behavior (terminate or keep) becomes active.
Further information see section 11.4.3 Behavior of the Process Outputs upon Startup and Failure

DC8-037-2, Edition 11.2020
1 and 2 pole Circuitry
[dw_DO-8203_block_diagram_ext_circuitry_1_2_pole, 1, en_US]
Figure 5-26 DO-8203 - Block Diagram and External Circuitry (1- and 2-pole)

DC8-037-2, Edition 11.2020
1½ pole Circuitry
[dw_DO-8203_block_diagram_ext_circuitry_15_pole, 1, en_US]
Figure 5-27 DO-8203 - Block Diagram and External Circuitry (1,5-pole)

DC8-037-2, Edition 11.2020
5.4.7 DO-8212
[DO-8212_Oblique_View, 1, --_--]
Figure 5-28 DO-8212
5.4.7.1 Features
Digital output module
• 8 relay outputs (4 groups with 2 outputs each)
• Galvanic insulation
• Switching voltage DC 24 to 220 V / AC 230 V
• The outputs can switch DC and AC voltages
5.4.7.2 Functions
Pulse Commands f1
• Secured output of pulse commands

– 1-pole, 1½-pole, 2-pole
– Not mixable

– Formal check
– Direct command

DC8-037-2, Edition 11.2020
• 1-out-of-n check
• Command interlocking
• Synchronization
• Revision

– Settable
• Command output for auto-reclose function
• If module outputs are used for pulse commands, no outputs of the same module can be used for signal
outputs
Binary Information Items
• Selectable behavior in case of communication failure fa

(deactivation or retention)
• Deactivation upon module failure fa
• If module outputs are used for signal outputs, no outputs of the same module can be used for pulse
commands
• Use as a watchdog that can be realized with an application program (categories DO_EX and DO_DX must
be used)
NOTE
i The above-mentioned functions are described in detail in the document SICAM RTUs Common Functions
Peripheral Elements according to IEC 60870-5-101/104 (DC0-010-2).

DC8-037-2, Edition 11.2020
Digital Outputs
8 digital outputs (relay) • 4 groups, 2 outputs each

• Each relay has a 1-pole normally-open contact
• The outputs are galvanically insulated from logic circuits and ground
by monostable relays with reinforced insulation
• Each group is galvanically insulated from the other groups, from logic
circuits and ground with reinforced insulation
• Within the groups, the outputs are galvanically insulated with opera-
tional insulation (250 V)
• The outputs can be used for switching direct voltage, as well as alter-
nating voltage
• Display of function and state of outputs via engineering tool or LED
module
Nominal voltages • DC 24/48/60/110/220 V
• AC 110/230 V
Maximum continuous current Standard circuitry
• 8 outputs, each max. 3 A (5 A / 1 min)

Circuitry with derating at 5 A
• 2 outputs, each max. 5 A

or

• 4 outputs, each max. 0 A (relay must not be activated)
Power augmentation 53
• 4 outputs, each max. 6 A (max. DC 24 V +20%; max. AC 230 V +10%)

Switching capacity with DC • Min. 50 mW at DC 5 V
• Max. acc. to diagram
Switching capacity with AC • max. 1250 VA at 5 A (AC 250 V), resistive load
• max. 500 VA at 2 A (AC 250 V), cosφ = 0.4
Switching cycles 3 x 104
Output circuits max. DC 250 V/AC 253 V
UL/CUL DC 6 A/24 V
AC 6 A/253 V resistive
Pilot duty: R300, B300
53 with parallel connection

DC8-037-2, Edition 11.2020
Power Supply


4 kV
Rated impulse voltage
< 2000 m: category III
< 3000 m: category II 54
Connection data X1, X2, X3, X4 Locking torque (PHOENIX terminal) 55 0.5 Nm to 0.6 Nm
AWG min. 22
max. 12
max. 2.5 mm²
max. 2.5 mm²
max. 7 mm
NOTE
i • For power augmentation, 2 relays may be connected in parallel; this must happen within one group
(only applies for I < 6 A → 2 x 3 A).
• Siemens recommends that outputs that are more heavily loaded should not be adjacent to one
another. As a result, the stress on the device is distributed more evenly.
NOTE
i The altitude at which DO-8212 is operated shall be considered applicable for all modules in the system.
54 category III – ONLY when connecting identical external voltage levels for each load on each contact of the groups X1 & X2 and X3 &
X4 respectively

DC8-037-2, Edition 11.2020

The process signals must be connected to four 4-pin screw terminals. The peripheral connectors are assigned
[DO-8212_Front, 1, --_--]
Figure 5-29 DO-8212 Front
Connector X1
Pin Signal Meaning

4 COM D01 common supply of output 1 of group 0
2 OUT D01 digital output 1 of group 0
Connector X2
Pin Signal Meaning

Connector X3
Pin Signal Meaning

Connector X4
Pin Signal Meaning


DC8-037-2, Edition 11.2020
Display
LED Meaning
RY Readiness

1-Pole Circuitry
[dw_DO-8212_block_diagram_and_external_circuitry_1pole, 1, en_US]
Figure 5-30 DO-8212 Block Diagram and 1-Pole External Circuitry Variant

DC8-037-2, Edition 11.2020
1.5-Pole Circuitry
[dw_DO-8212_block_diagram_and_external_circuitry_1-5_pole, 1, en_US]
Figure 5-31 DO-8212 Block Diagram and 1.5-Pole External Circuitry Variant

DC8-037-2, Edition 11.2020
2-Pole Circuitry
[dw_DO-8212_block_diagram_and_external_circuitry_2pole, 2, en_US]
Figure 5-32 DO-8212 Block Diagram and 2-Pole External Circuitry Variant
NOTE
i Within a group of signal outputs, there is only basic insulation. Therefore, the use of different circuits is not
permitted.
The insulation between the groups is provided as reinforced insulation.

DC8-037-2, Edition 11.2020
5.4.8 AI-8310
[AI-8310_oblique_view_40x87, 1, --_--]
Figure 5-33 AI-8310
5.4.8.1 Features
Analog input module
• Acquisition of temperatures via Pt100/Pt1000/Ni100 resistance measurement in 2-wire, 3-wire, and 4-

wire technology
• Noise rejection
5.4.8.2 Functions
Temperatures
• Connection of the resistance thermometers: 2-, 3-, or 4-wire technique
• Update every 400 ms

DC8-037-2, Edition 11.2020
• Settable measuring ranges

– Temperature values
Input range
Pt100: -50 to +350 °C / -58 to +662 °F / (≈80.31 to 229.67 Ω)
Pt100: -100 to +700 °C / -148 to +1292 °F / (≈60.25 to 345.13 Ω)
Ni100: -60 to +250 °C / -76 to +482 °F / (≈69.5 to 289.2 Ω)
Pt1000: -100 to +700 °C / -148 to +1292 °F / (≈602.5 to 3451.3 Ω)
Resolution
Pt100: -50 to +350 °C 0.15°C / 0.28 °F / (10 mΩ)
Pt100: -100 to +700 °C 0.15°C / 0.28 °F / (10 mΩ)
Ni100: -60 to +250 °C 0.15°C / 0.28 °F / (10 mΩ)
Pt1000: -100 to +700 °C 0.15°C / 0.28 °F / (100 mΩ)
Response Time
16⅔ Hz < 1.2 s
50 Hz < 1.0 s
60 Hz < 0.9 s
– Resistance values
Input range
40 to 400 Ω, resolution: 10 mΩ
400 to 4000 Ω, resolution: 100 mΩ
Response Time
16⅔ Hz < 1.2 s
50 Hz < 1.0 s
60 Hz < 0.9 s
• Revision
• Noise rejection
• Calibration for 2-wire technique
• Smoothing
• Adaptation
– Temperature value (°C, °F) calculation via implemented curves
– Resistance value (Ω)
• Change monitoring
• Spontaneous transmission of changes
NOTE
Peripheral Elements according to IEC 60870-5-101/104, Chapter Temperatures.

DC8-037-2, Edition 11.2020
Analog Inputs
4 analog inputs • 2 groups, 2 inputs each

• Voltage between 2 inputs of a group max. DC 600 mV
Measuring ranges • 40 to 400 Ω (Pt100, Ni100)
• 400 to 4000 Ω (Pt1000)
Resolution 10 mΩ (Pt100, Ni100)
100 mΩ (Pt1000)
Noise rejection 16⅔ Hz, 50 Hz, 60 Hz
Conversion time Noise rejection for 50 Hz, 200 ms
Noise rejection for 60 Hz, 200 ms
Noise rejection for 16⅔ Hz, 500 ms
Accuracy 0.19 % at 0 to +50 °C
0.4 % at -40 to +70 °C
Reference current 250 μA
Lead resistance Sum of go-and-return line max. 300 Ω
Common-mode rejection 16⅔ Hz, 50 Hz, 60 Hz to 20 kHz > 100 dB
10 Hz to 1 MHz > 70 dB
Normal-mode rejection 16⅔ Hz > 106 dB
50 Hz > 98 dB
60 Hz > 91 dB
Input circuits The circuits are operated with internal voltage (constant current source)
Power Supply

Power consumption max. 500 mW


DC8-037-2, Edition 11.2020

AWG min. 22
max. 12
max. 2.5 mm²
max. 2.5 mm²
max. 7 mm

[AI-8310_Front_ohne_Gefahrensymbol, 1, --_--]
Figure 5-34 AI-8310 Front
Connector X1
Pin Signal Meaning

10 IREF1- analog current output 1 of group 0
9 IN V1- analog voltage input 1 of group 0

DC8-037-2, Edition 11.2020
Pin Signal Meaning

8 IN V1+ analog voltage input 1 of group 0
7 IREF1+ analog current output 1 of group 0
Connector X2
Pin Signal Meaning

Display
LED Meaning
RY Readiness

DC8-037-2, Edition 11.2020

[dw_AI-8310_Block_Diagram_External_Circuitry, 1, en_US]
Figure 5-35 AI-8310 Block Diagram and External Circuitry Variant

DC8-037-2, Edition 11.2020
5.4.9 AI-8320
[AI-8320_Oblique_View, 1, --_--]
Figure 5-36 AI-8320
5.4.9.1 Features
Analog input module
• 4 inputs (4 groups, 1 input each)
• Galvanically insulated via transformer
• Acquisition of currents ±20 mA
• Acquisition of voltages ±10 V
5.4.9.2 Functions
Currents and voltages
• Settable acquisition grid n ⋅ 100 ms f
• Measurement range settable with a resloution of f

– 16 bits (15 bits + sign) at full measurement range
– Shrinking the range results in decreasing resolution
• Revision f
• Noise rejection f
• Automatic calibration f
• Smoothing f

DC8-037-2, Edition 11.2020
• Adaptation f
– Linear (normalized, technologically scaled or short floating point)
– Zero-Range Suppression
– Plausibility check
• Change monitoring f
• Currents and voltages cannot be mixed on the same module
NOTE
Peripheral Elements according to IEC 60870-5-101/104, chapter Currents and chapter Voltages.
Analog Inputs
4 analog inputs • 4 groups, 1 input each

• Groups are galvanically insulated from one another
Measuring ranges Current measurement -20 to 0 to +20 mA
Voltage measurement -10 to 0 to +10 V
Overrange current ~20 %, voltage ~30 %
Resolution 0.004 % at ±20 mA
0.004 % at ±10 V
Accuracy 0.15 % at 25 °C
Accuracy current inputs 0.2 % at 0 to 50 °C
0.3 % at –20 to 70 °C
0.4 % at –40 to 70 °C
Accuracy voltage inputs 0.4 % at 0 to 50 °C
0.5 % at –20 to 70 °C
0.6 % at –40 to 70 °C
Input impedance 52 Ω at ±20 mA
10.5 kΩ at ±10 V
Common-mode rejection min. 90 dB (1 Hz to 1 MHz)
current inputs
Common-mode rejection min. 50 dB (1 Hz to 5 kHz)
voltage inputs min. 70 dB (5 kHz to 1 MHz)
Normal-mode rejection 0 dB (10 Hz to 500 Hz)
+30 dB/decade (500 Hz to 1 KHz)
+50 dB/decade (1 kHz to 10 kHz)
min. 70 dB (10 kHz to 1 MHz)
Noise rejection 50 dB (50 Hz, 60 Hz, 16⅔ Hz)
Power Supply


DC8-037-2, Edition 11.2020

AWG min. 22
max. 12
max. 2.5 mm²
max. 2.5 mm²
max. 7 mm

[AI-8320_Front, 1, --_--]

DC8-037-2, Edition 11.2020
Connector X1
Pin Signal Meaning

4 IN V0 U– analog voltage input of group 0 (–10 V)
3 IN V0 I– analog current input of group 0 (–20 mA)
2 IN V0 I+ analog current input of group 0 (+20 mA)
1 IN V0 U+ analog voltage input of group 0 (+10 V)
Connector X2
Pin Signal Meaning

Connector X3
Pin Signal Meaning

Connector X4
Pin Signal Meaning

Display
LED Meaning
RY Readiness

DC8-037-2, Edition 11.2020

[AI-8320_Block_Diagram_External_Circuitry, 1, en_US]
Figure 5-38 AI-8320 Block Diagram and External Circuitry Variants
(1) Connection of a 2-wire measuring transducer with current output

(2) Connection of a 4-wire measuring transducer with voltage output

DC8-037-2, Edition 11.2020
5.4.10 AI-8510
Figure 5-39 AI-8510
5.4.10.1 Features
Analog input module
• Assembly on DIN rail
• 3 low-power (LoPo) current measuring inputs in connection with adaptor module CM-8820
• 3 voltage measuring inputs (settable 100 V/√3, 240 V, or 415 V/√3)
• Frequency acquisition (nominal frequency 45 to 65 Hz)
• Calculation of RMS values for

– Currents
– Phase and phase-to-phase voltages
• Calculation of
– Frequency
– Active, reactive, and apparent power
– Zero-sequence voltage, zero-sequence current
– Power factor
– Phase angle
– Fault current direction, power direction
• Acquisition and processing according to IEC 60870-5-101/104

DC8-037-2, Edition 11.2020
5.4.10.2 Functions
Acquisition Functions
• Measuring currents
– Acquisition of currents through submodule CM-8820 using DFT algorithm, 1 signal sampling per
millisecond
– Nominal value 1 A/5 A with 16 bit resolution
• Measuring voltages
– Acquisition of voltages through transformers or direct measurement using DFT algorithm, 1 signal
sampling per millisecond
– Circuitry of the voltage inputs with phase-element voltages
– Nominal value 100 V/√3, 240 V, 415 V/√3 with 16 bit resolution
– Supervision of the measuring voltage
• Frequency
– Acquisition of frequency through zero crossing of voltage U1
– Measuring range 45 Hz to 65 Hz (settable nominal frequencies of 50 Hz and 60 Hz) with a resolution
of 100 mHz

DC8-037-2, Edition 11.2020
Calculation Functions
• Calculation of Values from Acquired Values

– Current RMS value I1 fb, I2 fb, I3 fb
– Phase-element voltage RMS value U1 fb, U2 fb, U3 fb
– Phase-to-phase voltage RMS value U12 fb, U23 fb, U31 fb
– Frequency fb
Voltage and current RMS values undergo a linear (technological) adaptation fb and are the basis for calcu-
lating further values:
– Zero-sequence current RMS value I0 f
– Zero-sequence voltage RMS value U0 f
– Active power P1 f, P2 f, P3 f
– Active power P (total value) f
– Reactive power Q1 f, Q2 f, Q3 f
– Reactive power Q (total value) f
– Apparent power S1 f, S2 f, S3 f
– Apparent power S (total value) f
– Power factor 1 f, 2 f, 3 f
– Power factor (total value) f
– Phase angle I1 f, I2 f, I3 f, IN f
– Phase angle U12 f, U23 f, U31 f
– Phase angle U1 f, U2 f, U3 f, U0 f
The following functions are applied to calculated values:
– Revision fb
– Format conversion f
– Normalized, technologically scaled, or short floating-point number
– Zero-range suppression
– Change monitoring f
– Fault detection
– Spontaneous transmission upon change f
NOTE
Peripheral Elements according to IEC 60870-5-101/104, chapter Measurement in 3-Phase Systems – I/O
Module.
Inputs for Measuring Currents (Only via Adaptor Module CM-8820)
Input voltage at IN AC 225 mV following IEC 60044-8

Max. input voltage AC 2.25 V

DC8-037-2, Edition 11.2020
Nominal frequency 50 Hz, 60 Hz (range 45 to 65 Hz)

Resolution 16 bit
Sampling 1 value/ms
Inputs for measuring voltages
Input voltage UN AC 100 V/√3, AC 240 V, AC 415 V/√3 acc. to IEC 60044-7 (settable)
Max. measuring voltage 150% UN (fault condition)
Rated voltage 300 V
Resolution 16 bit
Sampling 1 value/ms
Intrinsic consumption < 0.3 VA at UN = AC 240 V
< 0.02 VA at UN = AC 100 V/√3
Power Supply

Power consumption max. 800 mW (typ. 625 mW)
• 3 LoPo measuring currents, 10-pin (X1)

• 3 measuring voltages, 9-pin (X2)
4 kV (X2)
< 2000 m: measurement category III
< 3000 m: measurement category II
AWG min. 22
max. 12
max. 2.5 mm²
max. 2.5 mm²
max. 7 mm

DC8-037-2, Edition 11.2020

NOTE
i The altitude at which the AI-8510 is operated shall be considered applicable for all modules in the system.
Accuracy of Measured Values
Measured variable Dependency of accuracy class according to IEC 61557 12:2007-08 (K55)
Voltage U 1% (100/√3 up to 3%)
Phase current I 1% at nominal frequency
Active power P 3%
Reactive power Q 3%
Apparent power S 3%
Power factor 3%
Frequency f (49 to 51/59 to 61 1%
Hz)
Accuracy of Measured Ground Current with Isolated/Resonant Ground Connection
Measured variable Dependency of accuracy class according to IEC 61557 12:2007-08 (K55)
Ground current IN setting 0.4 to 1.9 A 2.0 to 2000 A
Measuring range 0.2 to 2.89 A @ 50 Hz 2.9 to 600 A @ 50 Hz
0.2 to 2.99 A @ 60 Hz 3.0 to 600 A @ 60 Hz
Accuracy ±0.19 A for measuring range 0.2 to ±0.19 A for measuring range
2.9 A 2.8 to 11.99 A
±1% for measuring range
12 to 600 A

The process signals must be connected to a 10-pin and a 9-pin screw terminal. The peripheral connectors are
[AI-8510_Front, 2, --_--]

DC8-037-2, Edition 11.2020
Connector X1
Pin Signal Meaning

8 I1+ measuring current input 1
7 I1- measuring current input 1
6 I2+/IN+ measuring current input 2 / (sensitive) zero-
sequence current
5 I2-/IN- measuring current input 2 / (sensitive) zero-
sequence current
1 FE shield functional earth
Connector X2
Pin Signal Meaning

9 CC shield capacitive coupled to protective conductor earth
7 U1 measuring voltage input 1
6 N measuring voltage input 1
Display
LED Meaning
RY Readiness

DC8-037-2, Edition 11.2020
5.4.10.5 Block Diagram
[AI-8510_Block_Diagram, 2, en_US]
Figure 5-41 AI-8510 Block Diagram
NOTE
i For the measurement of currents, the current transformer adaptor module CM-8820 must be connected via
the X1 terminal. The specification for the connection cable is in section 5.4.12.3 Technical Data.
! DANGER
² The connectors X1 and X2 may be detached or attached in a de-energized state only!
² The connector X1 must always be plugged during operation (even if no current measurement is used)!
! WARNING
² The inputs of connector X1 must not be directly connected with a mains supply circuit!
² The inputs of connector X2 may be directly connected with a mains supply current circuit up to AC
240/415 V. Higher voltages must be adapted via interconnected voltage transformers!

DC8-037-2, Edition 11.2020
NOTE
i Bear in mind the direction of the current flow when connecting the current measuring inputs. In the case of
inverse connection, the measured values are inverted and are given a negative sign.
The same applies to the voltage measurement (direction and rotation angle) respectively.
5.4.10.6 External Circuitry

The following circuitry variants are examples and do not relate exclusively to the depicted values.
! DANGER
Work may be performed on the circuitry in a de-energized state only!
² During electrical installation, all the rules and regulations governing power systems must be observed.
Short-Circuit Indicator
The current inputs I1, I2/IN, I3 are connected via the adaptor module CM-8820 with the measuring trans-
formers of the corresponding phase currents.
In this configuration, the module functions as a short-circuit indicator. Fault information on the direction is not
provided.
[dw_CM-8820_3xI, 1, en_US]

DC8-037-2, Edition 11.2020
[dw_AI-8510_3xI, 1, en_US]
Figure 5-42 AI-8510 External Circuitry Variant for Short-Circuit Indicator
NOTE
i With this connection scheme, the accuracy of ground current measurements for isolated/resonant ground
connections cannot be guaranteed.
Ground-Fault Indicator
The current input I2/IN is connected via the adaptor module CM-8820 with the sum current measuring trans-
former.
In this configuration, the module functions as a non-directional ground-fault indicator.
[dw_CM-8820_IN, 1, en_US]

DC8-037-2, Edition 11.2020
[dw_AI-8510_IN, 1, en_US]
Figure 5-43 AI-8510 External Circuitry Variant for Ground-Fault Indicator
Fault Detector
The current inputs I1, I2/IN, I3 are connected via the adaptor module CM-8820 with the corresponding meas-
uring transformers. Additionally, the voltage inputs U1, U2, U3 are connected:
• through voltage transformers with 100 V/√3 to the middle-voltage network
• through voltage transformers with 415 V/√3 to the low-voltage network
• directly with 240 V to the low-voltage network

In this configuration, fault information with directional indication is output. All the measured and calculated
measurands are thus also provided.
3-Phase Voltage, 3-Phase Current

Through the current inputs I1, I2/IN, I3, the corresponding phase currents are measured. The value IN is calcu-
lated.
This configuration is used for solidly grounded networks. In this configuration, the module also works as a
power meter.
Example: Middle-voltage network
[dw_CM-8820_3xI, 1, en_US]

DC8-037-2, Edition 11.2020
[dw_AI-8510_3xI_3xV_MV, 1, en_US]
Figure 5-44 AI-8510 External Circuitry Variant for 3-Phase Voltage, 3-Phase Current (MV)
Example: Low-voltage network
[dw_CM-8820_3xI, 1, en_US]

DC8-037-2, Edition 11.2020
[dw_AI-8510_3xI_3xV_LV, 1, en_US]
Figure 5-45 AI-8510 External Circuitry Variant for 3-Phase Voltage, 3-Phase Current (LV)
! WARNING
² Miniature circuit breakers are mandatory (2 A recommended).
3-Phase Voltage, 2-Phase Current + Sensitive Zero-Sequence Current

Through the current inputs I1 and I3, the corresponding phase currents are measured, and through the input
I2/IN, the sensitive zero-sequence current is measured. The value I2 is calculated.
This configuration is used for isolated and resonant grounded networks.

DC8-037-2, Edition 11.2020
[dw_CM-8820_2xI_IN, 1, en_US]
[dw_AI-8510_3xI_3xV_MV, 1, en_US]
Figure 5-46 AI-8510 External Circuitry Variant for 3-Phase Voltage, 2-Phase Current, Sensitive Zero-
Sequence Current
Medium Voltage/Low Voltage Measurement

The voltages in the middle-voltage network are determined by measuring the voltages from the low-voltage
network (secondary side of the transformer).
The voltage inputs U1, U2, U3 are directly connected to 240 V in the low-voltage network. The current inputs
I1, I2/IN, I3 are connected through the adaptor module CM-8820 with the corresponding measuring sensors in
the middle-voltage network.
In this configuration, the module determines the direction of the phase fault and ground fault.
These connection diagrams are used for solidly grounded networks.

DC8-037-2, Edition 11.2020
NOTE
i The module supports the Dy-11 transformer type only. For this type, the secondary side of the transformer
lags the primary side by a phase angle of 330°.
5.4.11 AI-8511
Figure 5-47 AI-8511
5.4.11.1 Features
Analog input module
• Assembly on DIN rail
• 3 low-power (LoPo) current measuring inputs (225 mV)
• 3 low-power (LoPo) voltage measuring inputs (3.25 V/√3)
• Frequency acquisition (nominal frequency 45 to 65 Hz)
• Calculation of RMS values for

– Currents
– Phase and phase-to-phase voltages
• Calculation of
– Frequency
– Active, reactive, and apparent power
– Zero-sequence voltage, zero-sequence current
– Power factor
– Phase angle
– Fault current direction, power direction

DC8-037-2, Edition 11.2020
• Acquisition and processing according to IEC 60870-5-101/104
5.4.11.2 Functions
– Acquisition of currents through low-power measuring sensors using DFT algorithm, 1 signal
– Nominal value 0 to 225 mV with 16 bit resolution
• Measuring voltages
– Acquisition of voltages through low-power voltage transformers using DFT algorithm, 1 signal
– Circuitry of the voltage inputs with phase-element voltages
– Nominal value 3.25 V/√3 with 16 bit resolution
– Supervision of measuring voltage
• Frequency
– Acquisition of frequency through zero crossing of voltage U1
– Measuring range 45 Hz to 65 Hz (settable nominal frequencies of 50 Hz and 60 Hz) with a resolution
of 100 mHz

DC8-037-2, Edition 11.2020
Calculation Functions
• Calculation of values from acquired values

– Current RMS value I1 fb, I2 fb, I3 fb
– Phase-element voltage RMS value U1 fb, U2 fb, U3 fb
– Phase-to-phase voltage RMS value U12 fb, U23 fb, U31 fb
– Frequency fb
Voltage and current RMS values undergo a linear (technological) adaptation fb and are the basis for calcu-
lating further values:
– Zero-sequence current RMS value I0 f
– Zero-sequence voltage RMS value U0 f
– Active power P1 f, P2 f, P3 f
– Active power P (total value) f
– Reactive power Q1 f, Q2 f, Q3 f
– Reactive power Q (total value) f
– Apparent power S1 f, S2 f, S3 f
– Apparent power S (total value) f
– Power factor 1 f, 2 f, 3 f
– Power factor (total value) f
– Phase angle I1 f, I2 f, I3 f, IN f
– Phase angle U12 f, U23 f, U31 f
– Phase angle U1 f, U2 f, U3 f, U0 f
The following functions are applied to calculated values:
– Revision fb
– Format conversion f
– Normalized, technologically scaled, or short floating-point number
– Zero-range suppression
– Change monitoring f
– Fault detection
– Spontaneous transmission upon change f
NOTE
Peripheral Elements according to IEC 60870-5-101/104, Chapter Measurement in 3-Phase Systems – I/O
Module.
Inputs for Measuring Currents
Input voltage at IN AC 225 mV according to IEC 60044-8

Max. input voltage AC 2.25 V

DC8-037-2, Edition 11.2020

Resolution 16 bit
Sampling 1 value/ms
Internal resistance 22 kΩ
Inputs for Measuring Voltages
Input voltage UN AC 3.25 V/√3 according to IEC 60044-7

Max. measuring voltage 150% UN
Resolution 16 bit
Sampling 1 value/ms
Internal resistance 200 kΩ
Power Supply

Power consumption max. 800 mW (typ. 625 mW)
• 3 LoPo measuring currents, 10-pin (X1)

• 3 LoPo measuring voltages, 9-pin (X2)
4 kV (X2)
< 2000 m: measurement category III
< 3000 m: measurement category II
AWG min. 22
max. 12
max. 2.5 mm²
max. 2.5 mm²
max. 7 mm

DC8-037-2, Edition 11.2020

Accuracy of Measured Values
Measured variable Dependency of accuracy class according to IEC 61557-12:2007-08 (K55)

Voltage U 1%
Phase current I 1% at nominal frequency
Active power P 3%
Reactive power Q 3%
Apparent power S 3%
Power factor 3%
Frequency f (49 to 51/59 to 1%
61 Hz)
Accuracy of the Measured Zero-Sequence Current with Isolated/Resonant Ground Connection
Measured variable Dependency of accuracy class according to IEC 61557-12:2007-08 (K55)

Ground current IN setting 0.4 to 1.9 A 2.0 to 2000 A
Measuring range 0.2 to 2.43 A @ 50/60 Hz 2.44 to 600 A @ 50/60 Hz
Accuracy ±0.1 A for measuring range 0.2 to ±0.18 A for measuring range
2.43 A 2.44 to 11.99 A
±1% for measuring range
12 to 600 A

The process signals must be connected to a 10-pin and a 9-pin screw terminal. The peripheral connectors are
[AI-8511_Front, 2, --_--]
Connector X1
Pin Signal Meaning


DC8-037-2, Edition 11.2020
Pin Signal Meaning

6 I2+/IN+ measuring current input 2 / (sensitive) zero-
sequence current
5 I2-/IN- measuring current input 2 / (sensitive) zero-
sequence current
Connector X2
Pin Signal Meaning

9 CC shield capacitive coupled to protective earth conductor
Display
LED Meaning
RY Readiness

DC8-037-2, Edition 11.2020
[AI-8511_Block_Diagram, 1, en_US]
Figure 5-49 AI-8511 block diagram
! DANGER
² The connectors X1 and X2 may be detached or attached in a de-energized state only!
! WARNING
² The inputs for the connectors X1 and X2 must not be connected directly with a mains supply circuit!
NOTE
i Bear in mind the direction of the current flow when connecting the current measuring inputs. In the case of
inverse connection, the measured values are inverted and are given a negative sign.
The same applies to the voltage measurement (direction and rotation angle) respectively.

The following circuitry variants are examples and do not relate exclusively to the depicted values.

DC8-037-2, Edition 11.2020
! DANGER
Work may be performed on the circuitry in a de-energized state only!
² During electrical installation, all the rules and regulations governing power systems must be observed.
Short-Circuit Indicator
The current inputs I1, I2/IN, I3 are connected with the LoPo measuring sensors of the corresponding phase
currents.
In this configuration, the module functions as a short-circuit indicator. Fault information on the direction is not
provided.
[dw_AI-8511_3xI, 1, en_US]
Figure 5-50 AI-8511 External Circuitry Variant for Short-Circuit Indicator
NOTE
i With this connection scheme, the accuracy of zero-sequence current measurements for isolated/resonant
ground connections cannot be guaranteed.

DC8-037-2, Edition 11.2020
Ground-Fault Indicator
The current input I2/IN is connected with the LoPo sum current measuring sensor.
In this configuration, the module functions as a non-directional ground-fault indicator.
[dw_AI-8511_IN, 1, en_US]
Figure 5-51 AI-8511 External Circuitry Variant for Ground-Fault Indicator
Fault Detector
The current inputs I1, I2/IN, I3 are connected to the corresponding LoPo measuring sensors. Additionally, the
voltage inputs U1, U2, U3 are connected through LoPo voltage transformers with 3.25 V/√3 to the middle-
voltage network.
In this configuration, fault information with directional indication is output. All the measured and calculated
measurands are thus also provided.
3-Phase Voltage, 3-Phase Current

Through the current inputs I1, I2/IN, I3, the corresponding phase currents are measured. The value IN is calcu-
lated. This configuration is used for solidly grounded networks.
In this configuration, the module also works as a power meter.

DC8-037-2, Edition 11.2020
[dw_AI-8511_3xI_3xV, 1, en_US]
Figure 5-52 AI-8511 External Circuitry Variant for 3-Phase Voltage, 3-Phase Current
3-Phase Voltage, 2-Phase Current + Sensitive Ground Current

Through the current inputs I1 and I3, the corresponding phase currents are measured, and through the input
I2/IN, the sensitive zero-sequence current is measured. The value I2 is calculated.
This configuration is used for isolated and resonant grounded networks.
[dw_AI-8511_2xI_IN_3xV, 1, en_US]
Figure 5-53 AI-8511 External Circuitry Variant for 3-Phase Voltage, 2-Phase Current, Sensitive Zero-
Sequence Current

DC8-037-2, Edition 11.2020
5.4.12 CM-8820
[dw_CM-8820_Oblique, 1, --_--]
Figure 5-54 CM-8820
5.4.12.1 Features
• Mounting on DIN rail, at the last (right-most) slot of the I/O module line
• Current transformer adaptor for AI-8510
• 3 current transformer inputs

– Nominal current max. 1 A or 5 A with 100% overrange
• LoPo voltage output 225 mV

– Connection with AI-8510
– Removable screw terminal for LoPo output
5.4.12.2 Functions
– Acquisition of currents via current measuring sensors
– Measuring range 1 A or 5 A with 200% overrange
Output Functions
• Output through low-power outputs

– Nominal voltage 225 mV
– Measuring range 0 V to 450 mV

DC8-037-2, Edition 11.2020
Inputs for Transformer Currents
Nominal current 1 A/5 A (settable)

Max. measurement current 200 % IN
permitted
Internal consumption < 0.1 W at IN = 1 A
< 0.3 W at IN = 5 A
Thermal withstand capability 10 A permanent
100 A 1 s
Outputs for Measuring Currents
Nominal voltage AC 225 mV at IN = 1 A following IEC 60044-8

1.125 V at IN = 5 A
Max. voltage 2.25 V at IN = 10 A
Terminals • Removable screw terminals (grid size 5.08)

3 LoPo measuring currents, 10-pin (X1)
• Screw terminals for 3 transformer current inputs, 6-pin (X2)
4 kV (measurement category III)
Connection data X1 Locking torque (PHOENIX terminal) 60 0.5 Nm to 0.6 Nm
AWG min. 22
max. 12
max. 2.5 mm²
max. 2.5 mm²
max. 7 mm
Max. cable length 0.5 m 61
61 plastic-insulated copper conductors (7 core) with shield; up to 0.1 m (for AI-8510 and CM-8820 plugged side-by-side), single conduc-
tors without shield are possible. Nominal voltage U0/U = 300/500 V, temperature range -40 to 80 °C

DC8-037-2, Edition 11.2020
Connection data X2 Locking torque 0.5 Nm

AWG min. 24
max. 14
max. 2.5 mm²
max. 2.5 mm²
Wire strip length 9 mm
NOTE
i For USA and Canada: NRTL/SCC certified current transformers are required. Use only UL-listed energy-moni-
toring current transformers.
NOTE
i For each installed AI-8510, a CM-8820 must be connected ahead, if the current measurement is used.
Thereby CM-8820 modules may only be installed at the end of a module line (right-most), else the internal
I/O bus is interrupted.
CM-8820 modules may also be installed on a separate DIN rail, whereby the maximum cable length must
be considered.
NOTE
i The current carrying capacity of the connection cable is to be designed in relation to the maximum contin-
uous current or overcurrent.

DC8-037-2, Edition 11.2020
Accuracy of the Measured Values
Measured variable Dependency of accuracy class acc. to IEC 61557-12:2007-08 (K55)

Nominal current (input) 1A
2% @ 50 Hz; max. angle deviation 3°
5A
Nominal voltage (output) 3%
Nominal frequency 50 Hz
2% @ 0.2 to 10 A max. angle deviation 3°
60 Hz
3% @ 0.2 to 10 A max. angle deviation 3°

The process signals must be connected to 2 screw terminals. The peripheral connectors are assigned according
to the tables.
[dw_CM-8820_Front_v2, 1, --_--]
Figure 5-55 CM-8820 Front
Connector X1
Pin Signal Meaning

8 I1+ measuring current output 1
7 I1- measuring current output 1
6 I2+/IN+ measuring current output 2 / (sensitive) zero-
sequence current
5 I2-/IN- measuring current output 2 / (sensitive) zero-
sequence current
4 I3+ measuring current output 3
3 I3- measuring current output 3

DC8-037-2, Edition 11.2020
X2 current transformer terminals
Pin Signal Meaning

6 I1_P current transformer input 1
5 I1_N current transformer input 1
[dw_CM-8820_Block_Diagram, 1, en_US]
Figure 5-56 CM-8820 block diagram
! DANGER
² The connectors X1 and X2 may be detached or attached in de-energized state only!
! WARNING
² The inputs of connector X1 and X2 must not be connected directly with a mains supply circuit!

DC8-037-2, Edition 11.2020
NOTE
i Within the signal inputs exists only functional insulation. Therefore, the use of different current circuits is
not permitted.
! CAUTION
² Direct currents cannot be measured with CM-8820.
NOTE
i Please take account of the direction of current flow when connecting the current measuring inputs. With
inverse connection, the measured values are inverted and receive a negative sign.

The following circuitry variants are examples and not related exclusively to the shown values.
! DANGER
Works on the circuitry may be performed in de-energized state only!
² During electrical installation, all the rules and regulations of power systems must be considered.
! DANGER
Open transformer circuits will result in electric shock and arc flashover. Will cause death, serious injury or
considerable property damage.
² Only measure current with external current transformers. Do not use fuses for circuit protection. Do
not open the secondary circuit under load. Short circuit the secondary current terminals of the current
transformers before removing this device. The safety information for the current transformers used
must be followed.
3-Phase Current
Through the current inputs I1_P/I1_N, I2_P/I2_N, I3_P/I3_N the corresponding phase currents are measured.

DC8-037-2, Edition 11.2020
[dw_CM-8820_3xI, 1, en_US]
Figure 5-57 CM-8820 external circuitry for 3-phase current
Further options see 5.4.10.6 External Circuitry.
5.4.13 AO-8380
[AO-8380_Oblique_View, 1, --_--]
Figure 5-58 AO-8380

DC8-037-2, Edition 11.2020
5.4.13.1 Features
Analog output module
• 4 outputs (4 groups with 1 output each)
• Output of currents ±20 mA, ±10 mA
• Output of voltages ±10 V
5.4.13.2 Functions
Setpoint values by means of currents and voltages
• Output range settable with a resolution fa

– 16 bits (15 bits + sign) in the case of full output range
– Reducing the range results in a decreased resolution
• Basic application functions and procedures according to IEC 60870-5-101/104 fa

– Formal check
– Direct command
• Adaptation f
– Linear (normalized, technologically scaled, or short floating-point number) f
• Selectable behavior in case of communication failure and module failure fa

(keep value, output substitute value)
NOTE
Peripheral Elements according to IEC 60870-5-101/104, chapter Setpoint values by means of currents
and voltages.
Analog Outputs
4 analog outputs All outputs galvanically insulated

Current output max. ±20 mA at max. 500 Ω load
max. ±10 mA at max. 1 kΩ load
Voltage output max. ±10 V at min. 1 kΩ load
Resolution 0.025% at ±20 mA, ±10 mA, ±10 V

DC8-037-2, Edition 11.2020
Accuracy 0.3 % at 25 °C
0.4 % at 0 to 50 °C
0.7 % at -20 to 70 °C
0.8 % at -40 to 70 °C
Output circuits The circuits are operated with an internal voltage
Power Supply


AWG min. 22
max. 12
max. 2.5 mm²
max. 2.5 mm²
max. 7 mm


DC8-037-2, Edition 11.2020
[AO-8380_Front, 1, --_--]
Figure 5-59 AO-8380 Front
Connector X1
Pin Signal Meaning

3 OUT V0- analog output of group 0
2 OUT V0+ analog output of group 0
Connector X2
Pin Signal Meaning

Connector X3
Pin Signal Meaning

Connector X4
Pin Signal Meaning


DC8-037-2, Edition 11.2020
Display
LED Meaning
RY Readiness

[AO-8380_Block_Diagram_External_Circuitry, 2, en_US]
Figure 5-60 AO-8380 Block Diagram and External Circuitry Variant

DC8-037-2, Edition 11.2020
5.4.14 CM-8830
[dw_CM-8830_Oblique, 1, --_--]
Figure 5-61 CM-8830
5.4.14.1 Features
LED Module for a SICAM A8000 I/O row
• Indication of I/O module status (RY)
• Indication of I/O process status
• Indication of I/O process errors (ER)
• With a power consumption of less than 0.5 W, CM-8830 does not affect the power distribution of an
existing SICAM A8000 I/O row
5.4.14.2 Functions
• CM-8830 is detected after mounting without project engineering from the Master Module.
• CM-8830 is ready (RY) only when the Master Module system startup has been completed.
• The I/O process status of the DI and AI modules is displayed without project engineering from the SICAM
A8000 system.
• The LEDs provide actual status functions and status indications during system operation
• The LEDs also indicate correct wiring during commissioning
• CM-8830 updates the process data display every 100 ms

A detailed description of the visualization is provided in chapter 11.3.5 LED Module
CM-8830 can be fitted in any position on the right side of the power supply on the SICAM A8000 I/O row, as
shown in the following 3 figures.

DC8-037-2, Edition 11.2020
[dw_CM-8830_firstposition_8021, 1, --_--]
Figure 5-62 CM-8830 in the First Position
[dw_CM-8830_midposition_8021, 1, --_--]
Figure 5-63 CM-8830 in the Middle Position
[dw_CM-8830_lastposition_8021, 1, --_--]
Figure 5-64 CM-8830 in the Last Position

DC8-037-2, Edition 11.2020
5.4.14.3 Technical Specifications
Power Supply
Operating voltage DC 4.75 V to 5.5 V

Mechanics
Dimension 124 mm x 30 mm x 132 mm (L x W x H, dimensions w/o DIN rail)

Weight 185 g (including bus module 12 g)
Protection Type Class III
[dw_cm8830_blockdiagram, 1, en_US]
Figure 5-65 LED Module Block Diagram

DC8-037-2, Edition 11.2020
5.5 SICAM TM I/O Modules
NOTE
i The functions and the belonging mode of action are described in detail in the manual SICAM RTUs Common
Functions Peripheral Elements according to IEC 60870-5-101/104.
In the following listing, footnotes are used to specify the effect of the functions in detail.
f = Telecontrol
The function affects process information which is spontaneously transmitted
f1 = Telecontrol
The function delivers (acquisition) spontaneously transmitted process information or is controlled by such
information (output); partly, periodically transmitted information is also created/required
a = Automation
The function affects process information which is periodically transmitted
b = Calculation
The function affects process information which is used as input for the calculation of calculated (derived)
values
NOTE
i The technical data of the SICAM TM I/O Modules are described in the document SICAM TM I/O Modules .
5.5.1 DI-6100, DI-6101, DI-6104
5.5.1.1 Functions
Single-point informationn
• Revision fa
• Inversion fa
Double-point information
• Revision fa

DC8-037-2, Edition 11.2020
• Inversion fa
Integrated totals via count pulses f1

– Revision
– Inversion
– Pulse counting

– Set counter

– Counter request
5.5.2 DI-6102, DI-6103
5.5.2.1 Functions
Single-point information
• Revision fa

DC8-037-2, Edition 11.2020
• Inversion fa
Double-point information
• Revision fa
• Inversion fa
Integrated totals via count pulses f1

– Revision
– Inversion
– Pulse counting

– Set counter

– Counter request

DC8-037-2, Edition 11.2020
5.5.3 DO-6200
5.5.3.1 Functions
Pulse commands f1
• Output of pulse commands

– 1-pole

– Formal check
– Direct command
• Command locking
• Synchronization
• Revision

– Settable
• If outputs of the module are used for pulse commands, no outputs of the same module can be used for
binary information output
Binary information output
• Deactivation on module failure fa
• Spontaneous transmissionf or
• If outputs of the module are used for binary information output, no outputs of the same module can be
used for pulse commands
used)

DC8-037-2, Edition 11.2020
Return information to pulse command assignment
• Settable assignment for messages and pulse commands, which are acquired or output on the I/O Master
Module
• Predefined assignment for messages and pulse commands, which are acquired or output on the I/O
Master Module
5.5.4 DO-6212
5.5.4.1 Functions
Pulse commands f1
• Output of pulse commands

– Cannot be mixed
• – Formal check
– Direct command
• Command locking
• Synchronization
• Revision
• – Settable
• If outputs of the module are used for pulse commands, no outputs of the same module can be used for
binary information output
Binary information output
• Deactivation on module failurefa

DC8-037-2, Edition 11.2020
• If outputs of the module are used for binary information output, no outputs of the same module can be
used for pulse commands
used)
Binary information and command output
• Settable output of the categories DO_EX and DO_DX

– Mixed output of binary information items and commands on 1 DO module possible
– Output of pulse commands or persisting commands
Module
Master Module
5.5.5 DO-6220, DO-6222, DO-6230
5.5.5.1 Functions
Pulse commands f1
• Checked output of pulse commands

– Cannot be mixed on one module

– Formal check
– Direct command
• Command locking
• Synchronization
• Revision
• DO-6220 - command output according to IC1

– Idle check
– Selective activation check

DC8-037-2, Edition 11.2020
• DO-6221 - command output according to RC1

– Idle check
– Selective activation check
– Resistance check
– Current flow information
– Earth fault check
– Interference voltage check

– Settable
• Periodical control circuit check
• Monitoring of command output sequence to prevent incorrect outputs
• Command initionation for auto-reclose
• Activation of command contactors with or without series-break contacts (with DO-6221)
Return information to pulse command assignment (applies for DO-6230)
Module
Master Module
5.5.6 AI-6300, AI-6307, AI-6308
5.5.6.1 Functions
Currents and voltages
• Settable acquistion grid n ⋅ 100 ms f
• Measurement range settable with a resolution f

– 13 bits (12 bits + sign) at full measurement range
• Revision f
• Noise rejection f
• Automatic calibration f
• Smoothing f
• Adaptation f
– Linear (normalized, technologically scaled or short floating point)
– Suppression of zero range
– Plausibility check

DC8-037-2, Edition 11.2020
• Change monitoring f
• On the same module, currents and voltages cannot be mixed
5.5.7 AI-6310
5.5.7.1 Functions
Temperatures f1
• Connection of the resistance thermometers: 2-, 3-, or 4-wire technique
• Update every 400 ms
• Settable measuring range

– Temperature values
– Input range
Pt100: -50…+350°C / 58…+662°F / (≈80,31…229,67 Ω)
Pt100: 100…+700°C / 148…+1292°F / (≈60,25…345,13 Ω)
Ni100: 60…+250°C / 76…+482°F / (≈69,5…289,2 Ω)
– Resolution
Pt100: 50…+350°C 0,15°C / 0,28°F / (56 mΩ)
Pt100: 100…+700°C 0,15°C / 0,28°F / (56 mΩ)
Ni100: 60…+250°C 0,15°C / 0,28°F / (56 mΩ)
– Update grid
16⅔ Hz < 6,8 s
50 Hz < 5,6 s
60 Hz < 5,2 s
– Resistance values
– Input range 40...400 Ω
– Resolution: 56 mΩ
– Update grid
HW-Rev.="--" HW-Rev.≥"-A"
16⅔ Hz < 6,8 s 16⅔ Hz < 1,68 s
50 Hz < 5,6 s 50 Hz < 1,44 s
60 Hz < 5,2 s 60 Hz < 1,36 s
• Revision
• Noise rejection
• Automatic calibration
• Calibration for 2-wire technique
• Smoothing
• Adaptation
– Temperature value (°C, °F), conversion using implemented curves
– Resistance (Ω)
• Change monitoring
• Spontaneous transmission of changes

DC8-037-2, Edition 11.2020
5.5.8 AO-6380
5.5.8.1 Functions
Setpoint values by means of currents and voltages
• Output range settable with a resolution of fa

– 16 bits (15 bits + sign) at full output range
• Application functions and procedures according to IEC 60870-5-101/104fa

– Formal check
– Direct command
• Adaptationf
– Linear (normalized, technologically scaled or short floating point) f
• Selectable behavior on communication failure and module failurefa

(keep value, output substitute value)
• Spontaneous transmissionf or
5.5.9 TE-6430
5.5.9.1 Functions
Integrated totals via counting pulses
• 2 counting pulse inputs or
• 1 counting pulse input and 1 transfer input
• Inputs are galvanically insulated from logic circles and ground
• Inputs are not galvanically insulated from each other
• Input voltage range from 24 up to 60 V
• Inputs are secured by means of EMC filter and protector equipment
• The autonomous operable functions of the module are operated buffered, thus counting function and
counts remain correct also over a voltage failure from up to 72 hours
• Spontaneous transmissionf

DC8-037-2, Edition 11.2020
5.6 MTBF Data
5.6 MTBF Data

The MTBF values shown in this section have been calculated according to Siemens standard SN29500.
All electrical and electromechanical components have been considered. Not included are mechanical compo-
nents (screws, housing, adhesive labels, etc.).
The MTBF values are statistic values which serve only for the estimation of maintenance and substitute needs.
These values are no guaranteed product attribute.
The MTBF values have been calculated for an ambient temperature of 40°C.
5.6.1 MTBF Values of the SICAM A8000 Modules
Master Modules
Type Module [Hours] [Years]

CP-8021 Master Module 682 165 77.87
CP-8022 Master Module with GPRS 485 206 55.39
Power Supply Modules

PS-8620 Power Supply DC 24 to 60 V, 12 W 1 809 267 206.54
PS-8642 Power Supply DC or AC 100 to 240 V, 45 W 1 014 243 115.8
SICAM I/O Modules

DI-8110 Digital Input 2x8 DC 24 V 1 617 914 184.69
DI-8111 Digital Input 2x8 DC 48/60 V 1 617 914 184.69
DO-8212 Digital Output Relays 8x DC 24 to 220 V/AC 230 V 2 362 056 269.64
AI-8310 Analog Input 2x2 Pt100/Pt1000 1 293 929 147.71
AI-8320 Analog Input 4x ±20 mA 2 238 589 255.55
AI-8510 Analog Input 3x V (240 V), 3x I (LoPo) 1 354 169 154.59
AI-8511 Analog Input 3x V (LoPo), 3x I (LoPo) 1 408 352 160.77
AO-8380 Analog Output 4x ±20 mA/±10 V 1 377 524 157.25
Accessories

CM-8820 CT-Adapter 3x I 1 A_5 A/225 mV (only for AI-8510) 11 993 284 1369.10
CM-8830 SICAM I/O Module LED Unit 1 659 916 189.00
5.6.2 MTBF Values of SICAM TM I/O Modules
Type Module MTBF MTBF

[hours] [years]
DI-6100 Digital input 2x8, DC 24 to 60 V 474 651 54.18
DI-6101 Digital input 2x8, DC 110/220 V 474 651 54.18

DC8-037-2, Edition 11.2020
5.6 MTBF Data
Type Module MTBF MTBF

[hours] [years]
DI-6102 Digital input 2x8, DC 24 to 60 V, 1 ms 450 500 51.43
DI-6103 Digital input 2x8, DC 110/220 V, 1 ms 50 500 5.76
DI-6104 Digital input 2x8, DC 220 V 474 651 54.18
DO-6200 Digital output transistor: 2x8, DC 24 to 60 V 282 704 32.27
DO-6212 Digital output relay: 8x DC 24 to 220 V/AC 230 V 87 600 10
DO-6220 Command out basic module 87 600 10
DO-6221 Command out basic module measurement 70 080 8
DO-6230 Command output relay module 157680 18
AI-6300 Analog input 2x2 ±20 mA/±10 V 549 674 62.75
AI-6307 Analog input 2x2 ±2.5 mA/±5 mA/±10 V 549 674 62.75
AI-6310 Analog input 2x2 Pt100/Ni100 360 395 41.14
AO-6380 Analog output 4x ±20 mA/±10 mA/±10 V 224 549 25.63

DC8-037-2, Edition 11.2020
6 Installation and Circuitry
This chapter describes the mechanical design of CP- 8000/CP-802x and how the installation and wirings are to
be accomplished.
This chapter shows further how the various communication methods can be realized by means of the standard
modems and special cables.
6.1 Mechanical Design 220
6.2 Dimensions 226
6.3 Installation Location and Position 230
6.4 Assembly of CP-8000 232
6.5 Assembly of CP-802x 245
6.6 Memory Cards 256
6.7 Wiring 258
6.8 Switching the Device On and Off 260
6.9 Setup of External Communication Connections 261

DC8-037-2, Edition 11.2020
Installation and Circuitry
6.1 Mechanical Design
6.1.1 CP-8000
The electrical components of the device are housed in a plastic casing with the dimensions 128 mm x 124 mm
x 116 mm (W x H x D). The casing is designed for assembly on a DIN rail.
At the front are the operation and display elements, an interface for the communication via Ethernet, and a
slot for the SD card.
[ph_CP-8000_mecanical_design_front, 1, en_US]
Figure 6-1 CP-8000 - Mechanical Design Front/Upper Side
At the top of the device are the connections for the communication via RS-485 and RS 232, as well as a further
Ethernet interface.
On the right side of the housing is the bus connector for the I/O coupling module. It is covered with a label.

DC8-037-2, Edition 11.2020
On the bottom side of the device are the connections for the process signals as well as for the supply voltage.
[ph_CP-8000_mecanical_design_bottom, 1, en_US]
Figure 6-2 CP-8000 - Mechanical Design Lower Side
At the back is the DIN rail mounting.
[ph_CP-8000_mecanical_design_back, 1, en_US]
Figure 6-3 CP-8000 - Mechanical Design Back Side
6.1.1.1 Locking Hook

The device is locked onto the DIN rail and also removed again using the locking hook.
Details see section 6.4.4 Mounting of the Basic Device

DC8-037-2, Edition 11.2020
6.1.1.2 Type Plate

On the left side of the housing resides the type plate with specific information as type, power consumption,
order number, serial number, hardware addresses for the network operation (MAC address for interface X1
and X4).
[dw_CP-8000-40_type_plate, 1, --_--]
Figure 6-4 CP-8000 - Type Plate (Variant -40 bis +70°C)
Symbol Meaning
CE conformity
WEEE marking
Protection class II / protective insulation
Caution, risk of danger. The documentation

must be observed.

DC8-037-2, Edition 11.2020
6.1.2 CP-802x
The electrical components of the device are housed in a plastic casing with the dimensions 30 mm x 132 mm
x 124 mm (W x H x D). The casing is designed for assembly on a DIN rail.
At the front are the LED display elements, the communication interfaces and a slot for the SIM card.
[dw_CP-802x_mechanical_design_front, 1, en_US]
Figure 6-5 CP-802x - Mechanical Design Front Side
At the back are the locking hooks, the bus connector and below the slot for the SD card.
[dw_CP-802x_mechanical_design_back, 1, en_US]
Figure 6-6 CP-802x - Mechanical Design Back Side
6.1.2.1 Locking Hook

The device is locked onto the DIN rail and also removed again using the locking hook.
Details see section 6.5.4 Mounting of a SICAM A8000 Module.

DC8-037-2, Edition 11.2020
6.1.2.2 Type Plate

On the left side of the housing resides the type plate with specific information as type, power consumption,
order number, serial number, hardware addresses for the network operation (MAC address for interface X1
and X4).
[dw_CP-8022_type_plate, 1, --_--]
Figure 6-7 CP-802x - Type Plate (example CP-8022)
Symbol Meaning
CE conformity
UL conformity
WEEE marking
Protection class II / protective insulation
Caution, risk of danger. The documentation

must be observed.
6.1.3 SICAM I/O Modules
6.1.3.1 Labeling
The following places on the SICAM I/O modules are reserved for labels:
• Area on the center left hand side at the housing front

Label with 2D code for scanning and readable serial number (upon delivery already stuck)
• Bevel at the housing front bottom

Operational equipment indicator (free definable)

DC8-037-2, Edition 11.2020
6.1.3.2 Screw Terminal Types

For the screw terminals 2 different types are provided (manufacturer PHOENIX or FCI, see different imprinting
laterally at the terminal).
[dw_A8000_screw_terminal_types, 1, --_--]
Figure 6-8 Screw Terminal Types

DC8-037-2, Edition 11.2020
6.2 Dimensions
6.2 Dimensions
6.2.1 CP-8000 Front View
[dw_CP-8000_dimensions_front, 1, --_--]
Figure 6-9 CP-8000 - Dimensions Front

DC8-037-2, Edition 11.2020
6.2 Dimensions
6.2.2 CP-8000 Side View
[dw_CP-8000_dimensions_side, 1, --_--]
Figure 6-10 CP-8000 - Dimensions Side

DC8-037-2, Edition 11.2020
6.2 Dimensions
6.2.3 CP-802x Front and Side View
[dw_CP-802x_dimensions_side_front, 1, --_--]
Figure 6-11 CP-802x - Dimensions Side and Front

DC8-037-2, Edition 11.2020
6.2 Dimensions
6.2.4 SICAM I/O Module Front and Side View
[dw_A8000_io_module_dimensions, 1, --_--]
Figure 6-12 SICAM I/O Module - Dimensions Side and Front

DC8-037-2, Edition 11.2020
6.3 Installation Location and Position

Correct and safe operation of the product requires adequate transportation, storage, installation and
mounting in an NRTL/SCC certified fire/electrical industrial control panel/cabinet or similar enclosure. Further-
more, appropriate use and maintenance is necessary.
For details on the site of operation, please refer to chapter 4 Ambient Conditions.
The basic device (with or without I/O modules) may only be installed horizontally.
[dw_A8000_mounting_position, 1, --_--]
Figure 6-13 CP-8000, CP-802x - Installation Location
NOTE
i Not permitted is the vertical installation or installations on the ceiling and on the floor (excessive tempera-
ture, dust load).
6.3.1 DIN Rail (TS35 Rail)
For the installation of CP-8000/CP-802x a DIN rail is to be used, which conforms to the Standard EN 60715.
The orientation and position in which the DIN rail is to be installed must be determined locally.
The DIN rail must be installed horizontally on a vertical wall.
! WARNING
² The connection of the DIN rail with the cabinet/rack/mounting plate must guarantee a reliable
grounding of the device. This base itself must be grounded properly. A mounting plate is recom-
mended.
6.3.2 Cable Duct
Cable ducts are recommended for the cabling above and below the device. The minimum distance from the
device to the cable duct is 30 mm.

DC8-037-2, Edition 11.2020
NOTE
i When using a cable duct with 100 mm depth below the device, it is necessary to keep a 50 mm minimum
distance between device and cable duct to operate the locking hook.

DC8-037-2, Edition 11.2020
6.4 Assembly of CP-8000
6.4.1 Space Requirement for the Basic Device
The place requirement is dependent on the device size and the size of the cable ducts used.
For thermal reasons, a minimum distance of 30 mm must be maintained around the device.
[dw_CP-8000_space_requirement1, 1, --_--]
Figure 6-14 CP-8000 - Space Requirement
When using a cable duct with 100 mm depth below the device, it is necessary to keep a 50 mm minimum
distance between device and cable duct to operate the locking hook.
[dw_CP-8000_space_requirement2, 1, --_--]
Figure 6-15 CP-8000 - Minimum Distance

DC8-037-2, Edition 11.2020
6.4.2 Space Requirement with SICAM I/O Modules
When connecting external SICAM I/O Modules, the dimensions given in the table must be considered in addi-
tion to the number of modules used (max. 6).
Example: maximal equipped modules
Thermal distance on the left 30 mm

CP-8000 128 mm
CM-8811 coupling module 12.5 mm
CM-8830 LED module 30 mm
6 SICAM I/O Modules (6 x 30) 180 mm
End clamp 5 mm
Horizontal space requirement (mm) 385.5 mm
[dw_CP-8000_io_module_space_req, 1, --_--]
Figure 6-16 CP-8000 - Space Requirement with SICAM I/O Modules
6.4.3 Space Required with SICAM TM I/O Modules
When connecting external SICAM TM I/O modules, take into account the number of I/O modules used (max. 6)
as well as the dimensions given in the table.
Example: maximal equipped modules

CP-8000 128 mm
CM-8811 coupling module 5 mm
6 SICAM TM I/O modules (6 x 63) 378 mm
Protective cap for bus 3 mm
End clamp 5 mm
Horizontal space requirement (mm) 549 mm

DC8-037-2, Edition 11.2020
[dw_CP-8000_tm_io_module_space_req, 1, --_--]
Figure 6-17 CP-8000 – Space Required with SICAM TM I/O Modules
Example: 2-line arrangement with CM-6810

CP-8000 128 mm

DC8-037-2, Edition 11.2020
[dw_CP-8000_tm_io_module2_space_req, 1, --_--]
Figure 6-18 CP-8000 – Space Required, 2-Line with SICAM TM I/O Modules
6.4.4 Mounting of the Basic Device
CP-8000 can be installed on the DIN rail by hand, without any tools.
Hang the inclined device in the top edge of the DIN rail (1).
[dw_CP-8000_mounting1, 1, --_--]
Figure 6-19 CP-8000 – Mounting (1)

DC8-037-2, Edition 11.2020
Swivel the device until the locking hook comes into contact with the bottom edge of the DIN rail (2).
[dw_CP-8000_mounting2, 1, --_--]
Push the casing to the back (3). As a result, the locking hook opens briefly and the casing engages on the rail.
[dw_CP-8000_mounting3, 1, --_--]

DC8-037-2, Edition 11.2020
6.4.5 Removal of the Basic Device
To remove the device again, or to change its position on the DIN rail, the locking hook must be opened again.
Insert a screwdriver suitable for slotted screws into the locking hook below the casing (1). The screw driver
must have contact to the housing. The locking hook is opened by carefully pushing the screwdriver upwards.
[dw_CP-8000_removal1, 1, --_--]
Figure 6-22 CP-8000 - Removal (1)
Swing the bottom section of the device slightly forward (2).
[dw_CP-8000_removal2, 1, --_--]

DC8-037-2, Edition 11.2020
Lift the device upwards out of the rail (3).
[dw_CP-8000_removal3, 1, --_--]
NOTE
i If external I/O Modules are coupled to your device, then you can only remove the device after separating
the external I/O Modules.
6.4.6 Assembly of External SICAM I/O Modules
CP-8000 can be expanded by up to 6 external SICAM I/O Modules. Thereto the following steps are essential:
• Mounting of the coupling module for SICAM I/O Modules
• Mounting of the bus connector for SICAM I/O Modules
• Mounting of the SICAM I/O Modules
6.4.6.1 Mounting of the Coupling Module for SICAM I/O Modules

The coupling module CM-8811 must be mounted on the right side of the CP-8000 housing.
To mount the coupling module, it is necessary to remove the label (1) which covers the I/O bus. Afterwards
lead the coupling module parallel to the housing (2) and push it evenly on it until it is engaged.
[dw_CP-8000_mounting_io-module1, 1, --_--]
Figure 6-25 CP-8000 - Mounting of the Coupling Module for SICAM I/O Modules
Now you can mount CP-8000 on the DIN rail.

DC8-037-2, Edition 11.2020
NOTE
i The mounting of the coupling module on the CP-8000 housing can take place before or after the device is
mounted on the DIN rail.
6.4.6.2 Mounting of the Bus Connector for SICAM I/O Modules

Each SICAM I/O module is equipped with a bus connector (CM-8812). It must be equipped separately from the
I/O module. Disconnect the bus connector before mounting.
Clip the first bus connector to the right of the coupling module onto the DIN rail (1) and push it into the bus
plug of the coupling module (2). Both elements must be aligned seamlessly.
Figure 6-26 CP-8000 – Mounting of the Bus Connector for SICAM I/O Modules
You can then mount the bus connectors of further SICAM I/O modules in the same way.
! CAUTION
Bus communication is system-internal only.
² It is not allowed to modify the bus connector.

DC8-037-2, Edition 11.2020
6.4.6.3 Mounting of the SICAM I/O Modules

The SICAM I/O modules can be mounted as shown in following picture.
Figure 6-27 CP-8000 – Mounting of a SICAM I/O Module
NOTE
i The tongue and groove system integrated in the modules facilitates the correct combination of the plugs.
The module has only been connected correctly once the locking hooks have snapped onto the DIN rail.
End Clamp
To increase the stability, it is necessary to mount an end clamp flush left from the CP-8000 housing and flush
right after the last SICAM I/O module.
Figure 6-28 CP-8000 – Mounting of the End Clamp
Refer to 2.1.4.2 External SICAM I/O Modules for information about the SICAM I/O modules.
Note the data in the section2.1.4.4 Configuration Rules for I/O Modules.
6.4.6.4 Removal of the SICAM I/O Modules

For the removal, proceed according to section 6.5.5 Removal of a SICAM A8000 Module.

DC8-037-2, Edition 11.2020
6.4.7 Assembly of External SICAM TM I/O Modules
CP-8000 can be expanded with up to 6 external SICAM TM I/O Modules. Thereto the following steps are essen-
tial:
• Mounting of the coupling module for SICAM TM I/O Modules
• Mounting of the SICAM TM I/O Modules
6.4.7.1 Mounting of the Coupling Module for SICAM TM I/O Modules

The coupling module CM-6811 must be mounted on the right side of the CP-8000 housing.
To mount the coupling module, it is necessary to remove the label (1) which covers the I/O bus. Afterwards
lead the coupling module parallel to the housing (2) and push it evenly on it until it is engaged.
[dw_CP-8000_mounting_tm_io-module1, 1, --_--]
Figure 6-29 CP-8000 - Mounting of the Coupling Module for SICAM TM I/O Modules
Now you can mount CP-8000 on the DIN rail.
NOTE
i The mounting of the coupling module on the CP-8000 housing can take place before or after the device is
mounted on the DIN rail.

DC8-037-2, Edition 11.2020
6.4.7.2 Mounting of the SICAM TM I/O Modules

After CP-8000 and the coupling module have been mounted on the DIN rail, you can mount the SICAM TM I/
O modules.
Insert the first I/O module into the guides at the coupling module as shown in the following figure and press
together the locking clips at the top of the module. You can now position the module on the DIN rail and
release the locking clips. Make sure the module has correctly engaged on the DIN rail.
Figure 6-30 CP-8000 – Mounting of a SICAM TM I/O Module (1)
Then you can attach the further SICAM TM I/O modules.
! CAUTION
The last SICAM TM I/O module must be equipped with a protective cap to protect the bus.
² Use the bus termination for TM housings which has been enclosed with the coupling module.
Figure 6-31 CP-8000 – Mounting of a SICAM TM I/O Module (2)

DC8-037-2, Edition 11.2020
End Clamp
For reasons of stability, it is necessary to mount an end clamp flush left from the CP-8000 housing and flush
right after the last SICAM TM I/O module.
Figure 6-32 CP-8000 – Mounting of the End Clamps
Refer to the following document for information about SICAM TM I/O modules:
User manual SICAM TM I/O Module
https://support.industry.siemens.com/cs/attachments/109757734/SICAM_TM_IO_MODULE_ENG.pdf
Note the data in the section 2.1.4.4 Configuration Rules for I/O Modules.
6.4.7.3 Removal of the SICAM TM I/O Modules

For the removal, proceed as follows:
1. Press the locking clips together
2. Withdraw the module with clips pressed together
6.4.8 Separating of Basic Device and I/O Coupling Module
If you need to separate a CP-8000 from the I/O coupling module (e.g. spare part replacement), proceed as
follows:
1. Separate the external I/O Modules from the basic device.
2. Remove the basic device including the coupling module from the DIN-rail.
3. Loose at first the 4 clamps of the coupling module which are arrested at the housing.
[ph_CP-8000_coupling_module_removal_with_finger, 1, --_--]
Figure 6-33 CP-8000 - Separating of Basic Device and I/O Coupling Module (1)

DC8-037-2, Edition 11.2020
4. Loose the 3 clamps which are arrested inside the housing. Use a proper tool (e.g. a small slotted screw-
driver).
[ph_CP-8000_coupling_module_removal, 1, --_--]
Figure 6-34 CP-8000 - Separating of Basic Device and I/O Coupling Module (2)
5. Now you can demount the TM I/O coupling module

6. Cover the holes of the bus with a label.
NOTE
i Above illustrations show the separation of a SICAM TM I/O coupling module from a CP-8000.
The separation of a SICAM I/O coupling module works the same way..

DC8-037-2, Edition 11.2020
6.5 Assembly of CP-802x
6.5.1 Space Requirement for the Basic Device with Power Supply
For the operation of CP-8021 or CP-8022 a power supply module is required. The belonging dimension and
the minimum distance (30 mm) around the modules must be considered for the determination of the space
requirement.
For thermal reasons, a minimum distance of 30 mm must be maintained around the device.
[dw_CP-802x_space_requirement1, 1, --_--]
Figure 6-35 CP-802x - Space Requirement
[dw_CP-802x_space_requirement2, 1, --_--]
Figure 6-36 CP-802x - Minimum Distance

DC8-037-2, Edition 11.2020
6.5.2 Space Requirement CP-802x with SICAM I/O Modules
When connecting external SICAM I/O Modules, the dimensions given in the table must be considered in addi-
tion to the number of modules used (max. 8).
Example: Maximal number of installed modules

CP-802x 30 mm
2 SICAM PS-86xx (2 x 30) 60 mm
8 SICAM I/O Modules (8 x 30) 240 mm
CM-8830 LED Module 30 mm
End clamp 5 mm
[dw_CP-802x_io_module_space_req, 1, --_--]
Figure 6-37 CP-802x - Space Requirement with SICAM I/O Modules
6.5.3 Space Required for CP-802x with SICAM TM I/O Modules
When connecting external SICAM TM I/O modules, take into account the number of I/O modules used (max. 8)
as well as the dimensions given in the table.
Example: Maximum number of installed modules

CP-802x 30 mm
2x SICAM PS-86xx (2 x 30) 60 mm
Protective cap for bus 3 mm
End clamp 5 mm

DC8-037-2, Edition 11.2020
[dw_CP-802x_tm_io_module_space_req, 1, --_--]
Figure 6-38 CP-802x – Space Required with SICAM TM I/O Modules
6.5.4 Mounting of a SICAM A8000 Module
The modules of the SICAM A8000 Series are installed by means of a bus connector and a locking hook on the
DIN rail without using any tool.
Each module is equipped with a bus connector. Disconnect it from the module and clip it onto the DIN rail (1).
[dw_CP-802x_mounting1, 1, --_--]
Figure 6-39 CP-802x – Mounting of the Bus Connector
! CAUTION
Bus communication is system-internal only.
² It is not allowed to modify the bus connector.

DC8-037-2, Edition 11.2020
Press the module on the bus connector (2). This opens the locking hooks.
Figure 6-40 CP-802x – Mounting of a SICAM A8000 Module (1)
Once module and bus connector have been connected correctly, the locking hooks are latched on the DIN rail
(3).
Figure 6-41 CP-802x – Mounting of a SICAM A8000 Module (2)
NOTE
i You also can open and lock the locking hooks on the module, before you mount the module. They must be
closed manually after installation.

DC8-037-2, Edition 11.2020
6.5.5 Removal of a SICAM A8000 Module
Reopen the locking hooks to once again remove a module or change its position on the DIN rail.
Insert a screwdriver suitable for slotted screws into the locking hook (as shown in the picture). The screwdriver
must be in contact with the housing. The locking hooks are opened by carefully pushing the screwdriver
downwards (1) resp. upwards (2).
[dw_CP-802x_removal1, 1, --_--]
Figure 6-42 CP-802x – Removal of a SICAM A8000 Module (1)
Once the locking hooks have been locked on the housing, you can pull off the module forward (3).
[dw_CP-802x_removal2, 1, --_--]
Figure 6-43 CP-802x – Removal of a SICAM A8000 Module (2)

DC8-037-2, Edition 11.2020
NOTE
i If external I/O modules have been coupled to your device, the device can only be removed after having
separated the external I/O modules.
6.5.6 Mounting of the Power Supply Module
The Power Supply Module is equipped with a bus connector (CM-8812). This must be equipped separately
from the module. You must disconnect the bus connector before mounting.
Click the bus connector right beside the Master Module on the DIN rail (1) and push it into the bus plug of the
Master Module (2). Both elements must be aligned seamlessly.
[dw_CP-802x_mounting_ps-module1, 1, --_--]
Figure 6-44 CP-802x - Mounting of the Power Supply Module (1)
! CAUTION
Bus communication is system-internal only. It is not allowed to modify the bus connector.
² The devices must be powered by a SICAM A8000 power supply only. For USA and Canada: Use a UL
listed SICAM A8000 power supply.

DC8-037-2, Edition 11.2020
The Power Supply Module can be mounted as shown in the following picture.
[dw_CP-802x_mounting_ps-module2, 1, --_--]
Figure 6-45 CP-802x - Mounting of the Power Supply Module (2)
NOTE
i The tongue and groove system integrated in the modules facilitates the correct combination. The module is
only connected correctly when the locking hook is snapped onto the DIN rail.
6.5.7 Assembly of External SICAM I/O Modules
CP-802x can be expanded by up to 8 external SICAM I/O Modules. Thereto the following steps are essential:
• Mounting of the bus connector for SICAM I/O Modules
• Mounting of the SICAM I/O Modules

DC8-037-2, Edition 11.2020
6.5.7.1 Mounting of the Bus Connector for SICAM I/O Modules

Each SICAM I/O module is equipped with a bus connector (CM-8812). It must be equipped separately from the
I/O module. Disconnect the bus connector before mounting.
Mount the first bus connector right beside the power supply module on the DIN rail (1) and push it into the
bus plug of the power supply module (2). Both elements must be aligned seamlessly.
[dw_CP-802x_mounting_io-module1, 1, --_--]
Figure 6-46 CP-802x – Mounting of the Bus Connector for SICAM I/O Modules
Afterwards you can mount the bus connectors of further SICAM I/O modules in the same way.
! CAUTION
Bus communication is system-internal only. It is not allowed to modify the bus connector.
² Devices must be operated with a SICAM A8000 power supply only. For USA and Canada: Use UL-listed
SICAM A8000 power supply modules only.
6.5.7.2 Mounting of the SICAM I/O Modules

The SICAM I/O Modules can be mounted as shown in following picture.
Figure 6-47 CP-802x - Mounting of a SICAM I/O Module

DC8-037-2, Edition 11.2020
NOTE
i The tongue and groove system integrated in the modules facilitates the correct combination. The module is
only connected correctly when the locking hook is snapped onto the DIN rail.
End Clamp
To increase the stability, it is necessary to mount an end clamp flush left from the CP-802x housing and flush
right after the last SICAM I/O Module.
Figure 6-48 CP-802x - Mounting of the End Clamp
You can take information on the SICAM I/O Modules out of the following section 2.1.4.2 External SICAM I/O
Modules.
Please consider the notes in the section 2.1.4.4 Configuration Rules for I/O Modules.
6.5.7.3 Removal of the SICAM I/O Modules

For the removal, proceed according to section 6.5.5 Removal of a SICAM A8000 Module.
6.5.8 Assembly of External SICAM TM I/O Modules
CP-802x can be expanded with up to 8 external SICAM TM I/O Modules. Thereto the following steps are essen-
tial:
• Mounting of the coupling module for SICAM TM I/O Modules
• Mounting of the SICAM TM I/O Modules

DC8-037-2, Edition 11.2020
6.5.8.1 Mounting of the Coupling Module for SICAM TM I/O Modules

The coupling module CM-6812 must be mounted on the right side of the Power Supply Module housing.
Lead the coupling module parallel to the housing and push it evenly on it until it is engaged.
[dw_CP-802x_mounting_tm_io-module1, 1, --_--]
Figure 6-49 CP-802x - Mounting of the Coupling Module for SICAM TM I/O Modules
Afterwards you can mount SICAM TM I/O Modules on the DIN rail.
NOTE
i The mounting of the coupling module can take place before or after the housing is mounted on the DIN
rail.
6.5.8.2 Mounting of the SICAM TM I/O Modules

After CP-802x, the Power Supply Module and the coupling module are mounted on the DIN rail, you can start
to mount the SICAM TM I/O Modules.
Lead the first I/O Module as shown in the following picture into the guides on the coupling module and press
the locking clips on the top side of the module together. Now you can put the module on the DIN rail and
release the locking clips. Make sure that the module is correctly engaged on the DIN rail.
Figure 6-50 CP-802x - Mounting of a SICAM TM I/O Module (1)
Afterwards you can attach the further SICAM TM I/O Modules.

DC8-037-2, Edition 11.2020
! CAUTION
The last SICAM TM I/O Module must be equipped with a protective cap to protect the bus.
² The appropriate cap is delivered with the coupling module.
Figure 6-51 CP-802x - Mounting of a SICAM TM I/O Module (2)
End Clamp
To increase the stability, it is necessary to mount an end clamp flush left from the CP-802x housing and flush
right after the last SICAM TM I/O Module.
Figure 6-52 CP-802x - Mounting of the End Clamp
You can take information on the SICAM TM I/O Modules out of the following documents:
User Manual SICAM TM I/O Module
https://support.industry.siemens.com/cs/attachments/109757734/SICAM_TM_IO_MODULE_ENG.pdf
Please consider the notes in the section 2.1.4.4 Configuration Rules for I/O Modules.
6.5.8.3 Removal of the SICAM TM I/O Modules

For the removal, proceed as follows:
1. Press the locking clips together.
2. Withdraw the module with clips pressed together.

DC8-037-2, Edition 11.2020
6.6 Memory Cards
6.6 Memory Cards
6.6.1 SD Card
CP-8000/CP-802x uses an SD card (Secure Digital) for the storage of firmware, application and diagnosis data.
The Master Modules are supplied with an SD card inserted.
You find further information in section 7.4.1 SD Card.
NOTE
i Do not remove or insert the SD card during operation of the device.
6.6.1.1 Inserting the SD Card

Whith CP-8000 the SD card is inserted in the front of the device.
With CP-802x the SD card is inserted in the rear side, therefore the Master Module must be removed from the
DIN rail when exchanging the SD card.
[dw_A8000_sd-card_insert, 1, --_--]
Figure 6-53 CP-8000, CP-802x - Inserting SD-Card
Put the SD card in the slot and press carefully until it engages.
6.6.1.2 Removing the SD Card

Disconnect the device from the supply voltage and wait for at least 30 s.
Push the SD card carefully until it is disengaged and springs out of the slot. The SD card can now be removed.
6.6.2 SIM Card (CP-8022 only)
CP-8022 needs a SIM card for the communication via GPRS. This will be supported by your mobile network
provider.
You find further information in section 7.4.2 SIM Card (only CP-8022).

DC8-037-2, Edition 11.2020
6.6 Memory Cards
NOTE
i Do not insert or remove the SIM card during operation of the device. This can damage the SIM card and the
device!
Please consider that the SIM card supports the required temperature range. Such kind of SIM cards are
frequently managed under the tariff M2M.
6.6.2.1 Inserting the SIM Card

In CP-8022 the SIM card is inserted in the front of the device.
[dw_CP-8022_sim_card_slot, 1, --_--]
Figure 6-54 CP-8022 - Inserting the SIM-Card
Put the SIM card into the corresponding slot and press carefully until it engages.
6.6.2.2 Removing the SIM Card

Disconnect the device from the supply voltage and wait for at least 30 s.
Push the SIM card carefully until it is disengaged and springs out of the slot. The SIM card can now be
removed.

DC8-037-2, Edition 11.2020
6.7 Wiring
6.7 Wiring
Due to the power dissipation in the device there is a higher temperature on the terminals than the device
ambient temperature. This increase is maximum 15°C with full load. For this reason the isolation of the wires
must withstand a higher temperature than the device environment temperature (see example for
6.7.2 Process Peripherals).
6.7.1 Power Supply
CP-8000 has an integrated power supply module (see 5.3.1 PS-8630 (Internal to CP-8000)).
• The supply can be performed via a station battery or series power units.
• For the fuse protection a circuit breaker 2-pole 2 A, characteristic C is prescribed (standard type: Siemens
5SY5 202-7).
CP-802x needs an external power supply module PS-862x or PS-864x (see 5.3.2 PS-8620, PS-8622 and
5.3.3 PS-8640, PS-8642).
• The supply can be performed via a station battery or series power units.
• PS-8642 can be supplied optionally via the public low-voltage network.
• Furthermore, 2 redundant power supply modules can be used (PS-862x as of production level CC).
• For the fuse protection of PS-862x a circuit breaker 2-pole with 2 A, characteristic C is prescribed
(standard type: Siemens 5SY5 202-7)
• For the fuse protection of PS-864x a circuit breaker 2-pole with 10 A, characteristic C is prescribed
(standard type: Siemens 5SY5 210-7).
You can establish the supply with single leads of the type H07V-K (1.5 to 2.5 mm²) or a cable of the type LA-
YY-0 (2 x 1.5 to 2.5 mm²) or H05VV-F 3G (1.5 to 2.5 mm²).
Recommended and tested series power units (standard types) can be found in the Appendix A.7 Recom-
mended Upstream Power Supply Devices.
6.7.2 Process Peripherals
Cabinet-internal wiring is preferably carried out with plastic-insulated cables according to DIN VDE 298 T4
2/89. Use only copper wires.
You can establish the connections with single leads of the type H05V-K or H05V2-K (0.5 to 1 mm²), as well as
H07V-K or H07V2-K (1.5 to 2.5 mm²).
Max. ambient temperature Max. terminal temperature Wire type

55°C 70°C H05V-K, H07V-K
70°C 85°C H05V2-K, H07V2-K
Conductor size, ampacity, and temperature rating per the National Electrical Code.
• If a wire bridge with 0.75 mm² is used or a bridged comb, the cable cross section is limited to 1.5 mm².
• The construction of the peripheral connectors is designed for direct peripheral wiring. That means, that
the wiring can be carried out without the use of a routing terminal or other additional screw terminals.
• Removable screw terminals are used as peripheral connectors. These are attached to the device for
delivery. Optionally spring-loaded- or crimp terminals can be used.
• Preferably wire end sleeves are to be used.
• A cable duct is to be provided for the wiring of the process signals.

DC8-037-2, Edition 11.2020
6.7 Wiring
6.7.3 Shielding
CP-8000/CP-802x is designed in order that no shielded cables are necessary.

Normally, shielded cables are strain-relieved directly after the cabinet/rack entry and then grounded on a
large-surface screening rail installed for this purpose. The device itself provides no possibility of shield
clamping.
[ph_grounded_cable, 1, --_--]
Figure 6-55 Shield Clamping of Cable
6.7.4 Protective Earth/Ground
When installing CP-8000/CP-802x, it is to be ensured that the cabinet or rack used has proper protective earth
and ground. That means, that all electrical conducting parts must be connected large-surface and as short as
possible with the existing grounding system.
If these preconditions exist, the grounding of the device takes place via the connection of the DIN rail with the
cabinet spar. A reliable connection is achieved by using screws with contact washers.

DC8-037-2, Edition 11.2020
6.8 Switching the Device On and Off
6.8 Switching the Device On and Off

Before switching the device on it must be connected to the designated power supply.
Switching on takes place by connecting the voltage at the corresponding connector (X12/CP-8000, X1/
PS-862x, X1/PS-864x), commonly by switching on a miniature circuit breaker (details see 6.7.1 Power Supply).
The circuit breaker must be arranged at a suitable location, simply accessible to the user, close to the device,
and be marked as disconnector for the device.
SICAM I/O Modules which are connected to the Master Module are switched on and off by the Master Module.
The device starts up automatically. It is operational (without error display), as soon as all connected modules
have concluded the startup. The startup time is dependent on the loaded data on the SD card and may last up
to 15 minutes. Pay attention to the status display during and after startup. You will find the details therreto in
section 11.4 Checks and System Displays.
The switching off of the device takes place by disconnecting the power supply.
! CAUTION
Switching off during writing operations to the SD card (load firmware, load parameters) is to be avoided
without fail.
² The data on the SD card could be destroyed as a result.

DC8-037-2, Edition 11.2020
6.9 Setup of External Communication Connections

Via the communication interfaces of CP 8000/CP 802x selected transmission facilities can be connected.
Depending on the kind of the selected communication type, different connection cables, plugs, and, if
needed, converters, are required for the connection of a data transmission facility.
Connection type Communication type Transmission Facility Connection cable
Serial Multi-point traffic • Interface converter See section
6.9.1.1 Communication via
(X2, X3, X6) • Leased line modem
Interface Converter
• VFT channel modem
siehe 6.9.1.2 Multi-Point
Traffic via Leased Line
Modem/VFT Channel
Modem
Multi-point traffic via glass • RS-232–LWL converter See section 6.9.1.3 Multi-
fiber optic Point Traffic via Glass Fiber
• Optional star coupler
Optic
Dial-up traffic analog Westermo TD-36, TDW-33 See section 6.9.1.4 Dial-
with external supply Up Traffic Analog with
Westermo TD-36 (TDW-33)
Dial-up traffic ISDN Westermo IDW-90 with See section 6.9.1.5 Dial-
external supply Up Traffic ISDN with West-
ermo IDW-90
Dial-up traffic GSM Cinterion MC52iT See section 6.9.1.6 Dial-Up
Traffic GSM; SMS Sender/
Receiver
SMS MC Technologies MC55iw See section 6.9.1.6 Dial-Up
Traffic GSM; SMS Sender/
Receiver
Point-to-point traffic See section 6.9.1.7 Point-
to-Point Traffic with Other
AU
Ethernet TCP/IP LAN/WAN See section
(X1, X4) 6.9.2.1 Communication via
LAN/WAN
GPRS • Internal (CP-8022) See section
6.9.2.2 Communication via
• M874-2 GPRS Modem
GPRS
• MD741-1 GPRS Router
Order information for transmission facilities and cables see appendix A.6 Transmission Facilities and
A.8 Cables and Plugs.
NOTE
i Communication cables are, if possible, to be installed separately from the supply and peripheral cables.

DC8-037-2, Edition 11.2020
! CAUTION
It is not permitted to connect a serial port (e.g. X2) with an Ethernet interface (e.g. switch) and vice versa..
² With the RJ45 interfaces, pay attention to the designation on the device (ETH = Ethernet, RS-232 =
serial).
6.9.1 Serial Communication
6.9.1.1 Communication via Interface Converter

Using an external interface converter is required to connect devices with RS-485/RS-422 to interface X2
(RS-232). If devices with MODBUS RTU or with IEC 60870-5-103 are connected, Siemens recommends the use
of PHOENIX PSM-ME-RS232/RS485-P. Refer to Recommended Third-Party Products, Page 1853 for order infor-
mation.
CP-8000
[dw_CP-8000_connection_rs232_psm-me-rs232_rs485, 1, en_US]
Figure 6-56 CP-8000 – Connection to Interface Converter via Adapter
Wiring for CP-8000 Connection – Interface Converter
[dw_CP-8000_circuitry_rs232_psm-me_adapt, 1, en_US]
Figure 6-57 CP-8000 – Wiring of the Cable to Interface Converter via Adapter

DC8-037-2, Edition 11.2020
Variant via D-Sub Connection Cable
[dw_CP-8000_circuitry_rs232_psm-me_direct, 1, en_US]
Figure 6-58 CP-8000 – Wiring of the Cable to Interface Converter
NOTE
i With a serial connection via X2, a bridge is required between CTS and GND, as far as the interface shall also
be used for the connection with the engineering PC.
With a special parameter (Communication settings serial | Serial engineering inter-
face = disabled), you can define that interface X2 is not used for engineering. Thus no connection
between CTS and GND is required.
Recommended D-Sub/RJ45 Adapter

RS Pro MHDA9-SMJ8-M-K (see appendix Recommended Third-Party Products, Page 1858). This adapter provides
a wired RJ45 socket and an unwired D-sub plug (female).
Pinning of the RJ45 socket (wire colors valid for MHDA9-SMJ8-M-K):

Pin Wire Color Pin Assignment at RJ45 Socket
1 black
2 yellow
3 orange
4 red
5 green
6 brown
7 grey Figure 6-59 D-Sub/RJ45 Adapter –
8 blue RJ45 Pins
Shield black
Wiring at the 9-pole D-sub plug:

Pins at the D-sub plug can be assigned according to wiring diagram.
[dw_A8000_dsub_rj45_adapter_dsub_pin_assignment, 1, en_US]
Figure 6-60 D-Sub/RJ45 Adapter – D-Sub Pins

DC8-037-2, Edition 11.2020
Unused wires must be isolated!

When using the shield, it must be soldered to the metal plate of the D-sub plug.
Configuration of the PHOENIX PSM-ME-RS232/RS485-P-2744416

The interface converter must be configured for operation as an RS-485 interface. For instructions, see the
package leaflet. This is also availble via https://www.phoenixcontact.com.
NOTE
i Use the PHOENIX converter in Self Controlled Mode.
CP-802x
[dw_CP-802x_connection_rs232_psm-me-rs232_rs485, 1, en_US]
Figure 6-61 CP-802x – Connection to Interface Converter via Adapter
Wiring for CP-802x Connection – Interface Converter
[dw_CP-802x_circuitry_rs232_psm-me, 1, en_US]
Figure 6-62 CP-802x – Wiring of Cable to Interface Converter via Adapter

DC8-037-2, Edition 11.2020
NOTE

6.9.1.2 Multi-Point Traffic via Leased Line Modem/VFT Channel Modem
CP-8000
[dw_CP-8000_connection_rs232_ce-070x, 1, en_US]
Figure 6-63 CP-8000 – Connection to CE-070x

DC8-037-2, Edition 11.2020
Wiring for TC6-210 Cable
[dw_CP-8000_circuitry_rs232_ce-070x, 1, en_US]
Figure 6-64 CP-8000 – Wiring of Modem Cable to CE-070x
NOTE
CP-8021
[dw_CP-802x_connection_rs232_ce-070x, 1, en_US]
Figure 6-65 CP-802x – Connection to CE-070x

DC8-037-2, Edition 11.2020
Wiring for Modem Cable
[dw_CP-802x_circuitry_rs232_ce-070x, 1, en_US]
Figure 6-66 CP-802x – Wiring of Modem Cable to CE-070x
NOTE
With a special parameter ( Communication settings serial | Serial engineering inter-

DC8-037-2, Edition 11.2020
6.9.1.3 Multi-Point Traffic via Glass Fiber Optic
CP-8000
Connection via CM-0847 and Star Coupler to Other AU
[dw_CP-8000_connection_rs232_opt_star_cm-0847, 2, en_US]
Figure 6-67 CP-8000 – Connection via CM-0847 and Star Coupler to Other AU
NOTE
i • CM-0847 replaces CM-0827 which is used in existing plants.
• A maximum of 6 star couplers (CM-0822) may be attached next to each other.

DC8-037-2, Edition 11.2020
Wiring for CP-8000 Connection – CM-0847 Fiber Optic Interface
[dw_CP-8000_circuitry_rs232_cm-0847, 1, en_US]
Figure 6-68 CP-8000 – Wiring of Connection Cable to CM-0847
Wiring for CP-8000 Connection – CM-0827 Fiber Optic Interface (Existing Plants)
[dw_CP-8000_circuitry_rs232_cm-0827, 1, en_US]
Figure 6-69 CP-8000 – Wiring of Connection Cable to CM-0827
NOTE
With a special parameter ( Communication settings serial | Serial engineering inter-


DC8-037-2, Edition 11.2020
CP-802x
Connection via CM-0847 to Other AU
[dw_CP-802x_connection_rs232_opt_p2p_cm-0847, 1, en_US]
Figure 6-70 CP-802x – Connection via CM-0847 to Other AU
NOTE
i • The light idle state on the optical interface can be adjusted on the CM-0847 with the switch to set the
optical line idle state.
• The setting for the light idle state must be set identically on both sides of the optical cable!

DC8-037-2, Edition 11.2020
Connection via D-Sub/RJ45 Adapter and 7XV5652 Converter to Other AU
[dw_CP-802x_connection_rs232_opt_p2p_7xv5652_adapter, 1, en_US]
Figure 6-71 CP-802x – Connection via D-Sub/RJ45 Adapter and 7XV5652 Converter to Other AU
NOTE
i • The light idle-state on the optical interface can be adjusted on the 7XV5652 converter using the S1/8
switch (light idle state ON or light idle state OFF).
• The setting for the light idle state must be set identically on both sides of the optical line!
• Changing the light idle state does not affect the wiring!

DC8-037-2, Edition 11.2020
Wiring for CP-802x/X2 – 7XV5652 Connection
[dw_CP-802x_circuitry_rs232_x2_7xv5652, 1, en_US]
Figure 6-72 CP-802x – Wiring of Connection Cable to 7XV5652 (X2)
Wiring for CP-8022/X6 – 7XV5652 Connection
Figure 6-73 CP-8022 – Wiring of Connection Cable to 7XV5652 (X6)
NOTE

RS Pro MHDA9-PMJ8-M-K (see appendix Recommended Third-Party Products, Page 1858). This adapter provides
a wired RJ45 socket and an unwired D-sub plug (male).

DC8-037-2, Edition 11.2020
Connection via CM-0847 and 7XV5450 Star Coupler to Other AU
[dw_CP-802x_connection_rs232_opt_star_7xv5450, 1, en_US]
Figure 6-74 CP-802x – Connection via CM-0847 and 7XV5450 Star Coupler to Other AU
NOTE
i • The 7XV5450 mini star coupler must be set on all channels to light idle state OFF (DIP switch) as other-
wise the communication is blocked for all channels in the event of a substation failure or restart
and/or in the event of a defect fiber optic cable.
• If a channel has not been used at the 7XV5450 mini star coupler, the light idle state must be set to
OFF on this channel (DIP switch), as otherwise the communication via the mini star coupler is blocked
for all channels.

DC8-037-2, Edition 11.2020
Connection via D-Sub/RJ45 Adapter and 7XV5450 Star Coupler to Other AU
[dw_CP-802x_connection_rs232_opt_star_7xv5450_adapter, 1, en_US]
Figure 6-75 CP-802x – Connection via D-Sub/RJ45 Adapter and 7XV5450 Star Coupler to Other AU

DC8-037-2, Edition 11.2020
NOTE
i • The 7XV5450 mini star coupler must be set on all channels to light idle state OFF (DIP switch) as other-
• If a channel is not used on the 7XV5450 mini star coupler, the light idle state must be set to OFF on
this channel (DIP switch), as otherwise the communication via the mini star coupler is blocked for all
channels.
• If the 7XV5450 mini star coupler is connected via the RS-232 interface, then the R1/T1 optical inter-
face of the mini star coupler cannot be used.
At the 7XV5450 mini star coupler, set “Enhanced mode”, “Cascading star structure” and “RS232 inter-
face such that they can be activated by bridge 7-8 in the cable”.

DC8-037-2, Edition 11.2020
NOTE

Connection to SIPROTEC 5 via Star Coupler 7XV5450
[dw_CP-802x_connection_rs232_opt_star_7xv5450_sip5, 1, en_US]
Figure 6-78 CP-802x – Connection to SIPROTEC 5 via Star Coupler 7XV5450

DC8-037-2, Edition 11.2020
NOTE
i • Do not connect protection device slaves to the T1/R1 connector of the 7XV5450 mini star coupler.
T1/R1 is used for connection with the central station or other star couplers in a star or ring structure.
• The 7XV5450 mini star coupler must be set on all channels to light idle state OFF (DIP switch) as other-
• If a channel has not been used on the 7XV5450 mini star coupler, the light idle state must be set to
for all channels.
Connection via SIPROTEC 5 via 7XV5450 Star Coupler (Cascaded in Star Structure)
[dw_CP-802x_connection_rs232_opt_casc_star_7xv5450_sip5, 1, en_US]
Figure 6-79 CP-802x – Connection to SIPROTEC 5 via Star Coupler 7XV5450 (Star (Structure)

DC8-037-2, Edition 11.2020
NOTE
i • 33 mini star coupler units are required to connect 100 protection devices with the 7XV5450 mini star
coupler (cascaded in star structure).
With 32 mini star couplers, it is possible to use 3 optical interfaces each and 4 optical interfaces on the
last mini star coupler in the star structure to connect protection devices [32⋅3 + 1⋅4 = 100]. The other
optical interfaces are required to cascade the mini star couplers. If the master is connected with
RS-232 to the mini star coupler, then 1 optical interface remains unused.
• Do not connect protection device slaves to the T1/R1 connector of the 7XV5450 mini star coupler.
• If a channel has not been used on the 7XV5450 mini star coupler, the light idle state must be set to
for all channels.

DC8-037-2, Edition 11.2020
Connection to SIPROTEC 5 via 7XV5450 Star Coupler (Cascaded in Ring Structure)
[dw_CP-802x_connection_rs232_opt_ring_7xv5450_sip5, 1, en_US]
Figure 6-80 CP-802x – Connection to SIPROTEC 5 via 7XV5450 Star Coupler (Ring Structure)

DC8-037-2, Edition 11.2020
NOTE
i • 25 mini star coupler units are required to connect 100 protection devices with the 7XV5450 mini star
coupler (cascaded in ring structure).
Use 4 optical interfaces per mini star coupler to connect protection devices [25⋅4 = 100] – 1 optical
interface per mini star coupler is required to cascade the mini star couplers.
• Do not connect protection device slaves to the T1/R1 connector of the 7XV5450 mini star coupler.
• Redundant central stations are not supported with 7XV5450 mini star couplers in a cascaded ring
structure.
for all channels.

DC8-037-2, Edition 11.2020
Connection via 7XV5450 Star Coupler and 7XV5652 Converter to Other AU (Star Structure)
[dw_CP-802x_connection_rs232_opt_star_7xv5450_7xv5652, 1, en_US]
Figure 6-81 CP-802x – Connection via 7XV5450 Star Coupler and 7XV5652 Converter to Other AU (Star
Structure)

DC8-037-2, Edition 11.2020
NOTE
i • This configuration with converters applies if the complete communication infrastructure is already
available. Alternatively, a CM-0847 can be used in the substations instead of the optical converter
RS232-FO 7XV5652.
• The 7XV5450 mini star coupler must be set on all channels to light idle state OFF (DIP switch (DIP
switch) as otherwise the communication is blocked for all channels in the event of a substation failure
or restart and/or in the event of a defect fiber optic cable.
for all channels.

DC8-037-2, Edition 11.2020
NOTE

6.9.1.4 Dial-Up Traffic Analog with Westermo TD-36 (TDW-33)
CP-8000
[dw_CP-8000_connection_rs232_analog_td36, 2, en_US]
Figure 6-84 CP-8000 – Connection with Westermo TD36

DC8-037-2, Edition 11.2020
[dw_CP-8000_circuitry_rs232_analog_td36, 2, en_US]
Figure 6-85 CP-8000 – Wiring of Westermo TD36 Modem Cable
NOTE
face), you can define that interface X2 is not used for engineering. Thus no connection between CTS and
GND is required.
6.9.1.5 Dial-Up Traffic ISDN with Westermo IDW-90
CP-8000
[dw_CP-8000_connection_rs232_isdn_idw90, 2, en_US]
Figure 6-86 CP-8000 – Connection with Westermo IDW90

DC8-037-2, Edition 11.2020
[dw_CP-8000_circuitry_rs232_isdn_idw90, 2, en_US]
Figure 6-87 CP-8000 – Wiring of Westermo IDW90 Modem Cable
NOTE
GND is required.
6.9.1.6 Dial-Up Traffic GSM; SMS Sender/Receiver
Modem Protocol Description

Cinterion MC52iT DIAST0 Data transmission via GSM with CSD Service (Circuit Switched Data)
MC Technologies MC55iw SMST0 SMS Sender/Receiver

DC8-037-2, Edition 11.2020
CP-8000
[dw_CP-8000_connection_rs232_gsm_mc55iw, 2, en_US]
Figure 6-88 CP-8000 – Connection with Cinterion MC55iT
[dw_CP-8000_circuitry_rs232_gsm_mc55iw, 2, en_US]
Figure 6-89 CP-8000 – Wiring of Cinterion MC55iT Modem Cable
NOTE
GND is required.

DC8-037-2, Edition 11.2020
6.9.1.7 Point-to-Point Traffic with Other AU
CP-8000
[dw_CP-8000_connection_rs232_direct_au, 1, en_US]
Figure 6-90 CP-8000 – Connection to Direct AU
Wiring for D-Sub – RJ45 Connection (for example, SICAM AK 3)
[dw_CP-8000_circuitry_rs232_ak_3, 1, en_US]
Figure 6-91 CP-8000 – Wiring of Cable to Direct AU (SICAM AK 3)

DC8-037-2, Edition 11.2020
Wiring for D-Sub – D-Sub Connection (for example, CP-8000)
[dw_CP-8000_circuitry_rs232_cp-8000, 1, en_US]
Figure 6-92 CP-8000 – Wiring of Cable to Direct AU (CP-8000)
NOTE
CP-802x
[dw_CP-802x_connection_rs232_direct_au, 1, en_US]
Figure 6-93 CP-802x – Connection to Direct AU

DC8-037-2, Edition 11.2020
Wiring for RJ45 – RJ45 Connection (for example, SICAM AK 3)
[dw_CP-802x_circuitry_rs232_ak_3, 1, en_US]
Figure 6-94 CP-802x – Wiring of Cable to Direct AU (SICAM AK 3)
Wiring for RJ45 – D-Sub Connection (for example, CP-8000)
[dw_CP-802x_circuitry_rs232_cp-8000, 1, en_US]
Figure 6-95 CP-802x – Wiring of Cable to Direct AU (CP-8000)
NOTE

DC8-037-2, Edition 11.2020
6.9.2 Ethernet TCP/IP
6.9.2.1 Communication via LAN/WAN
[dw_CP-8000_802x_connection_lan, 1, en_US]
Figure 6-96 CP-8000, CP-802x – Connection via LAN
You will find more detailed information on the network configuration in the Appendix E Use Cases.
NOTE
i Depending on whether a connection is done inside or outside of cabinets, different types of patch cables
must be used.
You can find details on connections over 10 m in the manual SICAM RTUs Platforms Configuration Automation
Units and Automation Networks, Appendix A; section Electrical Connection, Cable longer than 10 m.

DC8-037-2, Edition 11.2020
6.9.2.2 Communication via GPRS
CP-8000, CP-8021
[dw_CP-8000_8021_connection_gprs, 1, en_US]
Figure 6-97 CP-80000, CP-8021 - Connection via GPRS
CP-8022
[dw_CP-8022_connection_gprs, 1, en_US]
Figure 6-98 CP-8022 - Connection via GPRS

DC8-037-2, Edition 11.2020
DC8-037-2, Edition 11.2020
7 Preparing Engineering
This chapter describes the methods to parameterize and program CP-8000/CP-802x and the prerequisites that
must be met in this process.
NOTE
i Graphics and screenshots in this chapter refer to the engineering of CP-8000. These correspondingly also
apply to CP-8021 and CP-8022.
7.1 Engineering Tools 294

7.2 Engineering Software 295
7.3 Loadable Firmwares 299
7.4 Memory Cards 301
7.5 Communication Interfaces 303
7.6 Connect Engineering PC with the Target System 304
7.7 Interaction with Engineering Tool 322

DC8-037-2, Edition 11.2020
Preparing Engineering
7.1 Engineering Tools
7.1 Engineering Tools

CP-8000/CP-802x is a parameter-settable miniature telecontrol device with optional automation function. The
engineering is alternatively possible via
• SICAM TOOLBOX II, with tool OPM II
• SICAM WEB
• SICAM Device Manager
7.1.1 Differences
For the engineering via SICAM WEB no special knowledge of an engineering system is required, and also no
licenses. The web user interface makes a very simple access to the parameter-setting of CP-8000/CP-802x.
The structure of the parameter blocks is basically identical structured like in the SICAM TOOLBOX II, an excep-
tion is the parameterization of the periphery (not consistent).
The engineering via SICAM WEB is useful for simple applications. Not all the functions offered by the
SICAM TOOLBOX II are available. You can find more details thereto in section 7.7.2.9 Exceptions with Engi-
neering via SICAM WEB.
You find an overview of the respective functions in the chapters 8 Engineering via SICAM TOOLBOX II and
9 Engineering via SICAM WEB.
7.1.2 Interlocking
The writing access to a target device is exclusive. This means, changes of the parameterization of a target
device are only possible with that engineering tool, with which engineering was begun for the first time.
If a target device has been parameterized via SICAM WEB, it is not possible to take over the parameterization
into the SICAM TOOLBOX II. All online tools of the SICAM TOOLBOX II (diagnosis, dataflow test, message simu-
lation, etc.) can not be used.
If a target device has been parameterized via the SICAM TOOLBOX II, there is only a reading access possible via
SICAM WEB (change of parameters not possible). The online functions (diagnosis, process display) can be used
in this case.
NOTE
i CP-8000/CP-802x is delivered ex factory with an equipped SD card and a default web parameterization. At
the moment that you load SICAM TOOLBOX II parameters, the access via SICAM WEB is only reading (role
guest).

DC8-037-2, Edition 11.2020
7.2 Engineering Software
The SICAM TOOLBOX II (as of Version 6.01) is available on a USB stick and consists of the following toolsets:
• “EM II”
Engineering Manager (base package)
• “PSR II”
Engineering and Maintenance Computer
• “OPM II”
Object-Oriented Process Data Manager
• “CAEx plus”
Tool for the creation of an application program as function diagram (FUD), structured text (ST), sequen-
tial function chart (SF)
Alternatively, an existing and compatible instruction list (IL) can be stored in the SICAM TOOLBOX II.
The toolsets are also available as light version. With this version, the engineering is limited to maximal 100
system elements and 2000 data points.
The toolsets are available individually. You find information and updates for the individual toolsets, as well as
numerous licences, on the website https://support.industry.siemens.com.
Document Item number

SICAM TOOLBOX II V6 License Catalog, License Ordering D30-013-6
SICAM TOOLBOX II Release Information V6 M3E-030-2
7.2.1.1 Prerequisites
Prerequisite for the operation of the SICAM TOOLBOX II is the usage of an appropriate PC, that must fulfill
certain hardware requirements, depending on the license package you purchased.
Information thereto reside within a permanently updated List of PC preference types. Should that be not at
your disposal, please consult your contact person at Siemens.
For the installation of the SICAM TOOLBOX II the following preconditions are required:
• USB interface must exist
• C:\ drive must exist
• File system NTFS
• Microsoft Windows 64 bit operating system
• Administrator rights for operating system Microsoft Windows (read and write rights to the file system and
the Windows Registry)
• Installed TCP/IP
• Other SICAM TOOLBOX II version must not be installed
• Other ORACLE applications (data base, client, etc.) must not be installed
• necessary regional settings:

– 'Dot' for decimal separator and 'comma' for the thousand separator must be different
– As separator an 'inverted comma' must not be used
• Usage of Windows Fonts in normal size (96 DPI)
• Microsoft Internet Explorer as of version 6.0

DC8-037-2, Edition 11.2020
• Installated Microsoft Media Player to play online help videos (www.microsoft.com)
• Installated Adobe Acrobat Reader to read related documentation (www.adobe.com)
• Minimum 30 GB free harddisk memory
• Minimum 4 GB installed main memory
Supported Operating Systems and Hardware Requirements

You find the exact information on supported operating systems and hardware, as well as installation and
accomplishment of updates, in the following document:
SICAM TOOLBOX II USB BOX Booklet V6 D3E-021-1
7.2.2 SICAM WEB
For the engineering via SICAM WEB you need the following programs:
Table 7-1 SICAM WEB - required programs
Program Version Designation

CPC80 as of 10.01 (CP-8000) Firmware for the Master Module 63
as of 11.01 (CP-8021, CP-8022
level BB)
as of 12.01 (CP-8022 level CC)
SWEB00 as of 4.2 Firmware SICAM WEB 63 64
Sicam_first_startup as of 2 Initializing tool for the device detection and IP
address setting 63
ASCII text editor for the creation of an instruc-
tion list (IL)
The following web browsers can be used alternatively:
Table 7-2 SICAM WEB - supported Web browsers
Web browser Version Download

Microsoft Internet Explorer as of 11 www.microsoft.com
Microsoft Edge as of 40 www.microsoft.com
Google Chrome (current) support.google.com
Mozilla Firefox (current) www.mozilla.com
Apple Safari (current) support.apple.com
Opera (current) www.opera.com
NOTE
i When accessing a SICAM A8000 device via other web browsers, a warning appears in the logon dialog.
63 further information see 7.3 Loadable Firmwares

64 functionality of a web server as grafical user interface for the engineering

DC8-037-2, Edition 11.2020
For SICAM WEB the following operating systems are supported:
Table 7-3 SICAM WEB - required operating systems
Operating System Hardware

Windows 7 (64-Bit) PC, Notebook
Windows 8 (64-Bit)
Windows Server 2012 (64-Bit)
Android as of version 4 Samsung Galaxy Tab 2 10.1
iOS as of version 6 Apple iPad4
The following minimum screen resolution is recommended:
• 1024 x 768 768 pixel screen resolution (1280 x 800 pixel recommended)
• 16 Bit color depth
• Screen diagonal: 7"
7.2.2.2 Program Sicam_First_Startup

The Sicam_first_startup.exe executable file must have been locally saved on the engineering PC. You can
create a shortcut on the taskbar of the engineering PC to make starting more convenient.
With the Sicam_first_startup program, you can:
• find CP-8000/CP-802x connected in a network
• assign an IP address to a target device
• write a parameter file available on the engineering PC to an SD card (backup of the parameterization of a
target device)
Use an SD card read/write device to copy engineering data and firmwares also without a target device, directly
from the engineering PC to an SD card, for instance to multiply projects.
[dw_A8000_offline_param, 1, en_US]
Figure 7-1 Offline Engineering with Sicam_First_Startup

DC8-037-2, Edition 11.2020
7.2.3 SICAM Device Manager
The SICAM Device Manager package consists of the following parts:
• DVD with software and license agreement
• USB stick with license key
• Product Information
• Certificate of license

SICAM Device Manager S51-000
SICAM Device Manager User Manual D51-007-1
Prerequisite for the operation of the SICAM Device Manager is the usage of an appropriate PC, that must fulfill
certain hardware requirements.
For the installation of the SICAM Device Manager the following preconditions are required:
• USB interface must exist
• DVD drive must exist
• C:\ drive must exist
• File system NTFS
• Microsoft Windows 64 bit operating system
• Administrator rights for operating system Microsoft Windows (read and write rights to the file system and
the Windows Registry)
• Installed TCP/IP
• Enabled DirectX functions
• 30 GB free harddisk memory
• 4 GB installed main memory

The memory requirements and the hard disk space of the operating system and all applications running
parallel to the SICAM Device Manager (Microsoft Office etc.) and/or memory usage of onboard graphic
adapters must be considered.
To make sure that DirectX features are enabled on your PC
• click the Start button, type “dxdiag” in the search box, and then press the enter key
• click the System tab and then, under SYSTEM INFORMATION, check the DirectX version number, e.g.:
DirectX 11
• click Next page
• under DirectX Functions all features must be enabled
Supported Operating Systems and Hardware Requirements

The detailed information on operating systems and hardware, as well as to the installation and execution of
updates, can be found in the following document:
SICAM Device Manager Product Information D51-001-1

DC8-037-2, Edition 11.2020
7.3 Loadable Firmwares

CP 8000/CP 802x consists of system elements that are designed for specific functions
• Master module
Central processing and communication
• Protocols
Communication with control center and further automation units
• I/O Master Module

Acquisition and output of process signals
For the performing of the respective function, a special firmware is provided for each system element. The
functionality of each system element is adjustable by means of parameters.
As a partner of Siemens, you are able to download all the code revisions for your system as loadable binary
files via the website https://support.industry.siemens.com:
• Select > Home > Product Support > Energy > Energy Automation and smart grid > Substation auto-
mation > Substation control systems and remote terminal units (RTU) > SICAM A8000
• Click on the corresponding download link, example: > Download SICAM A8000 CP-8000, CP-8021,
CP-8022 Package V1411
• Open the required package under

– Release Notes
– SICAM WEB Update (registration necessary)
– SICAM TOOLBOX II Update (registration necessary)
• Select the required firmware(s)

Examples:
CPC80 Central Processing/Communication Version: 1411
TBII Update: 80802414.11
SWEB Update: SC8-080-1_1411.bin
UMPMT0 Multipoint Master IEC60870-5-101 Version: 0202
SWEB Update: S26-500-1_0202.bin
USIO81 Universal Signal In-/Output Version: 0702
SWEB Update: SC8-098-1_0702.bin
SWEB00 SICAM WEB Version: 0511
SWEB Update: SWEB0005.F11
NOTE
i An SWEB update contains the firmware code for the engineering via SICAM WEB.
A TB II update contains the firmware code and the master data for engineering via the SICAM TOOLBOX II.
For the parameterization of the corresponding system elements, the respective
• TBII updates must be stored in the SICAM TOOLBOX II (for engineering via SICAM TOOLBOX II)
• SWEB updates must exist in the target device (for engineering via SICAM WEB)

DC8-037-2, Edition 11.2020
How to load firmwares into a target device depends on the used engineering tool:
• SICAM TOOLBOX II: section 8.1.4 Import Firmware and 11.7.1 SICAM TOOLBOX II
• SICAM WEB: section 9.3.7 Update Firmware and 11.7.2 SICAM WEB

DC8-037-2, Edition 11.2020
7.4 Memory Cards
7.4 Memory Cards
7.4.1 SD Card
For the storage of engineering data CP-8000/CP-802x needs an SD card. This resides in the slot at the housing
front (CP-8000) or housing back (CP-802x), refer to section 6.6.1 SD Card.
[ph_sd_card_2gb_big, 1, --_--]
Figure 7-2 SD-Card
With delivery of CP-8000/CP-802x, all required files for the correct operation are stored in folders on the SD
card:
• Firmware SICAM WEB (short text: SWEB00), binary file: SCD-001-1_xy.web
• The Web files for SICAM WEB are unzipped on the SD card in the folder SYSTEM\SICWEB
• The master data for SICAM WEB are unzipped on the SD card in the subfolders of SYSTEM\SICWEB\FW
• Firmware of the device (CPC80), binary file: SC8-080-1_xy.bin
• Optional firmwares for protocols and peripherals
With usage of another suitable SD card, please consider the instruction in section 11.6.4 Replacing the SD
Card.
7.4.1.1 Configurable SD Card Usage

The usage of the SD card in CP-8000/CP-802x can be set by parameter CPC80 | AU common settings |
Security | SD Card Mode.
The following settings are available:
• no updates via SD card allowed but spare part concept active

SD card is used and updates via SD card are disabled.
• spare part concept active and updates via SD card allowed (default setting)
SD card is used and updates via SD card are enabled.
• spare part concept disabled (secure mode)

This setting must be used if no SD card is used (e.g. due to security reasons).
NOTE
i Once the selection has been accepted, the configured mode can no longer be changed.
7.4.1.2 SD Card Reader/Writer

For archiving purposes, the engineering data and firmwares stored on the SD card can be read with a standard
commercially available SD card reader/writer and stored on a PC. It is also possible to write the data from a PC
to the SD card, particularly to initialize a target device.
If applicable, install the required driver software on the PC to use the SD card reader/writer. For this purpose,
follow the instructions of the manufacturer.

DC8-037-2, Edition 11.2020
7.4 Memory Cards
Use the SD Card Formatter formatting tool to format the SD card (https://www.sdcard.org/downloads/
formatter/). The SD card must have been formatted in the FAT16 file system.
7.4.2 SIM Card (only CP-8022)
For the communication via GPRS you need a mobile network provider. This supplies a SIM card (choose the
standard format = Mini SIM). The SIM card must be put in the slot at the housing front, refer to section
6.6.2 SIM Card (CP-8022 only).
[ph_sim_card_2ff, 1, --_--]
Figure 7-3 SIM Card

DC8-037-2, Edition 11.2020
7.5 Communication Interfaces
7.5 Communication Interfaces

CP-8000/CP-802x provides the following interfaces for engineering and maintenance:
Interface Type Engineering tool
X1 Ethernet TCP/IP SICAM TOOLBOX II or SICAM WEB
X2 serial RS-232 65 SICAM TOOLBOX II or SICAM WEB
X4 Ethernet TCP/IP SICAM TOOLBOX II or SICAM WEB
X6 serial RS-232 mode SICAM WEB
X7 GPRS SICAM TOOLBOX II or SICAM WEB
Via the duplicated Ethernet link (X1 and X4 in switch mode) it is for instance possible to connect a local engi-
neering PC and at the same time a GPRS modem for the communication to the central station.
Furthermore, X1 and X4 can be operated via 2 independent IP addresses, you will find examples in appendix
E Use Cases.
NOTE
i For CP-802x applies: X2/pin 3 (supply for external modem) must not be connected with the engineering PC!
NOTE
i If the serial interface X2 is not used for the engineering, this can be set by means of a special parameter
(Communication settings serial | Serial engineering interface = disabled).
The engineering via X2 is then no more possible, however, for the connection of other devices (see
6.9.1 Serial Communication) a simpler cable wiring can be created.
7.5.1 Required Accessories
Depending on the connection type, the following accessories are required:
• Direct cable
• D-sub/RJ45 adapter
• D-sub/USB adapter (if needed)
You will find the order information in appendix A.8 Cables and Plugs.
65 with additional voltage output (supply for external modem)

DC8-037-2, Edition 11.2020
7.6 Connect Engineering PC with the Target System
Before parameters can be loaded via the SICAM TOOLBOX II into CP-8000/CP-802x, the following steps must
be performed:
• Insert a suitable SD card into the target device (if not present)
• Store required TBII updates in the SICAM TOOLBOX II
• Switch on the target device
• Set up physical connection with the target device
The following connection options are available:
• Serial point-to-point connection
• Serial connection via telecommunication facilities
• LAN/WAN connection via Ethernet interface
• LAN/WAN connection via serial interface and terminal server
• Connection via further automation unit(s)
7.6.1.1 Physical Connection
Point-to-Point Connection via Serial Interface

Engineering PC and CP-8000 are connected with a direct cable via the serial interface (X2).
[dw_CP-8000_toolbox_connection_direct_serial, 1, en_US]
Figure 7-4 Connection Engineering PC with CP-8000 Serial Direct

DC8-037-2, Edition 11.2020
Wiring for Connection CP-8000 – PC (Direct Cable)
[dw_CP-8000_circuitry_rs232_engineering_pc, 1, en_US]
Figure 7-5 Wiring for Connection CP-8000 – PC
With CP-802x, a standard patch cable and a D-sub/RJ45 adapter must be used.
[dw_CP-802x_toolbox_connection_direct_serial, 1, en_US]
Figure 7-6 Connection Engineering PC with CP-802x Serial Direct
Wiring for Connection CP-802x – PC (Patch Cable + D-Sub/RJ45 Adapter)
[dw_CP-802x_circuitry_rs232_engineering_pc, 1, en_US]
Figure 7-7 Wiring for Connection CP-802x – PC


DC8-037-2, Edition 11.2020
Table 7-4 Pinning of the RJ45 socket: (wire colors are valid for MHDA9-SMJ8-M-K)
Pin Wire color Assignment of the pins of the RJ45

plug
1 black
2 yellow
3 orange
4 red
5 green
6 browne
7 grey Figure 7-8 D-Sub/RJ45 Adapter -
8 blue RJ45 Pins
Shield black
Wiring on the 9-pin D-sub plug:

The assignment of the pins at the D-sub plug can be made according to wiring diagram.
Figure 7-9 D-Sub/RJ45 Adapter - D-Sub Pins
Not used wires must be isolated!

With use of the shield this must be soldered at the metal plate of the D-sub plug.
NOTE
i If the engineering PC does not provide a serial COM port, additionally a USB/RS-232 converter is required.
Recommend products: FTDI Chip US232R-10 or FTDI Chip US232R-100-BLK (see appendix Recommended
Third-Party Products, Page 1858).
The required driver can be found under http://www.ftdichip.com/Drivers/D2XX.htm

DC8-037-2, Edition 11.2020
Serial Connection via Telecommunication Facilities

Engineering PC and CP-8000 are connected via the serial interface (X2) via modems and alternatively via a
dedicated line, the public fixed network, or wireless radio.
[dw_CP-8000_toolbox_connection_remote_serial, 1, en_US]
Figure 7-10 Connection of Engineering PC with CP-8000 via Telecommunication Facilities
With CP-802x, a special modem cable (or standard patch cable and D-sub/RJ45 adapter) must be used.
[dw_CP-802x_toolbox_connection_remote_serial, 1, en_US]
Figure 7-11 Connection of Engineering PC with CP-802x via Telecommunication Facilities
NOTE
i The circuitry of the modem cable (alternatively D-sub/RJ45 adapter) is dependent on the used modem. You
will find the corresponding circuitries in section 6.9.1 Serial Communication.

DC8-037-2, Edition 11.2020
LAN/WAN Connection via Ethernet Interface

Engineering PC and CP-8000 are connected via one of the Ethernet interfaces (X1 or X4) via a network by
means of standard patch cables.
[dw_CP-8000_toolbox_connection_remote_ethernet, 1, en_US]
Figure 7-12 Connection Engineering PC with CP-8000 via Ethernet LAN/WAN
Engineering PC and CP-802x are connected via one of the Ethernet interfaces (X1 or X4) via a network by
means of standard patch cables.
[dw_CP-802x_toolbox_connection_remote_ethernet, 1, en_US]
Figure 7-13 Connection Engineering PC with CP-802x via Ethernet LAN/WAN

DC8-037-2, Edition 11.2020
LAN/WAN Connection via Serial Interface and Terminal Server

Engineering PC and CP-8000 are connected via the serial interface (X2) via a network and a terminal server.
[dw_CP-8000_toolbox_connection_remote_terminalserver, 1, en_US]
Figure 7-14 Connection Engineering PC with CP-8000 via LAN/WAN and Terminal Server
NOTE
i The circuitry of the direct cable is described in section Point-to-Point Connection via Serial Interface,
Page 304.
With CP-802x, a standard patch cable and a D-sub/RJ45 adapter must be used for the connection with the
terminal server.
[dw_CP-802x_toolbox_connection_remote_terminalserver, 1, en_US]
Figure 7-15 Connection Engineering PC with CP-802x via LAN/WAN and Terminal Server
NOTE
i The circuitry of the D-sub/RJ45 adapter is described in section Point-to-Point Connection via Serial Interface,
Page 304.

DC8-037-2, Edition 11.2020
Remote Connection via further Automation Unit(s)

In need, the SICAM TOOLBOX II can also be connected indirectly via a connected automation unit
(SICAM AK 3, SICAM TM).
For engineering there must be a logical connection to that automation unit, which is subject of the engi-
neering task. The both following cases are differentiated:
• Connection with a local automation unit (that one, to which a physical connection exists)
NOTE
i A first initialization of the automation unit is only possible in this way.
• Connection with a remote automation unit that one, which can be accessed via a local automation unit;
thereby, a continuous remote communication according to IEC 60870-5-101 or -104 is required)
[dw_CP-8000_toolbox_connection_remote_au, 1, en_US]
Figure 7-16 Connection Engineering PC with CP-8000 via further Automation Unit(s)

DC8-037-2, Edition 11.2020
7.6.2 SICAM WEB
Before CP-8000/CP-802x can be parameterized via SICAM WEB, the following steps must be performed:
• Insert a suitable SD card with the current firmware codes into the target device (if not present)
• Switch on the target device
• Set up physical connection with the target device
• Establish communication with the target device

– Set up IP configuration on the engineering PC
– Set up dial-up connection on the engineering PC (if necessary)
– Install security certificate on the engineering PC (if necessary)
instruction thereto see www.siemens.com/gridsecurity, tab Cyber Security General Downloads,
directory Application Notes, document Certificate trusting in web browsers
– Connect with the target device via web browser
The following connection options are available:
• Point-to-point connection via serial interface
• Point-to-point connection via Ethernet interface
• LAN/WAN connection via Ethernet interface
7.6.2.1 Physical Connection

Engineering PC and CP-8000 are connected via the serial interface (X2) with a direct cable.
[dw_CP-8000_sicamweb_connection_direct_serial, 1, en_US]
Figure 7-17 Connection Engineering PC with CP-8000 Serial Direct

DC8-037-2, Edition 11.2020
Wiring for Connection CP-8000 – PC (Direct Cable)
[dw_CP-8000_circuitry_rs232_engineering_pc, 1, en_US]
Figure 7-18 Wiring for Connection CP-8000 – PC
With CP-802x, a standard patch cable and a D-sub/RJ45 adapter must be used.
[dw_CP-802x_sicamweb_connection_direct_serial, 1, en_US]
Figure 7-19 Connection Engineering PC with CP-802x Serial Direct
Wiring for Connection CP-8000 – PC (Patch Cable + D-Sub/RJ45 Adapter)
[dw_CP-802x_circuitry_rs232_engineering_pc, 1, en_US]
Figure 7-20 Wiring for Connection CP-802x – PC


DC8-037-2, Edition 11.2020
Table 7-5 Pinning of the RJ45 socket (wire colors are valid for MHDA9-SMJ8-M-K)
Pin Wire color Assignment of the pins on the RJ45

plug
1 black
2 yellow
3 orange
4 red
5 green
6 browne
7 grey Figure 7-21 D-Sub/RJ45 Adapter -
8 blue RJ45 Pins
Shield black
Wiring on the 9-pin D-sub plug:

The assignment of the pins at the D-sub plug can be made according to wiring diagram.
Figure 7-22 D-Sub/RJ45 Adapter - D-Sub Pins

NOTE
i If the engineering PC does not provide a serial COM port, additionally a USB/RS-232 converter is required.
Recommend products: FTDI Chip US232R-10 or FTDI Chip US232R-100-BLK (see appendix Recommended
Third-Party Products, Page 1858).
The required driver can be found under http://www.ftdichip.com/Drivers/D2XX.htm
Point-to-Point Connection via Ethernet Interface

The parameterization via point-to-point is suitable if the engineering PC and the target device are not operated
in a network.
Engineering PC and CP-8000 are connected with a cross connected patch cable via one of the Ethernet inter-
faces (X1 or X4).
[dw_CP-8000_sicamweb_connection_direct_ethernet, 1, en_US]
Figure 7-23 Connection Engineering PC with CP-8000 via Ethernet Direct

DC8-037-2, Edition 11.2020
Engineering PC and CP-802x are connected with a cross connected patch cable via one of the Ethernet inter-
faces (X1 or X4).
[dw_CP-802x_sicamweb_connection_direct_ethernet, 1, en_US]
Figure 7-24 Connection Engineering PC with CP-802x via Ethernet Direct

The parameterization via LAN/WAN is suitable if the engineering PC and (several) CP-8000/CP-802x are oper-
ated in a network.
Engineering PC and CP-8000 are connected with a cross connected patch cable via one of the Ethernet inter-
faces (X1 or X4).
[dw_CP-8000_sicamweb_connection_remote_ethernet, 1, en_US]
Figure 7-25 Connection Engineering PC with CP-8000 via Ethernet LAN/WAN
Engineering PC and CP-802x are connected with a cross connected patch cable via one of the Ethernet inter-
faces (X1 or X4).
[dw_CP-802x_sicamweb_connection_remote_ethernet, 1, en_US]
Figure 7-26 Connection Engineering PC with CP-802x via Ethernet LAN/WAN

DC8-037-2, Edition 11.2020
7.6.2.2 Communication with the Target Device

For the parameterization the target device must be connected with the engineering PC and switched on. In
the Master Module of the target device a SD card must be equipped.
The establishing of a communication connection between engineering PC and the target device takes place
via adjustable IP addresses. For the initial parameter setting of CP-8000/CP-802x, default IP addresses are avail-
able. These are specific for the respective physical connection.
With local engineering, fixed IP addresses are used since they are required only temporarily for the parameteri-
zation of the target device.
Table 7-6 Default IP Configuration in CP-8000/CP-802x
Parameter Value Meaning/Remark

<Own IP address> 172.16.0.1 Address of CP-8000/CP-802x web
server via serial interface X2 (fixed)
Autoconfiguration NO Configuration via DHCP service
deactivated
Mode of the Ethernet ports 1 IP address (connected Common IP address ON Ethernet
ports in switch mode) interfaces X1 and X4
Parameter “Mode of the display (selection) Mode for X1 and X4 can be
Ethernet ports” selected (configuration of separate
IP addresses enabled)
Own IP address 172.16.0.3 Address of CP-8000/CP-802x web
server via Ethernet interface X1
and X4
Subnet mask 255.255.255.0 0.0.0.0 = not used
Default gateway 0.0.0.0 0.0.0.0 = not used
In practice the default gateway is
assigned on the smallest (193) or
greatest (222) usable IP address in
the network.
If the own network is connected via
a router, the address of the router
is to be set.
Network connection LAN Utilized transmission media

The following steps are necessary:
• Configure IP address for engineering PC
• Connection setup via SICAM WEB
Configure IP Address for Engineering PC

For the parameter setting the IP addresses predefined in CP-8000/CP-802x are used. Thereby the web server of
the target device assignes automatically the IP address 172.16.0.2 to the engineering PC, if this is config-
ured for the automatic acceptance of an IP address. For the communication via the serial interface, a dial-up
connection must be set up on the engineering PC. You find the instruction thereto in Appendix D Setting Up a
Dial-Up Connection.
Connection via SICAM WEB

Start the web browser and enter the IP address of your target device (172.16.0.1) in the address bar.

DC8-037-2, Edition 11.2020
When the connection is established, the logon dialog is opened.
[sc_logon, 1, en_US]
Figure 7-27 SICAM WEB - Logon Dialog
You find the further information in chapter 9 Engineering via SICAM WEB.
Point-to-Point Connection via Ethernet Interface

• Configure IP address for engineering PC
Configure IP Address for Engineering PC

For the parameter setting the engineering PC must be adjusted corresponding to the IP address predefined in
CP-8000/CP-802x.
• Click in the control panel of the engineering PC on Network connections, after that on Local Network
and Properties
• Mark in the property dialog Internet Protocol (TCP/IP) and click on Properties
• Select USE THE FOLLOWING IP ADDRESS: and enter for instance 172.16.0.4 and the subnet mask
255.255.0.0 and confirm with OK
• Confirm the network setings with OK

Start the web browser and enter the IP address of your target device (172.16.0.3) in the address bar.

DC8-037-2, Edition 11.2020
NOTE
i According to the parameterization in CP-8000/CP-802x you have to enter a http- or https-address in the
browser to establish the connection.
During the first time connetion establishment via https there is a check if the corresponding security certifi-
cate is installed. If it is missing, it must be installed manually (see www.siemens.com/gridsecurity, tab
Cyber Security General Downloads, directory Application Notes, document “Certificate trusting in web
browsers”).

• Writing IP address with Sicam_first_startup
Configure IP Address with Sicam_first_startup

With operation in a network, an unambiguous IP address must be assigned to each connected CP-8000/
CP-802x. The assignment of the IP address is dependent on the subnet mask used in the network.
in the network. The identification for the assignment of the IP address happens solely via the MAC address of
the target device. This is printed on the type plate at the left side of the housing, or it can be read also on the
display (CP-8000) under the menu Device information.
NOTE
i The IP address can be assigned with the tool Sicam_first_startup within a network segment (subnet). This
can happen also if the IP address of the engineering PC is located out of this subnet. On the other side, the
assignment of the IP address via a routed network (PC and target device separated via a router) is not
possible.
For the address assignment start the program Sicam_first_startup.exe with double click.

DC8-037-2, Edition 11.2020
The Sicam_first_startup splash screen is opened, and the Sicam_first_startup symbol appears in the notifica-
tion area of the taskbar:
[sc_A8000_first_startup_splash_screen, 1, --_--]
Figure 7-29 Sicam_first_startup Splash Screen
• Click on the splash screen in order to close it
• Click then with the right mouse button on the Sicam_first_startup symbol
[sc_A8000_first_startup_notification_area, 1, --_--]
Figure 7-30 Notification Area of the Taskbar

The context menu of Sicam_first_startup is opened:
[sc_A8000_first_startup_pop-up_menu, 1, en_US]
Figure 7-31 Sicam_first_startup Context Menu
• Change the language if needed and open the context menu again
• After that click on Set Ethernet IP address
The window for the address assignment is opened.

DC8-037-2, Edition 11.2020
Click Discover A8000 to find the physically connected automation units within the network. The found
devices unambigously identified by the respective MAC address – are listed in the table.
[sc_first_startup_set_ip_search, 1, en_US]
Figure 7-32 Sicam_first_startup - Discover A8000 Devices
NOTE
i The IP settings depend on the configuration and the used transmission media of your network. For the
setting of these values please contact your network administrator.
NOTE
i With the firmware CPC80 as of revision 09 the setting of an IP address by means of Sicam_first_startup is
supported only as long as the default IP address (172.16.0.3) exists in the target device.
You can change the settings for IP ADDRESS, SUBNET and GATEWAY by means of clicking on the respective
value. Confirm each with the enter key. The status of the respective target device is set to changed.
After completion of the entries mark the corresponding target devices by marking their lines. Then click on Set
IP address for selected A8000.
Sicam_first_startup creates now the ARP table on the engineering PC (assignment MAC address to IP
address). Afterwards Sicam_first_startup tries to reach the target device. If this is successful, the parameter-
ized addresses are loaded into the respective target device and the status is set to OK. Thereafter a restart is
performed. The procedure is terminated for all target devices when the information Setting IP addresses
A8000 finished appears.
The supplement NOK means that an error occurred with writing the addresses. Check the set network
addresses and the physical connection. If necessary, check the IP settings of your PC via the command prompt
with the command “ipconfig”.

DC8-037-2, Edition 11.2020
Confirm the reset information with OK. After the startup, the respective target device can be addressed by the
webbrowser.
[sc_first_startup_set_ip_ok, 1, en_US]
Figure 7-33 Sicam_first_startup - Setting of an IP Address
NOTE
i The writing of the IP address with Sicam_first_startup is also possible locally via the serial interface.

Start the web browser and enter that IP address in the address bar you have previously assigned to your target
device.

DC8-037-2, Edition 11.2020
NOTE
i According to the parameterization in CP-8000/CP-802x you have to enter a http- oder https-address in the
browser to establish the connection.
During the first time connetion establishment via https there is a check if the corresponding security certifi-
cate is installed. If it is missing, it must be installed manually (see www.siemens.com/gridsecurity, tab
Cyber Security General Downloads, directory Application Notes, document “Certificate trusting in web
browsers”).
Configure IP Address via DHCP-Server

In a network, the IP address of the physically connected target devices CP-8000/CP-802x can be assigned by a
DHCP server. The DHCP service is switched off by default and can be only activated by means of parameter
(see 9.1.2.7 Autoconfiguration).

DC8-037-2, Edition 11.2020
7.7 Interaction with Engineering Tool
For the engineering of CP-8000/CP-802x serves the SICAM TOOLBOX II installed on the engineering PC.
Before you start with the engineering, the predefined configuration parameters of the SICAM TOOLBOX II
must be checked and changed, if necessary (see section 8.1.1 Presets). The system-technical and process-tech-
nical parameterization is performed with the tool “OPM II”. An application program can be created with the
tool “CAEx plus” as function diagram, or alternatively as instruction list with a text editor in ASCII format.
The setting of parameters is only possible independent from the target device (offline). Firmwares for the
system elements and application programs must be imported into the SICAM TOOLBOX II.
Engineering data maintained with the SICAM TOOLBOX II is stored in a data base on the harddisk of the engi-
neering PC. By means of loading processes, the engineering data can be transferred from the harddisk of the
engineering PC to a target device. Thereto the target device must be connected with the engineering PC and
switched on, and a SD card must be equipped in the Master Module of the target device
The engineering data is stored during a load procedure on the SD card of the target device. With startup of the
target device, all new or changed data is transferred into the main memory.
7.7.1.1 Structure
The individual tools of the SICAM TOOLBOX II have a design oriented according to Microsoft Windows ™. After
successful installation they can be started from the Windows start menu Start | All Programs | TOOLBOX II, or
via the Toolbox shortcut on the desktop.
[sc_tbii_startmenu, 1, --_--]
Figure 7-35 SICAM TOOLBOX II Start Menu
The most frequently needed tools (“Load Parameters”, “CAEx plus”, etc.) can be started also directly from the
central engineering tool “OPM II”.
NOTE
i The “SICAM TOOLBOX II” Online Help can be started either directly via the start menu of your PC, or from
each single tool via the menu Help.

DC8-037-2, Edition 11.2020
7.7.2 SICAM WEB
For the engineering of CP-8000/CP-802x serves the web browser installed on the engineering PC. The web
browser shows HTML sites provided by the integrated web server of CP-8000/CP-802x. The parameterization is
performed online in the target device.
By means of the web server the engineering data is maintained and stored on the SD card of the Master
Module. Engineering data can be transferred also by means of loading processes from the harddisk of the
engineering PC to a target device and reversely.
7.7.2.1 Dashboard
After successful login, the so called Dashboard appears. Here you can select the individual submenus via the
displayed tiles:
[sc_dashboard, 1, en_US]
Figure 7-36 SICAM WEB - Dashboard

DC8-037-2, Edition 11.2020
Context menu
Alternatively, each area and each tab can be also accessed via the context menu:
[sc_engineering_menu, 1, en_US]
Figure 7-37 SICAM WEB - Central Context Menu
Buttons for navigation
Home
By clicking on this button you are able to return to the Dashboard from each website in SICAM WEB
Navigation
By clicking on this button you are able to select the desired area from a drop-down list from each website in
SICAM WEB.
7.7.2.2 General Buttons
Open menu
The button contains the following menu functions available exclusively for the user name administrator.

DC8-037-2, Edition 11.2020
The menu functions are also visible for the user name guest, however, he has no authorization to execute
them. With attempt of a selection, a corresponding notification is recorded in the status log (example: Missing
privilege for restart).
[sc_main_menu, 1, en_US]
Figure 7-38 SICAM WEB - Administration Menu
Apply changes
This button is disabled after logging in.

As soon as you modified the parameter settings the button is enabled.
During the saving procedure the changed parameters are transmitted into the device. Then the button
remains disabled until the next modification of parameters. Thus, you can see at a glance whether there is a
modification of parameters (button enabled) or not (button disabled).
For the user name guest the button is always disabled.
Reload
This button causes an update of the data saved last in the device. If you changed values and you did not yet
save it,
• Click on the button, if you want to discard these changes

The web browser opens an interrogation dialog according to the following example:
[sc_message_from_web_page, 1, en_US]
Figure 7-39 Message from Webpage
• Select Cancel, if you want to abort the procedure
• Select OK to update (unsaved data will be lost)

If for instance one administrator and up to two guest are logged on to the same device, the changes made
and stored by the administrator will be visible for the guest only upon reload.

DC8-037-2, Edition 11.2020
Show status log
This button causes the display of a list of error information, warnings and information logged during the
current session:
[sc_status_log, 1, en_US]
Figure 7-40 SICAM WEB - Status Log (Example)
• You may close the list by means of button
• You may clear all by means of button
• You have the possibility to specifically search for certain information:

– In the field Filter enter the word (or a part of it) to search for
– Click the cross to reset the filter
7.7.2.3 Parameter Entry

In the submenu Settings you find all configuration data of the device.
You have the possibility to change configuration parameters. In the left window area, all configuration data is
shown as a hierarchical directory tree:
• CP-8000/CP-802x
– Master Module
NOTE
i At present, a modification of periphery parameters (node I/O Master Module) is not possible. At present,
navigation is possible via mouse only (via finger in case of touch screen). In order to carry out modifica-
tions, you have to log in as administrator.
This is how to retrieve information about parameters:
• In the directory tree, select any node
• You can expand or collapse each directory by clicking or

DC8-037-2, Edition 11.2020
To the right of the directory tree, all parameters of the selected parameter group or table parameters (such as
topology information, dataflow messages and so on) are shown in a table.
• Select the parameter group or parameter you want
• In the table, click on a value of a parameter
• For showing/hiding the description of the selected parameter, click on the yellow bar located to the right
of the work area
[sc_parameter_entry_info_text, 1, en_US]
Figure 7-41 Parameter Description Showing/Hiding
This is how to enlarge the work area:
• For hiding the tree, and therefore enlarging the work area, click on the grey bar left to the work area
[sc_parameter_entry_hide_tree, 1, en_US]
Figure 7-42 Directory Tree Showing/Hiding
This is how to edit parameters:

Depending on the parameter, different options for the parameter entry exist:
• Click on a parameter in the table and modify the value (in the input field)
• Select a predefined value in the drop-down list

DC8-037-2, Edition 11.2020
Each entered value has a specific validity range. Immediately after entering a value, a value range check will
be carried out.
Only valid values will be accepted. When entering an invalid value, a red highlighted notification about the
valid value range appears and the focus remains in the input field.
[sc_parameter_value_range, 1, en_US]
Figure 7-43 Input Value Invalid
• Enter a new valid value
• Press ESC key if you want to restore the previous valid value
In case of table parameters, there is the possibility to define new rows with parameters. The procedure for that
is described subsequently.
This is how to add new parameters:
• Click on the symbol
The new row containing initial values is added at the bottom of the table. These values may be
modified as you wish.
[sc_settings_topology, 1, en_US]
Figure 7-44 Add Parameters
This is how to remove parameters:
• In the table, select a row by placing a checkmark on the left next to the row
• Click on the symbol for delete
This is how to fill an amount of table parameters automatically:

DC8-037-2, Edition 11.2020
Example 1:
• Select the desired column
[sc_lines_fill_selected1, 1, en_US]
Figure 7-45 Select Column 1
• Enter the start value and the increment, then click on
The selected column is now filled according to the input:
Figure 7-46 Filled Column 1
NOTE
i The start value must be within the permitted range, the increment must be always a number.

DC8-037-2, Edition 11.2020
Example 2:
• Select the desired column
Figure 7-47 Select Column 2
• Enter the start value and the increment, then click on
The selected column is now filled according to the input:
Figure 7-48 Filled Column 2

DC8-037-2, Edition 11.2020
This is how to select all rows:
• Place a checkmark in front of the table name in the table header to place a checkmark in front of each
row:
[sc_mark_all_rows, 1, en_US]
Figure 7-49 Select All Rows
This is how to save your modifications:
• Click on the button (Apply) to save your changes
A restart with subsequent startup of the target device may be necessary after saving, refer to 9.3.1 Restart
Device.
NOTE
i The storage of values is possible only with equipped SD card.
This is how to undo your modifications since the last saving procedure:
• Click on the symbol (refer to Reload)

or
• Close the website without saving (with automatic logoff, refer to 7.7.2.7 Navigation with the Web
Browser).
Show Expert Parameters

For the most applications not all of the available parameters are required. For special cases, additional parame-
ters are provided (expert parameters).
To simplify the engineering of the target device, the expert parameters are hidden by default. Thereby the
directory tree has a reduced number of directories and parameter tables have a reduced number of columns
(no impact on the parameter table of the signals page).

DC8-037-2, Edition 11.2020
When activating the checkbox “Show all parameters”, the expert parameters get visible:
[sc_show_all_parameters1, 1, en_US]
Figure 7-50 Show Expert Parameters
The state of the checkbox is maintained during the current session. When logging on again, the state of the
checkbox is deactivated.
7.7.2.4 Automatic Restart Request

Under certain circumstances a restart of the device will be necessary (for instance if a changed parameter
requires a restart for activation, or after updating of the SICAM WEB application). In this case, a corresponding
dialog appears:
[sc_restart_request_param, 1, en_US]
Figure 7-51 Dialog Restart Request
• Click , if you want to perform the restart instantly
• Click , if you want to change arbitrary further parameters yet
The restart request appears then as an indication in the headline:
[sc_indication_line_restart_request1, 1, en_US]
Figure 7-52 Restart Indication
You can define the moment of the restart, and with that the activation of the changed parameters, on your
own. The indication is maintained also with change of the menus and also after abortion of the session. It
disappears only after the performance of a startup of the target device. For the information on execution of a
restart refer 9.3.1 Restart Device.

DC8-037-2, Edition 11.2020
7.7.2.5 SICAM TOOLBOX II Locking

If the initial engineering has been performed with the SICAM TOOLBOX II, a corresponding indication appears
in the header. Then only a reading access to the parameterization is possible.
7.7.2.6 Language Versions

SICAM WEB is available in the following languages:
• German
• English
The language of the GUI corresponds to the language settings of your browser. If the browser language is not
supported, English will be used as the standard language.
Additionally, you have the option of installing language packs, see 9.3.9 Installing the Language Package
7.7.2.7 Navigation with the Web Browser
If you refresh or change the page in the web browser:

After using the functions refresh or back a new page build does not happen. An interrogation dialog of
the web browser appears, whether you want to leave the page.
Example:
[sc_message_from_web_page1, 1, en_US]
Figure 7-53 Message from Webpage
• If you leave the page, the session is automatically terminated and unsaved data is lost; afterwards the
logon dialog appears
• If you stay on the page, you can continue workoing with the latest entered values
If you close the page in the web browser:

After clicking the button close of the web browser (or tab) an interrogation dialog of the web browser
appears, whether you want to leave the page.
• If you leave the page, the web browser is closed, the session is automatically terminated, and unsaved
data is lost
• If you stay on the page, you can continue workoing with the latest entered values

DC8-037-2, Edition 11.2020
7.7.2.8 Session Monitoring
If you do not terminate a session with SICAM WEB via the menu:
An automatic logout occurs after 15 minutes of inactivity. Unsaved data is thereby lost:
[sc_session_timeout, 1, en_US]
Figure 7-54 Report Dialog: Session Expired
• Click OK in order to reconnect with the device, refer to 9.1.1.1 Logon
If you open a new browser window or a new browser tab:

You are already logged on at target device.
The logon dialog will appear after opening a new browser window or a new browser tab, after entering the IP
address of the device and after a successful connection establishment.
With a log-on attempt, a corresponding error message will appear:
[sc_logon_too_many_users, 1, en_US]
Figure 7-55 Logon Dialog: Too Many Users
NOTE
i Please note that no more than one administrator and two guest can be logged in to the device at the
same time.
7.7.2.9 Exceptions with Engineering via SICAM WEB

The parameter records in the SICAM TOOLBOX II and in the SICAM WEB are basically identical structured.
However, for the engineering via SICAM WEB some simplifications exist, hence the following functions are not
supported or implemented in another manner:
• HW configuration Master Module

The Master Module is automatically configured as soon as a SD card with the firmware CPC80 has been
installed.
• System technique I/O Master Module

After the configuration of the I/O Master Module the I/O Modules must be configured in the OPM II. With
the engineering via SICAM WEB the I/O Modules are configured automatically.

DC8-037-2, Edition 11.2020
• Process technique I/O Master Module

In contrast to the OPM II no images are applied, for each I/O Module an assignment page and a parameter
page exist.
In the assignment page the usage of the I/Os is defined (according to the assignment in the SICAM
TOOLBOX II).
In the setting page the previously configured I/Os are parameterized. There appear only the parameters
relevant for the defined usage.
• Process technique protocol element

In contrast to the OPM II no images are applied, the process technique is provided as spreadsheets (send
detailed routing, receive detailed routing).
• Loading firmware of protocol elements

Protocol elements can not be loaded slot-selectively. If for instance on PRE0 and on PRE1 the system
element UMPST0 is configured, both are loaded.
• Message simulation
The message simulation is not supported (inserting of arbitrary messages into the system). However,
there is the possibility of displaying current process values of the periphery (binary information states,
integrated totals, measured values) and to set process values (commands, setpoint commands).
• Data flow test

The data flow test is not supported (different log points, filters, etc.).
• Revision interrogation
The current firmware revision of the Master Module is displayed in the header of the user interface, the
revisions of the additional system elements (protocol elements, I/O Master Module) in the drop-down
menu on the configuration page.
• Application program
A graphical function diagram (FUD) creation is not possible, only an instruction list (IL) with ASCII format
can be loaded into the target device.
• Test of the application program

Offline simulation of the application program is not possible. A simplified online test (state display,
forcing of a selectable signal) is available.

DC8-037-2, Edition 11.2020
DC8-037-2, Edition 11.2020
8 Engineering via SICAM TOOLBOX II
This chapter is a guideline for the work with the SICAM TOOLBOX II. You find the detailed instructions for the
work with the tools of the SICAM TOOLBOX II in the SICAM TOOLBOX II Online Help.
NOTE
i Screenshots shown in this chapter relate to the engineering of CP-8000. They apply analogously for
CP-8021 and CP-8022.
8.1 Telecontrol 338

8.2 Automation 356

DC8-037-2, Edition 11.2020
Engineering via SICAM TOOLBOX II
8.1 Telecontrol
8.1 Telecontrol
Overview of the Tasks
Task Meaning
Presets Define user and rights
Initialization of the plant data Configure plant and automation unit
Import firmware Load firmware into the SICAM TOOLBOX II
HW configuration Selection of the installed system elements
Parameterization of the system • Time management
technique
• Communication common
• Protocol elements
• Assignment of process signals to data points
• Decentralized archive
Parameterization of the process • Create images
technique
• Assign images to data points
• Settings for configured process signals
• Routing of send data and receive data
Bulk edit Creation of great amounts of values of the images
Transfer parameters Compile the set values
SD card Write and read application data
Import/Export Restore and backup of application data
Documentation Prepared spreadsheets for printing
• Hardware (configuration, pin assignment)

• Parameters
Load parameters Transfer parameters and function diagram to the target device
Parameter comparison Compare settings between current project and target device
Dataflow test Record and store dataflow in the target device
Message simulation Send messages from the SICAM TOOLBOX II to a target device
Service function online Read and set time of target device
ST emulation Execute system-internal functions (only for authorized users)
Topology test Acqusition of physically connected automation units in a SICAM RTUs
automation network
Diagnosis Read detailed information generated by the self monitoring
Read decentralized archive Chronological display of parameterized events

DC8-037-2, Edition 11.2020
8.1 Telecontrol
Fundamental Procedure of the Parameterization
[dw_A8000_toolbox_engineering_param_new, 1, en_US]
Figure 8-1 SICAM TOOLBOX II - Procedure for Creation of the Telecontrol Function
Essential Administrative Functions
[dw_A8000_toolbox_engineering_param_admin, 1, en_US]
Figure 8-2 SICAM TOOLBOX II - Procedure for Administrative Functions

DC8-037-2, Edition 11.2020
8.1 Telecontrol
8.1.1 Presets
Before you begin with the engineering of CP-8000/CP-802x, several basic settings are to be carried out for the
work with the SICAM TOOLBOX II:
• User and rights

– User-specific settings
• Password
• Workplace-secific settings
• Organization of the SICAM TOOLBOX II
• Language
For the access to the SICAM TOOLBOX II a logon with username and password is required.
The parameterization with the SICAM TOOLBOX II happens exclusively offline. Only the transfer of data (firm-
ware, application data), as well as test and diagnosis are performed online via a communication connection.
The globally valid configuration parameters in the SICAM TOOLBOX II are displayed and set with the tool
“TOOLBOX II Presets”. They can – dependent on the access rights – be changed at any optional time.
You find the details thereto in the SICAM TOOLBOX II Online Help, chapter TOOLBOX II Presets and chapter
Administration of TOOLBOX II .
8.1.1.1 Users and Rights

The following user names are predefined and can be selected. For each user name different rights are prede-
fined.
• Type admin
• Type profi
• Type standard
As user name admin you can freely assign new user names (max. 8 characters). For each user a special role
(max. 20 characters) can be assigned.
For each role certain rights can be freely selected and assigned from a list. Depending on which role a user has
been assigned, he may control determined functions. An exception are the unchangeable roles, that are
reserved for the Siemens specialists for maintenance purposes.
You find the details thereto in the SICAM TOOLBOX II Online Help, chapter TOOLBOX II Presets , section User/
Role Administration.
NOTE
i All operation and test functions of CP-8000/CP-802x described in this manual are generally applicable for
the admin role available in the SICAM TOOLBOX II.
NOTE
i As of SICAM TOOLBOX II V5.11 it is possible to create domain users. Such a domain user does not use a
specific SICAM TOOLBOX II user role to start SICAM TOOLBOX II, but he uses the user account for the logon
on his workstation.
8.1.1.2 Password
The entrance into the SICAM TOOLBOX II is protected for each user by means of an individual password. The
preset password is equal to the predefined user name.

DC8-037-2, Edition 11.2020
8.1 Telecontrol
NOTE
i The preset password must be changed after the first logon.
8.1.1.3 Language
The languages Deutsch or English can be selected.
8.1.1.4 Role Based Access Control

Regardless of the user administration for the access to SICAM TOOLBOX II, it is also possible to configure
different local users for the connected target device. This must be performed with SICAM WEB (refer to section
9.1.1.4 Creating a Local User).
NOTE
i Local users must be configured separately for each target device.

User authentication can also be carried out externally via a RADIUS server. Thereby, only one role per user is
possible.
Roles and their Rights/Functions
Table 8-1 SICAM TOOLBOX II – Roles and their Rights/Functions
Rights/Functions Roles
Viewer Operator Engineer Installer Security Security Role Admin
Admin Auditor Based
Access
Manager
Menu → Restart device ✓ ✓ ✓ ✓ ✓
Menu → Firmware update ✓ ✓
Menu → Log off ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Device ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Diagnosis → Status / logbook / IP ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
security status
Diagnosis → Security logbook ✓ ✓ ✓
Users → Local users / Users ✓ ✓ ✓
logged on
Users → Change password ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Firmwares → All submenus ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Time ✓ ✓ ✓ ✓
Support → All submenus ✓ ✓ ✓ ✓ ✓ ✓
For more information refer to the document SICAM A8000 Series/SICAM RTUs/SICAM TOOLBOX II – Adminis-
trator Security Manual (DC0-114-2), chapter Measures for System Hardening, , section SICAM A8000
Series / SICAM RTUs, section Role-Based Access Control in SICAM A8000 Series.

DC8-037-2, Edition 11.2020
8.1 Telecontrol
Role-Based Access Control with SICAM TOOLBOX II

When you start SICAM TOOLBOX II you must log in to the SICAM TOOLBOX II and then you can work with it.
[Login_dialog_user_profi, 2, --_--]
Figure 8-3 SICAM TOOLBOX II – Login Dialog (Working Offline)
Only if you carry out actions with SICAM TOOLBOX II which access the connected target device online (for
example, diagnosis), the system will query the access data for role-based access control.
NOTE
i This query is only carried out if a role has already been defined on this target device with SICAM WEB. If no
role was assigned with SICAM WEB, there will be no question for a password.
Then you have to use a local user defined with SICAM WEB.
[Login_dialog_RBAC, 2, --_--]
Figure 8-4 SICAM TOOLBOX II – Login Dialog (Working Online)
The following warning appears if the selected user does not have the required rights to carry out the desired
action:
[RBAC_Missing_Permission, 2, --_--]
Figure 8-5 SICAM TOOLBOX II – Dialog when Login is Denied
You then have the option to repeat the login with another user (with corresponding rights) to continue with
the action.
After a successful login the user can perform all enabled actions without another login.
NOTE
i You have to login again, if the connection to the device is interrupted (for example, caused by a reset
during parameterization) or no input was made within 2 minutes.

DC8-037-2, Edition 11.2020
8.1 Telecontrol
8.1.2 Project Access
8.1.2.1 Logon
With the initial start of a tool of the SICAM TOOLBOX II you must enter a user name and a password. After that
you are able to begin the parameterization.
[sc_tbii_login, 1, en_US]
Figure 8-6 SICAM TOOLBOX II - Login Dialog
A user change is possible with the tool “TOOLBOX II Presets” (menu Authorization | Login ).
8.1.2.2 Logoff
A user logoff is possible with the tool “TOOLBOX II Presets” (menu Authorization | Logout). You can continue
to operate tools that are still active, but the activation of tools requires another login.
If all tools are quit without logout, the user will remain logged in unless a logout from the Toolbox PC or
Toolbox Server takes place.
8.1.2.3 Change Password

As user name admin you can define a password for each newly added user.
Guidelines for the Assignment of Passwords:
• The password may consist of up to 8 characters
• No differentiation between upper case and lower case
• Special characters can be used
• Empty password possible (logon to the project without password)
NOTE
i The preset password must be changed after the first logon.
8.1.3 Plant Configuration
A plant is configured according to different perspectives:
• Project technique
• System technique
• Process technique
The configuration data is in each case specifically parameterized for the different views.
With the initial creation of a plant you must enter the configuration data into the SICAM TOOLBOX II with the
tool “OPM II”. The entry of the parameters is thereby supported by “Wizards”. The plant topology is determined
based on the parameter setting of the configuration data.
After the initialization, the administration of the plant configuration can be carried out with the tool “Plant
Management”. With this tool the configuration data can be changed or deleted at any time.
You find the details thereto in the SICAM TOOLBOX II Online Help, chapter Plant Management.

DC8-037-2, Edition 11.2020
8.1 Telecontrol
8.1.4 Import Firmware
For the parameterization of a target device the system elements to be used must be equipped, and the
belonging firmwares must be present in the SICAM TOOLBOX II.
You can import the required firmwares – if not yet present – into the data base of the SICAM TOOLBOX II with
the tool “Master Data Update”. You find further information in section 11.7.1.2 Importing Master Data into the
SICAM TOOLBOX II. You find information on firmware files in section 7.3 Loadable Firmwares.
8.1.5 Configuration and Settings for Telecontrol
The acquisition, parameter setting and documentation for the telecontrol function and its associated data
points is enabled in the SICAM TOOLBOX II mainly with the help of the tool “OPM II” (Object Orientated Process
Data Manager).
The user’s guide of the “OPM II” can be found in the SICAM TOOLBOX II Online Help, chapter OPM II.
The description of the system-technical and process-technical settings can be found in the manual SICAM
TOOLBOX II Online Help, chapter OPM II.
[sc_tbii_opmii, 1, en_US]
Figure 8-7 SICAM TOOLBOX II - Tool OPM II
8.1.5.1 Hardware Configuration

Before the parameter setting a target device must be configured with the required system elements:
• Master module (details see 2.1.2 Master Module)
• Protocol elements (details see 2.2.1 Protocol Elements)

DC8-037-2, Edition 11.2020
8.1 Telecontrol
• I/O Master Module (details see 2.1.3 I/O Master Modul)

– I/O Modules (details see 2.1.4 I/O Modules)
NOTE
i The firmware codes of the corresponding system elements must exist in the target device.
You find an overview of the available system elements and I/O Modules and their technical specification
chapter 5 System Components and Technical Data.
The configuration takes place with the tool OPM II via the menu items Tools | System Technique and Tools |
Library Overview.
By dragging the system elements of the system CP-8000/CP-802x from the Library Overview onto the respec-
tive target device in the system technique, the corresponding system elements are added with default param-
eters.
With use of I/Os, the higher-level I/O Master Module must be configured at first. After that you can drag I/O
Modules onto the I/O Master Module and assign signals to the respective I/O Module (system technique).
NOTE
i With CP 8000, the slots for the internal I/O Modules are predefined in the parameter-setting: IOM0: DO
8203, IOM1: DI 8100. For external I/O Modules, the slots IOM2 … IOM7 are available.
With CP 802x, the slots IOM0…IOM7 are available for external I/O Modules.
When deleting an I/O Module, all the assigned signals (hardware pins and software data points) are then
deleted from the plant tree.
The changed hardware configuration must be converted with the tool “OPM II”, menu Destination systems |
SICAM 1703 transformer, and subsequently transmitted to the target device with the tool “Load parameters”,
to become effective.
During startup the target device checks if the mechanically installed I/O Modules match the parameterization.
NOTE
i The configuration in the “OPM II” must match the mechanically installed I/O Modules. If you remove an I/O
Module mechanically, you must delete it also in the “OPM II”. If you do not adapt the configuration in the
“OPM II”, the target device detects this I/O Module as failed (error indication).
If you add an I/O Module mechanically without adapting the configuration in the “OPM II”, this has no
effects. In this case, the added I/O Module is ignored.
8.1.5.2 System-Technical Settings

The system-technical configuration of a target device resides in the window “System technique”. This can be
opened via the menu Tools | System technique.
The parameter setting is carried out in the directory tree, respectively below the selected Master Module:
• Common settings
• Time management
• Communication protocols
• Network settings
• Topology
• Dataflow filter

DC8-037-2, Edition 11.2020
8.1 Telecontrol
• Periphery
• Decentralized archiving
Communication
The protocol is determined by configuring a protocol element suitable for the existing application and its
parameterization.
For security relevant informationen refer to the SICAM RTUs / SICAM TOOLBOX II – Administrator Security
Manual.
Periphery
The peripheral functions are defined by means of configuring the I/O Master Module, the I/O Modules suitable
for the present application, as well as their parameters.
Below the level of the Ax peripheral bus the configured I/O Master Module with the configurable signals is
displayed:
• Hardware pins
• Software data points

By means of the context menu of a hardware pin or software data point, selection Edit image, you get directly
to the process-technical settings of the respective signal.
8.1.5.3 Process-Technical Settings
Levels
The process-technical plant can be structured in freely-definable hierarchy levels. The following graphic shows
an example:
[sc_tbii_levels, 1, en_US]
Figure 8-8 SICAM TOOLBOX II - Hierarchy Levels of the Process Technique
You find the instruction to create levels in the SICAM TOOLBOX II Online Help, chapter OPM II, section Levels.
The process-technical settings of the system elements can be opened centrally via the menu item Tools |
Images.

DC8-037-2, Edition 11.2020
8.1 Telecontrol
Types
Types form the template for the structure of a process-technical plant. They serve for the simplification with
engineering of large quantities of objects, parameters and values.
Types of the following type categories can be defined below the levels:
• User names
• Link types
• Info types
• Parameter types
A type is defined respectively for objects, that have the same features (examples: feeder, circuit breaker,
disconnector).
You find the instruction to define the different types in the SICAM TOOLBOX II Online Help, chapter OPM II
section Types.
Images
Images are real objects of the plant with parameters and signals (examples: feeder north, circuit breaker Q00,
disconnector Q10).
• Typified images
Typified images can be created from the defined types, that means, each images is assigned to a type.
The assigned type defines thereby the structure for the image. The structure defines which linktypes
include a signal and which parameter includes a link. This structure can be changed only in the type of
the belonging image. All images that are assigned to that type, adopt automatically the structure change
(inheritance).
The same behavior applies for default input. The usage of typified images is the more efficient, the more
identic images are present.
• Typeless images
Typeless images do not have a reference to the types, that means, no inheritance takes place. Typeless
images are also created by structural changes of a typified image (since the image does not have the
same structure as the type).
Typeless images are advantageous, if images are only uniquely existing.
Below typless images, typified images can be used (example: voltage level “20 kV“ is typeless since it is
only uniquely existing, all feeders thereunder are typified images).
• Link images
In the link images the parameters of the single target devices can be set.
The signals of the libraries include as first link a so-called common link (LNK_ADR). There reside parame-
ters (example: longtext, LAN station...) that include “references” to other links of the same signal or are
source of “formulas”.
A reference causes that upon changes of an entry in the common link the change takes place automati-
cally in the link of the specific target device. Message address CASDU(1,2), IOA(1,2,3) and TI are gener-
ated automatically with filling of the 1703 link address (Lk_Reg, Lk_Komp, Lk_BSE, Lk_ZSE, Lk_DP) by
means of formulas and references and do not have to be entered.
You find the instruction for the creation of images in the SICAM TOOLBOX II Online Help, chapter OPM II,
section Images.

DC8-037-2, Edition 11.2020
8.1 Telecontrol
Parameterization of the Process Signals and Assignment to the System Technique

The parameters for the technological processing of process signals reside in the directory tree below the link
images:
• Addressing
• Signal preprocessing
• Signal postprocessing
You find the description of the parameters in the SICAM TOOLBOX II Online Help, chapter Parameter Docu-
mentation.
You find the description of the technological processing of inputs and outputs of the process periphery in the
manual SICAM RTUs Common Functions Peripheral Elements According to IEC 60870-5-101/104.
The assignment of a process signal to a hardware pin or software data point in the system technique takes
place by means of assignment (alternatively automatical or manual). You find the instruction thereto in the
SICAM TOOLBOX II Online Help, chapter OPM II, section Assign.
8.1.5.4 Decentralized Archive (DEAR)

The decentralized archive serves for the local storage of events of a substation, and - whenever necessary - for
the transmission to the control system. By means of that, it is for instance possible to recover the archive of a
control system after a communication fault.
In the decentralized archive all the data points used in the substation can be acquired.
You can configure the archive in the system technique of the “OPM II” (parameter group Decentralized
archiving of the respective automation unit). In the images you can define the process-technical settings of
the data points to be acquired. During operation, these data points are archived chronologically upon status
change. This applies for all binary information items of the send and receive direction.
You find the detailed information on the settings in the manual SICAM RTUs Common Functions System and
Basic System Elements, chapter Telecontrol, section Decentralized Archiving.
8.1.6 Transform Parameters
Before loading into the target device, the process-technical parameters of the plant must be transformed. This
can be carried out with the tool “OPM II” through selection of the menu Destination systems | SICAM 1703…
| SICAM 1703 Transformer.
System-technical parameters are automatically transformed when saved.
You find the details thereto in the SICAM TOOLBOX II Online Help, chapter OPM II, section Transform and
Load | SICAM RTUs.
8.1.7 Import, Export and Backup of Engineering Data
The tool “Data Distribution Center” enables the importing and exporting of parameters, as well as the creation
of backup files.
You find the details thereto in the SICAM TOOLBOX II Online Help, chapter Data Distribution Center.
8.1.8 Documentation
With the tool “OPM II” you can generate and print the documentation of the engineering data:
• Hardware configuration
• Assembly technique
• Interface to Elcad

DC8-037-2, Edition 11.2020
8.1 Telecontrol
• Telecontrol function
– System-technical configuration
– Process-technical settings
You find the details thereto in the SICAM TOOLBOX II Online Help, chapter OPM II, section System Technique
| Documentation.
8.1.8.1 Hardware Configuration

You can initiate the documentation of the system elements in the plant tree of the menu System technique ,
via the context menu of the automation unit.
The output takes place as a table in a file (format .csv) or to a printer.
With the tool “HW-FW Configuration” you can assign the required assembly-technical information to the
system elements.
8.1.8.2 Assembly Technique

You can initiate the documentation of the assembly-technical configuration in the plant tree of the menu
System technique, via the context menus of the I/O Modules.
The output takes place as a table with adjustable layout, optionally as preview on the screen or to a printer.
The documentation extends over the HW pins of the respective I/O Module and contains:
• Slot and type of I/O Module
• System-technical address of each pins within the message
• Process-technical address of each pins within the message
• Common information of a pin (long text)
• Assignment of the pins to a link image in the “OPM II”
8.1.8.3 Interface to ELCAD

For the coupling with the design tool ELCAD, it is possible to transfer images that are assigned to a system
element via this defined interface.
The output takes place to a text file (format .asc).
The generation of the file takes place via selection of the menu Destination systems | SICAM 1703… | SICAM
1703 Transformer.
You find the details thereto in the SICAM TOOLBOX II Online Help, chapter OPM II, section Elcad.
8.1.8.4 Telecontrol Function
System-Technical Configuration
You can initiate the documentation of the system-technical configuration in the menu System technique, via
the context menu of an automation unit or of a specific system element.
The output takes place as a spreadsheet, optionally as preview on the screen or to a printer.
Process-Technical Settings
You can initiate the documentation of the process-technical settings in the tree of the menu Edit image, via
the context menu of a selected hierarchical level.
The output takes place as a spreadsheet, optionally as preview on the screen or to a printer.

DC8-037-2, Edition 11.2020
8.1 Telecontrol
8.1.9 Commissioning and Test
For commissioning and test of the projected settings the following functions are available (online):
• Load engineering data
• Parameter comparison
• Test functions
• Diagnosis (see section 11.5.2 SICAM TOOLBOX II)

For these functions the engineering PC must be connected with the target device (see section
7.6.1 SICAM TOOLBOX II).
8.1.9.1 Loading Engineering Data

Use the “Load Parameters” tool to load parameters of a process-technical plant from the PC to the target
system. You can launch it from the “OPM II” via the Target systems | SICAM 1703 | Parameter loader menu
or directly via the Start menu on your PC.
Use the “Parameter Loader” tool to add and select automation units and initiate loading via the Load |
Selected AUs menu.
All settings that have been performed in the SICAM TOOLBOX II are thereby saved jointly on the SD card of the
target system:
• Configuration parameters
• System-technical parameters
• Process-technical parameters (if they have previously been transformed)
• Application program (if code has previously been generated)

There are different variants to load parameters:
• Intelligent loading
– Only changed parameters are loaded into the target system
– Can be applied locally or remotely
– After the loading of the parameters an automatic startup of the target device is performed (for each
selected automation unit a corresponding notification appears subsequently)
• Unconditional loading
– All parameters are loaded into the target system
– Can be applied locally or remotely
– After the loading of the parameters an automatic startup of the target system is performed (for each
selected automation unit a corresponding notification appears subsequently)
• Initialize
– All parameters are deleted in the target system and all parameters are transferred from scratch
– Can be applied with the locally connected automation unit only
– Used for the first loading of an automation unit or a Master module
– If a changed parameter requires a system startup of the master module, a query appears after the
loading, asking whether the system startup is to be performed immediately or at a later point – for
instance if further changed parameters are to be activated together

DC8-037-2, Edition 11.2020
8.1 Telecontrol
[sc_tbii_reset_message, 2, en_US]
Figure 8-9 SICAM TOOLBOX II – Request to Restart to Activate Parameters
For more details refer to SICAM TOOLBOX II Online Help, chapter Service Programs, section Parameter
Loader.
NOTE
i During a loading operation, the switching off of the target device is to be absolutely avoided, since the data
on the flash card could be destroyed as a result.
8.1.9.2 Parameter Comparison

With the tool “Parameter Loader” you can check whether the parameter status in the target device is current.
You can select an automation unit and start the comparison via the menu Parameter | Comparison AUs <->
Toolbox.
For each selected automation unit appears the indication whether the parameters are current or not current.

The following test functions are available:
• Data flow test
• Message simulation
• Topology test
[dw_A8000_toolbox_engineering_test, 1, en_US]
Figure 8-10 SICAM TOOLBOX II - Procedure for Test Functions
Status Of Spontaneous Data Points

With the tool “Data Flow Test” data streams (flow of messages) can be simultaneously logged and visualized.
For a subsequent analysis also at another location a recording can take place with the Interface Recorder.

DC8-037-2, Edition 11.2020
8.1 Telecontrol
The function Simultaneous log serves for the recording of messages within the internal data flow of an auto-
mation unit. In protocol elements, the data flow from and to other automation units can also be acquired.
The following data can (with change of the spontaneous data) be simultaneously logged:
• Change of state of inputs/outputs
• Communication from and to protocol elements
• Data traffic from and to the application program
• Data traffic from and to special functions (for example set counters, set time)
By means of triggering a General Interrogation all spontaneous input signals can be simultaneously logged at
any arbitrary time.
You find the instruction for this test function in the SICAM TOOLBOX II Online Help, chapter Service
Programs, section Data Flow Test.
You find further information in the manual SICAM RTUs Common Functions System and Basic System
Elements, chapter System Services, section Data Flow Test.
Simulation Of Spontaneous Data Points

With the tool “Message Simulation” messages can be transmitted from the SICAM TOOLBOX II to automation
units. Just one message or up to 100 messages in succession can be transmitted; in addition sequential delays
and message repetitions can be defined.
The messages can be passed in at defined points of the system. With this function the following possibilities
exist:
• Setting of outputs
• Simulation of the communication from and to protocol elements
• Data traffic from and to the application program
• Data traffic from and to special functions (for example set counters, set time)
! DANGER
Pay attention that due to the simulation the plant state can change. The manual controlling of outputs with
the plant running can lead to damage to persons and machines.
² Ensure that aggregates in the control area of the command output and those subsequent aggregates
in the process chain are protected and that persons in the vicinity are warned.
Programs, section Message Simulation.
Elements, chapter System Services, section Message Simulation.
Check The Connection To Automation Units

The tool “Topology Test” is used for the acquisition of all automation units in a SICAM RTUs automation
network that are reachable or non-reachable from the automation unit momentarily physically connected.
Programs, section Topology Test.
Logging Ethernet Messages

With the tool “ST Emulation” it is possible to read out data packets that are are sent via Ethernet-based proto-
cols.

DC8-037-2, Edition 11.2020
8.1 Telecontrol
NOTE
i The tool “ST Emulation” is a developer application and requires administrator rights.
The logging function is available in the firmware CPC80 as of version 15.
The logging of the data packets is performed on the SD card in the Master Module. Thereto, the parameter
Advanced parameters | Software test points | Ethernet Packet Capture activate
must be set to Yes.
On the SD card exists a circular buffer with up to 500 files (format pcap, 30 kB for each file). In the presets all
data pakets are logged, however, via the parameters filters can be set.
[wireshark_parameter, 1, en_US]
Figure 8-11 Parameters for Logging of Ethernet Messages
For reading the data packets start the tool “ST Emulation” and enter the following instruction in the
command line:
M: idw
The recorded data packets are now read out and displayed. This can take several minutes.

DC8-037-2, Edition 11.2020
8.1 Telecontrol
[cap_data_st_emul, 1, en_US]
Figure 8-12 Display of Read Data Pakets
The display of the read data pakets is hexadecimal. Via the button Save you can save the data as text file on
the engineering PC.
For display of the data data pakets in a readable format, the file must be converted with the SICAM Protocol
Test System (item number SA0-900, as of revision 0708) via the menu Extras | Convert a ST IDW file to
pcapng. The resulting file can now be read with the established program Wireshark.
[cap_data_converted, 1, --_--]
Figure 8-13 Display of Read Data Pakets in Wireshark

DC8-037-2, Edition 11.2020
8.1 Telecontrol
8.1.9.4 Displaying Decentralized Archive (DEAR)

The current contents of DEAR can be displayed with the tool “OPM II”.
Via the context menu of the automation unit, submenu Display decentral archiving… , you get to the file
directory. Then select a file and click on the button Display archives to display the respective records.
NOTE
i The data records of the decentralized archive are registered in configurable files. The files are stored on the
SD card. The record of data points is therefore only possible with equipped SD card.
Example
[sc_tbii_dear_filestructure, 1, en_US]
Figure 8-14 SICAM TOOLBOX II - DEAR File Structure
You can save the displayed records of DEAR in a file (Format csv) on the engineering PC. You find the informa-
tion thereto in the SICAM TOOLBOX II Online Help, chapter OPM II, section System Technique | General |
SICAM RTUs | Decentral Archive Display.

DC8-037-2, Edition 11.2020
8.2 Automation
8.2 Automation
For the implementation of freely definable open-/closed-loop control functions you can create optionally an
application program as function diagram.
Task Meaning
Configure external signals Create images for spontaneous and periodical data points
Create function diagram Edit the application program
Simulate function diagram Offline test of the application program
Generate program code Compile application program
Load program code Transfer application program into the target device
Perform startup Initialize application program in the target device
Test function diagram Online test of the application program
Documentation Prepare application program for printing
Fundamental Procedure of the Programming
[dw_A8000_toolbox_engineering_automation, 1, en_US]
Figure 8-15 SICAM TOOLBOX II - Procedure for Creation of the Automation Function
8.2.1 Creation of a Function Diagram with CAEx plus
For the creation of a function diagram (FUD) the tool “CAEx plus” is required. This provides various editors and
standard libraries for the creation of the open-/closed-loop control function.

DC8-037-2, Edition 11.2020
8.2 Automation
The process-technical functions of a plant are created with the function diagram editor (FBD Editor). A func-
tion diagram is thereby created by the interconnection of
• predefined functions and function blocks
• functions and function blocks defined by the user

You find the description of the editor in the CAEx plus Online Help, chapter Editors. Additional information
can be found in the SICAM TOOLBOX II Online Help, chapter Tutorials, section CAEx plus.
You find the most important characteristic values (limits) for the creation of the open-/closed-loop control
function in section 5.2.1.2 Technical Data.
You find the technical details for the processing of the open-/closed-loop control function and its partial func-
tions in the manual SICAM RTUs Common Functions System and Basic System Elements, chapter Automation,
section Restricted Open-/Closed-Loop Control Function | Application Program | Function Diagram,.
NOTE
i Optionally to the creation of a function diagram, an instruction list (IL) with ASCII format can be imported
in “CAEx plus” (tool “OPM II”, context menu of the CPU, Instruction list | Import from file).
Function Diagram (Example)
[sc_tbii_caexplus_fud, 1, en_US]
Figure 8-16 SICAM TOOLBOX II - Function Diagram Editor
8.2.1.1 Restrictions when Creating a Function Diagram

Note some special characteristics when creating a function diagram:
• Blocks and data types

In the AU library, only blocks and in the type instance, only data types can be supported by CP-8000/
CP-802x.

DC8-037-2, Edition 11.2020
8.2 Automation
• Signals from the signal list

From the signal list, only data types supported by CP-8000/CP-802x can be used in the type instance (for
example, the message with TI 38 – "protection event" is not allowed). This is checked via the data type of
the signal. The system data point from the signal list can also not be used in the type instance.
• System data points

These are available as global variables in the global "System info" variable object in the resource. These
global variables can be used in FUD.
• Type identifications
The type identifications are checked during the creation of the FUP. Messages with type identifications
that are not supported by CP-8000/CP-802x cannot be used in the FUD.
• Non-volatile states
If messages or block inputs/outputs are set to Non-volatile in FUD, a corresponding warning appears
during code generation.
• CASDU
All information generated in the CP-8000/CP-802x application program has the same CASDU in the
message address. This makes it necessary to assign the same CASDU in the CAEx plus link for parameter-
settable messages that are generated in the application program (see chapter Application Program,
Page 384). In the event of a wrong setting in “OPM II”, code generation aborts with a corresponding error
information.
You can assign a random message address for incoming messages in the FUD.
• IOA
IOA = 0.0.0 is not allowed; this is not supported by numerous third-party systems.
• Status bit Class 1

This is not supported by FUD (priority management of the communication function).
• Status bit R (redundancy)

This is never set by the target system. A warning is output during code generation when using the redun-
dancy bit.
• Additional attributes
These are not supported by CP-8000/CP-802x. These attributes are not taken into account during code
generation and a warning and/or error will not be output.
• Periodic data points

CP-8000/CP-802x does not support periodic links (1703 links with use in FUD, no evaluation of the
parameter Use_CAEx_plus). Directly enter the variables in the FUD in the event of periodic use (system
variables with predefined names). These system variables have been listed in the SICAM TOOLBOX II
Online Help in the data point description of the I/O Master module firmware (internal key 92128 to
92255).
For more information refer to the manual SICAM RTUs Common Functions System and Basic System
Elements , chapter Automation, Restricted Open/Closed-Loop Control Function.
You will find some selected program examples in the appendix of the manual B Examples of Instruction Lists
(IL).
8.2.1.2 Configuring External Signals

The I/O’s are integrated into the Function Diagram via the Signal List. Dependent from the fact, whether the
target device is engineered via the SICAM TOOLBOX II or via the SICAM WEB, the Signal List can be alterna-
tively
• generated with the tool “OPM II”
• imported from a local parameterization (see thereto section 8.1.7 Import, Export and Backup of Engi-
neering Data

DC8-037-2, Edition 11.2020
8.2 Automation
The signals of the process-technical plant can be used by “CAEx plus” after the transformation (see section
8.1.6 Transform Parameters). The structure of the project tree automatically adapts to the structure from the
“OPM II”.
An introduction how to create a project can be found in the CAEx plus Online Help, chapter First Steps and
chapter Additional Products, section Signal List (Optional).
8.2.1.3 Program Code Generation

Before the loading of the open-/closed-loop control function into the target system, the program code must be
generated.
You can start the code generation via the following ways:
• “CAEx plus” transformer
• “CAEx plus”, via the context menu of the Master Module firmware
Start of the Program Code Generation
[sc_tbii_caexplus_codegen, 1, en_US]
Figure 8-17 SICAM TOOLBOX II – CAEx Plus Context Menu for Code Generation
The function diagram is consequently translated and checked by a compiler. Simultaneously, the program
code is created as an instruction list in the Specification folder.
Via the menu Tools | Error state viewer, you can activate the notification display of the code generation.
Here, common notifications (for instance information on occupied memory space for code and variables) as
well as detected errors are recorded in detail.

DC8-037-2, Edition 11.2020
8.2 Automation
Error State of the Viewer (Example)
[sc_tbii_caexplus_codegen_error_state, 1, en_US]
Figure 8-18 SICAM TOOLBOX II – CAEx Plus Error State Viewer
The tool has been described in detail in the CAEx plus Online Help, chapter Target System Connection,
section Functions for Target System Connection | Code Generation.
Code generation can be started independently from “CAEx plus” with the “OPM II” tool by selecting the Desti-
nation systems | CAEx plus… | signal list/generate code menu. Thereby a signal list is created to process
parameterized signals in the open-/closedloop control function and read into “CAEx plus”.
Refer to the SICAM TOOLBOX II Online Help, chapter OPM II, section Transform and Load, CAEx plus for
more details.
8.2.2 Documentation
8.2.2.1 Cross Reference List

With the tool “CAEx plus” a cross reference list over the project hierarchy can be generated, displayed on the
screen, or printed.
The cross reference list refers alternatively to
• Entire function diagram of the selected Master Module
• Single program organization unit

It is executed via the respective context menu Cross-references.
You find the details thereto in the CAEx plus Online Help, chapter Basics, section Default Operating
Elements | Commands of the Pop-Up Menus.
8.2.2.2 Open-/Closed-Loop Control Function

In the project hierarchy of the tool “CAEx plus”, by selecting one of each level, by means of pop-up menu the
function Print can be executed. The print operation is started on the default printer of the PC.
You find the details thereto in the CAEx plus Online Help, chapter Basics, section Default Operating
Elements | Commands of the Pop-Up Menus | Print in Project Management.
Additional information can be found in the CAEx plus Online Help, chapter Basics, section Default Properties
as well as chapter Lists and References, section Designing Printouts with DXF.
Further extensive possibilities for the documentation are provided by the optional function Document
Management (additional product for “CAEx plus”).
You find the details thereto in the CAEx plus Online Help, chapter Additional Products, section Document
Management (optional).

DC8-037-2, Edition 11.2020
8.2 Automation
8.2.3.1 Loading Program Code

To load the compiled program code into the target device, the engineering PC must be connected with the
target device (see chapter 7.6.1 SICAM TOOLBOX II.
The loading of the program code into the target device takes place jointly with the parameters set in the “OPM
II”. Thereto the tool “Parameter Loader” must be used (see also section 8.1.9.1 Loading Engineering Data).
NOTE
i During a loading operation, the switching off of CP-8000/CP-802x is to be absolutely avoided, since the
data on the SD card could be destroyed as a result.
You find the technical description thereto in the manual SICAM RTUs Common Functions System and Basic
System Elements, chapter Automation, section Open-/Closed-Loop Control Function | Loading of Applica-
tion Program. .
You find the instruction for the operation in the SICAM TOOLBOX II Online Help, chapter Service Programs,
section Parameter Loader.

• Simulating Function Diagram Offline
• Testing Function Diagram Online
Simulating Function Diagram Offline

The logic operations of a function diagram can be tested in “CAEx plus” with the Offline simulation.
This function can be called via the context menu of the Master Module, program instance or type instance.
You can find the details thereto in the CAEx plus Online Help, chapter Additional Products, section Offline
Simulation.
The oscilloscope function serves for the chronological representation of analog values and binary values
during the offline simulation of the function diagram.
You find exact details thereto in the CAEx plus Online Help, chapter Additional Products, section Logic Anal-
ysis with Oscilloscope Functions.
Testing Function Diagram Online

With the tool “CAEx plus”, all open- and closed-loop technical tasks in processing elements of the system can
be tested online.
This function can be called via the context menu of the Master Module <Firmware>, selection ONLINE Test.
• Display and force values
• Test switch input/output messages, input/output process images of the periphery

DC8-037-2, Edition 11.2020
8.2 Automation
• Changing the execution status of the open-/closed-loop control function

– Stop controller
– Start controller
– Perform cold start of the resource
– Perform warm start of the resource
– Halt task
– Continue task
– Perform cold start of a task
– Perform warm start of a task
– Halt program
– Continue program
• Setting breakpoints
• Real time archive
• Display status information
• Read and write variables
The technical description of the online test function can be found in the manual SICAM RTUs Common Func-
tions System and Basic System Elements, chapter Automation, section Online Test.
The details for operation can be found in the CAEx plus Online Help, chapter Target System Connection,
section Functions for Target System Connection.
NOTE
i With user program running, the simulated value of a variable is statically overwritten. In contrast to this,
inputs/outputs are not statically overwritten, rather only with a change to their process image (edge-trig-
gered).
With user program stopped, simulated values are retained.

DC8-037-2, Edition 11.2020
9 Engineering via SICAM WEB
9.1 Telecontrol 364

9.2 Automation 485
9.3 Administrative Functions 508

DC8-037-2, Edition 11.2020
Engineering via SICAM WEB
9.1 Telecontrol
9.1 Telecontrol
Task Meaning
Start and terminate session • Log on to the target device
• Log off from the target device
Presets • Define password
• Set IP adresses
Common settings • Configuration of the target device
• Topology (routing of send data and receive data)
• Failure behavior upon error
Hardware configuration • Add or remove protocol element
• Add or remove I/O Master Module
Time management • Time settings
• Local time setting
Communication • Settings of the messages
• Interface for the communication
• Transmission facility
Periphery • Configuration of the signals
• Signal list import/export
• Settings for configured signals
Administration • Restart device
• Save device settings
• Recover device settings
• Firmware update
• Install language package
• Set date and time
Test functions • Display of input/output signal states
• Forcing of output signals
Event list Chronological display of the occurred events
Alarm list Chronological display of the occurred alarms
Diagnosis Indications generated by the self monitoring
Preconditions for the Engineering

For the engineering via SICAM WEB the steps according to section 7.6.2 SICAM WEB must be performed:
• Firmware CPC80 (as of rev. 10) is on the SD card
• Firmware SWEB00 (as of rev. 03) is on the SD card
• SD card is installed in the target device
• Target device is switched on
• Physical connection to the target device is established
• IP addresses for target device and/or engineering PC are configured

DC8-037-2, Edition 11.2020
9.1 Telecontrol
9.1.1 Starting and Finishing a Session
9.1.1.1 Logon
Prerequisite: the device is in operation and reachable via its IP address.
This is how to establish a connection to the Web server of the device:
• Open your browser
• In the URL field of your browser, enter the IP address of the device
• Confirm with the Enter key

After connection establishment the Logon dialog appears.
The language of the Logon dialog corresponds to the language settings of your browser/operating system.
Figure 9-1 Dialog for Logon
For the entrance into a target device, the following entries are required:
• Input field USER NAME (entry user name)

– “administrator”
– “guest”
• Input field PASSWORD (entry of a password)

– an empty password is preset
• Dropdown list LANGUAGE (selection of the language)

– “Deutsch”
– “English”
• Click
If a connection via GPRS is used, the Dashboard will appear at the latest after 20 seconds. The session with
the web server of the target device has started. As user name “administrator” you can begin now with the
parameter-setting.

DC8-037-2, Edition 11.2020
9.1 Telecontrol
In case of missing entries or inconsistent entries regarding user name and password, a corresponding error
message will appear in a red line of the Logon dialog:
[sc_logon_fail, 1, en_US]
Figure 9-2 Dialog for Logon Error
• Re-enter user name and password

After entering of a valid user name/password
• Click
After sussessful logon the Dashboard of the SICAM WEB application will appear.
Rights of the Users

Depending on the user name, different rights are defined:
• “administrator” is generally entitled to make changes
• “guest” does not have any editing permissions, the relevant buttons are disabled
Action Administrator Guest

Change administrator password ✓ -
Change guest password ✓ -
Perform restart ✓ -
HW configuration ✓ -
Change parameters ✓ -
Display parameters ✓ ✓
Load parameters (backup upload) ✓ -
Save parameters (backup download) ✓ -
Load firmware ✓ -
Display I/O status ✓ ✓
Force outputs ✓ -
Diagnosis ✓ ✓
NOTE
i No more than 1 “administrator” and 2 “guest” can be logged in to the device at the same time.
9.1.1.2 Logoff
If you want to finish your work you should log out.
• Click the button and then the submenu Logout

DC8-037-2, Edition 11.2020
9.1 Telecontrol
Thus, you are logged out again, the Logon dialog will appear. If a connection via GPRS is used, the Logon
dialog will appear at the latest after 20 seconds.
If you made any changes after the last saving, the following dialog will appear after clicking Logout:
[sc_logoff_unsaved_changes, 1, en_US]
Figure 9-3 Dialog Save Changes
• If you click , changed data will not be saved and the logout will be performed
• If you click , you remain logged on and you can save the data
NOTE
i The session will be closed by the web server after 15 minutes of inactivity. In this case you have to logon
again. This applies also in case of an unwanted abortion of the communication connection (failure, closing
of the web browser, etc.).
9.1.1.3 Initial Login on the Target Device with SICAM WEB

Preconditions:
• The hardware of the systems (CP-8000/CP-802x, PS-86xx ...) is installed and ready for operation
• The connection between engineering PC and target device is established
Procedure:
Open a web browser and enter in the address bar the standard IP address (https://172.16.0.3) of your target
device.
If the target device is in status “Factory Settings” (e.g. during commissioning), you can only login with the
default user “administrator”. In the factory settings, no password is assigned to this user, hence you are
requested to set one.
[sc_initial_logon_change_pw, 2, --_--]
Figure 9-4 Password Dialog
The password must have between 8 and 54 signs (letters, numbers and special characters are possible). If you
do not enter a password, you will be logged off.

DC8-037-2, Edition 11.2020
9.1 Telecontrol
After a successful password input the Dashboard of the user“administrator” appears.
[sc_dashboard_admin_01, 2, en_US]
Figure 9-5 Dashboard for Administrator
9.1.1.4 Creating a Local User

Preconditions:
• User with administrator rights is logged on to the device.
Procedure:
² On the dashboard click the tile “Local users”.
The submenu Local users shows now which users exist on the connected device and which role they
have. A device which is in delivery status has only the user “administrator”.
²
Click on to create an additional local user.

DC8-037-2, Edition 11.2020
9.1 Telecontrol
² Define username, password and role of the new local user.
²
Save your settings with a click on
The sub menu Local users shows now the new created user and which role he has.
² By clicking the check box in column “Enabled” you can activate or deactivate the new user.
NOTE
i To delete a local user select it in the local user list and click on .
9.1.2 Basic Settings
• Menu Home | Settings

After the initial logon you should define some basic settings for working with SICAM WEB.
The basic settings are necessary to logon to the target device and security
• Authentication procedure
• Change web server password
• Set IP addresses
• Enable optional “Autoconfiguration”

DC8-037-2, Edition 11.2020
9.1 Telecontrol
9.1.2.1 Authentication Procedure

The authentication definition takes place in the directory tree under SICAM A8000 CP-80xx | Master module |
Network settings | Authentication (the checkbox SHOW ALL PARAMETERS must be activated).
[sc_settings_network_authentication, 1, en_US]
Figure 9-6 Network Settings Authentication
CP-8000/CP-802x provides different authentication mechanisms. Depending on the settings, SICAM WEB uses
the respective role information:
• Authentication via locally stored credentials

– Usernames, passwords, profiles defined by CP-8000/CP-802x will be used
• Authentication via external service (RADIUS server)

– Usernames, passwords, profiles defined by the RADIUS server will be used
– Fallback option, if the RADIUS server is not available
Authentication via Locally Stored Credentials

This is the default mechanism. After entering the login credentials and login attempt, the target device
compares these credentials with the locally stored credentials:
• If the comparison is successful, the target device returns the specific user role
• If the comparison is not successful, the logon fails
Authentication via External Service

For this mechanism a RADIUS server can be configured. The parameter Radius Authentication must be
set to YES.
CP-8000/CP-802x uses the RADIUS server IP address and the RADIUS shared secret key for the RADIUS commu-
nication.
After entering the login credentials and login attempt, the target device sends these credentials to the RADIUS
server for authentication:
• If the RADIUS server is available, it compares the login credentials

– If the comparison is successful, the RADIUS server returns the specific user role; SICAM WEB and the
internal role based protection mechanism use this role-information for the user
– If the login credentials are invalid, the logon fails

DC8-037-2, Edition 11.2020
9.1 Telecontrol
• If the RADIUS server is not available, the target device runs into a timeout
– If the fallback option is enabled, the authentication mechanism falls back to local authentication and
the target device compares the credentials with the locally stored credentials
– If the comparison is successful, the target device returns the specific user role; SICAM WEB and
the internal role based protection mechanism use this role-information for the user
– If the comparison is not successful, the logon fails
– If the fallback option is not enabled, the logon fails
Configuration with RADIUS Server

The IP address of the RADIUS server must match with the setting in the target device (parameter Radius
server IP address).
The shared key on the RADIUS server must match with the setting in the target device (parameter RADIUS
shared secret key).
The target device sends User-Name (attribute 1), User-Password (attribute 2), NAS Identifier (attribute 32) and
NAS Port (attribute 5) to the RADIUS server.
The RADIUS server should be configurated that way, that after successful authentication the role designed as a
vendor-specific value (attribute 26) will be sent back.
You find detailed information on the RADIUS protocol under https://tools.ietf.org/html/rfc2865.
Table 9-1 Structure of the authentication request from CP-8000/CP-802x:
Connection via HTTP Connection via HTTPS

User-Name User-Name
User-Password User-Password
NAS-Identifier = "00:E0:A8:B0:DC:80" NAS-Identifier = "**:**:**:**:**:**"
NAS-Port= "80" NAS-Port = "443"
Table 9-2 Structure of the response from the configured RADIUS server:
User role Administrator User role Guest

Service-Type = Login-User Service-Type = Login-User
Cisco-AVPair = "priv-lvl=15" Cisco-AVPair = "priv-lvl=0"

DC8-037-2, Edition 11.2020
9.1 Telecontrol
Schematic Procedure of the Authentication
[dw_CP-8000_radius, 1, en_US]
Figure 9-7 Schematic Procedure of the Authentication
9.1.2.2 Change Web Server Password

The change of the password for the web server takes place in the directory tree under SICAM A8000 CP-80xx
| Master module | Network settings | IP address | HTTP web server.
After the initial logon, an indication appears that a password must be defined. The password is required in
order to protect the respective target device against unauthorized access.
To change the settings, the parameter HTTP web server must be set to enabled.
NOTE
i With engineering via SICAM WEB, the HTTP web server is system-internally fixed enabled.
After transfer of the entered values, a new logon is only possible with the current password.
Password Assignment Rules
The following entries are allowed:
• Empty password possible (only with non-secure password)
• Maximum 8 characters
• Digits 0…9
• Letters A…Z and a…z (no umlauts)
• Special characters ! ? § $ % & / \ ( ) { } [ ] = ^ ° ´ ` ‘ @ * # | + - , . ; : _
• A secure password must contain at least one digit, one uppercase letter, one lowercase letter and one
special character
NOTE
i In case of problems with passwords please contact the Siemens Support Center

DC8-037-2, Edition 11.2020
9.1 Telecontrol
9.1.2.3 Differentiation Secure/Non-Secure Passwords

The selection of the secure password storage resides in the directory tree under SICAM A8000 CP-80xx |
Master module | Network settings | Security (the checkbox “Show all parameters” must be activated).
All passwords can be stored in the target device in a secure manner. Thereto the passwords are stored irrever-
sibly encrypted in a location not accessible by unauthorized persons. This applies for all protocols using a pass-
word for authentication, such as HTTP, HTTPS, SNMP.
NOTE
i For secure password storage/https in CP-8000 a hardware revision >= ***CC is required.
With the parameter Secure Password Storage you can select between non-secure or secure password
storage.
[sc_settings_network_security, 1, en_US]
Figure 9-8 Settings for Network Security
If the secure password storage is activated (parameterSecure Password Storage = YES), the parameter
HTTP/HTTPS must be HTTPS, otherwise a warning is generated in the diagnosis.

DC8-037-2, Edition 11.2020
9.1 Telecontrol
With the secure password storage, a password is masked behind 8 bullets, independently of the real length of
the password, even if no password was entered.
Example:
[sc_settings_snmp_passw1, 1, en_US]
Figure 9-9 Settings with Secure Password Storage
If the secure password storage is deactivated (parameter Secure Password Storage = NO), a password is
displayed as readable original text.
Example:
Figure 9-10 Settings with Non-Secure Password Storage

DC8-037-2, Edition 11.2020
9.1 Telecontrol
Change a Password
When modifying a secure password, a dialog is displayed when selecting a password field in the Settings page.
When opening the dialog both input fields are always empty and the checkbox “Unhide characters” is deacti-
vated.
Example:
Figure 9-11 Dialog for Change a Password
You must enter the same password in both input fields (new password and verify new password). Each
entered character is shown as a bullet.
Example:
Figure 9-12 Dialog with Entered Password
When activating the checkbox “Unhide characters”, the entered characters in both input-fields are displayed.
Example:
Figure 9-13 Dialog with Entered Password in Plain Text

DC8-037-2, Edition 11.2020
9.1 Telecontrol
• To close the dialog, click (new entries are discarded)
• To confirm the entries, click
With the entries are checked against conformity and against the guideline for the password assignment.If
the checks are not successful, a notification is shown in the dialog.
Example:
Figure 9-14 Dialog Invalid Password Entered
If all checks have been passed, the dialog is closed and the new password is valid.
• When pressing the button , the target device stores the password; if the secure password storage is
active, the password is encrypted before the storage
Switching Between Secure and Non-Secure Password

Secure passwords and non-secure passwords are stored separately in CP-8000/CP-802x.
If you enter a non-secure password in the target device, and you activate the secure password storage after-
wards, you must enter a new secure password. The non-secure one still remains stored, but it is deactivated.
If you deactivate the secure password storage afterwards, the non-secure password is active again and the
new secure password is deactivated.
9.1.2.4 Set IP Addresses

IP address settings are in the directory tree under SICAM A8000 CP-80xx | Master Module | Network
settings | IP address.
[sc_settings_network_ip_addresses, 1, en_US]
Figure 9-15 Settings IP Addresses

DC8-037-2, Edition 11.2020
9.1 Telecontrol
Compliant IP addresses must be assigned for operation in a network (company intranet, networked plant). The
IP address for the Web server of your target device can be changed with the parameter Own IP address.
NOTE
i The IP settings depend on the configuration and the transmission media of your network. Contact your
network administrator for the setting of these parameters.
The details on setting the advanced parameters for secure network configurations are available in the
SICAM RTUs • SICAM TOOLBOX II Administrator Security Manual.
With the parameter Mode of ethernet ports, you can define whether the interfaces X1 and X4 are oper-
ated using the same IP address or 2 separate IP addresses.
The presetting is 1 IP address (connected ports in switch mode).
NOTE
i The IP address set via SICAM WEB is only relevant when a DHCP server is not used (Autoconfiguration =
NO parameter).
When using a DHCP server the target device is automatically assigned the IP address. For more details see
9.1.2.7 Autoconfiguration (restricted operation mode).
With the selection 2 IP addresses (independent ports), you can define a 2nd IP address for X4. As a
result, you can access the target device also via X4 regardless of the network settings for X1, for example,
• X1: Process LAN
• X4: Office LAN

CP-8000/CP-802x server services are available at both interfaces.
Any resulting, further options have been described in the Appendix E Use Cases.
If it is not allowed to establish a connection between networks for security reasons, the use of a second IP
address at the interface X4 can be inhibited. For this purpose, define during initial parameterization whether
the parameter Mode of ethernet ports is permanently shown or hidden. Use the expert parameter
Advanced parameters | "Mode of ethernet ports" and select the following to adjust the setting:
• display (selection) (default)
• hide (freeze)
NOTE
i With the selection hide (freeze) this parameter and the parameter Mode of ethernet ports are
permanently hidden. It is then no longer possible to change these parameters!
The set operating mode remains unchanged unless the target device is restarted via a completely new
parameterization:
• Initialization with other parameters or with a newly created SD card (SICAM TOOLBOX II)
• Initialization with an empty SD card (SICAM WEB)
• Click to save the settings
The saved values require a restart of the target device and will only be active following the system startup.

DC8-037-2, Edition 11.2020
9.1 Telecontrol
NOTE
i After having changed the data the target device can only be addressed using the newly set IP address(es).
The current IP address is always shown on the LCD of the target device (main menu, Device information |
Device.
If it is no longer possible to access the Web server, check the IP settings of the engineering PC.
MAC Addresses of the Ethernet Interfaces

The local Ethernet interfaces X1 and X4 have 1 or 2 MAC addresses depending on the version of the module.
Designation MLFB Number of MAC
Addresses
CP-8000 -25/+70 °C Up to 6MF21010AB100AA0EE 1
CP-8000 -40/+70 °C Up to 6MF21011AB100AA0EE
CP-8000 -25/+70 °C From 6MF21010AB100AA0FF 2
CP-8000 -40/+70 °C From 6MF21011AB100AA0FF
CP-8021 Up to 6MF28021AA00 BB 1
CP-8021 From 6MF28021AA00 CC 2
CP-8022 Up to 6MF28022AA00 BB 1
CP-8022 From 6MF28022AA00 CC 2
The MAC addresses are listed on the name plate on the side of the module housing (see 6.1.1.2 Type Plate
and 6.1.2.2 Type Plate).
If the parameter Network settings | IP addresses | Mode of Ethernet ports has been set to
the value 1 IP address (connected ports in switch mode), then the first MAC address (of X1) is
used at both interfaces. If the parameter Network settings | IP addresses | Mode of Ethernet
ports has been set to the value 2 IP addresses (independent ports), then separate MAC addresses
are used for X1 and X4.
Access Options for the Engineering PC during Operation
DHCP Service Used DHCP Server Access Option IP Address SICAM IP Address Engi-
Available A8000 neering PC
Autoconfigura- Irrelevant Ethernet (X1) Own IP address <free address
tion = NO = <set value> in subnet of
SICAM A8000>
Autoconfigura- Yes Ethernet (X1) Own IP address assigned by DHCP
tion = YES = <automatic> server if DHCP has
been enabled at PC
Autoconfigura- No Ethernet (X1) Own IP address <free address
tion = YES = <169.254.0.1> in subnet
169.254.0> (IP
address in SICAM
A8000 is not routed)
Irrelevant Irrelevant Ethernet (X4) Own IP address <free address
(X4) = <set in subnet SICAM
value> A8000> 66
Irrelevant Irrelevant Point-to-point (X2) 172.16.0.1 172.16.0.2 (assigned
by SICAM A8000)
66 applies only if mode of Ethernet ports = 2 IP addresses (independent ports)

DC8-037-2, Edition 11.2020
9.1 Telecontrol
9.1.2.5 Security Settings for Internet Security (IPSec)

The settings for internet security reside in the direction tree under SICAM A8000 CP-8022 | Master module |
Network settings | Security (the checkbox “Show all parameters” must be activated).
The communication over IPSec can be enabled with the parameter IP Security activated.
With activated IPSec VPN a firewall is automatically activated. Only activated services can pass the firewall.
Interface Assignment
Furthermore, the assignment of the Ethernet interfaces according to the respective application is necessary.
You will find more information in section 9.1.7.2 Interfaces for Communication.
You will find further information in appendix E.6 Usage with IPSec VPN.
NOTE
i The detailed information on Internet Security can be found in the document SICAM A8000 Serie / RTUs /
TOOLBOX II / Device Manager ADMINISTRATOR Security Manual.
9.1.2.6 Settings for Internal GPRS Modem (CP-8022)

The settings for the internal GPRS modem reside in the direction tree under SICAM A8000 CP-8022 | Master
module | Network settings | GPRS (the checkbox “Show all parameters” must be activated).
[sc_settings_network_gprs_man, 1, en_US]
Figure 9-16 GPRS Settings (CP-8022)
The GPRS communication is activated or deactivated with the parameter enable GPRS communication.
With selection YES the parameter string for GPRS is visible and the parameter Mode of ethernet ports
will be hidden. The both interfaces X1 and X4 operate as connected ports in switch mode via 1 common IP
address.
You will find further information in appendix E.7 Usage of the Internal GPRS Modem (CP-8022).
Common Settings
With the parameter Operator selection you can define how to select the mobile radio provider:
• With selection automatic (default) the operator is read from the SIM card
• With selection manual the operator must be entered according to the corresponding SIM card; the oper-
ator list can be read out from the SD card, if the parameter GPRS log is set to operator list.

DC8-037-2, Edition 11.2020
9.1 Telecontrol
The entry for SIM PIN is needed if the SIM card is PIN protected. The default setting is an empty PIN
(unlocked SIM card).
With parameter APN the acccess point name can be configured. If no APN is entered, then the default APN is
used implicitly during the PDP context activation (acccess point name from provider).
The PPP authentication is required depending on the operator’s policy in particular APNs. If authentica-
tion is needed, then PPP user name and PPP password have to be entered.
Monitoring of the GPRS Modem

Additional settings for the handling in case of error reside in the direction tree under SICAM A8000 CP-8022 |
Master module | Network settings | GPRS | advanced parameters.
With the parameter advanced parameters | GPRS log the detail level of the logging procedure can be
selected (Operators / Modem status / Detailed logging of communication to modem (AT-
CMD). Logs will be saved on the SD card in the GPRS directory.
With the parameter advanced parameters | Debug trigger the action upon GPRS modem error is
defined for debugging (None / Stop logging on modem error).
Monitoring of the Mobile Radio Network

Settings for the monitoring of the mobile radio network reside in the direction tree under SICAM A8000
CP-8022 | Master module | Network settings | GPRS | Mobile radio ping supervision.
[sc_settings_network_gprs_ping, 1, en_US]
Figure 9-17 GPRS Monitoring (CP-8022)
With the setting Ping supervision enabled = Yes the belonging parameters get visible. With this func-
tion, 5 ping request are sent with an interval of 20 seconds to up to 2 adjustable IP addresses (Ping peer IP
address 1, Ping peer IP address 2). If no reply is received, the ping counts as failed attempt. After
that, the cycle time Ping interval (setting between 60 s and 3600 s) is started for the next ping
request.

DC8-037-2, Edition 11.2020
9.1 Telecontrol
After a specified number of failed attempts a selectable reaction is triggered. The following settings are
provided:
• Parameter Number of fails before action, selectable 2 to 100
• Parameter Action after ping failure, selection

– logging only
– mobile connection re-establishment
– mobile module restart
– device reboot
Interface Assignment
Furthermore, the assignment of the Ethernet interfaces according to the respective application is necessary.
You will find more information in section 9.1.7.2 Interfaces for Communication.
9.1.2.7 Autoconfiguration
CP-8000/CP-802x provides the option of being configured automatically by means of a complete autoconfigu-
ration file via DHCP service. The autoconfiguration file is a previously generated CP-8000/CP-802x backup (see
9.3.2 Download Device Settings).
NOTE
i If a SD card generated through copy is used, it is mandatory to delete the file dhcpid, located in AUTO-
CONFIG folder.
The selection of the autoconfiguration resides in the directory tree under SICAM A8000 CP-80xx | Master
module | AU common settings (the checkbox SHOW ALL PARAMETERS must be activated).
[sc_settings_au_common_autoconfig, 1, en_US]
Figure 9-18 Setting Autoconfiguration
With the expert parameter Autoconfiguration = YES the DHCP service is activated.
In a network with DHCP server, the DHCP server defines the IP address on X1. If the DHCP server is no more
available, the target device can be accessed via X1 with the IP address 169.254.0.1, if the“ lease time” of the
DHCP server is already terminated. Otherwise the IP address from the DHCP server is used until the termination
of the time. The time is defined by the DHCP server.

DC8-037-2, Edition 11.2020
9.1 Telecontrol
NOTE
i DHCP can be easily disturbed and manipulated because DHCP clients accept any DHCP server. The acci-
dental activation of a DHCP server, for example by a simple DSL router or wireless router on delivery status
can largely paralyze a network. That may respond faster than the foreseen DHCP server and thereby distrib-
utes invalid configurations.
On the DHCP server, corresponding DHCP options must be configured:
• Option 6: DNS Servers (optional)
• Option 61: Client Identifier
• Option 66: TFTP Server Name
• Option 67: Backup File Name
Example: settings on a DHCP server

[SETTINGS]
IPBIND_1==172.16.0.5
IPPOOL_1=172.16.0.8-255
AssociateBindsToPools=1
UseClientID=1 ;
Trace=1
DeleteOnRelease=0
ExpiredLeaseTimeout=3600
ConfigureUnknownClients=0;
IgnoreUnknownClients=1;
[GENERAL]
LEASETIME=300
NODETYPE=8
[test1]
IPADDR=172.16.0.10
;IPADDR=0.0.0.0
SUBNETMASK=255.255.248.0
;NEXTSERVER=172.16.0.55
;ROUTER_0=172.16.0.250
OPTION_6=172.16.0.5 ;
OPTION_66="tftp.at" ;
OPTION_67="SICAM_A8000_BACKUP_Siemens_Testanlage_Station_0dac08636b6790f868f7870
168d08df2.cmc" ;
[DNS-SETTINGS]
EnableDNS=0
FORWARD=172.16.0.5
[TFTP-SETTINGS]
EnableTFTP=1
PortRange=AUTO;
ROOT=C:\_DATA\DHCP_DNS_SERVER\DHCP-SERVER\dhcp\wwwroot
writePermission=1
[HTTP-SETTINGS]

DC8-037-2, Edition 11.2020
9.1 Telecontrol
EnableHTTP=1
ROOT=E:\DHCP-SERVER\dhcp\wwwroot
TFTP Server
The TFTP protocol serves for the loading of operating systems or configurations via the network. It is designed
for simpliest data transfer based on the client-server principle. The protocol supports only the reading and
writing of files and is suitable for applications that do not require the complex procedures of FTP.
The TFTP server must provide the configuration file of the respective CP-8000/CP-802x target device.
NOTE
i TFTP does not provide authentication or encryption. Therefore, the Internet access should be denied by
default when enabled TFTP service when using a firewall.

After the first startup with activated autoconfiguration, the engineering PC must be connected to the target
device via the interface X1.
Start the web browser and enter the IP address 169.254.0.1 in the address bar.
[sc_logon_autoconfig1, 1, en_US]
Figure 9-19 Dialog for the Entry of the DHCP Identifier
A dialog for the entry of the DHCP identifier and the confirmation appears.
• Click on (OK), if you want to save the DHCP identifier
• Click on (Skip to Logon), if you want to log on directly at the target device
As soon as this setting is saved, the target device uses this identifier as DHCP option 61. If no identifier is set,
the MAC address of the device is used. The parameter can be changed also afterwards in operation via SICAM
WEB.
In order that the autoconfiguration works, at least the DHCP options 66 and 67 must be given. The TFTP Server
Name can be either an IP address or likewise a Full Qualified Domain Name (see DNS), if one or more DNS
servers are supplied via DHCP.
The target device connects to the TFTP server indicated in DHCP option 66 and downloads the configuration
file indicated in DHCP option 67. The file is checked upon integrity by means of a cryptologic hash function
that is calculated over the file.

DC8-037-2, Edition 11.2020
9.1 Telecontrol
The result is compared with the hash value in the filename:
• if the file is valid, it is accepted and all settings in the target device are adapted
• with different results, the file is deleted and no changes are carried out
Depending on the setting of the “Lease Time” on the DHCP server, the configuration can be updated. If the
same file name is given, the target device keeps its settings. If another name is given, the file is downloaded
again and the settings are accepted.
9.1.3 Common Settings
9.1.3.1 Configuration of the Target Device

The settings for the configuration of the target device reside in the directory tree under SICAM A8000
CP-80xx | Master module | AU common settings.
[sc_settings_au_common, 1, en_US]
Figure 9-20 Settings of the Target Device
Here reside the basic settings for the identification of the target device (Customer, Plant, Device Name,
Region, Component).
If the target device is integrated in an existing plant, these values should fit to the existing parameterization
(conformable region and component number, same customer and plant designation).
Furthermore you can enter, amongst others, the values for Short Pulse Duration and Long Pulse
Duration. Depending on whether the target device receives a command with short or with long command
output time, the command is output with the duration adjusted here.
Application Program
With use of an application program, the address can be set which uses the application program for the genera-
tion of its data. The setting thereto resides under SICAM A8000 CP-80xx | Master module | AU common
settings | common address of ASDU (CASDU).
CASDU1 (least significant octet) and CASDU2 (most significant octet) result automatically in the CASDU upon
storing.
For the command processing according to IEC 60870-5-101/104, the parameter AU-common settings |
Forward ACTCON, DEACTCON, ACTTERM to control defines whether commands are passed on to the
application program with or without command response.

DC8-037-2, Edition 11.2020
9.1 Telecontrol
9.1.3.2 Topology
The settings for the topology reside in the directory tree under SICAM A8000 CP-80xx | Master module |
Topology.
[sc_settings_topology, 1, en_US]
Figure 9-21 Settings for the Topology
Here is defined via which interface which remote stations are accessible, and which basical data flow direction
is needed to these remote stations (control direction, monitor direction or both directions).
For the parameterization of remote stations you can insert lines with the button .
With activation of the checkbox SHOW ALL PARAMETERS the complete parameter block can be made visible
(the hidden expert parameters serve for special applications and need not to be used in normal case).
9.1.3.3 Failure Behavior upon Fault

The setting for the failure behavior resides in the directory tree under SICAM A8000 CP-80xx | Master
module | BSE common settings.
The occurance of a heavy fault can lead to an undefined state in the processing of the firmware on the Master
Module. Normally the target device stops thereby the firmware and records an error in the diagnosis.
You can change this behavior with the parameter Failure behavior. The setting Restart firmware
means that the firmware of the target device performs an automatic startup in case of error. This might be
advantageous upon a temporary error that disappears by itself.
You find further information thereto in the manual SICAM RTUs Common Functions System and Basic System
Elements, chapter System Services, section Operating States, Firmware Shut Down.
9.1.4 Configuring Optional Modules
• Menu Home | Hardware & Protocols
9.1.4.1 Overview
In addition to the Master Module, you can equip the following optional system elements:
• Protocol elements for the communication

Hardware (integrated on the Master Module) + loadable firmware
• I/O Master Modul for peripheral functions

Hardware (integrated on the Master Module) + loadable firmware
– internal I/O Modules (only CP-8000) are detected automatically
– external I/O Modules are detected automatically

DC8-037-2, Edition 11.2020
9.1 Telecontrol
The protocol elements and I/O Modules supported by CP-8000/CP-802x are listed in chapter 2.2.1 Protocol
Elements and 2.1.4 I/O Modules
Prerequisite for the equipment of additional system elements is that the corresponding Firmwares are loaded
in the target device. You find the instruction thereto in section 9.3.7 Update Firmware.
The hardware configuration overview resides in the directory tree under SICAM A8000 CP-80xx .
[sc_hw_config_bse, 1, en_US]
Figure 9-22 Configuration Overview
This page shows an overview of the equipped system elements:
• Master module
• I/O Master module

– I/O modules
• Communication module (protocol elements)
NOTE
i The selection in the drop-down boxes contains only that system elements, whose firmware has already
been loaded into the Master Module (with indication of the revision level).
By clicking you will leave the equipment program. Changes will not be saved, that means, selected system
elements will be rejected.
• In the respective drop down list, select the desired entry
• If you want to save the adjusted equipment, click
A restart request appears:
[sc_hw_config_restart_request, 1, en_US]
Figure 9-23 Dialog Restart Device
You have the possibility to abort the procedure.

DC8-037-2, Edition 11.2020
9.1 Telecontrol
• Confirm by clicking
The target device performs a restart, refer to 9.3.1 Restart Device.

During startup, the settings are stored on the SD card and the configuration pages for the selected system
elements are built in SICAM WEB.
9.1.4.2 Protocol Elements

You can install up to 4 protocol elements. The hardware for a protocol element has been integrated at the
Master module.
You can find the selection of the protocol elements also in the directory tree under SICAM A8000 CP-80xx |
Master module.
[sc_hw_config_pre, 1, en_US]
Figure 9-24 Configuration of the Protocol Elements
• Select a protocol element for the corresponding protocol element number to configure a protocol
element
A restart of the target system is required after having selected the protocols and accepted them with .
After system startup the configured protocol elements appear in the directory tree under SICAM A8000
CP-80xx | Master module | PRE <0...3>: <Protocol name>.
Parameterization takes place for each protocol on the settings page. Parameters of protocols that have been
newly identified have been assigned their default values.
Refer to the chapter 12 Communication Protocols for more detailed information on the protocols.
9.1.4.3 I/O Master Module

In CP-8000/CP-802x you can equip 1 I/O Master Module. The hardware for the I/O Master Module as well as 2
internal I/O Modules are integrated on the Master Module.
With use of external I/O Modules, these must be connected (mechanically) to the target device before the
engineering in SICAM WEB.

DC8-037-2, Edition 11.2020
9.1 Telecontrol
The selection of the I/O Master Module resides in the directory tree also under SICAM A8000 CP-80xx |
Master module | I/O Master module.
[sc_hw_config_pe, 1, en_US]
Figure 9-25 Configuration of the I/O Master Module
• In order to configure a I/O Master Module, select the desired firmware:

USIO80: operation with SICAM TM I/O Modules
USIO81: operation with SICAM I/O Modules
After the selection of the I/O Master Module a notification appears:
[sc_hw_config_assignments_info, 1, en_US]
Figure 9-26 Notification on Firmware Installation
This means, a new I/O Master Module (firmware revision) can be accepted only if no signals are assigned to
the I/O Master Module and to I/O Modules. If occasion arises, the corresponding signal assignments must be
deleted (see 9.1.11.3 Assigning Signals to the I/O Master Module and 9.1.11.4 Assigning Signals to the I/O
Module
• Click on the button in order to close the dialog
After the selection of the I/O Master Module and acceptance with a restart of the target device is required.
Thereby, the target device automatically detects the internal and the connected external I/O Modules. Hence,
for the equipment of an I/O Module you need not make a selection.
After the startup the configured I/O Modules appear in the directory tree under SICAM A8000 CP-80xx |
Master Modul | I/O Master Modul | <0...7>: <I/O Module name>.

DC8-037-2, Edition 11.2020
9.1 Telecontrol
[sc_hw_config_iom_learnt, 1, en_US]
Figure 9-27 Newly Equipped I/O Modules After Startup
You find more detailed information on the I/O Modules in the sections 5.4 SICAM I/O Modules und 5.5 SICAM
TM I/O Modules.
Please pay attention to the configuration notes and rules for the equipment of I/O Modules in section 2.1.4 I/O
Modules.
NOTE
i The detected configuration is checked with each additional startup against the actually connected I/O
Modules. With deviation the target device notifies an error.
If the once detected configuration is changed, pay attention to section 11.6.3 Adapting Newly Installed I/O
Modules in the Parameter Setting.
9.1.5 Configuring Time Management
9.1.5.1 Time Synchronization

The internal clock of CP-8000/CP-802x serves for the time tagging of generated data
• from the periphery
• from the optional open-/closed-loop control function
• for the records in the diagnosis

The resolution of the time tag is 1 ms.

DC8-037-2, Edition 11.2020
9.1 Telecontrol
The settings for time synchronization are in the directory tree under SICAM A8000 CP-80xx | Master module
| Time management | Common settings (the Show all parameters check box must have been activated).
[sc_settings_time_common, 1, en_US]
Figure 9-28 Common Time Settings
CP-8000/CP-802x supports the following time synchronization variants (can be selected with the Synchro-
nizing of the automation unit parameter):
• Remote synchronization via serial communication or LAN
• Free running
With the parameter Monitoring time for synchroniz. event, you can define the monitoring for
remote synchronization. A warning is recorded in the diagnosis if the time has already been set and synchroni-
zation does not take place within the parameterized time.
With the parameter Unit of time for free running and monitoring time, you can define the
time unit (seconds or minutes) for the monitoring time.
For detailed information on the time synchronization, refer to the manual SICAM RTUs Common Functions,
System and Basic System Elements, chapter System Services, section Time Management.
Time Synchronization with Multi-Point Traffic

The time is sent to CP-8000/CP-802x from a central station (time master). The time master must synchronize
at least every 60 s, so that the minimum resolution of 10 ms is achieved. If time synchronization fails, the
target device records a warning in diagnosis after 10 min.
Time Synchronization with Dial-Up Traffic

The time is sent to CP-8000/CP-802x from the central station (time master). Each synchronization can exclu-
sively take place when the connection is being established.

DC8-037-2, Edition 11.2020
9.1 Telecontrol
Time Synchronization with Ethernet
NTP/SNTP Client
(S)NTP-client settings are in the directory tree under SICAM A8000 CP-80xx | Master module | Network
settings | NTP/SNTP time synchronization client.
[sc_settings_network_ntp_sntp_time_sync, 1, en_US]
Figure 9-29 NTP Client Settings
For communication according to IEC 60870-5-104 or IEC 61850, the time can be synchronized via NTP or
SNTP. For this purpose, you can enter the IP addresses of up to 4 NTP servers, as well as the NTP synchroniza-
tion cycle time.
For the time synchronization, the current NTP server is determined by voting. This is carried out according to
the following weighting:
1. Attainability
2. Stand-alone (NTP server does not receive a time)
3. Distance (with regard to the time)
A voting takes place after each 3-fold cycle time (parameter NTP cycle time). The minimum voting time is 1
hour. If time synchronization fails, the target device records a warning in the diagnosis. The warning is
recorded after 10 minutes in the event of time synchronization via another automation unit (without NTP
server).
The parameters have been described in the sections 12.6.5.6 Clock Synchronization and 12.7.6.6 Clock
synchronization.

DC8-037-2, Edition 11.2020
9.1 Telecontrol
NTP Server
The settings for the NTP server are in the directory tree under SICAM A8000 CP-80xx | Master module |
Network settings | NTP time synchronization server (the check box Show all parameters must have been
activated).
[sc_settings_network_ntp_time_sync, 1, en_US]
Figure 9-30 NTP Server Settings
If further devices requiring time synchronization via NTP have been connected to a target device, these
devices can also be supplied with the time via the NTP server function. In this process, take into account that
the corresponding target device itself is already synchronized via a serial interface or NTP.
9.1.5.2 Daylight Saving Time Rule

The settings for the daylight-saving time reside in the directory tree under SICAM A8000 CP-80xx | Master
module | Time management | Daylight saving time (the checkbox SHOW ALL PARAMETERS must be acti-
vated).
[sc_settings_time_daylight_saving, 1, en_US]
Figure 9-31 Settings Daylight Saving Time Rule
You can enable the daylight saving time and select the format for the setting of the daylight saving time rule.
In the subdirectory Daylight saving time rule you can adjust the exact data for the daylight saving time/
normal time switchover.

DC8-037-2, Edition 11.2020
9.1 Telecontrol
9.1.6 Local Time Setting
• Menu Home | Time

This function enables setting the time manually on the target device. This function is particularly useful for
stand-alone operation.
This is how to set the time of your engineering PC at the target device:
• Click the button to load the PC time in the target device.
[sc_time_set_computer, 2, en_US]
Figure 9-32 Set the PC Time in the Target Device

This is how to set a random time at the target device:
• Activate the check mark “Enter manually”
• Edit the fields “Date”, “Time”, and “Time zone” as required
• Click the button to load the defined time to the target device
[sc_time_set_manually, 2, en_US]
Figure 9-33 Set a Random Time in the Target Device
9.1.7 Configuring Communication

DC8-037-2, Edition 11.2020
9.1 Telecontrol
9.1.7.1 Common Settings

The common communication settings are in the directory tree under SICAM A8000 CP-80xx | Master module
| Communication | Common settings (the “Show all parameters” check box must be activated).
[sc_settings_communication_common, 1, en_US]
Figure 9-34 Common Communication Settings
Periodical Transfer of User Data (Type Identifications TI 30 to TI 40)

A periodic level can be assigned to each user-data message (for data-point-specific routing only). 3 periodical
levels are possible, whereby a parameterizable period duration can be assigned to each of these levels. Once
the period duration of a level expired, all periodical data of this level is chained. Chaining is carried out sepa-
rately for each supplementary system element.
The chain of periodical data is processed using a separate priority level from the downstream process image. If
a new chaining trigger is activated and the chain is not empty, this trigger is saved. If the chain runs empty, a
saved trigger initiates a new chaining process of the periodical data at this level.
Blocked data is not triggered for transmission during a blocking condition.
Warning of the Filling Level of Priority Channels

For the system information that is not stored and the transparent channel, a warning for the filling level is
generated. For each channel, a warning is available for the entire master module (not for each remote
station). The filling level for the incoming and outgoing warning can be parameterized in percent for each
priority channel.
For the system information, the warning is activated if one of the remote stations reaches the parameterized
filling level for the incoming warning. It is reset once all remote stations that have set the warning have
reached the parameterized filling level for the outgoing warning.
For the transparent information, there is a channel for all remote stations. Here, the warning is set or reset
once the filling level of the channel has reached the parameterized thresholds.
9.1.7.2 Interfaces for Communication

CP-8000/CP-802x can communicate simultaneously via several physical interfaces. An interface must be exclu-
sively assigned for each configured protocol element.
The interface assignment for each protocol element is listed in the directory tree under SICAM A8000 CP-80xx
| Master module | PRE <0...3>: <Protocol name> | Common settings.

DC8-037-2, Edition 11.2020
9.1 Telecontrol
[sc_settings_pre1_common, 1, en_US]
Figure 9-35 Common Settings for Communication
Protocols that can be equipped can be assigned with the Interface parameter:
Firmware Protocol Name Interface
X1 X2 X3 X4 X6 X7
103MT0 IEC 60870-5-103 master – ✓ ✓ – ✓ –
BPPT0 IEC 60870-5-101 end-end – ✓ ✓67 – ✓ –
DIAST0 Dial-up traffic slave – ✓ – – ✓68 –
ET83 Ethernet TCP/IP (IEC 61850 Ed.1) ✓69 – – ✓69 – –
ET84 Ethernet TCP/IP (IEC 60870-5-104) ✓69 – – ✓69 – ✓
ET85 Ethernet TCP/IP (IEC 61850 Ed.2) ✓69 – – ✓69 – –
UMPMT0 IEC 60870-5-101 master – ✓ ✓ – ✓ –
UMPST0 IEC 60870-5-101 slave – ✓ ✓ – ✓ –
AGPMT0 AGP interfacing master – ✓ ✓ – ✓ –
BMCUT0 Benning MCU ASCII protocol – ✓ ✓67 – ✓ –
COUMT0 IEC 62056-21 (IEC 1107) master – ✓ ✓ – ✓ –
DNPMT0 DNP3 master – ✓ ✓ – ✓ –
DNPST0 DNP3 Slave – ✓ ✓ – ✓ –
DNPiT2 DNP3 TCP/IP master ✓69 – – ✓69 – –
DNPiT1 DNP3 TCP/IP Slave ✓69 – – ✓69 – –
MODMT2 MODBUS RTU master – ✓ ✓ – ✓ –
MODST0 MODBUS RTU slave – ✓ ✓ – ✓ –
MBCiT0 MODBUS TCP master (client) ✓69 – – ✓69 – –
MBSiT0 MODBUS TCP slave (server) ✓69 – – ✓69 – –
PCBST0 SAT SK 1703 PCMBA slave – ✓ ✓ – ✓ –
RP5UT1 ABB RP570/571 slave – ✓ ✓ – ✓ –
SMST0 ASCII-Prot. for SMS alerting – ✓ – – ✓68 –
ST1ST0 Siemens SINAUT ST1 slave – ✓ ✓ – ✓ –
TG8ST0 L&G Telegyr 800 slave – ✓ ✓ – ✓ –
67 only in operating mode RS-422

68 only in operating mode RS-232
69 no selection required for the mode of Ethernet ports = 1 IP address (connected ports in switch mode)

DC8-037-2, Edition 11.2020
9.1 Telecontrol
Protocols via Ethernet

The assignment of the Ethernet interface for all (integrated and equippable) protocols via Ethernet depends
on the use case:
• Use of 2 independent Ethernet interfaces (parameter Mode of ethernet ports = 2 IP addresses

(independent ports))
• Communication with IP Security (parameterIP security activated = YES)
• GRPS communication (parameter Enable GPRS communication = YES) (applies to CP-8022 only)
The Ethernet interface is assigned in the directory tree under SICAM A8000 CP-80xx | Master module |
Network settings | IP addresses | Interface mapping.
[sc_settings_network_ip_interface, 1, en_US]
Figure 9-36 Network Settings for IP Interface Mapping
Overview of the Selection Options for Ethernet Interface Assignment
IP Security enabled
NO YES
IPSec VPN Tunnel 1 enabled – YES NO YES
IPSec VPN Tunnel 2 enabled – NO YES YES
GPRS communication NO X1 X1-VPN0 X1-VPN1 –
X4 X4 X4
YES – GPRS-VPN0 GPRS-VPN1 GPRS-VPN0
X1/X4 X1/X4 GPRS-VPN1
X1/X4
With the Interface WEB-Server parameter only X1 or X4 can be selected.
NOTE
i If IP security has been enabled, LAN must be selected with the parameter Network settings | IP
address | Network connection X1 (Network connection X2) even if IP security is used via
GPRS.

DC8-037-2, Edition 11.2020
9.1 Telecontrol
9.1.7.3 Selection of the Transmission Facility

After having assigned a physical interface use the Transmission Facility parameter to select a transmis-
sion facility that has been preconfigured for the corresponding protocol element (does not apply to point-to-
point traffic and Ethernet).
A dynamic subdirectory is created in the directory tree under SICAM A8000 CP-80xx | Master module | PRE
<0...3>: <Protocol name> | Common settings depending on the selected transmission facility.
[sc_settings_pre1_common_modem, 1, en_US]
Figure 9-37 Common Settings at the Protocol Element
Adapt the settings at the protocol element to the transmission facility values in this subdirectory. Example: the
speed for the transmission to the remote station via the Baud rate parameter.
For more detailed information, refer to the chapter Communication Protocols, section Optimized Parameters
for Selected Transmission Facilities.
A request to restart appears after having saved the settings.
• Click if you want to change further parameters
• Click to restart
9.1.7.4 Settings for Messages

The message settings are in the directory tree under SICAM A8000 CP-80xx | Master module | Communica-
tion | PRE<0...3> | IEC 60870-5-101/104 (the check box Show all parameters must have been activated).

DC8-037-2, Edition 11.2020
9.1 Telecontrol
[sc_settings_communication_pre1_iec60870, 1, en_US]
Figure 9-38 Message Settings
These settings are independent from the communication type and exist individually for each protocol element
at the Master module:
• Transmission with/without time tag
• Variable message elements
• Command runtime monitoring
• ACTCON monitoring
Transmission with/without Time Tag

Information objects supported by CP-8000/CP-802x can either be transmitted to the control center with the
time tag or without the time tag. This is specified selectively for each type identification.
The associated parameter are in the Transmission with/without time tag subdirectory.
Variable Message Elements

For instance, the byte quantities of the identifiers in the message header can be parameterized for communi-
cation with different systems.
The settings at the Master module are in the Variable elements of the message subdirectory.
The associated information is available in the manual SICAM RTUs Common Functions for System and Basic
System Elements, Appendix Message formats.
The settings at the protocol element are in the directory tree under SICAM A8000 CP-80xx | Master module |
PRE <0...3>:<Protocol name> | Advanced settings | IEC 60870-5-101 (applies to multi-point traffic and
common traffic only).
The associated information is in the sections 12.3.5 Communication according to IEC 60870-5-101 and
12.4.5 Communication according to IEC 60870-5-101.
9.1.7.5 Data Management and Priority Control

The settings for data management and priority control are in the directory tree under SICAM A8000 CP-80xx |
Master module | Communication | PRE <0...3> | Advanced settings (the “Show all parameters” check box
must be activated).

DC8-037-2, Edition 11.2020
9.1 Telecontrol
[sc_settings_communication_pre1_advanced, 1, en_US]
Figure 9-39 Settings for Data Management and Priority Control
• Behavior during a communication failure
• Priority for emission

You can find the associated information in the manual SICAM RTUs Common Functions for System and Basic
System Elements, chapter Telecontrol, section Communication with other Automation Units, section Data
Storage, Behavior during a Communication Failure, and section Priority Control.
9.1.8 Configuration of the Decentralized Archive

The decentralized archive serves for the local storage of events of a substation, and - whenever necessary - for
the transmission to the control system. By means of that, it is for instance possible to recover the archive of a
control system after a communication fault.
The configuration of the decentralized archive resides in the directory tree under SICAM A8000 CP-80xx |
Master module | Decentral archiving (the checkbox SHOW ALL PARAMETERS must be activated).
[sc_settings_decentral_archive, 1, en_US]
Figure 9-40 Settings Decentralized Archive

DC8-037-2, Edition 11.2020
9.1 Telecontrol
All the data points that are recorded in the event list are simultaneously recorded in the decentral archive. The
definition thereto resides in the signal parameterization (see Configurable Logging and Displaying of Signal
States, Page 410).
The data points to be recorded are archived chronologically during operation. The record happens for the
following categories:
• Commands upon status change
• Binary information items upon status change
• Measured values according to parameter Recording grid for measured values

You find the detailed information on the settings in the manual SICAM RTUs Common Functions System and
Basic System Elements, chapter "Telecontrol", section "Decentralized Archiving".
NOTE
i The data records of the decentralized archive are registered in configurable files. The files are stored on the
SD card. The record of data points is therefore only possible with equipped SD card.
Memory Configuration Archive

With the help of this parameter it is possible to select the configuration of the archive stored on the SD card.
You may select this parameter referring to your field of application. The smaller the bandwidth of your
communication line is the smaller the separated files should be.
Recording Grid for Measured Values

This parameter defines the recording grid (the cycle time) for measured values. It can be set from 1 to 60
minutes.
Timeout for Filetransfer

With this parameter it is defined when the data transmission will be cancelled if a disturbance occurs during a
file transfer (connection error etc.).
Number of Bytes for CASDU, IOA, COT in the Archive

You can select the format of saving the entries into the archive. If there is a control system which needs
another format for the CASDU, IOA or COT you can define this with the help of these parameters. The parame-
ters only affect the entries in the archive, however, it will not affect any other data in your automation unit.
NOTE
i It is not possible to call the archive from more than one different control system which use different
settings for the number of bytes for CASDU, IOA, COT, because the settings for these parameters affect the
whole archive of a automation unit.
Spontaneous Transmission of Directory List

It is possible to transmit the directory list spontaneously. This behavior is specified in the IEC 60870-5. It
means, that whenever there is a change in the directory list (one file was written, or an old file was deleted),
this change may be reported to the control system. However, since upon initialization of a file transfer the
control system asks for the directory list anyway, it is not useful to transmit the directory list spontaneously.

DC8-037-2, Edition 11.2020
9.1 Telecontrol
NOTE
i The addresses that are calculated automatically are not shown in the web browser. If such an address is set
in the parameterization of the telecontrol function, an error message occurs on attempt to apply.
9.1.9 Configuration of the Process Data Archive

The process data archive serves for the local storage of binary information items and measured values of a
substation, and - whenever necessary - for the download and evaluation on the engineering PC.
The configuration of the process data archive resides in the directory tree under SICAM A8000 CP-80xx |
Master module | Process Data | Archive (the checkbox SHOW ALL PARAMETERS must be activated).
[sc_settings_process_archive, 1, en_US]
Figure 9-41 Setting Process Data Archive
Only those data points are recorded in the archive, which are parameterized for that. The assignment thereto
can be performed in the signal parameterization (see Configurable Logging and Displaying of Signal States,
Page 410).
The data points to be recorded are archived chronologically during operation. The archive captures up to
5.000.000 records over a maximal period of 3 months. The record happens for the following categories:
• Binary information items: upon status change (process data message)
• Measured values: according to parameter Recording grid for measured values (process data
measured values)
NOTE
i The contents of the process data archive is deleted with every change of the configuration of process data
measured values and/or of process data message (for instance if a new signal is added). If needed, down-
load the archive before such kind of change (see 9.3.6 Download Process Data Archive).
Change of a signal name affects the archive only after startup. Before startup the archive shows the
previous signal name.
Recording Grid for Measured Values

This parameter defines the recording grid (the cycle time) for measured values. It can be set from 1 to 60
minutes.

DC8-037-2, Edition 11.2020
9.1 Telecontrol
9.1.10 Configuration of the Local Process Data Display (CP-8000 Only)

The local process data display (cockpit) enables visualization of the process-signal status on the LCD. Binary
information items, measured values, and integrated totals can be selected for the cockpit by assigning them to
groups.
The configuration of the local process data display is in the directory tree under SICAM A8000 CP-80xx |
Master module | Process data | Cockpit (the “Show all parameters” check box must be activated).
[sc_settings_process_groups, 1, en_US]
Figure 9-42 Settings for the Local Process Data Display
Up to 32 freely definable groups with up to 256 entries each are available for the local process data display in
the cockpit. They can be assigned to groups in the signal parameterization (see Configurable Logging and
Displaying of Signal States, Page 410).
• Enter the respective desired name (max. 24 characters) in the VALUE column
• Press the button to save the settings
The group display on the LCD (menu Cockpit) is thus immediately refreshed.
NOTE
i If a group (number) is assigned in the signal settings for which a name has not been created, the default
group name appears in the cockpit (for example: Group_6).
This is how you get to the display of signal states on the LCD:
• Menu Monitoring | Cockpit (see Cockpit, Page 555)
9.1.11 Configuring Periphery and Internal Signals
• Menu Home | Signals

In order to use the peripheral functios, on the I/O Master Module a corresponding firmware must be selected
in the Configuration page.
The firmware of the I/O Master Module provides the functions for the technological preparation of the inputs/
outputs (signal preprocessing, signal postprocessing).
CP-8000/CP-802x supports 2 internal and up to 6 external I/O Modules. The following types can be used:

DC8-037-2, Edition 11.2020
9.1 Telecontrol
• Digital input (DI) for the acquisition of binary information and counting pulses
• Analog input (AI) for the acquisition of currents, voltages and temperatures
• Digital output (DO) of commands and binary information
• Analog output (AO) of currents and voltages
I/O Modules are equipped with an individual number of physical inputs/outputs that serve for the acquisition
or for the output of electrical signals.
The names of the I/O Modules appear in the directory tree corresponding to the equipped configuration.
9.1.11.1 Defining Signals

You can define signals from scratch, modify existing signals and assign them to the corresponding system
element. Electrical signals are assigned to an I/O module by the relative terminal assignment.
[sc_signals_start_page, 1, en_US]
Figure 9-43 Start Page to Define Signals
Define the inputs and outputs that can be connected from the hardware (HW pins) at the I/O module as data
points in the target device in the ASSIGNMENT tab.
The PARAMETER tab features the type-specific parameter block for the assigned signals to set the process-tech-
nical functionality for the assigned signals.
Refer to the manual entitled SICAM RTUs Common Functions for Peripheral Elements according to
IEC 60870-5-101/104 for the description of the functions for signal preprocessing and signal postprocessing
and the associated parameters.
An overview of parameters and ranges of values has been provided in the chapter SICAM TOOLBOX II Online
Help, Parameter Documentation and Diagnostic Info, SICAM RTUs and 1703 Ax (IEC) Periphery, Firm-
wares, USIO80 (USIO81).
This is how to create a new signal:
• Click the button in the top right to open the working area to create signals.

DC8-037-2, Edition 11.2020
9.1 Telecontrol
[sc_signals_define_add_line, 1, en_US]
Figure 9-44 Working Area to Create Signals
• Enter the desired number of rows (each row corresponds to 1 signal)
• Click the button
2 new signals have been created in the following example:
[sc_signals_define_add_line_result, 1, en_US]
Figure 9-45 Signals Created from Scratch
This is how to define a signal:
• Enter the signal name (Name)
• Enter the message address (CASDU1, CASDU2, IOA1, IOA2, IOA3)
• Select the type identification from the drop-down list (TI)

DC8-037-2, Edition 11.2020
9.1 Telecontrol
[sc_signals_define_ti, 1, en_US]
Figure 9-46 Selection of the Type Identification for a Signal
Signal Name
The signal name can have between 1 and 128 characters. It is used on the signal list, for the entry in the event
logging list, and for the test functions (visualization via SICAM WEB and LCD).
Message Address
The message address is used to assign data points for communication and the open-/closed-loop control func-
tion. Refer to the manual entitled SICAM RTUs Common Functions for System and Basic System Elements,
System Services section, Data-Flow Control paragraph for more detailed information.
Type Identification
The description of the various type identifications (TI) is available in the manual SICAM RTUs Common Func-
tions for System and Basic System Elements, Appendix Message formats.
Duplicating and Deleting Lines

This is how you can duplicate lines:
• Highlight the line/lines you want to copy.
• Enter the desired factor.
• Click the button.

DC8-037-2, Edition 11.2020
9.1 Telecontrol
[sc_signals_duplicate_select, 1, en_US]
Figure 9-47 Highlighted Signals for Duplication
In this example the EM_0 and EM_1 signals are duplicated twice each.
[sc_signals_duplicate_result, 1, en_US]
Figure 9-48 Duplicated Signals
Define the name, IEC address, and type identification for the new signals.
This is how you can delete lines:
• Highlight the corresponding line.
Automatically Filling and Automatic Incrementation

This function is designed to quickly and conveniently create several signals.

DC8-037-2, Edition 11.2020
9.1 Telecontrol
Example: You have created 4 new signals. The IOA1 of the first new signal must start with 3. The value must
consecutively increase by the value 1 for all following signals.
• Activate the check mark in front of the desired rows (you can also highlight all rows by activating the
check box above the column on the far left)
• Activate the check box over the IOA1 column in the table
• Enter 3 as the value in the “Start from” text box (this text box is always automatically prefilled with the
overlapping value made up of the highlighted column and the first highlighted row)
• Enter 1 as the value in the “Increment” text box
• Click the button (“Fill selected”)
[sc_signals_fill_selected, 1, en_US]
Figure 9-49 Highlighted Signals to have them Automatically Filled in
Result: IOA1 has been consecutively increased by 1 from value 2 onwards for all consecutive signals:
[sc_signals_fill_selected_result, 1, en_US]
Figure 9-50 Automatically Completed Column

DC8-037-2, Edition 11.2020
9.1 Telecontrol
9.1.11.2 Assigning Signals to the Master Module

If you have already defined signals, you can assign these to the master module for further processing.
Proceed as follows to assign signals to the master module:
• Click the button at the top right to close the working area to create signals
• Select the SICAM A8000 CP-80xx | Master Module directory
• Highlight the signals you would like to assign on the right-hand side
• Click the button (“Assign”)
[sc_signals_assign_bse, 1, en_US]
Figure 9-51 Highlighted Signals for Master Module
Assigned signals have now been listed in a table in the ASSIGNMENT tab.
[sc_signals_assign_bse_result, 1, en_US]
Figure 9-52 Assigned Signals at the Master Module

DC8-037-2, Edition 11.2020
9.1 Telecontrol
NOTE
i Click the bar on the right and/or left next to the working area to enlarge the working area.
• Select the desired category for the corresponding signal from the list box
[sc_signals_assign_bse_cat, 1, en_US]
Figure 9-53 Selecting the Desired Category
The list box exclusively offers the categories that match the signal's TI.
Proceed as follows to configure the parameters of the assigned signals:
• Open the PARAMETERS tab
• Select the previously defined category for the newly assigned signal from the list box
[sc_signals_param_bse_filter_pvd, 1, en_US]
Figure 9-54 Selecting the Defined Category
All signals of the selected category (at the selected system element) are shown in the table. In this process,
the signal name, telegram address, and type identification are transferred from the working area to create
signals.

DC8-037-2, Edition 11.2020
9.1 Telecontrol
After having selected the category you can adjust the process engineering parameters for the corresponding
signals.
• Activate the “Show All Columns” check box if you would like to edit expert parameters
• Regularly save your changes

Further steps: 9.3.1 Restart Device.
Configurable Logging and Displaying of Signal States

Process signals that have been assigned to the master module can be configured for logging (alarm, event,
archive) and for the display on the LCD (Cockpit – CP-8000 only).
Table 9-3 Categories and Signal Types for the Corresponding Logging
Category TI Alarm List Event List Archive Cockpit

Process data for command TI 45 ✓
TI 46 ✓
Process data for message TI 30 ✓ ✓ ✓ ✓
TI 31 ✓ ✓ ✓ ✓
Process data for measured value TI 34 ✓ ✓
TI 35 ✓ ✓
TI 36 ✓ ✓
TI 37 ✓ ✓
Proceed as follows to define signals for logging and/or display on the LCD:
Example: Process Data for Command
• Go to the Parameters tab and select the “Process Data for Command” category
All signals that have been assigned to this category are displayed.
• Enter the desired texts for names and states for each signal
• Select for each signal whether it should be logged as an event
[sc_signals_param_bse_pc, 1, en_US]
Figure 9-55 Setting Signals to Enter in the Event Lists
For a description of the parameters see Parameters for Assignment at the Master Module, Page 413 (Process
Data for Command).

DC8-037-2, Edition 11.2020
9.1 Telecontrol
Example: Process Data for Message
• Go to the Parameters tab and select the “Process Data for Message” category
• Enter the desired texts for names and states for each signal
• Select for each signal whether it should be logged as an event
• Select for each signal whether it should be logged as an alarm
• Select for each signal whether it should be logged in the process data archive
[sc_signals_param_bse_pvd1, 1, en_US]
Figure 9-56 Setting Signals to Enter in the Process Data Archive
• Assign the desired group number and position within the group for process visualization in the cockpit
[sc_signals_param_bse_pvd2, 1, en_US]
Figure 9-57 Assigning Messages to Groups and Position Numbers
In this example 3 messages have been assigned to group positions 1, 3 and 4. If position 2 is not used, an
empty row is shown at this point on the LCD (see Cockpit, Page 555).
Data for Message).

DC8-037-2, Edition 11.2020
9.1 Telecontrol
Example: Process Data for Measured Value
• Go to the Parameters tab and select the “Process Data for Measured Value” category
• Enter the desired texts for the name of each signal
• Select for each signal whether it should be logged in the process data archive
• Assign the desired group number and position within the group to each signal for process visualization in
the cockpit
[sc_signals_param_bse_pva1, 1, en_US]
Figure 9-58 Assigning Measured Values to Groups and Position Numbers
In this example 2 measured values have been assigned to group positions 1 and 5. If positions 2, 3, 4 are not
used, a blank row is shown at this point on the LCD (see Cockpit, Page 555.
• Enter the measuring ranges for value adaptation
• Enter the number of decimal places for the display
[sc_signals_param_bse_pva2, 1, en_US]
Figure 9-59 Adjusting the Measuring Range and Decimal Places
Data for Measured Value).

DC8-037-2, Edition 11.2020
9.1 Telecontrol
Proceed as follows to define groups for the cockpit:
• Home | Parameters menu

(refer to 9.1.10 Configuration of the Local Process Data Display (CP-8000 Only) for more information)
Proceed as follows to access the signal status log in SICAM WEB:
• Home | Alarms & Events | Events menu

(refer to9.1.14.1 Show Event List for more information)
• Home | Alarms & Events | Alarms menu

(refer to 9.1.14.2 Show Alarm List for more information)
Proceed as follows to access the signal status log at the LCD:
• View | Events | DEF Events menu

(refer to Events | DEF Events, Page 553 for more information)
• View | Alarms menu

(refer to Alarms, Page 555 for more information)
Parameters for Assignment at the Master Module
Category Parameter Meaning

Communication control tele- Control_func- • Revision function
gram tion_(KOM)
• Test function
• Block function
PRE Log element
Station_(KOM) Station number (selectively 0 to 99 or all)
CASDU1_(KOM) Data point address.
The complete address is formed from CASDU1,
CASDU2, IOA1, IOA2, and IOA3.
CASDU1 and CASDU2 to 255 = No spontaneous
forwarding
CASDU2_(KOM) Data point address.
forwarding
Function_group_(KOM) Function group number (0 to 255)
QID-BSE Source identification for basic system element
QID-ST Source identification for station number for multi-
point traffic type 0 to 99 for R-QID 0 to 254.
If automatic, source ID is taught in.
QID-ZSE Source identification for supplementary system
element

DC8-037-2, Edition 11.2020
9.1 Telecontrol

Decentralized archiving Function_(DEAR) • Archive data
• Main directory address
• Subdirectory address
• File address
element
Error telegram for detail diag- ZSE Supplementary System Element
nosis table Diagnostic class When selecting “All Bits, All Records, All Classes”
the “Diagnostics Record” and “Diagnostics Bit”
parameters do not carry any meaning
Diagnostic record Diagnostics Record 0 to 254 = Record number
within the selected diagnostics class
255 = Sum across all bits of all records (the "Diag-
nostics bit" parameter carries no meaning)
Diagnostic bit Bit number (0 to 15; all bits)
Error telegram for sum diag- Error_location/BSE Error location/basic system element
nostics table Error_location/ZSE Error location/supplementary system element
Error Type Error class in diagnostics

DC8-037-2, Edition 11.2020
9.1 Telecontrol

Parameters for measured Parameter_type • According to NUC
values ACP 1703
• Threshold value
• Smoothing
• Lower limit for transmission of measured
value
• Upper limit for transmission of measured
value
• Activation of parameters for measured values
GI_group General interrogation (group 1 to 16; none)
MW_CASDU1 Data point address.
priority forwarding
MW_CASDU2 Data point address.
priority forwarding
MW_IOA1 Data point address.
priority forwarding
priority forwarding
priority forwarding
MW_TI Type identification according to IEC
60870-5-101/104

DC8-037-2, Edition 11.2020
9.1 Telecontrol

Process data for command Event_(B) The data point is shown in the event list
Text_(B) The data point is shown with this name (at max.
13 characters)
Status_TextOn_(B) The ON status of a command is shown with this
name (at max. 6 characters)
Status_TextOff_(B) The OFF status of a command is shown with this
Status_TextDis_(B) The disturbed position of a double-point indica-
tion/command is shown with this name (at max. 6
characters)
Status_TextDiff_(B) The intermediate position of a double-point indica-
characters)
element

DC8-037-2, Edition 11.2020
9.1 Telecontrol

Process data for measured QID-BSE Source identification for basic system element
value QID-ST Source identification for station number for multi-
point traffic type 0 to 99 for R-QID 0 to 254. If
automatic, source ID is taught in.
element
Archive_(MW) The data point is entered in the local archive
Text_(MW) The data point is shown with this name (at max.
13 characters)
Cockpit_GroupNo_(MW) The data point is shown in the cockpit in this group
(1 to 32)
Cockpit_GroupPos_(MW The data point is shown in the cockpit at this posi-
) tion (1 to 256)
X_0%_(MW) Value adaptation: Lower limit of the range of
values used in the external (protocol-specific)
format. The corresponding internal value is config-
ured at Y_0%.
X_100%_(MW) Value adaptation: Upper limit of the range of
values used in the external (protocol-specific)
format. The corresponding internal value is config-
ured at Y_100%.
Y_0%_(MW) Value adaptation: Lower limit of the range of
values used in the selected internal format. The
internal format is specified by the TI (type identifi-
cation). The corresponding external value is
configured at X_0%.
Y_100%_(MW) Value adaptation: Upper limit of the range of
values used in the selected internal format. The
internal format is specified by the TI (type identifi-
cation). The corresponding external value is
configured at X_100%.
Decimal_places_(MW) Number of decimal places (at max. 7)
Unit_(MW) The value is shown with this unit (max. 8 charac-
ters)

DC8-037-2, Edition 11.2020
9.1 Telecontrol

Process data for message Event_(MLD) The data point is shown in the event list
Alarm_(MLD) The data point is shown in the alarm list
Archive_(MLD) The data point is entered in the local archive
Text_(MLD) The data point is shown with this name (at max.
13 characters)
Status_TextOn_(MLD) The ON status of a message is shown with this
Status_TextOff_(MLD) The OFF status of a message is shown with this
Status_TextDis_(MLD) The disturbed position of a double-point indica-
characters)
Status_TextDiff_(MLD) The intermediate position of a double-point indica-
characters)
Cockpit_GroupNo_(MLD The data point is shown in the cockpit in this group
) (1 to 32)
Cockpit_GroupPos_(ML The data point is shown in the cockpit at this posi-
D) tion (1 to 255)
element

DC8-037-2, Edition 11.2020
9.1 Telecontrol

Protocol element control tele- Control_function_(PRE) • 0 to 239 = Defined by PRE firmware
gram
• 240 = GI request
• 241 = Reserved
• 242 = Control location specification
• 244 = CASDU selective GI request
• 245 to 255 = Spare for additional BSE func-
tions
Edge_(PRE) • positive edge
• Negative edge
• Status (0 = Function, 1 = Function + 1)
PRE_(PST) Protocol element number
• PRE0 to PRE3
• Distribute via multi master function
Station • 0 to 99 = Station number
• 125 = Not all stations
• 255 = Not used
Additional_param- 0 to 65535 = Meaning defined by PRE firmware for
eter_(PRE) each function
element
104-Address
TI Type identification according to IEC
60870-5-101/104
• Single-point indication
• Single command
Protocol element return infor- Feedback func-
mation message tion_(PRE)
PRE_(RM) Protocol element number (0 to 3)
Station Station number (selectively 0 to 99; to all stations;
station not used)

DC8-037-2, Edition 11.2020
9.1 Telecontrol

Redundancy of control tele- Control_function_(RED) • User priority
gram
• A/P control
• Keylock switch
• Listening mode
• A/P control for SCA-RS failure
• Switchover block
Failure_response_(RED) • Terminate message
• Maintain status
BSE_(RED) Basic system element
PRE_(RED) Protocol element number
Priority_(RED) Priority 0 (lowest) to priority 14 (highest)
element
Redundancy of feedback tele- Feedback_func- • Redundancy state
gram tion_(RED)
• Switchover runs for global switchover
• Key switch of SCA-RS System A active
• Key switch of SCA-RS automatic
• Key switch of SCA-RS System B active
• Listening mode
BSE_(RED) Basic system element
PRE_(RED) Protocol element number

DC8-037-2, Edition 11.2020
9.1 Telecontrol

Selective data flow routing PRE Protocol element number (0 to 3)
Station 0 to 99 = Selective station
Not used = Single-Point-PRE or Multi-Point-PRE at
all remote partners
Data class • Data class 1
• Class 2 data
Periodic_forwarding Selection of periodic level or no periodic
forwarding
Event_data
Time_marker Forwarding with or without time stamp
Function Group
Address_conversion 0 = Yes, 1 = No
Change_Prefix_of_Meas
ured_value
New_CASDU1 New data point address. The complete address is
formed from CASDU1, CASDU2, IOA1, IOA2, and
IOA3.
CASDU1 and CASDU2 to 255 = No address conver-
sion
New_CASDU2 New data point address. The complete address is
IOA3.
sion
New_IOA1 New data point address. The complete address is
IOA3.
sion
IOA3.
sion
IOA3.
sion
Selectivity Selective or to all remote partners
element

DC8-037-2, Edition 11.2020
9.1 Telecontrol

Special application of input OUT_CASDU1 Data point address
OUT_CASDU2 Data point address
OUT_IOA1 Data point address
OUT_TI Type identification according to IEC 60870 5
101/104
inversion NO/YES
TI31_selection OFF/ON
Fail_resp Failure response
Fail_SUBSTITUTE VALUE Substitute value in the event of failure
Individual object
number
Command Status • Do not take into account command status
• Command status ON before OFF
• Command status OFF before ON
Command output time For TI 160: 0 to 6200•50 ms, for TI 45, 46, 47:
• 0 = No additional definition
• 1 = Short command output time
• 2 = Long command output time
• 3 = Persistent command
element
Special application of output Function • OR linkage, outgoing edge delayed
• AND linkage, outgoing edge delayed
• OR linkage, output as fleeting contact,
outgoing edge delayed
• Telegram conversion
• OR linkage, rising edge delayed
inversion NO/YES
Fail_resp_status Linkage type
Time delay Time delay n•100 ms
• 0 = No delay
• 1 = 100 ms
• 255 = 25.5 s
9.1.11.3 Assigning Signals to the I/O Master Module

If you have already defined signals, you can assign these to the I/O I/O master module for further processing.
Proceed as follows to assign signals to the I/O master module:
• Click the button in the top right to close the working area to create signals
• Select the SICAM A8000 CP-80xx | Master Module | I/O Master Module directory

DC8-037-2, Edition 11.2020
9.1 Telecontrol
[sc_signals_assign_pe, 1, en_US]
Figure 9-60 Highlighted Signals for I/O Master Module

Assigned signals now appear in a table in the ASSIGNMENT tab.
[sc_signals_assign_pe_result, 1, en_US]
Figure 9-61 Assigned Signals at the I/O Master Module
Click the bar on the right and/or left next to the working area to enlarge the working area.
• Select the processing type for the corresponding signal from the corresponding list box

DC8-037-2, Edition 11.2020
9.1 Telecontrol
[sc_signals_assign_pe_type, 1, en_US]
Figure 9-62 Selecting the Processing Type
The list box exclusively offers the processing types that match the signal's TI. It is exclusively possible to assign
software data points to the I/O master module.
• Select the data point for the corresponding signal from the corresponding list box
[sc_signals_assign_pe_dp, 1, en_US]
Figure 9-63 Selecting the Data Point
The list box exclusively offers data points that match the selected processing type and are not used yet.
HW pins are irrelevant here and for this reason, they cannot be edited.
• Select the previously defined processing type for the newly assigned signal from the list box

DC8-037-2, Edition 11.2020
9.1 Telecontrol
[sc_signals_param_pe_filter_sw_di, 1, en_US]
All signals of the selected processing type (at the selected system element) are shown in the list. In this
process, the signal name, telegram address, and type identification are transferred from the working area to
create signals.
The processing types offered at the I/O Master Module depend on the installed firmware for the I/O Master
Module and exclusively feature expert parameters.
• Regularly save your changes

Parameters for Assignment at the I/O Master Module
Processing type Parameter Meaning

SW_CO_INTE – Command interlocked –
SW_DI – Software data point for digital –
input
SW_DO – Software data point for digital –
output
SW_LOC_REM – Local/remote criterion QID-BSE Source identification for basic system element
QID-ST Source identification for station number for
multi-point traffic type 0 to 99 for R-QID 0 to
254.
element
SW_REV – Revision QID-BSE Source identification for basic system element
QID-ST Source identification for station number for
254.
element

DC8-037-2, Edition 11.2020
9.1 Telecontrol

SW_CONTROL_LOCATION – Control QID-BSE Source identification for basic system element
location QID-ST Source identification for station number for
254.
element
ACTCON_yes_no Send from ACTCON and ACTTERM
SW_CO_SQ – Command error acknowl- –
edgment
SW_DO_TE-6460 –
9.1.11.4 Assigning Signals to the I/O Module

If you have already defined signals, you can assign these to the I/O modules for input and output purposes.
Proceed as follows to assign signals to an I/O module:
• Click the button in the top right to close the working area to create signals
• Select the SICAM A8000 CP-80xx | Master Module | I/O Master Module | <0 to 7>: <Module name>
directory
[sc_signals_assign_do, 1, en_US]
Figure 9-65 Highlighted Signals for I/O Module

DC8-037-2, Edition 11.2020
9.1 Telecontrol
Assigned signals have now been listed in a table in the ASSIGNMENT tab.
[sc_signals_assign_do_result, 1, en_US]
Figure 9-66 Assigned Signals at the I/O Module
Click the bar on the right and/or left next to the working area to enlarge the working area.
• Select the processing type for the corresponding signal from the corresponding list box.
[sc_signals_assign_do_type, 1, en_US]
The list box exclusively offers the processing types that match the signal's TI.
• Select the data point for the corresponding signal from the corresponding list box.

DC8-037-2, Edition 11.2020
9.1 Telecontrol
[sc_signals_assign_do_dp, 1, en_US]
Figure 9-68 Selecting the Data Point
The list box exclusively offers data points that match the selected processing type and are not used yet.
The HW pin is assigned automatically as soon as you have defined the processing type and data point for the
signal.
• Select the previously defined processing type for the newly assigned signal from the list box
[sc_signals_param_do_filter_sc, 1, en_US]
All signals of the selected processing type (at the selected system element) are shown in the list. In this
process, the signal name, telegram address, and type identification are transferred from the working area to
create signals.
The processing types offered at the I/O master module depend on the configured firmware for the I/O master
module.

DC8-037-2, Edition 11.2020
9.1 Telecontrol
After having selected the processing type you can now configure the process engineering parameters of the
associated signals.
[sc_signals_param_do_sc, 1, en_US]
Figure 9-70 Result after having selected the Processing Type
• Save your changes

Automatically Showing Signal States

Process signals that are recorded or output using HW pins are automatically configured for process visualiza-
tion using SICAM WEB and for process visualization on the LCD.
Automatic process visualization in SICAM WEB is in the Home | I/O Modules menu (see 9.1.13.2 Display
Process Values).
Automatic process visualization on the LCD is in the View | I/O Modules menu (see I/O Modules, Page 557).

DC8-037-2, Edition 11.2020
9.1 Telecontrol
Parameters for Assignment at the DI Module

DI_DM – Double-point Inversion_0 Inversion (S)
indication input NO/YES
Chatt_DP_QDS Data point quality identification for chattering
messages
BL/IV
Inversion_1 Inversion (S)
NO/YES
Blocking Block (= not used) (S)
NO/YES
MSP_monitoring Signaling-voltage supervision: The sensor voltage is
monitored using a dedicated Power Monitoring input
(S)
ON/YES
Chatt_number Number of fleeting contacts for chatter suppression
(S)
1 to 255
SW_Filter_t Software filter time in seconds (S)
0.001 to 16.383
Chatt_t Chatter time in seconds. 0 = No chatter suppression
(S)
0.1 to 6553.5
intermediate_pos_t Intermediate position suppression time in seconds 0 =
No intermediate position suppression (S)
0.1 to 6553.5
Disturbed_position_t Disturbed position suppression time in seconds. 0 =
No disturbed position suppression (S)
0.1 to 6553.5
AREC_Sign_t Time for signaling the automatic reactivation (AREC)
in seconds 0 = No AREC signaling (S)
0.1 to 25.5
ON_before_OFF Definition of the sequence for activation of double
commands/double-point indications: NO: OFF is I/O
with lower I/O number ON is I/O with greater I/O
number YES: ON is I/O with lower I/O number OFF is
I/O with greater I/O number.
NO/YES
Module_selec- Switchover for Power Monitoring treatment (PM)
tion_MSP_monitoring Standard PM (PM inputs per module) or input IN D17
of a DI module as PM input for all modules.
ATTENTION: A DI module must be selected.
Chatt_t_stabil Chatter suppression: Stability time in seconds
0 = Stability time defined by Flatt_t parameter (S)
0.1 to 6553.5

DC8-037-2, Edition 11.2020
9.1 Telecontrol

DI_EM – Single-point inversion Inversion (S)
indication input NO/YES
Blocking Block (= not used) (S) NO/YES
Chatt_DP_QDS Data point quality identification for chattering
messages
BL/IV
Input function Input functionality
This parameter configuration makes it possible to
block the indication input for revision treatment. (S)
(S)
ON/YES
Chatt_number Number of fleeting contacts for chatter suppression
(S)
1 to 255
SW_Filter_t Software filter time in seconds (S)
0.001 to 16.383
Chatt_t Chatter time in seconds. 0 = No chatter suppression
(S)
0.1 to 6553.5
Status_chattering_message Message status in telegram with BL bit
Time_delay_t Time delay of the On message in seconds
Module_selection_MSP_ Switchover for Power Monitoring treatment (PM)
Monitoring Standard PM (PM inputs per module) or input IN D17
of a DI module as PM input for all modules. ATTEN-
TION: A DI module must be selected.
Chatt_t_stabil Chatter suppression: Stability time in seconds. 0 =
Stability time defined by Flatt_t parameter (S)
0.1 to 6553.5

DC8-037-2, Edition 11.2020
9.1 Telecontrol

DI_ZW – Meter impulse Telegram_lock_time Telegram lock time in seconds. Identical telegrams are
recording discarded without error message within this time
0.1 to 6553.5
Interval_time_0 Interval time. An interval can also be input as the
trigger for transmission or trigger for freezing the
counter status. In this case, plan the associated time.
Interval_time_1 Interval time. An interval can also be input as the
trigger for transmission or trigger for freezing the
counter status. In this case, plan the associated time.
inversion Inversion (S)
NO/YES
NO/YES
Type Conditioned value type (S)
• Frozen absolute value

• Frozen relative value
(S)
NO/YES
Transmi_trigger Trigger for transmission. The trigger to forward the
frozen counter status can be initiated by a counter
interrogation telegram (group), adjustable intervals or
the function plan. (S)
Freeze_trigger The trigger for freezing may differ from the trigger for
transmission (S)
Range_of_values Range of values of the meters (S)
Value Value per pulse (S)
0.0001 to 9999
Module_selec- Switchover for Power Monitoring treatment (PM)
tion_MSP_monitoring Standard PM (PM inputs per module) or input IN D17
of a DI module as PM input for all modules. ATTEN-
TION: A DI module must be selected.
SW_DI – Software data -
point for digital input
SW_DM_AWE – Auto- -
matic reactivation
SW_DM_NACHF – Originator address Permissible originator address
Manually updating QOC If a command is received with a different QOC, it is not
double-point indica- confirmed/terminated
tions
point traffic type 0 to 99 for R-QID 0 to 254
If automatic, source ID is taught in
element
SW_DM_SF – breaker -
tripping
SW_DM_SL – Switching -
operation in progress

DC8-037-2, Edition 11.2020
9.1 Telecontrol

SW_ZW_SET – Set QID-BSE Source identification for basic system element
metered value QID-ST Source identification for station number for multi-
point traffic type 0 to 99 for R-QID 0 to 254
element

DC8-037-2, Edition 11.2020
9.1 Telecontrol
Parameters for Assignment at the DO Module

DO_DB_1,5POL – Retry_suppression_t Command retry suppression time in seconds.
Double command A command with the same address is discarded
output 1.5-pole without error message within this time (S)
0.1 to 6553.5
Output_t_0 Command output time in seconds (S).
Please note: Effective only if no time has been stated in
the command telegram.
0.01 to 327.67
Selection_execution_t Maximum time between selection and execution
command (in seconds).
Renewed selection is required once this time has
expired.
0 = No selection command (direct command output)
0.1 to 102.3
Sync_t_0 The interlocking must be released within this time (in
seconds) after having received a command.
0 = No synchronization via interlocking release
0.1 to 6553.5
FB_MON_t Feedback monitoring time in seconds (S).
0 = No feedback monitoring
0.01 to 655.35
Prolong_t Command prolongation time in seconds (S)
0.01 to 327.67
0.01 to 327.67
0.1 to 6553.5
FB_Out_equal_add_0 Selection whether command output is carried out and
how the command confirmation must be designed
even though feedback is in the desired final position
before being output.
Please note: Effective only if FB_MON_t ≠ 0
Sync_input_t_0 The release must take place via the synchronization
input within this time (in seconds) after having
received a command.
0 = No synchronization via the synchronization input
Please note: Function effective only if sync_t = 0
0.1 to 6553.5
1_off_n_t_0 The 1-of-n release must take place within this time (in
0 = No 1-of-n release required.
0.1 to 25.5

DC8-037-2, Edition 11.2020
9.1 Telecontrol

received a command.
0.1 to 6553.5
1_of_n_t_1 The 1-of-n release must take place within this time (in
0.1 to 25.5
SF_command_seq_0 Switching sequence: Switch additional command
before or after the command
SF_Add_command_0 Switching sequence: Selecting the additional
command
SF_Command_seq_1 Switching sequence: Switch additional command
command
FB_MON_source_0 Feedback source for feedback monitoring
• Periphery
• Open/closed-loop control function
• Both (logical OR)
• Periphery
QID-ST Source identification for station number for multi-point
traffic type 0 to 99 for R-QID 0 to 254
element
QOC>8 If QOC > 8 (qualifier of command) are permitted, each
QOC > 8 is interpreted like QOC = 0
commands/double-point indications:
• NO: OFF is I/O with a lower I/O number

ON is I/O with a greater I/O number
• YES: ON is I/O with a lower I/O number
OFF is I/O with a greater I/O number
Regulating command Use as regulating command (S)
FB_Image Parameter is effective only with ACP 1703 platform

DC8-037-2, Edition 11.2020
9.1 Telecontrol

DO_DB_1POL – Double Retry_suppression_t Command retry suppression time in seconds.
command output 1- A command with the same address is discarded
pole without error message within this time (S)
0.1 to 6553.5
0.01 to 327.67
command (in seconds). Renewed selection is required
once this time has expired.
0.1 to 102.3
0.1 to 6553.5
0.01 to 655.35
0.01 to 327.67
Output_t_1 Command output time in seconds (S). Please note:
Effective only if no time has been stated in the
command telegram.
0.01 to 327.67
0.1 to 6553.5
received a command.
0 = No synchronization via the synchronization input.
0.1 to 6553.5
0.1 to 25.5

DC8-037-2, Edition 11.2020
9.1 Telecontrol

received a command.
0.1 to 6553.5
0.1 to 25.5
command
command
• Periphery
• Periphery
element
QOC > 8 is interpreted like QOC = 0
• NO: OFF is I/O with lower I/O number ON is I/O

with greater I/O number
• YES: ON is I/O with lower I/O number OFF is I/O

DC8-037-2, Edition 11.2020
9.1 Telecontrol

DO_DB_2POL – Double Retry_suppression_t Command retry suppression time in seconds. A
Command Output 2- command with the same address is discarded without
pole error message within this time (S)
0.1 to 6553.5
Output_t_0 Command output time in seconds (S). Please note:
Effective only if no time has been stated in the
command telegram.
0.01 to 327.67
0.1 to 102.3
0.1 to 6553.5
0.01 to 655.35
0.01 to 327.67
0.01 to 327.67
0.1 to 6553.5
received a command.
0.1 to 6553.5
0.1 to 25.5
Please note: Effective only if FB_MON_t ≠ 0.

DC8-037-2, Edition 11.2020
9.1 Telecontrol

received a command.
0.1 to 6553.5
0.1 to 25.5
command
command
• Periphery

• Periphery
element
QOC > 8 is interpreted like QOC = 0.
• NO: OFF is I/O with lower I/O number ON is I/O

• YES: ON is I/O with lower I/O number OFF is I/O

DC8-037-2, Edition 11.2020
9.1 Telecontrol

DO_DX – Double-point Fail_resp Response in the event of failure
indication and double
command output
• Retain
• Terminate
element
0 to 6553.5
FB_Image_CASDU1 Address of the associated feedback (S)
0 to 255
0 to 255
FB_Image_IOA1 Address of the associated feedback (S)
0 to 255
0 to 255
0 to 255
FB_Image_TI Type identification of the associated feedback (S)
• Single-point indication
• Double-point information
Term_with_Conf Sending termination directly after having sent the
confirmation (S)
NO/YES
0.01 to 327.67
Termination_t_0 Time between confirmation and termination (s).
0 = No termination
0 to 6553.5
FB_React_t_0 Message reaction time (S)
Pulse command: 0 = Time corresponds to output time
Persistent command: 0 = Time corresponds to termina-
tion time
0 to 6553.5
0.01 to 327.67
Termination_t_1 Time between confirmation and termination (s).
0 = No termination

DC8-037-2, Edition 11.2020
9.1 Telecontrol

0 to 6553.5
FB_React_t_1 Message reaction time (S)
tion time
0 to 6553.5

DC8-037-2, Edition 11.2020
9.1 Telecontrol

DO_EB_1.5POLE – Retry_suppression_t Command retry suppression time in seconds. A
Single command command with the same address is discarded without
output 1.5-pole error message within this time (S)
0.1 to 6553.5
Output_t Command output time in seconds (S).
the command telegram
0.01 to 327.67
0.1 to 102.3
Sync_t The interlocking must be released within this time (in
0.1 to 6553.5
0.01 to 655.35
0.01 to 327.67
FB_Out_equal_add Selection whether command output is carried out and
Please note: Effective only if FB_MON_t is not equal to
0.
Sync_input_t The release must take place via the synchronization
received a command.
0.1 to 6553.5
1_off_n_t The 1-of-n release must take place within this time (in
0.1 to 25.5
FB_MON_source Feedback source for feedback monitoring
• Periphery
SF_command_seq Switching sequence: Switch additional command
SF_Add_command Switching sequence: Selecting the additional
command

DC8-037-2, Edition 11.2020
9.1 Telecontrol

element

DC8-037-2, Edition 11.2020
9.1 Telecontrol

DO_EB_1POL – Single Retry_suppression_t Command retry suppression time in seconds. A
command output 1- command with the same address is discarded without
0.1 to 6553.5
0.01 to 327.67
0.1 to 102.3
0.1 to 6553.5
0.01 to 655.35
0.01 to 327.67
0.
received a command.
0.1 to 6553.5
0.1 to 25.5
• Periphery
command

DC8-037-2, Edition 11.2020
9.1 Telecontrol

element

DC8-037-2, Edition 11.2020
9.1 Telecontrol

DO_EB_2POL – Single Retry_suppression_t Command retry suppression time in seconds. A
command output 2- command with the same address is discarded without
0.1 to 6553.5
0.01 to 327.67
0.1 to 102.3
0.1 to 6553.5
0.01 to 655.35
0.01 to 327.67
0.
received a command.
0.1 to 6553.5
0.1 to 25.5
• Periphery
command

DC8-037-2, Edition 11.2020
9.1 Telecontrol

element
DI_EM – Single-point Reception format Data point source
indication output Fail_resp Response in the event of failure
• Retain
• Terminate
element

DC8-037-2, Edition 11.2020
9.1 Telecontrol

DO_EX – Single-point Reception format Data point source
indication and single- Fail_resp Response in the event of failure
command output
• Retain
• Terminate
element
0 to 6553.5
0 to 255
0 to 255
0 to 255
0 to 255
0 to 255
Term_with_Conf Sending termination directly after having sent the
confirmation (S)
NO/YES
Output_t Command output time in seconds (S)
the command telegram
0.01 to 327.67
Termination_t Time between confirmation and termination (s).
0 = No termination
0 to 6553.5
FB_React_t Message reaction time (S)
tion time
0 to 6553.5
SW_CO_SYNC_A – -
Command synchroniza-
tion abortion
SW_CO_SYNC_L – -
Command synchroniza-
tion in progress
SW_DO – Software data -
point for digital output

DC8-037-2, Edition 11.2020
9.1 Telecontrol
Parameters for Assignment at the AI Module

AI_I – Current value Power_frequency Hum suppression carried out for configured power
acquisition frequency (S)
• 50 Hz
• 60 Hz
• 16.7 Hz
Zero_range Zero range suppression (and plausibility check) (S)
NO/YES
Thresh_additive Change threshold in % of X_100% (S)
AI_T: In % of the temperature range
0 to 1000.0
Thresh_uncond Change threshold in % of X_100% (S)
0 to 103.0
NO/YES
Processing grid Acquisition grid in seconds
0.1 to 25.5
X_0% Nominal range in the physical unit of the input/output
(0%) (S)
-50.0 to 50.0
(100%) (S)
-50.0 to 50.0
Y_0% Technological or normalized value 0% (S)
-1000000000000000.000 to
1000000000000000.000
-1000000000000000.000 to
1000000000000000.000
Smoothing 0 to 99 in %. 0% = No smoothing, 99% = Maximum
possible smoothing
MW_CON_AR_Xg Limit of implausible range. Parameter setting effective
only if Zero_range_u_MW_CON set to as required
-103.00 to 103.00
zero_range_Xzu Upper limit of the zero range in % of X_100% (S)
-103.00 to 103.00
zero_range_Xzl Lower limit of the zero range in % of X_100% (S)
-103.00 to 103.00
zero_range_Yz Technological or normalized value of the zero range
(S)
-1000000000000000.000 to
1000000000000000.000
Zero_range_u_MW_CON Zero range suppression (and plausibility check) either
standard or can be planned as required (S)
• Standard
• Can be configured as required

DC8-037-2, Edition 11.2020
9.1 Telecontrol

OV_Suppr_t OV suppression time in seconds, 0= No OV suppres-
sion
0 to 255
Standard load The measuring range can be adapted by replacing the
load (S)
NO/YES

DC8-037-2, Edition 11.2020
9.1 Telecontrol

AI_U – Voltage value Power_frequency Hum suppression carried out for configured power
acquisition frequency (S)
• 50 Hz
• 60 Hz
• 16.7 Hz
Zero_range Zero range suppression (and plausibility check) (S)
NO/YES
0 to 1000.0
0 to 103.0
NO/YES
Processing grid Acquisition grid in seconds
0.1 to 25.5
(0%) (S)
-50.0 to 50.0
(100%) (S)
-50.0 to 50.0
-1000000000000000.000 to
1000000000000000.000
-1000000000000000.000 to
1000000000000000.000
Smoothing 0 to 99 in %. 0% = No smoothing, 99% = Maximum
possible smoothing
MW_CON_AR_Xg Limit of implausible range. Parameter setting effective
only if Zero_range_u_MW_CON set to as required
-103.00 to 103.00
zero_range_Xzu Upper limit of the zero range in % of X_100% (S)
-103.00 to 103.00
zero_range_Xzl Lower limit of the zero range in % of X_100% (S)
-103.00 to 103.00
zero_range_Yz Technological or normalized value of the zero range
(S)
-1000000000000000.000 to
1000000000000000.000
Zero_range_u_MW_CON Zero range suppression (and plausibility check) either
standard or can be planned as required (S)
• Standard
• Can be configured as required
OV_Suppr_t OV suppression time in seconds, 0= No OV suppres-
sion
0 to 255

DC8-037-2, Edition 11.2020
9.1 Telecontrol

Standard load The measuring range can be adapted by replacing the
load (S)
NO/YES
SW_COSPHI – Power Thresh_additive Change threshold in % of X_100% (S)
factor software AI_T: In % of the temperature range
0 to 1000.0
0 to 103.00
SW_CT_FDIR_I>_I>> I> Trigger value in ampere for overcurrent detection
For short circuit 0: Function switched off
50 to 2000
I>> Trigger value in ampere for overcurrent detection
For short circuit 0: Function switched off
50 to 2000
I>>_t Time delay for overcurrent detection
0.04 to 60
I>_t Time delay for overcurrent detection
0.04 to 60
t_reset Time for automatic reset
0 = Function switched off
SW_CT_FDIR_IN IN> Trigger value in ampere for ground fault
0: Function switched off
0.4 to 2000
IN>_Idir Ground current for ground-fault detection when using
wattmeter method
0.2 to 30
IN>_Neutral_point Neutral-point treatment
• Permanently grounded
• isolated
• Compensated
IN>_U0 Neutral displacement voltage in percent of the primary
voltage
0 to 100
IN>_U0_t Neutral displacement voltage time delay
0.04 to 60
IN>_t Delay for ground fault display
t_reset Time for automatic reset
0 = Function switched off
SW_CT_MW_SELECTION Measured_value_sel Measured value selection
0 to 1000.0
0 to 103.00

DC8-037-2, Edition 11.2020
9.1 Telecontrol

SW_CT_PDIR -
SW_F – Frequency soft- Thresh_additive Change threshold in % of X_100% (S)
ware AI_T: In % of the temperature range
0 to 1000.0
0 to 103.00
SW_PQ – Power software Thresh_additive Change threshold in % of X_100% (S)
0 to 1000.0
0 to 103.00
SW_REV – Revision -
SW_T_SPA_WA_NOK – QID-BSE Source identification for basic system element
Voltage transformer not QID-ST Source identification for station number for multi-
OK point traffic type 0 to 99 for R-QID 0 to 254
element
SW_UI – Voltage, current Thresh_additive Change threshold in % of X_100% (S)
software AI_T: In % of the temperature range
0 to 1000.0
0 to 103.00
T_AI_I – Current trans- Power_freq_trans Power frequency setting
former input Thresh_additive Change threshold in % of X_100% (S)
0 to 1000.0
0 to 103.00
Trans_X_100% Nominal range of the transformer/input: Secondary
8510: 1 A – 8511: Small signal (225 mV)
8510: 5 A - 8511: Small signal (225 mV)
Trans_Y_100% Nominal range of the transformer: Primary in KV of the
linked voltage or 240 V for direct measurement or in
ampere
50 to 800
Trans_Y_100% _5A Nominal range of the 5 A current transformer: Primary
in ampere. Applies to AI-8510 and X_100% = 5 A only.
50 to 400
Overrange Definition of the overrange for QDS "OV" in % of the
transformer's nominal range

DC8-037-2, Edition 11.2020
9.1 Telecontrol

T_AI_U – Voltage trans- Power_freq_trans Power frequency setting
former input Primary voltage correc- Correction value for primary voltage
tion
0 to 1000.0
0 to 103.00
Trans_X_100% Nominal range of the transformer/input: Secondary
• 8510: 100 V/SQRT3 – 8511: 3.25 V/SQRT3

• 8510: 240 V – 8511: 3.25 V/SQRT3
• 8510: 415 V/SQRT3 – 8511: 3.25 V/SQRT3
Trans_Y_100% Nominal range of the transformer: Primary in KV of the
linked voltage or 240 V for direct measurement or in
ampere
1.0 to 36.0
Transformer type Transformer type
Transformer angle Angle between transformer's over- and undervoltage
side
0 to 359
Overrange Definition of the overrange for QDS "OV" in % of the
transformer's nominal range

DC8-037-2, Edition 11.2020
9.1 Telecontrol
Parameter for Assignment at AO Module

AO_I – analog current FAIL_SUBSTITUTE_VALUE Substitute value, if the failure response has been config-
output ured to output substitute value (S)
-1000000000000000.000 to 1000000000000000.000
0 to 655.3
Fail_resp Response in the event of failure
• Retain
• Substitute value
NO/YES
(0%) (S)
-20.0 to 20.0
(100%) (S)
-20.0 to 20.0
-1000000000000000.000 to 1000000000000000.000
-1000000000000000.000 to 1000000000000000.000
Reception format Data point source
Spontaneous
0 = No termination
0 to 6553.5
QID-ZSE Source identification for supplementary system element

DC8-037-2, Edition 11.2020
9.1 Telecontrol

AO_U – Analog voltage FAIL_SUBSTITUTE_VALUE Substitute value, if the failure response has been config-
output ured to output substitute value (S)
-1000000000000000.000 to 1000000000000000.000
0 to 655.3
Fail_resp Response in the event of failure
• Retain
• Substitute value
NO/YES
(0%) (S)
-10.0 to 10.0
(100%) (S)
-10.0 to 10.0
-1000000000000000.000 to 1000000000000000.000
-1000000000000000.000 to 1000000000000000.000
Reception format Data point source
Spontaneous
0 = No termination
0 to 6553.5
QID-ZSE Source identification for supplementary system element
9.1.11.5 Signal Wiring

Different variants result for signal wiring.
Table 9-4 I/O Wiring Variants
Function Signal type connector circuitry

information acquisi- Single-point indica- 1 digital input
tion tion
Double-point informa- 2 successive digital inputs
tion
count pulse acquisi- Metered value 1 digital input
tion
Current/voltage Current 1 analog input
acquisition Voltage 1 analog input

DC8-037-2, Edition 11.2020
9.1 Telecontrol
Function Signal type connector circuitry

temperature acquisi- Temperature 2-phase 1 analog input
tion 3-phase
4-phase
Resistor 2-phase 1 analog input
3-phase
4-phase
Command Output Single command 1-pole 1 digital output
1.5-pole 1 digital output
+ 1 digital output for group relay
2-pole 2 successive digital outputs
Double command 1-pole 2 successive digital outputs
1.5-pole 2 successive digital outputs
+ 1 digital output for group relay
2-pole 4 successive digital outputs
Indication output Single-point indica- 1 digital output
tion
Current/voltage Current 1 analog output
output Voltage 1 analog output
Signal type and connection depend on the corresponding I/O module.
NOTE
i Note the data in the paragraph entitled 2.1.4.4 Configuration Rules for I/O Modules.
information acquisition
A suitable digital input module must have been installed for the parameter configuration of single-point indi-
cations or double-point indications and the DI signals to be used must have been assigned.
Sensor Voltage Monitoring
You can activate sensor voltage monitoring for digital inputs using the MSP monitoring parameter in each
case. Monitoring is carried out in groups:
Group 0:
IOM x – IN D00 to IN D07
Group 1:
IOM 1 – IN D10 to IN D13 (for DI-810x)
IOM x – IN D10 to IN D17 (for DI-610x, DI-811x)
The last input of a group (IN D07 and IN D13 or IN D17) must have the secured sensor voltage wired to it for
sensor voltage monitoring. In this process, the process information quantity is reduced to 7 or 3 entries per
group.
With a further parameter, sensor voltage monitoring can be reconfigured so that not one input per group is
responsible for monitoring, but the last input of an I/O module for the entire automation unit. In this process,
select the desired I/O module.
NOTE
i In the case of a mixture of 1 ms and 10 ms acquisition modules, the sensor voltage monitoring must be
configured at an acquisition module with an accuracy of 1 ms.

DC8-037-2, Edition 11.2020
9.1 Telecontrol
Refer to the manual entitled SICAM RTUs Common Functions for Periphery Elements according to IEC
60870-5-101/104, Single-Point Indications section and Double-Point Indications section, in each case in the
Sensor Voltage Monitoring (Power Monitoring) paragraph for more information.
count pulse acquisition

A suitable digital input module must have been installed for the acquisition of meter pulses and the DI signals
to be used must have been assigned.
Sensor Voltage Monitoring
You can activate sensor voltage monitoring for digital inputs using the MSP monitoring parameter in each
case. Monitoring is carried out in groups:
Group 0:
IOM x – IN D00 to IN D07
Group 1:
IOM 1 – IN D10 to IN D13 (for DI-810x)
IOM x – IN D10 to IN D17 (for DI-610x, DI-811x)
The last input of a group (IN D07 and IN D13 or IN D17) must have the secured sensor voltage wired to it for
sensor voltage monitoring. In this process, the process information quantity is reduced to 7 or 3 entries per
group.
With a further parameter, sensor voltage monitoring can be reconfigured so that not one input per group is
responsible for monitoring, but the last input of an I/O module for the entire automation unit. In this process,
the desired I/O module is selected.
NOTE
i In the case of a mixture of 1 ms and 10 ms acquisition modules, the sensor voltage monitoring must be
configured at an acquisition module with an accuracy of 1 ms.
60870-5-101/104, Metered Value using Meter Pulses section, in the Sensor Voltage Monitoring (Power
Monitoring) paragraph for more information.
Setting the Meter

You can set a metered value to a defined value if a telegram to set the meter has been assigned in the corre-
sponding data point (signal list).
60870-5-101/104, Metered Values using Meter Pulses section, Setting the Meter paragraph and Counter
Interrogation paragraph for more detailed information.
Buffered Meter Pulse Acquisition

Buffered meter pulse acquisition enables acquiring meter pulses even if the target device has been de-ener-
gized. For this purpose a TE-6430 module must be installed and the DI signals to be used must have been
configured.
Current/voltage acquisition
A suitable analog input module must have been installed for the acquisition of currents and voltages and the
AI signals to be used must have been assigned.
60870-5-101/104, Currents section and Voltages section for functional details and settings.

DC8-037-2, Edition 11.2020
9.1 Telecontrol
NOTE
i A mixed wiring of current and voltage is not permitted when using the AI-6300, AI-6307, AI-6308, AI-8320
modules.
Modules AI-8510 with CM-8820 and AI-8511 are available to directly acquire currents, voltages and the
frequency.
60870-5-101/104, Measurement in Three-Phase Systems – I/O Module section for functional details and
settings.
NOTE
i If the Trans_X_100% parameter is set to 100 V/√3 with AI-8510, the Trans_Y_100% parameter must only
have a value from 1 to 36 V.
The Trans_Y_100% parameter must only be set to 240 V if the Trans_X_100% parameter has been set to
240 V
temperature acquisition
A suitable analog input module must have been installed for the acquisition of temperatures and the AI signals
to be used must have been assigned.
Connecting Resistance Thermometers

Resistance thermometers can be connected in 2, 3, or 4-phase technology. A calibration process is required for
2-phase technology. If a calibration process has not been carried out, the target device enters a calibration
error in diagnostics.
60870-5-101/104, Temperatures section, Acquisition paragraph for instructions on the calibration process.
Direct Measurement
During the HW pin assignment for the analog input module, you can choose between Temperature and
Resistance (Value Selection parameter).
During resistance acquisition, the preprocessing functions on the module (adaptation, gradient monitoring)
are deactivated to meet the process requirements regarding the reaction time (for example, to record trans-
former stages). If required, preprocessing functions must be emulated in the Open-/closed-loop control func-
tion.
NOTE
i The direct measurement is supported for the AI-6310 module from revision "-A".
The distinction between temperature acquisition and resistance acquisition is carried out in groups per value.
Do not calibrate parameters for temperature acquisition for both values of a group to activate direct measure-
ment.
Group 0:
IOM x – IN V0 and IOM x – IN V1
Group 1:
IOM x – IN V2 and IOM x – IN V3

DC8-037-2, Edition 11.2020
9.1 Telecontrol
If temperature acquisition and resistance acquisition is calibrated for a group, the acquisition is carried out
with all preprocessing steps (calculation of average value and transient suppression).
During temperature acquisition (for example, Pt20) using a resistance acquisition the calculation of the
average value and transient monitoring must be emulated in the open-/closed-loop function.
Standard Command Output

A suitable digital output module must have been installed for the standard command output (OC) and the DO
signals to be used must have been assigned.
General settings:
• Pulse duration monitoring

The command output time defines how long the actuator is actuated. The command output time interval
can be set for each data point with parameter Output_t .
• Monitoring feedback
Feedback monitoring is intended to limit the command output to the output time required by the
process. Feedback monitoring can be switched on per data point using the FB_MON_t parameter.
• Process for command transmission according to IEC 60870-5-101/104

The procedure for “direct command ”is set by the Selection_execution_t = 0 parameter.
The procedure for “Select and execute command” is set by the Selection_execution_t > 0 param-
eter. The configured value states within which time after the selection command the execution
command must be received.
60870-5-101/104, Pulse Commands section, Functions Independent of the System Element Hardware
paragraph for more detailed information about command output.

This function coordinates messages and pulse commands that are acquired or output on SICAM TM I/O
modules. Refer to the manual entitled SICAM RTUs Common Functions for Periphery Elements according to IEC
60870-5-101/104, Assignment of Feedback to Pulse Command paragraph for detailed information.
• Settable Assignment
The assignment of a message (DI signal) to a pulse command (DO signal) can be set using the 5-digit
feedback address (FB_Image_CASDU1, FB_Image_CASDU2, FB_Image_IOA1, FB_Image_IOA2,
FB_Image_IOA3 parameters). Assignment is not carried out if the parameters are set to 255 as the
value (default setting); in this case the target device uses the fixed assignment.
• Predefined Assignment
If the installed sequence of I/O modules is suitable for this purpose, the message is automatically
assigned to a command. In any other case, no assignments are made.

DC8-037-2, Edition 11.2020
9.1 Telecontrol
I/O Master Module with USIO80 Firmware
Table 9-5 Assignment of Feedback to Pulse Command – USIO80
Type Predefined Assignment

Single-point indication to single command EM IOM x – IN D00 ... Command IOM y – OUT D00
(1-pole): EM IOM x – IN D01 ... Command IOM y – OUT D01
DI-610x with DO-6200 :
EM IOM x – IN D07 ... Command IOM y – OUT D07
:
DI-610x with DO-6212 (2 DO-6212 with 1 :
DI-610x possible) EM IOM x – IN D07 ... Command IOM y – OUT D07
EM IOM x – IN D10 ... Command IOM z – OUT D00
:
Single-point indication to single command EM IOM x – IN D00 ... Command IOM y – CA00
(1-pole): EM IOM x – IN D01 ... Command IOM y – CA01
EM IOM x – IN D07 ... Command IOM y – CA07
EM IOM x – IN D10 ... Command IOM y – CB00
::
(1.5-pole): EM IOM x – IN D01 ... Command IOM y – OUT D01
DI-610x with DO-6212 (2 DO-6212 with 1 :
:
Single-point indication to single command EM IOM x – IN D00 ... Command IOM y – CA00
(1.5-pole): EM IOM x – IN D01 ... Command IOM y – CA01
EM IOM x – IN D07 ... Command IOM y – CA07
:

DC8-037-2, Edition 11.2020
9.1 Telecontrol

Single-point indication to single command EM IOM x – IN D00 ... Command IOM y – OUT D00/D01
(2-pole): EM IOM x – IN D02 ... Command IOM y – OUT D02/D03
DI-610x with DO-6212 (2 DO-6212 with 1 EM IOM x – IN D04 ... Command IOM y – OUT D04/D05
DI-610x possible) EM IOM x – IN D06 ... Command IOM y – OUT D06/D07
EM IOM x – IN D10 ... Command IOM z – OUT D00/D01
Single-point indication to single command EM IOM x – IN D00 ... Command IOM y – CA00/CB00
(2-pole): EM IOM x – IN D01 ... Command IOM y – CA01/CB01
EM IOM x – IN D07 ... Command IOM y – CA07/CB07
Double-point indication to double DM IOM x – IN D00/D01 ... Command IOM y – OUT D00/D01
command (1-pole): DM IOM x – IN D02/D03 ... Command IOM y – OUT D02/D03
DI-610x with DO-6200 DM IOM x – IN D04/D05 ... Command IOM y – OUT D04/D05
DM IOM x – IN D06/D07 ... Command IOM y – OUT D06/D07
DI-610x with DO-6212 (2 DO-6212 with 1 DM IOM x – IN D04/D05 ... Command IOM y – OUT D04/D05
DI-610x possible) DM IOM x – IN D06/D07 ... Command IOM y – OUT D06/D07
DM IOM x – IN D10/D11 ... Command IOM z – OUT D00/D01
Double-point indication to double DM IOM x – IN D00/D01 ... Command IOM y – CA00/CA01
command (1-pole): DM IOM x – IN D02/D03 ... Command IOM y – CA02/CA03
DI-610x with DO-6230 DM IOM x – IN D04/D05 ... Command IOM y – CA04/CA05
DM IOM x – IN D06/D07 ... Command IOM y – CA06/CA07
DM IOM x – IN D10/D11 ... Command IOM y – OUT CB00/CB01
DM IOM x – IN D12/D13 ... Command IOM y – CB02/CB03
command (1.5-pole): DM IOM x – IN D02/D03 ... Command IOM y – OUT D02/D03
DI-610x with DO-6212 (2 DO-6212 with 1 DM IOM x – IN D04/D05 ... Command IOM y – OUT D04/D05
DI-610x possible) DM IOM x – IN D10/D11 ... Command IOM z – OUT D00/D01

DC8-037-2, Edition 11.2020
9.1 Telecontrol

Double-point indication to double DM IOM x – IN D00/D01 … Command IOM y – CA00/CA01
command (1.5-pole): DM IOM x – IN D02/D03 ... Command IOM y – CA02/CA03
DI-610x with DO-6230 DM IOM x – IN D04/D05 ... Command IOM y – CA04/CA05
DM IOM x – IN D06/D07 ... Command IOM y – CA06/CA07
DM IOM x – IN D10/D11 ... Command IOM y – OUT CB00/CB01
Double-point indication to double DM IOM x – IN D00/D01 ... Command IOM y – OUT D00..D03
command (2-pole): DM IOM x – IN D04/D05 ... Command IOM y – OUT D04..D07
DI-610x with DO-6212 (2 DO-6212 with 1 DM IOM x – IN D10/D11 ... Command IOM z – OUT D00..D03
DI-610x possible) DM IOM x – IN D14/D15 ... Command IOM z – OUT D04..D07
Double-point indication to double DM IOM x – IN D00/D01 ... Command IOM y – CA00..CB01
command (2-pole): DM IOM x – IN D02/D03 ... Command IOM y – CA02..CB03
DI-610x with DO-6230 DM IOM x – IN D04/D05 ... Command IOM y – CA04..CB05
DM IOM x – IN D06/D07 ... Command IOM y – CA06..CB07
x = 0...7, y = x + 1, z = x + 2
NOTE
i The DO-62xx module must be installed directly after the DI-610x module in each case.
I/O Master Module with USIO81 Firmware
Table 9-6 Assignment of Feedback to Pulse Command – USIO81

DI-810x with DO-820x :
DI-811x with DO-821x (2 DO-8212 with 1 :
:
DI-810x with DO-820x :

DC8-037-2, Edition 11.2020
9.1 Telecontrol

DI-811x with DO-821x (2 DO-821x with 1 :
:
DI-810x with DO-820x EM IOM x – IN D04 ... Command IOM y – OUT D04/D05
EM IOM x – IN D06 ... Command IOM y – OUT D06/D07
DI-811x with DO-821x (2 DO-821x with 1 EM IOM x – IN D04 ... Command IOM y – OUT D04/D05
DI-811x possible) EM IOM x – IN D06 ... Command IOM y – OUT D06/D07
DI-810x with DO-820x DM IOM x – IN D04/D05 ... Command IOM y – OUT D04/D05
DI-811x with DO-821x (2 DO-821x with 1 DM IOM x – IN D04/D05 ... Command IOM y – OUT D04/D05
DI-811x possible) DM IOM x – IN D06/D07 ... Command IOM y – OUT D06/D07
DI-810x with DO-820x DM IOM x – IN D04/D05 ... Command IOM y – OUT D04/D05
DI-811x with DO-821x (2 DO-821x with 1 DM IOM x – IN D04/D05 ... Command IOM y – OUT D04/D05
DI-811x possible) DM IOM x – IN D10/D11 ... Command IOM z – OUT D00/D01
DI-810x with DO-820x
DI-811x with DO-821x (2 DO-821x with 1 DM IOM x – IN D10/D11 ... Command IOM z – OUT D00..D03
DI-811x possible) DM IOM x – IN D14/D15 ... Command IOM z – OUT D04..D07

DC8-037-2, Edition 11.2020
9.1 Telecontrol
x = 0...7, y = x + 1, z = x + 2
NOTE
i The DO-82xx module must be installed directly after the DI-81xx module in each case.
Checked Command Output

The corresponding digital output modules must have been installed and the DO signals to be used must have
been assigned to output checked commands.
Parameters are set at the command output relay module only.
60870-5-101/104, Pulse Commands section, Functions Dependent on the System Element Hardware
paragraph for more detailed information about checked command output.
Required I/O modules:
• 1 command output base module; either of the following

– DO-6220 – Command output with internal checks IC1
– DO-6221 – Command output with resistance check RC1
• 1 to 5 DO-6230 command output relay modules, either of the following

– 8 relay outputs for 16 pulse commands for 1 or 1.5-pole wiring
– 8 pulse commands for 2-pole wiring
NOTE
i Mixed wiring (1, 1.5, and 2-pole) at a DO-6230 module is not permitted. Use additional DO-6230 modules
for different wiring.
Indication output
A suitable digital output module must have been installed for the message output and the DO signals to be
used must have been assigned.
Use the Fail_Resp parameter to define the message output response in the event of master module failure.
60870-5-101/104, Indication Output section, Terminate or Maintain in the Event of Failure paragraph.
Current/Voltage Output
A suitable analog output module must have been installed for the output of currents and voltages and the AO
signals to be used must have been assigned.
Use the Fail_Resp parameter to define the setpoint output response in the event of master module failure.
60870-5-101/104, Setpoints via Currents and Voltages section, Substitute Value or Maintain in the Event
of Failure paragraph.
9.1.11.6 Importing and Exporting a Signal List

Import and export a signal list that has already been created in the Home | Signals list.

DC8-037-2, Edition 11.2020
9.1 Telecontrol
Exporting a Signal List

Proceed as follows to export your signal list:
• Click the triangle on the right-hand side to open the working area for creating signals
[sc_signals_definition_work_area, 1, en_US]
Figure 9-71 Working Area to Create Signals

The signal list is now generated as a csv file. A download dialog subsequently opens.
[sc_signal_list_export_success, 1, en_US]
Figure 9-72 Dialog to export the Signal List
• Click Start Download to save the file locally
• After having saved, click the button
The saving process depends on the web browser and may thus vary. Follow the instructions of your web
browser. Maintain the csv file type.
NOTE
i Do not quit the menu during the generation process. Browsing to a different website may cause undefined
states.
The signal list can be opened and modified as a csv file only.
• Save your changes in the signal list and save the list as a csv file

DC8-037-2, Edition 11.2020
9.1 Telecontrol
Importing a Signal List

Proceed as follows to import your signal list:
• Click the triangle on the right-hand side to open the working area for creating signals
[sc_signal_list_import, 1, en_US]
Figure 9-73 Dialog to import the Signal List
Click the button to cancel the process
• Click Select File to open the selection dialog
• Select the source directory and source file (the file type must be csv)

The target device starts the import process. The duration of the import depends on the number of signals
and the communication connection used.
The file is checked for validity. If the data is valid, it is written to the target device's SD card. In any other
case an error message is output.
The following dialog appears after having successfully imported:
[sc_signal_list_import_success, 1, en_US]
Figure 9-74 Import Successful Dialog
Further steps: Assigning (master, I/O master, I/Os), Transferring
9.1.12 Using CP-8000/CP-802x as SICAM PAS I/O
The devices CP 8000/CP 802x can be used as non-licensed SICAM PAS substations. The differentiation between
normal operation and operation as SICAM PAS I/O is done via a parameter.
With operation as SICAM PAS I/O, the IEC 60870 5 104 protocol element is defined as a SICAM PAS I/O inter-
face upon startup. All stations that are connected with this protocol element are switched to SICAM PAS I/O
mode. A connection with a normally operated station on the same protocol element is not possible.

DC8-037-2, Edition 11.2020
9.1 Telecontrol
Prerequisite for the operation as SICAM PAS I/O is an equipped IEC 60870 5 104 protocol element (in the
following example PRE0 is used).
Set in the directory SICAM A8000 CP-80xx | Master module | Communication | PRE0 the parameter
Project specific settings to YES.
Now appears the directory SICAM A8000 CP-80xx | Master module | Communication | PRE0 | Project
specific settings. Here you can set the parameter SICAM PAS IO Mode to YES.
[sc_settings_pas_io, 1, en_US]
Figure 9-75 Operation as SICAM PAS I/O
For the operation as SICAM PAS I/O the following parameters are relevant:
• SICAM A8000 CP-80xx | Master module | AU common settings

– Plant
– Device name
• SICAM A8000 CP-80xx | Master module | AU common settings | Common address of ASDU (CASDU)
– CASDU1 (must be set equally for all data points)
– CASDU2 (must be set equally for all data points)
• SICAM A8000 CP-80xx | Master module | Network settings | IP adress

– Own IP address X1/X4
• SICAM A8000 CP-80xx | Master module | PRE0 | Network connection | LAN | IEC 104 parameter
– Timeout connection setup t0
– Timeout transmit t1
– Timeout transmit acknowledge t2
– Timeout connection check t3
– Max. no. of APDUs until acknowledgement (k)
– number of APDUs until acknowledgement (w)
• SICAM A8000 CP-80xx | Master module | PRE0 | Connection definition

– Since the IEC 60870 5 104 parameters in SICAM PAS can only be configured once for all connection,
the following parameters must be adjusted equally in all connection definition:

DC8-037-2, Edition 11.2020
9.1 Telecontrol
Parameter Value
Stat. no. <internal station number>
IP address <SICAM PAS>
Controlling/Controlled Controlled
Redundancy None
Stop behaviour Save
Failure Notify
Clear ring buffer No
Data throughput limit in receive direction 0
Data throughput limit in send direction 0
Signals in the function diagram

Existing modules deliver signals. If the CASDU is invalid, it will be replaced by the CASDU parameterized on the
Master Module.
Signals via I/O Modules

If available, each signal is described by its signal name, otherwise by its IEC 60870 5 104 address.
The I/O modules deliver all signals assigned to software data points depending on a hardware pin.
9.1.12.1 Synchronization of the I/O Configuration in SICAM PAS

The configuration of the I/Os can be imported in SICAM PAS, for instance via a system configurator. Thereto
the configuration can be downloaded as XML file via a menu item in SICAM WEB. You will find further details
in section 9.3.5 Downloading SICAM PAS IO Configurations.
9.1.13 Test Functions
• Home | I/O Modules menu

The test functions are intended for visualization and to intentionally change process signals when using I/O
modules.
The test page supports the following functions:
• Showing signal assignments for a selected I/O module

– Showing corresponding, up-to-date process values (signal inputs and outputs)
• Changing process values (signal outputs only)
NOTE
i Test functions are supported for hardware data points only (spontaneous input and output signals). Signals
assigned to a software data point or a data point that can merely be forwarded periodically are not
supported.
NOTE
i With a fast connection, the directory tree is shown within 3 seconds after having selected the test page for
the first time in the session. The loading time may be longer in the case of a slow connection (GPRS). The
same also applies to the first time an I/O module is selected.

DC8-037-2, Edition 11.2020
9.1 Telecontrol
[sc_test_start_page, 1, en_US]
Figure 9-76 Test Start Page
Directory Tree
The test page features a directory tree with installed modules on the left-hand side.
Exclusively I/O modules can be selected for the test functions.
Sidebar
Click the sidebar to the right of the directory tree to enlarge the display area.
Click the sidebar on the far right to open the control area to change process values (the control area is closed
if the test page is opened for the first time in a session).
9.1.13.1 Supported Signal Types
Processing type Type identification

Signal inputs
DI_SI Single-point information (TI 30)
DI_DI Double-point information (TI 31)
DI_CV Counter value (TI 37)
DI_CV_Sub Counter value (TI 37)
AI_I Measured value normalized (TI 34)
Measured value scaled (TI 35)
Measured value short floating point (TI 36)
AI_U Measured value normalized (TI 34)
AI_T Measured value normalized (TI 34)
T_AI_I (CTVT) Measured value normalized (TI 34)
T_AI_U (CTVT) Measured value normalized (TI 34)
Signal outputs
DO_SI Single-point information (TI 30)
DO_SX Single-point information (TI 30)
Single command (TI 45)

DC8-037-2, Edition 11.2020
9.1 Telecontrol
Processing type Type identification

DO_DX Single command (TI 45)
Double command (TI 46)
DO_SC_1POL Single command (TI 45)
DO_SC_1.5POL Single command (TI 45)
DO_SC_2POL Single command (TI 45)
DO_DC_1POL Single command (TI 45)
Tap positioning command (TI 47)
DO_DC_1.5POL Single command (TI 45)
DO_DC_2POL Single command (TI 45)
AO_I Measured value normed (TI 34)
Setpoint normed (TI 48)
Setpoint scaled (TI 49)
Setpoint short floating point (TI 50)
AO_U Measured value normed (TI 34)
Setpoint normed (TI 48)
Setpoint scaled (TI 49)
Setpoint short floating point (TI 50)
9.1.13.2 Display Process Values

If you select an I/O Module for the process display, SICAM WEB performs the following steps:
• Load signal assignments for the selected I/O Module from the target device
• Load actual process values and the according states from the target device
NOTE
i If you modify the signal assignments for an I/O Module, these changes are not immediately visible in the
test page. After changing a signal assignment you save the settings, after that a startup of the target device
is required. Only then the data in the test page is loaded again from the device when selecting the corre-
sponding I/O Module.
When selecting an I/O Module, a table is displayed in the status area right beside the directory tree. Each row
of the table is a signal assignment of the related I/O Module. The displayed values can be read only.
The table contains the following columns:
• Checkbox (only for signal output)
• DATAPOINT
Datapoint name and Hardware pins on the I/O Module

DC8-037-2, Edition 11.2020
9.1 Telecontrol
• VALUE
Actual process value
• SINCE
Time tag of the last change of state
• SIGNAL
Name70 and IEC 60870-5-101/104 address
• TI
Type identification
You can change the column width with exception of the fixed columns. The column width is maintained
during the session, even if another menu is selected. Only if you select another I/O Module, the column width
will be reset.
Example: Digital input – single-point information
[sc_test_di_si, 1, en_US]
Figure 9-77 Digital Input – Single-Point Information
Example: Digital input – double-point information, counter value
[sc_test_di_di_cv, 1, en_US]
Figure 9-78 Digital Input – Double-Point Information, Counter Value
Update Counter Value

Counter values (TI 37) are not transmitted by the I/O Master Module upon each change, but by means of a
corresponding counter interrogation. With that, the displayed process value can be also updated.
If a counter value is assigned on the selected DI module, then a button appears below the status area.
70 empty, if engineered with an older SICAM WEB version or with the SICAM TOOLBOX II

DC8-037-2, Edition 11.2020
9.1 Telecontrol
• In order to initiate the counter interrogation, click on the button
[sc_test_di_ci_freeze, 1, en_US]
Figure 9-79 Dialog Counter Interrogation
• Select in the dialog the parameterized counter group (or all groups)
• Select the desired action:

– Example: “Freeze and transmit”, if you want to update the status display
– Example: “Freeze with reset and transmit”, if you want to set the value to 0 and update the status
display
• After that, click on the button
• Click on the button , in order to close the dialog
The updated process value of the requested group is now displayed.
NOTE
i The counter group and action correspond to the identifiers FRZ and RQT in the message to the I/O Master
Module.
Example: Digital output – binary information state
[sc_test_do_si, 1, en_US]
Figure 9-80 Digital Output – Binary Information State

DC8-037-2, Edition 11.2020
9.1 Telecontrol
Example: Digital output – command state
[sc_test_do_dc_sc, 1, en_US]
Figure 9-81 Digital Output – Command State
Example: Analog input – measured value, floating point
[sc_test_ai_mv_float, 1, en_US]
Figure 9-82 Analog Input – Measured Value, Floating Point
Supported Type Identifications and Possible Values
Type Identification Possible value

Single-point information (TI 30) Off (0)
On (1)
Double-point information (TI 31) Intermediate (00)
Off (01)
On (10)
Error (11)
Single command (TI 45) Off (0)
On (1)
Double command (TI 46) Terminated (00)
Off (01)
On (10)
Error (11)

DC8-037-2, Edition 11.2020
9.1 Telecontrol
Type Identification Possible value

Tap position command (TI 47) Terminated (00)
Lower (01)
Higher (10)
Error (11)
Counter value (TI 37)
Measured value normalized (TI 34) -1…+1-15
Measured value scaled (TI 35) -32768…+32767 (15 Bit + sign)
Measured value short floating point (TI 36) -1,000•1015…+1,000•1015
Setpoint normalized (TI 48) -1…+1-15
Setpoint scaled (TI 49) -32768…+32767 (15 Bit + sign)
Setpoint short floating point (TI 50) -1,000•1015…+1,000•1015
The values are converted depending on the type identification (TI). Analog values are displayed as conditioned
values.
The data format of the displayed inputs corresponds to the setting of the respective data point on the I/O
Module (signal list).
9.1.13.3 Changing Process Values

You can change (force a change of) the signal output status for test purposes. It is to be observed thereby,
that the state of a simulated output can change automatically due to
• Telecontrol function settings
• running user program (state change through logic operation)
• Communication (status change in received telegram)

It is not possible to set new process values for signal inputs.
! DANGER
Changing the signal output status of a running plant may cause personal injury or damage to the machine.
² Make sure that the units within the control section of the command output and the downstream units
in the process chain are protected and persons within the area have been warned.
• Select a DO module or an AO module

Signal outputs assigned to the selected I/O module are shown in a table in the status area.

DC8-037-2, Edition 11.2020
9.1 Telecontrol
• Click the bar to the right of the status area to open the control area on the right-hand side
[sc_test_do_control_area, 1, en_US]
Figure 9-83 Opening the Control Area for DO or AO

The control area remains inactive for as long as no signal has been selected.
You can select one or several signal outputs of the same type to change their status in one go. A notice
appears if you select signal outputs with different type identifications.
Exception for commands: As a result of the 1-of-n interlocking you can always only change 1 signal output at
the same time.
NOTE
i Errors the target device identifies when controlling outputs (for example, with internal interlocking, user
parameters, etc.) are entered in the diagnostics (History menu).
Proceed as follows to change a process value:

Example: Double command output
• Highlight the corresponding DO module in the directory tree
• Click the bar to the left of the status area if you would like to enlarge it
• Highlight the row with the desired data point
[sc_test_do_dc_force, 1, en_US]
Figure 9-84 Changing Process Values (double command)

Control Area:
• Select a “New Value”

The data format corresponds to the setting of the data point at the I/O module (signal list)

DC8-037-2, Edition 11.2020
9.1 Telecontrol
• Select the “Command qualifier” option

Select Undefined to apply the settings of the corresponding data point at the I/O module (Output_t
for single commands, Output_t_0 and Output_t_1 for double command) for the duration of the
command output.
Select Short Output Time or Long Output Time to apply the corresponding values of the AU
General Parameters for the duration of the command output.
Select Persistent Command to output a persistent command (for DO_EX and DO_DX processing type
only)
• Enter the “Originator address” (control location)

This value defines the control location for the corresponding command (0 to 255)
• Select the “Select prior to Execution” option

Select Yes and the button to activate the selection command. Once again click the button within
the set time ( Select_Execute_t) to activate the execution command. Select No and the button
to directly activate the execution command.
The new process value is transferred to the target device and shown in the VALUE column.
60870-5-101/104, Pulse Commands sections, Functions Independent of the System Element Hardware
paragraph, Select and Execute Command, Setting Control Location, Command Output Time paragraphs
for more detailed information.
Example: Normalized setpoint adjusting command
• Highlight the corresponding AO module in the directory tree
[sc_test_ao_sv_48, 1, en_US]
Figure 9-85 Change the Process Value (Setpoint Adjusting Command)

Control Area:

The data format corresponds to the setting of the data point at the I/O module (signal list)
• Select the “Select prior to Execution” option

Select Yes and the button to activate the selection command. Once again click the button within
the set time ( Select_Execute_t) to activate the execution command.
Select No and the button to directly activate the execution command.
60870-5-101/104, Setpoints via Currents and Voltages section, Select and Execute Command paragraph
for more information.

DC8-037-2, Edition 11.2020
9.1 Telecontrol
Example: Single-point indication output
• Highlight the corresponding DO module in the directory tree
[sc_test_do_si_force, 1, en_US]
Figure 9-86 Changing the Process Value (Single-point Indication)

Control Area:
Type identifications and Possible Values

The following type identifications and attributes are supported to control a new process value:
Type identification New value Selection Command quali- Origi-
before fier nator
execution address
Single point indication (TI 30) Off (0)
On (1)
Single command (TI 45) Off (0)
On (1)
Double command (TI 46) Off (01) No Without defini-
On (10) Yes tion
Long output time
Short output 0 to 255
time
Persistent
command
Regulating Step Command (TI 47) Lower (01)
Higher (10)
Normalized measured value (TI 34) -1 to +1-15
Scaled measured value (TI 35) -32768 to +32767
Short floating-point number measured -1,000•1015 to
value (TI 36) +1,000•1015
Normalized setpoint adjusting -1 to +1-15
command (TI 48)

DC8-037-2, Edition 11.2020
9.1 Telecontrol
Type identification New value Selection Command quali- Origi-

before fier nator
execution address
Scaled setpoint adjusting command (TI -32768 to +32767 No
49) Yes
Short floating-point number setpoint -1,000•1015 to
adjusting command (TI 50) +1,000•1015
9.1.14 Logging
• Home | Alarms & Events menu

In operation, the system diagnosis and the status change process will log messages occurring in the target
device.
9.1.14.1 Show Event List

Select the Events submenu to show the event list. It is displayed as a table. The table has read only rights.
[sc_event_list, 1, en_US]
Figure 9-87 Event List
Events are recorded chronologically upon a change of state in an event buffer. The events are distinguished in
2 classes:
• Diagnosis events (notifications from the diagnosis function)
• See Configurable Logging and Displaying of Signal States, Page 410 for process events (states of signals
that are marked as event)
When selecting the event list, the most current records (up to 50) are loaded. If more than 50 records are in
the event-log buffer, the next 50 records will be loaded when scrolling to the bottom. The number of loaded
records and the total number are displayed above the table.
The table is sorted chronologically descending (latest event first, oldest event at last), the time tagging has a
resolution of 1 ms. If a new event occurs, this automatically prepended at the first place of the table. The older
events are moved down.
The event buffer contains up to 4096 records and is managed as ring buffer. This means, if the event buffer
has been fully written, the respective oldest record is overwritten by the most current. The event buffer is
stored non-volatile.

DC8-037-2, Edition 11.2020
9.1 Telecontrol
Stop Function
Click the button to stop the display of new events. If new events occur, then they are recorded furthermore
in the event buffer, but not displayed in the table.
Depending on the state the button changes its design:
• Event display stopped and no new event occurred:
• Event display stopped and new event occurred:

By means of clicking the green button the new events are displayed in the table.
Click the general button to reload event list. With activated halt function, this is thereby not canceled.
Table Structure
Column value Meaning / Note

Class Diagnostics Diagnosis event
Process Process event
Name <Signal Name> At max. 99 characters, only if planned with SICAM WEB
(applies to process events)
104 address <IEC 60870-5-101/104 Configured CASDU1-CASDU2, IOA1-IOA2-IOA3 (applies to
Address> process events)
TI <Number> Type identification (30, 31, 45, 46) (applies to process
events)
Process text <Error Class> Internal diagnostics class (applies to diagnostics events)
<Status Name> At max. 13 characters (applies to process events)
value Coming Defined status text (applies to diagnostics events)
Going
<Status Text On> Freely configurable status text (applies to process events)
<Status Text Off>
<Status Text
Disturbed Position>
<Status Text Inter-
mediate Position>
Quality NT At failure of I/O Module
IV Invalid value (applies to process events)
Time Tag YYYY-MM-DD, Date and time
Thh:mm:ss:ms+hh:mm
NOTE
i When selecting another menu within the session (for example, settings, signals), the content of the table
remains, but the polling for new events is stopped. If the event page is reopened again, all events since
leaving the event page are automatically loaded.
If during the leaving of the event page a ring buffer overflow occurred, only the last 4096 events can be
loaded.

DC8-037-2, Edition 11.2020
9.1 Telecontrol
Export Event List

With the export function you can save the events which are recorded in the ring buffer in a file on your PC.
The target device saves the records in a file.
[sc_alarms_events_export_info, 1, en_US]
Figure 9-88 Exporting Log Entries Dialog
• Click to cancel the process
• Click the button to start the export

You can download the file (csv format) after the export. A dialog with the Start Download link opens.
[sc_alarms_events_export_success, 1, en_US]
Figure 9-89 Start Download Dialog
• Click with the right mouse button on the link

A dialog for the selection of the saving path is opened. The default file name can be changed, if needed.
Follow the instructions of your web browser.
• Click to cancel the process.

DC8-037-2, Edition 11.2020
9.1 Telecontrol
9.1.14.2 Show Alarm List

Select the Alarms submenu to open the alarm list display. It is displayed as a table. The table has read only
rights.
[sc_alarm_list, 1, en_US]
Figure 9-90 Alarm List
Alarms are recorded chronologically upon a change of state in an event buffer. The alarms are distinguished in
2 classes:
• Diagnosis alarms (notifications from the diagnosis function)
• See Configurable Logging and Displaying of Signal States, Page 410 for process alarms (states of signals
that are marked as alarm)
When selecting the alarm list, all the present alarms are loaded, this means, the table contains only current
states. The Outgoing and Off states are not displayed in the table and the corresponding row is then deleted
from the table.
The table is sorted chronologically descending (latest alarm first, oldest alarm at last). If a new alarm occurs,
this is automatically prepended at the first place of the table. The older alarms are moved down.
Stop Function
Click the button to stop the display of new alarms. If new alarms occur, then they are recorded furthermore
in the alarms buffer, but not displayed in the table.
Depending on the state the button changes its design:
• Alarm indicator stopped and no new alarm occurred:
• Alarm indicator stopped and new alarm occurred:

By means of clicking the green button the current alarms are displayed in the table.
Click the general button to reload alarm list. With activated halt function, this is thereby not canceled.

DC8-037-2, Edition 11.2020
9.1 Telecontrol
Table Structure
Parameter Output Meaning / Note

Class Diagnostics Diagnosis alarm
Process Process alarm
Name <Signal Name> At max. 99 characters, only if planned with SICAM WEB
(applies to process alarms)
104 address <IEC 60870-5-101/104 Configured CASDU1-CASDU2, IOA1-IOA2-IOA3 (applies to
Address> process alarms)
TI <Number> Type identification (30, 31, 45, 46) (applies to process
alarms)
Process text <Error Class> Internal diagnostics class (applies to diagnostics alarms)
<Status Name> At max. 13 characters (applies to process alarms)
value Coming Defined status text (applies to diagnostics alarms)
<Status Text On> Freely configurable status text (applies to process alarms)
<Status Text
Disturbed Position>
<Status Text Inter-
mediate Position>
Quality NT At failure of I/O Module
IV Invalid value (applies to process alarms)
NOTE
i When selecting another menu within the session (for example, settings, signals), the content of the table
remains, but the polling for new alarms is stopped. If the alarm page is reopened again, all current alarms
are automatically loaded.
Export Alarm List
Click the button at the bottom of the alarm page to export the alarms to a file. With the export function
you can save all current alarms in a file on your PC.
[sc_alarms_events_export_info, 1, en_US]
Figure 9-91 Exporting Log Entries Dialog

DC8-037-2, Edition 11.2020
9.1 Telecontrol

[sc_alarms_events_export_success, 1, en_US]
Figure 9-92 Start Download Dialog

• Click to cancel the process.

DC8-037-2, Edition 11.2020
9.2 Automation
9.2 Automation
For the accomplishment of freely definable open-/closed-loop control tasks you can create optionally an appli-
cation program as instruction list (IL).
Task Meaning
Create instruction list Edit the application program
Import program code Transfer instruction list from PC to the target device or copy offline on
the SD card
Export program code Transfer instruction list from target device nach PC
Cold start Initialize instruction list and reset all variables
Warm start Initialize instruction list and reset all volatile variables
Halt Halt cyclic program processing
Continue Continue cyclic program processing
Cycle step Execute one program cycle
Diagnosis Statistics information (cycle time and memory usage)
Test functions • Status of inputs/outputs
• Simulation of inputs
You find further details in the manual SICAM RTUs Common Functions System and Basic System Elements,
chapter Automation, section Restricted Open-/Closed-Loop Control Function.
Exceptional thereto please consider the following:
NOTE
i The signals from the periphery are distributed based on the settings in the Topology (data flow direction,
data flow routing). Therefore, a system variable for the data flow routing must not be used in the instruc-
tion list.
9.2.1 Creating an Instruction List
The creation of an instruction list is only possible independently from the target device.
For the programming is an ASCII-Editor (for instance Microsoft Notepad) required.
Example
PLC_RESET:
LD 10
ST PLC_CYCLETIME (*cycle time in ms*)
PLC_INIT:
LD MR_DINT_MINUTES (*load power-fail safe value*)
ST M_DINT_MINUTESOLD (*freeze in a flag as old value*)
PLC_START:
(*Operating hours counter*)

LD PLC_SYSTIME.SEC (*fetch second value of the system time*)
ST M_DINT_SEC (*and store in variable*)
LD M_DINT_SEC (*current second*)

DC8-037-2, Edition 11.2020
9.2 Automation
EQ 0
ST CTU_COUNTER.CU (*HIGH always at the second 0 - required edge detection
is*)
(*implemented within the counter*)
CAL CTU_COUNTER (*increments the counter*)
LD CTU_COUNTER.CV (*load current counter score*)
ST ADD.IN0 (*store at input 0 for ADD function*)
LD M_DINT_MINUTESOLD (*load old value*)
CAL ADD (*call ADD function*)
ST MR_DINT_MINUTES (*store sum of operating minutes in a retaining flag,
after startup*)
(*the old value will be added to the current counter
score*)
ST DIV.IN0 (*store at input 0 for DIV function*)
LD 60 (*load constant for 60 minutes*)
CAL DIV (*call DIV function*)
ST M_DINT_HOURS (*sum of operating hours = minutes divided by 60*)
The instruction list must be stored as file type .plc.

For loading the program code into the target device please follow the instruction in section Import Application
Program, Page 494.
You find the general specification of the programming language (IL) in the manual SICAM RTUs Common
Functions System and Basic System Elemen, chapter Automation, section Restricted Open-/Closed-Loop
Control Function, Application Program, Instruction List.
9.2.1.1 Structure of the Instruction List

The instruction list consists of 3 parts (in the following sequence):
• Startup (PLC_RESET)
The startup part is run through once after a startup. Here all variables can be initialized, that are required
directly after startup and before the current initial image.
• Initialization (PLC_INIT)
The initialization part is run through once after a startup. Here all variables can be initialized, that are
required directly after the current initial image and before the execution of the cycle part.
• Cycle (PLC_START)
The cycle part is run through cyclically (CP 8000/CP 802x provides 1 task). The cycle time is definable by
means of a system variable.
You will find some selected program examples in appendix B Examples of Instruction Lists (IL).
9.2.1.2 Syntax for Instructions
General
Each instruction command must be in one line. Each line must be concluded with a paragraph break, line
break or both (done automatically by the text editor).
An instruction command consists of the command (operation) and an operand.
Example:
LD M_BOOL_TEST (*Operation: LD, Operand: M_BOOL_TEST*)
Each operation produces a calculated value (result). The following operation can calculate further with this
result.

DC8-037-2, Edition 11.2020
9.2 Automation
Addressing I/O Variables

The format of an I/O variable must correspond to the format of the corresponding periphery input/output (I/O).
The command or setpoint is assigned to an I/O variable with an ST operation and the address of the operand.
The status or actual value is read out from an I/O variable with an LD operation and the address of the
operand.
The attribute of the I/O variable must be separated by a dot. An I/O variable without attribute is not permitted.
Examples for the simple syntax:
I_030_001_000_000_TEST.VALUE O_031_005_001_000.OFF
Examples for advanced syntax:
E_045_001_001_001_002_003_TEST.VALUE E_045_001_001_001_002_003.VALUE
NOTE
i If the same IOA is used on the input and output side, the freely definable name must be different.
IOA = 0.0.0 is not permitted; this is not supported by numerous third-party systems.
Special characters are not permitted.
I/O Master Module Data Points

I/O Master Module data points for use in the statement list have been listed in the SICAM TOOLBOX II Online
Help, Parameter Documentation and Diagnostics Information section, 1703 ACP and 1703 Ax (IEC) | Firm-
wares | USIO81 paragraph (USIO80 for SICAM TM I/O modules) in the corresponding category.
Addressing Flags
A flag is assigned with an ST operation and the address of the operand. The status or value of a flag is read out
with an LD operation and the address of the operand.
Select the numerical format as per the format of the value you would like to save.
Example:
LD I_030_002_000_000.VALUE ST M_BOOL_FLAG00
NOTE
i All flags not highlighted as non-volatile are initialized with 0 during system startup.
Accessing Functions
Functions merely have temporary variables and for this reason, all required access parameters must be set
upon each access. Unused access parameters do not influence the result when running the function.
Example:
If an addition (ADD) of 3 values is performed, then the inputs IN0, IN1, IN2 are used. The remaining inputs are
automatically set to the value 0.
The access parameter description must always start with IN0 and be in ascending order without gaps.
The access parameters must be transferred by a combination of LD and ST.
The name of the access parameter results from the name of the function and the name of the operator sepa-
rated by a dot.
Example:
LD 9 (*Load the value 9 to the battery*) ST SQRT.IN0 (*Save at input for root
extraction*) CAL SQRT (*Access the function*) ST ADD.IN0 (*Root extraction
result at input 0*) (*Save from ADD*) LD 17 (*Load the value 17 to the

DC8-037-2, Edition 11.2020
9.2 Automation
battery*) ST ADD.IN1 (*Save at the next ADD input*) CAL ADD (*Access the ADD
function*) ST M_DINT_RESULT (*Save the result on a flag*)
The results of the respective functions are written in the accumulator. With the example the value is also
stored on the flag M_DINT_ERGEBNIS.
After the call of a function (CAL) all inputs of the respective function are set to the default values again.
Example:
LD M_DINT_COMPARISON (*Load flag*) ST EQ.IN0 (*Save at input 0*) LD 3 (*Load to
value 3*) ST EQ.IN1 (*And save at next input*) CAL EQ (*Open the function; if
the two*) ST O_030_008_000_000.VALUE (*Values are identical, the function
output is 1*)
If two values are compared, the output is set if 3 is written to the M_DINT_VERGLEICH flag (writing to the flag
is not included here).
NOTE
i When wiring inputs of the following functions with "Constant values", use the type-checked CAL access:
ADD, SUB, MUL, DIV, GT, GE, EQ, NE, LE, LT (with the corresponding type variations).
All binary functions (AND, XOR, etc.) are automatically BOOL and for this reason, must not be assigned a
CAL.
When creating a statement list BOOL must be wired as a constant with 0 and 1 at the listed functions,
numeric constant of value 0 and 1 with 00 or 01, as the runtime currently does not support a + leading to
distinction (but supports a leading 0).
Accessing Function Blocks

Function blocks do not have any temporary variables. Each new (derived) function block occupies a new
memory slot in the RAM.
The corresponding first result of the function block is in the battery. If the function block has more than one
result, you can access it like with the transfer of access parameters.
Example:
LD 1 ST CTU_TEST.CU ST CTU_TEST.R LD 5 ST CTU_TEST.PV CAL CTU_TEST LD
CTU_TEST.CV (*Access to 2nd Result*)
9.2.1.3 Instruction Comments

Comments in the application program can be set at any arbitrary place and must be included between
brackets and stars. The documentation can also extend over several lines.
Example:
LD 15 (*load constant 15*)
ST M_DINT_CONSTANT (*store in flag*)
The following characters may be used:
• Numbers 0...9
• Letters A...Z, a...z
• Special characters ´` ! " $ % & / ( ) = ? [ ] { } \ @ # ' + * ~ < > | , ; . : - _
9.2.1.4 Settings in the Application Program

With help of system variables the following parameters can be set for the program execution:
• Cycle time
• Spontaneous program execution

DC8-037-2, Edition 11.2020
9.2 Automation
Setting the Cycle Time

The cycle time determines the time interval for the execution of the application program. The shorter the set
interval is the smaller must be the application program, otherwise a timeout happens. A cycle time of for
instance 2 ms is only possible for a very small application program.
The cycle time can be specified in the IL with the variable PLC_CYCLETIME:
• In the program part PLC_RESET

Time-scale is set one time with a startup.
• In the program part PLC_START

Time-scale is set during running operation and can be changed by means of the application program.
Example:
PLC_RESET:
LD 20
ST PLC_CYCLETIME (*set cycle time 20 ms*)
If the cycle time is set to the value 0, no cyclic program execution takes place.
Under certain circumstances the cycle time can be changed independently by the system:
• If no cycle time is set, it is set to 100 ms (default)
• Extended due to timeout
• Retriggering due to spontaneous program execution
Affecting the Processing Time

The processing time is the duration of a complete program run. It is primarily determined by the size of the
application program (number of operations).
NOTE
i Consider that the processing time of the application program may be inconstant.
The processing time can be extended due to:
• Number of communication connections (to further automation units, control system)
• Number of used I/O Modules
• Conditional program calls
• Diagnosis and error handling
• Test- and commissioning functions such as status and simulation of inputs/outputs
• Saving the application program (download)
• Change of parameters online
The processing time of the application program is displayed on the user interface (online) under PLC | Diag-
nosis.

DC8-037-2, Edition 11.2020
9.2 Automation
Timeout
The processing time must not be greater than the cycle time. If the maximum processing time successively
exceeds 50% of the set cycle time five times, then the cycle time is increased by 50% independently by the
system. Simultaneously an error information is set.
Spontaneous Program Execution

For faster reaction times, the application program can be executed spontaneous (event-controlled). This must
be defined in the startup part of the IL (PLC_RESET).
Possible events are:
• Status change of a data point from the periphery
• Status change of a data point from the communication
The spontaneous program execution is enabled in the IL by setting the variable PLC_SINGLE to 1 (single run).
Example:
LD 1 (*load Constante 1*)
ST PLC_SINGLE (*set single run*)
With a spontaneous program execution the entire application program is processed one time. If an event
occurs, the spontaneous program execution is first started after the current program execution has completed
(the application program cannot interrupt itself). The reaction time can therefore be delayed accordingly.
If several events occur at the same time or one after the other just when the application program is running,
then the states are temporarily stored in a ring and processed chronologically with the next spontaneous
program execution. The same is also valid if a data point changes its state several times (transient storage).
Example: Event occurs during a cyclic program execution (S1).
Event occurs during a pause (S2).
[dw_plc_timing, 1, en_US]
Figure 9-93 IL Time Response
At the end of each spontaneous pass the cyclic pass is retriggered around the set cycle time. In this case no
exceeding of the cycle time is signaled.
As long as the events occur in a time-scale that is smaller than the cycle time, only spontaneous program
passes take place. If the cycle time is set to 0 and the spontaneous program execution to 1, then only sponta-
neous program passes take place.

DC8-037-2, Edition 11.2020
9.2 Automation
You find further details in the manual SICAM RTUs Common Functions System and Basic System Elements,
chapter Automation, section Restricted Open-/Closed-Loop Control Function, Internal Signal Processing.
9.2.1.5 System Information

The following system variables (VAR_GLOBAL) can be read out and evaluated in the application program.
Table 9-7 System variables in the application program
Variable name Meaning Format

PLC_CYCLETIME_OVERFLOW Cycle time exceeded BOOL
PLC_CYCLETIME Cycle time DINT
PLC_SINGLE Single run BOOL
PLC_PROCESSINGCOUNTER Number of program runs DINT
PLC_PROCESSINGTIME Processing time DINT
PLC_SYSTIME.MS System time millisecond DINT
PLC_SYSTIME.SEC System time second DINT
PLC_SYSTIME.MIN System time minute DINT
PLC_SYSTIME.IVT System time IV bit BOOL
PLC_SYSTIME.H System time hour DINT
PLC_SYSTIME.DST System time daylight saving BOOL
PLC_SYSTIME.DAY System time day DINT
PLC_SYSTIME.WEEKDAY System time weekday DINT
PLC_SYSTIME.MONTH System time month DINT
PLC_SYSTIME.YEAR System time year DINT
PLC_SYSTIME.TIME_DATE System time complete (7 bytes) TIME_DATE
PLC_SYSERROR_001 Sum error internal BOOL
PLC_SYSERROR_002 Sum error external BOOL
PLC_SYSERROR_003 Sum error communication BOOL
PLC_SYSERROR_004 Sum error test BOOL
PLC_SYSERROR_005 Sum error warning BOOL
PLC_SYSERROR_006 Sum error board failure BOOL
PLC_SYSERROR_007 Sum error failure BOOL
PLC_SYSERROR_008 Sum error startup BOOL
PLC_SYSERROR_009 M-CPU fault BOOL
PLC_SYSERROR_010 Periphery fault BOOL
PLC_SYSERROR_011 Protocol 0 fault BOOL
PLC_SYSERROR_014 Protocol 0 communication fault BOOL
PLC_SYSERROR_017 Periphery failure BOOL
PLC_SYSERROR_018 Protocol 0 failure BOOL
PLC_SYSERROR_021 Protocol 0 communication failure BOOL

DC8-037-2, Edition 11.2020
9.2 Automation
Variable name Meaning Format

Example:
PLC_START:
LD PLC_SYSERROR_005 (*sum error warning if bit = "1"*)
ST M_BOOL_ERROR005 (*store in a flag*)
You find the description of the system variables in the manual SICAM RTUs Common Functions System and
Basic System Elements , chapter Automation, section Restricted Open-/Closed-Loop Control Function | Vari-
ables | System Variables.
9.2.1.6 Command Processing According to IEC 60870-5-101/104

Generally, commands are only passed on to the control with the cause of transmission ACT or DEACT. If the
command response is also to be processed, this can be enabled with a special parameter in the AU-common
settings (refer to Application Program, Page 384). For this, the cause of transmission in the attribute COT
must be evaluated in the application program.
If a command (Activation, ACT) is generated by the control and output on a I/O Master Module, then the
messages for command acknowledgement (ACTCON) and command termination (ACTTERM) are generated
with the corresponding output address of the control.
If an ACT remains in the control (target = control, no periphery), then an ACTCON, ACTTERM that is to be
possibly simulated can be generated in one cycle pass. For this the cause of transmission for the command
must be set to 0 and the spontaneous bit to 1. Then one ACTCON and one ACTTERM respectively will be trans-
mitted.
Example:
LD 0
ST O_045_001_001_001.COT
LD 1
ST O_045_001_001_001.S
If this function is not used, the ACTCON and ACTTERM can also be generated individually (for this at least two
cycle passes are required).
NOTE
i The corresponding type identification can be generated by means of utilization of the command "with/
without time" (for instance TI 45/TI 58).
Single Command and Double Command

Single commands (TI 45) can be generated by the IL only with the states
0 (OFF) only with COT = 7, 10 (CON, TERM) and S = 1
1 (ON)
Double commands (TI 46) can be generated by the IL only with the states
01 (OFF)
10 (ON)

DC8-037-2, Edition 11.2020
9.2 Automation
Other states will not generate a command output.

You find the details for the processing of commands in the manual SICAM RTUs Common Functions System
and Basic System Elements, chapter Automation, section Treatment for Commands to the Open-/Closed-
Loop Control Function according to IEC 60870-5-101/104.
9.2.1.7 Generation of Integrated Totals

There are two possibilities of integrated total generation in the control:
• Spontaneous transmission with change

Automatically if the input address is unequal to the output address of the controller
• Behavior according to parameter setting of the digital inputs (remote control)

Automatically if the input address is equal to the output address of the controller
• Menu Home | Logic
For commissioning and test of the application program the following functions are available:
• General functions
– Import application program
– Export application program
– Syntax check
• Test functions
– Statistic information
– Cold restart
– Warm restart
– Status of variables
– Forcing signal inputs

DC8-037-2, Edition 11.2020
9.2 Automation
9.2.2.1 Common Functions

When selecting the logic page, the instruction list (IL) currently loaded on the target device is shown. If an
instruction list has not yet been loaded into the target device, the display on the logic page remains empty.
[sc_logic_not_loaded, 1, en_US]
Figure 9-94 Display for Empty Instruction List
Import Application Program

The corresponding instruction list must have been loaded on the target device to run the open-/closed-loop
control function.
This is how to upload an instruction list to the target device:
• Click the button if an instruction list is available in ASCII format.
[sc_logic_import_select, 1, en_US]
Figure 9-95 Dialog Select Instruction List

You have the option to abort the procedure.
• Click "Select a file" to open the selection dialog
• Select the source directory and source file (the file type must be plc)
• Click the button to start the import
The target device starts the loading procedure. The duration of the loading procedure depends on the
program size and the communication connection used.

DC8-037-2, Edition 11.2020
9.2 Automation
NOTE
i Do not quit the menu during the loading procedure. The selection of another web page may cause unde-
fined states.
The data is checked during loading. An error indication appears if the data is invalid.
The following dialog appears if the data is valid:
[sc_logic_import_success, 1, en_US]
Figure 9-96 Dialog Instruction List Upload Successful
After successful upload, the content of the instruction list is displayed on the logic page and an automatic
syntax check is performed (see Syntax Check, Page 497).
[sc_logic_display, 1, en_US]
Figure 9-97 Display for Loaded Instruction List
The syntax check result is shown in the bottom toolbar. The status log lists additional information in the event
of an error.
• Click the general button if you want to read the status log.
Note the conventions in the section 9.2.1 Creating an Instruction List when correcting errors.
The changed data must be saved as otherwise the instruction list is discarded upon quitting the session.

DC8-037-2, Edition 11.2020
9.2 Automation
This is how to activate an instruction list in the target device:
• Click the button if you want to save the instruction list.
The program file is saved on the SD card. A restart of the target device is required after saving (see
9.3.1 Restart Device) to activate the program code.
During startup the newly loaded program code is compiled, checked, and written to the program memory.
Any already available program code is overwritten in the process.
• If no error is present, the program is processed after startup.
• If an error is present, the program is stopped and an error indication is recorded in the diagnosis and in
the history.
NOTE
i For transmission via Ethernet, it is recommended to deactivate the settings for HTTP 1.1 of your PC (Control
Panel, Internet Options, tab Advanced). In any other case there is the possibility that CP-8000/CP-802x is
unable to interpret the transmitted ASCII file.
Load Application Programm Offline

For instance as part of the initialization of a target device (refer to 11.6.4.1 Initialization of the Firmware) you
can directly copy an instruction list saved as an ASCII file from your PC to the SD card.
• Insert the SD card into a read/write device installed on the engineering PC.
• Copy the program file to the root directory of the SD card.
• Change the file name to plc_src.plc.
• Then insert the SD card into the target device.
The target device performs a startup and checks the program code in this process:
• If no error is present, the program code is compiled and written to the program memory. Any existing
program code is overwritten in this process. The new program code is run after startup.
• If an error is present, an error indication is recorded in the history including details. If available, the
existing program code is maintained and executed again after startup.
Export Application Program

You can download the instruction list loaded to the target device for archiving purposes or to edit it.
This is how to download an instruction list from the target device:
• Click the button if you want to create a backup of the instruction list loaded to the target device.
[sc_logic_export_info, 1, en_US]
Figure 9-98 Dialog Export Instruction List

DC8-037-2, Edition 11.2020
9.2 Automation
• Right-click Start download to open the dialog to save the data.
• Select the storage location and (if required) change the file name; keep the plc file type.
• Click the button to close the dialog.
The storage procedure depends on the web browser and may thus vary. Follow the instructions of your web
browser.
The content of the displayed instruction list is written to the selected file. The destination is a text file
containing the program code in ASCII format. You can read or change the file with a text editor.
Syntax Check
This function can be performed manually at any time, for instance after having quit and restarted a session in
addition to the automatic syntax check during the instruction list import.
Click the button to check the instruction list for errors (if required). The following criteria are checked:
• Syntax, logic, addressing
• Limits for program size, cycle time, variables
The status log lists additional information in the event of an error:
[sc_logic_syntax_error, 1, en_US]
Figure 9-99 Feedback after Syntax Check

Diagnosis and test of the application program provide read functions that display information from the open-/
closed-loop control function and write functions that influence the open-/closed-loop control function.
• Menu Home | Logic (Category “Test”)
Read Functions
Available for the user names administrator and guest (can be used from administrator and more than one
guest at the same time).
• Display statistic information of the application program
• Display current value of selected variables (signal status)
Write Functions
Only available for user name administrator. When logging on to the target device as guest, the control
elements for the writing operations are not visible in the logic test page.
• Change status of the application program

– Cold start
– Warm start
– Halt cyclic processing
– Continue cyclic processing
– Run 1 cycle
• Change value of selected variable (forcing signal)

DC8-037-2, Edition 11.2020
9.2 Automation
Statistic Information
In the logic test page the program statistic information and the currently loaded IL are displayed. If no or an
empty IL is loaded (no application program is running in the target device), the logic test page shows all the
values set to 0 and the IL display is empty.
[sc_logic_test_statistics, 1, en_US]
Figure 9-100 Statistic Information of the Application Program
Display
Table 9-8 Statistic information in the instruction list
Information Meaning
State Running
Running Normal program execution
Halt
Program execution halted (the processing can be halted either manually or by the system
due to an error; more detailed information in the history)
Cycle time <Set value>
Increasement of the adjusted cycle time by the system possible (see section Setting the
Cycle Time, Page 489)
<Actual value>
Processing time of the application program at the moment of the refreshment of the diag-
nosis menu
<Maximal value>
Maximum reached program processing time since the last startup
Memory code <Number>/ 131072 bytes
Used program memory on the SD card of maximum number of bytes
Var <Number> / 4096 bytes
Used variables of maximum number of bytes
Test mode off /on

DC8-037-2, Edition 11.2020
9.2 Automation
Display Current Value of Selected Variables

At the right side of the logic test page you can enter up to 10 variable names from the IL displayed at the left
side of the page. You can also copy a variable name from the IL and paste it into an input field.
[sc_logic_test_page, 1, en_US]
Figure 9-101 Logic Test Page with Example
After entering a valid variable name into the input field, the current value of this variable is displayed right
beside the input field.
The update is performed in a grid of 1 s.
Example: Binary value
If you select a binary variable, T is displayed for TRUE and F for FALSE:
[sc_logic_test_ctu_counter, 1, en_US]
Figure 9-102 Example for Binary Variable
Example: Analog value

If you select a numeric variable, the number is displayed as follows:
[sc_logic_test_m_dint, 1, en_US]
Figure 9-103 Example for Analog Variable

DC8-037-2, Edition 11.2020
9.2 Automation
Example: Various variables

The value display happens for each selected variable in the designated data format.
[sc_logic_test_mixed_var, 1, en_US]
Figure 9-104 Example for Various Variables
Example: Invalid variable

With invalid variables, like with empty fields, the value "unknown" is displayed:
[sc_logic_test_variable_unknown, 1, en_US]
Figure 9-105 Example for Invalid Variable
Valid are only those variables that are used in the current running IL.
Change Status of the Application Program

For each possible action, an according button is placed in the logic test page. After each action, the current
status of the application program is requested from the target device, and the buttons are enabled or disabled
accordingly.
In normal mode of the application program, the state is displayed as follows:
Figure 9-106 Statistic Information (Application Program Running)

DC8-037-2, Edition 11.2020
9.2 Automation
The control buttons are enabled/blocked as follows:
[sc_logic_test_page, 1, en_US]
Figure 9-107 Example for Logic Test Page
With execution of one of the functions, the test mode is switched on:
• Halt of the application program (immediately)
• Cold start of the application program (per request)
• Warm start of the application program (per request)
Halt program
Precondition: The application program is running in normal mode.
When clicking on the button , the cyclic processing of the application program is halted and the test mode
is automatically switched on.
This is displayed as follows:
[sc_logic_test_halted_status, 1, en_US]
Figure 9-108 Statistic Information (Halt Application Program)
The buttons are enabled/blocked as follows:
[sc_logic_test_halted_buttons, 1, en_US]
Figure 9-109 Buttons in State Halted
Run Single Program Cycle

Precondition: The application program is halted.

DC8-037-2, Edition 11.2020
9.2 Automation
When clicking the button (Cycle step), the application program executes only one single cycle and is halted
again.
The status display of the application program and the buttons do not change.
With this function you can trace for instance the status change of variables for each program cycle, or change
the value of a signal input for exactly 1 program cycle.
Continue Program Processing

Precondition: The application program is halted.
When clicking the button , the application program is processed cyclically again and the test mode remains
switched on.
This status changes as follows:
[sc_logic_test_continued_status, 1, en_US]
Figure 9-110 Statistic Information (Application Programm Running and Test Mode On)
The buttons are enabled/blocked as follows:
[sc_logic_test_continued_buttons, 1, en_US]
Figure 9-111 Buttons in State Continue
Switch off Test Mode

Precondition: The application program is in the test mode.
If you click on the button , the test mode will be terminated.
The status changes as follows:
Figure 9-112 Statistic Information (Application Program Running and Test Mode Off)
Cold Start
When pressing the button (Cold start), the following dialog is opened:
[sc_logic_test_cold_start, 1, en_US]
Figure 9-113 Dialog Execute Cold Start
• Click on the button in order to perform a cold start

DC8-037-2, Edition 11.2020
9.2 Automation
The test mode is switched on and the values of all variables are initialized with 0 and the application program
is restarted. The program parts PLC_RESET and PLC_INIT are processed once and if the program has been
previously
• in the “State: running”, the program part PLC_START is processed cyclically again
• in the “State: halt”, the program processing is halted
Warm Start
When pressing the button (Warm start), the following dialog is opened:
[sc_logic_test_warm_start, 1, en_US]
Figure 9-114 Dialog Execute Warm Start
• Click on the button in order to perform a warm restart
The test mode is switched on and the values of the volatile variables are initialized with 0 and the application
program is restarted. The program parts PLC_RESET and PLC_INIT are processed once and if the program has
been previously
• in the “State: running”, the program part PLC_START is processed cyclically again
• in the “State: halt”, the program processing is halted
Change Value of Selected Variable

The changing of values is only possible for signal inputs. Signal outputs and local variables are overwritten by
the application program every cycle, therefore a permanent forcing for those values is not provided.
It is not possible to force more than one signal input at the same time. If you want to change more than one
signal input, this can only be done one after another.
When forcing a signal input, the according signal is automatically separated from the input process image and
therefore this signal is not overwritten each cycle. Additionally the application program is switched to the test
mode automatically.
The test mode is maintained even if you switch to other pages within the session with the target device. If the
communication with SICAM WEB is disconnected, the test mode is automatically terminated by the target
device after 30 seconds.
You can terminate the test mode manually by pressing the button :
• All values for the signal inputs are taken from the process image again
• The manually changed values during test mode are then overwritten by the respective process value
again

DC8-037-2, Edition 11.2020
9.2 Automation
! DANGER
The value change of a signal input can – dependent on the programmed logic – have an impact on the
status of signal outputs.
² The change of state of signal outputs with the plant running can lead to damage to persons and
machines. Ensure that aggregates in the control area of the command output as well as those subse-
quent aggregates in the process chain are protected and that persons in the vicinity are warned.
This is how to overwrite the value of a variable:

Below the IL you can enter a variable name from the IL into the input field VARIABLE. You can also copy a
variable name from the IL and paste it into an input field.
If the variable name is invalid or empty, the type is displayed as “unknown” and the button is disabled.
[sc_logic_force_unknown, 1, en_US]
Figure 9-115 Example for Invalid Variable Name
If the variable name is valid, the type and the actual value of the variable is displayed:
[sc_logic_force_valid, 1, en_US]
Figure 9-116 Example for Valid Variable Name

DC8-037-2, Edition 11.2020
9.2 Automation
You can now enter a value into the field NEW VALUE. The permitted value range is displayed right beside the
button .
Example: Binary value
If you select a signal input with data type BOOL, the value range T, F is displayed.
When you enter a valid value, for instance T, the button is enabled.
[sc_logic_force_bool, 1, en_US]
Figure 9-117 Example for Change Binary Value of a Variable
• Click on the button
The new value is written on the signal in the IL and is displayed right beside the variable type.
The test mode is automatically switched on and the button is enabled.
[sc_logic_force_bool_done, 1, en_US]
Figure 9-118 Example for Changed Binary Value of a Variable
If you click on the button , the test mode is terminated.

Example: Analog value
When selecting a signal with datatype DINT, the value range -32768 to 32767 is displayed.
If you enter a valid value, for instance 10, the button is activated.

DC8-037-2, Edition 11.2020
9.2 Automation
[sc_logic_force_dint, 1, en_US]
Figure 9-119 Example for Change Analog Value of a Variable
• Click on the button
The new value is written on the signal in the IL and is displayed right beside the variable type.
The test mode is automatically switched on and the button is enabled.
[sc_logic_force_dint_done, 1, en_US]
Figure 9-120 Example for Changed Analog Value of a Variable
When entering a signal with data type REAL, you must enter the new value with a decimal point, otherwise a
corresponding notice is displayed. The display looks then as follows:
[sc_logic_force_real_info, 1, en_US]
Figure 9-121 Example for Missing Decical Point

DC8-037-2, Edition 11.2020
9.2 Automation
When entering the new value correctly and pressing the button , the new value is written on the signal and
is displayed right beside the data type:
[sc_logic_force_real_done, 1, en_US]
Figure 9-122 Example for Changed Variable Value of Type REAL
If you click on the button , the test mode will be terminated.

DC8-037-2, Edition 11.2020
9.3 Administrative Functions
For the performance of the following functions you get via the button :
• Restart device
• Backup device settings
• Restore device settings
• Upload ICD, IID file
• Download SICAM PAS IO configuration
• Download process data archive
• Update firmware
• Update SICAM WEB
• Install language package
NOTE
i These functions are only allowed for the user type Administrator.
9.3.1 Restart Device
This function allows you to restart the target device at any arbitrary moment (for instance after change of
several parameters that require a restart).
Select thereto the submenu Restart device.
The following dialog will appear:
[sc_restart_manually, 1, en_US]
• Confirm the procedure with
If settings still have not been saved, the following dialog will appear:
[sc_restart_unsaved_changes, 1, en_US]
Figure 9-124 Dialog Unsaved Changes

DC8-037-2, Edition 11.2020
You have the possibility to abort the procedure in order to save the changes.
• If you want to perform the restart, click on the button → unsaved changes will be rejected thereby!
The following information will appear during a restart:
[sc_restart_progress, 1, en_US]
Figure 9-125 Dialog Restart in Progress
At the bottom of the dialog the current startup time is displayed. Depending on the size of the engineering
data, the startup time can take up to 15 minutes.
A successful restart of the device is shown by the following dialog:
[sc_restart_success, 1, en_US]
Figure 9-126 Dialog Restart Successful
• Click in order to quit the session with the target device
• Click the suitable hyperlink in order to return to the Logon page of the previously started target device
• If in the target device the parameter Autoconfiguration was set to YES, the IP address is set to
169.254.0.1; that remains until it is assigned anew by the set DHCP server (see 9.1.2.7 Autoconfigura-
tion)
NOTE
i A startup concernes also the automation function (if used). You find further information in section
9.2.2 Commissioning and Test.
NOTE
i With the initial commissioning, the startup may last up to 15 minutes, since at this the files on the SD card
will be unpacked and the system folders on the SD card are created.

DC8-037-2, Edition 11.2020
9.3.2 Download Device Settings
This function enables to save the entire engineering data of the target device as a backup on the engineering
PC.
The backup contains firmware codes and engineering data (parameters and – if existing – the instruction list).
Select thereto the submenu Backup device settings.
The following dialog will appear:
[sc_backup_manually, 1, en_US]
Figure 9-127 Dialog Backup Device Settings
• Confirm the procedure with
If settings still have not been saved, the following dialog will appear:
[sc_backup_unsaved_changes, 1, en_US]
Figure 9-128 Dialog Unsaved Changes
You have to abort the procedure and save the changes.

If the settings have been saved, the target device starts with the generation of the backup file. The progress is
thereby displayed by the web server. This procedure can take a few minutes.
[sc_backup_progress, 1, en_US]
Figure 9-129 Progress Display
NOTE
i During generation procedures the website must not be left. The selection of another website may lead to
the occurrence of undefined states.

DC8-037-2, Edition 11.2020
When the generation of the backup file has finished, the following dialog appears:
[sc_backup_success, 1, en_US]
Figure 9-130 Dialog Backup File Ready
• Click on Start download

The storing procedure may vary dependent on the used web browser and may take some time, depending on
the file size and transmission rate. Follow the instructions of your web browser. The file name is put together
of SICAM_CP<Type>_BACKUP_<Customer>_<Plant>_<Station>_<Hash value of file>.cmc.
• After successful generation click on in order to close the dialog
NOTE
i Users, passwords and certificates are not included in the backup.

The file saved via SICAM WEB cannot be imported into the SICAM TOOLBOX II.
9.3.3 Restoring Device Settings
This function makes it possible to open the previously saved target device settings and parameter configura-
tions (backup) and load them to the target device.
In this process, all telecontrol parameters, statement lists, and firmware codes are saved together on the SD
card in the master module.
For this purpose, select the Restore Device Settings submenu.
[sc_recover_select, 1, en_US]
Figure 9-131 Restore Device Settings Dialog
You have the option to cancel the process.
• Select the source directory and the source file (file type must be cmc, file name including path name
must not exceed 128 characters)

DC8-037-2, Edition 11.2020
The target device starts the import process. The duration of the import depends on the file size and the
communication connection used.
NOTE
i Do not quit the menu during the generating and loading processes. Browsing to a different website may
cause undefined states.
The file is then checked for integrity. For this purpose, a cryptologic hash function is computed over the file
and the result is checked with the hash value in the file name:
• If the file is valid, the data is written to the SD card of the target device and all settings in the target
device are adapted
• If the results differ, the file is deleted and no changes are made. An error message appears
The target device is automatically restarted following a successful loading process:
[sc_recover_success, 1, en_US]
Figure 9-132 Restore Device Settings Successful Dialog
• Click the button to close the dialog
9.3.3.1 Loading Device Settings Offline

For the duplication of an already existing parameterization, you can write the data also without target device
(offline) on an SD card with the program Sicam_first_startup.
Thereto a backup file created with the function “Save device settings” via SICAM WEB must exist (file type
cmc). Further you need a read/write device for SD cards connected on the engineering PC, a corresponding
driver installed on the PC (if needed), as well as a suitable SD card.
• Insert the SD card into the read/write device
• Start the program Sicam_first_startup per double-click

The Sicam_first_startup splash screen is opened, and the Sicam_first_startup symbol appears in the notifica-
tion area of the taskbar:
[sc_A8000_first_startup_splash_screen, 1, --_--]
Figure 9-133 Sicam_first_startup Splash Screen

DC8-037-2, Edition 11.2020
• Click on the splash screen in order to close it
• Click then with the right mouse button on the Sicam_first_startup symbol
[sc_A8000_first_startup_notification_area, 1, --_--]
Figure 9-134 Notification Area of the Taskbar

The context menu of Sicam_first_startup is opened:
[sc_A8000_first_startup_pop-up_menu, 1, en_US]
Figure 9-135 Sicam_first_startup Context Menu
• Change the language if needed and open the context menu again
• After that click on Write flash card from A8000 parameter file
The file selection dialog for the source is opened:
[sc_first_startup_open_file, 1, en_US]
Figure 9-136 Dialog for File Selection
• Select now the source directory and the source file of the type cmc and accept
The file selection dialog for the target is opened:
[sc_first_startup_select_flash_card, 1, en_US]
Figure 9-137 Dialog for Target Selection
• Select the target drive (read/write device) and accept

Sicam_first_startup generates the files with the format needed for the web server from the parameter file
and stores them on the SD card. The generation terminates with a notification.

DC8-037-2, Edition 11.2020
The write procedure takes a few seconds (watch the Active-LED on the read/write device, as far as present).
When the write procedure is completed, you can insert the SD card into the target device, whereupon a
startup is performed.
After the startup you can logon to the target device via SICAM WEB, for instance to adapt the parameterization
or to carry out test functions.
NOTE
i With operation in a network first a valid IP address must be assigned by means of the program
Sicam_first_startup.
9.3.4 Uploading ICD/IID Files
IEC 61850 specifies the “Substation Configuration Description Language” (SCL) as the display format to
configure substation devices. Depending on the purpose of the SCL file this has been categorized in different
file types.
CP-8000/CP-802x devices support the icd and iid file types. The corresponding files can be loaded to IEC
61850 protocol elements only.
NOTE
i The function is supported from the following firmware revision version: CPC80 V.12, ET85 V.04.
For this purpose, select the Load ICD/IID File submenu.

An error message appears if no IEC 61850 protocol element has been installed or the firmware revision
(Master Module, protocol element) does not support loading ICD/IID files:
[sc_icd_iid_upload_no_pre, 1, en_US]
Figure 9-138 Error Message Dialog

DC8-037-2, Edition 11.2020
• Click to close the dialog and check the configurations in Assembly & Protocols.
[sc_icd_iid_upload_select, 1, en_US]
Figure 9-139 Update ICD/IID File Dialog

• Select the source file (file type must be icd or iid)
• Select the target protocol element
The file is then checked for validity.
An error message appears if the data is invalid or the file size exceeds 10 MB:
[sc_icd_iid_upload_error, 1, en_US]
Figure 9-140 Error Message Dialog

DC8-037-2, Edition 11.2020
• Click to close the dialog

If the data is valid, it is written to the target device's SD card.
The following dialog appears after having successfully updated:
[sc_icd_iid_upload_success_, 1, en_US]
Figure 9-141 ICD/IID File Update Successful Dialog
• Click to confirm the process
The following dialog then appears:
[sc_fw_update_restart, 1, en_US]
Figure 9-142 Restart the Device Dialog
You have the option to cancel the target device's restart to load more data.
• Click the button to restart the device (see 9.3.1 Restart Device)
NOTE
i Do not quit the menu during the loading process. Browsing to a different website may cause undefined
states.
During system startup the file is saved on the SD card as \ETx5\5_<BSE>_<ZSE>.icd.
9.3.5 Downloading SICAM PAS IO Configurations
The data point configuration can be synchronized with a superordinate SICAM PAS device for the use of
CP-8000/CP-802x as SICAM PAS I/O.
The data point configuration can be downloaded as a file in xml format and it can be saved on the project
engineering PC. This file can subsequently be imported to the SICAM PAS.
The file features system engineering information from the master module and IEC 60870-5-104 protocol
element, as well as the signals that are used via I/O modules and in the user program.

DC8-037-2, Edition 11.2020
For this purpose, select the Download SICAM PAS Configuration submenu.
The following dialog appears:
[sc_pas_io_download_info, 1, en_US]
Figure 9-143 Download Configuration Dialog
The following dialog appears if you have not yet saved the settings:
[sc_pas_io_download_unsaved_changes, 1, en_US]
Figure 9-144 Unsaved Changes Present Dialog
You must cancel the process and save the changes.

If the settings have been saved, the target device starts generating the configuration file. The progress is
displayed by the web server. This process can take several minutes.
[sc_pas_io_download_progress, 1, en_US]
Figure 9-145 Progress Indication Window
NOTE
i Do not quit the menu during the generation processes. Browsing to a different website may cause unde-
fined states.

DC8-037-2, Edition 11.2020
The parameters used for SICAM PAS I/O are checked during the generation of the configuration file. The
following dialog appears if the parameter configuration is faulty:
[sc_pas_io_download_error, 1, en_US]
Figure 9-146 Download Canceled Dialog
You must cancel the process and correct the parameters, see Parameter Check.
The following dialog appears once the configuration file has been completed:
[sc_pas_io_download_success, 1, en_US]
Figure 9-147 Configuration File Completed Dialog
• Click Start Download

The storage process may vary depending on the web browser used and, depending on the file size and
transfer rate, may take some time. Follow the instructions of your web browser.
The file name consists of PASIO_CFG<Date>_<Time>.xml
• Click after having successfully saved to close the dialog

DC8-037-2, Edition 11.2020
Configuration example:
[sc_pas_io_download_success_file, 1, --_--]
Figure 9-148 SICAM PAS IO Configuration File
Parameter Check
The configured data points and assigned statement list elements are checked while generating the file.
The configuration file can be downloaded once the following conventions have been met:
• CASDU1 and CASDU2 of the signals correspond to the settings at the master module
• Signals that have been assigned to hardware pins of a DO with TI 45 to TI 50

– must use “Selection before Execution” in the same way
• Signals that have been assigned to hardware pins of a AO with TI 48 to TI 50

– must use “Termination” in the same way
• Signals from the user program with TI 45 to TI 50 are treated as directly executed
– If a signal is imported by the user program, all other signals from any source must be configured as
directly executed with the same type identification
• Signals from the user program with TI 48 to TI 50 are treated as terminated

– If a signal is imported by the user program, all other signals from any source must be configured as
terminated with the same type identification
In the event of an error the error information is written to the file. This is saved on the SD card in the \System
\Downloads directory.

DC8-037-2, Edition 11.2020
Remove the SD card from the target device and insert it into a card reader installed at your project engineering
PC to be able to read out the configuration file.
NOTE
i Once the SD card is reinserted into the target device, a system startup is performed.
Configuration example (with error)
[sc_pas_io_download_error_file, 1, --_--]
Figure 9-149 SICAM PAS IO Configuration File with Error
Table 9-9 Parameters for the SICAM PAS Configuration
System-engineering settings Parameter

RTU_NAME Plant name
LRU_NAME Device name
ASDU_ADDRESS CASDU2 x 256 + CASDU1
NETWORK_CONNECTION IP_ADDRESS Own IP address X1/X4
MAX_NUM_UNRECEIPTED_SEND_TELEGRAMS Maximum number of unacknowledged
APDUs (k)
MAX_NUM_UNRECEIPTED_RECEIVED_TELEGRAMS Number of APDUs up to acknowl-
edgment (w)

DC8-037-2, Edition 11.2020
System-engineering settings Parameter

TIMEOUT_T0 Timeout during establishment of
connection t0
TIMEOUT_T1 Timeout to send t1
TIMEOUT_T2 Timeout to send acknowledgment
t2
TIMEOUT_T3 Timeout for connection test t3
Table 9-10 Signals for the SICAM PAS Configuration
Process-engineering settings Signals

DIGITAL_VALUE, DIGITAL_VALUE_TYPE = SINGLE TI 30
DIGITAL_VALUE, DIGITAL_VALUE_TYPE = DOUBLE TI 31
DIGITAL_VALUE, DIGITAL_VALUE_TYPE = TRANSFORMER_TAP TI 32
SEL_BEFORE_EXE = "DIRECT" or "SELECT" TI 45 to TI 50
CMD_TERMINATION = "YES" or "NO" TI 45 to TI 50
ANALOG_VALUE, ANALOG_VALUE_TYPE = NORMALIZED TI 34
ANALOG_VALUE, ANALOG_VALUE_TYPE = SCALED TI 35
ANALOG_VALUE, ANALOG_VALUE_TYPE = FLOAT TI 36
COUNTER_VALUE TI 37
DIGITAL_CONTROL, DIGITAL_CONTROL_TYPE = SINGLE TI 45
DIGITAL_CONTROL, DIGITAL_CONTROL_TYPE = DOUBLE TI 46
OUTPUT_TIME0, OUTPUT_TIME1, OUTPUT_TIME2
ANALOG_CONTROL, ANALOG_CONTROL_TYPE = NORMALIZED TI 48
ANALOG_CONTROL, ANALOG_CONTROL_TYPE = SCALED TI 49
ANALOG_CONTROL, ANALOG_CONTROL_TYPE = FLOAT TI 50
OUTPUT_TIME0 71 TI 45, TI 46, TI 47
TELEGRAM_ADDRESS (IOA3 x 65536) +
(IOA2 x 256) + IOA1
HIERARCHICAL_NAME Signal name if available, in any other case
CASDU_<casdudecimal>_IOA_<ioadecimal>
9.3.6 Download Process Data Archive
The data saved in the process data archive can be downloaded as a file in csv format and it can be saved on
the project engineering PC. This file can then be read out as a table.
The file contains the recorded messages, measured values, and metered values that have been configured for
the recording in the process data archive (see Configurable Logging and Displaying of Signal States,
Page 410).
71 Single command: Output_t, double command: Output_t0, Output_t1

72 AU general settings | Short command output time
73 AU general settings | Long command output time

DC8-037-2, Edition 11.2020
For this purpose, select the Download Process Data Archive submenu.
[sc_proc_archive_download_info, 1, en_US]
Figure 9-150 Download Process Data Archive Dialog
If the download - possibly in another session - has already been started but not yet finished, the following
dialog appears:
[sc_proc_archive_download_started_abort, 1, en_US]
Figure 9-151 Download Canceled Dialog
You must cancel the process and await the completion of the previous download.
If the settings have been changed, the target device starts generating the archive file. The progress is
displayed by the web server. This process can take several minutes.
[sc_proc_archive_download_progress, 1, en_US]
Figure 9-152 Progress Indication Window
If the archive file can not be generated due to errors, the following dialog appears:
[sc_proc_archive_download_error, 1, en_US]
Figure 9-153 Error during Download Dialog

DC8-037-2, Edition 11.2020
One cause may be, for example, a poor communication connection or the memory usage in the target device.
Cancel the process and try again. If the error persists, check the communication connection and / or - if
possible - trigger a startup of the target device.
When the archive file has been successfully completed, the following dialog appears:
[sc_proc_archive_download_success, 1, en_US]
Figure 9-154 File Ready for Download Dialog
• Click Start Download

The storage process may vary depending on the web browser used and, depending on the file size (at max. 1
GB) and transfer rate, may take some time. Follow the instructions of your web browser. The file name
consists of PROC_ARCHIVE<Date>_<Time>.csv.
• Click to close the dialog
You can now log off from the destination system or continue working in the current session. The download
continues in the background until it has completed. The download can be aborted at any time by means of:
• Cancel function of the web browser
• Closing the web browser
Example for an Archive File
[sc_proc_archive_download_file, 1, en_US]
Figure 9-155 Example for an Archive File
9.3.7 Update Firmware
With this function, you are able to load the most recent firmwares (see 7.3 Loadable Firmwares) into the
target device.

DC8-037-2, Edition 11.2020
For this purpose, select the Update firmware submenu.
[sc_fw_update_select, 1, en_US]
Figure 9-156 Dialog Update Firmware
You have the option to abort the procedure.
• Click Select a file to open the selection dialog
• Select the source file (file type must be bin)
The target device starts the loading procedure. The duration of the loading procedure depends on the file size
and the communication connection used.
NOTE
i Do not quit the menu during the loading procedure. Browsing to a different website may cause undefined
states.
The file is then checked for validity. If the data is valid, it is written to the SD card of the target device. In any
other case an error information is displayed.
After successful update, the following dialog appears:
[sc_fw_update_success, 1, en_US]
Figure 9-157 Dialog Update Firmware Successful

DC8-037-2, Edition 11.2020
You have the option to abort the restart of the target device and update more firmware.
9.3.8 Updating SICAM WEB
This function makes it possible to use the up-to-date software for the SICAM WEB application.
For this purpose, select the Update Application Software submenu.
[sc_sweb_update_select, 1, en_US]
Figure 9-159 Updating SICAM WEB Dialog
• Select the source directory and source file (the file type must be web)
NOTE
states.
The file is then checked for validity. If the data is valid, it is written to the target device's SD card. In any other

DC8-037-2, Edition 11.2020
[sc_sweb_update_success, 1, en_US]
Figure 9-160 SICAM WEB Update Successful Dialog
You have the option to cancel the target device's restart and update more firmware.
9.3.9 Installing the Language Package
This function makes it possible to install additional languages for the graphical user interface.
For this purpose, select the Install the Language Package submenu.
[sc_lp_update_select, 1, en_US]
Figure 9-162 Installing the Language Package Dialog

DC8-037-2, Edition 11.2020
• Select the source directory and source file (the file type must be nls)
NOTE
states.
The file is then checked for validity. If the data is valid, it is written to the target device's SD card. In any other
The following dialog appears after a successful installation:
[sc_lp_update_success, 1, en_US]
Figure 9-163 Installing the Language Package Successful Dialog
You have the option to cancel the target device's restart to update more firmware.
The newly installed language is available in the list box of the login dialog.
NOTE
i No language packages have currently been defined apart from the standard languages German and
English.

DC8-037-2, Edition 11.2020
DC8-037-2, Edition 11.2020
10 Engineering via SICAM Device Manager
10.1 General Information 530

DC8-037-2, Edition 11.2020
Engineering via SICAM Device Manager
10.1 General Information
10.1 General Information

The SICAM Device Manager is the intuitive engineering software for SICAM A8000 Series.
• Clear project and device management
• Simple duplication of devices
• Online connection with the devices via SICAM WEB

You will find the instructions for this tool in document SICAM Device Manager User Manual (D51-003).

DC8-037-2, Edition 11.2020
11 Service
This chapter describes the internal checks and displays of the devices CP-8000/CP-802x, which diagnosis
options are available, what is to be considered with the exchange of the system or external modules, and how
functional updates can be loaded into the system.
11.1 Maintenance, Cleaning, and Waste Disposal 532
11.2 Environmental Protection Hints 533
11.3 Control and Display Elements 534
11.4 Checks and System Displays 558
11.5 Diagnostics 562
11.6 Maintenance of the Hardware 582
11.7 Firmware Update 586
11.8 Resetting Device to Factory Settings 589
11.9 Remote Servicing 591

DC8-037-2, Edition 11.2020
Service
11.1 Maintenance, Cleaning, and Waste Disposal
11.1 Maintenance, Cleaning, and Waste Disposal

Maintenance
The device is maintenance-free.
Provide adequate ESD protection when working on the bus or in its vicinity.
Cleaning
If required, wipe the device with a clean, dry, soft, and lint-free cotton cloth.
Cleaning agents may cause damage. Do not use cleaning agents.
Humidity or moisture may impair the components' functionality. Make sure that humidity or moisture does
not penetrate the device.
Waste Disposal
Note the local and national stipulations when disposing of the device.

DC8-037-2, Edition 11.2020
Service
11.2 Environmental Protection Hints
11.2 Environmental Protection Hints

Disposal of Old Equipment and Batteries (Applicable only for European Union and Countries with a Recycling
System)
The disposal of our products and possible recycling of their components after decommissioning has to be
carried out by an accredited recycling company, or the products/components must be taken to applicable
collection points. Such disposal activities must comply with all local laws, guidelines and environmental speci-
fications of the country in which the disposal is done. For the European Union the sustainable disposal of elec-
tronic scrap is defined in the respective regulation for "waste electrical and electronic equipment" (WEEE).
The crossed-out wheelie bin on the products, packaging and/or accompanying documents means
that used electrical and electronic products and batteries must not be mixed with normal house-
hold waste.
According to national legislation, penalties may be charged for incorrect disposal of such
waste.
By disposing of these products correctly you will help to save valuable resources and prevent any potential
negative effects on human health and the environment.
NOTE
i Our products and batteries must not be disposed of as household waste. For disposing batteries it is neces-
sary to observe the local national/international directives.
Disposal of Mobile Storage Devices (e.g. USB Sticks and Memory Cards)
When disposing of/transferring mobile storage devices, using the format or delete functions only changes the
file management information and does not completely delete the data from your mobile storage device. When
disposing of or transferring a mobile storage device, Siemens strongly recommends physically destroying it or
completely deleting data from the mobile storage device by using a commercially available computer data
erasing software.
REACH/RoHS Declaration
You can find our current REACH/RoHS declarations at:
https://www.siemens.com/global/en/home/products/energy/ecotransparency/ecotransparency-down-
loads.html
NOTE
i You can find more information about activities and programs to protect the climate at the EcoTransparency
website:
https://www.siemens.com/global/en/home/products/energy/ecotransparency.html

DC8-037-2, Edition 11.2020
Service
11.3 Control and Display Elements

The following section shows the arrangement of the operation and display elements on the front of the
respective housing and describes the states and meaning of the single elements.
NOTE
i LED displays don't guarantee zero potential connectors.
11.3.1 Master Module CP-8000
CP-8000 provides
• 3 LEDs which indicate the operating status of the module

– POK (Power Ready LED, yellow)
– RY (Ready LED, yellow)
– ER (Error LED, red)
• 8 LEDs which indicate the connection status of the communication interfaces X1 to X4 (dependent on
the configured protocol elements)
• an LCD text display
• 4 function keys
[dw_CP-8000_disp_op_elements, 1, en_US]
Figure 11-1 CP-8000 Control and Display Elements
Operating Status
Status of the POK LED Meaning

Dark • Sum error (voltage failure, power supply defective, etc.)
• Startup
Lights up Power supply without error
Status of the RY LED Meaning

Dark System or specific module not ready
Lights up System ready

DC8-037-2, Edition 11.2020
Service

Flashes regularly • Loading of parameters into the Flash PROM
• Loading of firmware into the Flash PROM
Flashes irregularly Startup
Status of the ER LED Meaning

Dark No error
Lights up • Sum error (internal error, external error, warning, module failure, system
failure; inclusive I/O Master Module)
• Startup
Connection Status
LED Status X1 Meaning

LK1 Lights up Physical connection to the Ethernet Hub
Dark • Connection not established
• Startup
PK1 Flickers Activity (TCP frame sent/received)
Dark Startup

OH2 Flickers Sending message
Lights up Connection with minimum one physical partner set up (dial-up traffic)
• Startup
RTX2 Flickers Activity on send/receive line
Dark Startup

• Startup
Dark Startup

• Startup
Dark Startup

DC8-037-2, Edition 11.2020
Service
11.3.2 Master Module CP-802x
CP-8021 provides

• 8 LEDs (yellow) which indicate the connection status of the communication interfaces X1 to X4
(dependent on the configured protocol elements)
CP-8022 provides

• 12 LEDs (yellow) which indicate the connection status of the communication interfaces X1 to X4, X6, X7
(dependent on the configured protocol elements)
Figure 11-2 CP-8021 Display Elements Figure 11-3 CP-8022 Display Elements
Operating Status

Dark System or specific module not ready
Lights up System ready
Flashes regularly • Loading of parameters into the Flash PROM
• Loading of firmware into the Flash PROM
Flashes irregularly Startup

DC8-037-2, Edition 11.2020
Service
Status of the ER LED Meaning

Dark No error
Lights up • Sum error (internal error, external error, warning, module failure, system
failure; inclusive I/O Master Module)
• Startup
Connection Status

• Startup
Dark Startup

• Startup
Dark Startup

• Startup
RTX3 Flickers Sending or receiving message
Dark Startup

• Startup
Dark Startup

74
• Startup
RTX6 Flickers Sending or receiving message
75
Dark Startup
74 only CP-8022
75 only CP-8022

DC8-037-2, Edition 11.2020
Service

LK7 Lights up Connection established
76
Flashes regularly • 0.5 s: net search, not registered, turning off
• 1 s: registered to mobile network
• 2 s: error (SIM, registration, IPsec, …)
• Startup
PK7 Flickers Data exchange with GPRS modem
77
Dark Startup
11.3.3 Power Supply Modules
PS-862x and PS-864x provide the display element RY (Ready LED, yellow) that indicates the operating state of
the module.
Figure 11-4 PS-8620 Figure 11-5 PS-8622 Figure 11-6 PS-8640 Figure 11-7 PS-8642
76 only CP-8022
77 only CP-8022

DC8-037-2, Edition 11.2020
Service
Operating state
Status of the LED Meaning

Dark • Sum error power (voltage failure, power supply defect, at least one of the
monitored voltages is smaller than the setpoint value, etc.)
• System startup
Flashes Power supply without error
• 1 s interval: PS in Bootloader (system startup)

• 0.3 s interval: Connection to CP-802x interrupted
• 0.1 s interval: Load of firmware into the Flash PROM
Lights up Module ready (power supply without error)
! CAUTION
Risk of electric shock
Failure to observe these safety instructions may lead to injury.
² The output voltage may be available in the power supply module, even though the RY LED is in unlit
status.
² The LED displays of the module cannot guarantee that the periphery connectors are de-energized!

DC8-037-2, Edition 11.2020
Service
11.3.4 SICAM A8000 I/O Modules
The SICAM A8000 I/O modules provide one RY display element (Ready LED, yellow), which indicates the oper-
ating state of the module.
[dw_SICAM_IO_disp_elements, 1, --_--]
Figure 11-8 SICAM A8000 I/O Modules
Operating State

Dark • Sum error (voltage failure, defective)
• System startup
Lights up Module ready

DC8-037-2, Edition 11.2020
Service
11.3.5 LED Module
The LED module provides:
• an RY display element (Ready LED, yellow), which indicates the operating state of the module
• 8 display elements (Ready/Error LED, bicolor) which indicate the process status of the respective SICAM
I/O modules
• 128 display elements which indicate the process status of the I/Os of the respective SICAM I/O module
[dw_CM-8830_disp_elements, 1, en_US]
Figure 11-9 CM-8830 Display Elements
LED Module Operating State

Dark Module not ready or failed
Lights up Module ready
Operating States of the SICAM I/O Modules (RY/ER LED)

The IOM LEDs (IOM 0 to 3 and IOM 4 to 7) are bicolor LEDs that indicate the operating state and the process
errors of the SICAM I/O modules in a SICAM A8000 I/O row.

DC8-037-2, Edition 11.2020
Service
Status of the I/O Meaning How to Read the LED Sequence

Module LEDs
Dark • Respective I/O module is not ready • Left to right (IOM 0 to 3)
• Respective I/O module not detected or in • Left to right (IOM 4 to 7)
error state
Lights up (yellow) • Respective I/O module is ready, monitoring
is active
• No process error
Lights up (red) • Respective I/O module monitoring is active
and
• I/O module process error indication
I/O Process Status

The LEDs (00 to 07 and 10 to 17) indicate the process status of the digital and analog inputs/outputs of the
respective SICAM I/O module.
Status of I/O Process Meaning How to Read the LED Sequence
Status LEDs
Dark Respective I/O module is not ready and/or Bottom to top (00 to 07 and 10 to
channel is inactive 17) of IOM 0 to 7
Lights up (yellow) Respective I/O module is ready, channel is
active
• The I/O process status of the DI and AI is displayed without the project engineering of the SICAM A8000
system.
• The I/O process status (of the DO and AO) and the I/O process errors (of the DI and AI) are displayed only
when the SICAM A8000 system has been engineered.
• The I/O process status for the AI-8320 and AO-8380 modules is displayed when the measured input is > 3
%. Accordingly, the LEDs do not light up when the measured input is < 3 %.
• The I/O process status of the AI-8310 module is displayed only when the measured input is between 20 Ω
and 4075 Ω.
Process-Signal Assignment for Each SICAM I/O Module Type
Type Process Signal How to Read the LED Sequence

DI-811x IN D00 to IN D07 and IN D10 to IN D17 Bottom to top (00 to 07 and 10 to
17)
DO-8212 OUT D00 to OUT D03 and OUT D04 to OUT D07 Bottom to top (00 to 03 and 04 to
07)
AI-8310 IN V0 to IN V3 Bottom to top (00 to 03)
AI-8320 IN V0 to IN V3 Bottom to top (00 to 03)
AO-8380 OUT V00 to OUT V03 Bottom to top (00 to 03)
Process-Error Visualization
Name Process Error Visualization

DI-811x Power monitoring error
AI-8320 Zero-point suppression error

DC8-037-2, Edition 11.2020
Service
The following figure explains the mapping of the I/O module pin assignment and the mapping of the LED
module displays:
[dw_cm8830-display-mappi, 1, en_US]
Figure 11-10 Mapping of the I/O Module Pin Assignment and Mapping of the LED displays
The mapping shown above is for illustration purposes only. The actual display mapping and system setup can
vary from configuration to configuration.
The following figure explains the I/O signal connection from SICAM A8000 to the LED module, compared to
SICAM WEB I/O monitoring:
[dw_cm8830-display-sweb, 1, --_--]
Figure 11-11 I/O Signal Connection from SICAM A8000 to the LED Module
The mapping shown above is for illustration purposes only. The actual display mapping and system setup may
vary from configuration to configuration.

DC8-037-2, Edition 11.2020
Service
11.3.6 LCD Display (CP-8000 only)
The LCD display comprises
• Device Information
• Configuration
• Monitoring
• Alarms
Overview of the menu structure:

1.0 2.0 3.0 4.0
Main menu Device information Configuration Monitoring Alarms
Submenu 1.1 Device 2.1 I/O Modules 3.1 Events (Alarm List)
2.1.1 IOM0 3.1.1 All Events
2.1.2 IOM1 3.1.2 DEF Events
... 3.1.3 DIA Events
2.1.8 IOM7
1.2 Language 2.2 Protocols 3.2 Alarms
2.2.1 PRE0
2.2.2 PRE1
2.2.3 PRE2
2.2.4 PRE3
1.3 Display 2.3 Version 3.3 Cockpit
1.4 Startup page 3.4 I/O Modules
3.4.1 IOM0
3.4.2 IOM1
...
3.4.8 IOM7
NOTE
i Consider the notes in section 4.3 Climatic Ambient Conditions.
11.3.6.1 Navigation
The navigation within the menus is done via the function keys F1 to F4. Their current function is shown in the
bottom row of the display.
Name Function Meaning
F1 ESC • Back to the previous menu
• Reject entry
F2 ▲ Selection up (circulating list)
+ Value +1

DC8-037-2, Edition 11.2020
Service
Name Function Meaning

F3 ▼ Selection down (circulating list)
- Value -1
F4 MENU Back to the previous menu
ENTER • Open submenu
• Open list
EDIT Edit value
OK Accept
11.3.6.2 Device Information
The menu item Device information

is devided in the submenus
• Device
• Language
• Display
• Startup page
Device
Information on the device itself can

be found in the submenu Device.
Submenu Submenu Display/settings Meaning/range

1.1 Device - Article number
Serial number
MAC address(es) 1 or 2 according to
parameter
IP address
Hardware/firmware identification

DC8-037-2, Edition 11.2020
Service
Language
In the submenu Language you can

select the language of the display.
All available languages are listed in
alphabetical order.
With the function keys ▲ and ▼ you can select a language.

Press the function key OK to activate the selected language.
1.2 Language - Deutsch
English
Language settings have no impact on
• labels of the function keys
• parameterized name and state of events (appear as they have been parameterized)
• parameterized name and state of alarms (appear as they have been parameterized)
• name and state of diagnosis events (fixed in english)
• name and state of diagnosis alarms (fixed in english)
Display
In the submenu Display you can

change the display settings (e.g.
brightness, contrast).
With the function keys ▲ and ▼ you can select a parameter.

Press the function key EDIT to edit the selected parameter.
For changing press the function key + or – and accept with OK.

DC8-037-2, Edition 11.2020
Service

1.3 Display - Contrast 1...9
Backlight level 1...3
Backlight dimmed 0...2
Time until dimmed 0...99
Invert display ☐◄►☑
Display test
Start Page
In the submenu Startup page you

can select that page which shall be
displayed after a startup.
With the function keys ▲ and ▼ you can select a page.

Press the function key OK to activate the selected page.
After the next startup of the target device the selected page is displayed.
1.4 Startup - Main menu
page I/O Modules 1
I/O Modules 2
: :
I/O Modules 8
All Events
DEF Events
DIA Events
Alarms
Cockpit 1
Cockpit 2
: :
Cockpit 32
NOTE
i If the selected page is not existing, then the superior menu will be displayed.
Example: selection of an I/O Module that is not equipped.

DC8-037-2, Edition 11.2020
Service
11.3.6.3 Configuration
The menu item Configuration is devided in the

submenus
• I/O Modules
• Protocols
• Version
I/O Modules
In the submenu I/O Modules you can select the status

display of the internal and – if used – external I/O
Modules (only with equipped I/O Master Module).
You may also view equipped I/O Modules in the Moni-
toring | I/O Modules submenu.
The image besides shows the standard submenu.
Menu with external SICAM I/O Modules (example) Menu with external SICAM TM I/O Modules (example)
IOM7: DI-811x IOM7: DI-610x
With the function keys ▲ and ▼ you can select an I/O Module.
With the function key ENTER you get to the status display of the selected I/O Module.

DC8-037-2, Edition 11.2020
Service
Status of digital outputs (example) Status of digital inputs (example)
With the function keys ▲ and ▼ you can switch directly between the I/O Modules.
Submenu Submenu Function Status Meaning
2.1 2.1.1 OUT D00…OUT D07 ● DI: activated
I/O Modules IOM0: DO-820x ○ DI: not activated
2.1.2 IN D00…IN D07 ● DO: activated
IOM1: DI-810x IN D10…IN D13 ○ DO: not activated
2.1.3 IOM2: 78 <Value> AI: input value79
<Value> AO: output value79
2.1.4 IOM3: 78
2.1.5 IOM4: 78
2.1.6 IOM5: 78
2.1.7 IOM6: 78
2.1.8 IOM7: 78
Protocols
In the submenu Protocols the status of the individual

communication connections is displayed (only with
configured protocol).
The image besides shows an example without config-
ured PRE1.
Meaning of the status symbols in the Protocols menu:
78 dependent on the respective module

79 percentage of the measuring range of the respective module

DC8-037-2, Edition 11.2020
Service
[dw_CP-8000_display_protocols_descr, 1, en_US]
Submenu Submenu Function Status Meaning

2.2 2.2.1 PRE0: <Firmware> ● (All) connection(s) established
Protocols 2.2.2 PRE1: <Firmware> ●! Not all connections estab-
lished
2.2.3 PRE2: <Firmware> ○! No connection established
○ Connection not established
2.2.4 PRE3: <Firmware> ○? No detailed information avail-
able for this protocol
X? No interface is assigned to
this protocol
Examples:
Ethernet
• Only parametrized connections are displayed.

• If there are more connections available as can be
shown on one page, these will be displayed on
the next page.
Meaning of the status symbols:
● Connection is established
○ Connection is not established
Point-to-point traffic
Meaning of the status symbols:
● Connection is established
○ Connection is not established

DC8-037-2, Edition 11.2020
Service
This information is displayed if there are no details

available for this protocol.
Version
In the submenu Version the version numbers of the

individual firmwares are displayed.
11.3.6.4 Monitoring
The menu item Monitoring is devided in the

submenus
• Events
• Alarms
• Cockpit
• I/O Modules
The submenu Events | ALL Events displays a list with max. of 4000 process and diagnosis events. Process
events are optional configurable.
The submenu Alarms displays a list with max. of 4000 process and diagnosis alarms (you may also view the
alarm list from the main menu item Alarms). Prozess alarms are optional configurable.
The submenu Cockpit displays up to 32 configurable groups with up to 255 signals each.
The submenu I/O Module displays the signal states at the inputs and outputs of the equipped I/O Modules.
The following signals can be defined by means of parameter as process event and/or process alarm (refer to
Configurable Logging and Displaying of Signal States, Page 410):

DC8-037-2, Edition 11.2020
Service
Type of signal Designation Type identifier (TI) Process event Process alarm
Single point infor- SI TI 30 ✓ ✓
mation
Single command SC TI 45 ✓
Double point infor- DI TI 31 ✓ ✓
mation
Double command DC TI 46 ✓
The following diagnosis events and diagnosis alarms (sum errors) are generated by the device and entered in
the list. These diagnosis events cannot be parameterized:
Event process text Meaning Process event Process alarm
Dia IntError Internal error ✓ ✓
Dia ExtError External error ✓ ✓
Dia ComError Communication error ✓ ✓
Dia Test Test ✓ ✓
Dia Warning Warning ✓ ✓
Dia BoardFail Board failure ✓ ✓
Dia Restart Restart ✓ ✓
Events | ALL Events
The submenu Events is devided in the submenus
• All Events
• DEF Events (process events)
• DIA Events (diagnosis events)
In the submenu All Events all process events and

diagnosis events are displayed in chronological order
(most recent entry first).
In the header you can see which entry you have
selected and the amount of all entries.
After opening the list, the most recent entry is auto-
matically selected.
You can navigate through the entire list via function keys ▼ and ▲.
In the selected entry you can see detailed information on the selected entry (date, timestamp, etc.).
Using the function key TOP, you go to the beginning of the list (and select the first entry).

DC8-037-2, Edition 11.2020
Service
The oscillating function key TOP shows that a new event is active.
• Press the oscillating function key TOP to refresh the entire list
The function key TOP will not be oscillating if you did select the first entry and a new event occurs. In this case,
however, the list will be refreshed.
3.1 Events 3.1.1 All Events Event name • Freely parameterizable text (applies for
process events)
• Always beginning with “Dia” (applies for
diagnosis events)
Status • Freely parameterizable text (applies for
process events)
• Coming, going (applies for diagnosis
events)
Quality bit Applies for process events (TI 30 and TI 31)
only:
?: not topical
!: invalid
#: blocked
$: substituted
Date Date of the selected event
Time stamp Timestamp of the selected event
Time quality bit !: invalid (optional)
Indication of daylight- S: daylight-saving time (optional)
saving time
Events | DEF Events
The submenü Events | DEF Events shows exclusively

process events in a list.
For a more detailed description of the display and navigation, refer to section Events | ALL Events, Page 552.

DC8-037-2, Edition 11.2020
Service

3.1 Events 3.1.2 DEF Event name Freely parameterizable text
Events Status Freely parameterizable text
Quality bit Valid for process-events (TI 30 and TI 31) only:
?: not topical
!: invalid
#: blocked
$: substituted
saving time
Events | DIA Events
The submenu Events | DIA Events shows exclusively

diagnosis events in a list.
For a more detailed description of the display and navigation, refer to section Events | ALL Events, Page 552.
3.1 Events 3.1.3 DIA Event name Always beginning with “Dia
Events Status coming, going
saving time

DC8-037-2, Edition 11.2020
Service
Alarms
In the submenu Alarms are displayed in chronological

order (most recent entry first).
In the header you can see which entry you have
selected and the amount of all entries.
After opening the list, the most recent entry is auto-
matically selected.
You can navigate through the entire list via function keys ▼ and ▲.
In the selected entry you can see detailed information on the selected entry (date, timestamp, etc.).
Using the function key TOP, you go to the beginning of the list (and select the first entry). The oscillating func-
tion key TOP shows that a new alarm is active.
• Press the oscillating function key TOP to refresh the entire list
The function key TOP will not be oscillating, if you did select the first entry and a new alarm occurs. In this
case, however, the list will be refreshed.
3.2 Alarms - Alarm name • Freely definable text (applies for process
alarms)
• Always beginning with “Dia” (applies for
diagnosis alarms)
Status • Freely definable text (applies for process
alarms)
• Coming (applies for diagnosis alarms)80
Cockpit
The submenu Cockpit is devided in freely definable

groups.
Under each group, the status of signals assigned to
the group can be read:
• Binary information (Process value digital)

• Measured values (Process value analog)
The groups and their assigned signals are defined via the engineering tool (SICAM WEB: refer to section
Configurable Logging and Displaying of Signal States, Page 410).
80 no historical alarms

DC8-037-2, Edition 11.2020
Service
You can navigate through the entire list via function keys ▼ und ▲.
You can open the selected group with the function key OK.
Under the opened group the respectively assigned

signals appear with the status display.
Example: binary information items
In this example, 3 binary information items are
assigned to the group positions 1, 3 and 4.
Position 2 is not assigned. (blank line).
Example: measured values

In this example, 2 measured values are assigned to
the group positions 1 and 5.
Positions 2, 3 and 4 are not assigned (blank line).

3.3 Cockpit <Group 1> Signal name Freely definable text
<Group 2> Status Freely definable text (applies for binary informa-
<Group 3> tion)
: Value Freely definable text (applies for analog infor-
<Group 32> mation)
Unit Freely definable text (applies for analog infor-
mation)
Quality bit Valid for process-events (TI 30 and TI 31) only:
?: not topical
!: invalid
#: blocked
$: substituted

DC8-037-2, Edition 11.2020
Service
I/O Modules
In the submenu I/O Modules you can select the status

display for the individual I/O Modules (only with
equipped I/O Master Module).
The image besides shows the standard submenu.
The menu structure and the display corresponds with the submenu Configuration | I/O Modules (see section
I/O Modules, Page 548).

DC8-037-2, Edition 11.2020
Service
11.4 Checks and System Displays

The single system elements carry out checks of the hardware and software. If an error is detected, this leads
• to a signaling on the LED display
• dependent of the severeness of the error possibly

– to an abort of the startup
– in operation to a shutdown of the modules or firmware
After an errorless startup of a system element further checks are carried out.
11.4.1 Checks during Startup
Table 11-1 LED display in the startup
Startup (step) RY ER Error/reaction

Power-up or reset ○ ● Start startup
○ • Module defective
• Massive error in the program memory
Check of the code memory (flash PROM) ○ ● PROM error (code)
• Module is shut down

• Startup is aborted
Check of the data memory (RAM) with ○ ● RAM error (data)
address error check
• Module is shut down
Check whether SD card is present ○ ● SD card not present
Check of the checksum of all parameter files ○ ● Checksum error on the SD card
and firmware files on the SD card
• Diagnosis information is set
Check whether all parameters on the SD card ○ ● Parameter files incomplete
are present
• Firmware is shut down
Check whether all firmware files on the SD ○ ● Firmware code incomplete
card are present
Check whether the firmware code of the ○ ● If not, load firmware code at a later time
subordinate system elements (protocol (11.7 Firmware Update)
elements, I/O Master Module) is current
Revision check of the parameters in the ○ ● If the parameters are not current, they are
parameter memory loaded from the SD card
Check parameter memory (flash-PROM) ○ ● Checksum error of the parameters
• Firmware is shut down

Initiate the startup of the subordinate system ○ ●
elements
Check for accordance of the parameterized ○ ● Configuration error
HW configuration with the mechanical config-
uration (I/O Modules)
• Wrongly configured or defective module
is not operational
• Successional modules are not opera-
tional

DC8-037-2, Edition 11.2020
Service
Startup (step) RY ER Error/reaction

Check of the configuration for pulse ○ ● Configuration error
command output
• Pulse command output is locked for all
modules
Loading the parameters to the subordinate ○ ● Too little memory on the protocol element or
system elements I/O Master Module
• Firmware on the protocol element or I/O

Master Module is shut down
Check of the parameter contents ○ ● Parameter error
Startup completed (OK) ● ○
Startup completed (error) ● ●
Table 11-2 LED display of errors (Startup aborted)
Error RY ER Note
Module defective ○ ○ Replace system/external module
PROM error (code) ○ ● Replace system/external module
RAM error (data) ○ ● Replace system/external module
Parameter files incomplete ○ ● • Read diagnosis
• Initialize automation unit
Checksum error of the parameters ○ ● • Read diagnosis
Parameter error ○ ● Read diagnosis
Table 11-3 LED display of errors (Startup continued)
Error (startup continued) RY ER Note

No SD card present ● ● • Read diagnosis
• Insert SD card
Firmware code incomplete ● ● • Read diagnosis
• Load firmware newly
Configuration error ● ● Read diagnosis
Too little memory on the protocol element or ● ● Read diagnosis
I/O Master Module
Parameter error ● ● Read diagnosis (depending on type of error)
NOTE
i “Firmware shut down” means that all functions with exception of those, which are necessary for the
communication with the engineering tool in the local operating mode, are halted. In this state all outputs
are terminated.
By means of the lighted display this state can not be identified clearly. On occurrence of this state, a diag-
nostic information is set with an error code. This state can now only be ended with a Power up or Reset.
The reset can be initiated both by the SICAM TOOLBOX II as well as with SICAM WEB.

DC8-037-2, Edition 11.2020
Service
NOTE
i “Module shut down” means that all activities of the hardware and firmware are halted. In this state all
outputs are terminated.
By means of the lighted display this state can not be identified clearly. This state can now only be ended
with a Power up or Reset. The reset can be initiated by the SICAM TOOLBOX II as well as with SICAM WEB.
11.4.2 Checks after Startup
Table 11-4 LED display in operation
Cyclic operation RY ER Error/reaction

Check of the communication connections ● ● Communication error
• Communication failure
• Communication fault
Communication connections set up (OK) ● ○
Function check of the I/O Modules over the ● ● I/O Module error
TM bus
• Periodical information for the open-/
closed-loop control function
• Diagnosis information
I/O Modules operational (OK) ● ○
Table 11-5 LED display of errors
Error RY ER Note
Communication failure ● ● • Diagnosis
• Check communication lines
• Check remote station
Communication error ● ● Diagnosis
I/O Module error ● ● • Diagnosis
• Replace system (if internal module)
• Replace I/O Module (if external module)
Table 11-6 LED display at loading of firmware
Load firmware code RY ER Error/reaction

System element is shut down and the firm- ● ●
ware code is loaded from the SD card
Initiate startup of the Master Module for new ● ●
loaded system elements (protocol element,
I/O Master Module)
Startup completed (OK) ● ○
Startup completed (error) ● ●
11.4.3 Behavior of the Process Outputs upon Startup and Failure
With failure of the supply voltage and during startup of the system all the process outputs are terminated.

DC8-037-2, Edition 11.2020
Service
After startup of the Master Module the periodical information items for the open-/closed-loop control
function are initialized with the value 0 and a status "faulty" dependent on the I/O Module.
After startup of the I/O Master Module all periodical information items from faultless inputs are written with
the current preprocessed value, and the corresponding status "faulty" is reset.
The behavior of outputs upon communication failure is dependent on the I/O Module and can be defined for
each output selectively with the parameter Fail_behav.
For binary information outputs the following behavior can be selected:
• terminate (default)
• keep
For current and voltage outputs the following behavior can be selected:
• keep (default)
• substitute value
If the substitute value is selected, in the following cases the value defined via parameter
fail_subst_value is output.
Table 11-7 Case dependent output of a substition value
Event Description Action

Power-on Return of the supply As long as no setpoint value was received, the parameter-
voltage after failure ized substitution value is calculated and transferred as
active value into the process image
Startup Startup possible via With a remote startup the value is reset to the last value,
independent of the parameterization; if a value never
• Remote command
was received, the substitution value is output
• Operation
Communication failure Substitution value is output
Master Module
Failure Master Module Substitution value is output

DC8-037-2, Edition 11.2020
Service
11.5 Diagnostics
11.5 Diagnostics
11.5.1 Distinction of the Error Types
The following listing explains the different error types and their logging.
• System errors
– Supervision of the system, communication, time synchronization by the firmware of the configured
system elements
– Logging in the online diagnosis
– Activation of the red error LED on the Master Module
• Parameterization errors (telecontrol function)

– Supervision by the engineering tool
– Specific conventions or plausibility checks
– Indication upon entry or prevention of the transfer
– Supervision online by the firmwares of the configured system elements
– Activation of the red error LED on the Master Module
If in the target device a parameterization is loaded that does not match with the mechanical present system
elements, this leads to the indication of a hardware error.
• Programming errors (open-/closed-loop control function)

– Supervision by “CAEx plus” (engineering via SICAM TOOLBOX II)
– Specific conventions or plausibility checks
– Indication upon entry or prevention of the transfer
– Supervision by the “CAEx plus” compiler (engineering via SICAM TOOLBOX II)
– Logging in the Error state viewer
– Supervision by the ASCII-Compiler during startup (engineering via SICAM WEB)
– Logging in the PLC diagnosis
– Supervision online by the firmware of the Master Module
• Operator errors
Are largely excluded due to plausibility checks or queries by the engineering tool (additional hints see
Appendix C.1 Errors with the Engineering via SICAM WEB).
NOTE
i Naturally, all operator inputs, such as for example the loading of parameters or the online testing, are
subject to the responsibility of the user.
Profound knowledge of the automation technique in general, as well as the documents mentioned in the
Preface is presumed.
Errors that are recorded in the online diagnosis are devided in diagnosis classes and contain further indications
about the possible error cause, as well as hints for the error elimination (“cause”, “remedy”).
You find the meaning of the diagnosis classes in the manual SICAM RTUs Common Functions System and Basic
System Elements, chapter System Services, section Diagnostic and Signaling.

DC8-037-2, Edition 11.2020
Service
11.5 Diagnostics
You find the error indications recorded in the online diagnosis in the SICAM TOOLBOX II Online Help, chapter
Parameter Documentation and Diagnosis Info, section Diagnosis Information, under the respective firm-
ware.
11.5.2.1 Connection Possibilities for the Diagnosis

For the access to the diagnosis data of CP 8000/CP 802x, an online connection of the engineering PC to the
target device is required. Reading access is at the same time possible locally and from the distance. Writing
access (example: startup request to the target device) is only exclusively possible.
You find the basic connection possibilities in section 7.6.1 SICAM TOOLBOX II. Following you find some appli-
cation examples.
Direct Connection
[dw_A8000_telemaintenance_toolbox_direct, 1, en_US]
Figure 11-12 SICAM TOOLBOX II - Direct Connection

DC8-037-2, Edition 11.2020
Service
11.5 Diagnostics
Connection via Ethernet
[dw_A8000_telemaintenance_toolbox_ethernet, 1, en_US]
Figure 11-13 SICAM TOOLBOX II - Connection via Ethernet

DC8-037-2, Edition 11.2020
Service
11.5 Diagnostics
Remote Connection via Further Automation Units
[dw_A8000_telemaintenance_toolbox_remote, 1, en_US]
Figure 11-14 SICAM TOOLBOX II - Remote Connection
11.5.2.2 Diagnosis Overview

CP-8000/CP-802x contains extensive diagnosis functions for monitoring the system. Since the firmware
executes the appropriate error monitoring routines automatically, no settings by the user are necessary
thereto.
[dw_A8000_toolbox_engineering_system_diag, 1, en_US]
Figure 11-15 SICAM TOOLBOX II - System Diagnosis
With the tool “Diagnostic” (TOOLBOX II | Service Programs | Diagnostic), system states and error information
items can be read, and printed out if required.
The following functions are available:
• Network overview diagnosis

The error entries of all automation units in the network are output in a report window via the menu
Network overview diagnostic (sum information).

DC8-037-2, Edition 11.2020
Service
11.5 Diagnostics
• Acknowledge network
Via the button Acknowledge network, the error entries of all automation units located in the network
are deleted, insofar as they are no longer present.
• AU overview diagnosis
The error entries of all automation units in the network are output in a report window via the menu AU
overview diagnostic (sum information for each system element able to report).
• AU individual diagnosis
The error entries of each system element in the AU are output in a report window via double-click on the
respective AU.
• History Diagnosis
The time dependent course of error entries is output in a report window via the menu History Diagnosis.
• Clear history diagnosis

Via the button Clear, all error entries located in the history diagnostis are deleted, insofar as they are no
longer present.
• Automatic diagnosis
An overview of the error entries of all automation units in a network as well as their system elements is
output in a report window via the menu Automatic diagnosis. The outputs are structured hierarchically
in
– Network overview diagnosis
– AU overview diagnosis
– AU single diagnosis
– History (if preset)

DC8-037-2, Edition 11.2020
Service
11.5 Diagnostics
Automatic Diagnosis (Example)
[sc_tbii_automatic_diagnosis, 1, en_US]
Figure 11-16 SICAM TOOLBOX II - Automatic Diagnosis
You find further details on the diagnosis functions in the SICAM TOOLBOX II Online Help, chapter Diagnosis.
You find the description of the diagnosis functions in the manual SICAM RTUs Common Functions System and
Basic System Elements, chapter System Services, section Diagnosis.
11.5.2.3 System Performance

Information on the system performance of a selected automation unit can be interrogated with the tool
“Online Maintenance Function”.
[dw_A8000_toolbox_engineering_service_function, 1, en_US]
Figure 11-17 SICAM TOOLBOX II - System Performance
The following functions are available:

DC8-037-2, Edition 11.2020
Service
11.5 Diagnostics
• Display equipped system elements
• Read serial numbers
• Display/delete data flow routing
• Shut down selected system elements
• Shut down selected automation unit
• Startup selected system elements
• Startup automation unit
• Display time
• Memory check
• Data processing capacity
• Control- and bus runtime
You find further details on the maintenance functions in the SICAM TOOLBOX II Online Help, chapter Service
Programs, section Special Programs | Service Function Online.
11.5.2.4 Diagnosis of the Open-/Closed-Loop Control Function

With the tool “CAEx plus” the following status information can be displayed for each task with the function
ONLINE Test:
• Parameterized cycle time
• Current runtime
• Minimum/maximum runtime
• Number of runtime time-outs
• Bus runtime
Elements, chapter Automation, section Open-/Closed-loop Control Function, section Display Status Infor-
mation.
Errors that can occur with the creation of the function diagram (for example the linking of a binary signal to an
analog input of a function) are displayed in a separate report window (POU error check):
• Automatic upon incorrect input
• Manually with the function Early error detection (pop-up menu in the function diagram)
You find the exact details in the CAEx plus Online Help, chapter Editors, section FBD Editor, section Opera-
tion in FBD Editor.
Errors with Engineering

Errors that can occur with engineering are displayed centrally in the Error-state viewer of “CAEx plus”. It
essentially concerns thereby
• Indications of the installation
• Indications of the export/import
• Indications of the project management
• Indications of the FBD editor

DC8-037-2, Edition 11.2020
Service
11.5 Diagnostics
• Indications of the code generation
• Object-related indications
• Indications of the object assistant
• Indications of the typical import
• Indications of the signal list
• Indications of hardware signal data bases
The indications are created after the initiation of a function (for instance code generation).
You find the exact details in the CAEx plus Online Help, chapter Additional Products, section Error-State
Viewer.
Errors with the Target Device Connection

Errors that can occur with the target device connection are displayed centrally in the Error-state viewer of
“CAEx plus”. It concerns thereby notifications
• of the target device connection
• of the code generator
• of the control panel
• of the online applications
• of the “Open Operating System”
• of the target device integration in the project management
• of the “openPLC”
You find the exact details in the CAEx plus Online Help, chapter Target System Connection, section Program
Messages for Target System Connection.
11.5.3 SICAM WEB
11.5.3.1 Connection Options for the Diagnosis

An online connection of the engineering PC to the target device is required to access the CP-8000/CP-802x
diagnosis data. Read access is also possible if the target device has been engineered with the SICAM TOOLBOX
II. Write access (for example, startup request to the target device) is possible exclusively only.
You can find the basic connection options in section 7.6.2 SICAM WEB. In the following, you can find some
application examples.

DC8-037-2, Edition 11.2020
Service
11.5 Diagnostics
Direct Connection
[dw_A8000_telemaintenance_webserver_direct, 1, en_US]
Figure 11-18 SICAM WEB – Direct Connection

DC8-037-2, Edition 11.2020
Service
11.5 Diagnostics
Connection via Ethernet
[dw_A8000_telemaintenance_webserver_ethernet, 1, en_US]
Figure 11-19 SICAM WEB – Connection via Ethernet
11.5.3.2 Diagnosis Overview

CP-8000/CP-802x provides an automatic diagnosis system. This recognizes ocurring errors, and generates
corresponding indications.
The system diagnosis can be read out in different menus:
• Device information
• Diagnosis indications
– Diagnosis status
– Diagnosis logbook
The recorded indications are differentiated in:
• Errors with the hardware (modules and wiring)
• Errors with the communication
• Errors with the parameter setting
• Errors with the application program

DC8-037-2, Edition 11.2020
Service
11.5 Diagnostics
NOTE
i Error indications may contain additional statements about the possible error cause and notes for the error
removal.
11.5.3.3 Device Information
• Menu Home | Device
On the device page, you can see the specific information of the target device:
• Device view
• Article number
• Application software with revision level
• Device information according to the settings
• System time
[sc_device_info_8000_61850, 1, en_US]
Figure 11-20 SICAM WEB – Device Information (Example: CP-8000)
Under System status you can immediately see the system elements of the target device with the loaded firm-
ware that are not in OK status:
• System element (master module, I/O master module, I/O module, protocol element)
• Status: Faulty (system elements in OK status are not displayed)
• Designation of the system element
• Revision level of the loaded firmware
Under Protocol details, you can find a hyperlink to the Web server of the protocol element in case of a
protocol via IEC 61850. This requires that the Web server has been activated (in the directory tree under
SICAM A8000 CP-80xx | Master module | PRE<0...3>: Ethernet Interface IEC61850
Ed.2 HTTP web server = enabled).

DC8-037-2, Edition 11.2020
Service
11.5 Diagnostics
Click More Information… to connect to the IEC 61850 Web server; the protocol details will open in a new Web
browser tab:
[sc_device_info_61850, 1, en_US]
Figure 11-21 SICAM WEB – More Information (Example: IEC 61850)
For more information refer to the section 12.7.10 Web Server.
Example for CP-8022
[sc_device_info_8022, 1, en_US]
Figure 11-22 SICAM WEB – Device Information (Example: CP-8022)
11.5.3.4 Diagnostics
• Home | Diagnostics menu

DC8-037-2, Edition 11.2020
Service
11.5 Diagnostics
[sc_dashboard_diagnosis, 1, en_US]
Figure 11-23 SICAM WEB – Diagnostics Dashboard
Diagnostics Status
After having opened the diagnostics status page, the currently applicable errors are read out from the target
device and listed in a table.
[sc_diagnosis_status, 1, en_US]
Figure 11-24 SICAM WEB – Diagnostics Status
The diagnostics status shows all current errors in the target device. The errors are shown in plaintext and in
chronological sequence.
The content of each column (except: detailed information) can be sorted in ascending or descending order.
NOTE
i Depending on the communication connection, reading out all diagnostics messages may take some time.
The process cannot be canceled.

DC8-037-2, Edition 11.2020
Service
11.5 Diagnostics
Table 11-8 Diagnostics Status Structure
Column Name Description

Module System element name
Severity Information
Warning
Fault
Topic Serves as quick orientation, for example, Operating system, system startup, communica-
tion to station xy, protocol element
Error text Short Description
Detailed infor- Detailed description
mation
Error class module failure
Communication
Internal
Startup
Warning
Event
Error ID ID of the error
Select a row and a section opens on the right-hand side listing detailed information.
[sc_diagnosis_status_info, 1, en_US]
Figure 11-25 SICAM WEB – Diagnostics Status Information
NOTE
i If you reopen the diagnostics status page during a session, the diagnostics status messages are no longer
updated.
Proceed as follows to update the entries in the diagnostics status:
• Click the general button to once again read out all diagnostics status messages from the device
The existing table is deleted and the detailed information is once again read out from the device and listed in a
table.

DC8-037-2, Edition 11.2020
Service
11.5 Diagnostics
Diagnostic Logbook
After having opened the diagnostics logbook page, recorded messages are read out from the target device
and listed in a table.
[sc_diagnosis_logbook, 1, en_US]
Figure 11-26 SICAM WEB – Diagnostics Logbook
The diagnostics logbook shows the chronological history of all incoming and outgoing errors in the target
device. The errors are shown in plaintext and in chronological sequence (resolution 1 ms).
The content of each column (except: detailed information) can be sorted in ascending or descending order.
NOTE
i Depending on the communication connection, reading out all messages from the diagnostics logbook may
take some time. The process cannot be canceled.
Table 11-9 Diagnostics Logbook Structure

Date/time Time stamp of the diagnostics entry
Module System element name
Severity Information
Warning
Fault
Topic Serves as quick orientation, for example, Operating system, system startup, communica-
tion to station xy, protocol element
Error text Short Description
Error state Incoming or outgoing error
Detailed infor- Detailed description
mation

DC8-037-2, Edition 11.2020
Service
11.5 Diagnostics

Error class module failure
Communication
Internal
Startup
Warning
Event
Error ID ID of the error
The 30 most recent entries are listed as part of the session's first read out.
• Click the button if you want to view older entries
The next older messages are then reloaded and shown. The button remains activated for as long as there are
messages to load.
The error table lists up to 10000 entries and is saved in non-volatile condition. Once the error table is full, the
oldest entry is overwritten with the most recent entry (ring buffer).
Select a row and a section opens on the right-hand side listing detailed information.
[sc_diagnosis_logbook_info, 1, en_US]
Figure 11-27 SICAM WEB – Diagnostics Logbook Information
• Click the sidebar to the right of the table if you would like to hide the detailed description of the selected
entry.
NOTE
i If you reopen the history page during a session the diagnostics logbook messages are no longer updated.
Proceed as follows to update the entries in the diagnostics logbook:
• Click the general button to once again read out all diagnostics logbook messages from the device
The existing table is deleted and the entries that have been created in the device since the last read out are
once again read out from the target device and listed in a table.

DC8-037-2, Edition 11.2020
Service
11.5 Diagnostics
Exporting the Diagnostics Logbook

You can save the diagnostics entries saved in the ring buffer in a file on your PC with the export function.
[sc_diagnosis_logbook_export_info, 1, en_US]
Figure 11-28 SICAM WEB – Exporting History Diagnostics
[sc_diagnosis_logbook_export_success, 1, en_US]
Figure 11-29 SICAM WEB – Exporting History Diagnostics Completed


DC8-037-2, Edition 11.2020
Service
11.5 Diagnostics
Security Logbook
After having opened the security logbook page, the currently applicable errors are read out from the target
device and listed in a table.
[sc_security_logbook, 1, en_US]
Figure 11-30 SICAM WEB – Security Logbook
The security logbook shows all information in the target device relevant to safety. The errors are shown in
plaintext and in chronological sequence.
The content can be sorted in each column in ascending or descending order.
NOTE
i Depending on the communication connection, reading out all security messages may take some time. The
process cannot be canceled.
Table 11-10 Security Logbook Structure

Time Tag Time stamp of the information relevant to security
System Address Address of the corresponding hardware:
Region number
Component
Master module address
Supplementary system element address
Information Short Description
Class Notice
Warning
Alert
Exporting the Security Logbook

You can save the diagnostics entries saved in the ring buffer in a file on your PC with the export function.

DC8-037-2, Edition 11.2020
Service
11.5 Diagnostics
[sc_security_logbook_export_info, 1, en_US]
Figure 11-31 SICAM WEB – Exporting the Security Logbook
[sc_security_logbook_export_success, 1, en_US]
Figure 11-32 SICAM WEB – Exporting the Security Logbook Completed


DC8-037-2, Edition 11.2020
Service
11.5 Diagnostics
11.5.3.5 Time Diagnostics

Open the Time menu to open the time diagnostics. This section shows the clock status.
The clock status reports whether or not the time is subject to a daylight saving time offset and whether or not
it is valid.
[sc_time_set, 1, en_US]
Figure 11-33 SICAM WEB – Clock Status
Errors during time synchronization are recorded in the diagnostics status and in the diagnostics logbook.
11.5.3.6 Diagnostics of the Open/Closed-Loop Control Function

There are various diagnostics functions to monitor the Open-/closed-loop control function.
The diagnostics logbook shows errors that have occurred due to the linkage logic or external effects. The
corresponding monitoring routines are run automatically and no user settings are required for this purpose.
Errors as a result of the syntax or program size are automatically identified during loading via SICAM WEB and
these will be reported in the status log (see Import Application Program, Page 494 paragraph).
If the statement list has been loaded offline (saved in the SD card's root directory), you can manually start the
syntax check in the Logic menu.
The check result is shown in the bottom toolbar. In the event of errors the details are shown in the status
protocol.
• Click the general button if you would like to read the status log

DC8-037-2, Edition 11.2020
Service
11.6 Maintenance of the Hardware
11.6.1 Identifying Hardware Errors
11.6.1.1 Modules
CP-8000/CP-802x monitors the hardware during system startup and in operation. A faulty or failed module is
reported using the error LED at the system and if applicable, at the faulty I/O module. An entry is also saved in
the online diagnostics.
If a hardware failure has occurred, it is necessary to replace the system or the external I/O module.
NOTE
i A defective device can be identified by the fact that after the target device's system startup the yellow RY
LED and the red ER LED do not light up. It is then no longer possible to access it using SICAM TOOLBOX II.
In this case, contact our Customer Support Center.
Users must not open or repair modules!
11.6.1.2 SD Card
CP-8000/CP-802x accesses with each startup the SD card and checks it. The following cases lead to errors with
the SD card:
• SD card not available
• SD card defective
• Wrong type of SD card
• SD card empty
• SD card not formatted
• Checksum error with firmware codes
• Checksum error with parameter files
Possible causes for a checksum error are power failure or write error during a loading processes on the SD
card.
Upon startup with erroneous SD card the supplementary system elements are not started, hence for instance
no remote communication is possible.
CP-8000/CP-802x accesses also during operation the SD card due to operator control actions or loading
processes. With missing SD card loading processes are blocked. With engineering via SICAM WEB the access is
blocked, with loading of web pages (change of the menu) the web browser notifies an error. The target device
performs an automatic logoff. The logon is only possible again with inserted SD card.
! DANGER
Inserting the SD card during operation leads to a restart of the relevant target device! Please note that this
can change the plant status. A restart with the plant running can lead to damage to persons and machines.
² Ensure that aggregates in the control area of the command output as well as those subsequent aggre-
gates in the process chain are protected and that persons in the vicinity are warned.

DC8-037-2, Edition 11.2020
Service
11.6.2 Replacement of a Module
! WARNING
² The removal and attachment of energized modules is not allowed.
² For modules that operate with voltages > 60 V, care must be taken that manipulation on the periph-
eral connectors may only be carried out in a de-energized state.
² The display (LCD, LED) of the modules do not grant a guarantee that the peripheral connectors are de-
energized!
The application data reside non-volatile on the SD card in the Master Module.
When replacing a module by the same type (same revision level), the engineering data (parameters and appli-
cation program) stored on the SD card can be applied automatically for the new module.
If the relevant type is no longer available, then the appropriate successor product is to be used. When
replacing a module by another type, an anew parameterization is necessary. This applies in particular, if some-
thing in the functionality of a module (firmware) was changed, or a module was removed or added. In this
case, the corresponding firmware update must be loaded before the parameter-setting takes place (see
section 11.7 Firmware Update).
The connection of process signals is carried out via removable screw terminals. Since the screw terminals carry
the wiring, no connections need to be detached when changing a module.
The replacement of a module is achievable without a special tool. Please consider the instructions in the
sections 6.4 Assembly of CP-8000 and 6.5 Assembly of CP-802x.
General Procedure for Module Exchange
• Switch the power supply of the relevant device off
• Detach the terminals (with CP-8000 the power supply first) from the module
• Detach the communication cables from the (Master) module
• Remove the module from the DIN rail
• Before replacing the Master Module, you can unlock and withdraw the SD card through pressing, and
then insert it easily in the new Master Module
• Put the new module in place of the withdrawn module on the DIN rail
• Attach the terminals (with CP-8000 the power supply at last) at the module
• Attach the communication cables at the (Master) module
• Switch the power supply of the relevant device on
The new module is operational, if the RY LED is lightning after performed startup.
NOTE
i With CP-8000, internal modules cannot be exchanged.

DC8-037-2, Edition 11.2020
Service
11.6.3 Adapting Newly Installed I/O Modules in the Parameter Setting
• Remove the I/O Master Module in the parameterization and click on the button
• After request, carry out a startup of the target device
• Add the I/O Master Module again and click on the button
• After request, carry out a startup of the target device
CP-8000/CP-802x detects thereby the new mechanical equipment.
NOTE
i Please consider that with the removal of the I/O Master Module the existing parameterization (configura-
tion and settings of the I/Os) is lost.
With startup the parameterization of the detected I/Os is built up newly with the default values.
11.6.3.1 Adding I/O Modules

Additionally equipped I/O Modules are recognized by CP-8000/CP-802x and learnt upon startup, without noti-
fying an error thereby. With parameterization via SICAM WEB, new modules are added automatically in the
directory tree.
11.6.4 Replacing the SD Card
If the use of the SD card is activated with CP-8000/CP-8021/CP-8022, the master module can be exchanged
simply by plug & play.
When replacing the device, only the SD card with the data from the old device must be plugged into the
replacement device.
Upon startup of the device, all required data are checked and - in case of differences to the settings stored in
the device - automatically transferred from the SD card. Thus, when the device is exchanged with the same
type, no subsequent loading process, this means, no engineering tool, will be required. The configuration is
transferred directly to the replacement device.
The use of the SD card is released using the following parameter: SICAM A8000 CP-80xx | Master
module | AU common settings | Security | SD-Card Mode = spare part concept
active and updates via SD-Card allowed.
New SD cards can be ordered at Siemens, see appendix A.9 Memory Cards.
You find the hints for the replacement of the SD card in section 6.6.1 SD Card.
! CAUTION
Insert or remove the SD card only in the de-energized Master Module. The contents of a SD card can
become invalid, if it is removed during a running write procedure.
² If occasion arises, the contents of the SD card must be deleted and written newly again.
You find further technical information in the manual SICAM RTUs Common Functions System and Basic System
Elements, chapter System Services, section Data Storage on Flash Card.

DC8-037-2, Edition 11.2020
Service
11.6.4.1 Initialization of the Firmware

With use of a suitable, still empty SD card, you must download the Firmwares (see 7.3 Loadable Firmwares)
from the website http://www.siemens.com/sicam and copy it into the root directory of the SD card.
• CPC80
• Optional firmware for protocols
• Optional firmware for periphery
• SWEB00 in case of parameterization via SICAM WEB
When the required files are stored on the SD card, insert the SD card into the de-energized target device and
switch that on. During startup the firmwares are configured in the target device.
NOTE
i The startup may last up to 15 minutes (depending on the number of firmwares).
11.6.5 Replacement of the SIM Card (only CP-8022)
When signing a new mobile radio contract or whith change of the mobile network provider you will be
supplied with a new SIM card.
For the activation of the GPRS communication you must replace the hitherto used SIM card by the new one.
You find the hints for the replacement of the SD card in section 6.6.2 SIM Card (CP-8022 only).
NOTE
i Removing or inserting the SIM card is allowed only in the de-energized device!
Subsequently, the access data must be adapted in the parameterization, see 9.1.2.6 Settings for Internal GPRS
Modem (CP-8022).

DC8-037-2, Edition 11.2020
Service
11.7 Firmware Update

In CP 8000/CP 802x, a new system element or the functionality of a system element can be updated in need.
For each system element, an individual loadable firmware is provided. You find information thereto in section
7.3 Loadable Firmwares.
For the accomplishment of firmware updates different methods are possible:
• Engineering via SICAM TOOLBOX II

– online
– offline
• Engineering via SICAM WEB

– online
– offline
The SICAM TOOLBOX II contains after its installation all current firmware revisions (based on the date of issue
of the installed version).
Procedure for the Update of System Elements
[dw_A8000_toolbox_engineering_fw_update, 1, en_US]
Figure 11-34 SICAM TOOLBOX II - Procedure Firmware Update
11.7.1.1 Interrogation of the Firmware Revision

The firmware revisions of all configured system elements (Master Module, I/O Master Module, protocol
elements) can be displayed and printed with the tool “Revision Interrogation and Display” for a selected auto-
mation unit.
You find further details on the tool in the SICAM TOOLBOX II Online Help, chapter Service Programs, section
Revision Interrogation and Display.
11.7.1.2 Importing Master Data into the SICAM TOOLBOX II

New firmware codes can be loaded into the SICAM TOOLBOX II with the tool “Master Data Update”. Thereto
belong
• Libraries for the tool “OPM II”
• Firmwares of SICAM RTUs system elements

DC8-037-2, Edition 11.2020
Service
You find the details thereto in the SICAM TOOLBOX II Online Help, chapter OPM II, section Master Data
Update.
An additional option provides the tool “Live Update”. You find the information thereto in the SICAM TOOLBOX
II Online Help, chapter Service Programs, section Live Update.
11.7.1.3 Loading Firmware Codes into the Target Device

Firmware codes that are stored in the SICAM TOOLBOX II can be loaded into a target device.
Loading Firmware Online

For the accomplishment the engineering PC must be connected with the target device, and a suitable SD card
must be inserted in the target device. The configuration options listed in section 7.6.1 SICAM TOOLBOX II
apply.
NOTE
i A serial connection via modem is not supported.
With the tool “Load Firmware” (TOOLBOX II | Service Programs ) you can load firmware codes into the target
device. The following options are available:
• Load intelligent
The latest firmware revision available in the SICAM TOOLBOX II is loaded, if it is more current than that
one on the corresponding system element
• Load unconditional
The latest firmware revision available in the SICAM TOOLBOX II is loaded
You find the instructions for the tool “Load Firmware” in the SICAM TOOLBOX II Online Help, chapter Service
Programs, section Load Firmware.
Loading Firmware Offline

For the accomplishment a SD card reader/writer must be connected on the Toolbox PC, and a suitable SD card
must be inserted.
With the tool “OPM II” you can select the corresponding AE via the menu Tools | System technique. Via the
context menu of the automation unit Flashcard | create files… you can transfer firmware files on a SD card.
You find the details thereto in the SICAM TOOLBOX II Online Help, chapter OPM II, section System technique
| SICAM RTUs | Load Flashcard.
Insert the SD card afterwards in the de-energized target device, and then switch on the power supply. The
target device performs a startup (duration up to 15 minutes depending on number and size of the loaded
files) and loads thereby the firmwares of the corresponding modules.
11.7.2 SICAM WEB
11.7.2.1 Loading Firmware to the Target Device

As part of project engineering using SICAM WEB, updated firmware codes made available as binary files on the
https://support.industry.siemens.com web page can be easily loaded to the target device.
NOTE
i SICAM TOOLBOX II firmware updates cannot be loaded using SICAM WEB.

DC8-037-2, Edition 11.2020
Service
Loading Firmware Online

For this purpose, the project engineering PC must have been connected to the target device and a suitable SD
card must have been inserted into the target device. The configuration options listed in the 7.6.2 SICAM WEB
paragraph apply.
In each case you can directly load 1 firmware file each to the target device. Refer to the 9.3.7 Update Firm-
ware paragraph for corresponding instructions.
The firmware is saved on the SD card in the target device during loading. The target device then runs a system
startup whereby the associated module is updated (if it has already been installed). Modules that had previ-
ously not been installed now appear in the selection in the Assembly menu.
NOTE
i CPC80 and SWEB00 firmware that is already running must be available on the target device to load using
SICAM WEB. This firmware has already been loaded to the target device's SD card during production.
Loading Firmware Offline

For this purpose, an SD card reader/writer must have been connected to the project engineering PC and a suit-
able SD card must have been inserted.
• Now copy the required firmware files from the PC to the root directory of the SD card
• Then insert the SD card into the de-energized target device
• Then switch on the power supply
The target device now runs a system startup (takes up to 15 minutes depending on the number and size of the
loaded files) and in this process, it loads the firmwares for the associated modules (if these have already been
installed).
11.7.3 Errors with Loading of Firmware
For a perfect functioning of the Master Module, it is absolutely necessary that the loading process completes
without errors.
If the loading process is terminated with an error, cancel it. Afterwards, start the loading process again and
attempt to complete without error. If an error occurs again, check the record in the diagnosis and the lighted
display on the Master Module.
The following reasons lead to a malfunction of the Master Module:
• Voltage failure
• Premature abortion by the user
• Failure (defect, shutdown) of the engineering PC
• Abortion due to hardware error
• Abortion or excessively long fault of the communication connection between engineering PC and target
device
You find further technical information in the manual SICAM RTUs Common Functions System and Basic System
Elements, chapter System Services, sections Loading Operation and Firmware Shut Down.

DC8-037-2, Edition 11.2020
Service
11.8 Resetting Device to Factory Settings

A Secure Factory Reset sets the device in the delivery status. This means that the following information rele-
vant to security is deleted from the customer system or it is reset to factory settings:
• All applications (firmware), except CPC80, SWEB00
• All configurations (parameters, user management, users, passwords, keys, certificates)
• All logging and diagnostics information (diagnostics logbook, security log)
• All data on the SD card
When is a Secure Factory Reset necessary?
• The device is faulty and you intend to return it to the manufacturer
• All interfaces have been configured as secure using role concept and secure configuration (access no
longer possible) and the administrator password has been forgotten/lost
Procedure for CPC80 from V14:
• Remove the current SD card from the device
• Save a text file called FactoryReset.txt in the root directory of this SD card
Content of the file: FactoryReset
• Insert the SD card into the master module and switch on the device
• Wait until the RY LED lights up (may take up to 15 minutes)
Procedure for CPC80 up to V13:
• Remove the current SD card from the device
• Format this SD card
• Using SICAM TOOLBOX II:

– Create a new AU and create the SD card using this configuration
• Using SICAM WEB:

– Copy the SC8-080-1_13.bin file to the SD card
• Insert the SD card into the master module and switch on the device
• Wait until the RY LED lights up (may take up to 15 minutes)
Comparing Factory Settings To Default Settings

The following table shows the items affected by a Secure Factory Reset and their configurations following the
reset in the “Factory settings” column. Additionally, the “Default settings” of the corresponding items have
been listed in the next column for comparison.
Table 11-11 Comparison of the Settings from CPC80 V14
Pin Factory settings Default settings → New AU,

parameters configured using
SICAM TOOLBOX II
Firmwares/applications CPC80, SWEB00 (version as per the CPC80, SWEB00 (version as per the
last version loaded) last version loaded)
Region number 249 is set during creation of the AU

DC8-037-2, Edition 11.2020
Service

SICAM TOOLBOX II
Component number 254 is set during creation of the AU
X1 (TCP/IP address) 172.16.0.3 172.16.0.3
Remote operation Blocked Blocked
Web browser for SICAM WEB Enabled via… Enabled via…
(https)
serial connection with Enabled via… Enabled via…
SICAM TOOLBOX II
Standard user admin (no password set) admin (no password set)
Mode of SD-Card Spare Parts Concept Spare Parts Concept
Table 11-12 Comparison of the Settings up to CPC80 V13

SICAM TOOLBOX II
Firmwares/applications CPC80, SWEB00 (version as per the CPC80, SWEB00 (version as per the
last version loaded) last version loaded)
Region number 249 is set during creation of the AU
Component number 254 is set during creation of the AU
X3 (LAN 1) TCP/IP address 172.16.0.3 172.16.0.3
Remote operation Blocked Blocked
Web browser for SICAM WEB Enabled via… Enabled via…
(https)
serial connection with Enabled via… Enabled via…
SICAM TOOLBOX II
Standard user admin (no password set) admin (no password set)

DC8-037-2, Edition 11.2020
Service
11.9 Remote Servicing
11.9 Remote Servicing

Apply the “web.engineering” option to use a controlling PC (remote maintenance center) and remotely control
a remote SICAM TOOLBOX II (remote maintenance session) that is available via a data connection (modem,
ISDN, LAN/WAN).
[dw_A8000_toolbox_web_engineering, 1, en_US]
Figure 11-35 SICAM TOOLBOX II – Remote Maintenance
With “web.engineering” all SICAM TOOLBOX II clients operate with a central web server running the SICAM
TOOLBOX II. In this process, the SICAM TOOLBOX II is run in a web browser.
11.9.1 Configuration of Server and Clients
Install on the web server Microsoft Windows with Terminal Services Web Access (TS Web Access). After that
install the SICAM TOOLBOX II on this server.
On the clients is no installation required, the access to the web server takes place via the Microsoft Internet
Explorer (as of version 5.0).
You find a detailed description of the configuration in the SICAM TOOLBOX II Online Help, chapter web.engi-
neering.

DC8-037-2, Edition 11.2020
DC8-037-2, Edition 11.2020
12 Communication Protocols
12.1 Introduction 594

12.2 IEC 60870-5-101 (Dial-Up Communication) 604
12.3 IEC 60870-5-101 (Point-to-Point Traffic) 655
12.4 IEC 60870-5-101 (Multi-Point Traffic) 703
12.5 IEC 60870-5-103 758
12.6 IEC 60870-5-104 832
12.7 IEC 61850 900
12.8 Modbus RTU 1058
12.9 Modbus TCP 1166
12.10 DNP3 1288
12.11 SINAUT ST1 1400
12.12 Telegyr TG800 1440
12.13 ASCII SMS 1531
12.14 IEC 62056-21 (Meter Protocol) 1566
12.15 SAT SK 1703 1570
12.16 ABB RP570/571 1632
12.17 Benning MCU 1710
12.18 AGP (Power Distributor Branch Specific Test Equipment) 1746
12.19 IOT 1792
12.20 VLAN 1820
12.21 SNMP 1823

DC8-037-2, Edition 11.2020
Communication Protocols
12.1 Introduction
12.1 Introduction
12.1.1 Overview
A communication protocol 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, for
example, control systems.
The task of the communications protocol is:
• the processing of specific communication protocols for the communication of SICAM A8000 automation
units with each other or with devices of other manufacturers
• Adaptation of the internal telegram formats to the corresponding, external telegram formats
• the adaptation of system and addressing concepts of SICAM A8000 and the devices of other manufac-
turers
Thereby a distinction is made between communication protocols with serial communication or with LAN /
WAN communication.
Serial Communication
For serial communication are available as standard protocols:
• IEC 60870-5-101 (Point-to-point traffic)
• IEC 60870-5-101 (Multi-point traffic Master)
• IEC 60870-5-101 (Multi-point traffic Slave)

However, there is a host of additional protocols available, such as:
• IEC 60870-5-103 (Multi-point traffic Master for interfacing of protective devices)
• Modbus RTU
LAN/WAN Communication
The following protocols are available for LAN/WAN communication:
• IEC 60870-5-104
• IEC 61850 (Client, Server, Goose)
• Modbus TCP
• DNP3 via Ethernet (TCP/IP)
NOTE
i The hardware of the protocol elements has been integrated on the master module . The associated details
have been described in the corresponding Technical Data paragraph.
12.1.2 Limits of the Communication Protocols
Table 12-1 The following limits apply for the basic system element and for each installed protocol
element:
Firmware Max. number of remote Max. number of remote Max. number of data points
partners partners (recom-
mended)
AGPMT0 1 1 24
BMCUT0 1 1

DC8-037-2, Edition 11.2020
12.1 Introduction
Firmware Max. number of remote Max. number of remote Max. number of data points
partners partners (recom-
mended)
BPPT0 1 1 81
DIAST0 1 1 81
UMPMT0 100 20 to 30 81
UMPST0 1 1 81
103MT0 100 10 1000

ET84 100 10 (5 with TLS) 81
ET85 "Client" 100 20 1000

ET85 "Server" 6 20000 82
DNPiT2 4
DNPiT1 1 1 2000
DNPMT0 100 20 2000
DNPST0 1 1 2000
PCBST0 1 1
RP5UT1 1 1
ST1ST0 1 1
SMST0 10 SMS: 500, printer: 1500
COUMT0 10
TG8ST0 1 1
MODMT2 100 20 to 30 2000
MODST0 1 1 500
MBCiT0 "Client" 100 20 to 30 1000
MBSiT0 "Server" 100 10 to 20 1000
OPUPT0 1 1 500
OPUPT1 1 1 500
NOTE
i The respective number of possible datapoints applies if only the one respective protocol is used. If several
different protocols are used, the maximum number of possible datapoints may be less.
With LAN protocols take notice that a datapoint that is transmitted via multiple connections must be
considered n-fold.
You must consider also the total number of supported datapoints for SICAM A8000 CP-8000, CP-8021,
CP8022. As a datapoint in the system counts each datapoint that is acquired or output by the I/O Modules,
that is processed in the Automation Function (input/output), or that is received or transmitted via serial or
LAN interfaces for each connection.
12.1.3 Common Functions
12.1.3.1 Control location function for commands and setpoint values

The “Control location” function is used to exclusively output commands and setpoints from "Authorized
sources" to the substations.
81 Unlimited (limited only by available memory)

82 For a more accurate determination of the maximum possible number of data points depending on the number of LogicalDevices/
Connections/Data Points, see Formulas for the determination of the total number of data points (n):, Page 906

DC8-037-2, Edition 11.2020
12.1 Introduction
Possible control locations (points authorized to control):
• Local command input
• Local control
• Local SCDA system
• Command input at one of the superordinate master stations
• Command input at one of the superordinate operating points (SCADA systems)
• …
The control function is a controllable filter at the protocol element which exclusively lets through commands
and setpoints from enabled control locations to substations. Commands and setpoints to substations from
disabled (that is, not authorized) control locations are rejected by the protocol element and confirmed with
ACTCON.
Authorized sources are addressed using the originator address (control location) in the IEC 60870-5-101/104
command/setpoint telegram.
Activate control location function

The “Control location” function is activated at the protocol element as soon as a signal with the “Protocol
element control telegram CP-80xx” processing type has been entered at the base system element (BSE) for the
protocol element (PRE) with the Control_function_(PRE) = Set control location. After PRE system
startup, the BSE sends a Set control location PRE control telegram to the PRE. This activates the
“Control location” function with control location check at the PRE.
Enable/disable Control Location

The selection which origin addresses (control locations) may send commands/setpoint values to substations
must be made either in the control system or in an application program of the open-/closed-loop control func-
tion of the central station.
The release/block of the control locations is carried out regardless of the command or setpoint value that is to
be sent with an single command telegram in single command format <TI:=45> which is transferred to a Set
control location PRE control telegram at the base system element by the “Protocol control” function.
A confirmation of activation (ACTCON) and termination of activation (ACTTERM) is not emulated for the
Release/block control location command telegram.
The control location has been entered in the originator address of the command telegram.
The Release/block control location is exclusively processed internally at the protocol element and it
is not transferred to the remote partner.
Originator address control location
0 Not specified
1 to 127 Remote command
128 to 255 local command
NOTE
i The released/blocked control locations must be transmitted to the protocol element with the control tele-
gram defined accordingly for "Control location".
With the control location function activated, all control locations are blocked following protocol element
system startup, that is, all required control locations must be set from scratch!
Enable/disable Control Location
• Release/block control location with Set control location PRE control telegram
• Single command state ON = Release control location

DC8-037-2, Edition 11.2020
12.1 Introduction
• Single command state OFF = Block control location
• enable/disable selective control location for selective station
• enable selective control location for all stations
• all control locations are blocked for all stations
• the enabled/disabled control locations apply to all commands of a protocol element
• after startup of the protocol element all control locations are blocked
NOTE
i The enable/disable of the control locations can either be performed globally for all stations or for selective
stations.
A mixed control of the control locations (enable control location selective - disable control location globally
for all stations) is not supported!
Protocol Element Control Telegram

The conversion of the command to release/block the control locations to a PRE control telegram is carried out
in the SICAM Device Manager with the “Signals” function and the “Protocol element control telegram”
processing type.
• Creating signals for the control location in SICAM Device Manager
[DM_PRE_Steuerort_a, 1, en_US]
Parameter
Name Signal name
CASDU1, CASDU2 IEC 60870-5-101/104 telegram address (104 address)
IOA1, IOA2, IOA3
TI Supported type identifications:
• <TI:=45> ... Single command

Unit … Not used for protocol element control telegram !
Description Signal description
• Assigning signals for the control location to the central processing or base system element (BSE)
[DM_PRE_Steuerort_b, 1, en_US]

DC8-037-2, Edition 11.2020
12.1 Introduction
Parameter
Name Signal name 83
104 address IEC 60870-5-101/104 telegram address 83
TI .. Type Identi- Supported type identifications 83
fication
Processing type Processing type
• Protocol element control telegram
• Parameters for control telegram protocol element (control function = Set control location)
[DM_PRE_Steuerort_c2, 1, en_US]
Parameter
Name Signal name 83
104 address IEC 60870-5-101/104 telegram address 83
(CASDU1, CASDU2, IOA1, IOA2, IOA3)
TI .. Type Identi- Supported type identifications: 83
fication
Control_func- Control function
tion_(PRE)
• 242 = Set control location
Edge_(PRE) … Not used for control function 242
(Must be set to positive edge)
PRE_(PST) Assignment of the control function to a protocol element (PRE):
• PRE 0 to PRE 7
83 These parameters are specified during signal definition.

DC8-037-2, Edition 11.2020
12.1 Introduction
Parameter
Station Assignment of the control function for a station (SICAM A8000 internal station
number):
• 125 … All stations

SCS=<ON>: Release control location for all stations
SCS=<OFF>: Disable all control locations for all stations
• 0 to 99 … Station 0 to 99
SCS=<ON>: Release control location for stations
SCS=<OFF>: Block control location for stations
Note:
• The <SCS> command state

(single command state) specifies the release/block of the control location
• The control location has been entered in the originator address of the
<TI:=45>
command telegram.
Additional_param- Must be set to 65535
eter_(PRE)
Control location check

If the “Control location” function has been activated, commands and setpoints from the protocol element are
only transferred to the remote partner if the command or setpoint has been sent from an authorized source,
that is, from an enabled control location (originator address). After startup of the protocol element, no control
locations are enabled.
If the “Control location” function has been activated and the control location has not been enabled,
• the command/setpoint value is not transmitted to the remote station
• a negative acknowledgment of the activation (ACTCON-) for the command/setpoint value is transmitted
to the source address
If the “Control location” function has not been activated, commands and setpoints are transferred to the
remote partner without control location check.
Showing the Control Location

For protocol elements that support the web server, the enabled control locations are displayed on the Deve-
loper Information – Diagnosis (IDE) website in Control location.
Examples:
• Control location function activated, no control location enabled for all stations
[U80ZI0_Web_IDE_Steuerort_Alle_HKA_gesperrt_, 1, --_--]

DC8-037-2, Edition 11.2020
12.1 Introduction
• Enable control location 1, 2, 3 for all stations
[U80ZI0_Web_IDE_Steuerort_Alle_Stationen_HKA_123_, 1, --_--]
• Enable control location 1, 2, 3 for stations 50 only
[U80ZI0_Web_IDE_Steuerort_Station_50_HKA_123_, 1, --_--]
12.1.3.2 Data Management on the BSE for Communication Protocols
At the basic system element (BSE) a PRE-specific data management (process image, rings, ...) for the chrono-
logical or state storage of the data in the transmission direction is implemented for each communication
protocol (PRE). In this data management, all data to be sent are stored independently of the protocol in the
internal format IEC 60870-5-101/104.
The parameters for the PRE-specific data management are part of the protocol - the function of the data
management is on the BSE.
The format conversion from the internal IEC 60870-5-101/104 format to the format of the respective protocol
is carried out on the protocol element. Depending on requirements, a protocol-dependent process image is
additionally implemented on the PRE.
In the receive direction, no PRE-specific data management is implemented at the BSE. Received telegrams are
immediately distributed to the destination (peripheral element for data output, for transmission to another
communication protocol, input process image for function diagram, etc.).
For details, see "Communication functions on the basic system element".
Parameters and properties for data management

Depending on the protocol element, some parameters may not be visible if not needed.

DC8-037-2, Edition 11.2020
12.1 Introduction
Parameter Name Description Settings

[PRE] Data base management
Settings for the data base management on BSE (per PRE)
[PRE] Data base management | Messages in send direction
TI 32 Step position infor- Permitted range =
mation
• state change stored
• chronological
Default setting = state change
stored
TI 34 Measured value, Permitted range =
normalized value
• chronological
stored
scaled value
• chronological
stored
short floating point
number • state change stored
• chronological
stored
[PRE] Data base management | Priority
Priority messages Permitted range =
• high priority
• middle priority
• low priority
Default setting = high priority
Priority measured values Permitted range =
• high priority
• middle priority
• low priority
Default setting = medium priority
Priority integrated totals Permitted range =
• high priority
• middle priority
• low priority
Default setting = high priority

DC8-037-2, Edition 11.2020
12.1 Introduction

[PRE] Data base management | Data base management at failure
Failure behavior for Processing of stored process infor- Permitted range = 0 to 65535 s
process inform. mation in case of communication 0 .. Delete data immediately
failure. 65535 .. Do not delete data
1-65534 .. Delete data after the set
time
Default setting = 65535 s
Failure behavior for Processing of stored process infor- Permitted range =
process inform (GI) mation (GI data) in case of commu-
nication failure.
• Do not delete
• Delete
Default setting = do not delete
Failure behavior for Processing of stored "transparent Permitted range =
transparent info. information" in case of communica-
tion failure.
• Do not delete
• Delete
Default setting = do not delete
[PRE] Data base management | Advanced parameters | Memory size
Buffer size priority Permitted range = 0; 5 to 65535
channel high data class 1 0 .. automatic
5 - 65535 … number of entries
Standard setting = 0
channel middle data class 0 .. automatic
1 5 - 65535 … number of entries
channel low data class 1 0 .. automatic
channel high data class 2 0 .. automatic
channel middle data class 0 .. automatic
2 5 - 65535 … number of entries
channel low data class 2 0 .. automatic
[PRE] Data base management | Advanced parameters | Data base management at
memory size error
Storing of process infor- Buffer overflow clears the selected Permitted range =
mations if buffer overflow process information.
• delete the oldest
• delete the newest
Default setting = delete the newest

DC8-037-2, Edition 11.2020
12.1 Introduction

Storing of measured values Buffer overflow clears the selected Permitted range =
if buffer overflow process information.
• delete the oldest
• delete the newest
Default setting = delete the newest
Reset of buffer overflow The error "buffer overflow" is Permitted range =
cleared at xx%.
• at 50% free
• at 100% free
Default setting = at 100% free
Suppress diagnostic info Permitted range = yes, no
"ring overflow for data to Default setting = no
PRE"

DC8-037-2, Edition 11.2020
12.2 IEC 60870-5-101 (Dial-Up Communication)
12.2.1 Introduction
Dial-up traffic describes a serial communications protocol with which a central station (Master) is connected
with one or more substations (Remote station) 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 spon-
taneously by the central station as well as by the substation. With connection established, the data traffic is
controlled by the central station.
Either data messages or station interrogation messages are transmitted from the central station. Data from the
substation to the central station can only be transmitted as reply to a station interrogation.
With connection established in dial up mode the transmission of telecontrol data is based on IEC 60870-5-101
(unbalanced) with proprietary extensions and the usage of additional message formats in the private range of
IEC 60870-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, the central station initiates all message transmissions, while the substations may
only transmit when they are called.
The dial-up traffic 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-101A
• 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
12.2.2 General Functions
Communication of a central station with up to 100 substations.
• Unbalanced multi-point (dial-up traffic) based on IEC 60870-5-101

DIAST0 is substation

DC8-037-2, Edition 11.2020
• 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
– Data acquisition by polling (station interrogation)
– Acquisition of events (transmission of data ready to be sent)
– General interrogation, outstation interrogation
– Clock synchronization
– Each time a connection has been established
– When a connection is established, one time per minute
– Command transmission
– Transmission of integrated totals
• Coordination 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) tele-
phone network
• Multi-hierarchical configurations
• Optimized parameters for selected transmission facilities
• Toll-Saving Transmission Strategies
• Having a telephone set connected in parallel
• Functions for supporting redundant communication routes
12.2.3 Operating Modes
The operating mode of the interface is determined by parameters of the protocol element and optional
devices.

DC8-037-2, Edition 11.2020
Operating mode Interface → Interface signals

optional DTE
Unbalanced interchange circuit (V.24/V.28) X2 →Modem RXD, TXD, CTS84, RTS, DCD, DTR,
RS-232 asynchronous (GSM, PSTN, DSR/VCC, GND
TETRA, ISDN)
Unbalanced interchange circuit (V.24/V.28) RS 232 X685 RXD, TXD, CTS, RTS, DCD, DTR, DSR,
asynchronous GND
NOTE
i Details about realization of various operation modes are given in the manual SICAM RTUs Platforms –
Configuration Automation Units and Automation Networks.
12.2.4 Communication
For the communication infrastructure, additional suitable transmission facilities and/or network components
may be needed.
Own Station (Substation)
System System element Protocol element Remarks

SICAM A8000 CP-8000/CPC80 DIAST0
CP-802x/CPC80
Remote Station (Central Station)

SICAM AK 3 CP-2016/CPCX26 SM-2551/DIAMA1
CP-2019/PCCX26 SM-0551/DIAMA1
Legacy systems CP-20xx SM-2551/DIAMA1
(SICAM AK CP-50xx SM-0551/DIAMA1
SICAM TM CP-60xx SM-2541DIAM00
SICAM BC
Ax 1703)
12.2.5 Controlling Connection Establishment and Disconnection
A connection setup for the transmission of data over the telephone network can be performed spontaneously
or cyclic by the central station as well as by the substation.
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
84 not usable (reserved for SICAM TOOLBOX II)

85 only CP-8022 (RS-232 mode)

DC8-037-2, Edition 11.2020
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 protec-
tion).
Co-ordination of several masters in “Multi-Master” Mode

In the Multi-Master mode, provided there are several dial-up modems available in the central station and just
as many SM-25xx/DIAMxx protocol elements, more than one connection can be established simultaneously
with different substations, whereby no fixed assignment of the substations to one specific master is required.
By means of that higher availability and higher data throughput is achieved.
Red Telephone
In the central 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 central 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 substations.
In the substations, commonly only one telephone number (main telephone number) of the central station is
parameterized. The stepping to the individual modems in the central station is normally carried out by the
functionIn “Private branch series or telephone number stepping” of the telephone system or by a corre-
sponding service of the telephone network operator.
An active connection setup is not carried out by the central station over this interface. The function “Red Tele-
phone” is only implemented in combination with the function “Multi-Master in dial-up traffic” and is enabled in
the advanced parameters with the parameter Advanced parameters | Red telephone.
The failure management of the substations 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.
Common utilization of one modem by different interfaces

An “active interface” established by the redundancy state in dial-up traffic always requires one specific trans-
mission 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.
12.2.5.1 Security for Dial-Up Traffic

For the data communication using dial up mode a serial based communication protocol based on IEC
60870-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.

DC8-037-2, Edition 11.2020
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 transmis-
sion 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)
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!
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 IEC
60870-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.
Scrambling
The data communication protocol for transmission of telecontrol data in dial up mode based on IEC
60870-5-101 does actually not support scrambling of data!
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 IEC 60870-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 must be parameterized in the master station.
→ No identification (validation) of the telephone number of the calling station!

DC8-037-2, Edition 11.2020
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 IEC 60870-5-101 use an authenti-
cation (password and access key) after every connection set-up.
The authentication (LOGIN procedure) will be done after each successful connection set-up (does not matter if
the connection set-up is initiated by the central station or by the substation) and after successful procedure for
station identification.
The authentication will be controlled by the central station and confirmed after successful verification by the
substation.
Possible methods for authentication:
• Basic Security: Password
• Enhanced Security: Password + access key (for SICAM A8000 stations)
• Enhanced Security: Password + access key (for 3rd party systems)

The method for authentication can be selected in the central station for each individual substation (default =
Enhanced security for SICAM A8000 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!
For interfacing 3rd party systems supporting this communication protocol used for transmission of telecontrol
data in dial up mode an “authentication using password” or an “authentication using password + access key
(for 3rd party systems)” must be used.
Authentication with Password

The authentication with password is only used in combination with older systems and enables a basic protec-
tion “Basic security” against unauthorized access. This security mode is not longer used with standard configu-
rations (is used only for interfacing of older existing substations 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 connec-
tion 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
Authentication with Password + Keys for SICAM A8000

The authentication with “password + access key for SICAM A8000 substations” 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 uses 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!

DC8-037-2, Edition 11.2020
The access to the SICAM A8000 substation will be enabled only with valid password and valid access activation
key. The data transfer from the substation will be activated in the central station only after receiving a valid
access confirmation key.
• The password is parameterized and stored in the central station and in the substation
• The access activation key (64 Bit) is generated dynamically in the central station
• The password + access activation key + station number will be sent to the substation after each connec-
tion 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 central station including the new generated access confirmation
key.
→ the central station checks also the validity of the access confirmation key
• Data transfer enable

→ the central station enables the data transfer from/to the substation only after receiving a “positive acti-
vation confirmation” including a valid access confirmation key according the defined LOGIN procedure
→ the substation enables the data transfer from/to the central station only after receiving a valid pass-
word + access activation key according the defined LOGIN procedure
This authentication method is only used for SICAM A8000 systems and this method will not be published!
Authentication with Password + Keys for 3rd Party Systems

The authentication with “password + access key for 3rdparty substations” is actually not used!
This authentication method will be published to manufacturer of 3rd party system on request, if 3rd party
substations must be interfaced to SICAM A8000 central 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 A8000
substations, but different methods for generating the keys will be used.
12.2.5.2 Connection Establishment spontaneously and cyclically, Controlling Station ↔ Controlled Station
With an error-free state, a connection setup by the central station or substation is always initiated to the tele-
phone number (first telephone number) of the substation, which is set according to the parameter Connec-
tion 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 substation by the central station
• Transmission of the user data between central station and substation
• GI-request of the central station to the substation (optional)

The general interrogation function after every active connection establishment can be activated in the central
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 central
station itself and transmitted to the substation.
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 substation, these can be used
for redials. The use of main/standby telephone numbers is established by the mode for connection setup – this

DC8-037-2, Edition 11.2020
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 parame-
terized main telephone number.
Redials are thereby always performed directly one after the other on expiry of the parameterized timeouts and
delays. Redials from the central station to a substation are not interrupted by data to another substation.
In the central station, if another substation 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 connec-
tion setup is performed to that substation whose redials were previously interrupted. For this substation, 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 substation is reported as failed. In the central station, the message not transmitted is discarded
after expiry of the dialing attempts. In the substation, 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 substation or central 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 substation, 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 imme-
diately.
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 Connec-
tion 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 substation is negatively acknowledged to the basic system element (BSE) and trans-
mitted 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.
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 central station

If a second telephone number (standby telephone number) is parameterized for the substation in the central
station in addition to the main telephone number, the connection setup to the substation 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 (per substation) Mode-0 Mode-1 Mode-2 Mode-3 Mode-4
Main telephone number ✓ ✓ ✓ ✓ ✓
Standby telephone number (optional) ✓ ✓ ✓ ✓
The main telephone number of every substation is to be set in the central station with the parameters
Station definition | Main Tel No. The standby telephone number of every substation is to be set in
the central station with the parameters Station definition | Secondary phone number.

DC8-037-2, Edition 11.2020
Mode for Connection Setup Note

Mode-0 Main number A connection setup to the substation is only performed to
the main telephone number.
Mode-1 Main number + standby number A connection setup to the substation 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 tele-
phone number.
Mode-2 Main number + standby number A connection setup to the substation is always performed
(alternating telephone numbers) to the main telephone number first.

be established, further dialing attempts are made alter-
nating to the standby telephone number and then to the
main telephone number again.
Mode-3 Main number + standby number A connection to the substation 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 Connec-
tion setup | Mode 3 day_night | Day number
- hour and with the parameter Connection setup |
Mode 3 day_night | Day number - minute. zu
parametrieren.
→ The time range in which the standby telephone number

is used is to be parameterized with the parameter Connec-
tion setup | Mode 3 day_night | Night
number - hour and with the parameter Connection
setup | Mode 3 day_night | Night number -
minute. zu par
Example:
from 08:00 to 20:00 … connection to the substation only
via the main telephone numbervon
from 20:00 to 08:00 … connection to the substation only
via the standby telephone number
Mode-4 Main number + standby number A connection to the substation is established to that tele-
(selection with phone number (main or standby telephone number)
PRE control message) selected via PRE control message.
→ If the connection to this telephone number cannot be

established, redials are only performed to the selected tele-
phone number.
Connection setup modes of the substation

If other telephone numbers (standby telephone numbers) are parameterized for the central station in the
substation in addition to the main telephone number, the connection setup to the central station is performed
to that telephone number that is determined with the selected mode for connection setup.

DC8-037-2, Edition 11.2020
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
central 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 central station is only performed
to the main telephone number.
The main telephone number is to be set with the param-

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

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 tele-
phone number.
1 | Main phone number. einzustellen.
The standby telephone number is to be set with the param-

1 | Substitute phone number 1.

DC8-037-2, Edition 11.2020

Mode-2 Main number + 3 standby numbers A connection setup to the central station is always
(alternating telephone numbers) performed to the main telephone number first.

be 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.
2 | Main phone number.
The standby telephone numbers are to be set with the

parameter Connection setup | Telephon number
mode 2 | *.
Mode-3 Main number + standby number A connection to the central station is established either to
(day/night operation) the 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 Connec-
tion setup | Mode 3 day_night | Day number
- hour and with the 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 Connec-
tion 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 to 20:00 … connection to the central station
only via the main telephone number
from 20:00 to 08:00 … connection to the central station
only via the standby telephone number
3 | Main phone number einzustellen.


DC8-037-2, Edition 11.2020

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

established, redials are only performed to the selected tele-
phone number.
4 | Main phone number.

Mode-5 Standby transmission line via dial-up Substations are connected to the central station over the
traffic main transmission line (SICAM A8000 multi-point traffic or
point-topoint protocol). Every substation is also equipped
with a dial-up modem. If the substation is no longer reach-
able on the main transmission line, a connection over the
telephone network (dial-up traffic) is established automati-
cally.
→ 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 substation can be reached again on the main trans-
mission line during this delay time, the standby transmis-
sion 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 | *.
Cyclic Connection Setup at a settable Interval (monitoring cycle)

A cyclic connection setup can be performed by the central station as well as by the substation at a settable
interval (monitoring cycle) and is used in particular for:
• Monitoring the station availability, monitoring the substation
• Transmission of low priority data from the substation to the central station

DC8-037-2, Edition 11.2020
In the monitoring cycle of the central station, a connection setup is performed 1 x to every parameterized
substation. Through the monitoring cycle, failed substations are detected by the central station and signaled
as failed.
In the monitoring cycle – triggered by the substation, a connection setup is performed 1x to the central
station. Through this monitoring cycle, if necessary a failure of the central stations can be detected by the
substation.
For failed substations, 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 central station to the substation
• Transmission of low priority data from the substation to the central station (these data is stored in the
substation and first transmitted with the next connection setup)
Spontaneous data from the central station to another substation during a running monitoring cycle are trans-
mitted after the disconnection of an existing connection. The monitoring cycle is thereby interrupted by spon-
taneous data and then resumed – these substations are then no longer handled in the monitoring cycle.
Spontaneous data from the central station to that remote terminal to which a connection has just been estab-
lished 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, timecontrolled or time-
controlled by the “Multi-Master” function on the basic system element.
Cyclic monitoring
The cyclic monitoring starts after startup of the central station or substation 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 substation, 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 | Moni-
toring times | Cyclic monitoring | Multiplicator and the parameter Advanced parame-
ters | 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 substations by the central station can be set with the param-
eter Connection setup | Monitoring cycle for failed stations. The cyclic monitoring of
failed substations 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 moni-
toring 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

DC8-037-2, Edition 11.2020
Time Moment 2:

hour

minute
Time Moment 3:

hour

minute
Time Moment 4:

hour

minute
Time-controlled monitoring by basic system element (“Multi-Master”)

For the “Multi-Master”operating mode in the central station, a time-controlled monitoring can be imple-
mented, controlled by the “Multi-Master” function of the basic system element. When the moment for a moni-
toring 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 substations is
started. In a minute grid, a monitoring cycle to the next substations is then initiated, until all substations have
been handled by this.
If the number of connected substations is greater than the number of Multi-Master interfaces of a basic
system element in the central station, then it is ensured, that every modem also uses a Multi-Master interface
and has thus been tested.
12.2.5.3 Connection Setup Control via Modem Commands

The connection setup is controlled, depending on the parameterized procedure, either with a state line (tele-
phone number of the substation is stored in the modem) or with messages for the control of the modem (tele-
phone 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 auto-
matically – 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).
AT-Hayes
The Hayes command set (also AT command set) is a command set for the control of modems. It was devel-
oped by the company Hayes, still applicable today as recognized industry standard.

DC8-037-2, Edition 11.2020
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.
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).
V.25bis
According to the interface procedure for the V.25bis connection setup control, the following methods of oper-
ation 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 substations 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 substations is stored in the terminal and is transmitted to the
modem with every connection setup.
→ This method can be implemented in central stations and substations in dial-up traffic.
X.20
X.20 is an ITU-T (CCITT) recommendation for interfaces between data terminal equipment (DTE) and data
transmission equipment (DCE) 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).
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 A8000) is thereby coupled to a data transmission equipment PAD
(Packed Assembler Disassembler).
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 substation 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. Example: 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.

DC8-037-2, Edition 11.2020
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 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 substation with the parameter

Station definition | Main Tel No
• Standby telephone number: per substation with the parameter

Station definition | Secondary phone number
Telephone numbers in the remote terminal unit

In the substations 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
2
3
1
2
3

DC8-037-2, Edition 11.2020
• Mobile telephone number (SMS recipient):

Common settings | Modem GSM-TC35 data box | Mobile phone number (SMSreceiver)
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 V.25bis X.20 X.28
(108.1) (108.2)
Telephone number 0 to 9 0 to 9 0 to 9 0 to 9
Wait until dialing tone detected (contin- : :
uous 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 86 <BLANK> <BLANK> <BLANK> <BLANK> <BLANK>
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 II with <BLANKs>.
→ if the telephone number is now to be changed and additional characters are required for this, then the
<BLANKs> 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 <,>
12.2.5.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 proce-
dure with password and access activation key verification is performed in the private range of IEC
60870-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 initi-
ated 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 LOGINmessage is sent with the password BLOCK. The LOGIN message is acknowledged by the
remote terminal unit.
86 the end of the telephone number is defined with <BLANK> (=space)

DC8-037-2, Edition 11.2020
• 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!
12.2.5.5 Disconnection Control

The dial-up communication protocol uses “disconnect control in the private range of IEC 60870-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 central 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 substation has no more data to transmit
• The substation has no more data to transmit

An existing connection in dial-up traffic is disconnected by the substation in the following cases:
• The substation does not dial the central station due to an incorrectly parameterized telephone number.
• The disconnection has been performed by the central station, but the modem in the substation does not
detect the connection as terminated. 87
• With connection established, the substation is no longer called by the central station within a time that
can be set with the parameter Advanced parameters | Monitoring times | Timeout
station call. 88
The disconnection control is initiated by the central station with the message Hang up dialed line (in
the private range of IEC 60870-5-101) to the substation with the cause of transmission ACTIVATION. As soon
87 the cause for these problems is in most cases a faulty or incorrectly switched DCD state line
88 the cause for these problems is in most cases a faulty or incorrectly switched DCD state line

DC8-037-2, Edition 11.2020
as the substation has received this message, no more data for transmission is received from the basic system
element.
Afterwards the central station sends one more interrogation message for class 2 data in order to still fetch
data that are already prepared for transmission in the substation. After that the connection is disconnected by
the central station.
If the “Multi-Master” function is used in the central station, the central station always terminates the connec-
tion 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 central station the connection time is managed for each substation. 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 substation 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 connec-
tion time counter is to be managed as absolute value or relative value can be set with the parameter
Advanced parameters | Connection time counter.
Maximum connection time

With connection established, the connection is terminated by the central station on expiry of the maximum
connection time at the latest (regardless of “connection time per message type” or if the substation still has
more data to transmit). The maximum connection time is to be set in the central 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
substation has no more data to transmit. The minimum connection time is to be set in the central station with
the parameter Advanced parameters | Monitoring times | Connection time minimum.
NOTE
i 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.
Substation has no more data to transmit

An established connection is terminated prematurely by the central station if no message-type specific
connection time is active and the substation has no more data to transmit. If the substation has no more data
to transmit, station interrogations of the central station are replied to by the substation with short acknowl-
edgements (single character E5H). The connection is disconnected by the central station after a parameterset-
table number of short acknowledgements in succession. The number of short acknowledgements for the
premature connection release is to be set in the central 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 estab-
lished for a settable time, controlled by the central station, even if the substation has no data to transmit
during this time.
This function enables the central station to transmit a command or setpoint value to the substation in the
same connection establishment and to acquire a binary information or measured value change (caused by the
command or setpoint value).

DC8-037-2, Edition 11.2020
With remote parameterization, remote diagnostic and firmware loading of the substation, 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 central station after expiry of the “connection
time per type identification”, if the substation has no more data to transmit.
A connection is terminated by the central station at the latest after expiry of the maximum connection time.
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 (Index) Function Code Connection Designation
Time (default)
Function code A 128 20 s Service command with confirmation
Function code B 129 20 s Service reply
Function code C 130 20 s 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, …).
12.2.6 Communication according to IEC 60870-5-101
With connection established, the data traffic is controlled by the central station.
If the connection setup has been carried out by the substation, the central station still requires the station
address for the cyclic station interrogation with connection established. The link address of the substation
(station address) is determined by the central station with a “Quick-Check Procedure”. For this, the central
station sends a general request to the substation for access request (“Request Status of Link” as broadcast
message). This message is replied to by the substation with a “Status of Link” (with the link address of the
substation).
Either data messages or station interrogation messages are transmitted from the central station. Data from the
substation to the central station can only be transmitted as reply to a station interrogation.
12.2.6.1 Data Acquisition by Polling (Station Interrogation)

The transmission of the data from the substation to the central station with established connection takes place
by means of station-selective station interrogations (interrogation procedure, polling), controlled by the
central station; i.e., changed data is stored in the substation and transmitted to the central station with the
interrogation of this substation. The interrogation procedure of the central station ensures, that the substation
to which the connection has been established is interrogated permanently as long as the connection exists.
The substation 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 central 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.

DC8-037-2, Edition 11.2020
In every substation, 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
central station and in the substation.
In dial-up traffic with connection established, data and system messages are always transmitted selectively
and acknowledged from the central station to the substation during the running interrogation cycle.
Data to all substations 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 central station and no station
interrogation takes place. In addition, messages to be sent are not transmitted from the central station to the
substations, 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.
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 Octets 89
Element
Address field of the link (number) Number of octets for the address --- 1
field of the link layer
Cause of transmission (COT) Number of octets for cause of trans- BSE 2
mission
Common address of ASDU (CASDU) Number of octets for common BSE 2
address of the ASDU
Information object address (IOA) Number of octets for the address of BSE 3
the information object
Acknowledgement IEC 60870-5-2 Acknowledgement on IEC 60870-5-2 --- 90
layer Single character or short
message (ACK)
Maximum message length BSE
Time tag Number of octets for time tag BSE
Legend:
PRE ........... Protocol element
BSE ........... Basic system element
Continuous Interrogation of a Substation

The “Continuous interrogation of a substation in dial-up traffic” is always performed with connection estab-
lished. The central station thereby carries out a permanent station interrogation for the duration of the
connection only to that substation 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 (example: command, setpoint value)
the central station can quickly fetch changed data from the substation (example: measured values after
command or setpoint value). The continuous interrogation is terminated after expiry of the connection time.
During “continuous interrogation of one substation” no data ate transmitted to other substations. 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 substation can be determined independent of the parameter
89 the number of octets are fixed by the dial-up protocol and may not be changed!
90 as “acknowledgement to IEC 60870-5-2 layer” only the single character is used for dial-up traffic

DC8-037-2, Edition 11.2020
setting. For spontaneous messages to the substation, the connection time is determined by the connection
time per message type. The maximum connection time is however always limited by the parameter setting.
Acknowledgement Procedure
With connection established, all data messages transmitted to a substation 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 substation is flagged as faulty. The connection remains established – further
messages are transmitted without retries.
The connection is terminated by the central station at the latest after expiry of the maximum connection time.
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 substations must be taken into consideration.
For the automatic determination of the expected acknowledgement time, the times of the selected transmis-
sion facility in the substation are also taken into consideration by the DIAMA0 protocol firmware.
The number of retries is to be set in the central 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).
In the central 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 substation to the central station is transmitted as single character (E5).
Failure Monitoring in the Central Station

The monitoring of the substation by the active central 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 substations are monitored by the cyclic or time-controlled monitoring cycle. In the monitoring
cycle of the central station, a connection setup is performed 1 x to every parameterized substation. Through
the monitoring cycle, failed substations are detected by the central station and signaled as failed.
With connection established, a substation is reported as failed by the central station after expiry of the number
of retries. Retries to a substation are thereby always sent in succession immediately after expiry of the
expected acknowledgement time i.e. the connection is not disconnected and no other substations are interro-
gated during a running retry handling. For failed substations, a communication fault is only then reported, if
this is parameterized accordingly in the parameter Stationsdefinition | Station failure.
With connection established, the failure of substations is thus detected by the central station during the
normal interrogation cycle or the monitoring cycle. Failed substations continue to be interrogated by the
central station in the monitoring cycle. Redials to failed substations can be deactivated with the parameter
Connection setup | 1st dialling attempt with faulty station.
For failed substations, 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.
Data from the central station to the substation which could not be transmitted during the redials are
discarded.
Failure Monitoring in the substation

In the substation, with connection established, the monitoring of the central station is carried out by the func-
tion “Monitoring for cyclic message reception”.
If there are no user data to be transmitted, if necessary the substation can monitor the central station with the
cyclic or time-controlled monitoring cycle. In the monitoring cycle of the substation, a connection setup is
performed 1 x to the central station. Through the monitoring cycle, a failed central station is detected by the
substation and signaled as failed.

DC8-037-2, Edition 11.2020
The monitoring time for cyclic message reception is to be set in the substation with the parameter Advanced
parameters | Monitoring times | Timeout station call. This monitoring time is retriggered in
the substation by station-selective call messages or station-selective data messages. If the monitoring time
elapses, the connection is terminated by the substation.
With failed interface, data to be transmitted are stored in the data storage on the basic system element (BSE)
of the substation until these are deleted by the dwell time monitoring or can be transmitted to the central
station.
12.2.6.2 Station Initialization

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.
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 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 trans-
mitted to master station
End of Initialization
The end of initialization according to IEC 60870-5-101 is not supported by this protocol element!
12.2.6.3 Acquisition of Events (transmission of data ready to be sent)

Data that are to be transmitted from the substation to the central station are stored on the basic system
element (BSE) in the substation until transmission. Further information resides in section 12.2.6.1 Data
Acquisition by Polling (Station Interrogation).
In dial-up traffic, the substation itself can establish a connection to the central station and in this way ensure a
fast transmission of the data. Data that are not to be transmitted immediately, are stored in the substation 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 substation as long as no connection is established. This func-
tion can be set in the substation with the parameter Advanced parameters | Behavior if connec-
tion is not established.
Message from the Substation to the Central Station

With connection established, messages from the substation to the central station are only transmitted with
station interrogation. A quick-check procedure for speeding up the transmission of data is not implemented.
12.2.6.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.
In dial-up traffic, the general interrogation of remote terminal units must be carried out stationselective by the
master station and due to the connection setup required to every selective remote terminal unit according to

DC8-037-2, Edition 11.2020
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 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.
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 param-
eter Connection setup | Send online GI with active connection setup. The general inter-
rogation command is thereby generated by the protocol element of the master station itself and transmitted
to the remote terminal unit.
12.2.6.5 Clock Synchronization

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 stationselective 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 (regard-
less whether spontaneous or cyclic, initiated by the master or remote terminal unit) – with connection estab-
lished 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 moni-
toring 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 [per hour] 91 Max. Inaccuracy [per day] 92
10-5 360 ms 8.6 s
10-4 3.6 s 86.4 s
If the accuracy of the remote synchronization is insufficient, a local time signal receiver must be used in the
91 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
92 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

DC8-037-2, Edition 11.2020
12.2.6.6 Command Transmission
Message from the Central Station selectively to a Substation

Station-selective data messages in command direction are always inserted into the running interrogation
procedure (station interrogation) by the central station with high priority after termination of the data trans-
mission in progress. Data to be sent from the basic system element (BSE) are always prioritized 1:1 with
station interrogations.
Demand
If the reaction from the substation to a transmitted message is to be acquired quickly by the central station,
the connection – controlled by the central station – can remain established for a settable time, even if the
substation has no data to transmit during this time.
This function enables the central station to transmit a command or setpoint value to the substation 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 central station after expiry of the “connection
time per type identification”, if the substation has no more data to transmit.
A connection is terminated by the central 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 | *.
Control Location
If the function “control location” is activated, commands from the protocol element of the central station are
only then transmitted to the addressed substation 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 loca-
tion) 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 central station and is discarded. For these commands a negative confirmation of acti-
vation (ACTCON-) is sent back immediately by the protocol element to the originator address.
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 the control loca-
tions 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.

DC8-037-2, Edition 11.2020
Set Control Location

The control location is set on the PRE with a PRE-control message (Function = Set control location) either glob-
ally 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 II 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 Not defined
1 to 127 Remote command
128 to 255 Local command
NOTE
i 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 loca-
tions 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, 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 indi-
vidually or globally for all stations and all control locations.
No confirmation (ACTCON) and no termination (ACTTERM) of the command initiation is created for the infor-
mation object “Control location”.
With each startup of the protocol element, all enabled control locations are reset. The control locations are to
be set again after every startup of the protocol element.
Message from the Central Station to all Substations (Unacknowledged)

In dial-up traffic, unacknowledged messages from the central station to all substations are not supported!
Since a BROADCAST-transmission is not possible in dial-up traffic, messages to all must always be transmitted
selectively to all substations.
12.2.6.7 Transmission of Integrated Totals

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 communications
12.2.6.8 Acquisition of Transmission Delay

In dial-up traffic, the protocol element of the remote terminal unit does not support “acquisition of the trans-
mission delay” and the correction of the time resulting from this for clock synchronization according to IEC
60870-5.

DC8-037-2, Edition 11.2020
The protocol element of the master station uses a SICAM A8000 specific method for the “acquisition of trans-
mission 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 selec-
tively 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.
12.2.7 SMS Messages
The remote terminal unit in dial-up traffic can also transmit SMS messages (Short Message Service) to a para-
meterized telephone number (mobile telephone) with the GSM modems Siemens TC35 and Cinterion MC52iT.
For the transmission of SMS messages, no connection is established to the central 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 GSMTC35 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 parameter-
ized. This is always sent together with the transmission of an SMS message.
12.2.8 Coordination of Several Masters in Multi-Master Mode
In the so-called Multi-Master mode – provided there are several dial-up modems available in the central
station and just as many SM-25xx/DIAMxx protocol elements – more than one connection can be established
simultaneously with different substations, whereby no fixed assignment of the substations to one specific
central station 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 must be parameterized identically!
In Multi-Master mode, the connection time counters in the protocol element return information are only trans-
ferred from the protocol element of the master station as relative values (connection time of the last connec-
tion).
In Multi-Master mode, no standby number is supported for the connected remote terminal units!

DC8-037-2, Edition 11.2020
12.2.9 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 tele-
phone 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.
12.2.10 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 substation, also using different communication protocols.

DC8-037-2, Edition 11.2020
12.2.11 Standby Transmission Line via Dial up Traffic
The data transmission between central station and the substations during fault-free operation is carried out
over the main transmission line in point-to-point or multi-point traffic or over LAN. Every substation 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
substations 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):
[dw_DIAMyy_Ersatzwegbetrieb_ueber_WV, 2, en_US]
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 time-
outs 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 auto-
matic switchover will be done for activating the main transmission line again.

DC8-037-2, Edition 11.2020
• Parameter Stand-by transm. line switchover mode must be set to stand-by transmis-
sion line with 2 Master (Mode 5) in the substation.
• If the central 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 central station (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 substations are interrogated by the central station predominantly on the main transmission line. If the
protocol element of the central station detects a substation 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 substation is detected on the basic system element by means of special keep-alive messages
transmitted cyclic by the substation.
In the central station (SICAM RTUs) standby transmission line operation over dial-up traffic is only activated to
a substation 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 substation over the public telephone network (PSTN). If the
substation can be reached again on the main transmission line during this delay time, the standby transmis-
sion line operation is not activated. The connection to the substation over the standby transmission line is only
established, if there is data to be transmitted. The connection time is limited by the parameter for the limita-
tion of the connection time.
When the substation can be reached again on the main transmission line, the standby transmission line opera-
tion over dial-up traffic to this substation 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 substations continue to be also interrogated on the main transmission line. If a failed substation 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 central station.
12.2.12 Optimized Parameters for Selected Transmission 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 | Inter-
face 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
i After modem exchange (or for some modems also after switching on the supply voltage again) it is advis-
able 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.

DC8-037-2, Edition 11.2020
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, example: 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 para-
meterized, 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 parame-
terized 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 para-
meterized 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 transmis-
sion 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 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 interrup-
tion 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.
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 tele-
phone and the PIN-Code request deactivated. This setting is stored on the SIMcard.
→ In the protocol element, the PIN-Code request is deactivated by setting the parameterI Common
settings | Modem GSM-TC35 data box | GSM M20 Box - pincode to the value "10000".

DC8-037-2, Edition 11.2020
• 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 parame-
ters 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 IDW90 (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 IDW90 (ISDN)”
• B-channel protocol (X.75, V.110)

With ISDN, information for the connection setup, information about service detection etc. are trans-
mitted on the D-channel. On the B-channel, the conversation, fax or data is transmitted.
When using the modem “Westermo IDW90 (ISDN)” 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 1200 to 19200 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 IDW90 (ISDN)”, the transmission protocol to be used can
be set with the parameter verwendende Common settings | Modem Westermo IDW90 (ISDN) |
B-Channel protocol.
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 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 | Inter-
face 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).

DC8-037-2, Edition 11.2020
When using the freely definable transmission facility, the following parameters can be set:
• 5 V supply (DSR)
If necessary the voltage supply of the transmission facility (only 5 V) – insofar as this is sufficient – can
take place over the state line DSR. The enabling of the voltage supply is 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 para-
meterized 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 defin-
able | Data mode baud rate.
• 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 param-
eter Common settings | Modem free definable | Data mode parity and the parameter
Common settings | Modem free definable | Data mode stop bits.

DC8-037-2, Edition 11.2020
• Data mode "ASCII transmission"

Some transmission facilities do not support the transmission of data with 8 data bits. With these trans-
mission 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 poly-
nomial. This additional security can be activated with the parameter Common settings | Modem
free definable | Data mode CRCgeneratorpolynom.
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 defin-
able | Assessment of modem inform. (data mode). Only through this function is an unam-
biguous detection of command mode and data transmission mode possible.
• 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 termi-
nated 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.

DC8-037-2, Edition 11.2020
• 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 disconnec-
tion 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 disconnec-
tion of the connection is controlled over state lines.
Parameters for transmission facilities
Parameter Transmission Facility

Westermo Westermo Coherent Siemens Cinterion
* TD-32 * TDW-33 * Eurocom- * M20-Box * MC52iT
* TDW-33 * TD-35 24 Siemens
* TD-36 * TD-36 * TC35
* TC35i
5V Supply (DSR) NO NO JA NO NO
Automatic call acceptance by modem NO NO NO NO NO
Command mode baud rate 9600 9600 1200 9600 9600
Command mode data bits 8 8 8 8 8
Command mode end character <CR> <CR> <CR> <CR> <CR>
<LF> <LF> <LF> <LF> <LF>
Command Mode Parity No No No No No
Command mode stop bits 1 1 1 1 1
Command mode message end 100 Bit 100 Bit 100 Bit 100 Bit 100 Bit
Use DCD with AT-Hayes YES YES YES YES YES
Data mode ASCII transmission NO NO NO NO NO
Data mode baud rate 9600 9600 1200 9600 9600
Data mode CRC generator polynomial YES YES YES YES YES
Data mode data bits 8 8 8 8 8
Data mode end character if ASCII <CR> <CR> <CR> <CR> <CR>
Data Mode parity No No No No No
Data mode stop bits 1 1 1 1 1
Evaluate modem messages (data mode) NO NO NO NO NO
Call acceptance with call acceptance delay YES YES YES YES YES
Disconnection via escape sequence Do not send Do not send Do not send Do not send Do not send
(ATHayes)
Disconnection via command NO NO NO NO NO
Connection setup (procedure) AT-Hayes AT-Hayes AT-Hayes AT-Hayes AT-Hayes
Connection setup V25.bis_command CRI,<C> CRI,<C> CRI,<C> CRI,<C> CRI,<C>

DC8-037-2, Edition 11.2020

Westermo Westermo Kabelmetall Kabelmetall Westermo
* ID90 * ID90V.90 LGM/H 64K LGM/H 64K * GD01
* IDW90 "Direkt- "Normal- * GDW-11
Mode" Mode"
5V Supply (DSR) NO NO NO NO NO
Automatic call acceptance by modem NO NO NO NO NO
Command mode baud rate 9600 9600 19200 19200 9600
Command mode data bits 8 8 8 8 8
Command mode end character <CR> <CR> <CR> <CR> <CR>
<LF> <LF> <LF>
Command Mode Parity No No No No No
Command mode stop bits 1 1 1 1 1
Command mode message end 100 Bit 100 Bit 100 Bit 100 Bit 100 Bit
Use DCD with AT-Hayes YES YES YES YES YES
Data mode ASCII transmission NO NO NO NO NO
Data mode baud rate 9600 9600 19200 19200 9600
Data mode CRC generator polynomial YES YES YES YES YES
Data mode data bits 8 8 8 8 8
Data mode end character if ASCII <CR> <CR> <CR> <CR> <CR>
Data Mode parity No No Even Even No
Data mode stop bits 1 1 1 1 1
Evaluate modem messages (data mode) NO NO NO NO NO
Call acceptance with call acceptance delay YES YES YES YES YES
Disconnection via escape sequence Do not send Do not send Do not send Do not send Do not send
(ATHayes)
Disconnection via command NO NO NO NO NO
Connection setup (procedure) AT-Hayes AT-Hayes AT-Hayes AT-Hayes AT-Hayes
Connection setup V25.bis_command CRI,<C> CRI,<C> CRI,<C> CRI,<C> CRI,<C>

Freely SIMOCO SEPURA INSYS GSM INSYS PSTN
definable SRM1000 SRH3500 56K
5V Supply (DSR) NO NO
Automatic call acceptance by modem NO NO NO
Command mode baud rate 38400 38400
Command mode data bits 8 8 8
Command mode end character <CR> <CR> <CR>
<LF> <LF>
Command Mode Parity No No No
Command mode stop bits 1 1 1
Command mode message end 100 Bit 100 Bit 100 Bit
Use DCD with AT-Hayes YES NO YES
Data mode ASCII transmission NO YES NO
Data mode baud rate 38400 38400
Data mode CRC generator polynomial NO YES NO
Data mode data bits 8 8 8

DC8-037-2, Edition 11.2020

Data mode end character if ASCII <CR> <CR> <CR>
<LF> <LF> <LF>
Data Mode parity No No No
Data mode stop bits 1 1 1
Evaluate modem messages (data mode) NO YES NO
Call acceptance with call acceptance delay YES YES YES
Disconnection via escape sequence Do not send send send
(ATHayes)
Disconnection via command NO YES YES
Connection setup (procedure) AT-Hayes AT-Hayes AT-Hayes
"ETSI"
Connection setup V25.bis_command CRI,<C> CRI,<C> CRI,<C>
Time settings for “freely definable transmission facility”
NOTE
i 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.
Parameter Default Setting Note
Timeout 2 100
Timeout 3 5
Timeout 4 600
Timeout 5 300
Timeout 6 50
Timeout 7 Active 10
Timeout 7 Passive 10
Timeout 9 5
Timeout A 300
Timeout B 300
Timeout D 5
Timeout E 50
Timeout F 2
Timeout 10 2
Timeout 12 30
Timeout 13 100
Timeout 17 30
Timeout 18 0
Timeout 19 30
Timeout 1C 200
Timeout 1D 10
Timeout 1E 10
Timeout 1F 10
Timeout 22 0
Timeout 24 50

DC8-037-2, Edition 11.2020
Parameter Default Setting Note

Timeout 26 200
Timeout 27 200
Timeout 28 2
Timeout 2B 20
Timeout 2C 30
12.2.12.1 Supported Combinations for Dial-Up Modems
[sc_supported_combinations_dial_up_modems, 2, en_US]
[sc_supported_combinations_dial_up_modems1, 2, en_US]

DC8-037-2, Edition 11.2020
[cs_legend_supported_combinations _dial_up_modems, 2, en_US]
12.2.12.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. Example:
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 option-
ally 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 Interface modem = USER defined Modem, the ASCII mode can be activated with
the parameter Data Mode ASCII transmission.
NOTE
i 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 itself is transmitted with
message formats according to IEC 60870-5-101 – in ASCII mode.

DC8-037-2, Edition 11.2020
[dw_DIAxyy_ASCII_Mode, 1, en_US]
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
i CRC-CCITT consists of 4 characters in ASCII mode.
12.2.12.3 CRC Generator Polynomial

With connection established the 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 Interface modem = USER defined
Modem) can be deactivated with the parameter Data Mode CRC generatorpolynom.
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.
[sc_DIAxyy_CRC_CCITT, 1, en_US]
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.
12.2.13 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, substation) 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”: central station and substa-
tion 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 substations cyclic. If necessary, every substation
can also be parameterized, so that it monitors its central station.

DC8-037-2, Edition 11.2020
When a connection is established – spontaneous or cyclic – all data ready to be transmitted is transmitted in
each case – regardless whether it is selected for spontaneous transmission or not.
12.2.14 Having a Telephone Set Connected in Parallel
A normal telephone call can be made over a telephone connection which is used with a modem for the trans-
mission 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.
When 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.
12.2.15 Functions for the Support of Redundant Communication Routes
In the substation, no functions for the support of redundant communications routes are supported!
To increase the availability central stations can be designed redundant.
12.2.15.1 Redundancy Mode PRE Redundancy (applies only for Remote Station = Central Station)
In the central station only the redundancy mode PRE Redundancy is supported and does not need to be set
with a parameter. The switchover of the redundancy state takes place system-internal through redundancy
control messages.
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.
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:
• Interface “tristate” – only listening mode
• Interface “active” – only listening mode

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
(example: with locally separated redundant masters).
In redundant central stations that are not active (passive central station), no failure of the interface is moni-
tored and also no station-selective failure of substations.
Station-specific pending faults are reset in a redundant STANDBY central station, if a faultfree message from
the respective station is “listened”.
For configurations with locally separated redundant central 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 substation, commonly only one telephone number of the central station is stored. If
the central station on the main connection does not accept the call within a defined time, the call of the
substation is transferred to another connection (to the STANDBY master) by the telephone number stepping.
12.2.16 Message Conversion
Data in transmit direction is transferred from the basic system element to the protocol element in the SICAM
A8000 internal IEC 60870-5-101-/104 format, and 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 is converted by the protocol element from IEC 60870-5-101 format on the transmis-
sion line to a SICAM A8000 internal IEC 60870-5-101/104 format and transferred to the basic system element.

DC8-037-2, Edition 11.2020
12.2.16.1 Blocking
For the optimum utilization of the transmission paths, for the data transmission with IEC 60870-5-101 proto-
cols 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 A8000 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.
12.2.16.2 Class 1, 2 Data

In dial-up traffic, data from the remote terminal unit is always transmitted to the master station as class 2
data.
SICAM A8000 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.
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 this data changes or whether this data is only to be
transmitted during the next connection setup.

This function is used for the user-specific influencing of the functions of the protocol elements.

The Protocol Element Control enables:
• Applicational control of the station interrogation
• Setting control location
• Testing the reachability of stations
• Suppression of errors with intentionally switched-off stations (Station Service)

The Protocol Element Return Information enables:
• States of certain state lines to be used as process information
• Obtaining of information on station interrogation
• Obtaining of information on the route state/failure of main/standby transmission line
• Obtaining of information on the station status/failure

DC8-037-2, Edition 11.2020
Block Diagram
12.2.17.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 A8000 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 A8000 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.
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 to 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.
Possible Master Station Functions Single-Master (or PST direct to PRE)

Protocol element control messages with PRE_(PST) = 128 to 131 are distributed further by the basic system
element directly to the respective selective protocol element.

DC8-037-2, Edition 11.2020
Function PST Detail Routing Note

SF Station Z-Par FI
Z-Par = 0, 65535: no minimum
0 to connection time
Start monitoring cycle (initiate) 0 125
65535 Z-Par = 1 to 65534: minimum connec-
tion time (n ⋅ 100 ms)
Connection setup to remote 0 to connection time
1 0 to 99
terminal unit 65535 Z-Par = 1 to 65534: minimum connec-
tion time (n ⋅ 100 ms)
Connection release 2 0 to 99, -
125
Reset connection time counter 0 to 99, The function of the counter is defined
3 -
(or connection setup counter) 125 with a parameter.
A connection setup to the remote
0 to 99, terminal unit is carried out to the main
Use main telephone number first 4 -
125 telephone number first (see Mode-4,
connection setup procedure)
A connection setup to the remote
Use standby telephone number 0 to 99, terminal unit is carried out to the
5 -
first 125 standby telephone number first (see
Mode-4, connection setup procedure)
0 to 99,
Terminate call attempts (abort) 6 -
125
0 to 99 only parameterized RTUs can be added
to the station polling
Add station to station polling 128 -
⇒ otherwise error “faulty PST-control
message”
0 to 99 only parameterized RTUs can be
removed from the station polling
⇒ otherwise error “faulty PST-control
Remove station from station
129 0, 1 message”
polling
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 to the protocol element as
Send (general) interrogation
240 - system message and not using PRE-
command
control message!
CASDU = BROADCAST
125 SCS = <ON>: set control location (HKA)
65535
(all stations)
SCS = <OFF>: reset control location
65535
(HKA) (all stations)
Set control location 242
0 to 99 SCS = <ON>: set control location (HKA)
65535
(selective station)
SCS = <OFF>: reset control location
65535
(HKA) (selective station)
244 CASDU system message and not using PRE-
command
control message!
CASDU = selective

DC8-037-2, Edition 11.2020
Set control location:
• 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 Z-Par = 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
Possible Master Station Functions Multi-Master (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 FI
Connection setup to remote 0 to connection time
1 0 to 99
terminal unit 65535 Z-Par = 1 bis 65534: minimum connec-
tion time (n ⋅ 100 ms) 93
Connection release 2 0 to 99 - Is only transferred by the multimaster
function if a connection is established
to this station
Terminate call attempts (abort) 6 0 to 99 -
Activate standby transmission 0 to 99 Z-Par = 0, 65535: no minimum
line and connection setup to connection time
0 to
remote terminal unit over acti- 10 Z-Par = 1 to 65534: minimum connec-
65535
vated standby transmission line tion time (n ⋅ 100 ms)
94
Connection release to remote 0 to 99 Is only transferred by the multimaster

terminal unit and deactivate 11 - function if a connection is established
standby transmission line 94 to this station
93 during connection established the minimum connection time will be always retriggered with this PST control message; the connec-
tion will be released latest after elapsed maximum connection time
94 this PRE control messages are used by BSE for integrated function “standby transmission line operation” only (other usage is not
supported)

DC8-037-2, Edition 11.2020

SF Station Z-Par FI
0 to 99 Z-Par = 0, 65535: no minimum
connection time
Z-Par = 1 to 65534: minimum connec-
Connection setup to remote 0 to
12 tion time (n ⋅100 ms) 93
terminal unit via “red telephone” 65535
Wwith this PST control message a USER
controlled monitoring of the modem
for the “red telephone” can be realized.
system message and not using PRE-
Send (general) interrogation control message!
240 -
command CASDU = BROADCAST
The (general) interrogation command
will be forced to transmit by BSE for
each individual station.
Legend:
SF ... Control function_(PRE)
Station ... Station number
0 to 99 = selective station 0 to 99 of the selected protocol element
125 = all parameterized stations of the selected protocol element
Z-Par ... additional parameter_(PRE)
Fl ... edge
SCS ... single command state
HKA ... originator address (HKA) = 0 to 255
Possible Functions in the Substation

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

DC8-037-2, Edition 11.2020

SF Station Z-Par FI
240 - system message and not using PRE-
command
control message!
CASDU = BROADCAST
command
control message!
CASDU = selective
Legend:
Station ... Station number (not used = 255)
Z-Par ... Additional parameter_(PRE)
12.2.17.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 state lines
• Status of the stations
• Protocol-specific return information (dependent on the protocol element used)

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 A8000 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 Central Station Return Information Single-Master
Return information func- Parameter Note

tion_(PRE) Station
Status RTS 255 Status DTR 95
0 = status line inactive
1 = status line active
Status CTS 255 Status CTS 95
95 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 100 ms grid
⇒ State line changes shorter than 100 ms are not guaranteed to be transmitted!

DC8-037-2, Edition 11.2020

tion_(PRE) Station
Status DCD 255 Status DCD 95
Status DTR 255 Status DTR 95
Status DSR 255 Status DSR 95
Station status 0 to 99 1 = Station enabled for call cycle
Station failure 0 to 99 1 = Station failed
Protocol-specific return infor- 0 to 99 Connection setup stored (flagged in advance)
mation 0
Protocol-specific return infor- 0 to 99 Connection setup in progress
mation 1
Protocol-specific return infor- 0 to 99 Connection established
mation 2
Protocol-specific return infor- 0 to 99 Connection setup not possible 96
mation 3 (number of redials elapsed without success)
Protocol-specific return infor- 0 to 99 Connection setup executed successfully 96
mation 4
Protocol-specific return infor- 0 to 99 Dialing pause
mation 5 (after an unsuccessful connection setup attempt, a dialing
pause is performed, afterwards a new connection setup is
initiated)
Protocol-specific return infor- 0 to 99 Connection terminated 96
mation 6
Protocol-specific return infor- 0 to 99 Connection setup not possible
mation 7 (Station not enabled on protocol element) 96
Protocol-specific return infor- 0 to 99 The telephone line has been unplugged
mation 9 Status of Layer 1 interrogation
(only applicable for Kabelmetall ISDN terminal adapter)
Protocol-specific return infor- 255 It’s ringing (RING)
mation 14 With redundant configurations this information can be used
for redundancy switchover
Protocol-specific return value 0 to 99 The return value can be selected via parameter.
• connection time counter (connection time in seconds)

(for active/passive connection setup)
Format of the return value: IEEE 754 Floating Point
96 this information is transmitted as transient information; transmit general interrogation command to basic system element (ON/OFF-
status of the information is transmitted immediately in succession)

DC8-037-2, Edition 11.2020
Possible Central Station Return Information Multi-Master

tion_(PRE) Station
Station status 0 to 99 1 = station enabled for call cycle
Station failure 0 to 99 1 = station failed
Protocol-specific return infor- 0 to 99 Connection setup in progress
mation 1
Protocol-specific return infor- 0 to 99 Connection established
mation 2
Protocol-specific return infor- 0 to 99 Connection setup not possible 96
Protocol-specific return infor- 0 to 99 Connection terminated 96
mation 6
Protocol-specific return infor- 255 It’s ringing (RING)
mation 14 With redundant configurations this information can be used
for redundancy switchover
Protocol-specific return infor- 255 PRE0 assigned
mation 0 (Multimaster function cannot perform any connection setup
over this PRE)
over this PRE)
over this PRE)
mation Rückmeldung 3 (Multimaster function cannot perform any connection setup
over this PRE)
Protocol-specific return infor- 255 All PRE's assigned
over these PRE's)
Legend:

DC8-037-2, Edition 11.2020
Station Station number

0 to 99 Station 0 to 99 of the selected protocol element
125 Station number not used
PRE Protocol element
Possible Substation Return Information

tion_(PRE) Station
Station status 255 1 = station enabled for call cycle
Station failure 255 1 = central station failed
Protocol-specific return infor- 255 Connection setup stored (flagged in advance)
mation 0
Protocol-specific return infor- 255 Connection setup in progress
mation 1
Protocol-specific return infor- 255 Connection established
mation 2
Protocol-specific return infor- 255 Connection setup not possible 96
Protocol-specific return infor- 255 Connection setup executed successfully 96
mation 4
Protocol-specific return infor- 255 Dialing pause
mation 5 (after an unsuccessful connection setup attempt, a dialing
pause is performed; afterwards a new connection setup is
initiated)
Protocol-specific return infor- 255 Connection terminated 96
mation 6
Protocol-specific return infor- 255 Connection setup not possible
mation 7 (Station not enabled on protocol element) 96
Protocol-specific return infor- 255 The telephone line has been unplugged
mation 9 Status of Layer 1 interrogation
(only applicable for Kabelmetall ISDN terminal adapter)

DC8-037-2, Edition 11.2020

tion_(PRE) Station
Protocol-specific return infor- 255 The return information value can be selected via parameter.
mation value
• retries in % (of the last full hour)
IEEE 754 floating point format will be used for return informa-
tion value
Legend:
255 = Station number not used

DC8-037-2, Edition 11.2020
12.3 IEC 60870-5-101 (Point-to-Point Traffic)
12.3.1 Introduction
The IEC 60870-5-101 protocol (point-to-point) is a standardized serial transmission protocol for communica-
tion with remote stations with point-to-point traffic.
For CP-8000/CP-802x, the following protocol firmware for IEC60870-5-101 (point-to-point) is available:
Firmware System Standard and function
BPPT0 CP-8000 IEC 60870-5-101 Balanced (point-to-point traffic)
CP-802x
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.
[BPPxx_config, 1, en_US]
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 deter-
mined through the initiation of the data transmission.
For point-to-point traffic a "full duplex" transmission medium is required.
12.3.2 Functions
Communication of a central station with a substation.
• Serial communication protocol according to IEC60870-5-101
• Balanced transmission (point-to-point traffic)

– Network configuration
– Point-to-point configuration
– Multiple point-to-point configuration (each point-to-point configuration requires a separate
interface)
– Max. connections: 1
– System or device (application function)
– “Controlled Station”
– “Controlling Station”

DC8-037-2, Edition 11.2020
• Physical layer/data flow control

– Unbalanced interface according to V.24/V.28
– Data transmission route (full duplex)
– Byte frame (8E1)
– Data flow control bit used in receive direction
• Interoperability
– IEC60870-5-101 Ed.1
• Interoperability according to 12.3.10 Interoperability IEC 60870-5-101 (BPP)
• Recording events (transferring data ready for sending)
– Non-Interruptible General Interrogation
• Clock synchronization according to IEC 60870-5-101

– Time synchronization with <TI:=103> Time synchronization command
– Acquisition of transmission delay (primary station) used for correction of time synchronization with
<TI:=106>
– Acquisition of transmission delay (secondary station) used for correction of time synchronization
with <TI:=106>
• Accuracy ±20 ms
• Command transmission
– Setting control location
• Metered value transmission
• File transfer
• Optimized parameters for selected transfer directions

– Freely definable parameters for transmission facility
• Protocol Element Control and Return Information

– Protocol element control telegrams
– Send (general) interrogation command to all
– Send (general) interrogation command to selective CASDU
– Send (general) interrogation command for GI image to own master module
– Data filter in transmit direction on/off
– Data filter in receive direction on/off
– Activate, deactivate interface
– Activate, deactivate interface + protocol functions
– Protocol element feedback telegrams
– Protocol-specific feedback 0 Interface activated/deactivated
– Protocol-specific feedback 1 Interface + protocol function activated/deacti-
vated

DC8-037-2, Edition 11.2020
• Special functions
– Daylight saving time bit (SU) = 0 for all telegrams in sending direction (in time marker)
– Day of the week (DOW) = 0 for all telegrams in transmit direction (in time marker)
– Originator address = 0 for all messages in transmit direction
– Convert general interrogation command in receive direction to broadcast
– Send ACTCON for time synchronization command
– Emulate ACTCON +/-
– Emulate ACTCON for commands with control telegram
– Compatibility for TCS100
– Special functions for DBAG project
– Breaker delay in transmit direction
(DBAG-specific special message format <TI=150>)
– Sending the originator address with adjustable value
– Transparent mode (tunneling, container mode)
– Special functions for RWE project
– NT-Bit, IV-Bit according to RWE Requirements
• Engineering
– SICAM TOOLBOX II
– Remote maintenance with SICAM TOOLBOX II via serial interface
12.3.3 Modes of Operation
The operating mode of the interface is determined by parameters of the protocol element and optional equip-
ment.
optional DTE
Unbalanced interchange circuit (V.24/V.28) X2 RXD, TXD, CTS 97, RTS, DCD, DTR,
RS-232 asynchronous DSR/VCC, GND
Balanced interface (V.11) RS-422 (4 wire) asyn- X3 TXD+, TXD-, RXD+, RXD- (4-wire)
chronous
Balanced interface (V.11) RS-422 (4 wire) asyn- X2 → CM-0829 98 RXD, TXD, CTS, RTS, DCD, DTR, DSR/
chronous VCC, GND (to CM-0829)
Optical interface (multimode fibre optic) ring X2 → CM-0821 RXD, TXD, CTS, RTS, DCD, DTR, DSR/
VCC, GND (to CM-0821)
Unbalanced interchange circuit (V.24/V.28) X699 RXD, TXD, CTS, RTS, DCD, DTR, DSR,
RS-232 asynchronous GND
Balanced interface (V.11) RS-422 (4 wire) asyn- X699 TXD+, TXD-, RXD+, RXD- (4-wire)
chronous

98 in case of transmission rates > 9600 bit/s converter PHOENIX PSM-ME-RS232/RS485-P is required: Interface signals D(A), D(B), T(A),
T(B), GND (RS-422)
99 only CP-8022 (switchable mode via parameter)

DC8-037-2, Edition 11.2020
NOTE
i Details about realization of various operation modes are given in the manual SICAM RTUs Platforms -
For the stations to communicate with each other, suitable transmission facilities and/or network components
may be needed in addition.
Own station
System System element Protocol Element Remarks

SICAM A8000 CP-8000/CPC80 BPPT0
CP-802x/CPC80
Remote station

SICAM A8000 Series CP-8000/CPC80 BPPT0
CP-802x/CPC80
CP-8050/CPCI85 BPPI0
SICAM AK 3 CP-2016/CPCX26 SM-2551/BPPA0
CP-2019/PCCX26 SM-0551/BPPA0
Legacy systems CP-20xx SM-2551/BPPA0
(SICAM AK CP-60xx SM-0551/BPPA0
SICAM TM CP-50xx BPPT0
SICAM BC
SICAM EMIC)
Siemens devices – – according to
12.3.10 Interoperability
IEC 60870-5-101 (BPP)
Third-party system – – according to
IEC 60870-5-101 (BPP)
12.3.5.1 Basic Configuration

For the communication with a remote station in point-to-point traffic according to IEC 60870-5-101 the
following basic settings are required:
• Link layer address
• Number of octets for the link layer address
• Station type
For this purpose, the Advanced parameters | IEC60870-5-101 | Link layer address parameter
and the Advanced parameters | IEC60870-5-101 | Address field in the link layer
(quantity) parameter must be set according to the defined specification in the master/substation. The

DC8-037-2, Edition 11.2020
address of the link layer must be adjusted identically at both stations (master/substation) for communication
with a remote partner as part of point-to-point traffic!
Setting the General settings | Station type parameter is also required for communication with a
remote partner as part of point-to-point traffic according to IEC 60870-5-101. In this process, either “Station A”
or “Station B” must be assigned to a station.
“Own station” station type “Remote partner” station type
Station A Station B
Station B Station A
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 parameter can be found in the interoperability list (master station and
remote station must be parametrized identically).
The following table provides an overview of which IEC-parameters must be configured at which system
elements.
IEC 60870-5-101 Parameter Description System element
Link address byte number Number of octets for the link layer PRE
address field
Cause of transmission (COT) Number of octets for cause of transmis- BSE
sion
Common address of ASDU Number of octets for common address BSE
(CASDU) of the ASDU
Information object address Number of octets for the address of the BSE
(IOA) information object
Acknowledgment on IEC Single character or short message (ACK) PRE
60870-5-2 layer
Maximum telegram length BSE
Time_marker Number of octets for time marker BSE
Legend:
PRE ... Protocol element
BSE ... Base system element
12.3.5.2 Data Transmission Procedure
The transmission of data from the remote station to the master and vice versa takes place spontaneous. The
prioritization and blocking of the data takes place on the basic system element (BSE). The data transmission is
started after 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 are saved in the data storage of the communication
function on the basic system element (BSE) until they 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 parameter
| 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.

DC8-037-2, Edition 11.2020
Acknowledgment Procedure
All sent data messages must be acknowledged by the other station (secondary station). If, with non-faulty
transmission line, the acknowledgment is missing for longer than the expected acknowledgment time, trans-
mitted 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 acknowledgment time is determined automatically from the set parameters, but if
necessary can be extended accordingly with the parameter Advanced parameter | 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 repetition | Retries
for data message SEND/CONFIRM (station selective) or for messages for station initialization
with the parameter message repetition | Retries for INIT-messages SEND/CONFIRM
(station selective) .
The acknowledgment 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
acknowledgment, however some third-party systems always expect the acknowledgment as message with
fixed length.
The message type for the acknowledgment can be selected with the parameter Advanced parameter
IEC60870-5-101 | Acknowledgment IEC60870-5-2 .
Failure Monitoring
The monitoring of the interface by the active master / remote terminal unit takes place by means of cyclic
transmitted (subject to acknowledgment) 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 parameter | 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 these are deleted by the
dwell time monitoring or can be transmitted to the re-reachable remote station.No further data is sent to a
failed remote station until successful station initialization.
After startup or redundancy switchover, the operation of the interface is begun after successful station initiali-
zation.
Reset Command Function in the Remote Station

REQUEST STATUS OF LINK • "STATUS OF LINK" is transmitted to the remote
station
• Acknowledgment for RESET of REMOTE LINK is
transmitted to remote station
NOTE
i 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 .

DC8-037-2, Edition 11.2020
If sending of "end of initialization" is enabled on the basic system element in the IEC 60870-5-101/104 param-
eter 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 Initializa-
tion" is also transmitted to the remote station. The clock synchronization command or general interrogation
command may only be transmitted after "INIT-End".
12.3.5.4 Acquisition of events (transmission of data ready to be sent)
The transmission of data clear to send from the remote station to the master and vice versa takes place spon-
taneous. The prioritization and blocking of the data clear to send takes place on the basic system element
(BSE). The data transmission is started after startup or in case of redundancy switchover after successful
station initialization.
For further details, see to section "Data transmission procedure".
12.3.5.5 General interrogation, Outstation interrogation
internal station initialization or after the master station has detected a loss of information. The function
Non-Interruptible General Interrogation
From the remote terminal unit periodic and spontaneous data can also be transmitted during a running
general interrogation.
With the parameter Advanced parameter | 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 cyclic or cyclic and 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 parameter | IEC60870-5-101 | Disable
data during non interrupted GI periodic data or periodic and spontaneous data.
The monitoring time is to be set on the protocol element with the parameter Advanced parameter |
IEC60870-5-101 | Timeout for non interrupted GI 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".
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.

DC8-037-2, Edition 11.2020
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 minute. The time of trans-
mission 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 A8000 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 controlled by the protocol element is
to be activated with the parameter Advanced parameter | 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 SICAM A8000 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.
12.3.5.7 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).
For further details, refer to section 12.3.5.2 Data Transmission Procedure.
Control location / Check control location

The “Control location” function is used to make sure that commands and setpoints are transferred from
authorized sources only. Once the function has been activated, commands/set point adjusting commands are
only transferred to the remote partner by the protocol element if the control location (originator address) has
been enabled.
If the control location is not enabled, the protocol element immediately sends back a negative acknowledg-
ment of activation (ACTCON) to the originator address (for more details on the control location, see section
12.1.3.1 Control location function for commands and setpoint values).
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".
12.3.5.9 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!

DC8-037-2, Edition 11.2020
12.3.5.10 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"!
12.3.6 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:
Parameters
• Common settings | Electrical interface [only SM-2541]
• Common settings | Asynchron/isochron
• Common settings | Source for receive-/transmit clock (only for "Isochronous")
• [PRE] Interface Parameter | Time settings for free definable interface modem
| Pause time (tp)
| Set up time (tv)
| Run out time (tn)
| DCD Handling
| Continuous level monitoring time (tcl)
| Transmission delay if continuous level (tcldly)
| Bounce suppression time (tbounce)
| Disable time (tdis)
• Common settings | Advanced time settings | Stability monitoring time (tstab)
• Advanced parameters | 5V supply (DSR) [only SM-0551, SM-2551]
• Advanced parameters | Configuration for CM-082x [only SM-0551, SM-2551]

How the individual time settings are effective during the data transmission is shown on the following page in
a Timing Diagram.

DC8-037-2, Edition 11.2020
Parameter "5V Supply (DSR)" [only SM-0551, SM-2551]

If necessary the voltage supply of the transmission facility (only 5V) – if this is enough – can be supplied over
the status line DSR (VCC). The enabling of the voltage supply is performed with the parameter advanced
parameters | 5V supply (DSR). The voltage supply is only switched to the DSR status line with corre-
sponding parameter setting.
NOTE
i Required voltage supply and maximum current consumption of the transmission facility must be observed!
Parameter "Configuration for CM-082x" [only SM-0551, SM-2551]

If an optical converter of the type CM-082x is used as external transmission facility, then when using a patch
plug of the type CM-2860 the parameter advanced Parameter | Configuration for CM-082x
must be enabled.
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) must be set depending on the used sub-module for communication, for transmit/receive direction
separated with parameter Common settings | Baud rate receive direction and the parameter
Common settings | Baud rate transmit direction 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:
Parameters
• 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

Acknowledgment Procedure)
The signal monitoring time is used for the message interruption monitoring and message resynchronization in
receive direction. A message interruption is detected when the time between 2 bytes of a message is greater
than the set signal monitoring time. With message interruption the receive processing in progress 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 – insofar as the transmission facility provides this signal receive-side – can evaluate the
interface signal DCD and e.g. utilize it for monitoring functions.
Default parameter for transmission facility:
Legend:
Electrical Interface Parameter Electrical Interface [only SM-2541]
RTS is switched for the control of the carrier switching of the modem RTS = ON (at tv=0),
RTS = ↑↓ (at tv≠0), carrier switching (ON / OFF) with each message in transmit direc-
tion

DC8-037-2, Edition 11.2020
tp Parameters Pause time (tp), Parameter Pause time_time base (tp)

tv Parameters Set-up time (tv), Parameter Set-up time_time base (tv)
tn Parameters Overtravel time (tn), Parameter Overtravel time_time base (tn)
tdis Parameters Blocking time (tdis), Parameter Blocking time_time base (tdis)
DCD Parameters DCD-evaluation
tbs Parameters Bounce suppression time (tbs)
tstab Parameters Stability monitoring time (tstab)
tduration Parameters Continuous level monitoring time (tduration) (tduration)
tdelay Parameters Transmit delay at level (tdelay)
A_I Parameters Asynchronous_Isochronous, (A=asynchron, I=isochron)
T Parameters Bit timing (only with isochronous), (I=internal, E=external)
5V Parameters 5V Supply (DSR) [only SM-0551, SM-2551]
CM-082x Parameter Configuration for CM-082x, configuring of the interface for optical
transformer CM-082x with patch plug CM-2860 [SM-0551, SM-2551 only]
NOTE
i
The following diagram shows in detail the timing 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.

DC8-037-2, Edition 11.2020
12.3.7 Function for the Support of Redundant Communication Routes
To increase the availability central stations as well as remote terminal units can be implemented redundantly.

DC8-037-2, Edition 11.2020
In the master station and remote station, with the parameter Advanced parameter | Project
specific settings | Redundancy control one can select between the following redundancy
controls:
• PRE-Redundancy
• NUC-Redundancy
• Deactivation of Interface
The switchover of the redundancy state takes place system-internal by means of redundancy control messages
or protocol control messages .
In addition, in the central station and remote terminal unit a delay with the switchover of the redundancy
state from PASSIVE (=STANDBY) to ACTIVE can be set with the parameter [PRE] Redundancy | Delay
time passive⇒active.
12.3.7.1 PRE-Redundancy
The PRE-Redundancy is selected with parameter Advanced parameter | Project specific

settings | Redundancy control = "Standard".
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 redundancy
• 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 moni-
toring 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.
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.

DC8-037-2, Edition 11.2020
Behavior when interface is "deactivated":

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
i 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).
12.3.7.2 NUC-Redundancy
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 operation "Norwegian User Conventions (NUC)" is selected with parameter Advanced
parameters | Project specific settings | Redundancy control = "Norwegian User Conven-
tions (NUC)".
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 auto-
matically 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 neces-
sary.

DC8-037-2, Edition 11.2020
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.
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 transmis-
sion line is defined on a basic system element as follows:
Interface 1 Interface 2 Note
Main/Standby Main/Standby
transmission Line transmission Line
ZSE = 128 ZSE = 129 Redundant interface pair for NUC-Redundancy
Legend:
SSE Supplementary system element (with serial interfaces, this is always configured with a PRE)
The CP-8050 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")
12.3.7.3 Port-Redundancy (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 transmis-
sion 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!
Data in control direction are transferred from the basic system element to the protocol element in the SICAM
A8000 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 transmis-
sion line to a SICAM A8000 internal IEC 60870-5-101-/104 format and transferred to the basic system
element.
12.3.8.1 Blocking
cols the “Blocking” according to IEC 60870-5-101 is implemented. This function is performed on the basic

DC8-037-2, Edition 11.2020
60870-5-101!
processing. Received messages with maximum length are transmitted SICAM A8000 internal in 2 blocks to the
60870-5-101/104 parameter block
12.3.8.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:
• Daylight saving time bit (SU) = 0 for all telegrams in transmit direction (daylight saving time bit in time
marker)
• Day of the week (DOW) = 0 for all telegrams in transmit direction (day of the week in the time marker)
• Originator address = 0 for all telegrams in transmit direction
• WhiteList-Filter
• TI filter
• Data throughput limit
• Convert General Interrogation Command to BROADCAST in Receive Direction
• Non Interruptible GI
• ACTCON for clock synchronization command
• Emulate ACTCON+/-
• Emulate ACTCON, ACTTERM for commands
• Emulate ACTCON, ACTTERM for commands with commands
• TCS100 compatibility
• Special functions DBAG
• Special Functions RWE
Summer Time Bit = 0 for all Messages in Transmit Direction

The daylight saving time bit is always set to 0 by the protocol element for all telegrams with time marker in
transmit direction when the function is enabled with the Advanced parameters | IEC60870-5-101 |
Time marker | Daylight saving time bit (SU) = 0 parameter.
Day of Week = 0 for all Messages in Transmit Direction

The day of the week (DOW) bit is always set to 0 by the protocol element for all telegrams with time marker in
transmit direction when the function is enabled with the Advanced parameters | IEC60870-5-101 |
Time marker | Day of the week (DOW) = 0 parameter.
NOTE
i This function is only active for process information messages in transmit direction. The day of week in clock
synchronization command message is not affected!

DC8-037-2, Edition 11.2020
Originator address = 0 for all messages in transmit direction

The originator address is always set to 0 by the protocol element for all telegrams in transmit direction when
the function is enabled with the Advanced parameters | IEC60870-5-101 | Originator address
in transmit direction = 0 parameter.
NOTE
i 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.
WhiteList-Filter
Caused by increased using of the norm protocol IEC 60870-5-101/104 in the area of the telecontrol engi-
neering/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 is activated with the Advanced parameters | IEC60870- 5-101 profile |
IEC60870-5-101 profile (type identification check) parameter.

DC8-037-2, Edition 11.2020
Following WhiteList-Filters can be selected:
– This profile can be used on interfaces between different providers or regions within same provider.
– Exclusively selected type identifications are permitted to pass in send/receive direction by the prede-
fined WhiteList filter (see Profile Definition: “WhiteList-Filter“, Page 674).
• WhiteList-Filter for passive PRE

– This WhiteList filter is only active if the protocol element (PRE) has been set to PASSIVE redundancy
state by redundancy control telegrams.
– In this state 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.
– The "SICAM RTUs – IEC 101" profile is used in ACTIVE redundancy state.
• TI-Filter + WhiteList-Filter
– From the pre-defined WhiteList-Filter only selected type identifications are passed through by the TI-
Filter.
– The TI-Filter can be parameterized separately in transmit-/receive direction.
– IEC 60870-5-101 telegrams with type identifications that have already been filtered out by the
WhiteList filter cannot be let through by the TI filter.
– IEC 60870-5-101 telegrams that have been filtered out by the TI filter are acknowledged to the
remote partner and then discarded (ACTCON/ACTTERM is not emulated).
• TI-Filter
– Only the IEC 60870-5-101 messages with type identifiers selected in the TI-Filter will be passed in
transmit-/receive direction (the cause of transmission is not evaluated).
– The TI-Filter can be parameterized separately in transmit-/receive direction.
– IEC 60870-5-101 telegrams that have been filtered out by the TI filter are acknowledged to the
remote partner and then discarded (ACTCON/ACTTERM is not emulated).
• SICAM RTUs - IEC 101 (SICAM RTUs “Standard“)

– WhiteList filter switched off (= preset).
– This profile is typically used for interfacing SICAM RTUs systems within region of same provider.
– All supported telegrams from the interoperability list according to 12.3.10 Interoperability IEC
60870-5-101 (BPP) including the type identifications for SICAM RTUs in the private section (telecon-
trol diagnostics, telecontrol parameterization, etc.) are supported in send/receive direction.
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 100

(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 100
(filtered messages cannot be logged in data flow test)
100 An error message is output for telegrams with type identifications that are not supported according to the WhiteList filter definition.
An error message will not be output for telegrams with type identification that are supported according to the WhiteList filter defini-
tion, but for which the cause of transmission is not supported according to the WhiteList filter definition.

DC8-037-2, Edition 11.2020
• 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 direction with
COT=ACTCON (DEACTCON)/ACTTERM will be passed only in a time 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 IEC 60870-5-101/104 standard (ACTACTCONACTTERM) the stored command infor-
mation will be deleted. The stored command information is deleted at a faulty command sequence after
expiry of the time window at the latest.
TI-Filter (“Type Identification Pass Filter”)

The TI-Filter (“Type identification pass filter“) will pass only IEC 60870-5-101/104 messages in transmit-/receive
direction with type identifiers selected in the TI-Filter.
The TI filter is activated with the Advanced parameters | IEC60870-5-101 profile |
IEC60870-5-101 profile (type identification check) parameter.
After activating the TI-Filter, the detailed parameters for the type identifier pass filter will be displayed.
• A maximum of 30 type identifications can be defined in the TI filter (also TIs for GI and TIs for system
information must be defined).
• Each type identifier may only be entered once in the TI-Filter

DC8-037-2, Edition 11.2020
• For each type identification, you can select in TI-Filter "Type identification pass in":
– Transmit- and Receive direction
– Transmit Direction
– Receive Direction
.
• The TI-Filter can be parameterized separately in transmit-/receive direction.
• The TI-Filter can be used either selectively or in combination with the WhiteList-Filter.
• If the TI-Filter is used with the WhiteList-Filter, only the IEC60870-5-101/104 messages with type identi-
fiers passsed by the WhiteList-Filter and selected in the TI-Filter will be passed in transmit-/ receive direc-
tion (the cause of transmission is evaluated by the WhiteList-Filter). Any TIs that have not been entered
are not permitted to pass through.
• If the TI-Filter is used without the WhiteList-Filter, only the IEC 60870-5-101 messages with type identi-
fiers selected in the TI-Filter will be passed in transmit-/ receive direction (the cause of transmission will
not be evaluated). Not selected TI’s in TI-Filter will be discarded.
• IEC 60870-5-101 messages, with type identifiers that are filtered out by the TI-Filter in receive direction,
are acknowledged to the remote station and then discarded (ACTCON / ACTTERM will not be sent).
Profile Definition: “WhiteList-Filter“

The following table below includes the profile definition for “WhiteList-Filter” and “WhiteList-Filter for passive
PRE”.

DC8-037-2, Edition 11.2020
Semantics of cause of transmission:

<0> := not used
<1> := periodic, cyclic
<2> := background scan
<3> := Spontaneous

DC8-037-2, Edition 11.2020
<4> := initialized
<5> := request or requested
<6> := activation
<7> := Confirmation of activation
<8> := Abortion of activation
<9> := Confirmation of the abortion of activation
<10> := Termination of the activation
<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> := Queried by station query
<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)
Profile Definition: "SICAM RTUs – IEC 101"

The SICAM RTUs - IEC 101 ("SICAM RTUs Standard") profile defines the functionality according to 12.3.10 Inter-
operability IEC 60870-5-101 (BPP). This profile will be used as standard for interfacing SICAM RTUs compo-
nents.

DC8-037-2, Edition 11.2020
*) ... blank or “X“ only

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

DC8-037-2, Edition 11.2020
Use Cases
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 has been received at this interface
Partner Interface between SICAM A8000 and SICAM RTUs Systems

Data exchange via interface (LAN, serial) between different partners (utilities) – both partners are using SICAM
RTUs systems.
Partner Interface between SICAM A8000 System and Third-Party System

Data exchange via interface (LAN, serial) between different partners (utilities) – one partner use SICAM RTUs
system the other partner uses a 3rd party system.
Internal Segmentation between SICAM A8000 Systems

Data exchange via interface (LAN, serial) between different divisions within the same partner (utility) – both
divisions are using SICAM RTUs systems.

DC8-037-2, Edition 11.2020
Internal Segmentation between SICAM A8000 System and Third-Party System

Data exchange via interface (LAN, serial) between different divisions within the same customer – one division
uses a SICAM RTUs system the other division uses a 3rd party system.
Redundant SICAM RTUs Automation Units

The WhiteList-Filter is only enabled on the interfaces between the redundant systems. All other interfaces are
not affected.

DC8-037-2, Edition 11.2020
Redundant SICAM RTUs Base 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.

DC8-037-2, Edition 11.2020
Redundant SICAM RTUs Base System Elements (BSEs) – Remote Maintenance
• 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.

DC8-037-2, Edition 11.2020
Data throughput limit

The protocol element for IEC 60870-5-101 balanced point-to-point does not support specific functions for
reduction of data throughput. With IEC 60870-5-101, data throughput can be reduced as follows:
• Reduction of the baud rate

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

For example: Dead time “tp“
Note: An increase of the acknowledgment waiting time at the remote partner may be required for delays
in sending the telegram.
Convert General Interrogation Command to BROADCAST in Receive Direction

All <TI:=100> general interrogation commands received by the protocol element are forwarded from the
transmission line with "Cause of transmission = Activation" to the base system element with CASDU = BROAD-
CAST address if the function is enabled and has theAdvanced parameters | IEC60870-5-101 | GI
command to all parameter.

DC8-037-2, Edition 11.2020
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 Inter-
rogation, Outstation Interrogation".
Emulate ACTCON+ for Clock Synchronization Command

The protocol element sending ACTCON+ for time synchronization can be adjusted as follows using the
Advanced parameters | IEC60870-5-101 | ACTCON for time synchronization commands
parameter:
• Do not send (= preset)
• immediately send
• Send after minute change and internal transfer of the time (= preset)
Emulate ACTCON+/- for Commands

If ACTCON is not supported by the basic system element or by the peripheral element used, then the emula-
tion 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> Incremental command
<TI:=48> Setpoint adjusting command, normalized value
<TI:=49> Set point command, scaled value
<TI:=50> Setpoint adjusting command, short floating-point number
• Immediately send ACTCON- from PRE if

– CASDU is not known to the PRE
• ACTCON+/- from BSE or PE is sent from PRE
ACTCON- for:
<TI:=100> Interrogation command

– CASDU is not known to the PRE and
– CASDU ≠ FFFF (=BROADCAST)
• ACTCON+/- from BSE is sent from PRE

DC8-037-2, Edition 11.2020
Emulation of Note
ACTCON+/- for:
<TI:=101> Counter interrogation command
• Immediately send ACTCON+ from PRE if

– CASDU is known to the PRE or
– CASDU = FFFF (=BROADCAST)
– CASDU is not known to the PRE
ACTCON+/- for:
<TI:=103> Time synchronization command if
• Send ACTCON+ from PRE if

– CASDU = FFFF (=BROADCAST)
The time to send ACTCON+ can be configured with theAdvanced parame-
ters | IEC60870-5-101 | ACTCON for time synchronization
command parameter
– CASDU ≠ FFFF (=BROADCAST)
Legend:
BSE ... Basic system element
PRE ... Log element
PE ... Peripheral element
The emulation of ACTCON by the protocol element (PRE) can be activated with the Advanced parameters
| IEC60870-5-101 | ACTCON +/- emulation parameter. 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.
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
<TI:=47> Incremental 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 Advanced
parameters | IEC60870-5-101 | ACTCON emulation parameter.
When the function has been activated, ACTCON telegrams are emulated by the protocol element as shown in
the table. All ACTCON+/- telegrams that are transferred from the base system element to the protocol element
are filtered out by the protocol element and therefore not transmitted.
ACTTERM telegrams that are transferred from the base system element to the protocol element are trans-
mitted by the protocol element.

DC8-037-2, Edition 11.2020
When the function has not been activated, ACTCON and ACTTERM telegrams that are transferred from the
base 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 periphery elements
used!
The Advanced parameters | IEC60870-5-101 | ACTCON +/- emulation parameter must be
enabled for the emulation of ACTCON- with unknown CASDU.
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 at the protocol element if the type identification in the
Advanced parameters | Project-specific settings | Emulate ACTCON, ACTTERM for
commands with control telegrams | TI and the monitoring times for ACTCON, ACTTERM have been
configured as "≠ 0".
The control can be performed by an application program of the open-/closed-loop control function.
The control telegrams trigger the emulation of the ACTCON+/- and ACTTERM+/- telegrams of a previously
received command (TI=45, TI=46, TI=47 - Select or Execute) to the remote partner.
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-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 activation confirmation must be set at the protocol element with
the Advanced parameters | Project-specific settings | Emulate ACTCON, ACTTERM for
commands with control telegrams | ACTCON monitoring time (after ACT) parameter.
The monitoring time for the reception of the activation termination must be set at the protocol element with
the Advanced parameters | Project-specific settings | Emulate ACTCON, ACTTERM for
commands with control telegrams | ACTTERM monitoring time (after ACTCON) parameter.
The IEC 60870-5-101/104 address of the control message (TI, CASDU1, CASDU2, IOA1, IOA2, IOA3) for the
emulation of ACTCON+ must be configured with the Advanced parameters | Project-specific
settings | Emulate ACTCON, ACTTERM for commands with control telegrams | * param-
eter. 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-
Configured address, IOA+2 Control message for emulation ACTTERM+
Configured address, IOA+3 Control message for emulation ACTTERM-
*) If <TI:=0> has been configured, there is no emulation by the protocol element; ACTCON,
ACTTERM telegrams from the base system element are transferred to the remote partner
TCS100 Compatibility
Corresponding parameters must be configured to link SICAM RTUs stations using the TCS100 protocol firm-
ware to guarantee compatibility in terms of the addressing type.

DC8-037-2, Edition 11.2020
The remote partner type is configured with the Advanced parameters | TCS100 compatibility |
"TCS100" remote partner parameter.
Set the configured addressing type in the TCS100 protocol firmware with the Advance parameters |
TCS100 compatibility | Addressing type for TCS100 parameter.
Select the region number to be added in receive direction with the Advanced parameters | TCS100
compatibility | Region number to be added for TCS100 remote partner type parameter.
You can either add the "own region number" or a configurable region number.
Set the configurable region number with the Advanced parameters | TCS100 compatibility |
Region number of the remote partner parameter.
Special functions DBAG

For the implementation of the protocol firmware in DBAG projects the following special functions can be acti-
vated:
• Breaker delay in transmit direction (DBAG-specific special message format <TI=150>)
• Sending the originator address with adjustable value

These special functions can be activated with the Advanced parameters | Project-specific
settings | DBAG functions parameter.
When the function has been activated, telegrams in the <TI:=33> "32 bit pattern" bound for the base system
element → Protocol element are converted to the DBAG-specific <TI:=150> telegram format and sent by the
protocol element.
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 transmission IEC-Parameter Type Identification for Transmission to
the Remote Station
Spontaneous - <TI=150> DBAG-specific format
GI with time (3 octets) <TI=4> Double-point information with
time tag
GI With time (7 octets) <TI=31> 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 transmission Time Format Type Identification for Transmission to
Basic System Element
spontaneous, GI With time (7 octets) <TI=33> Bitstring of 32 bits with time tag
CP56Time2a
NOTE
i 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!
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 telegrams in transmit direction with the Advanced parameters | Project-
specific settings | DBAG functions | Breaker delay in transmit direction parameter.
Message structure <TI=150> "Railway-specific Format" (in the private range)

DC8-037-2, Edition 11.2020
Sending the Originator address with Adjustable Value

In DBAG projects the originator address in transmit direction is always transferred with a fixed parameterized
value. Set the originator address with the Advanced parameters | Project-specific settings |
DBAG functions | Originator address in transmit direction parameter.
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).
Special Functions RWE

For the implementation of the protocol firmware in RWE projects the following special functions can be acti-
vated:
• NT-Bit, IV-Bit according to RWE Requirements

These special functions can be activated with the Advanced parameters | Project-specific
settings | RWE functions parameter.
NT Bit, IV Bit as per 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.

DC8-037-2, Edition 11.2020
If RWE-specific functions have been activated the special handling for the NT bit and the IV bit can be selected
with the Advanced parameters | Project-specific settings | RWE functions |
Converting the NT bits to IV bit in transmit direction parameter 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) has been set
SICAM A8000 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!

• Set Control Location
• Data filter control
• Activation/Deactivation of Interface + Protocol

• Information to be obtained about the station state/failure

DC8-037-2, Edition 11.2020
Block Diagram
12.3.9.1 Protocol element control
Internal protocol element functions can be controlled with protocol element control telegrams. At the base
system element IEC 60870-5-101/104 telegrams with process information in control direc-
tion are converted to protocol element control telegrams and sent to the selected protocol element (see
13.1.4.10 Protocol Element Control Telegrams).
12.3.9.2 Protocol Element Feedback
Protocol element feedback represents internal status information of the protocol element that is transferred
spontaneously and in the event of a general interrogation with internal telegram formats from protocol
element to base system element. At the base system element the protocol element feedback (see 13.1.4.9
Protocol Element Feedback) is converted to IEC 60870-5-101/104 telegrams with process informa-
tion in monitoring direction.
Supported protocol element feedback:

Protocol element feedback Station Note
Feedback_func-
tion_(PRE)
Status DTR 255 Status DTR
Status DSR 255 Status DSR *)
Station failure 255 1 = Station failed

DC8-037-2, Edition 11.2020

Feedback_func-
tion_(PRE)
protocol-specific return infor- 255 Interface activated/deactivated": Return information for PRE
mation 0 control message "activate/deactivate" interface
0 = interface "activated"
1 = interface "deactivated"
Protocol-specific feedback 1 255 Interface + protocol functions "activated/deactivated":
Return information for PRE control message
"activate/deactivate" interface + protocol
0 = interface + protocol functions "deactivated"
1 = interface + protocol functions "activated"
12.3.10 Interoperability IEC 60870-5-101 (BPP)
This companion standard presents sets of parameters and alternatives from which subsets must be selected to
implement particular telecontrol systems. Certain parameter values, such as the number of octets in the
COMMON ADDRESS of ASDUs represent mutually exclusive alternatives. This means that only one value of the
defined parameters is admitted per system. Other parameters, such as the listed set of different process infor-
mation in command and in monitor direction, allow the specification of the complete set or subsets, as appro-
priate for given applications. This clause summarizes the parameters of the previous clauses to facilitate a suit-
able selection for a specific application. If a system is composed of equipment stemming from different manu-
facturers it is necessary that all partners agree on the selected parameters.
The selected parameters should be marked in the white boxes as follows:
Function or ASDU is not used
Function or ASDU is used as standardized (default)
Function or ASDU is used in reverse mode
Function or ASDU is used in standard and reverse mode
The possible selection (blank, X, R, or B) is specified for each specific clause or parameter.
NOTE In addition, the full specification of a system may require individual selection of certain parameters for
certain parts of the system, such as the individual selection of scaling factors for individually addressable
measured values.
12.3.10.1 System or device function
(system-specific parameter, indicate the system’s or station’s function by marking one of the following with
„X“)
System definition
Controlling Station (Master)
Controlled Station (Slave)

DC8-037-2, Edition 11.2020
12.3.10.2 Network configuration
(network-specific parameter, all configurations that are used are to be marked „X“
Point-to-Point Multipoint-partyline
Multiple Point-to-Point Multipoint-star
12.3.10.3 Physical layer
(network-specific parameter, all used interfaces and data rates must be marked wirth „X“
Transmission speed (control direction)
Unbalanced Unbalanced Balanced

Interface Interface Interface
V.24/V.28 V.24/V.28 X.24/X.27
Standard Recommended if >1200
bit/s
100 bit/s 2 400 bit/s 2 400 bit/s 56 000 bit/s
300 bit/s 9 600 bit/s 9 600 bit/s
600 bit/s 19 200 bit/s 19 200 bit/s
1 200 bit/s 38 400 bit/s 38 400 bit/s
Transmission speed (monitor direction)

V.24/V.28 V.24/V.28 X.24/X.27
bit/s
300 bit/s 9 600 bit/s 9 600 bit/s
600 bit/s 19 200 bit/s 19 200 bit/s
1 200 bit/s 38 400 bit/s 38 400 bit/s

DC8-037-2, Edition 11.2020
12.3.10.4 Link Layer
(network-specific parameter, all configurations that are used are to be marked „X“ Specify the maximum frame
length. If a non-standard assignment of class 2 messages is implemented for unbalanced transmission, indi-
cate the Type ID and COT of all messages assigned to class 2.)
Frame format FT 1.2, single character 1 and the fixed time out interval are used exclusively in this companion
standard.
Link transmission procedure Address filed of the link
Balanced transmission not present (balanced transmission only)
Unbalanced transmission 1 Octet
2 Octets
structured
unstructured
Frame length
Maximum length L (control direction)
Maximum length L (monitor direction)
Time interval in which repetitions are allowed (Trp) or number of repetitions

When using an unbalanced link layer, the following ASDU types are returned in class 2 messages (low priority)
with the indicated causes of transmission:
The standard assignment of ASDUs to class 2 messages is used as follows:
Type Identification Cause of transmission

9, 11, 13, 21 <1>
A special assignment of ASDUs to class 2 messages is used as follows:
Type identification Cause of transmission
NOTE:
In response to a class 2 poll, a controlled station may respond with class 1 data when there is no class 2 data
available.

DC8-037-2, Edition 11.2020
12.3.10.5 Application Layer
Transmission mode for application data

Mode 1 (Least significant octet first), as defined in clause 4.10 of IEC 60870-5-4, is used exclusively in this
companion standard.
Common address of ASDU

(system-specific parameter, all configurations that are used are to be marked "X")
1 Octet 2 Octets
Address of the information object

1 Octet structured
2 Octets unstructured
3 Octets
Cause of transmission
2 Octets (with originator address)
1 Octet
Only originator address not used (=0) is used
Selection of standard ASDUs
Process information in monitor direction

(station-specific parameter, mark each Type ID "X" if it is only used in the standard direction, "R" if only used in
the reverse direction, and "B" if used in both directions)
<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

DC8-037-2, Edition 11.2020
<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 number M_ME_NC_1
<14> := Measured value, short floating point number 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 M_PS_NA_1
<21> := Measured value, normalized value without quality descriptor M_ME_ND_1
<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 bits 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 number 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 time tag CP56Time2a M_EP_TE_1
<40> := Packed output circuit information of protection equipment with time tag
M_EP_TF_1
CP56Time2a
Either ASDUs of the set <2>, <4>, <6>, <8>, <10>, <12>, <14>, <16>, <17>, <18>, <19> or of the set <30 –
40> are used.
6) Reception possible, thereby the blocked single-point information is deblocked and further individually
processed as TI = 30 (address translation occurs algorithmic).
Process information in control direction


DC8-037-2, Edition 11.2020
<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 number C_SE_NC_1
<51> := Bitstring of 32 bit C_BO_NA_1
<58> := Single command with time tag CP56Time2a C_SC_TA_1
<59> := Double command with time tag CP56Time2a C_DC_TA_1
<60> := Regulating step command with time tag CP56Time2a C_RC_TA_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 bits with time tag CP56Time2a C_BO_TA_1
Either the ASDUs of the set <45> - <51> or of the set <58> - <64> are used.
System information in monitoring direction

<70> := End of initialization M_EI_NA_1
System information in control direction

<100> := Interrogation command C_IC_NA_1
<101> := Counter interrogation command C_CI_NA_1
<102> := Read command C_RD_NA_1
<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

DC8-037-2, Edition 11.2020
Parameter in control direction

<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 P_ME_NC_1
<113> := Parameter activation P_AC_NA_1
+ … secondary application function only

4) … Not used in IEC 60870-5-101 Edition 2. No use case.
File transfer
<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
Type identifier and Cause of Transmission Assignments

(station-specific parameter)
Shaded boxes are not required.
Black boxes are not permitted in this companion standard
Blank = Function or ASDU is not used.
Mark Type Identification/Cause of transmission combinations:
"X" if only used in the standard direction,
"R" if only used in the reverse direction,
"B" if used in both directions.

DC8-037-2, Edition 11.2020

DC8-037-2, Edition 11.2020

DC8-037-2, Edition 11.2020
12.3.10.6 Basic application functions
Station Initialization
(station-specific parameter, mark "X" if function is used)
Remote initialization
Cyclic data transmission

(station-specific parameter, mark each Type ID "X" if function is only used in the standard direction, "R" if only
used in the reverse direction, and "B" if used in both directions)
' … secondary application function only
Read procedure
Read procedure
Spontaneous transmission
Double transmission of information objects with cause of transmission spontaneous

(station-specific parameter, mark each information type "X" where both a Type ID without time and corre-
sponding Type ID with time are issued in response to a single spontaneous change of a monitored object)
The following type identifications may be transmitted in succession caused by a single status change of an
information object. The particular information object addresses for which double transmission is enabled are
defined in a project-specific list.
Single-point information M_SP_NA_1, M_SP_TA_1, M_SP_TB_1 and M_PS_NA_1
Double-point information M_DP_NA_1, M_DP_TA_1 and M_DP_TB_1
Step position information M_ST_NA_1, M_ST_TA_1 and M_ST_TB_1
Bitstring of 32 bit M_BO_NA_1, M_BO_TA_1 and M_BO_TB_1 (if defined for a specific project)
Measured value, normalized value M_ME_NA_1, M_ME_TA_1, M_ME_ND_1 and M_ME_TD_1
Measured value, scaled value M_ME_NB_1, M_ME_TB_1 and M_ME_TE_1
Measured value, short floating point value M_ME_NC_1, M_ME_TC_1 and M_ME_TF_1

DC8-037-2, Edition 11.2020
Station Interrogation
(station-specific parameter, mark "X" if function is only used in the standard direction, "R" if only used in the
reverse direction, and "B" if used in both directions)
Global
group 1 group 7 group 13
group 5 group 11
Information Object
group 6 group 12
Addresses assigned to each
group must be shown in a
separate table.
Clock synchronization
Day of week used
RES1, GEN (time tag substituted/ not substituted) used
SU-bit (summertime) used
Command transmission
(object-specific parameter, mark "X" if function is only used in the standard direction, "R" if only used in the
Direct command transmission
Direct set point command transmission
"Select and execute" command
"Select and execute" set point command
C_SE ACTTERM used
No additional definition
Short pulse duration (duration determined by a system parameter in the outstation)
Long pulse duration (duration determined by a system parameter in the outstation)
Persistent output

DC8-037-2, Edition 11.2020
B* can be generated by the PLC
Transmission of integrated totals

(station- or object-specific parameter, mark "X" if function is only used in the standard direction, "R" if only
Mode A: Local freeze with spontaneous transmission
Mode B: Local freeze with counter interrogation
Mode C: Freeze and transmit by counter interrogation commands
Mode D: Freeze by counter interrogation command, frozen values reported spontaneously
Counter read
counter freeze without reset
Counter freeze with reset
counter reset
General request counter
counter interrogation group 1
Parameter loading 101

Threshold value
Smoothing factor
Low limit for transmission of measured value
High limit for transmission of measured value
Parameter activation
act/deact of persistent cyclic or periodic transmission of the addressed object
101 Not supported with "Controlled Function"

DC8-037-2, Edition 11.2020
Test procedure
(station-specific parameter, mark "X" if function only used in standard direction, "R" if only used in the reverse
direction, and "B" if used in both directions)
Test procedure
file transfer
File transfer in monitor direction
Transparent file
Transmission of disturbance data of protection equipment
Transmission of sequences of events
Transmission of sequences of recorded analog values
File transfer in control direction
Transparent file
X* Data can be transparently transported by the system but not generated or evaluated. A maximum of
220 bytes of user data can be transported in a segment telegram for file transfer.
Background scan
Background scan
Note: used for data which are transmitted caused by a self-initiated general interrogation
Acquisition of transmission delay


DC8-037-2, Edition 11.2020
12.4 IEC 60870-5-101 (Multi-Point Traffic)
12.4.1 Introduction
The IEC 60870-5-101 protocol (multi-point traffic) is a standardized serial transmission protocol for communi-
cation with remote stations with multi-point traffic (master/slave principle; “Partyline”).
For CP-8000/CP-802x, the following protocol firmware for IEC60870-5-101 (point-to-point) is available:

UMPMT0 CP-8000 IEC 60870-5-101 Multi-point traffic Master
CP-802x
UMPST0 CP-8000 IEC 60870-5-101 Multi-point traffic Slave
CP-802x
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 line 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.
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 multiple point-to-
point, star or linear structure.
The master station and the remote terminal units in multi-point traffic operate with a communications
protocol according to IEC 60870-5-101. The supported functionality (interoperability) is described in the
section 12.4.13 Interoperability IEC 60870-5-101 (UMP).
12.4.2 Functions
Communication of a central station with one or several substations in multi-point traffic.
Central Station
• Serial communications protocol according to IEC 60870-5-101

UMPMT0 is central station

DC8-037-2, Edition 11.2020
• Unbalanced transmission Master

– Multipoint-partyline
– Multipoint-star
– Controlling station
• Physical layer / data flow control

– Unbalanced interchange circuit according to V.24/V.28 standard
– Transmission line (half duplex)
– Byte Frame (8E1)
– Data flow control bit in receive direction
– Data flow control Bit supervision
• Interoperability according to IEC 60870-5-101 Ed.1
• Interoperability according to 12.4.13 Interoperability IEC 60870-5-101 (UMP)
• Data Acquisition by Polling (Station Interrogation)

– Continuous interrogation of a remote terminal unit
– Station failure delay
• Acquisition of events (transmission of data ready to be sent)
• General interrogation, Outstation interrogation

– Clock synchronization with <TI=103> clock synchronization command
– Acquisition of transmission delay (primary station) used for correction of clock synchronization (with
“request status of link” = proprietary)
– Demand
– Set control location
– Check control location
• 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
– 5 V power supply for external modem
ATTENTION: check power consumption of external modem!
• 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/Standby transmission Line

DC8-037-2, Edition 11.2020

– Protocol element control
– Data filter in transmit direction ON/OFF
– Data filter in receive direction ON/OFF
– Interface activate/deactivate
– Interface + Protocol activate/deactivate
– Add / Remove station to station polling
– Call cycle START/STOP/CONTINUE
– Continuous call station x ON / OFF
– Main/ Standby transmission line ACTIVE
– Protocol element return information
– Station failure
– Station status
– Status DTR (1 = state line active)
– Status DSR (1 = state line active)
– Protocol-specific return information 0 to 3, 6, 7, 8 to 11
• Remote maintenance with SICAM TOOLBOX II via serial connection
– 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)
• Transparent Mode (Tunneling)
Remote Station
• Serial communications protocol according to IEC 60870-5-101

UMPST0 is substation
• Unbalanced transmission Slave

– Multipoint-star
– Controlled station

DC8-037-2, Edition 11.2020
• Physical layer / data flow control

– Unbalanced interchange circuit accordingV.24/V.28 standard
• Interoperability according to IEC 60870-5-101 Ed.1
• Interoperability according to 12.4.13 Interoperability IEC 60870-5-101 (UMP)

– Send GI Data as Class 1 Data
– Convert general interrogation command in receive direction to Broadcast

– Acquisition of transmission delay (secondary station) used for correction of clock synchronization
with <TI:=106>
– Correction of clock synchronization (via parameter)
– Accuracy ±20 ms
– Accuracy with relay operation ±20 ms 102
• File Transfer
• Optimized parameters for selected transmission facilities (modems)


– Protocol element control
– I bit handling for time ON/OFF
– Protocol element return information
– Status DTR (1 = state line active)
– Status DSR (1 = state line active)
102 with relay operation accuracy will be reduced 10 ms per routing station

DC8-037-2, Edition 11.2020
– 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 in Transmit Direction
ment.
optional DTE
Unbalanced interchange circuit X2 RXD, TXD, CTS 103, RTS, DCD, DTR,
(V.24/V.28) RS-232 asynchronous DSR/VCC, GND
Balanced interface (V.11) RS-485 X3 TXD+/RXD+, TXD-/RXD- (2-wire)
(2-wire)/ RS-422 (4-wire) asynchronous TXD+, TXD-, RXD+, RXD- (4-wire)
Balanced interface (V.11) RS-485 X2 → CM-0829 RXD, TXD, CTS, RTS, DCD, DTR,
(2-wire)/ RS-422 (4-wire) asynchronous (CM-0819) 104 DSR/VCC, GND (to CM-08x9)
Optical interface (multimode fibre optic) ring X2 → CM-0821 RXD, TXD, CTS, RTS, DCD, DTR,
DSR, GND (to CM-0821)
Unbalanced interchange circuit X6105 RXD, TXD, CTS, RTS, DCD, DTR,
(V.24/V.28) RS-232 asynchronous DSR, GND
NOTE

104 in case of transmission rates > 9600 bit/s converter PHOENIX PSM-ME-RS232/RS485-P is required: Interface signals D(A), D(B), GND
(RS-485); D(A), D(B), T(A), T(B), GND (RS-422); CM-0819 does not support RS-422

DC8-037-2, Edition 11.2020
Own Station (Central Station)
System Master Module Protocol Element Remarks

SICAM A8000 CP-8000/CPC80 UMPMT0
CP-802x/CPC80 UMPMT0
Remote Station (Substation)

SICAM A8000 CP-8000/CPC80 UMPST0
CP-802x/CPC80 UMPST0
SICAM AK 3 CP-2016/CPCX26 UMPSA0
CP-2019/PCCX26 UMPSA0
Legacy systems CP-20xx SM-2551/UMPSA0 according to
(SICAM AK CP-50xx SM-0551/UMPSA0 12.4.13 Interoperability
SICAM TM CP-60xx UMPST0 IEC 60870-5-101 (UMP)
SICAM EMIC SM-2541/UMPS00
SICAM MIC
SICAM BC
Ax 1703)
Third-party system - - according to
IEC 60870-5-101 (UMP)

SICAM A8000 CP-8000/CPC80 UMPST0
CP-802x/CPC80 UMPST0

SICAM A8000 CP-8000/CPC80 UMPMT0
CP-802x/CPC80 UMPMT0
SICAM AK 3 CP-2016/CPCX26 SM-2551/UMPMA0
CP-2019/PCCX26 SM-0551/UMPMA0
Legacy systems CP-20xx SM-2551/UMPMA0 according to
(SICAM AK CP-50xx SM-0551/UMPMA0 12.4.13 Interoperability
SICAM TM CP-60xx UMPMT0 IEC 60870-5-101 (UMP)
SICAM BC SM-2541/UMPM00
Ax 1703)
IEC 60870-5-101 (UMP)

DC8-037-2, Edition 11.2020
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 inter-
rogation 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 inter-
rogated 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 parameter | 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 param-
eter Station definition .
In every remote terminal unit, the station-selective address must be set with the parameter 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 parameter | IEC60870-5-101
| Address field of the link (number of octets).
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:
Parameters
• 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 priority lvl (A)
• Station call prioritization | No. of stat. calls in low priority 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.
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:

DC8-037-2, Edition 11.2020
• 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".
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
of the message is required. These parameter can be found in the interoperability list (master station and all
remote stations must be parametrized identically).

DC8-037-2, Edition 11.2020
The variable elements of the message must be set at the protocol element.
IEC 60870-5-101 Parameters Description System element
Byte number link address Number of octets for the address field of the link PRE
layer
Cause of transmission (COT) Number of octets for cause of transmission BSE
Common address of ASDU (CASDU) Number of octets for common address of the BSE
ASDU
Information object address (IOA) Number of octets for the address of the informa- BSE
tion object
Acknowledgment on IEC 60870-5-2 Single character or short message (ACK) PRE
layer
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
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. Data messages
ready for sending to same remote station will be sent during demand in progress.
During the demand, user data telegrams continue to be transmitted to this substation.
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 acknowledgment is missing for longer than the expected acknowledgment
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 acknowledgement from the remote terminal unit to the master station can be transmitted as single char-
acter (E5), if no additional information (such as DCF-Bit or ACD-Bit) is to be transmitted. If additional informa-
tion 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 acknowledgment can be selected with the parameter Advanced parameter
IEC60870-5-101 | Acknowledgment IEC60870-5-2 .
necessary can be extended accordingly with the parameter Advanced parameter | 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 remote terminal units must be taken into consideration.
The number of retries for data messages is to be set with the parameter message repetition | Retries
for data message SEND/CONFIRM (station selective) or for messages for station initialization

DC8-037-2, Edition 11.2020
with the parameter message repetition | 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 stationZentrale). 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.
Failure Monitoring in the Master Station

The monitoring of the interface by the active master station takes place by means of the cyclic running inter-
rogation 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 acknowledgment time i.e. no other remote terminal units are interro-
gated 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 defini-
tion .
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 central station by means of the interrog-
ation procedure, however no message repetition (Retry) is carried out during the station interrogation for such
The interrogation cycle for failed stations can be set with the parameter Advanced parameter |
IEC60870-5-103 | 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 are transmitted from the central station to failed remote terminal units. The data are saved in the data
storage of the communication function on the basic system element (BSE) until they 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 parame-
terized with the parameter Advanced parameter IEC60870-5-101 | Station 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
i 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!

DC8-037-2, Edition 11.2020
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 parameter | 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 parameter | Monitoring times | Call timeout retrigger also
with "request status of link" retriggern 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 stationZen-
trale). 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.
of the remote terminal until these are deleted by the dwell time monitoring or can be transmitted to the
master station.
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.

REQUEST STATUS OF LINK • "STATUS OF LINK" is transmitted to the master station
• Acknowledgment for RESET of REMOTE LINK is transmitted to
master station
tion" is also transmitted to the remote station.
The clock synchronization command or general interrogation command may only be transmitted after "INIT-
End".

DC8-037-2, Edition 11.2020
12.4.5.3 Acquisition of events (transmission of data ready to be sent)
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)".
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.A Quick-Check procedure for accelerating the transmission of data is not
implemented.
Note:
• 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 parameter |
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 synchronization 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 remote Link
before following 1st message with time tag.
The general interrogation function (RTU interrogation) is used for updating the central station after the
internal station-initialization or after the central station has detected a loss of information. The function
A general interrogation command "to all" triggered in the system is always transferred by the communications
Non-Interruptible General Interrogation

Spontaneous data is also transmitted from the remote terminal unit during a running general interrogation.
With the parameter Advanced parameter | IEC60870-5-101 | Timeout for non interrupted
GI the spontaneous transmission of data can be disabled in the remote station 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)

DC8-037-2, Edition 11.2020
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 parameter |
IEC60870-5-101 | Timeout 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 interrog-
ation command is received with the cause of transmission "Termination of Activation".
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 parameter | 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)
Messages, which are sent 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 Advanced parameter | 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 calcu-
lated 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 parameter |
IEC60870-5-101 | Correction time for time synchronization 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 remote station; time in ACTCON for <TI:=103>=t<TI:=103> + tD<TI:=106> - tDtel
• "T_Delay <> 0":

New time of remote station; time in ACTCON for <TI:=103>=t<TI=103> + t_Delay
(t<TI:=103> = new time for remote station included in <TI:=103>;tD<TI:=106> = correction time included in
<TI:=103>;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 parameter | IEC60870-5-101 | ACTCON for clock synchronization command as
follows (see also section "Special functions"):
• Do not send (=default)
• Send immediately

DC8-037-2, Edition 11.2020
• Send after minute change and internal transfer of the time (DEFAULT)
• Send immediately and ignore (do not accept clock synchronization command)
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.
Message from the Central Station selectively to a Remote Terminal Unit

Station-selective data messages in command direction are always inserted by the central station with high
priority into the running interrogation procedure (station interrogation) after completion of the data transmis-
sion in progress. Data to be sent from the base system element (BSE) is always prioritized at a ratio of 1:1
compared with station queries.
Inquiry
If the reaction of the substation to a transmitted telegram is to be acquired quickly by the master station, an
inquiry (configurable station-selective continuous query) can be performed by the master station. This station-
selective inquiry is retriggered by further telegrams to the same station (telegram configured with inquiry) or
canceled by telegrams to other stations.
Run type identification selection and adjustment of the continuous access time for type identification with the
Advanced parameters | Access procedure per type identification | * parameters to
enable this inquiry.
Data-Flow Control
If a substation is unable to process additional data telegrams (messages), the DFC bit (data flow control) is set
in the telegram control field towards substation → master station. From this moment onwards, the protocol
firmware of the master station no longer sends data telegrams to the corresponding substation until the
substation once again resets the DFC bit. The protocol firmware also monitors whether the substation resets
the DFC bit within a time that can be adjusted using the Advanced parameters | IEC60870-5-101 |
DFC continuous monitoring time parameter.
If the DFC bit applies for longer than the set monitoring time, the DFC bit timeout to station no.
xx warning is output.
Control location / Control location check

been enabled.
Message from the Master Station to all Remote Terminal Units (unacknowledged)
“Unacknowledged” telegrams from the multi-point traffic master station to all are inserted into an on-going
polling cycle (station query) after having completed the on-going data transmission. In this process, the tele-
gram is sent several times from the master station with the configurable number of telegram retries according
to the Telegram retries | Retries for SEND/NO REPLY (broadcast) data telegram param-
eter. Afterwards the interrupted interrogation cycle is resumed.

DC8-037-2, Edition 11.2020
12.4.5.7 Transmission of integrated totals
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
parameter | 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.
document Common Functions of Peripheral Elements according to IEC 60870-5-101/104.
12.4.5.8 Acquisition of transmission delay
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 station. The
correction of the time in the clock synchronization command is performed in the remote station.
The protocol element of the master station uses a SICAM RTUs specific method for the "acquisition of transmis-
sion 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 parameter | station-selective clock synchronization | Cycle time for
sending clock synchronization command .
With the parameter Advanded parameter | station-selective clock synchronization |
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 time-synchronization
command is already corrected by the protocol firmware of the master station with the automatically deter-
mined correction value and the parameterized correction value.
12.4.6 Optimized Parameters for Selected Transmission Facilities
The protocol element supports selected transmission facilities – for which the parameters are set permanently
– the selection of the transmission facility is carried out with the General settings | Transmission
facility parameter. By selecting the "free definable" certain parameters can be set individually.
In most cases transmission facilities support only particular baud rates or combinations of baud rates in send/
receive direction – these must be taken from the descriptions for the transmission facility.
The transmission rate (baud rate) must be set depending on the used sub-module for communication, for
transmit/receive direction separated with parameter Common settings | Baud rate receive direc-
tion and the parameter Common settings | Baud rate transmit direction or for transmit/
receive direction together with the parameter Common settings | Baud rate .
When using the "DLC modem (CE-0740, CE-0741)" transmission facility, the settings of the DLC modem, such
as DIP switch S1/1 .. S1/4 and the Frequency band used (= current DIP switch settings at the DLC
modem) must be additionally configured at the protocol element with the General settings | DLC
modem (CE-0740, CE-0741) | * parameters. These parameters serve to optimize the data transmission
via DCL modem (CE-0740, CE-0741) and to automatically adjust the required time settings in the protocol
firmware.
When using the "SATTELLINE 2ASxE time-slice modem" transmission facility additionally configure the
General settings | Time slice modem (SATTELLINE 2ASxE) | Failure monitoring,
parameter, the General settings | Time slice modem (SATTELLINE 2ASxE) | Time slice
length parameter, and the General settings | Time slice modem (SATTELLINE 2ASxE) |
Start second for time slice parameters. These parameters are used for the optimization of the data
transmission with time slot radio technique.

DC8-037-2, Edition 11.2020
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 the broadcast telegrams can be adjusted in the master station with the Advanced parame-
ters | Additional time settings | Dead time after broadcast telegram (tp_bc)
parameter. If the pause time is set to "0", a minimum pause of 33 bit is maintained by the protocol element.
A transmission facility that can be freely defined by users can also be selected and all available parameters can
be individually configured for this. This is necessary when transmission facilities are to be used that are not
predefined or if modified parameters are to be used for predefined transmission facilities. Adjust the General
General settings | Transmission facility parameter to Freely definable to select the
freely definable transmission facility.
Only then are all supported parameters displayed and can be configured with the required values (refer to
table with preset parameters for transmission facilities).
The following parameters can be set individually for the adaptation to various modems or time requirements
of external systems:
• General settings | Asynchronous/isochronous
• General settings | Bit cycle (for isochronous only)
• General settings | Freely definable transmission facility | Dead time (tp)
• General settings | Freely definable transmission facility | "Time base" dead

time (tp)
• General settings | Freely definable transmission facility | Lead time (tv)
• General settings | Freely definable transmission facility | "Time base" lead

time (tv)
• General settings | Freely definable transmission facility | Post-trigger time

(tn)
• General settings | Freely definable transmission facility | "Time base" post-

trigger time (tn)
• Advanced parameters | Additional time settings | Dead time after broadcast

telegram (tp_bc)
• Advanced parameters | Additional time settings | "Time base" dead time after
broadcast telegram (tp_bc)
• General settings | Freely definable transmission facility | DCD evaluation
• General settings | Freely definable transmission facility | Bounce suppres-

sion time (tbounce)
• General settings | Freely definable transmission facility | Reclaim time

(tdis)
• General settings | Freely definable transmission facility | "Time base"

reclaim time (tdis)
• General settings | Freely definable transmission facility | Stability moni-

toring time (tstab)
• General settings | Freely definable transmission facility | Continuous level

monitoring time (tcl)
• General settings | Freely definable transmission facility | Send delay at

level (tcldly)
• General settings | Freely definable transmission facility | Selectively send

time synchronization command to stations
How the individual time settings are effective during the data transmission is shown in Figure 12-1.

DC8-037-2, Edition 11.2020
If necessary the power supply of the transmission facility (5V only) – if sufficient – can be supplied by the DSR
status line. The power supply is enabled by the General settings | Freely definable transmis-
sion facility | X2: DTR/VCC pin as output for. The power supply is only switched to the DSR
status line instead of the DSR signal with a corresponding parameter setting.
NOTE
i Required supply voltage and maximum current consumption of the transmission facility must be observed!
In addition, the following parameters are available for the adaptation of the protocol to the transmission
medium used or to the time behavior of the connected remote partner:
• Advanced parameters | Monitoring times | Character monitoring time
• Advanced parameters | Monitoring times | "Time base" character monitoring

time
• Advanced parameters | Monitoring times | Idle monitoring time
• Advanced parameters | Monitoring times | "Time base" idle monitoring time
• Advanced parameters | Monitoring times | Acknowledgment expectation time

correction (see acknowledgment procedure in the master station)
The character monitoring time and idle monitoring time is use in the receive direction for telegram interrup-
tion monitoring and telegram resynchronization. A telegram interruption is identified if the time between 2
bytes of a telegram is greater than the set character monitoring time. In the event of a telegram interruption
the on-going receive handling is canceled and the telegram is discarded. After a telegram interruption has
been identified a new telegram is only accepted on the line in receive direction after an idle time.
If the transmission facility (for example: VFT channel) provides this signal on the receive side, the protocol
element can evaluate the DCD interface signal and use it for monitoring functions.
Default parameters for transmission facilities with UMPMxx

DC8-037-2, Edition 11.2020
Time settings “freely definable” for selected converters/modems with UMPMxx, UMPSxx
Default parameters for transmission facilities with UMPSxx0
Legend:
RTS ↑↓ = RTS is scanned for each telegram to control the modem's level scan (ON/OFF)
tp Dead time (tp) parameter
tv Lead time (tv) parameter
tn Post-trigger time (tn) parameter
tp_bc Dead time after broadcast telegram (tbc) parameter
(valid only for MASTER station!)
tdis Reclaim time (tdis) parameter
DCD DCD evaluation parameter
tbs Bounce suppression time (tbounce) parameter
tstab Stability monitoring time (tstab) parameter
tduration Continuous level monitoring time (tduration) parameter
tdelay Transmission delay at level (tdelay) parameter
A_I Asynchronous_Isochronous parameter, (A=asynchronous, I=isochronous) [BSE]
T Bit cycle parameter (for isochronous only) (I=internal, E=external) [BSE]
Z Selectively send synchronization command to stations parameter
(s=selectively, B=BROADCAST) – valid for master station only!
5V/12V 5V/12V supply (DSR) parameter [BSE]
The following diagram shows in detail the time behavior (timing) for the data transmission when using trans-
mission facilities with scanned carrier.

DC8-037-2, Edition 11.2020
[UMPxyy_Timing, 1, en_US]
Figure 12-1 Timing during transmission
12.4.7 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 trans-
mission line over the public telephone network (PSTN).

DC8-037-2, Edition 11.2020
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 addi-
tion 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:
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 parameter |
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 Backup Line Note
ZSE = 128 ZSE = 129 The SSEs for Main-/Backup transmission line must be on the
same BSE.
ZSE = 130 ZSE = 131

DC8-037-2, Edition 11.2020
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 parameter | 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 parameter | 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 acknowledgment, 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.
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).

DC8-037-2, Edition 11.2020
NOTE
i • The "Standby Transmission Line over the Public Telephone Network (PSTN)" will be supported in the
master station only for following transmission facilities (Data transmission with "no Parity"):
– 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)
• 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 [PRE] IEC60870-5-101 | Time
settings, retries | Monitoring times | Character monitoring time and the
parameter Advanced parameter | Monitoring times | Character monitoring time
"time base".
12.4.8 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 transmis-
sion 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 measure-
ment 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.

DC8-037-2, Edition 11.2020
The data transmission using the time slot method is selected by selecting the transmission facility "SATTELLINE
2ASxE time slot radio modem " with the parameter [PRE] Interface parameter | Time settings
for interface modem . When using this transmission facility, in addition, in the MASTER the parameter
[PRE] Interface parameter | Time slot radio modem (SATTELLINE 2ASxE) | failure
monitoring, the parameter [PRE] Interface parameter | Time slot radio modem (SATTEL-
LINE 2ASxE) | length of time slot and the parameter [PRE] Interface parameter | Time
slot radio modem (SATTELLINE 2ASxE) | start second of time slot must be parameter-
ized. These parameters are used for the optimization of the data transmission with time slot radio technique.
12.4.9 Data Transmission in Relay Operation Mode (Multi-Point Traffic with Routing)
In relay operation, messages transmitted from the master station can also reach the remote terminal unit indi-
rectly (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 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 transmission
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 A8000-specific expansion of the IEC 60870-5-101 protocol in multi-
point traffic.
The function Relay Operation is activated by enabling the parameter Advanced parameter | 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 them-
selves continue to be used according to IEC 60870-5-101.
Parameters for relay operation:
• Enabling of the relay function with the parameter Advanced parameter | Repeater function
(Routing)
• Switchover main-/standby transmission line with the parameter Advanced parameter | Repeater
function (Routing) | Retries until switchover to stand-by line

DC8-037-2, Edition 11.2020
• Routing method (optimized/not optimized) with the parameter Advanced parameter | Repeater
function (Routing) | Routing Method
• "Radio circuit identifier/master number" with the parameter Advanced parameter | Radio area
identifier/master number
• "Routing paths" (path-type, destination station number, routing station number) with the 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 prob-
lems. 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 the fact that only most simple radio communication units, even of
low transmission power, with only one single frequency are used in the entire automation area.
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 trans-
mitter up-switching operations in the entire network thereby takes place.
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 communi-
cating 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).

DC8-037-2, Edition 11.2020
For the transmission of a message from the master station Z to the remote stations U1, U2, U3, and U4, the
following routes are possible (reverse direction along the same route):
Source Destina- Route Note
tion
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, Ux ... source, destination
ux ... Routing-Station
Legend:
In the following picture, radio regions are represented by closed curves.
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.
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 interroga-
tion 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

DC8-037-2, Edition 11.2020
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 inter-
face 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 accu-
racy 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).
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 parameter | 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.
12.4.9.1 Main and Standby Transmission Line
For every remote terminal unit that cannot be reached directly, but only via routing stations, the main trans-
mission 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).

DC8-037-2, Edition 11.2020
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 arameter Advanced parameters | Repeater func-
tion (Routing) | Retries until switchover to stand-by line the moment for the switch-
over from main to standby transmission line can be defined. If this attempt to obtain an acknowledgment 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.
12.4.9.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
parameter | Repeater function (Routing) | Routing procedure .

DC8-037-2, Edition 11.2020
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").
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).

DC8-037-2, Edition 11.2020
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 Infor-
mation".
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 neces-
sary 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"

DC8-037-2, Edition 11.2020
In this section, the possible redundancy concepts themselves that can be realized are not described, rather
only those functions supported by the protocol element for the support of redundant communication routes.
In the master station and remote station, with the parameter Advanced parameter | Project
specific settings | Redundancy control one can select between the following redundancy
controls:
• PRE-Redundancy
• NUC-Redundancy
In addition, in the central station and remote terminal unit a delay with the switchover of the redundancy
state from PASSIVE (=STANDBY) to ACTIVE can be set with the parameter Redundancy | Delay time
passive⇒aktiv .
• Interface "tristate" – only listening mode
• Interface "active" – only listening mode
• Interface "active" – interrogation mode


DC8-037-2, Edition 11.2020
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 recep-
tion. The monitoring time is set with the parameter Redundancy | Listening mode (failure moni-
toring time). On receive timeout (active central station or transmission facility of the central 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 trans-
mission facility of the remote terminal unit has failed) the remote terminal unit is signaled as failed.
Station-specific faults present are reset in a redundant STANDBY master station, if a faultless message from
In case of redundancy switchover from "PASSIV → AKTIV", the substation forces a station initializtion by not
answering any telegrams until the "REQUEST STATUS OF LINK" message is received. This means that the
central station detects a failure of the interface and, after successful station initialization, a general query is
carried out and the current status of the data is transferred from the now active redundant substation (a
redundancy switchover always leads to a brief station failure).
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":

– 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":

– 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
i 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).

DC8-037-2, Edition 11.2020
12.4.10.2 NUC-Redundancy
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 NUC-Redundancy is supported in the master station and remote terminal and is selected with the para-
meter Listening mode (failure monitoring time)= "Norwegian User Conventions (NUC)".
The switchover of the redundancy state in the master station (CP-8050) takes place system-internal through
redundancy control messages.
In addition, in the central station a delay with the switchover of the redundancy state from PASSIVE
(=STANDBY) to ACTIVE can be set with the parameter [PRE] Redundancy | Delay time
passive⇒active.
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 inter-
face 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 inter-
faces 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 neces-
sary.
The SICAM A8000 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").

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.
IIn the SICAM A8000 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

DC8-037-2, Edition 11.2020
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 SICAM A8000 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
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".
NOTE
i • In the remote terminal unit the parameter Advanced parameter | 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!
RTUs internal IEC 60870-5-101/104 format. These are converted by the protocol element to the IEC
protocol.
Data in receive direction are converted by the protocol element from IEC 60870-5-101 format on the transmis-
sion line to a SICAM RTUs internal IEC 60870-5-101/104 format and transferred to the basic system element.
12.4.11.1 Blocking
cols the "Blocking" according to IEC 60870-5-101 is implemented. This function is performed on the basic

DC8-037-2, Edition 11.2020
60870-5-101!
processing. Received messages with maximum length are transmitted SICAM RTUs internal in 2 blocks to the
12.4.11.2 Class 1, 2 Data
According IEC 60870-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
parameter | 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 trans-
mitted for SICAM A8000 master stations as class 2 data. SICAM A8000 internal mechanisms for the priori-
tization 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 IEC 60870-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
parameter | 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
12.4.11.3 Special Functions
• Summer time bit (SU)=0 for all messages in transmit direction

(summer time bit in the time tag)

DC8-037-2, Edition 11.2020
• 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
• Send GI Data as Class 1 Data
• Send End of init message as class 1 data
• Send ACTCON, ACTTERM 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, ACTTERM for commands
• Message Synchronization
• Filtering of Measured Values in Transmit Direction

With function enabled with the parameter Advanced parameter | 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.

With function enabled with the parameter Advanced parameter | IEC60870-5-101 | Time tag |
Day of week (DOW) = 0 the day of week (DOW) in the time tag is always set to "0" by the protocol
element for all messages with time tag in transmit direction.
NOTE
i This function is only active for process information messages in transmit direction. The day of week in clock
synchronization command message is not affected!
Originator address = 0 for all messages in transmit direction

With function enabled with the parameter Advanced parameter | 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
i 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 in parameter to 2.
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 A8000 stations, GI-data is always transmitted as class 2 data.
With the parameter Advanced parameter | 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 trans-
mitted 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.

DC8-037-2, Edition 11.2020
Send End of init message as class 1 data

When interfacing remote stations to third-party master stations it can be necessary to transmit the end of initi-
alization message to the master station as class 1 data.
For SICAM A8000 stations, the end of initialization message is always transmitted as class 2 data. The enabling
of the function is carried out on the protocol element by setting the parameter Advanced parameter |
IEC60870-5-101 | Prioritization of data to "Class 1,2". With the parameter Advanced param-
eter | IEC60870-5-101 | Advance parameters (prioritization of data) | Prioriti-
zation 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.
Send ACTCON, ACTTERM Message as Class 1 Data

When interfacing remote stations to third-party master stations it can be necessary to transmit the messages
for "activation confirmation" (ACTCON) and "activation termination" (ACTTERM) to the master station as class 1
data.
For SICAM A8000 stations, this messages will be sent as default with the same data class priority as used for
the associated indication.
parameter | IEC60870-5-101 | Prioritization of data to "Class 1,2". With the parameter
Advanced parameter | IEC60870-5-101 | Advance parameters (prioritization of
data) | Prioritization of data ACTCON, ACTTERM (TK45-51, TK101-107) 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 A8000 internal parameter setting.
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
i A detailed description of the function "Non Interruptible GI" can be found in the section "General Interroga-
tion, Outstation Interrogation".
Timeout Monitoring for GI-data

With parameter Advanced parameter | 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!
Convert General Interrogation Command to BROADCAST in Receive Direction

With function enabled with the parameter Advanced parameter | 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.
Do not store General Interrogation Commands in Receive Direction

When a general interrogation is in progress, further in SICAM A8000 received general interrogation commands
will be stored on basic system element (BSE) (for each CASDU and each group) and processed after termina-
tion of general interrogation in progress. When interfacing remote stations to third-party master stations it can

DC8-037-2, Edition 11.2020
be necessary that general interrogation commands should not be stored (only the actual requested GI-data
should be sent).
parameter | 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.
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 parameter | IEC60870-5-101 | ACTCON for clock synchronization
command as follows:
• Do not send (=default)
• Send after minute change and internal transfer of the time
• Send immediately and ignore (do not accept clock synchronization command)
More details for clock synchronization command can be found in section clock synchronization.
Emulate ACTCON+/- for Commands

If ACTCON is not supported by the basic system element or by the peripheral element used, then the emula-
tion of ACTCON can be performed by the protocol element (PRE) of the remote terminal unit as follows:
Emulation of Note
ACTCON- at <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, short 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)
* CASDU is not known to the PRE
ACTCON+/- for <TI=103> Clock synchronization command if
→ ACTCON+ send from PRE if
* CASDU = FFFF (=BROADCAST) *)
* CASDU ≠ FFFF (=BROADCAST)

DC8-037-2, Edition 11.2020
*) the moment for the transmission of ACTCON+ in the remote terminal unit can be parameterized with the
parameter Advanced parameter | IEC60870-5-101 | ACTCON for clock synchroniza-
tion command .
Legend:
PE Peripheral Element
The emulation of ACTCON in the remote terminal unit can be activated on the protocol element with the
parameter Advanced parameter | IEC60870-5-101 | ACTCON +/- emulation. So that the emula-
tion 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.
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+ at <TI=45> Single command
<TI=47> Regulating step 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 parameter | 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 trans-
mitted 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
i This function is not required in SICAM A8000 or if the this function is supported by the peripheral elements
used!
For the emulation of ACTCON- with unknown CASDU, the parameter Advanced parameter |
IEC60870-5-101 | ACTCON +/- emulation is to be enabled.
Message Synchronization
With the parameter Advanced parameter | IEC60870-5-101 | Message synchronization one
can select between the following methods of synchronization for disturbed reception:

DC8-037-2, Edition 11.2020
Message synchronization Description

Standard (IEC 60870-5-1) Received byte sequences "68,X,Y" (without gaps between the
bytes):
If X ≠ Y ist
→ Message synchronization after a pause (> 33 Bit Idle)
Mode-A (68 xx yy) Received byte sequences "68,X,Y" (without gaps between the
bytes):
If X ≠ Y ist
→ The receiver must discard 68 and begin with the IEC message
check from X (without pause > 33 Bit Idle)
Filtering of Measured Values in Transmit Direction

When interfacing remote stations to 3rd party master stations, it can be necessary to suppress (filtering) meas-
ured 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 number
• <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 number with time tag CP56Time2a
NOTE
i Only measured values with <TI:=34,35,36> will be sent from basic system element (BSE) to protocol
element (PRE). The different IEC 60870-5-101 message formats for transmission on line to 3rd party master
station will be generated by protocol element according the parameter .
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.


DC8-037-2, Edition 11.2020
• Set control location
• 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
• Information about the station status/failure to be obtained
Block Diagram
12.4.12.1 Protocol element control messages
Internal protocol element functions can be controlled with protocol element control telegrams. At the base
system element IEC 60870-5-101/104 telegrams with process information in control direc-
tion are converted to protocol element control telegrams and sent to the selected protocol element (see
13.1.4.10 Protocol Element Control Telegrams).
Possible substation functions:
Function PST detailed routing Note

SF Station Z-Par FI
I – Bit handling for time "OFF" 0 - -
I – Bit handling for time "ON" 1 - -
Send (general) interrogation 240
command
Reset command 243 This function is not presently
supported by PRE!

DC8-037-2, Edition 11.2020
12.4.12.2 Protocol element return information
Supported protocol element feedback:

Feedback_func-
tion_(PRE)
Status DSR 255 Status DSR
Station status 0-99 1 = Station enabled for access cycle
Station failure 0-99 1 = Station failed
protocol-specific return infor- 255 Interface "activated/deactivated":
mation 0 Return information for PRE control message "activate/deacti-
vate" interface
0 = interface "activated"
1 = interface "deactivated"
Protocol-specific feedback 1 255 Interface + protocol functions "activated/deactivated":
Return information for PRE control message "activate/deacti-
vate" interface + protocol functions
0 = interface + protocol functions "deactivated"
1 = interface + protocol functions "activated"
protocol-specific return infor- 0-99 Main transmission line parameterized
mation 0
Protocol-specific feedback 1 0-99 Main transmission line OK
Protocol-specific feedback 2 0-99 Main transmission line faulty
Protocol-specific feedback 3 0-99 Main transmission line NOK
Protocol-specific feedback 8 0-99 Standby transmission line parameterized
Protocol-specific feedback 9 0-99 Secondary path OK
Protocol-specific feedback 10 0-99 Secondary path faulty
Protocol-specific feedback 11 0-99 Secondary path NOK
protocol-specific return infor- 255 IDLE cycle
mation 0
• Station polling is stopped.
User data messages will be sent furthermore.
Protocol-specific feedback 1 255 NORMALMODE cycle
• cycle control running in normal mode

(cyclic RTU interrogation)
Protocol-specific feedback 2 255 Continuous station polling
• Continous station polling of a specific station is in

progress.

DC8-037-2, Edition 11.2020

Feedback_func-
tion_(PRE)
Protocol-specific feedback 3 255 Station polling stopped
• Cycle was stopped by PST-control message.

Protocol-specific feedback 6 255 Sending "Data to all"
• Transmission of BROADCAST data message is in progress

at this moment.
Protocol-specific feedback 7 255 Sending "data message"
• Data messoge transmission to single station is in progress

at this moment.
protocol-specific return infor- 0-99 The return information value can be selected via parameter.
mation value
• retries in % (of the last full hour)
IEEE 754 floating point format will be used for return informa-
tion value.
Supported protocol element feedback of the substation:

Feedback_func-
tion_(PRE)
Station failure 0 1 = Station failed (currently not supported by BSE!)
12.4.13 Interoperability IEC 60870-5-101 (UMP)
This companion standard IEC 60870-5-101 presents sets of parameters and alternatives from which subsets
must be selected to implement particular telecontrol systems. Certain parameter values, such as the number
of octets in the COMMON ADDRESS of ASDUs represent mutually exclusive alternatives. This means that only
one value of the defined parameters is admitted per system. Other parameters, such as the listed set of
different process information in command and in monitor direction, allow the specification of the complete
set or subsets, as appropriate for given applications. This clause summarizes the parameters of the previous
clauses to facilitate a suitable selection for a specific application. If a system is composed of equipment stem-
ming from different manufacturers it is necessary that all partners agree on the selected parameters.
Note:
In addition, the full specification of a system may require individual selection of certain parameters for certain
parts of the system, such as the individual selection of scaling factors for individually addressable measured
values.
The selected parameters should be crossed in the white boxes.

DC8-037-2, Edition 11.2020
"X")
System definition
(network-specific parameter, all configurations that are used are to be marked "X")
(network-specific parameter, all interfaces and data rates that are used are to be marked "X")

V.24/V.28 V.24/V.28 X.24/X.27
bit/s
300 bit/s 9 600 bit/s 9 600 bit/s
600 bit/s 19 200 bit/s 19 200 bit/s
1 200 bit/s 38 400 bit/s 38 400 bit/s

DC8-037-2, Edition 11.2020

V.24/V.28 V.24/V.28 X.24/X.27
bit/s
300 bit/s 9 600 bit/s 9 600 bit/s
600 bit/s 19 200 bit/s 19 200 bit/s
1 200 bit/s 38 400 bit/s 38 400 bit/s
(network-specific parameter, all options that are used are to be marked "X") Specify the maximum frame
length.
If a non-standard assignment of class 2 messages is implemented for unbalanced transmission, indicate the
Type ID and COT of all messages assigned to class 2.)
standard.
2 Octets
structured
unstructured
Frame length
Time interval in which repetitions are allowed (Trp) or number of repetitions


DC8-037-2, Edition 11.2020

9, 11, 13, 21 <1>

not dependent on parameterization all
NOTE:
In response to a class 2 poll, a controlled station may respond with class 1 data when there is no class 2 data
available.

companion standard.

1 Octet 2 Octets

1 Octet structured
3 Octets
1 Octet 2 Octets (with originator address)


DC8-037-2, Edition 11.2020

DC8-037-2, Edition 11.2020
M_EP_TF_1
CP56Time2a
Either ASDUs of the set <2>, <4>, <6>, <8>, <10>, <12>, <14>, <16>, <17>, <18>, <19> or of the set <30 –
40> are used.



DC8-037-2, Edition 11.2020

+ .... UMPSI0 only; only secondary application function

File transfer


DC8-037-2, Edition 11.2020


DC8-037-2, Edition 11.2020

DC8-037-2, Edition 11.2020
Remote initialization
+ ... only UMPS

' … secondary application function only
Read procedure
Read procedure
Note: No spontaneous transmission (blank field) is not supported

DC8-037-2, Edition 11.2020

Global
group 5 group 11
Information Object
group 6 group 12
separate table.
Day of week used

DC8-037-2, Edition 11.2020
C_SE ACTTERM used
Persistent output

Counter read
counter reset

DC8-037-2, Edition 11.2020

Threshold value
Smoothing factor
Test procedure
Test procedure
file transfer
Transparent file
Transparent file
Background scan
Background scan

DC8-037-2, Edition 11.2020

+ ... only UMPS

DC8-037-2, Edition 11.2020
12.5 IEC 60870-5-103
12.5 IEC 60870-5-103
12.5.1 Introduction
The IEC 60870-5-103 protocol is a standardized serial transmission protocol for communication with digital
protective devices with multi-point traffic (master/slave principle; “Partyline”).
For CP-8000/CP-802x, the following protocol firmware for IEC60870-5-103 (multi-point traffic) is available:
103MT0 CP-8000 IEC 60870-5-103 multi-point traffic Master (interfacing of protective
CP-8021 devices)
CP-8022
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. Data messages or station interrogation messages are sent
from the central station. Data from the remote station to the central station can only be transmitted as a reply
to a station interrogation.
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 operate with a communications
protocol according to IEC 60870-5-103. The supported functionality (interoperability) is described in the
chapter 12.5.11 Interoperability IEC 60870-5-103.
12.5.2 Functions
Communication of one master station and up to 100 protection devices
• Serial communication protocol according to IEC60870-5-103

103MT0 is master station

DC8-037-2, Edition 11.2020
12.5 IEC 60870-5-103
• Unbalanced transmission for Master (primary station)

– Point-to-point configuration (Master + 1 Slave)
– Multiple point-to-point configuration (each point-to-point configuration requires a separate
interface)
– Multipoint-partyline configuration
– Multipoint-star configuration

– Unbalanced interface according to V.24/V.28
– Data transmission route (half duplex)
– Byte frame (8E1)
– Data flow control bit used in receive direction
– Data flow control bit supervision
• Interoperability
– Compatibility level 1 (VDEW/ZVEI standard)
– Compatibility level 2 (fault records)
– Telegram conversion (traffic processing/telegram format)
– IEC 60870-5-103/IEC 60870-5-103 "standard" [default]
– IEC 60870-5-103/IEC 60870-5-101 "Tunneling mode" 109
• Interoperability according to 12.5.11 Interoperability IEC 60870-5-103
• Data Acquisition by Polling (Station Interrogation)

– Continuous query of a substation

– Test mode

– Send general interrogation command with delay
• Time synchronization according to IEC 60870-5-103

– Cyclical time synchronization (configurable with parameters)
– Correction of clock synchronization (via parameter)
– Inquiry
108 At max. 30 stations recommended

109 IEC 60870-5-101 telegrams are sent in IEC 60870-5-103 container telegrams (in private section); 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

DC8-037-2, Edition 11.2020
12.5 IEC 60870-5-103
• File transfer
– Fault records for SICAM DISTO
– Disturbance records to control center systems according to IEC 60870-5-101/104
• Optimized parameters for selected transfer directions

– Predefined parameters for selected transmission facilities
– 5 V power supply for connected transmission facility
ATTENTION: Check current consumption of transmission facility!

– Protocol element control telegrams
– START/STOP/CONTINUE access cycle
– Continuous polling of station x ON/OFF
– ACTIVATE/DEACTIVATE interface
– Station failure
– Station status
– DTR status (1 = Status line active)
– DSR status (1 = Status line active)
– Protocol-specific feedback 0 to 3, 6, 7
– Send Short Circuit Location Values with GI
– Resetting the Short Circuit Location Values
– Reset Short Circuit Location Values automatically
– Reset short-circuit location values with command
– 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 “Blocked Activation/Tripping of the Protection” information
– Transmit process images that have not been updated
– Emulation of the Going Binary Information
– Remote parameter configuration of Reyrolle protection devices
ment.

DC8-037-2, Edition 11.2020
12.5 IEC 60870-5-103
Operating mode Interface → optional DTE Interface signals

Unbalanced interchange circuit X2 RXD, TXD, CTS 110, RTS, DCD, DTR,
(2-wire)/ RS-422 (4-wire) asynchro- TXD+, TXD-, RXD+, RXD- (4-wire)
nous
Balanced interface (V.11) RS-485 X2 → CM-0829 (CM-0819) 111 RXD, TXD, CTS, RTS, DCD, DTR, DSR/
(2-wire)/ RS-422 (4-wire) asynchro- VCC, GND (to CM-08x9)
nous
Optical interface (multimode fibre X2 → CM-0821 RXD, TXD, CTS, RTS, DCD, DTR, DSR/
optic) ring VCC, GND (to CM-0821)
Unbalanced interchange circuit X6112 RXD, TXD, CTS, RTS, DCD, DTR, DSR,
(V.24/V.28) RS-232 asynchronous GND
(2-wire)/ RS-422 (4-wire) asynchro- TXD+, TXD-, RXD+, RXD- (4-wire)
nous
Own Station (Central station, IEC 60870-5-103 Master)
Own Station (Central station, IEC 60870-5-103 Master)

SICAM A8000 Series CP-8000/CPC80 103MT0
CP-802x/CPC80
Remote Station (Substation, IEC60870-5-103 Slave)

Legacy systems CP-50xx SM-2551/103SA0 electrical
(SICAM BC) SM-0551/103SA0
SM-2541/103S00
Local serial interface optical
Protection devices of - - according to
SIPROTEC series 12.5.11 Interoperability
IEC 60870-5-103
IEC 60870-5-103


DC8-037-2, Edition 11.2020
12.5 IEC 60870-5-103
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 inter-
rogation 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 inter-
rogated more often. Remote terminal units may only transmit when they are called.
The interrogation procedure can be influenced with the following parameters:
• Continuous cycle
• Priority level assignment (each station is assigned one of the 4 priority levels: high priority, medium
priority, low priority-A, low priority-B)
The continuous interrogation of the remote terminal units by the master station interrogation procedure is to
be performed by enabling the parameter [PRE] IEC60870-5-103 | Communication functions |
Data communication control | 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", "Number of calls", “Block of class 2 data” are to
be set in the parameter [PRE] IEC60870-5-101 | Station definition .
In every remote terminal unit, the station-selective address must be set with the parameter Common
settings | Station definition | Address of the link .
In each remote terminal an unambiguous station address (address of link layer) must be set. 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:
• 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.
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)

DC8-037-2, Edition 11.2020
12.5 IEC 60870-5-103
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".
Interrogation Procedure of Master Station - Station Change

The master station will do a station change 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
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

DC8-037-2, Edition 11.2020
12.5 IEC 60870-5-103
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 address of
ASDU link layer (=station address)
Number of octets for the address of the informa- 2 Octets IOA1 = Function type
tion object IOA2 = Information number
Acknowledgment message Single character or
short message (ACK)
Number of octets for time tag 4 Octets
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. Data messages
ready for sending to same remote station will be sent during demand in progress.
During the demand, user data telegrams continue to be transmitted to this substation.
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

DC8-037-2, Edition 11.2020
12.5 IEC 60870-5-103
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 acknowledgment is missing for longer than the expected acknowledgment
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.
necessary can be extended accordingly with the parameter [PRE] IEC60870-5-103 | Time settings,
retries | Monitoring times | Expected_ack_time_corr_factor . This is then the case if addi-
tional signal propagation delays, delay times or slow processing times of the 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 [PRE] IEC60870-5-103 | Time settings, retries | Retries |
Retries for data message SEND/CONFIRM (station selective) or for messages for station
initialization with the parameter [PRE] IEC60870-5-103 | Time settings, retries | Retries
| Retries for INIT-messages SEND/CONFIRM (station selective) .
The acknowledgment 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 trans-
mitted, the acknowledgment is transmitted as message with fixed length (ACK).
Failure Monitoring in the Master Station

The monitoring of the interface by the active master station takes place by means of the cyclic running inter-
rogation 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 acknowledgment time i.e. no other remote terminal units are interro-
gated 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 [PRE] 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 central station by means of the interrog-
ation procedure, however no message repetition (Retry) is carried out during the station interrogation for such
The interrogation cycle for failed stations can be set with the parameter [PRE] IEC60870-5-103 |
Communication function | Data communication control | Faulty stations | 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 are transmitted from the central station to failed remote terminal units. The data are saved in the data
storage of the communication function on the basic system element (BSE) until they are deleted by the dwell
time monitoring or are transmitted to the non-failed remote 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.
tion (receive timeout). The monitoring time is set with the parameter [PRE] 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 central station or transmission facility of the central 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.

DC8-037-2, Edition 11.2020
12.5 IEC 60870-5-103
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 [PRE] Redundancy | Cyclic message
for station selective failure monitoring.
Failure Monitoring in the Remote 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 [PRE] Advanced parame-
ters | Call monitoring time .
The call monitoring time will be retriggered in the remote terminal unit usually by station selective polling
messages.
The parameter [PRE] IEC60870-5-103 | Time settings, retries | Monitoring times |
Call timeout retrigger also with "request status of link" has to be used only when
formally required (specific functionality or required for 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).
of the remote terminal until these are deleted by the dwell time monitoring or can be transmitted to the
master station.
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 [PRE] 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)

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 corre-
sponding remote terminal unit is initialized with the reset command "Reset KE". The time for the switchover of

DC8-037-2, Edition 11.2020
12.5 IEC 60870-5-103
the station initialization can be set with the parameter [PRE] IEC60870-5-103 | Time settings,
retries | Monitoring times | 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
(Reset FCB) *)
in redundant configurations "Reset FCB" or "Request Status of Link" can be sent cyclic to enable station-selec-
tive 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.
After startup or redundancy switchover, the operation of the interface is begun after successful station initiali-
zation.

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
• Acknowledgment for RESET of REMOTE LINK is transmitted to
master station
tion" is also transmitted to the remote station.
The clock synchronization command or general interrogation command may only be transmitted after "INIT-
End".
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)".
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.
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 distribu-
tion/processing.

DC8-037-2, Edition 11.2020
12.5 IEC 60870-5-103
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 IEC 60870-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 IEC 60870-5-101/104 and forwarded to BSE with "cause of transmission = spontaneous"
<COT=3> and "T=1"
• test mode = YES (T=0)

All received messages from the protection devices with "cause of transmission = test" <COT=7>) will be
converted to IEC 60870-5-101/104 and forwarded to BSE with "cause of transmission = spontaneous"
<COT=3> and "T=0"
Data with test-bit set (T=1) will be routed SICAM A8000 internally without any evaluation and sent out via IEC
60870-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 [PRE] Station definition | Test mode .
When using the protocol firmware on SMx551 this parameter is part of the Station definition.
12.5.5.4 General Interrogation, Outstation Interrogation

The general interrogation function (RTU interrogation) is used for updating the central station after the
internal station-initialization or after the central station has detected a loss of information. The general inter-
rogation 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 communica-
tions 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 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 [PRE] IEC60870-5-103 | Communication functions |
General interrogation | Send initiation of general interrogation after delay .
If generic data is used, this function is to be enabled with the parameter [PRE] IEC60870-5-103 |
Communication functions | 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 communication line –
controlled by the master station. The time synchronization is carried out spontaneously and cyclically by the
central station.
The period for cyclic clock synchronization can be set with the parameter [PRE] IEC60870-5-101 |
Communication functions | Clock synchronization | Cycle time for sending clock
synchronization command .
The accuracy (typical) is ± 20 ms (clock synchronization 1x per minute). If the accuracy of the remote synchro-
nization is insufficient, a local time signal receiver must be used in the remote terminal unit.
Messages, which are sent 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 will be sent by the protocol element of the master station (either sponta-
neously after startup/at change of time or cyclic) as BROADCAST message (SEND/NO REPLY service) to the

DC8-037-2, Edition 11.2020
12.5 IEC 60870-5-103
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 [PRE] IEC60870-5-103 | Commu-
nication functions | Clock synchronization | Synchronization also with invalid
time .
Default: "Synchronization also with invalid time" = YES.
NOTE
i • IEC 60870-5-103 does not define procedures for acquisition of transmission delay and therefore no
correction of the time for clock synchronization!
Message from the Central Station selectively to a Remote Terminal Unit

sion in progress. Data to be sent from the base system element (BSE) is always prioritized at a ratio of 1:1
compared with station queries.
Inquiry
If the reaction of the substation to a transmitted telegram is to be acquired quickly by the master station, an
inquiry (configurable station-selective continuous query) can be performed by the master station. This station-
selective inquiry is retriggered by further telegrams to the same station (telegram configured with inquiry) or
canceled by telegrams to other stations.
Run type identification selection and adjustment of the continuous access time for type identification with the
Advanced parameters | Access procedure per type identification | * parameters.
Data-Flow Control
If a substation is unable to process additional data telegrams (messages), the DFC bit (data flow control) is set
in the telegram control field towards substation → master station. From this moment onwards, the protocol
firmware of the master station no longer sends data telegrams to the corresponding substation until the
substation once again resets the DFC bit.
The status of the DFC bit for the corresponding substations is requested cyclically by the master station with
REQUEST STATUS OF LINK. The protocol firmware of the master station also monitors whether the substation
resets the DFC bit within an adjustable time specified with the Advanced parameters | IEC parame-
ters | DFC continuous monitoring time parameter. 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. Use the Advanced parameters | IEC parameters
| Response with "DFC-bit = 1" parameter to select whether the substation must be requested in the
polling cycle or in a slower polling cycle with lower priority. The cycle time can be configured with the
Advanced parameters | IEC-Parameter | Polling cycle for stations with "DFC-bit =
1" parameter.
Control location / Check control location

been enabled.

DC8-037-2, Edition 11.2020
12.5 IEC 60870-5-103
Message from the Master Station to all Remote Terminal Units (unacknowledged)
“Unacknowledged” telegrams from the multi-point traffic master station to all are inserted into an on-going
polling cycle (station query) after having completed the on-going data transmission. In this process, the tele-
gram is sent several times from the master station with the configurable number of telegram retries according
to the Telegram retries | Retries for SEND/NO REPLY (broadcast) data telegram param-
eter. Afterwards the interrupted interrogation cycle is resumed.
The protocol element for IEC 60870-5-103 master function exclusively sends the time synchronization
command as telegram that is “not acknowledged to all”. All other messages are transmitted station-selective.
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 [PRE]
IEC60870-5-103 | Communication functions | Transmission of integrated totals |
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".
12.5.5.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 transfer-
ring disturbance records:
• Transfer of Disturbance Records to SICAM DISTO
• Transfer of disturbance records to IEC 60870-5-101/104 systems

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 trans-
mitted in a user data container defined for SICAM RTUs in the private range of the IEC 60870-5-101.
The IEC 60870-5-101/104 address of this user data container (CASDU1, CASDU2, IOA1, IOA2, IOA3) is to be
parameterized with the parameter [PRE] 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.
Transfer of Disturbance Records to SICAM DISTO

The transfer of disturbance records from protection equipment is controlled by SICAM DISTO (SICAM SCC
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.

DC8-037-2, Edition 11.2020
12.5 IEC 60870-5-103
The data transmission between SICAM DISTO and the protocol element with protection equipment connected
is carried out 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).
Disturbance Records Container

All IEC 60870-5-103 message formats necessary for the transfer of disturbance records from protection equip-
ment 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/104. 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.
The transmission of the user data container within SICAM RTUs takes place with type 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).

DC8-037-2, Edition 11.2020
12.5 IEC 60870-5-103
IEC 60870-5-101/104 IEC 60870-5-103

<TI:=142> User data container <TI:=23> Disturbance event overview
<TI:=26> Ready for transmission of disturbance data
<TI:=27> Ready for transmission of a channel
<TI:=28> Ready for transmission of tags
<TI:=29> Transmission of tags
<TI:=30> Transmission of disturbance values
<TI:=31> end of transmission
<TI:=142> User data container <TI:=24> Order to Transmit Disturbance Data
<TI:=25> Acknowledgment for Disturbance Data Trans-
mission
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 trans-
mission in progress cyclic request will be retriggered with each single disturbance record message.
Cyclic Request for Disturbance Records Overview:
• the cycle time 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 over-
view in case of successful/failed disturbance record transmission via positive/negative confirmation
by SICAM DISTO.

DC8-037-2, Edition 11.2020
12.5 IEC 60870-5-103
• the request for the disturbance record overview will be sent as broadcast (send/no reply) for each func-
tion type with station number 255.
Note:
– function type of all connected protection devices (e.g.: function type 128 = “distance protection“,
160 = “over current 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 conver-
sion.
– with 103Mx0: in transmit-and receive direction (Containtertype_Rec and Container-
type_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
be included in the station definition.
• a disturbance records overview (also empty directories) will be always sent to SICAM DISTO.

DC8-037-2, Edition 11.2020
12.5 IEC 60870-5-103
File Transfer between Protocol Element and SICAM DISTO

DC8-037-2, Edition 11.2020
12.5 IEC 60870-5-103
Segmentation
With user data containers a maximum of 180 bytes of transparent message data can be 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 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> for transmission of disturbance records
NOTE
i The user data container is described here in the internal format of the protocol element with the essential
information fields.

DC8-037-2, Edition 11.2020
12.5 IEC 60870-5-103
Elements of the Message

TI .. Type Identification <TI:=142> Single command
CASDU, IOA .. Message address
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 monitoring direction
06 .. activation ... in control direction
Time
7 octet 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 octets Length of the user data in octets (exclusive message
type)
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
... the 1st segment has segment number 1
Direction bit (R) 0 = control direction (SICAM DISTO → PRE)
1 = monitoring direction (PRE → SICAM DISTO)
Transfer of disturbance records to control systems according to IEC 60870-5-101/104

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 A8000 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 [PRE] IEC60870-5-103 | Communication functions | 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

DC8-037-2, Edition 11.2020
12.5 IEC 60870-5-103
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:=128> File directory
The assignment of the IEC 60870-5-101/104 message address for the spontaneous information object "distur-
bance record container" is carried out in the OPM II in the master station in the process-technical parameteri-
zation in transmit direction (to SCADA system) with the category firmware / Tra_container and in
receive direction (from SCADA system) 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.
The protocol element monitors a running transmission of a file both in the direction of the higher-level master
station (SCADA system) as well as in the direction of the protective device. A failure during a running transmis-
sion of a file is detected by the protocol element by means of a monitoring time (Timeout). Wit the parameter
[PRE] IEC60870-5-103 | Communication functions | File transfer | Timeout for
file transfer 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 [PRE]
IEC60870-5-103 | Communication functions | File transfer | spontaneous transmis-
sion 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.
12.5.6 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
SCC, REYDISP – the Engineering Tool for Reyrolle Protective Devices – can be implemented directly on the
control centre system SICAM SCC "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 SCC, 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 A8000 with the user data containers provided for this purpose.
REYDISP does not require its own interface to SICAM A8000 – the communication takes place over the inter-
face of the control centre system (REYDISP is coupled to the software of the control centre system over a soft-
ware 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 A8000 in the private range of IEC
60870-5-101/104. Only the IEC 60870-5-103 message format included in the user data container will be trans-
mitted to the protection equipment, and not the data container itself.
The transmission of the user data container within SICAM A8000 takes place with type identification <TI=142>
in the private range of IEC 104-5-104. SICAM A8000 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).

DC8-037-2, Edition 11.2020
12.5 IEC 60870-5-103
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-parame-
terized 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 sponta-
neous 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 Containter-
type_Tra . With the parameterization of the message addresses, the transfer of parameters to REYDISP is
also activated.
In SICAM A8000 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).
Segmentation
With user data containers a maximum of 180 bytes of transparent message data can be 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 missing segments the partially
transmitted parameter message is discarded.

DC8-037-2, Edition 11.2020
12.5 IEC 60870-5-103
User data container <TI=142> "REYDISP parameter container"
NOTE
i The user data container is described here in the internal format of the protocol element with the essential
information fields.

TI .. Type Identification <TI:=142> Single command
CASDU, IOA .. Message address
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 octet dual time
Message type = 132 REYDISP parameter container

DC8-037-2, Edition 11.2020
12.5 IEC 60870-5-103

Length of the user data part in octets Number of the user data in octets (exclusive message
type)
Segmentation field
Number of segments Total number of segments
Segment number Current number of the transmitted segment
... the 1st segment has segment number 1
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"

DC8-037-2, Edition 11.2020
12.5 IEC 60870-5-103
Container type "0" IEC 60870-5-103 message "Message with variable block length"
Container type "2" IEC 60870-5-1/FT1.2 "Single character"
12.5.7 Optimized Parameters for selected Transmission Facilities
The protocol element supports selected transmission facilities – for which the parameters are set fixed – the
selection of the transmission facility takes place with the parameter [PRE] Interface parameter |
Time setting for interface parameter . With the selection of the "free definable transmission
facility" certain parameters can be set individually.
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) must be set depending on the used sub-module for communication, for
transmit/receive direction separated with parameter Common settings | Baud rate receive direc-

DC8-037-2, Edition 11.2020
12.5 IEC 60870-5-103
tion and the parameter Common settings | Baud rate transmit direction or for transmit/
receive direction together with the parameter [PRE] Interface parameter | Baud rate .
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 parame-
ters | Advanced time settings | Pause time after broadcast message (tp_bc) and the
parameter Advanced parameters | Advanced time settings | Pause time after broad-
cast 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
parameters that are available can be individually set. This is necessary when 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 [PRE] Interface parameter
| Time setting for interface parameter is to be set to "free definable" . Only then
are all supported parameters displayed and can be parameterized with the required values (refer to table with
Default Parameters for Transmission Facilities).
For the adaptation to various modems or time requirements of external systems, the following parameters can
be set individually:
| Pause time (tp)
| Set up time (tv)
| Run out time (tn)
| DCD Handling
| Continuous level monitoring time (tcl)
| Transmission delay if continuous level (tcldly)
| Bounce suppression time (tbounce)
| Disable time (tdis)
How the individual time settings are effective during the data transmission is shown in Figure 12-2.
Parameter "5V/12V Supply (DSR)" [BSE]

If necessary the voltage supply of the transmission facility (5V/12V) – if this is enough – can be supplied over
the status line DSR (VCC). The voltage supply is enabled with parameter [BSE] System settings |
Serial Interfaces | Port | CP-X5 | DSR voltage supply. The voltage supply is only output to
the DSR status line with corresponding parameter setting. The DSR status line cannot be used by the protocol
as status line.
NOTE
i Required voltage supply and maximum current consumption of the transmission facility must be observed!

DC8-037-2, Edition 11.2020
12.5 IEC 60870-5-103
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:
• [PRE] IEC60870-5-103 | Time settings, retries | Monitoring times | Idle moni-

toring time
• [PRE] IEC60870-5-103 | Time settings, retries | Monitoring times | Character

monitoring time
• [PRE] IEC60870-5-103 | Time settings, retries | Monitoring times |

Expected_ack_time_corr_factor (see acknowledgment procedure in the master station)
The character monitoring time is used for the message interruption monitoring and message resynchroniza-
tion in receive direction. A message interruption is detected when the time between 2 bytes of a message is
greater than the set signal monitoring time. With message interruption the receive processing in progress 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 – insofar as the transmission facility provides this signal receive-side – can evaluate the
interface signal DCD and e.g. utilize it 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)
Default parameters for transmission facilities with 103M00, 103S00
Default parameters for transmission facilities with 103MA0, 103SA0
Legend:
Electrical Interface Parameter Electrical Interface [BSE]
RTS ↑↓ = RTS is for the control of the carrier switching of the modem scanned with each
message (ON / OFF)
tp Parameter Pause time (tp)
tv Parameter Set-up time (tv)
tn Parameter Overtravel time (tn)
tp_bc Parameter Pause time after broadcast message (tp_bc)
(valid only for MASTER station!)
tdis Parameter Blocking time (tdis)
DCD Parameter DCD-evaluation
tbs Parameter Bounce suppression time (tbs)
tduration Parameter Continuous level monitoring time (tduration) (tduration)
tdelay Parameter Transmit delay at level (tdelay)
A_I Parameter Asynchronous_Isochronous, (A=asynchron, I=isochron) [BSE]
T Parameter Bit timing (only with isochron) (I=internal, E=external) [BSE]

DC8-037-2, Edition 11.2020
12.5 IEC 60870-5-103
Z Parameter Send clock synchronization command station-selective (s=selective,

B=BROADCAST) – valid only for MASTER station!
5V/12V Parameter 5V/12V Supply (DSR) [BSE]
NOTE
i The parameter on the basic system element [BSE] are not selected automatically by the selection of the
transmission facility.. These parameter must be set by the user!

DC8-037-2, Edition 11.2020
12.5 IEC 60870-5-103
The following diagram shows in detail the timing for the data transmission when using transmission facilities
with switched carrier.
Figure 12-2 Timing during transmission
Master stations can be designed redundantly to increase the availability.

DC8-037-2, Edition 11.2020
12.5 IEC 60870-5-103
In this section, the possible redundancy concepts themselves that can be realized are not described, rather
only those functions supported by the protocol element for the support of redundant communication routes.
In the master station one of the following redundancy controls can be selected:
• PRE redundancy
• Ring redundancy (main/substitute route with 2 interfaces)
• Deactivation of Interface
The switchover of the redundancy state takes place system-internal by means of redundancy 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 [PRE] Redundancy | Delay time passive=>active .
configuration with the parameter [PRE] Redundancy | Operation if passive as follows:
• Interface "tristate" – only listening mode
• Interface "active" – only listening mode
• Interface "active" – interrogation mode

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.
tion. The monitoring time is set with the parameter [PRE] Redundancy | Listening mode (failure
monitoring time) . On receive timeout (active central station or transmission facility of the central 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 trans-
mission facility of the remote terminal unit has failed) the remote terminal unit is signaled as failed.
Station-specific faults present are reset in a redundant STANDBY master station, if a faultless message from
12.5.8.2 Ring Redundancy

Data transmission between the master station and the substation is carried out in “ring redundancy” redun-
dancy operating mode (main/substitute route with 2 interfaces) via the main route or the substitute route.
Substitute route operation is activated with the Redundancy | Substitute route parameter.
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.

DC8-037-2, Edition 11.2020
12.5 IEC 60870-5-103
Schematic configuration for main/substitute route operation with 2 interfaces:
[103MT0_ring_redundancy, 1, en_US]
A feature of this redundancy mode is supporting a switch over from main transmission line to backup trans-
mission 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 transmis-
sion 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 standby transmission line is defined as follows:
Main Line Backup Line Note
same BSE
same BSE
Legend:
ZSE ... Supplementary system element (with serial interfaces, this is always configured with a PRE)
PRE ... Log element
BSE ... Basic system element

DC8-037-2, Edition 11.2020
12.5 IEC 60870-5-103
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 transmission line. The time
synchronization control message will be sent 1st 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. In this process, all substations are polled once via the substitute route at certain intervals.
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 the protocol element for the main route identifies a substation at an interface (main or substitute route) as
failed, a warning is reported to the base system element (BSE) for this station. A remote station will be
signaled as faulty if no communication to this station is possible via main transmission line and backup trans-
mission line. Faulty remote stations will be polled further in the basic cycle but without retries. If communica-
tion 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 transmis-
sion line or via backup transmission line.
Both protocol elements perform a cyclic monitoring of the assigned partner protocol element for this redun-
dancy mode. If the active protocol element fails, the previously passive protocol element takes over the func-
tion. A general interrogation is triggered by the active protocol element during the switchover. In this situa-
tion, data is then only transmitted via the interface of the own protocol element. The assigned partner
protocol element for this redundancy mode will be supervised further on. Once the failed protocol element is
available again, the main/substitute route function 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". In this case the data is
collected from the base system element, the data is sent, and interference signaling is carried out from the
protocol element for the substitute route.
A cyclic switchover between the assigned protocol elements is not supported! The passive protocol element
will only take over protocol functions if the active protocol element fails.
NOTE
i Parameter configuration notes
• All data to the substations must be routed in the master station via the two protocol elements.
• Do not configure main/substitute routing in the topology for this redundancy operation type.
• The line-by-line redundancy is not 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.
12.5.8.3 Port-Redundancy
Deactivation of interface with protocol element control message

With the possibility of deactivation of interface by a PRE control messages, simple redundancy solutions can be
realized.
With deactivated interface the transmitter of the interface is switched to "tristate" and the data for transmis-
sion 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.

DC8-037-2, Edition 11.2020
12.5 IEC 60870-5-103
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!
Data in transmit direction is transferred by the base system element to the protocol element in SICAM A8000-
internal IEC 60870-5-101/104 format. These are converted by the protocol element to the IEC 60870-5-103
telegram format on the line and transmitted according to the transmission procedure of the protocol.
Data in receive direction is converted by the protocol element from the telegram format using the transmis-
sion line to a SICAM A8000-internal IEC 60870-5-101/104 format and the data is transferred to the base
system element.
The protocol element supports the following operating modes for telegram conversion:
Telegram conversion operating Communication protocol to the protection Master Sub-
mode equipment station station
113
IEC 60870-5-101 ⇔ IEC 60870-5-103 • Transmission procedure: IEC 60870-5-103 ✓ ✓

• Telegram formats: IEC 60870-5-103
IEC 60870-5-101 ⇔ IEC 60870-5-101 • Transmission procedure: IEC 60870-5-101 - ✓
• Telegram formats: IEC 60870-5-101
IEC 60870-5-101 ⇔ IEC 60870-5-103 • Traffic processing: IEC 60870-5-103 ✓ ✓
(101) “Container Mode”
• Telegram formats: IEC 60870-5-101 “Trans-
parent Mode”
IEC 60870-5-101 telegrams are transferred
in IEC 60870-5-103 container telegrams (in
private section)
– For SICAM RTUs configurations with
SICAM BC the conversion of IEC
60870-5-101 ⇒ IEC 60870-5-103 ⇒
IEC 60870-5-101 can be omitted
The operating mode for the telegram conversion (and also for the transmission procedure) can be adjusted in
the substation with the [PRE] General settings | Operating mode at the interface param-
eter. A parameter has not been provided at the master station for this purpose, use the corresponding
protocol firmware for for multi-point traffic as the master station for IEC 60870-5-101.
The assignment of the telegram address for the spontaneous information objects for the IEC 60870-5-101 ⇔
IEC 60870-5-103 telegram conversion operating mode is carried out in the SICAM TOOLBOX II, OPM II with
“SIP telegram address conversion”.
12.5.9.1 Message Conversion IEC 60870-5-101 ↔ IEC 60870-5-103

Data in transmit direction are transferred from the basic system element to the protocol element in the SICAM
A8000 internal IEC 60870-5-101-/104 format. These are converted by the protocol element to the IEC
protocol.
113 Protection equipment

DC8-037-2, Edition 11.2020
12.5 IEC 60870-5-103
Data in monitoring direction are received from the protocol element according to the transmission procedure
according to IEC 60870-5-103, converted by the protocol element to the internal IEC 60870-5-101/104 format
and then transferred to the basic system element.
The supported functionality (interoperability) is described in chapter 12.5.11 Interoperability IEC
60870-5-103.
NOTE
i Generic data are only partially supported!
The parameter setting 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-Nr. SICAM A8000 internal station Link address SICAM A8000 internal station
number (0 to 99) number (0 to 99)
CASDU1 CASDU
CASDU Station address of the protection
CASDU2 equipment
FUN
IOA1 IOA Function type
INF
IOA2 Information number
IOA3
TI Type identification 114 TI Function type 114
divers Additional info per category
Message conversion in control direction (public range of IEC 60870-5-103)
IEC 60870-5-101/104 IEC 60870-5-103 C S

– – <TI:=6> Time synchronization 115 ✓ ✓
– General interrogation <TI:=7> General interrogation ✓ ✓
command Command
(SICAM A8000 internal)
<TI:=50> Set point command, short <TI:=10> Generic data (setpoint ✓ -
floating point number command)
<TI:=45> Single command <TI:=20> General command ✓ ✓
<TI:=47> Regulating step command <TI:=20> General command ✓ -
– General interrogation <TI:=21> Genenic command ✓ -
command (general interrogation
(SICAM A8000 internal) command) 116
<TI:=142> User data container <TI:=24> Order to transmit disturbance ✓ ✓
“Disturbance record transmis- <TI:=25> data ✓ ✓
sion to SICAM DISTO” Acknowledgment for distur-
bance data transmission
114 see message conversion in send-/receive direction

115 Is generated from the protocol element; SICAM A8000 internally the time management message (function code 156) is used
116 Only general interrogation command for generic data is supported!

DC8-037-2, Edition 11.2020
12.5 IEC 60870-5-103
IEC 60870-5-101/104 IEC 60870-5-103 C S

<TI:=45> Single command – Reset of the fault locations (acts ✓ -
<TI:=46> Double command only protocol element internal)
117
<TI:=122> Interrogation of file directory, ✓ –

118
<TI:=124> File selection, file interrogation,

section interrogation
File confirmation, section
confirmation
Message conversion in control direction (private range of IEC 60870-5-103)
IEC 60870-5-101/104 IEC 60870-5-103 C S

<TI:=45> Single command <TI:=232> Command to protective device ✓ -
<TI:=46> Double command ALSTOM ✓ -
Command with SELECT/ ✓ -
<TI:=45, 46>
EXECUTE ALSTOM
Command without SELECT/
<TI:=45, 46> EXECUTE ALSTOM
<TI::=142> User data container <TI:=254> REYDISP Parameter Frame ✓ -
“Parameter messages to <TI:=255> REYDISP Parameter Last Frame ✓ -
Reyrolle protective devices”
117 This command is not transmitted. The fault locations of the parameterized Link Address are reset to the corresponding initial value!
118 Only Transmission of Files in Monitoring Direction (disturbance record transmission of a protective device) according to IEC
60870-5-101/104

DC8-037-2, Edition 11.2020
12.5 IEC 60870-5-103
Message conversion in monitoring direction (public range of IEC 60870-5-103)
IEC 60870-5-101/104 119 IEC 60870-5-103 C S

<TI:=30> Single-point information with <TI:=1> Binary Information with time ✓ ✓
<TI:=31> time tag tag
<TI:=38> Double-point information with
<TI:=39> time tag
<TI:=40> Events of protection equipment
with time tag
Packed start events of protec-
tion equipment with time tag
Packed output circuit informa-
tion of protection equipment
with time tag
<TI:=30> Single-point information with <TI:=2> Binary information with relative ✓ –
<TI:=31> time tag time
<TI:=36> Double-point information with
<TI:=38> time tag
<TI:=39> Measured value, short floating
point number with time tag
<TI:=40>
Events of protection equipment
with time tag
Packed start events of protec-
tion equipment with time tag
Packed output circuit informa-
tion of protection equipment
with time tag
<TI:=34> Measured value, normalized <TI:=3> Measurands I ✓ ✓
<TI:=35> value with time tag
<TI:=36> Measured value, scaled value
with time tag
Measured value, short floating
<TI:=34> Measured value, normalized <TI:=4> Real-time measured values with ✓ ✓
<TI:=35> value with time tag relative time
with time tag
<TI:=30> Single-point information with <TI:=5> Identification information 120 ✓ ✓
<TI:=31> time tag
Double-point information with
time tag
– – <TI:=6> Time synchronization, binary – ✓
information 120
– – <TI:=8> General interrogation end 120 – ✓
119 All with time tag format CP56Time2a

120 is generated in the RTU directly by the protocol element!

DC8-037-2, Edition 11.2020
12.5 IEC 60870-5-103
IEC 60870-5-101/104 119 IEC 60870-5-103 C S

<TI:=34> Measured value, normalized <TI:=9> Measurands II ✓ ✓
<TI:=35> value with time tag Measured
<TI:=36> value, scaled value with time
tag Measured value, short
floating point number with
time tag
<TI:=36> Measured value, short floating <TI:=10> Generic data (measured value) ✓ –
point number with time tag 121
– – <TI:=11> Generic identification – –

<TI:=120> File ready 122 <TI:=23> Disturbance event overview ✓ –
<TI:=121> Section ready <TI:=26> Ready for transmission of ✓
<TI:=123> Last section, last segment <TI:=27> disturbance data ✓
<TI:=125> Segment <TI:=28> Ready for transmission of a ✓
<TI:=126> <TI:=29> channel ✓
File directory
<TI:=30> Ready for transmission of tags ✓
<TI:=31> Transmission of tags ✓
Transmission of disturbance
values
End of transmission
<TI:=142> User data container <TI:=23> Disturbance event overview ✓ ✓
“Disturbance record transmis- <TI:=26> Ready for transmission of ✓ ✓
sion to SICAM DISTO” <TI:=27> disturbance data ✓ ✓
<TI:=28> Ready for transmission of a ✓ ✓
<TI:=29> channel ✓ ✓
<TI:=30> Ready for transmission of tags ✓ ✓
<TI:=31> Transmission of tags ✓ ✓
Transmission of disturbance
values
End of transmission
Message conversion in monitoring direction (private range of IEC 60870-5-103)
IEC 60870-5-101/104 123 IEC 60870-5-103 C S

<TI:=30> Single-point information with <TI:=33> Real-time information ✓ –
<TI:=31> time tag (SEG protective devices)
Double-point information with
time tag
<TI:=30> Single-point information with <TI:=65> Single-point information with ✓ –
<TI:=30> time tag <TI:=66> time ALSTOM ✓
<TI:=31> Single-point information with <TI:=67> Single-point information ✓
<TI:=31> time tag <TI:=68> without time ALSTOM ✓
Double-point information with Double-point information with
time tag time ALSTOM
Double-point information with Double-point information
time tag without time ALSTOM

121 Only data in the format GDD [DATATYPE] = 7 (short Real IEEE STD 754) are supported!
122 Transmission of Files in Monitoring Direction (disturbance record transmission of a protective device) according to IEC
60870-5-101/104

DC8-037-2, Edition 11.2020
12.5 IEC 60870-5-103
IEC 60870-5-101/104 123 IEC 60870-5-103 C S

<TI:=33> Bit sting of 32 bit with time tag <TI:=71> 32 bit binary value ALSTOM ✓ –
<TI:=72>
<TI:=34> Measured value, normalized <TI:=140> Measured values SIEMENS ✓ –
<TI:=35> value with time tag
with time tag
<TI:=36> Measured value, short floating <TI:=204> Measured value short floating ✓ –
point number with time tag point
(Reinhausen TAPCON 240)
<TI:=36> Measured value, short floating <TI:=205> Measured value 28 bit ✓ –
<TI:=37> point number with time tag (SIEMENS SIPROTEC)
Integrated totals with time tag
<TI:=142> User data container “Parameter <TI:=253> REYDISP Termination of Private ✓ –
messages to Reyrolle protective Data Response Frame
devices” REYDISP Parameter Frame
<TI:=254> ✓
REYDISP Parameter Last Frame
<TI:=255> ✓
Causes of transmission in control direction
IEC 60870-5-101/103 Central Substation

Station
COT Cause of transmission
8 Time synchronization, command ✓ ✓
9 GI-initiation ✓ ✓
19 ALSTOM command <TI:=232> 124 ✓ –
20 General command ✓ ✓
31 Disturbance data transmission ✓ ✓
40 Generic write command ✓ –
42 Generic read command – –
Causes of transmission in monitoring direction

Station
COT 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 ✓ ✓

124 Only for ALSTOM protection equipment!

DC8-037-2, Edition 11.2020
12.5 IEC 60870-5-103

Station
11 Local operation – –
12 Remote operation ✓ ✓
13 Remote operation negative 125 ✓ –
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 – –
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
central station to the protection equipment spontaneously with a change of time and cyclic in a parameter-
settable grid.
Elements of the Message (SICAM A8000 internal) BSE → Elements of the Message (IEC 60870-5-103) C → S
PRE
Function code = 156 Time management (SICAM Type identification
Information code = 0 .. Clock A8000 internal) not evalu- TI 6 .. Time synchronization
synchronization ated
Message address
CASDU = 255.. Station
address of the protection
equipment (BROADCAST)
FUN = 255 .. Global function
type
INF = 0 .. Information System function (time
number synchronization)
Cause of transmission (COT)
COT = 8 .. Time synchroniza-
tion
Time With this SICAM RTUs Time In the message the time of
CP56Time2a ... Dual time internal message, the CP56Time2a ... Dual time the 1st bit is entered on the
with 7 octets internal clock of the protocol with 7 octets line
element is set and a time
synchronization of the
protection equipment
connected in initiated.
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).
125 Only for ALSTOM protection equipment!

DC8-037-2, Edition 11.2020
12.5 IEC 60870-5-103
Elements of the Message (SICAM RTUs internal) BSE → Elements of the Message (IEC 60870-5-103) C → S
PRE
Function code = 155 General interrogation Type identification
Information code = 1 .. request (SICAM RTUs TI 7 .. General interrogation
Source-GI request internal) not evaluated
Message address Message address
CASDU .. Station address of CASDU .. Station address of
the protection equipment the 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 .. Initiation of
general interrogation
Qualifier of interrogation Not evaluated
Cycle number (SCN) Beginning from 0, the cycle
SCN = 0 to 255 .. Cycle number is increased by 1
number with each transmitted
command (per protective
device).
All data of a protective
device subject to GI that are
transmitted following a
command are transmitted
with the cycle number of the
command.
Note: The cycle number is
not evaluated in the master
station.
NOTE
i 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!
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 SICAM TOOLBOX II, OPM II in the central station with the category firmware / Trans_command and
in the substation with the category firmware / Rec_command.

DC8-037-2, Edition 11.2020
12.5 IEC 60870-5-103
Elements of the Message (IEC 60870-5-101/104) BSE Elements of the Message (IEC 60870-5-103) C → S
↔PRE
Type identification Type identification126
TI 45 .. Single command TI 20 ... General command
TI 46 .. Double command TI 232 ... Command to
protective device
TI 45, 46 .. Command with
SEL / EXE Private range 127
TI 45, 46 .. Command Private range 127
without SEL / EXE Private range 127
Type identification Type identification126
TI 47 .. Regulating step TI 20 ... General command
command
Parameter-settable Parameter-settable
CASDU (CASDU1, CASDU2) CASDU .. Station address of
Parameter-settable
IOA (IOA1, IOA2, IOA3) the protection equipment
FUN .. Function type Parameter-settable
INF .. Information number Parameter-settable
Return information identifi- Parameter-settable
cation (RII)
PRE→BSE (after reception of
<6> ..Activation RM or TIO) <20> .. General command
Only for ALSTOM <TI:=232>
<7> .. Confirmation of activa- Not supported <19> .. 127
tion
Not supported
<8> .. Abortion of activation
<9> .. Confirmation of the
abortion of activation PRE→BSE (after reception of
RM or TIO)
<10> .. Termination of the
activation PRE→BSE (after reception of
RM or TIO)
P/N .. positive/negative
confirmation Not evaluated
T ..Test See Setting Control Location!
Originator address
126 TI is defined with the additional info in the OPM (see Special Functions)
127 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!

DC8-037-2, Edition 11.2020
12.5 IEC 60870-5-103
Elements of the Message (IEC 60870-5-101/104) BSE Elements of the Message (IEC 60870-5-103) C → S
↔PRE
Qualifier of command Qualifier of command Only for <TI:=45>, <TI:=46>
QU <0> .. No additional defi- QU <0> .. No additional defi- 127
nitions nitions
QU <1> .. Short command QU <1> .. Short command
execution time execution time
QU <2> .. Long command QU <2> .. Long command
execution time execution time
QU <3> .. Persistent QU <3> .. Persistent
command Not supported only for IEC command
S/E <0> .. Execute 60870-5-103 <TI:=45, 46> S/E <0> .. Execute
S/E <1> .. Select 126 S/E <1> .. Select
Single Double Double command (DCO)
command command <0> .. Not permitted
(SCO) (DCO) <1> .. OFF
<0> .. OFF <0> .. Not <2> .. ON
<1> .. ON permitted
<3> .. Not permitted
<1> .. OFF
<2> .. ON
<3> .. Not
permitted
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, to ALSTOM protective device in the Private range with SELECT /
46> EXECUTE
<3> = General command <TI:=45, to ALSTOM protective device in the Private range without SELECT /
46> EXECUTE
<4> = General command <TI:=20> according to IEC 60870-5-103 to remote station (protection equip-
ment) 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 [PRE] IEC60870-5-103 | Communication functions |
Command transmission | Select/Execute command emulation | 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 ↔AUS 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.

DC8-037-2, Edition 11.2020
12.5 IEC 60870-5-103
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 acknowledgment of command)
→ ACTCON- emulate from PRE to BSE
ACTTERM+ • Return information is received from the protection equipment with COT=<20> (=
positive acknowledgment 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> (=
negative acknowledgment of command)
→ ACTTERM- emulate from PRE to BSE
Legend:
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 SICAM TOOLBOX II, OPM II with the category firmware /
Trans_generic_setpoint command(GDD=7).
Elements of the Message (IEC 60870-5-101/104) BSE → Elements of the Message (IEC 60870-5-103) C → S
PRE
Type identification Type identification
Setpoint command
TI 50 .. Set point command, TI 10 .. Generic data
short floating point number
Parameter-settable
Parameter-settable
Parameter-settable
FUN = 254 .. Generic func-
tion type
number Generic function

DC8-037-2, Edition 11.2020
12.5 IEC 60870-5-103
Elements of the Message (IEC 60870-5-101/104) BSE → Elements of the Message (IEC 60870-5-103) C → S
PRE
<6> .. Activation <40> .. Generic write
PRE→BSE (immediately by
<7> .. Confirmation of activa- command
PRE)
tion
Not supported
<8> .. Abortion of activation
Not supported
<9> .. Confirmation of the
abortion of activation
<10> .. Termination of the Not supported
activation Positive
P/N .. positive/negative Not evaluated
T ..Test
Originator address
Generic data description
(data record)
Not supported
RII = 0 .. Return information
identification
NGD = 1 .. Number of
generic data records Parameter-settable GIN
GIN .. Generic identification [ group, entry ]
number
KOD = 1 .. Actual Value
GDD [DATATYPE] = 7 .. IEEE Short Real IEEE STD 754
STD 754
GDD [DATASIZE] = 4 .. 4
Number of data elements
Octets
No following data elements
GDD [NUMBER] = 1
GDD [CONT] = 0
Data Generic data
32 bit floating point value 32 bit floating point value
short floating point number GID = short floating point
IEEE STD 754 number
(IEEE STD 754)
Identifier for setpoint
command (QOS)
Not supported
QL <0> .. not defined
Not supported
QL <1..127>
Not supported
S/E <0> .. execute
Not supported
S/E <1> .. select
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).

DC8-037-2, Edition 11.2020
12.5 IEC 60870-5-103
Elements of the Message (SICAM A8000 internal) BSE → Elements of the Message (IEC 60870-5-103) C → S
PRE
Function code = 155 General interrogation Type identification
General interrogation
Information code = 1 .. request TI 21 .. Genenic command command for generic data
Source-GI request (SICAM A8000 internal) not
evaluated
CASDU .. Station address of CASDU .. Station address of
the protection equipment the protection equipment
FUN = 254 .. Generic func-
tion type
number Generic function
<6> .. Activation COT = 9 .. Initiation of
T ..Test general interrogation
P/N .. Positive/negative Not evaluated
Originator address Not evaluated
Qualifier of interrogation Not evaluated Generic data description
(data record)
Beginning from 0, the cycle
RII = 0 .. Return information
number is increased by 1
identification (=cycle
with each transmitted
number)
command (per protective
device).
All data of a protective
device subject to GI that are
transmitted following a
command are transmitted
with the cycle number of the
command.
NOG = 0 .. Number of Note: The cycle number is
generic identifications not evaluated in the master
station.
NOTE
i ACTCON and ACTTERM for general interrogation request are not emulated by the protocol element of the
master station!
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 SICAM TOOLBOX II, 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 "Reydisp container" (see also section 12.5.6 Transfer of
Parameters for Reyrolle Protection Equipment).

DC8-037-2, Edition 11.2020
12.5 IEC 60870-5-103
Elements of the Message (IEC 60870-5-101/104) BSE ↔ Elements of the Message (IEC 60870-5-103) C ↔ S
PRE
User data container for Monitoring direction
TI 142 .. User data container REYDISP parameter data TI 253 .. REYDISP termination
of Private Data Response
Frame Control/monitoring direction
TI 254 .. REYDISP Parameter Control/monitoring direction
Frame
TI 255 .. REYDISP Parameter
"Last Frame"
Parameter-settable
FUN = xx .. is not evaluated!
128
INF = xx .. is not evaluated!

128

<3> .. Spontaneous COT = xx .. is not evaluated!
T ..Test
P/N .. positive/negative 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.
Type identification 23: list of recorded disturbances
Type identification 24: Order to Transmit Disturbance Data
Type identification 25: Acknowledgment for Disturbance Data Transmission
Type identification 26: ready for transmission of disturbance data
Type identification 27: ready for transmission of a channel
Type identification 28: ready for transmission of tags
Type identification 29: transmission of tags

Type identification 30: transmission of disturbance values
Type identification 31: end of transmission

The assignment of the message address for the spontaneous information object “User data container” is
carried out in the SICAM TOOLBOX II, 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 12.5.5.8 File
Transfer).
128 These items of information are copied 1:1 from the user data container into IEC 60870-5-103 without assessment

DC8-037-2, Edition 11.2020
12.5 IEC 60870-5-103
Elements of the Message (IEC 60870-5-101/104) BSE ↔ Elements of the Message (IEC 60870-5-103) C ↔ S
PRE
User data container for Monitor direction
TI 142 .. User data container disturbance record transmis- TI 23 .. Disturbance event
Control direction
sion overview
TI 24 .. Order to Transmit
Disturbance Data Control direction
TI 25 .. Acknowledgment for
Disturbance Data Transmis- Monitor direction
sion
TI 26 .. Ready for transmis-
sion of disturbance data Monitor direction
TI 27 .. Ready for transmis- Monitor direction
sion of a channel
TI 28 .. Ready for transmis- Monitor direction
sion of tags Monitor direction
TI 29 .. Transmission of tags Monitor direction
TI 30 .. Transmission of
disturbance values
TI 31 .. end of transmission
Parameter-settable
FUN = 255 .. only for TI 24
129
INF = 0 .. only for TI 24 129

In monitoring direction
<3> .. Spontaneous <31> .. only with TI 24 129
In control direction
<6> .. Activation
Not evaluated
T ..Test
Not evaluated
Not evaluated
confirmation
Originator address
User data part 130
Type identification 1: Binary Information with time tag
Type identification 2: Binary information with relative time

The assignment of the message address for the spontaneous information object “Binary information” is carried
out in the SICAM TOOLBOX II, OPM II in the central station with the category firmware / Rec_binary .
129 These items of information only have the specified values with TI 24 – with all other TIs these items of information are copied 1:1
from the user data container into IEC 60870-5-103 without assessment
130 IEC 60870-5-103 message formats for the transmission of files are transmitted in the user data part of the user data container

DC8-037-2, Edition 11.2020
12.5 IEC 60870-5-103
Elements of the Message (IEC 60870-5-101/104) BSE ← Elements of the Message (IEC 60870-5-103) C← S
PRE
Type identification (all with Type identification
time tag CP56Time2a) TI 1 .. Binary Information
TI 30 .. Single-point informa- with time tag
tion TI 2 .. Time-tagged message
Only for relative time as
TI 31 .. Double-point infor- measured value with relative time 131
mation
TI 32 .. Measured value,
TI 38 .. Event of protection
equipment
TI 39 .. Blocked activation of
the protection
TI 40 .. Blocked triggering of
the protection
CASDU (CASDU1, CASDU2) CASDU .. Common address
Parameter-settable
IOA (IOA1, IOA2, IOA3) of ASDU
<3> .. Spontaneous 132
<20> .. Interrogated by <1> .. spontaneous

station interrogation <7> .. Test mode 133
<12> .. Return information, <9> .. General Interrogation
caused by a local command
<11> .. Local operation
<11> .. Return information,
<12> .. Remote operation
caused by a remote
command
T ..Test
confirmation
Originator address Not defined
Quality descriptor Not used
BL = 0 .. blocked Not used
SB = 0 .. substituted Emulated by the basic
NT .. not topical system element on failure of
the protocol element or the
remote terminal unit
IV = x .. Invalid
EI = 0 .. Elapsed time Only TI 39,40
(0/1 = valid/invalid) Not used
131 Binary information with relative time is not supported by SICAM A8000 remote terminal unit!
132 Binary information with other causes of transmission are discarded!
133 For more details see section Test Mode, Page 767

DC8-037-2, Edition 11.2020
12.5 IEC 60870-5-103
PRE
• Double-point informa- Only TI 31 Double-point information
tion state (DPI) Only TI 38 (DPI)
• Binary information state Intermediate position
(ES) <0> .. Not used
<0> .. Undetermined state <1> .. OFF
<1> .. OFF Faulty position <2> .. ON
<2> .. ON <3> .. Not used
<3> .. Undetermined state
Time Time
CP56Time2a ... Dual time CP32Time2a ... dual time
with 7 octets with 4 octets
start events of protection Only TI 39
equipment The IEC 60870-5-103 binary
SRD .. Start of operation in information state can be
reverse direction assigned one of these binary
SIE .. Start of operation IE information items
(earth current)
SL3 .. Start of operation
phase L3
phase L2
phase L1
GS .. General start of opera-
tion
Binary information to the Only TI 40
output current of the protec- The IEC 60870-5-103 binary
tion equipment information state can be
CL3 .. Command to output assigned one of these binary
circuit phase L3 information items
CL2 .. Command to output
circuit phase L2
CL1 .. Command to output
circuit phase L1
GC .. General command to
output circuit
• Measured value, short Only TI 36 (relative time as Relative time (CP16Time2a)
floating point number measured value)
• Elapsed time
(CP16Time2a) Only TI 38
• Relay duration time Only TI 39
(CP16Time2a) Only TI 40
• Relay operation time
(CP16Time2a)

DC8-037-2, Edition 11.2020
12.5 IEC 60870-5-103
PRE
• Measured value, short Only TI 36 Fault number
floating point number
Additional information (SIN)
134
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 items can be converted to 1 double-point informa-
tion item.
Note: For both single-point information items, the same SICAM A8000 address of the double-point infor-
mation item 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 infor-
mation 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 trans-
ferred 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.
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 SICAM TOOLBOX II, OPM II in the master station with the category firmware / Rec_binary.
134 Master station: not evaluated! Remote 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 acknowledgment
→ SIN = return information identification of the command Cause of transmission = other →SIN = not used!

DC8-037-2, Edition 11.2020
12.5 IEC 60870-5-103
PRE
time tag CP56Time2a) TI 33 .. Binary information
TI 30 .. Single-point informa- with time tag 135
tion TI 65 .. Binary information
TI 31 .. Double-point infor- without time tag 136
mation
TI 66 .. Binary information
with time tag 136
without time tag 136
with time tag 136
Parameter-settable
Type identification 3: Measurands I
Type identification 4: Real-time measured values with relative time
Type identification 9: Measurands II

The assignment of the message address for the spontaneous information object “Measured value” in receive
direction is carried out in the SICAM TOOLBOX II, 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 SICAM TOOLBOX II, OPM II in the slave station with the category firmware /
Trans_measured value..
135 Binary information with time tag SEG-protective device – private range!
136 Binary information with time tag ALSTOM-protective device – private range!

DC8-037-2, Edition 11.2020
12.5 IEC 60870-5-103
PRE
time tag CP56Time2a) TI 3 .. Measurands I
Fault location
TI 34 .. Measured value, TI 4 .. Real-time measured
normalized value values with relative time
TI 35 .. Measured value, TI 9 .. Measurands II
scaled value 137
TI 36 .. Measured value,
Parameter-settable
FUN .. Function type
Parameter-settable
INF .. Information number
Subvalue … number of the
measurand in message
<3> .. spontaneous <1> .. Spontaneous
<2> .. Cyclic
<20> .. Interrogated by <9> .. General interrogation
station interrogation
Originator address Not defined

Quality descriptor
Not used
BL = 0 .. blocked
Not used
SB = 0 .. substituted
NT = ER 138
NT .. not topical ER = x .. Error
<0> .. if NT=0 and IV=0 139
IV = x .. invalid <1> .. if NT=1 or IV=1 139
OV = x .. overflow OV = x .. Overflow
Value 137 Converted and scaled 103 MEA … Measurand-type Parameter-settable
measurand 103 measurand
<TI:=3, 9 only>
Value 137 Converted and scaled 103 SCL … short circuit location Parameter-settable
measurand <TI:=4 only>
– – FAN (fault number) The FAN (= fault number)
<TI:=4 only> will be incremented with
each general trip received
from BSE → PRE
– – RET … relative time =0
<TI:=4 only>
137 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) .
138 Receive direction Master only
139 Transmit direction Slave only

DC8-037-2, Edition 11.2020
12.5 IEC 60870-5-103
Suggestions for the SIP message address conversion of the master station:
• Type of measured values (selection of the measurand data format in IEC 60870-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
i 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.
12.5.9.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.
Data in transmit direction is transferred from the basic system element to the protocol element in the SICAM
A8000 internal IEC 60870-5-101/104 format. The data is 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 is converted by the protocol element from IEC 60870-5-101 format on the transmis-
sion line to a SICAM A8000 internal IEC 60870-5-101/104 format and transferred to the basic system element.
12.5.9.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 A8000 central station/substations is transmitted with a user data
container in the private range of IEC 60870-5-103. As a result, between SICAM A8000 systems, no parameteri-
zation of the address conversion IEC 60870-5-101 ⇔ IEC 60870-5-103 is required. The data transmission to
protection equipment (substations) of other manufacturers is carried out according to IEC 60870-5-103.
Data messages are transmitted from the basic system element in SICAM A8000 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 A8000.
In receive direction, the IEC 60870-5-101 message format is read out from the user data container and trans-
ferred to the basic system element in the SICAM A8000 internal IEC 60870 5-101/104 message format. When
using SICAM BC as substation, the operating mode for the message conversion (101 mode) is signaled to the
master station with the startup signal.
NOTE
i • In the central station and in the substation, the IEC parameters (number of bytes for COT, CASDU, IOA)
must be set identical.
• In the central station (SICAM A8000) the message conversion for a binary information (IEC
60870-5-103 → IEC 60870-5-101) must be entered in the receive detailed routing, 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
A8000.

DC8-037-2, Edition 11.2020
12.5 IEC 60870-5-103
IEC 60870-5-103 User Data Container <TI:=200>
12.5.9.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 inter-
face.
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)" oper-
ating 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.
processing.

DC8-037-2, Edition 11.2020
12.5 IEC 60870-5-103
12.5.9.5 Class 1, 2 Data
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 interrog-
ation can be determined selectively for every remote terminal unit in the master station in the parameters for
the [PRE] Station definition with the parameter [PRE] Station definition | Prioritiza-
tion 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 A8000 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.
For the coupling of protection equipment, if necessary the following special functions can be activated for the
• Send Short Circuit Location Values with GI
• Resetting the Short Circuit Location Values
• 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
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 center
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 [PRE] IEC60870-5-103 | Communication functions |
General interrogation | Send fault locaton values within GI .
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:

DC8-037-2, Edition 11.2020
12.5 IEC 60870-5-103
• 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 [PRE] IEC60870-5-103
| Communication functions | Fault location values | 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 [PRE]
IEC60870-5-103 | Communication functions | Fault location values | Send initial
values with delay .
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 protec-
tion 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 [PRE] IEC60870-5-103 | Communica-
tion functions | Fault location values | Initialization value 16 bit normalized
(TI 34) , the parameter [PRE] IEC60870-5-103 | Communication functions | Fault loca-
tion values | Initialization value 16 bit scaled (TI 35) and the parameter [PRE]
IEC60870-5-103 | Communication functions | Fault location values | Initializa-
tion value Floating Point (TI 36) .
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 [PRE] IEC60870-5-103 | [PRE] IEC60870-5-103 |
Communication functions | Fault location values | Reset fault location values
automatically and the parameter [PRE] IEC60870-5-103 | Communication functions |
Fault location values | Imitate initialization values . In addition, with the parameter
[PRE] IEC60870-5-103 | Communication functions | Fault location values | 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 [PRE] IEC60870-5-103 | Communica-
tion functions | Fault location values | Initialization value 16 bit normalized
(TI 34) , the parameter [PRE] IEC60870-5-103 | Communication functions | Fault loca-
tion values | Initialization value 16 bit scaled (TI 35) and the parameter [PRE]
IEC60870-5-103 | Communication functions | Fault location values | Initializa-
tion 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.

DC8-037-2, Edition 11.2020
12.5 IEC 60870-5-103
Signaling / Measured Value Disabling

The signaling / measured value disabling is a function of the protection equipment and can be activated glob-
ally (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 func-
tion, the spontaneous transmission of the data from the protection equipment to the master station is deacti-
vated.
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 deacti-
vation.
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 disa-
bling, 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 .
Technological Adaptation for Measured Values

The technological adaptation enables the measured value supplied by the protection equipment to be trans-
formed 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
Measured value, normalized value - 1 ... + 1-2-15 normalized, percental representa-
tion
Measured value, scaled value - 32768 technological, integer
...
+ 32767
Measured value, short floating - 8,43 * 10-37 technological, floating point
point ...
+ 3,37 * 1038
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%" und "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 meas-
uring range X100.
The adaptation line with "kx+d" is to be parameterized for each measured value with the parameters
"Factor_k" und "Offset_d".
Bipolar measured values without zero-range suppression and plausibility check

Example for <TI:3,9>

DC8-037-2, Edition 11.2020
12.5 IEC 60870-5-103
Value Meaning Parameters

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%
Y100 technological value at X100 Y_100%
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 system element specific processing grid the measured value is monitored for change. In the parameter-
ized processing grid the measured value is monitored for change. If the deviation from the last spontaneously

DC8-037-2, Edition 11.2020
12.5 IEC 60870-5-103
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 totalled according to the polarity sign. First 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 established:
• 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.
The values for the parameter thresh additive and thresh uncond are absolute values and refer to the
value after the technological adaptation.
The processing grid is to be parameterized for all measured values with the parameter [PRE]
IEC60870-5-103 | Communication function | Measured values | 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".
The measured value thresholds are to be parameterized with the parameters [PRE] IEC60870-5-103 |
Communication function | Measured values | Measured value thresholds | * .
The following example shows a normal case, where the adaption 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

DC8-037-2, Edition 11.2020
12.5 IEC 60870-5-103
0.0s 0.1s 0.2s 0.3s 0.4s 0.5s 0.6s 0.7s 0.8s ... 7.4s 7.5s
Additive total 0 79 158 237 316 395 395 553 632 ... 5925 6004
Transmission x x
Example 2:
threshold) and subsequently remains 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
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 protec-
tion 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)) .
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 trig-
gering of protection".
With the message "blocked activation of protection" several protection activation signals and the relay dura-
tion 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.

DC8-037-2, Edition 11.2020
12.5 IEC 60870-5-103
IEC 60870-5-101/104 IEC 60870-5-103

<TI:=39> Packed start events of protection <TI:=2> Binary information with relative time
with time tag CP56Time2a
<TI:=40> Packed output circuit information of <TI:=2> Binary information with relative time
protection equipment with time tag
<TI=39> Packed Start Events of Protection with IEC 60870-5-103 Disturbance Information 140
Time Tag (SPE)
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> Blocked tripping of the protection with IEC 60870-5-103 Disturbance Information
time stamp CP56Time2a messages to output
current circuit of the protective device (OCI)
GC General command to output circuit <INF=68> General trip
CL1 Command to output circuit phase L1 <INF=69> Trip L1
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 [PRE]
IEC60870-5-103 | Communication functions | Protection indications IEC60870-5-101
(TI=38,39) | 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.
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“.
140 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)

DC8-037-2, Edition 11.2020
12.5 IEC 60870-5-103
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).
Transmit Non-Updated Process Images

After a general interrogation, the protocol firmware of the master station sends all non-received but parame-
terized 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 [PRE] IEC60870-5-103 |
Communication functions | General interrogation | Emulation of not updated
process data after GI | Timeout for emulation of not updated process data after
GI .
The emulation of these data points can be deactivated with the parameter [PRE] IEC60870-5-103 |
Communication functions | General interrogation | Emulation of not updated
process data after GI | 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".
Emulation of the Going Binary Information [Client 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 IEC 60870-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".

DC8-037-2, Edition 11.2020
12.5 IEC 60870-5-103

• Set control location
• the suppression of errors with intentionally switched-off stations (Station Service)

• the obtaining of station interrogation information
Block Diagram
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 used.
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.
For messages with process information which are used in SICAM RTUs as protocol element
control message, an unused CASDU is to be used! All CASDUs for process information are distributed auto-
matically to the corresponding remote terminal unit.

DC8-037-2, Edition 11.2020
12.5 IEC 60870-5-103
Possible master station functions:

SF Station Z-Par FI
Call cycle START 0 125 -
Call cycle STOP (disabling) 1 125 -
Call cycle CONTINUE (enabling) 2 125 -
Continuous call station x ON 3 0-99 0 -65535 Z-Par=continuous call time (n *
100ms)
Z-Par=0: Continuous call without time
input
(stopped by other function)
Continuous call station x OFF 4 0-99 -
"Deactivate" interface 5 - - • Reset interface failure
• Do not send all messages from
BSE
• Received messages are discarded
"Activate" interface 6 - -
Send (general) interrogation 240 - - This function is processed on the BSE
command and sent to the protocol element as
control message!
CASDU = BROADCAST
Set Control Location *) 242 125 65535 SCS=<ON>: set control location (HKA)
(all stations)
65535 SCS=<OFF>: reset control location
(HKA)
(all stations)
0-99 65535 SCS=<ON>: set control location (HKA)
(selective station)
(HKA) (selective stations)
supported by PRE!
Send (general) interrogation 244 - CASDU This function is processed on the BSE
control message! CASDU = selective
*) 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 Z-Par =
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
Legend:

DC8-037-2, Edition 11.2020
12.5 IEC 60870-5-103

0 - 99 = station 0 - 99 of the selected protocol element
125 = all stations of the selected protocol element (=BROADCAST)
Fl ... Edge
SCS ... Single command state
HKA ... Originator address (HKA) = 0 - 255
Possible remote terminal unit functions:

SF Station Z-Par FI
control message!
CASDU = BROADCAST
command for GI-group to own and not sent to the protocol element
BSE 141 as PRE-control message!
(=simulate received general inter-
rogation command for GI group)
supported by PRE!
Send (general) interrogation 244 - CASDU This function is processed on the BSE
control message!
CASDU = selective
Legend:
SF Control function_(PRE)
Z-Par Additional parameter_(PRE)
12.5.10.2 Protocol element return information
141 only supported in Ax 1703 (not supported in SICAM RTUs, ACP 1703)!

DC8-037-2, Edition 11.2020
12.5 IEC 60870-5-103
Possible master station protocol element feedback:

Feedback_func-
tion_(PRE)
Station status 0-99 1 = Station enabled for access cycle
Station failure 0-99 1 = Station failed
protocol-specific return infor- 255 IDLE cycle
mation 0
• Station polling is stopped.
User data messages will be sent furthermore.
Protocol-specific feedback 1 255 NORMALMODE cycle
• cycle control running in normal mode

(cyclic RTU interrogation)
Protocol-specific feedback 2 255 Continuous station polling
• Continous station polling of a specific station is in

progress.
Protocol-specific feedback 3 255 Cycle stopped
• Station polling was stopped by PST-control message.

Protocol-specific feedback 6 255 Send "data to all"
• Transmission of BROADCAST data message is in progress

at this moment.
Protocol-specific feedback 7 255 Send "data telegram"
• Data messoge transmission to single station is in progress

at this moment.
Possible substation feedback:
Feedback function_(PRE) Parameter Note

Station
Status DTR 255 DTR status 142
Status DSR 255 DSR status 142
Station failure 0 1 = Station failed 143
142 The protocol element sends status line states spontaneously upon changes or as a response to a general interrogation command to
the base system element; the spontaneous transmission of the current states is internally carried out at 100 ms intervals → Status
line changes shorter than 100 ms are not always transferred!
143 is currently not supported by BSE!

DC8-037-2, Edition 11.2020
12.5 IEC 60870-5-103
12.5.11 Interoperability IEC 60870-5-103
Electrical Interface
EIA RS-485
Number of loads ……………….…… for one protection equipment
NOTE:
EIA RS-485 standard defines unit loads so that 32 of them can be operated on one line. For detailed informa-
tion refer to clause 3 of EIA RS-485 standard.
Optical interface
Glass fiber *)
Plastic fiber *)
F-SMA type connector *)
BFOC/2,5 type connector *)
*) For optical interfaces suitable converter (RS-232 ↔ optical) must be used!
Transmission rate
9600 bit/s
19200 bit/s
There are no choices for the link layer.

Mode 1 (least significant octet first), as defined in 4.10 of IEC 870-5-4, is used exclusively in this companion
standard.
One Common Address of ASDU (identical with station address)
More than one Common Address of ASDU

DC8-037-2, Edition 11.2020
12.5 IEC 60870-5-103
12.5.11.4 Selection of standard-ASDU in monitor direction
ASDU 1 time-tagged message
ASDU 2 time-tagged message with relative time
ASDU 3 measurands I
ASDU 4 time-tagged measurands with relative time
ASDU 5 identification
ASDU 6 time synchronization
ASDU 8 general interrogation termination
ASDU 9 measurands II
ASDU 10 generic data
ASDU 11 generic identification
ASDU 23 list of recorded disturbances
ASDU 26 ready for transmission of disturbance data
ASDU 27 ready for transmission of a channel
ASDU 28 ready for transmission of tags
ASDU 29 transmission of tags
ASDU 30 transmission of disturbance values
ASDU 31 end of transmission
NOTE:
For full compatibility, the INFORMATION NUMBERS should also be specified with the ASDU.
12.5.11.5 Selection of standard-ASDU in control direction
ASDU 6 time synchronization
ASDU 7 general interrogation
ASDU 10 generic data

DC8-037-2, Edition 11.2020
12.5 IEC 60870-5-103
ASDU 20 general command
ASDU 21 genenc command
ASDU 24 order for disturbance data transmission
ASDU 25 acknowledgement for disturbance data transmission
NOTE:
For full compatibility, the INFORMATION NUMBERS should also be specified with the ASDU.
12.5.11.6 Selection of standard information numbers in monitor direction
System functions in monitor direction
INF Description
<0> End of general interrogation
<0> Time Synchronization
<2> Reset FCB
<3> Reset KE
<4> Start/restart
<5> Power on
Status indications in monitor direction
INF Semantics
<16> Auto-recloser acitve
<17> Teleprotection active
<18> Protection active
<19> LED reset
<20> Monitor direction blocked
<21> Test Mode
<22> Local parameter setting
<23> Characteristic 1

DC8-037-2, Edition 11.2020
12.5 IEC 60870-5-103
<27> Auxiliary input 1
Supervision indications in monitor direction
INF Semantics
<32> Measurand supervision I
<33> Measurand supervision V
<35> Phase sequence supervision
<36> Trip circuit supervision
<37> I>> back-up operation
<38> VT fuse failure
<39> Teleprotection disturbed
<46> Group warning
<47> Group alarm
Earth fault indications in monitor direction
INF Semantics
<48> Earth fault L1
<49> Earth fault L2
<50> Earth fault L3
<51> Earth fault forward, i.e. line
<52> Earth fault reserve, i.e. busbar

DC8-037-2, Edition 11.2020
12.5 IEC 60870-5-103
Fault indications in monitor direction
INF Semantics
<64> Start/pick-up L1
<67> Start/pick-up N
<68> General trip
<69> Trip L1
<70> Trip L2
<71> Trip L3
<72> Trip I>> (back-up operation)
<73> Fault location X in ohms
<74> Fault forward/line
<75> Fault reverse/busbar
<76> Teleprotection signal transmitted
<77> Teleprotection signal received
<78> Zone 1
<79> Zone 2
<80> Zone 3
<81> Zone 4
<82> Zone 5
<83> Zone 6
<84> General start/pick-up
<85> Breaker failure
<86> Trip measuring system L1

DC8-037-2, Edition 11.2020
12.5 IEC 60870-5-103
<89> Trip measuring system E
<90> Trip I>
<91> Trip I>>
<92> Trip IN>
<93> Trip IN>>
Auto-reclosure indications in monitor direction
INF Semantics
<128> CB ‘on’ by AR
<129> CB ‘on’ by long-time AR
<130> AR blocked
Measurands in monitor direction
INF Semantics
<144> Measurand I
<145> Measurand I, V
<146> Measurand I, V, P, Q
<147> Measurands IN, VEN
<148> Measurands IL1,2,3, VL1,2,3, P, Q, f
Generic functions in monitor direction
INF Semantics
<240> Read headings of all defined groups
<241> Read values or attributes of all entries of one group
<243> Read directory of a single entry
<244> Read value or attribute of a single entry

DC8-037-2, Edition 11.2020
12.5 IEC 60870-5-103
<245> End of general interrogation of generic data
<249> Write entry with confirmation
<250> Write entry with execution
<251> Write entry aborted
12.5.11.7 Selection of standard information numbers in control direction
System functions in control direction
INF Semantics
<0> Initiation of general interrogation
<0> Time synchronization
General commands in control direction
INF Semantics
<16> Auto-recloser on/off
<17> Teleprotection on/off
<18> Protection on/off
<19> LED reset
<23> Activate characteristic 1
Generic functions in control direction
INF Semantics
<240> Read headings of all defined groups
<241> Read values or attributes of all entries of one group
<243> Read directory of a single entry
<244> Read value or attribute of a single entry

DC8-037-2, Edition 11.2020
12.5 IEC 60870-5-103
<245> General interrogation of generic data
<248> Write entry
<249> Write entry with confirmation
<250> Write entry with execution
<251> Write entry abort
Test Mode
Blocking of monitor direction
Disturbance data
Generic services
Private data
12.5.11.9 Miscellaneous
Measurands are transmitted with ASDU 3 as well as with ASDU 9. As defined in 7.2.6.8, the maximum MVAL
can either be 1,2 or 2,4 times the rated value. No different rating shall be used in ASDU 3 and ASDU 9, i.e. for
each measurand there is only one choice.
Measurand Max. MVAL = times
rated value
1.2 or 2.4
Current L1
Current L2
Current L3
Voltage L1-E
Voltage L2-E
Voltage L3-E
Active power P
Reactive power Q

DC8-037-2, Edition 11.2020
12.5 IEC 60870-5-103
Measurand Max. MVAL = times

rated value
Frequency f
Voltage L1 – L2

DC8-037-2, Edition 11.2020
12.6 IEC 60870-5-104
12.6 IEC 60870-5-104
12.6.1 Introduction
The IEC 60870-5-104 protocol is a standardized transmission protocol (TCP/IP) for communication with remote
stations in the network (LAN, WAN).
For CP-8000/CP-802x, the following protocol firmware for IEC60870-5-104 is available:

ET84 CP-8000 IEC 60870-5-104 controlling-/controlled station
CP-802x
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.

DC8-037-2, Edition 11.2020
12.6 IEC 60870-5-104
12.6.2 Functions
• LAN/WAN communication via Ethernet TCP/IP – General Information

– 10 Mbit/s (full duplex)144
– 10 Mbit/s (half duplex)144
– 10 Mbit/s (full duplex, auto negotiation144
– 10 Mbit/s (half duplex, auto negotiation)144
– 10/100 Mbit/s (half duplex/full duplex, auto negotiation)144
– 100 Mbit/s (full duplex)144
– 100 Mbit/s (half duplex)144
– 100 Mbit/s (full duplex, auto negotiation)144
– 100 Mbit/s (half duplex, auto negotiation)144
– Auto-MDIX (Auto Medium Dependent Interface Crossover)144
– Parameters for TCP/IP optimization144
– TCP/IP Keep Alive144
• LAN/WAN communication via Ethernet TCP/IP according to IEC 60870-5-104

– Controlled station
• Supported ports
– Port 2404: IEC 60870-5-104
– Port 80: HTTP (Hypertext Transfer Protocol)
"Remote operation for SICAM TOOL-BOX II"
– Port 443: HTTPS (Hypertext Transfer Protocol over SSL/TLS)
"Remote operation for SICAM TOOLBOX II"
– Port 123: NTP V3 (Network Time Protocol)144
– Port 123: SNTP V3 (Simple Network Time Protocol)144
• Special protocols
– Address Resolution Protocol (Gratuitous ARP) 144
• Interoperability according to 12.6.9 Interoperability IEC 60870-5-104
• Time synchronization according to NTP (Network Time Protocol)

– NTP server144
– NTP client144
– SNTP client144
144 Function integrated into Master Module

145 recommendation max. 10 connections

DC8-037-2, Edition 11.2020
12.6 IEC 60870-5-104
– Monitoring the maximum transport time in command direction

Protocol element control telegrams
– Send (general) interrogation command
– "Activate, deactivate" remote operation
Protocol element feedback telegrams
– PRE feedback 0 "Status DATA TRANSFER (Master Module)"
– PRE feedback 1 "Status DATA TRANSFER (104)"
• Functions for the Support of Redundant Ways of Communication

– PSI redundancy (synchronous connections)
– 104 redundancy according IEC 60870 -5 -104 Edition 2.0
– 104 redundancy "Controlled Station" with 1 Ethernet interface
– 1703-Redundancy
– Dual LAN interface with integrated switch for ring or multipoint-star configurations (DNIP)
– Switch mode144
• Connection of the SICAM TOOLBOX II via LAN/WAN ("remote operation")

– Remote operation based on HTTP/HTTPS144
– Authentication in SICAM RTUs using connection password (optional)144
– "Remote operation" warning 144
• Security
– IPSec VPN
– IPSec in tunnel mode: Initiator144
– Authentication/encryption based on preshared key144
– Internet Key Exchange Protocol: IKEv1, IKEv2144
– Authentication: HMAC-SHA1, SHA2_224, SHA2_256, SHA2_384, SHA2_512, HMAC-MD5144
– Encryption: AES-128/-192/-256, 3DES144
– Diffie Hellman Group: 1, 2, 5, 14 144
– Security logging
– Syslog Client144

DC8-037-2, Edition 11.2020
12.6 IEC 60870-5-104
– Daylight saving time bit = 0 for all telegrams in transmit direction (time marker)
– Day of the week (DOW) = 0 for all telegrams in transmit direction (time marker)
– WhiteList Filter
– Data throughput limit
– Suppress error message in case of connection failure
– Error handling for connection with "Failure = suppress"
– NT bit emulation for received data
– General interrogation once connection is OK again

optional DTE
Electrical ethernet-interface X1 TXD+, TXD-, RXD+, RXD-
(twisted pair) X4
GPRS X7146 (Antenna)
NOTE
Own Station (Central Station or Substation)

SICAM A8000 Series CP-8000/CPC80 ET84
CP-802x/CPC80
Remote Station (Substation or Central Station)

SICAM A8000 Series CP-8000/CPC80 ET84
CP-802x/CPC80
SICAM A8000 Series CP-8050/CPCI85 ETI4
SICAM AK 3 CP-2016/CPCX26 ET24 only 100 Mbit/s
CP-2019/PCCX26 SM-2558/ETA4
146 only CP-8022

DC8-037-2, Edition 11.2020
12.6 IEC 60870-5-104

Legacy systems CP-20xx SM-2558/ETA4 according to 12.6.9 Inter-
(SICAM AK CP-50xx SM-2557/ETA2 operability IEC
SICAM TM CP-60xx ETT0 60870-5-104
SICAM EMIC
SICAM MIC
SICAM BC)
Third-party system - - according to 12.6.9 Inter-
operability IEC
60870-5-104
12.6.5 Communication via Ethernet TCP/IP according to IEC 60870-5-104
12.6.5.1 Ethernet interface

The Ethernet interface is implemented either direct on the communication module (NIP) or on the basic
system element.
Ethernet speed (10/100 Mbps), full/half duplex
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 parame-
ters, such as speed, duplex mode, and flow control. 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 with direct coupling of other systems with cross-over cables or when
using HUBs or other network components, then "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“).
The parameter Network settings | Advanced parameters | Diagnostic information for
Ethernet-link status X# defines if a diagnostic information shall be set.
For system elements supporting 2 Ethernet ports the diagnostic information “LINK DOWN“ will be set individu-
ally for each port.
12.6.5.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 232, therefore
4,294,967,296 addresses can be represented. The IP address is mostly represented in the dotted decimal nota-
tion.
Example: 192,168,122,195
The IP address of the own station is to be parameterized in the system technique 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-tech-
nical parameters of the Connection definition.

DC8-037-2, Edition 11.2020
12.6 IEC 60870-5-104
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 determined by the IANA (Internet Assigned Numbers Authority).
Port numbers used in the LAN/WAN protocol firmware:
Port
Number Protocol Standard ETA2 ETA4 ET84 ET24
2404 IEC 60870-5-104 IEC 60870-5-104 Edition 2.0 ✓ ✓ ✓ ✓
80 HTTP ✓
(Hypertext Transfer Protocol) RFC 2616 (HTTP/1.1)
80 HTTP Remote operation for SICAM ✓ ✓147 ✓147
(Hypertext Transfer Protocol) TOOLBOX II
443 HTTPS Remote operation for SICAM ✓ ✓147 ✓147
(Hypertext Transfer Protocol TOOLBOX II
over SSL/TLS)
123 NTP V3 RFC 1305 ✓ ✓ ✓147 ✓147
123 SNTP V4 RFC 2030 ✓ ✓147 ✓147
(Simple Network Time Protocol)
2001 148 Remote operation for SICAM Remote operation for SICAM ✓
TOOLBOX II TOOLBOX II
---- RSTP IEEE 802.1D, Edition 2004 ✓
(Rapid Spanning Tree Protocol)
Legend:
RFC Request for Comments
Default Router (Default Gateway) 149

If one’s 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 parameter of the protocol firmware with the parameter IP address | Default
router (default gateway) .
Subnet Mask 149

The subnet mask is a bit mask, that separates an IP address into a network- 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, to 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 are set to "0".
In most cases the notation of a network mask is not carried out binary, rather (as with IP address also)
frequently in decimal notation (dotted decimal notation).
Therefore 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 the first 27 places
of the IP address of the network part and for all hosts of the network are identical. In all practical cases of
application the network part is continuous (without zeros in between).
147 in CP-8000/CP-802x and SICAM AK3 with local protocol (PRE without NIP), this function is integrated on the basic system element
148 This port number is not registered at IANA!
149 Function integrated on the basic system element

DC8-037-2, Edition 11.2020
12.6 IEC 60870-5-104
A network mask with 27 set bits produces a network part of 192.168.122.192. 5 bits and therefore 32
addresses are left over for the device part.
In the above example the smallest host address ends with 11000000 (decimal: 192), the greatest 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 greatest address is by definition reserved for the IP Broadcast and the smallest address describes the
network itself. They are therefore not included in the freely usable addresses.
In practice the Default Gateway is often assigned to the smallest (binary in the example: 11000001, decimal:
193) or largest (binary in the example: 11011110, decimal: 222) usable IP address in the network.
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 Station definition (Connection definition) .
The following parameters can be set for each connection:
• Stat. Nr
The station number is used SICAM A8000 internal for the routing of the data, diagnostic treatment and
failure management. The station number is the SICAM A8000 internal reference for the connection that
is assigned to an IP address. During the data transmission, only the IP address assigned to the station
number is transmitted, the station number is not transmitted.
During the data flow routing the data are routed for transmission to a "station number" (=Connection
number = destination station number).
The station number is to be entered in the parameter Connection definition | Stat. Nr for
each connection.
• Connection
A parameterized connection can be activated/deactivated with the parameter Connection defini-
tion | Connection ; e.g. this way connections can be prepared, which are activated at a later time
by means of parameterization.
• 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 a 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 defini-
tion | IP-addr.

DC8-037-2, Edition 11.2020
12.6 IEC 60870-5-104
• 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 details refer 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 refer to section "Functions for the support of redundant communication routes".
With the parameter Connection definition | RedGroup the redundancy group number is para-
meterized 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 IEC 60870-5-104 parameters for network connection:
– LAN (IEC 104 default)
– WAN
– LAN (fast dropout detection)
– GPRS
– Satellite
– free definable 1
• 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 | 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: With that a ring overflow is avoided with non-connected remote stations.
• Day of week
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.

DC8-037-2, Edition 11.2020
12.6 IEC 60870-5-104
• 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 IEC 60870-5-104 message will be executed.
Supported Profiles:
– SICAM RTUs - IEC104 (“SICAM RTUs “Standard“)
– IEC 60870-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 IEC 60870-5-104 in SICAM RTUs supports a limitation of data throughput in
transmit-/receive direction for IEC 60870-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 Connec-
tion definition | Data throughput limit in receive direction (msg/s) (0 = no
data throughput limitation).
IEC 60870-5-104 Parameter

of the message according to IEC 60870-5-104 to the following defined values is required:
IEC 60870-5-101 Parameter Description System
Element
Cause of transmission (COT) Number of octets for cause of transmission = 2 BSE
Common address of ASDU Number of octets for common address of the ASDU = 2 BSE
(CASDU)
Information object address Number of octets for the address of the information object = 3 BSE
(IOA)
Maximum message length max. 253 BSE
Time tag Number of octets for time tag = 7 BSE

DC8-037-2, Edition 11.2020
12.6 IEC 60870-5-104
NOTE
i 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 unac-
knowledged 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
i 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!
Supported IEC 60870-5-104 / TCP Parameters
Network connection
LAN (fast
LAN (IEC dropout free free free
104 detec- GPR Satel- defin- defin- defin- Group
Parameters default) WAN tion) S lite able 1 able 2 able 3 1-4
IEC 104 Parameter
timeout connection setup 5 5 5 60 5 5 5 5 30
t0
Timeout transmit t1 15 60 7 250 60 15 15 15 15
timeout transmit acknowl- 10 10 2 10 10 10 10 10 10
edge t2
timeout connection check 20 20 10 250 20 20 20 20 20
t3
Max. no. of APDUs until 12 12 12 12 60 12 12 12 12
acknowledgement (k)
Number od APDUs until 8 8 8 8 8 8 8 8 8
acknowledge (w)
TCP-parameters *) *)
transmission optimization **) **) **) **) **) **) **) **) **)
initial TCP retransmission 2500 2500 100 2500 2500 2500 2500 2500 2500
timeout
minimum TCP retransmis- 250 250 100 1000 250 250 250 250 500
sion timeout
maximum TCP retransmis- 5000 5000 200 1000 5000 5000 5000 5000 5000
sion timeout 0
MSS (maximum segment 1460 1460 1460 512 1460 1460 1460 1460 1460
size) transmit direction
TCP connection close ***) ***) ***) ***) ***) ***) ***) ***) ***)

DC8-037-2, Edition 11.2020
12.6 IEC 60870-5-104
*) ... The settings for TCP parameters can not be changed in CP-8000/
CP-802x (ET84)
**) ... Possible settings:
• default (ack delay, no nagle)

• bandwith (ack delay, nagle)
• throughput (no ack delay, nagle)
• response time (no ack delay, no nagle)
***) ... Possible settings:
• close with FIN or RST (default)

• close with RST
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 | Standard 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 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 acknowledgment, if no data is transmitted t2<t1.
With the simultaneous transmission of user data (I-Frames) in both directions, acknowledgments are sent
together in the user data messages. For the data transmission of user data in only one direction, an
acknowledgment (S-frame) is sent after Timeout t2 at the latest.
parameter | Timeout transmit acknowledge t2 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 proce-
dure can be performed independently by both sides of a connection. The Timeout t2 is retriggered by the
reception of Information/Transmit/Test frames.
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 .

DC8-037-2, Edition 11.2020
12.6 IEC 60870-5-104
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 trans-
mitted from one station to the remote station without needing to receive an immediate acknowledge-
ment 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 acknowl-
edgement (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 od APDUs until acknowledge (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 | Max. no. of APDUs until acknowledgement
(w) or with the parameter 104 parameter | Group # | Number of APDUs until acknowl-
edgement (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 Parameter | TCP/IP optimi-
zations | 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 Parameter
| TCP/IP optimizations | transmission optimization for the following requirements:
– default (ack delay, no nagle)
– bandwith (ack delay, no nagle)
– throughput (no ack delay, nagle)
– Response time (no ack delay, no nagle)
(For details see chapter "Data Transmission Procedure")

DC8-037-2, Edition 11.2020
12.6 IEC 60870-5-104
• Maximum segment size (MSS) in transmit direction

In rare cases transmission systems support only a limited Maximum Segment Size (MSS) for Ethernet
packets (MSSmax = 1460 Bytes).
e.g.: there are GPRS systems that only support a max. Segment Size of 512 Bytes.
The maximum segment size can be set with parameter Network connection | * | TCP-param-
eter | 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 expected acknowledgement time or with the parameter Advanced parame-
ters | TCP/IP optimizations | TCP retransmission timeout | Initial TCP
retransmission timeout . Depending on the quality of the connection the expected acknowledge-
ment time is adapted dynamically between the parameterized minimum or 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 parameterr Network
connection | * | TCP-parameter | TCP connection close or with parameter Advanced
parameters | TCP/IP optimizations | TCP connection close :
– close with FIN or RST (default)
– close with RST
(for further details, see to section "Data Transmission Procedure")
By default the parameters are set so that no modification is required.
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 for each LAN connection. For each LAN connec-
tion, the data transmission is comparable with that between 2 stations over a virtual point-to-point connec-
tion.

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 func-
tion on the basic system element (BSE).

DC8-037-2, Edition 11.2020
12.6 IEC 60870-5-104
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 Netzwerkverbindung | * |
TCP-Parameter | Übertragungsoptimierung or with parameter advanced Parameter | 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.
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 connec-
tion. 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 (Connec-
tions 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 STARTD-
Tact (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 IEC 60870-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 param-
eters | Compatibility | GI after START DT or with 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.

DC8-037-2, Edition 11.2020
12.6 IEC 60870-5-104
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 connec-
tion with the parameter Connection definition | Stop behaviour .
Handling of the user data if the data transmission is stopped with STOPDTact:
• "Save" [Default]
The data are saved in the data storage of the communication function on the basic system element (BSE)
until they are deleted by the dwell time monitoring or can be transmitted to 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 parameters of
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: 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
Acknowledgement Procedure
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

DC8-037-2, Edition 11.2020
12.6 IEC 60870-5-104
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 acknowledge-
ment 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 with
the parameter 104 parameter | Extended group # | Max. no. of APDUs until acknowl-
edgement (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, acknowledgments are sent together in the user data
messages. For the data transmission of user data in only one direction, an acknowledgment (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 | Max. no. of APDUs
until acknowledgement (w) or with parameter 104 parameter | Standard group # | Number
of APDUs until acknowledgement (w) or with 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 connec-
tion | * | 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 optimiza-
tions | TCP retransmission timeout | Maximum TCP retransmission timeout,
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 or 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.
NOTE
i The parameters Network connection | * | IEC 104 parameter | Timeout connection

setup t0 and 104 parameter | Group # | Timeout connection setup and 104 param-
eter | 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.
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.

DC8-037-2, Edition 11.2020
12.6 IEC 60870-5-104
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 moni-
toring 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 Proce-
dure”.
No further data is sent to failed remote stations until successful establishment of the connection.
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 re-reachable remote station.No
further data is sent to a failed remote station until successful station initialization.
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 Error
handling for connection 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“: 150
• no error in diagnostics
• NT-Bit emulation for received data by BSE
• general interrogation command initiated by BSE after connection error

During connection failure all data messages in transmit direction (including “End of Init”) will be discarded. As
a result a ring overflow is avoided with non-connected remote stations.
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)" 151 supporte
d
notify notify ✓
notify suppress ✓
suppress notify
suppress suppress
150 ETA2 supports only mode-1 (without parameter)! not supported by ETA4 with “IEC 60870-5-104 redundancy with 2 Ethernet inter-
faces”! During connection failure all data messages in transmit direction (including “End of Init”) will be discarded. With that a ring
overflow is avoided with non-connected remote stations.
151 All real connections of a redundancy group must have the same parameter settings!

DC8-037-2, Edition 11.2020
12.6 IEC 60870-5-104
After startup, the connection is first established on the TCP/IP level. Then the Controlling Station starts the
connection on the 104-level by means of STARTDTact (Start Data Transfer Activation). Afterwards the trans-
mission 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
• "INIT-End" has been received by the basic system
• Parameter Connection definition | Stop behaviour = "save"
• Parameter Connection definition | Failure = "notify"
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 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.
For further details, see to section "Data Transmission Procedure".
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.
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 IEC 60870-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 trans-
mission control with Start/Stop (data flow block)".
If the IEC 60870-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).

DC8-037-2, Edition 11.2020
12.6 IEC 60870-5-104
In networks and in systems with time-critical tasks a precise time is indispensable.

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 152
• 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 1.1.2001
Reference date for Ax1703: 1.1.1997 1.1.1997
In both cases, the time tag is marked as invalid until the first reception of the synchronizing event.
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 transmis-
sion delay cannot be performed properly.
However, the clock synchronization with the clock synchronization command can be implemented in configu-
rations with networks if the "maximum network delay" is less than the accuracy required for time synchroniza-
tion.
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 synchro-
nization via NTP must be used by the remote station.
SICAM RTUs as Sender of Clock Synchronization Command

The clock synchronization command will be sent cyclic at the 30th second of minute. In SICAM RTUs the trans-
mission of the clock synchronization command is initiated by the basic system element.
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 command will be
received between 10th and 50th second. In SICAM RTUs the new time will be set at next change of minute.
NOTE
i 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.
152 Function integrated on the basic system element

DC8-037-2, Edition 11.2020
12.6 IEC 60870-5-104

The master station always sends data telegrams in command direction to the remote partner spontaneously if
the connection has been established (data transmission must have been started and the number of unac-
knowledged APDUs must not have been reached yet). 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 “Control location check” function can optionally be used in the
protocol element. If the control location check has been enabled, commands will only be sent if the originator
address of the command has been enabled beforehand by control telegrams.
The <TI:=107> test command with cause of transmission <COT=6> (activation) can be sent via each connec-
tion from the base system element to check the situation.
The remote partner must respond to the test command with cause of transmission <COT=7> (confirmation of
activation) 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 triggered by the base system element to a prepared connection is not sent and confirmed by
the protocol element with ACTCON+.
Refer to the Data Transmission Procedure, Page 844 paragraph and 12.6.7 Message Conversion paragraph for
more detailed information.
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.
This monitoring prevents the output of outdated commands.
If the command delay monitoring is activated and a command message arrives via the LAN interface, then the
time tag of the telegram is compared with the current time of the component.
If the evaluated command delay time (transmission time of the data in the network) is longer than the para-
metrized command delay monitoring the command message is discarded without an error message.
If the time of the component has not been specified yet, the Advanced parameters | Discard
command when local time not set or with the Parameter Command delay monitoring |
Discard command when local time not set parameter or with the Command runtime moni-
toring | Discard command if local time not set parameter can specify whether a received
command telegram is forwarded for further processing or whether it is deleted when command runtime moni-
toring is active.
The controlling station detects the failed command output through the missing of the confirmation of activa-
tion (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 deacti-
vated (Command delay monitoring = 0).
Error signalization To localize the error, the number of commands discarded by the command delay moni-
toring since RESET is summed and the last discarded command messages are additionally saved in a diagnostic
ring. The counters and the diagnostic ring can be read out with the SICAM TOOLBOX II (ST-Emulation).
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 CP56Time2a time marker
• <TI:=107> Check command with time tag CP56Time2a

DC8-037-2, Edition 11.2020
12.6 IEC 60870-5-104
NOTE
i • 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 transmis-
sion ACT (Activation)!

been enabled.
12.6.5.8 Transmission of integrated totals
A counter interrogation command "to all" triggered in the system is always transferred by the 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.
document "Common Functions Peripheral Elements according to IEC 60870-5-101/104."
In this section, not the possible redundancy concepts themselves that can be realized are described, rather
only those functions supported by the protocol element (PRE) for the support of redundant systems or
communication routes.
The following redundancy modes are supported:
• 104-Redundancy
• 104-Redundancy “Controlled” with 1 Ethernet Interface
• 104-Redundancy “Controlled” with 2 Ethernet Interfaces
• 104 redundancy „Controlling“
• PRE-Redundancy
• Port-Redundancy (deactivation of Interface)
• PSI-redundancy (synchronous connections)
• Device redundancy
NOTE
i Only 1 redundancy mode can be used per protocol element (PRE)!
All redundancy modes (except deactivation of the interface) can use the additional functionality of dual-LAN
interface (DNIP):

DC8-037-2, Edition 11.2020
12.6 IEC 60870-5-104
• Switch Mode
• Line Mode (Siemens specific)
• RSTP Mode
Using "Line Mode" or "RSTP" of the dual-LAN interface (DNIP), redundancy concepts on Ethernet level can be
realized.
12.6.6.1 104-Redundancy
The "104-Redundancy" is defined in the IEC 60870-5-104 standard.
With 104-redundancy, one or more substations (Controlled Station) are connected to one or more redundant
master stations (Controlling Stations) via several logical connections. The data transfer always takes place via
only 1 started connection per redundancy group.
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 test frames
• One redundancy group is only supplied by one process image (data base)
There is a TCP connection for each redundant Ethernet interface of the remote station and these redundant
connections are combined into a redundancy group. Only one of the redundant connections may be started
by the controlling station and transmit data. At the NIP, the 104-redundancy group can be described like a
switch which controls the sending of data to the started connection.
The 104-redundancy with 2 Ethernet interfaces uses an additional logical switch on the BSE which selects to
which NIP the data to be sent is forwarded, and thus the redundancy group extends over both NIPs and the
BSE.
NOTE
i The 104-redundancy "Controlled with 2 Ethernet interfaces" can only be used within one basic system
element (BSE).
A distribution of 104-redundancy over several BSE's is not supported!
The controlling station switches between the redundant connections. There are two types of redundancy
switching, the "soft switchover" and the "hard switchover".
The soft switchover is applied, e.g. during tests or when a part of the controlling station is to be decommis-
sioned. First, the previously started connection is stopped with a STOPDTact. Only when STOPDTcon has been
received by the controlling station a STARTDTact will be sent from the controlling station to another connec-
tion. This then becomes the new started connection.
The hard switchover occurs primarily when the controlling station detects a connection failure (for example,
a 104 timeout). The controlling station will immediately send a STARTDTact to another connection. This then
becomes the new started connection. If the previously started connection in the controlled station is still
established at this time (because the controlled station has not yet detected a connection failure), it is immedi-
ately closed.
Several independent redundancy groups are possible. Each connection can be assigned to exactly one redun-
dancy group.
The connection parameterization, the connection state and the redundancy state can be read out from PRE in
the ST emulation with the command "idh".

DC8-037-2, Edition 11.2020
12.6 IEC 60870-5-104
12.6.6.2 104 redundancy „Controlling“
The 104 redundancy "Controlling" enables the interfacing of a central station to one or more remote stations.
One PRE in the central station works as a controlling station. The number of controlling stations depends on
the redundancy configuration and the PRE's can be equipped as required (mixed configurations are also
possible):
• on one BSE
• on various BSE’s within one component
• on various BSE’s in different components

Redundancy switching is controlled by the BSE with the redundancy A/P control message (FC 159, IC 1) - the
entire PRE is switched to passive or active. With redundancy switching, all redundant connections of a PRE are
switched together with STARTDT or STOPDT. It is not possible to switch some connections as started (with
STARTDT) and other connections as stopped (with STOPDT).
The redundancy control logic (active/passive switching) controls all connections that are parameterized as
"104-redundancy controlling:
• PRE is set to “active“:

– 104 data transfer is started with STARTDTact when connection is established.
– should be confirmed by the remote station with STARTDTcon.
• PRE is set to “passive“:

– 104 data transfer is stopped with STOPDTact when connection is established.
– should be confirmed by the remote station with STOPDTcon.
When the START/STOP switchover has been acknowledged with "STARTDTcon / STOPDTcon" from all connec-
tions, a redundancy A/P control acknowledgment message (FC 159, IC 2) is returned to the BSE.
In the following cases, a connection is not taken into account during redundancy switching and the handling
of the A/P control message acknowledgment (FC 159, IC 2):
• the connection fails (remote device close the connection → IEC 104 Timeout) before a STARTDTcon /
STOPDTcon is received. The A/P control acknowledgment message will be delayed until the remote
station is detected as failed.
• The connection is established during redundancy switchover and started if necessary.
Operating Mode of the 104-Redundancy “Controlling”:

The redundancy control evaluates the criteria for a redundancy switchover and sets the controlling stations
used in the redundancy configuration to started or stopped. Depending on the redundancy group, two to four
controlling stations are possible. A maximum of one controlling station may be started.
After a redundancy switchover the redundancy control logic must wait for the A/P control acknowledgment
message from the PRE before initiating another switchover, otherwise the following behavior may occur:
• Hard switchovers and connection terminations
• Non-IEC 104 compliant behavior

The redundancy control requires additional functionality, which can be implemented as follows:
• SICAM RTUs Redundancy or
• recundancy controlled by logic (CAEx)

DC8-037-2, Edition 11.2020
12.6 IEC 60870-5-104
Prosess data message handling between BSE and PRE depends on the redundancy and connection state.
Process data messages to the PRE are, depending on the operating state, fetched and sent, fetched up and
discarded or piled up.
PRE active/passive Connection Handling of Data Note
104-data transfer (Data BSE → PRE)
passive/STOPDT down fetched and discarded • loss of data on this
PRE
passive/STOPDT up fetched and discarded • loss of data on this
PRE

DC8-037-2, Edition 11.2020
12.6 IEC 60870-5-104
PRE active/passive Connection Handling of Data Note

104-data transfer (Data BSE → PRE)
aktive/STARTDT down piled up • ring overflow
possible (loss of
data)
• confirmation time-
outs
aktive/STARTDT up fetched and discarded
Process data messages received from the remote station are forwarded without change to the BSE.
Parameter settings for the 104-Redundancy “Controlling”

(valid for all connections with controlling functionality of the 104-redundancy)
The number of connections with controlling redundancy on one NIP is functionally unlimited, all 100 connec-
tions of one NIP can be operated with controlling redundancy (see recommendations in the function over-
view).
• The parameter [PRE] Redundancy | Redundancy mode must be set to 104-Redundancy .
• The the parameters of the connection definitions the parameter Connection definition |
Connection must be set to enabled .
• The IEC 60870-5-104 data flow control of the own station (Controlling / Controlled) must be set in the
parameters of the connection definitions with the parameter Connection definition | data
flow routing must be set to controlled.
• The “redundancy“ mode must be set in the parameters of the connection definitions with the parameter
Connection definition | Redundancy to 104-Contr-Red.
• In the parameters of the connection definitions the parameter Connection definition |

RedGroup is not relevant.
• In the parameters of the connection definitions, set the parameter Connection definition | Stop
behavior to store.
• In the parameters of the connection definitions, set the parameter Connection definition |
Station failure to notify.
• In the parameters of the connection definitions, set the parameter Connection definition |
Clear ring buffer to No.
• In addition, all required parameters such as the IP address of the remote station, ... must be parameter-
ized for the connections in the parameters of the Connection definition.
• The parameter Redundancy | Station number is not evaluated.
• If the PRE is switched to "passive" by the redundancy control of the BSE, the transmission of the telegram
"<TI:=103> Clock synchronization command“ can be suppressed with parameter Redundancy | Send
time setting (TI103) if passive .
• If the PRE is switched to "passive" by the redundancy control of the BSE, the transmission of the telegram
"<TI:=107> Check command with time tag CP56Time2a“ can be suppressed with parameter Redundancy
| Send test command (TI107) if passive .
• The parameter Redundancy | Disable Ethernet-Port if passive must be set to "no".
With PRE 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.

DC8-037-2, Edition 11.2020
12.6 IEC 60870-5-104
The PRE redundancy mode is selected by setting the parameter Connection definition | Redundancy
to none .
The switchover of the redundancy state ("ACTIVE" ↔ "PASSIVE") takes place system-internal through redun-
dancy control messages.
Operating mode of the redundancy control for PRE-redundancy
• There is no difference between redundancy state "ACTIVE/PASSIVE" on the IEC 60870-5-104 interface.
• 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 BSE to the PRE 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 PRE and not selectively per connection.
Parameter settings PRE-Redundancy:
• The "PRE-Redundancy" is selected by setting the parameter Connection definition | Redun-

dancy to none.
• The parameter [PRE] Redundancy | Redundancy mode must be set to "104-Redundancy" .
• The parameter Redundancy | Station number for received messages is not evaluated.
• For all connections of the 104 redundancy group, the parameter Connection definition | data
flow routing must be set to "controlled" .
• In the redundancy state "PASSIVE", the message "<TI=107> check command with time tag CP56Time2a"
can be disabled for transmission by the PRE with the parameter Redundancy | Send test command
(TI107) if passive .
• In the redundancy state "PASSIVE", the message "<TI:=103> Clock synchronization command" can be disa-
bled for transmission by the PRE with the parameter Redundancy | Send time setting (TI103)
if passive .
• In the redundancy state "PASSIVE", the Ethernet interface can be deactivated with the parameter Redun-
dancy | Disable Ethernet-Port if passive .

DC8-037-2, Edition 11.2020
12.6 IEC 60870-5-104
NOTE
i There is no difference between redundancy state "active / passive" on the IEC 60870-5-104 interface.
When using IEC 104 redundancy “Controlled" and "PRE Redundancy" at the same time, the following must
be observed with the following configuration:
Configuration:
• 2 telecontrol front ends (at one time one is active and one passive).
On each telecontrol front end, 104 redundancy "Controlled" is parameterized.
• 2 SCADA systems with 104 redundancy “Controlling" parameterized.

Each SCADA system has a connection to each telecontrol front end.
What is to be considered:
• In total there are two IEC 104 redundancy groups with two connections each.
For each redundancy group, a connection has been started.
• The IEC 104 redundancy control in the SCADA system must recognize which telecontrol frontend is
active.
e.g.: only the active telecontrol front end send <TI:=103> or <TI:=107> messages.
With this the SCADA system can recognize the active telecontrol frontend.
– in SICAM RTUs telecontrol frontend the sending of messages with <TI:=103> or <TI:=107> can be
disabled in redundancy state “passive”.
12.6.6.4 Port-Redundancy (deactivation of Interface)
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 PRE 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 IEC 60870-5-104 connections will be released after 104 timeouts

The function "Deactivation of interface" can not be used with dual-LAN interface (DNIP)!
12.6.6.5 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".

DC8-037-2, Edition 11.2020
12.6 IEC 60870-5-104
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 continu-
ously 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!
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 synchro-
nous 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 trans-
ferred to the BSE for each synchronous 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 BSE.
The synchronism of the connections is controlled directly by the LAN/WAN-protocol element. The data trans-
ferred from the BSE 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 trans-
mission can only then take place when all remote stations have acknowledged.

DC8-037-2, Edition 11.2020
12.6 IEC 60870-5-104
In transmit direction, on the BSE 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 BSE 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 defini-
tions | Redundancy .
The virtual connection is used only for internal communication with the BSE. This connection is not
present on the LAN (the IP address of the virtual connection is not relevant and will not be 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 in Connection definition.
• 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 Connec-
tion definition | Data Flow Control for the virtual connection!
Necessary parameter settings of the communications function/topology on the BSE for synchronous connec-
tions 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"!
Data in transmit direction are transferred from the basic system element (BSE) to the protocol element (PRE) in
the SICAM RTUs internal format. These are converted by the protocol element to the IEC 60870-5-104

DC8-037-2, Edition 11.2020
12.6 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.
12.6.7.1 Blocking
For the optimum utilization of the transmission paths, for the data transmission with IEC 608705104 protocols
the "Blocking" according to IEC 60870-5-101/104 is implemented. This function is performed on the basic
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.
processing. Received messages with maximum length are transmitted SICAM RTUs internal in several blocks to
the basic system element (BSE) because of the additionally required transport information.
• 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)
• Time stamp (IV=1) in Messages in Transmit Direction
• Originator address = 0 for all messages in transmit direction
• Data Throughput Limitation
• Special functions DBAG
• Special functions RWE

With the setting of the parameter [PRE] Station definition (Connection definition) |
Station 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.

DC8-037-2, Edition 11.2020
12.6 IEC 60870-5-104

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
i This function is only active for process information messages in transmit direction.
The day of week in clock synchronization command message is not affected!
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
i 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).
Originator Address = 0 for all Messages in Transmit Direction

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 the protocol element.
WhiteList-Filter
Caused by increased using of the norm protocol IEC 60870-5-101/104 in the area of the telecontrol engi-
neering/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.

DC8-037-2, Edition 11.2020
12.6 IEC 60870-5-104
The WhiteList-Filter can be enabled for each single connection with the parameter Connection defini-
tion | Profile (type identification check) .
Following WhiteList-Filters can be selected: 153
– This profile can be used on interfaces between different providers or regions within same provider.
– From the pre-defined WhiteList-Filter only selected type identifications in transmit/receive direction
are passed through (siehe Profile Definition: “WhiteList-Filter“ , Page 864).
• 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 this state 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.
153 For profiles additional parameter settings (BSE + PRE) are required! (Profile definitions later in this chapter)

DC8-037-2, Edition 11.2020
12.6 IEC 60870-5-104
• SICAM RTUs - IEC104 (“SICAM RTUs “Standard“)

– WhiteList-Filter switched off (=Default).
– This profile is typically used for interfacing SICAM RTUs systems within region of same provider.
– All supported type identifications from interoperability 12.6.9 Interoperability IEC 60870-5-104 incl.
type identifications used by SICAM RTUs in private range (remote diagnostics, remote configuration,
…) will be passed through in transmit-/receive direction.
• IEC 60870-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 IEC 60870-5-104 by KEMA.
– Only the supported type identifications from interoperability for SICAM RTUs “Protocol Implementa-
tion 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 irection.
– Type identifications in private range (e.g.: remote diagnostics, remote parameterization,…) will not
be supported! Spontaneous tasks are not supported.
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 154

(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 154
(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/connection.
For commands received with COT=ACT/DEACT, the reply for the command in transmit direction with
COT=ACTCON (DEACTCON)/ACTTERM will be passed only in a time 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.
Profile Definition: “WhiteList-Filter“

The following table includes the profile definition for “WhiteList-Filter“ and "WhiteList-Filter for passive
PRE" .
154 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.

DC8-037-2, Edition 11.2020
12.6 IEC 60870-5-104

DC8-037-2, Edition 11.2020
12.6 IEC 60870-5-104
Table 12-2 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> := Confirmation of activation
<8> := Abortion of activation
<9> := Confirmation of the abortion of activation
<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

DC8-037-2, Edition 11.2020
12.6 IEC 60870-5-104
<47> := unknown information object address

<48, 63> := for special use (private range - not used)
Profile Definition "SICAM RTUs – IEC104"

The profile SICAM RTUs – IEC104 (“SICAM RTUs Standard“) defines the functionality according to 12.6.9 Inter-
operability IEC 60870-5-104. This profile will be used as standard for interfacing SICAM RTUs components.

DC8-037-2, Edition 11.2020
12.6 IEC 60870-5-104
*) blank or “X“ only

+ secondary application function only
5) transparent transmission by system
6) Reception possible, thereby the blocked single-point information is deblocked and further individ-
ually processed as TI = 30 (address translation occurs algorithmic)
7) Not supported; reply sent with COT=45 „unknown cause of transmission“
Profile Definition "IEC 60870-5-104 Ed.2"

The profile IEC 60870-5-104 Ed.2 (“KEMA Conformance tested“) defines IEC 60870-5-104 Ed. 2 functionality
as conformance tested by KEMA. This profile is used at interfaces required functionality as conformance tested
according IEC 60870-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“

DC8-037-2, Edition 11.2020
12.6 IEC 60870-5-104

DC8-037-2, Edition 11.2020
12.6 IEC 60870-5-104
*) blank or “X“ only

+ secondary application function only
X* can be generated by the PLC
1) transparent transmission by system
Use Cases
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.

DC8-037-2, Edition 11.2020
12.6 IEC 60870-5-104
[dw_whitelist_partnerkopplung_a8000, 1, en_US]
Partner Interface between SICAM RTUs System and 3rd Party System
Data exchange via interface (LAN, serial) between different partners (utilities) – one partner use SICAM RTUs
system the other partner uses a 3rd party system.
[dw_whitelist_partnerkopplung_a8000_fremdsys, 1, en_US]
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.

DC8-037-2, Edition 11.2020
12.6 IEC 60870-5-104
[dw_whitelist_intern_segm_a8000, 1, en_US]
Internal Segmentation between SICAM RTUs Systems and 3rd Party Systems
Data exchange via interface (LAN, serial) between different divisions within the same customer – one division
uses a SICAM RTUs system the other division uses a 3rd party system.
[dw_whitelist_intern_segm_a8000_fremdsys, 1, en_US]
Redundant SICAM RTUs Automation Units

The WhiteList-Filter is only enabled on the interfaces between the redundant systems. All other interfaces are
not affected.

DC8-037-2, Edition 11.2020
12.6 IEC 60870-5-104
Redundant SICAM RTUs Basic System Elements (BSE)
• 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.
Note: A routing of data messages to redundant BSE will be suppressed per standard by passive BSE.
• The parameter "WhiteList-Filter for passive PRE" must be applied to both BSE.
• The WhiteList-Filter is only activated on “passive” BSE and deactivated on “active” BSE.

DC8-037-2, Edition 11.2020
12.6 IEC 60870-5-104
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 parameter "WhiteList-Filter for passive PRE" must be applied to both BSE.
• 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.

DC8-037-2, Edition 11.2020
12.6 IEC 60870-5-104
Data Throughput Limitation

The protocol element for IEC 60870-5-104 in SICAM RTUs supports a limitation of data throughput in
transmit-/receive direction for IEC 60870-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 IEC 60870-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 IEC 60870-5-104
• data throughput limitation in transmit direction in case of exceeded limit by delay of transmission of IEC
60870-5-104 data messages

DC8-037-2, Edition 11.2020
12.6 IEC 60870-5-104
NOTE
i The data throughput limitation works properly only if the IEC 60870-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 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.
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 IEC 60870-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 = IEC 60870-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 perma-
nently 90% of the parameterized limit within the last 10 minute window.
Special functions DBAG

For the implementation of the protocol firmware in DBAG projects the following special functions can be acti-
vated:
• 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 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 pattern" is converted as follows:
Cause of IEC-Parameter Type Identification for Transmission to the Remote Station
Transmission
spontaneous - <TI=150> DBAG-specific format
GI with time (3 octets) <TI=4> Double-point information with time tag
GI with time (7 octets) <TI=31> Double-point information with time tag CP56Time2a
GI without time <TI=3> Double-point information

DC8-037-2, Edition 11.2020
12.6 IEC 60870-5-104
In receive direction <TI=150> is converted as follows:

Cause of Time Format Type Identification for Transmission to Basic System
Transmission Element
spontaneous, with time (7 octets) <TI=33> Bitstring of 32 bits with time tag CP56Time2a
GI
NOTE
i 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!
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 | parameter settings for DBAG/PSI | Switch transfer
time in transmit direction .
Message structure <TI=150> "Railway-specific Format" (in the private range)
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

DC8-037-2, Edition 11.2020
12.6 IEC 60870-5-104
specific settings | parameter settings for 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).
Special Functions RWE

For the implementation of the protocol firmware in RWE projects the following special functions can be acti-
vated:
• 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

These special functions can be activated with the parameter Advanced parameters | Project
specific settings | RWE functions and are effective for all connections of the LAN/WAN protocol
element.
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.
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 Address Range for Fields
the 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]
NOTE
i • 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:

DC8-037-2, Edition 11.2020
12.6 IEC 60870-5-104
Parameterized Return Bit by Bit marking of Addresses of the Return Information deter-
Information Address the Field "Mask" mined by this
[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]
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.
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
i 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 sponta-
neous 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

DC8-037-2, Edition 11.2020
12.6 IEC 60870-5-104
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
NOTE
i 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 .
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 deter-
mined 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 parame-
ters 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.

DC8-037-2, Edition 11.2020
12.6 IEC 60870-5-104
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".
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.
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!

• Applicational control of ENABLE/DISABLE Ethernet interface

DC8-037-2, Edition 11.2020
12.6 IEC 60870-5-104
• Information to be obtained about the status of the data transfer
Block Diagram
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 used.
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 from the basic system element – regardless of the user data
to be sent and the priority control – immediately to the protocol element.
For messages with process information that are converted in SICAM RTUs to a protocol element
control message (FC=161, IC=0), an unused CASDU is to be used! All CASDUs for process information are
distributed automatically to the corresponding remote terminal unit.

DC8-037-2, Edition 11.2020
12.6 IEC 60870-5-104
Possible functions:

SF Station Z-Par FI
ENABLE Ethernet interface =
• Ethernet-Controller Chip will be

enabled
• "Ethernet-connection" (Link) is
"Activate" interface 0 - - established.
• assigned services of this Ethernet
interface are activated.
(IEC 60870-5-104, WEB, NTP,
remote operation)
DISABLE Ethernet interface =
• Ethernet-Controller Chip will be

disabled
• "Ethernet-connection" (Link) is
released.
"Deactivate" interface 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 synchroniza-
tion for the local AU, also in AK1703
Time sync. “NOK“ 3 - - the special function “Time mark (IV=1)
with messages in send direction” can
be used
This function is processed on the BSE
240 - - system message and not using PRE-
command
control message!
CASDU = BROADCAST
SCS=<ON>: set control location (HKA)
65535
(all stations)
125
SCS=<OFF>: reset control location
65535
(HKA) (all stations)
Set Control Location *) 242
65535
(selective stations)
0-99
SCS=<OFF>: reset control location
65535
(HKA) (selective stations)
command
control message!
CASDU = selective

DC8-037-2, Edition 11.2020
12.6 IEC 60870-5-104
*) 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
Legend:
125 = all stations of the selected protocol element (=GLOBAL)
Fl ... Edge
SCS ... Single command state
HKA ... Originator address (HKA) = 0 - 255
information in monitor direction and thereby enables states of the protocol elements to be
There are two different categories of return information:
• State of the stations (PRE return information "Station state" FC=161, IC=12)

(PRE return information "General" FC=161, IC=11)
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:

tion_(PRE) Station
Station failure 0-99 0 = Station OK
1 = Station NOK (failed)
Remote operation - 0 = Remote operation disabled
1 = Remote operation enabled

DC8-037-2, Edition 11.2020
12.6 IEC 60870-5-104

tion_(PRE) Station
protocol-specific return infor- 0…99 Status DATA TRANSFER (BSE) 155
mation 0 0 = data transfer from/to BSE is stopped
1 = data transfer from/to BSE is started
protocol-specific return infor- 0…99 Status DATA TRANSFER (104-Connection) 156
mation 1 0 = IEC 60870-5-104 data transfer is stopped (STOPDTact)
1 = IEC 60870-5-104 data transfer is started (STARTDTact)
Legend:
0 - 99 station of the selected protocol element
125 Station number not used!
12.6.9 Interoperability IEC 60870-5-104
This companion standard presents sets of parameters and alternatives from which subsets must be selected to
implement particular telecontrol systems. Certain parameter values, such as the choice of “structured“ or
“unstructured“ fields of the INFORMATION OBJECT ADDRESS of ASDUs represent mutually exclusive alterna-
tives. This means that only one value of the defined parameters is admitted per system. Other parameters,
such as the listed set of different process information in command and in monitor direction allow the specifi-
cation of the complete set or subsets, as appropriate for given applications. This clause summarizes the
parameters of the previous clauses to facilitate a suitable selection for a specific application. If a system is
composed of equipment stemming from different manufacturers it is necessary that all partners agree on the
selected parameters.
The interoperability list is defined as in IEC 60870-5-101 and extended with parameters used in this standard.
The text descriptions of parameters which are not applicable to this companion standard are strike-through
(corresponding check box is marked black).
NOTE: In addition, the full specification of a system may require individual selection of certain parameters for
certain parts of the system, such as the individual selection of scaling factors for individually addressable
measured values.
The selected parameters should be marked in the white boxes as follows:
A black check box indicates that the option cannot be selected in this companion standard.
155 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)"
156 actual state of "DATA TRANSFER (104 Connection)"

DC8-037-2, Edition 11.2020
12.6 IEC 60870-5-104
"X")
System definition
(network-specific parameter, all configurations that are used are to be marked "X")
(network-specific parameter, all interfaces and data rates that are used are to be marked "X")

interchange Circuit V.24/ interchange Circuit V.24/ interchange CircuitX.24/
V.28 V.28 X.27
bit/s
300 bit/s 9 600 bit/s 9 600 bit/s
600 bit/s 19 200 bit/s
1 200 bit/s 38 400 bit/s

interchange Circuit V.24/ interchange Circuit V.24/ interchange Circuit X.24/
V.28 V.28 X.27
bit/s

DC8-037-2, Edition 11.2020
12.6 IEC 60870-5-104
300 bit/s 9 600 bit/s 9 600 bit/s
600 bit/s 19 200 bit/s
1 200 bit/s 38 400 bit/s
12.6.9.4 Link Layer
(network-specific parameter, all options that are used are to be marked "X") Specify the maximum frame
length. If a non-standard assignment of class 2 messages is implemented for unbalanced transmission, indi-
cate the Type ID and COT of all messages assigned to class 2.)
standard.
2 Octets
structured
unstructured
Frame length
Time period in which repetitions are allowed (Trp) or number of repetitions


9, 11, 13, 21 <1>

DC8-037-2, Edition 11.2020
12.6 IEC 60870-5-104
NOTE: In response to a class 2 poll, a controlled station may respond with class 1 data when there is no class 2
data available.

companion standard.

1 Octet 2 Octets

1 Octet structured
3 Octets
2 Octets (with originator address)
1 Octet
Length of APDU
(system-specific parameter, specify the maximum length of the APDU per system)
The maximum length of the APDU in both transmission directions is 253. This is a fixed system parameter.
Length of APDU
Maximum length of APDU per system in control direction
Maximum length of APDU per system in monitoring direction


DC8-037-2, Edition 11.2020
12.6 IEC 60870-5-104

DC8-037-2, Edition 11.2020
12.6 IEC 60870-5-104
M_EP_TF_1
CP56Time2a
In this companion standard only the use of the set <30> – <40> for ASDUs with time tag is permitted.




DC8-037-2, Edition 11.2020
12.6 IEC 60870-5-104
<107> := Test command with time tag CP56time2a C_CD_NA_1
X** … supported but not recommended (bad accuracy)

File transfer
<127>:= QueryLog – Request for an archive file F_SC_NB_1


DC8-037-2, Edition 11.2020
12.6 IEC 60870-5-104

[Type_Identification_1, 1, en_US]

DC8-037-2, Edition 11.2020
12.6 IEC 60870-5-104
[Type_Identification_2, 1, en_US]

DC8-037-2, Edition 11.2020
12.6 IEC 60870-5-104
[Bedeutung_Übertragunsursachen, 1, en_US]

Read procedure
Read procedure


DC8-037-2, Edition 11.2020
12.6 IEC 60870-5-104
Global
group 5 group 11
Information Object
group 6 group 12
separate table.
Day of week used
B** supported but not recommended (bad accuracy) By default time synchronization is done by NTP/SNTP
Optional, see 10.5.8.6

DC8-037-2, Edition 11.2020
12.6 IEC 60870-5-104
C_SE ACTTERM used
Persistent output
B* can be used only when the COT is generated via a function plan application (CAEx)
Supervision of maximum delay in command direction of commands and set point commands
Maximum allowable delay of commands and set point commands

Counter read
counter reset

DC8-037-2, Edition 11.2020
12.6 IEC 60870-5-104

Threshold value
Smoothing factor
Test procedure
(station-specific parameter, mark "X" if function only used in standard direction, "R" if only used in the reverse
direction, and "B" if used in both directions)
Test procedure
file transfer
Transparent file
Transparent file

DC8-037-2, Edition 11.2020
12.6 IEC 60870-5-104
Background scan
Background scan

Definition of time outs
Parameters Default Value Note Selected value

t0 30 s Time-out of connection establishment
t1 15 s Time-out of send or test APDUs
t2 10 s Time-out for acknowledges in case of no
data messages t2<t1
t3 20 s Time-out for sending test frames in case of a
long idle state t3>t1
Maximum range of values t0 to t2 : 1 to 255 s, accuracy 1 s

Recommended range of values t3 : 0 s to 48 h, accuracy 1 s
Large range of values t3 are needed in special cases, where satellite or dial-up connections are used (for
example, with only daily or weekly connection setup for data transmission).
Maximum numbers of outstanding l format frames k and latest acknowledge
Parameters Default Value Note Selected value

k 12 APDUs Maximum difference receive sequence
number to send state variable
w 8 APDUs Latest acknowledge after receiving w I-
format APDUs
Maximum range of value k k: 1 to 32 767 (215 – 1) APDU, accuracy 1 APDU. 158

Maximum range of value w: 1 to 32 767 APDU, accuracy 1 APDU (Recommendation: w should not exceed 2/3
of k). 158
Port number
Parameters Value Note
Port number 2404 In all cases
Redundant Connections
Number N connections used in redundancy group
158 SICAM A8000 supports only 1 to 128 APDUs

DC8-037-2, Edition 11.2020
12.6 IEC 60870-5-104
RFC 2200 suite

RFC 2200 is an official Internet Standard which describes the state of standardization of protocols used in the
Internet as determined by the Internet Architecture Board (IAB). It offers a broad spectrum of actual standards
used in the Internet. The suitable selection of documents from RFC 2200 defined in this standard for given
projects has to be chosen by the user of this standard.
Ethernet 802.3
Serial X.21 interface
Other selection from RFC 2200
List of valid documents from RFC 2200

1. ………………………………………
2. ………………………………………
3. ………………………………………
4. ………………………………………
5. ………………………………………
6. ………………………………………
7. etc.

DC8-037-2, Edition 11.2020
12.7 IEC 61850
12.7 IEC 61850
12.7.1 Introduction
IEC 61850 is a general, network-based transmission protocol for the protection and control in electrical switch-
gear 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 samples according to standard IEC 61850-9-1

(is currently not supported by the protocol element Server + Client!)
• Transmission of GOOSE messages according to standard part IEC 61850-8-1

The IEC 61850 Client actively establishes the connection and fetches data from a IEC 61850 Server or sends
data to a IEC 61850 Server. The IEC 61850 Server waits passively for a connection established by a IEC 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.
One major peculiarity of the IEC 61850 protocol is the decoupling of the object-orientated technological repre-
sentation of the data from the communication. The IEC 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
A8000 protocol element supports either IEC 61850-Server function or IEC 61850-Client function.
The following Firmwares are available for the different systems:

DC8-037-2, Edition 11.2020
12.7 IEC 61850

ET85 CP-8000 IEC 61850 Edition 1+2 Client
CP-802x IEC 61850 Edition 2 Server +
GOOSE
NOTE
i 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.
12.7.2 Functions
General Functions IEC 61850 Client
• LAN/WAN communication over Ethernet TCP/IP - general

– 100 Mbit/s (full duplex, auto-negotiation) 159
– Auto-MDIX (Auto Medium Dependent Interface Crossover) 159
• IEC 61850 Client

– Edition 1
– Edition 2
– Max. number of servers (max. connections): 100 (recommended: 20)
– Max. number of “Logical Devices” (for each connection): 160
– Max. number of “Logical Devices” (for each connection): 160
– Max. number of data points: 1000
– Startup time PRE: 161
– Initialization (after startup time PRE)162
– ACSI Services 163
– Common Data Classes 163
– Attributes 163
– Supported functionality according to:
– PICS (Protocol Implementation Conformance Statement)
– PIXIT (Protocol Implementation Extra Information)
– Supported Logical Nodes and their Attributes
• Certificate (AoC Attestation of Conformity)

UCA: IEC 61850 Certificate Level A for the client system: SICAM A8000 CP-8000 modular device for tele-
control and automation applications. Software version: ET85 Rev. 03.04 issued by DNVGL (KEMA) No.
84000136-OPE/INC 17-1739 Sachnummer: SC8-505-1.Cl/79
159 function is integrated in the master module

160 not limited (limited only by free memory)
161 due to performance matters (initialization times upon connection setup), no more than 2000 data points are recommended
162 Max. startup time (with10000 data points): approx. 4 min Min. startup time (with 1 data point): approx. 30 to 60 s (dependent on
the configuration of the AU)
163 supported only to a limited extent (for details see section 12.7.6.1 Objects and Data | Basic Data Types and section 12.7.8.2 Conver-
sion IEC 60870-5-101/104 ↔ IEC 61850

DC8-037-2, Edition 11.2020
12.7 IEC 61850
• Security IEC 62315-3,4 (2006)

Application Security
– A-security profile
Transport Security
– TLS
• Supported ports
– Port 102: MMS (Manufacturing Message Specification)
– Port 3782: MMS (Manufacturing Message Specification) TLS
– Port 80: HTTP (Hypertext Transfer Protocol) – Web server 159
– Port 80: HTTP (Hypertext Transfer Protocol) - Remote operation for SICAM TOOLBOX II 159
– Port 443: HTTPS (Hypertext Transfer Protocol over SSL/TLS) – Web server 159
– Port 443: HTTPS (Hypertext Transfer Protocol over SSL/TLS) - Remote operation for SICAM TOOLBOX
II 159
– Port 123: NTP V3 (Network Time Protocol) 159
– Port 123: SNTP V3 (Simple Network Time Protocol) 159
• Acquisition of events
– Static Data Sets
– Dynamic Data Sets
– Buffered Reports
– Unbuffered Reports
• File transfer
– Disturbance records to SICAM DISTO
• General Interrogation
– Command interlocking
– Direct Control with Normal Security
– Direct Control with Enhanced Security
– SBO control with enhanced security
• Parameter Groups
• Clock synchronization according to NTP (Network Time Protocol)

– NTP Server 159
– NTP Client 159
– SNTP Client 159
– Conversion of the time information (UTC; local time w/wo normal time/daylight saving time)

DC8-037-2, Edition 11.2020
12.7 IEC 61850

– Dual LAN interface with integrated switch for ring or star configurations
– Switch Mode 159
– Single Mode 159
– Single + Service Mode 159

Protocol element control
– START connection to server (“Initiate”)
– STOP connection to server (“Conclude”)
• SICAM TOOLBOX II connection over LAN/WAN (remote connection)

– Remote connection based on HTTP/HTTPS 159
– User authentication in SICAM RTUs using connection password (optional) 159
– Warning Remote operation 159
• Web Server
– Integrated web server to display connection-/statistic-/developer information
– Access to the web server with standard web browser via HTTP 159
– Access to the web server with standard web browser via HTTPS 159
– Conversion of the time information (UTC; local time with/without Summer-Wintertime)
– 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
– Monitoring intermediate and faulty positions of double-point information
– Remote parameterization/diagnostic of SICAM RTUs components via 61850
General Functions IEC 61850 Server
• LAN/WAN communication over Ethernet TCP/IP

– 100 Mbit/s (full duplex, auto-negotiation) 159

DC8-037-2, Edition 11.2020
12.7 IEC 61850
• IEC 61850 Server

– Edition 2
– GOOSE
GOOSE Publish and GOOSE Subscribe support with
– IEC 61850 Ed. 1: only data attributes (no Data Objects)!
– IEC 61850 Ed. 2: Data attributes and data objects (data structures) with following CDCs: (FC=
ST): SPC, DPC, ENC, INC, SPS, DPS, ENS
– Max. number of servers (max. connections): 6
– Max. number of logical devices (including all servers): 500
– Max. number of logical nodes (including all servers): 160
– Max. number of data points: 164
– Supported functionality according to:
– PICS (Protocol Implementation Conformance Statement)
– PIXIT (Protocol Implementation Extra Information)
– Supported Logical Nodes and their Attributes
• Certificate (AoC Attestation of Conformity)

UCA: IEC 61850 Certificate Level A for the Server product: SICAM A8000 CP-8000 modular device for tele-
control and automation applications. Software version: ET85 Rev. 03.04 issued by DNVGL (KEMA) No.
844000136-OPE/INC 17-1741 Sachnummer: SC8-505-1.Se/79
• Security IEC 62315-3,4 (2006)

Application Security
– A-security profile
Transport Security
– TLS
• Supported ports
– Port 102: MMS (Manufacturing Message Specification)
– Port 3782: MMS (Manufacturing Message Specification) TLS
– Port 80: HTTP (Hypertext Transfer Protocol) – Web server 159
– Port 80: HTTP (Hypertext Transfer Protocol) - Remote operation for SICAM TOOLBOX II 159
– Port 443: HTTPS (Hypertext Transfer Protocol over SSL/TLS) – Web server 159
– Port 443: HTTPS (Hypertext Transfer Protocol over SSL/TLS) - Remote operation for SICAM TOOLBOX
II 159
– Port 123: NTP V3 (Network Time Protocol) 159
– Port 123: SNTP V3 (Simple Network Time Protocol) 159
– Static Data Sets
– Buffered Reports
– Unbuffered Reports
164 See: Formulas for the determination of the total number of data points (n):, Page 906

DC8-037-2, Edition 11.2020
12.7 IEC 61850
• File transfer
– Disturbance records to SICAM DISTO
• General Interrogation
– Direct Control with Normal Security
– Direct Control with Enhanced Security
– SBO control with enhanced security
• Parameter Groups
• Clock synchronization according to NTP (Network Time Protocol)

– NTP Server 159
– NTP Client 159
– SNTP Client 159
– Conversion of the time information (UTC; local time w/wo normal time/daylight saving time)

– Server Redundancy
– GOOSE redundancy

Protocol element control
• SICAM TOOLBOX II connection over LAN/WAN (remote connection)

– Remote connection based on HTTP/HTTPS 159
– User authentication in SICAM RTUs using connection password (optional) 159
– Warning Remote operation 159
• Web Server
– Remote connection based on integrated terminal server (Enable/Disable) option
– Access to the web server with standard web browser via HTTP 159
– Conversion of the time information (UTC; local time with/without Summer-Wintertime)
– Technological Adaptation for Measured Values
– Logging of the remote commands at the local control center
– Automatic Load Shedding
– Remote parameterization/diagnostic of SICAM RTUs components via 61850
NOTE
i At the moment IEC 61850 Server can only be engineered with SICAM TOOLBOX II (not with SICAM WEB).

DC8-037-2, Edition 11.2020
12.7 IEC 61850
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:
#LD Number of Logical Devices
#CON Number of Connections
#DP Number of data points
The following maximum value applies: n = 20000

optional DTE
(twisted pair) X4
NOTE
12.7.4 Communication- ET85 Client
Own Station (Client)

SICAM A8000 Series CP-8000/CPC80 ET85 Edition 1 + 2
CP-802x/CPC80
Remote station (Server)

SICAM A8000 Series CP-8050/CPCI85 ETI5 Editon 2
SICAM A8000 Series CP-8000/CPC80 ET85 Editon 2
CP-802x/CPC80
SICAM AK 3 CP-2016/CPCX26 ET25 Edition 2
CP-2019/PCCX26 SM-2558/ETA5 Edition 2
Legacy systems CP-20xx SM-2558/ETA5 Editon 2
(SICAM AK, SICAM TM, CP-60xx SM-2558/ETA3 Editon 1
SICAM BC) CP-50xx SM-2557/ET03 Editon 1
IEC 61850 interoperability
Protection devices of - - IEC 61850 interoperability
SIPROTEC series
Third-party system – – IEC 61850 interoperability

DC8-037-2, Edition 11.2020
12.7 IEC 61850
12.7.5 Communication - ET85 Server
Own Station (Server)

SICAM A8000 Series CP-8000/CPC80 ET85 Edition 2
CP-802x/CPC80
Remote station (Client)

SICAM A8000 Series CP-8050/CPCI85 ETI5 Editon 2, Edition 2.1
SICAM A8000 Series CP-8000/CPC80 ET85 Editon 2, Edition 2.1
CP-802x/CPC80
SICAM AK 3 CP-2016/CPCX26 ET25 Editon 2, Edition 2.1
CP-2019/PCCX26 SM-2558/ETA5 Editon 2, Edition 2.1
Legacy systems CP-20xx SM-2558/ETA5 Editon 2, Edition 2.1
(SICAM AK, SICAM TM, CP-60xx SM-2558/ETA3 Editon 1
SICAM BC) CP-50xx SM-2557/ET03 Editon 1
IEC 61850 interoperability
Third-party system – – IEC 61850 interoperability
12.7.6 Communication via 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 (IEC 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)

DC8-037-2, Edition 11.2020
12.7 IEC 61850
• Standardized Configurations
– devices and the entire switchgear are described completely formal
– the IEC 61850-6 standard provides an XML-based system description language (Substation Configu-
ration Language, SCL) with which the standardized configuration files are created
Protocols according to the IEC 61870-5 standard are based on the OSI layer model
Layer Task Functions, Characteristics, Comments

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
In the "private range" according to IEC 60870-5-104, Ax 1703/
SICAM RTUs-specific system messages and some user data is
implemented (e.g. transmission of disturbance records to SICAM
DISTO)

DC8-037-2, Edition 11.2020
12.7 IEC 61850
Layer Task Functions, Characteristics, Comments

5 - Session Interface between • GOOSE
data format and
communication
• MMS
protocol • HTTP
• Remote operation for SICAM TOOLBOX II
• NTP according to RFC 1305
4 - Transport Communication • TCP/IP according to RFC 791 and RFC 793; GOOSE
protocol
3 - Network • 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
• Connection technique (on the master control or communi-
cation element) RJ45 for copper and MT-RJ connector for
FO
• ARP according to RFC 826
• IP Encapsulation according to RFC 894
Relevant Standards
Standard Application
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 oper-
ating conditions)

DC8-037-2, Edition 11.2020
12.7 IEC 61850
Standard Application
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
secondary technology equipment – Abstract Communication Serv-
ices Interface (ACSI)
• Description of the abstract communication service interface (ACSI)
• Specification of the abstract communication services
• Model of the server database
secondary technology equipment – Common Data Classes
• Abstract common data classes and attribute definitions
secondary technology 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 commu-
nication 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 trans-
former (with and without Merging Unit)
IEC 61850-10 Conformity Check
• Procedure for the conformity check
IEC 60255-24 IEEE COMTRADE
NOTE
i The underlined standards contain essential information for the implementation of the IEC 61850 functions
in the protocol element.

DC8-037-2, Edition 11.2020
12.7 IEC 61850
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 Class CDC The IEC 61850 defines different Common Data Classes. 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 Set Dynamic data sets are generated (created) by the client per RUN-
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
e.g.: the static data set for 3rd 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 there-
fore 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!

DC8-037-2, Edition 11.2020
12.7 IEC 61850
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
Report Spontaneous transmission from ServerClient takes place using
Reports: [FC = BR]
• spontaneous data remain stored with interface fault Unbuf-

fered Reports: [FC = RP]
• spontaneous data is deleted with interface fault
Report Control Block Every Report (in the server) has its own Report Control 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 interrog-
ation, …)
• 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 165
PIXIT PIXIT Protocol Implementation eXtra Information for Testing 165
MICS MICS Model Implementation Conformance Statement
SCSM SCSM Specific Communication Service Mapping
PICOM PICOM Pieces of Communication
12.7.6.1 Objects and Data
Data Models
The data models for IEC 61850 describe the real data of a device, that can be read or written over the commu-
nication.
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.
165 the IEC 61850 Interoperability is documented in the documents PICS and PIXIT

DC8-037-2, Edition 11.2020
12.7 IEC 61850
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.
Physical 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, meas-
ured 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 Function: . .
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.
Logical nodes are defined in following standards:
• IEC 61850-7-4
Communication networks and systems for power utility automation
Part 7-4: Basic communication structure - Compatible logical node classes and data object classes

DC8-037-2, Edition 11.2020
12.7 IEC 61850
• IEC 61850-7-410
Communication networks and systems for power utility automation
Part 7-410: Hydroelectric power plants – Communication for monitoring and control
• IEC 61400-25
Wind Turbines
Part 25: Communications for monitoring and control of wind plants
Group (initial Logical Node Categories Number of

letter) defined
logical nodes
A Automatic Functions . 4
C Supervisory Control . 5
D Distributed Energy Resources
E Thermal power plant specific logical nodes ("Enthalpy")
F Functional Blocks
G Generic References . 3
H Hydropower specific Logical Nodes
I Interfacing and Archiving 4
..
K Mechanical and non-electrical Primary Equipment
L System Logical Node . 3
M Metering and Measurement . 8
P Protection Functions . 28
Q Power Quality Events Detection related
R Protection Related Functions 10
..
S Supervision and Monitoring 4
..
T Instrument Transformer and Sensors . 2
W Wind Power
X Switchgear . 2
Y Power Transformer and Related Functions . 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.
Client
SICAM RTU's IEC 61850 client (Ed.1 and Ed.2) supports all logical nodes based on the supported CDC's.
Server
The following logical nodes are supported by SICAM RTUs IEC 61850 Server:
Logical Nodes Description Server Server
(Ed.1) (Ed.2)
A Automatic Functions .
ACTM Control mode selection ✓
AJCL Joint control ✓
ANCR Neutral Current Regulator ✓ ✓
APSF PSS 4B filter function ✓
APSS PSS control common information ✓

DC8-037-2, Edition 11.2020
12.7 IEC 61850

(Ed.1) (Ed.2)
APST PSS 2A/B filter function ✓
ARCO Relative Power Control ✓
ARIS Resistor 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 ✓ ✓
CSYN Synchronizer controller ✓
F Functional Blocks
FCNT Counter ✓
FCSD Curve shape description ✓
FFIL Generic filter ✓
FHBT Functional heartbeat ✓
FLIM Control function output limitation ✓
FPID PID regulator ✓
FRMP Ramp function ✓
FSCH Scheduler ✓
FSPT Set-point control function ✓
FXOT Action at over threshold ✓
FXPS Functional prioirty status ✓
FXUT Action at under threshold ✓
G Generic References .
GAPC Generic Automatic Process Control ✓ ✓
GGIO Generic Process I/O ✓ ✓
GLOG Generic log ✓
GSAL Generic Security Application ✓
H Hydro Power
HBRG Turbine – generator shaft bearing ✓
HCOM Combinator ✓
HDAM Hydropower dam ✓
HDFL Deflector control ✓
HDLS Dam leakage supervision ✓
HEBR Electrical brake ✓
HGOV Governor control mode ✓
HGPI Gate position indicator ✓
HGTE Dam gate ✓
HITG Intake gate ✓
HJCL Joint control ✓
HLKG Leakage supervision ✓
HLVL Water level indicator ✓
HMBR Mechanical brake ✓
HNDL Needle control ✓

DC8-037-2, Edition 11.2020
12.7 IEC 61850

(Ed.1) (Ed.2)
HNHD Water net head data ✓
HOTP Dam over-topping protection ✓
HRES Hydropower/water reservoir ✓
HSEQ Hydropower unit sequencer ✓
HSPD Speed monitoring ✓
HSST Surge shaft ✓
HTGV Guide vanes (wicket gate) ✓
HTRB Runner blades ✓
HTRK Trash rack ✓
HTUR Turbine ✓
HUNT Hydropower unit ✓
HVLV Valve (butterfly valve, ball valve) ✓
HWCL Watern control ✓
I Generic References .
IARC Archiving ✓
IFIR Fire detection and alarm ✓
IHMI Human Machine Interface ✓ ✓
IHND Hand interface ✓
ILOC Local interface (pushbutton) ✓
ISAF Safety alarm function ✓
ITCI Telecontrol Interface ✓
ITMI Telemonitoring Interface ✓
ITPC Teleprotection communication interfaces ✓
K Mechanical and non-electrical Primary Equipment
KFAN Fan ✓
KFIL Filter ✓
KHTR Heater, cubicle heater ✓
KPMP Pump ✓
KTNK Tank ✓
KVLV Valve Control ✓
L System Logical Node .
LCCH Physical communication channel supervision ✓
LGOS GOOSE subscription ✓
LLN0 Logical Node Zero ✓ ✓
LPHD Physical Device Information ✓ ✓
LSVS Sampled value subscription ✓
LTIM Time management ✓
LTMS Time master supervision ✓
LTRK Service tracking ✓
M Metering and Measurement .
MENV Environmental information ✓
MFLK Flicker measurement name ✓
MDIF Differential Measurements ✓
MHAI Harmonics Or Interharmonics ✓
MHAN Non Phase Related Harmonics Or Interharmonics ✓
MHYD Hydrological information ✓

DC8-037-2, Edition 11.2020
12.7 IEC 61850

(Ed.1) (Ed.2)
MMDC DC measurement ✓
MMET Meteorological information ✓
MMTN Metering ✓
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 ✓ ✓
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 ✓ ✓
PRTR Rotor protection ✓
PSCH Protection Scheme ✓ ✓
PSDE Sensitive Directional Earthfault ✓ ✓
PTEF Transient Eart Fault ✓ ✓
PTHF Thyristor protection ✓
P Protection Functions .
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 ✓ ✓
Q Power Quality Events detection related
QFVR Frequency variation ✓
QITR Current transient ✓
QIUB Current unbalance variation ✓
QVTR Voltage transient ✓
QVUB Voltage unbalance variation ✓

DC8-037-2, Edition 11.2020
12.7 IEC 61850

(Ed.1) (Ed.2)
QVVR Voltage variation ✓
R Protection Related Functions .
RADR Disturbance Recorder Channel Analog C V
RBDR Disturbance Recorder Channel Binary ✓ V
RBRF Breaker Failure ✓ ✓
RDIR Directional Element ✓ ✓
RDRE Disturbance Recorder Function ✓ ✓
RDRS Disturbance Record handling ✓
RFBC Field breaker configuration ✓
RFLO Fault Locator ✓ ✓
RMXU Differential measurements ✓
RPSB Power Swing Detection / Blocking ✓ ✓
RREC Autoreclosing ✓ ✓
RSYN Synchronism-Check or Synchronising ✓ ✓
S Supervision and Monitoring .
SARC Monitoring And Disgnostic For Arcs ✓
SCBR Circuit breaker supervision ✓
SFLW Supervision of media flow ✓
SIMG Insulation Medium Supervision (Gas) ✓ ✓
SIML Insulation Medium Supervision (Liquid) ✓ ✓
SLTC Tap changer supervision ✓
SLVL Supervision of media level ✓
SOPM Supervision of operating mechanism ✓
SPDC Monitoring And Disgnostics For Partial Discharges ✓
SPOS Supervision of the position of a device ✓
SPRS Supervision media pressure ✓
SPTR Power transformer supervision ✓
SSWI Circuit switch supervision ✓
STMP Temperature supervision ✓
SVBR Vibration supervision ✓
T Instrument Transformer and Sensors .
TANG Angle ✓
TAXD Axial displacement ✓
TCTR Current Transformer ✓ ✓
TDST Distance ✓
TFLW Liquid flow ✓
TFRQ Frequency ✓
TGSN Generic sensor ✓
THUM Humidity ✓
TLEV Level sensor
TLVL Media level ✓
TMGF Magnetic field ✓
TMVM Movement sensor ✓
TPOS Position indicator ✓
TPRS Pressure sensor ✓
TRTN Rotation transmitter ✓

DC8-037-2, Edition 11.2020
12.7 IEC 61850

(Ed.1) (Ed.2)
TSND Sound pressure sensor ✓
TTMP Temperature sensor ✓
TTNS Mechanical tension / stress ✓
TVBR Vibration sensor ✓
TVTR Voltage Transformer ✓ ✓
TWPH Water acidity ✓
W Wind Power
WALG Wind turbine analogue log information
WALM Wind turbine alarm information
WAPC Wind power plant active power control information ✓
WAVL Wind turbine availability information ✓
WCNV Wind turbine converter information ✓
WGDC Wind turbine grid connection information
WGEN Wind turbine generator information ✓
WMET Wind power plant meteorological information ✓
WNAC Wind turbine nacelle information ✓
WROT Wind turbine rotor information ✓
WREP Wind turbine report information
WRPC Wind power plant reactive power control information ✓
WSLG Wind turbine state log information
WTOW Wind turbine tower information ✓
WTRF Wind turbine transformer information ✓
WTRM Wind turbine transmission information ✓
WTUR Wind turbine general information ✓
WYAW Wind turbine yawing information ✓
X Switchgear .
XCBR Circuit Breaker ✓ ✓
XFFL Switching control for field flashing ✓
XSWI Circuit Switch ✓ ✓
Y Power Transformer and Related Functions .
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 ✓

DC8-037-2, Edition 11.2020
12.7 IEC 61850

(Ed.1) (Ed.2)
ZRES Resistor ✓
ZRRC Rotating Reactive Component ✓
ZSAR Surge Arrestor ✓ ✓
ZSCR Semi-conductor controlled rectifier ✓
ZSMC Synchronous machine ✓
ZTCF Thyristor Controlled Frequency Converter ✓
ZTCR Thyristor Controlled Reactive Component ✓
Legend:
S (Ed.1) … IEC 61850 Server Edition 1
S (Ed.2) … IEC 61850 Server Edition 2
C ….…….. Client
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 .
• Common Logical Node Information .
• Status Information .
• Settings .
• Measured Values .
• Controls .

DC8-037-2, Edition 11.2020
12.7 IEC 61850
Example:
[ET03_LN_XCBR, 1, en_US]

DC8-037-2, Edition 11.2020
12.7 IEC 61850
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.
[ET03_LD_LN_CDC, 1, en_US]

DC8-037-2, Edition 11.2020
12.7 IEC 61850
The following example shows the representation of the logical node in the IEC 61850-7-4 standard for the
circuit breaker (XCBR).
[ET03_XCBR_Norm, 1, en_US]
Legend: M…Mandatory (these attributes must be supported mandatory)

O…Optional (these attributes can be supported optionally)
In field "Attr. Type" is the CDC = Common Data Class .

DC8-037-2, Edition 11.2020
12.7 IEC 61850
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)".
[ET03_DPC, 1, en_US]
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 IEC 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):
LDName/LNName.DataName.DataAttributeName
LDName ……… Logical Device Name
LNName .…….. Logical Node Name

DC8-037-2, Edition 11.2020
12.7 IEC 61850
Data and data attributes can thereby occur several times in the structure.
Edition 1:
61850 address: LDName + "/" + FCD = 32 + 1 + 29 = max. 62 characters
FCD: LNName + DataName + DataAttributeName + DataComponentName = max. 29 char-
acters
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 char-
acters
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
i 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.

DC8-037-2, Edition 11.2020
12.7 IEC 61850
The structure of the IEC 61850 address is explained with the help of the following example.
[etxx_61850_address, 1, en_US]
Examples for the valid syntax of 61650 addresses:

BC1703CTRL/Q00XCBR1.Pos.stVal
VLC01/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 IEC 61850 address with max. recursion depth:

IED001MEAS/Q1MMXU1.PhV.phsA.cVal.mag.f
BC1703_E17CTRL/GO_E07GGIO1.DPCSOQ1.stVal
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 IEC 61850 address of 62 charac-
ters.

DC8-037-2, Edition 11.2020
12.7 IEC 61850
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
VLC01/q=XCBR1$ST$Mod$stVal
T403B1CTRL$GGIO10$CO$SPCSO0$ctlVal
BC1703_E17CTRL/GO_E07GGIO1$ST$DPCSOQ1$stVal
Examples for MMS addresses with max. recursion depth:

VLC01/MMXU1$MX$A$phsA$cVal$mag$f
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 struc-
turing 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 IEC 61850 will be mapped to MMS SUB-structures (if supported by MMS) or mapped
to common data classes.

DC8-037-2, Edition 11.2020
12.7 IEC 61850
NOTE
i 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.
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 [abbrev.]166 Common Data Class Specification for Ss Se SsG SrG Cs Ce

167 167
Status Information
SPS Single Point Status ✓ - ✓ ✓ - ✓
DPS Double Point Status ✓ - ✓ ✓ - ✓
INS Integer Status ✓ - ✓ ✓ - ✓
168
ENS Enumerated Status ✓ - ✓ ✓ - ✓

168 168 168 168
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 ✓|- ✓|- ✓|- ✓|- ✓|- ✓|-
166 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)
167 in the protocol element with IEC 61850 Client function, for data (attributes) in transmit/receive direction that are not contained in
the IEC 61850 standard, the Common Data Class (CDC) can be parameterized Devices of different manufacturers utilize the possi-
bility 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: VLC01/CSWI1.SPos.ctlVal (SPos = DPC) VLC01/
XCBR1.SPos.ctlVal (SPos = DPC) VLC01/MMXU1.STotW.mag.f (STotW = MV) VLC01/MMXU1.AS.phsA.cVal.mag.f (AS = WYE)
168 applies only for IEC 61850 Edition 2

DC8-037-2, Edition 11.2020
12.7 IEC 61850
CDC [abbrev.]166 Common Data Class Specification for Ss Se SsG SrG Cs Ce

167 167
INC [ST|CO] Controllable Integer Status ✓|- ✓|- ✓|- ✓|- ✓|- ✓|-
168
ENC [ST|CO] Controllable Enumerated Status ✓|- ✓|- ✓|- ✓|- ✓|- ✓|-
168 168 168 168 168 168
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 ✓|- ✓|- - - ✓|- ✓|-
168 168 168 168
Status Settings
SPG [SP] Single Point Setting ✓|- ✓|- - - ✓ ✓|-
169 169 169
ING [SP] Integer Status Setting ✓|- ✓|- - - ✓ ✓

168 168
Analog Settings
ASG [SP] Analog Setting ✓|- ✓|- - - ✓ ✓
168 168
CURVE Setting Curve - - - - - -

Description Information
DPL Device Name Plate ✓ - - - - -
169
LPL Logical Node Name Plate ✓ - - - - -

169
CSD Curve Shape Description - - - - - -

SGCB Setting Group Control Block 170 ✓ ✓ - - ✓ ✓
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 [abbrev.]171 Extended Common Data Class Specification for Ss Se SsG SrG Cs Ce
167 167
Controllable Status Information

SPC [ST|CO] Extended Common Data Class Controllable Single ✓|- ✓|- ✓|- ✓|- ✓|- ✓|-
Point
DPC [ST|CO] Extended Common Data ClassControllable Double ✓|- ✓|- ✓|- ✓|- ✓|- ✓|-
Point
167 in the protocol element with IEC 61850 Client function, for data (attributes) in transmit/receive direction that are not contained in
the IEC 61850 standard, the Common Data Class (CDC) can be parameterized Devices of different manufacturers utilize the possi-
bility 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: VLC01/CSWI1.SPos.ctlVal (SPos = DPC) VLC01/
XCBR1.SPos.ctlVal (SPos = DPC) VLC01/MMXU1.STotW.mag.f (STotW = MV) VLC01/MMXU1.AS.phsA.cVal.mag.f (AS = WYE)
169 this information is generated by PRE
170 SGCB is a Control Block and not a Common Data Class, but is handled as a CDC by the protocol element

DC8-037-2, Edition 11.2020
12.7 IEC 61850
CDC [abbrev.]171 Extended Common Data Class Specification for Ss Se SsG SrG Cs Ce
167 167
INC [ST|CO] Extended Common Data Class Controllable Integer ✓|- ✓|- ✓|- ✓|- ✓|- ✓|-
Status 168
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 [ST|CO] Extended Common Data Class Controllable Analog Set ✓|- ✓|- - - ✓|- ✓|-
Point Information 168 168 168 168
Legend:
Ss Server transmitting
Se Server receiving
Cs Client transmitting
Ce Client receiving
SsG Server senden GOOSE (publish)
SrG Server receiving GOOSE (subscribe)
12.7.6.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 232, therefore 4,294,967,296 addresses can
be represented. The IP address is mostly represented in the dotted decimal notation . Definition of the
Connections
Example: 192,168,122,195
The IP address of one’s own station is to be parameterized in the system technical parameters with the param-
eter 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-tech-
nical 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 determined by the IANA (Internet Assigned Numbers Authority).
Port numbers used in the LAN/WAN protocol firmware:
Port number Protocol Standard
102 MMS ISO/IEC 9506
(Manufacturing Message Specification)
80 HTTP RFC 2616
(Hypertext Transfer Protocol) (HTTP/1.1) 172
443 HTTPS Webserver 173
(Hypertext Transfer Protocol over SSL/TLS)
172 In CP-8000/CP-802x, or SICAM AK3 with local PRE (PRE without NIP) this function is integrated on the basic system element

DC8-037-2, Edition 11.2020
12.7 IEC 61850
Port number Protocol Standard

443 HTTPS Remote operation for SICAM TOOLBOX II 174
(Hypertext Transfer Protocol over SSL/TLS)
123 NTP V3 RFC 1305 175
123 SNTP V3/V4 RFC 2030 176
(Simple Network Time Protocol)
Legend:
RFC Request for Comments
Default Router (Default Gateway)

If one’s 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, that separates an IP address into a network- 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, to 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 are set to "0".
In most cases the notation of a network mask is not carried out binary, rather (as with IP address also)
frequently in decimal notation (dotted decimal notation).
Therefore 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 the first 27 places
of the IP address of the network part and for all hosts of the network are identical. In all practical cases of
application the network part is continuous (without zeros in between).
A network mask with 27 set bits produces a network part of 192.168.122.192. 5 bits and therefore 32
addresses are left over for the device part.
In the above example the smallest host address ends with 11000000 (decimal: 192), the greatest 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 greatest address is by definition reserved for the IP Broadcast and the smallest address describes the
network itself. They are therefore not included in the freely usable addresses.
In practice the Default Gateway is often assigned to the smallest (binary in the example: 11000001, decimal:
193) or largest (binary in the example: 11011110, decimal: 222) usable IP address in the network.

DC8-037-2, Edition 11.2020
12.7 IEC 61850
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 .
The following parameters can be set for each connection:
• "Station number"
is assigned to an IP address. During the data transmission, only the IP address assigned to the station
number is transmitted, the station number is not transmitted.
During the data flow routing the data are routed for transmission to a "station number" (=Connection
number = destination station number).
The station number is to be entered for each connection in the parameters Connection definition
| Stationsnummer .
• "Enable"
A parameterized connection can be activated/deactivated with the parameter Connection defini-
tion | Enable .
Thus, connections can be prepared that are activated only at a later moment by means of parameteriza-
tion.
• "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 Station 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: With that 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 para-
meterized for every connection.
• "IP-addr"
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 IP networks. This address
must always be unambiguous in a 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. .
• "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 defi-
nition | 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 IEC 61850 protocol element.
In the IEC 61850 Client as of Edition 2, the following parameters can be set per connection:
• "Timeout IEC61850 connection setup"

Timeout for the cyclic connection reestablishment to the connected device (default 10 s).
• "Timeout IEC 61850 Services"

Timeout for IEC 61850 services, every service must be confirmed within this timeout. This timeout is
increased during command transmission to the Timeout ACT→CON (default 7 s).

DC8-037-2, Edition 11.2020
12.7 IEC 61850
• "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 (“unbuf-
fered, 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"
• "DynamicDatasets"
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 IEC 61850 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).
• "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).

DC8-037-2, Edition 11.2020
12.7 IEC 61850
• "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.
• "Filetransfer"
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"

• Test mode
Data which is provided with the quality bit “Test” can be passed on (unchanged with Test = 1, or with
Test = 0) or can be rejected.
• Static & dynamic datasets

With usage of static and dynamic datasets, at first static datasets are used for the reporting. Data which is
not existing in static datasets is combined in dynamic datasets.

The transmission of data ready to be sent from the master station (IEC 61850 Client) to the remote terminal
unit (IEC 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 (IEC 61850 Server) to the master
station (IEC 61850 Client) takes place either spontaneous by means of IEC 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 IEC 61850, for the transmission of data between servers the multicast transmission proce-
dure "GOOSE" (Generic Object Oriented Substation Events) is used.
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 parame-
ters, such as speed, duplex mode, and flow control. This procedure is only used for wired Ethernet (twisted
pair cable) – but not for WLAN-, fiber optic- or coaxial cables.

DC8-037-2, Edition 11.2020
12.7 IEC 61850
NOTE
i 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 IEC 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 IEC 61850 Client function, with the parameter IEC61850 |
Client | Timeout IEC61850 Services the monitoring time for IEC 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 IEC 61850 Edition 2: Connectiondefi-
nitionen | Timeout CON → TERM).
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 param-
eters 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 IEC 61850 Edition 2: Connection definitions | Connection estab-
lishment (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 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 re-reachable remote station.No
further data is sent to a failed remote station until successful station initialization.
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 IEC 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 after-
wards the connection is established for every single connection at TCP/IP level by the IEC 61850 Client.

DC8-037-2, Edition 11.2020
12.7 IEC 61850
For failed or unreachable remote stations, a connection setup (attempt) for the connection is performed cyclic
by the IEC 61850 Client.
After complete initialization of a connection, the protocol element with IEC 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 IEC 61850 Server function, the protocol element waits for an establishment of the
connection at TCP/IP level by the IEC 61850 Client.
12.7.6.4 Recording events (transferring data ready for sending)

Once the connection has been established the transmission from master station (client) to substation (server)
is carried out spontaneously. The transmission from the substation (server) to the master station (client) takes
place either spontaneously by means of reports or on the basis of requests by the master station.
The “GOOSE” transmission procedure can be used to transfer data between servers.
Server ↔ Client Data Transmission

The transmission of data ready to be sent from the master station (IEC 61850 client) to the substation
(IEC 61850 server) takes place spontaneously once the connection has been established and for each connec-
tion.
The transmission of data ready to be sent from the substation (IEC 61850 server) to the master station
(IEC 61850 client) takes place either spontaneously by means of IEC 61850 reports or on request by the
master station.
The IEC61850 | Client | Advanced parameters | IEC61850 service for query parameter
specifies whether the transmission of the data from the substation (IEC 61850 server) to the master station
(IEC 61850 client) is carried out spontaneously using reports or by cyclical queries by the master station.
In the event of spontaneous transmission using reports the protocol element with IEC 61850 client function in
the report control block of the IEC 61850 server activates spontaneous transmission.
In the event of data transmission by cyclical queries the protocol element with IEC 61850 client function selec-
tively queries the data attributes (report control block, reports and data sets are not used in this case).
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-block during 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 to the
protocol element with IEC 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 to the
protocol element with IEC 61850 client function.
Reports/Report Control Block

The spontaneous transmission of data from the IEC 61850 server to the IEC 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 properties of the respective report have been entered in the report control block. The IEC 61850
client can read and write to the report control block.
The following information is stored in the report control block (summarized):
• Reference to the associated data set
• Trigger for the transmission (spontaneous, general interrogation, etc.)
• Data set name
• …

DC8-037-2, Edition 11.2020
12.7 IEC 61850
Unbuffered/Buffered Reports
A distinction is made between buffered reports and unbuffered reports. This function is determined by the
IEC 61850 device. For buffered reports, changes are stored after a connection failure.
After system startup or after an outgoing connection failure all available unbuffered/buffered control blocks
are requested and their associated data sets are read (“DatSet” attribute). Predominantly, the Unbuffered
Control Block is used, only if no Unbuffered Control Blocks are present, Buffered Control Blocks are used.
The SICAM RTUs protocol element with IEC 61850 client function does not distinguish between buffered and
unbuffered reports when handing reports during reception.
As of IEC 61850 Edition 2 the selection of reports can be defined with the Connection definitions |
Reports parameter. With “unbuffered, buffered” and “buffered, unbuffered” both are used with priority to
the first selection. Merely configured reports are used with "unbuffered", "buffered", and “individual requests".
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 IEC 61850 Edition 2 the IEC61850 | Client | Advanced parameters | Report definition
table can revoke the automatic search for reports.
Parameter Description
Station 0 to 99 (internal SICAM station)
Report name Name of the report (for example, IEDPROT/LLN0$RP$urcb01
NOTE
i The SICAM RTUs protocol element with IEC 61850 Server function only supports “Unbuffered Reports”.
Static/Dynamic Data Sets

Data sets feature all information that can be spontaneously transferred from the IEC 61850 server to the IEC
61850 client. Required values that are not included in the data sets must be read out by the IEC 61850 client
using cyclical attribute queries.
Static datasets are predefined by the IEC 61850 device and are created in the device by the IEC 61850 server
function itself.
In SICAM RTUs devices, the static data sets are generated by the protocol element with IEC 61850 server func-
tion from the data of the SIP telegram address conversion in transmit direction.
Dynamic datasets must be created by the IEC 61850 client in the IEC 61850 server. In the initialization phase,
the protocol element with IEC 61850 client function reads out the information from those devices with
IEC 61850 server function, to establish whether dynamic data sets are supported. Dynamic data sets are
generated by the protocol element with IEC 61850 server function from the data of the SIP telegram address
conversion in receive direction and created in the devices with IEC 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 IEC 61850 Edition 2, the Connection definitions | Dynamic datasets parameter defines
whether the IEC 61850 server supports dynamic data sets. This parameter can be used to adjust whether or
not dynamic data sets can be created by the IEC 61850 client. This parameter is created upon the SCD import
by the SICAM TOOLBOX II, depending on whether or not the device supports dynamic data sets.
The number of elements for dynamic data sets is specified with the Connection definitions |
Elements per data set parameter (typically: 60).
The dataSet dynamic and Dynamic data sets parameters must be set to YES to be able to use
dynamic data sets and additionally the device must report upon establishing the connection that it supports
dynamic data sets.
When using the SICAM TOOLBOX II SCD import, these parameters are set automatically. For instance, a typical
use case is the import of a SIPROTEC5 device (which supports dynamic data sets), whereby both parameters

DC8-037-2, Edition 11.2020
12.7 IEC 61850
are set to YES. If, instead of dynamic datasets, predefined ones are to be used in the Sysconf, the parameter
dynamic datasets must be set to NO.
The report attributes (dynamic dataSet, dynamic cbName, dynamic rpId, etc.) are automatically taken
out of the SCD file for the SICAM TOOLBOX II import and reflect the options offered by the device as to
whether the relevant report attributes are dynamic (that is,. can be changed by the client).
NOTE
i Siemens protection devices from the SIPROTEC series only support dynamic datasets. Protection devices of
other manufacturers mostly support static datasets only.
Setting Group Control Model

Setting groups are supported only for Logical Device “Protection” and Logical Node “LLN0”.
Values from a SGCB are not transmitted spontaneously, but interrogated cyclically.
NOTE
i Only a group changeover can be carried out (SelectActiveSG), no parameter settings.
Data Transmission Server ↔« Server with "GOOSE" [Server only]

Das Generic Object Oriented Substation Events (GOOSE) is a IEC 61850 transmission service for generic status
events that are transmitted to several devices simultaneously using Multicast to be able to meet stringent real-
time requirements. Typical use cases are spontaneous transmission of the switching device status in the
decentral interlocking system for switching commands in substations. GOOSE telegrams use the Ethertype
specification for VLAN, the prioritization and are represented on the Ethernet layer itself.
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.
The IEC 61850 protocol element only supports basic types for GOOSE data transmission (single elements) -
data structures are only supported for the following CDCs in Edition 2 (FC=ST): SPC, DPC, ENC, INC, SPS, DPS,
ENS, INS.
The GOOSE data transmission is supported by the server function of the protocol element in transmit direction
“Publisher” (transmitter) as well as in receive direction “Subscriber” (receiver).
The datasets to be transmitted are defined with the process parameterization of the SIP message address
conversion. The datasets must consist of data from the MMS directories.
The internal station number (from SSE to BSE) of the received GOOSE messages is 254 (own SSE). This means
that publish messages must be included in the transmit routing and subscribe message in the receive routing.
GOOSE messages are transmitted with high priority by the switches implemented in IEC 61850 networks. The
switches must support the IEEE802.1Q standard for this purpose (prioritizing telegrams).
GOOSE Transmission Scheme
The GOOSE data transmission is a cyclical multicast transmission. A GOOSE message is thereby transmitted
from one device as the “Publisher” (transmitter) and received by multiple devices that are the “Subscribers”
(receivers).
In the case of GOOSE data transmission, the GOOSE message is transmitted immediately and spontaneously
when there is a change, and then transferred in a cyclical fashion with a changed cycle time (retry time). Data
transmission is not acknowledged, reception of the current status is ensured through the retry 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.

DC8-037-2, Edition 11.2020
12.7 IEC 61850
The maximum repeat time for GOOSE messages is to be parameterized with the parameter IEC61850 |
Server | Goose | Max. repeat time for GOOSE messages .
Failure monitoring
Failure monitoring for GOOSE messages in receive direction (subscriber) is derived from the current HOLD
time (retry time) for each GOOSE application. The current HOLD time is transmitted in each telegram for a
GOOSE message.
The time for 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 in the event of GOOSE
failure.
NOTE
i If the emulation of the data in question is deactivated on failure, monitoring by the user function must be
ensured.
Parameters for GOOSE data

The GOOSE data is exclusively parameterized using the SICAM TOOLBOX II GOOSE configurator. Only existing
projects using GOOSE data should be parameterized using a technical process parameterization for the
protocol element.
Data for the technical process parameterization (SIP telegram address conversion in transmit/receive direction)
can be selected for GOOSE data transmission. All data with the same “GOOSE index” is assigned to a GOOSE
application.
The detail parameters for each GOOSE application (GOOSE index) must be parameterized in the technical
system parameters in the spreadsheet IEC61850 | Server | Goose | Goose definition
All data for a GOOSE application is transmitted with the parameterized multicast address.
The following parameters can be set in the goose definitions:
• “Release”
A parameterized GOOSE application can be activated/deactivated with the parameter IEC61850 |
Server | Goose | Goose definition | Enable for example, this way GOOSE applications can
be prepared, that are first activated at a later time by means of parameterization.

DC8-037-2, Edition 11.2020
12.7 IEC 61850
• “Goose Index”
The data for the SIP message address conversion are assigned to the GOOSE application with the GOOSE
index.
The GOOSE Index is only used SICAM RTUs internal and is parameterized for each GOOSE application with
the parameter IEC61850 | Server | Goose | Goose definition | Goose Index .
• “Goose Control Block (gocbref)”

With the parameter IEC61850 | Server | Goose | Goose definition | 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
goose definition parameters, and can be read by the client.
The GOOSE control block can be read in the server directory with the integrated Web server under the
functional constraint “GO”.
• “GOOSE Id (goid)”
An unambiguous GOOSE identification is parameterized with the parameter IEC61850 | Server |
Goose | Goose definition | Goose Id (goid) 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. The reference to the
dataset can be parameterized using the parameter IEC61850 | Server | Goose | Goose defi-
nition | Dataset reference for each GOOSE application.
• “MAC Address”
Every GOOSE application is transmitted with Multicast to multiple devices as a GOOSE message. With the
parameter IEC61850 | Server | Goose | Goose definition | MAC Address the multicast
address (=MAC-address) is to be parameterized for each GOOSE application.
The MAC address is to be parameterized as a character string without a separating character.
Example: The multicast address 01-0C-CD-01-01-FF must be parameterized with the character sequence
010CCD0101FF.
• “AppId”
The application identification (AppId) for the GOOSE application is to be parameterized using the param-
eter IEC61850 | Server | Goose | Goose definition | AppId.
• “configRev”
An unambiguous revision identifier for the GOOSE application is to be parameterized using the parameter
IEC61850 | Server | Goose | Goose definition | configRev.
This revision identifier should be changed when the dataset of the GOOSE application changes, so that
no malfunction occurs in connected devices with an incompatible parameter setting.
Note: The revision identifier check can be switched on and off with a system parameter.
• “VLAN Vid”
The VLAN-ID (unambiguous number of the virtual LANs) is to be parameterized using the parameter
IEC61850 | Server | Goose | Goose definition | VLAN Vid
For details on VLAN, see 12.20 VLAN.
• “VLAN priority”
With the parameter IEC61850 | Server | Goose | Goose definition | VLAN priority
the priority for the data packets in the VLAN is to be parameterized.
For details on VLAN, see 12.20 VLAN.
General Notes on GOOSE
Attribute They are unambiguous for each

Electrical power Device
system
GoCBRef ✓ ✓

DC8-037-2, Edition 11.2020
12.7 IEC 61850
Attribute They are unambiguous for each

GoId ✓ ✓
Dataset ✓
MAC Address ✓
AppId ✓
configRev
VLAN Vid
VLAN Priority
The GoCBRef and GoId combination must be unambiguous in the network.

The Logical Nodes of the Goose receiver should be of the type GGIO:
GOOSE Publish:
VLC01/Q0CSWI1.Pos.stVal
VLC01/Q0CSWI1.Pos.q
GOOSE Subscribe:
VLC02/Q0GGIO1.DPCSO1.stVal
VLC02/Q0GGIO1.DPCSO1.q
Q0CSWI.Pos.stVal und Q0GGIO1.DPCSO1.stVal are both of the double-point indication type.
A new data point is created (VLC02) on the receiver (subscribe). The quality should always be transmitted as
well.
Example of a valid GOOSE parameterization:
GoCBReg Go Dataset MAC AppId config VLAN VLAN
Id Rev Vid Priority
VLC01/LLN0$GO$gcb01 1 VLC01/LLN0$ds1 010CCD010000 1 1 1 4
VLC01/LLN0$GO$gcb02 2 VLC01/LLN0$ds2 010CCD010001 2 1 1 4
By means of this parameterization, in the VLC01/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. The created dataset can also not be
read.
The attributes of the GGIOs must be assigned according to the following table:
Basic type Used as GGIO Attribute
BOOLEAN Single-point indication SPCSO.stVal
CODED ENUM Double-point information DPCSO.stVal
FLOAT32 Measurand AnIn.mag.f
Quality Quality 177
TimeStamp Real time 178
initialization of the connection or after the master station has detected a loss of information.
function on the basic system element (BSE) station-selective (per 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.
177 additional attribute to single-point indication, double-point indication, measured value

178 additional attribute to single-point indication, double-point indication, measured value

DC8-037-2, Edition 11.2020
12.7 IEC 61850
Handling of the General Interrogation in the IEC 61850 Client

A general interrogation is only sent to the server by the protocol element with IEC 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 IEC 61850 Server
The protocol element with IEC 61850 Server function does not perform any general interrogation towards the
basic system element. A general interrogation triggered by the IEC 61850 Client is replied to by the protocol
element with IEC 61850 Server function directly from the internal process image of the protocol element by
means of "Unbuffered Reports".
12.7.6.6 Clock synchronization
In networks and in systems with time-critical tasks 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 1/1/2001
Reference date for Ax1703: 1.1.1997 1/1/1997
In both cases, the time tag is marked as invalid until the first reception of the synchronizing event.
Network Time Protocol (NTP)

For further details refer to chapter 12, NTP.

For the transmission of commands, the Common Data Classes expanded in the IEC 6185081 standard are
used. These expanded Common Data Classes consist of several attributes that are all transmitted in one
IEC 61850 message.
The protocol element with IEC 61850 Client function describes the attribute “Check” as last attribute during
the preparation of the command. The protocol element with IEC 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 IEC 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 TimeAc- Note
tivatedOperate 179
Direct with normal security Oper Only EXECUTE-command
Direct with enhanced security Only EXECUTE-command
Oper
179 "Data Attributes with Time Activated Operate" are not supported by the protocol element!

DC8-037-2, Edition 11.2020
12.7 IEC 61850
IEC 61850 Control Model Data Attributes without TimeAc- Note

tivatedOperate 179
Select Before Operate with normal Select Before Operate (SBO) Oper Only SELECT/EXECUTE-commands
security 180 Cancel
Select before operate with Select Before Operate (SBOw) Only SELECT/EXECUTE-commands
enhanced security Oper
Cancel
The “Control Model” (ctlmodel) is determined by the IEC 61850 Server and read out by the IEC 61850 Client in
the startup phase.
With the control models “Direct with enhanced security” and “Select before operate 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 181
The SICAM RTUs protocol element for IEC 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 IEC 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.
A command is sent with the following attributes and sequence:
IEC 61850 Attribut Description
ctlVal Command State
origin.orCat see Causes of Transmission
origin.orIdent
ctlNum Ascending number
T current time
Test depending on Test-Bit IEC 60870-5-101/104
Check Refer to the following table
Control Model
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
179 "Data Attributes with Time Activated Operate" are not supported by the protocol element!
180 is not supported by the SICAM RTUs protocol element!
181 is not supported by the SICAM RTUs protocol element!

DC8-037-2, Edition 11.2020
12.7 IEC 61850
All commands with short, long and without definition are sent with “interlocking”. Commands that are gener-
ated 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
Server
IEC 61850 Check IEC 60870-5-101/104 QU Meaning

00 9
01 0 interlocking 182
10 10 synchrocheck
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
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
182 this is the typical command; the meaning of QU = 0 corresponds "without additional definition"

DC8-037-2, Edition 11.2020
12.7 IEC 61850
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).
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 and return information is created via the IEC 61850 address
(detailed routing).
State Behaviour
Command running (no timeout) and return informa- Copying of ctlNum, origin.orCat,
tion has the cause 11 (remote) origin.orIdent
Return information has not the cause 11 (remote) origin.orCat = process
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 IEC 61850 protocol element (see IEC 61850: Common Data Attribute
Types, Page 964, IEC 61850: Originator).
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.
In the SICAM RTUs protocol element with IEC 61850 Client function, with the parameter IEC61850 |
Client | Advanced parameters | Terminations for commands (as of IEC 61850 Edition 2:
Connection definitions | Termination) it can be selected whether the “Termination of Activation” is
to be derived from the “Command Termination” of IEC 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 IEC 61850 address from the parameters of the SIP message address
conversion (ctlVal, stVal).
In the SICAM RTUs protocol element with IEC 61850 Client function, with the parameter IEC61850 Client
| Timeout IEC61850 Services the monitoring time for IEC 61850 Services (e.g.: Read/Write) can be set
(e.g.: Connection definition | Timeout IEC61850 Services). For commands, this monitoring
time is extended to the time that can be set with the parameter IEC61850 | Timeout Confirmation →
Termination (as of IEC 61850 Edition 2: Connection definition | 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”.
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 IEC 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 IEC 61850 Server function with the parameter
IEC61850 | Server | 1 of n control .
Converting EXECUTE (104) → SELECT/EXECUTE (61850) [Client only]

DC8-037-2, Edition 11.2020
12.7 IEC 61850
The protocol element with IEC 61850 Client function can convert IEC 60870-5-101/104 commands with
“direct command transmission” (EXECUTE only) for the transmission to the IEC 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 IEC 61850 Edition 2: Connection definition | Convert
commands EXE to SEL/EXE).
With function activated the SELECT-command is transmitted immediately to the remote station. After recep-
tion 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 IEC 61850 Edition 2: Connection definition | Delay
SEL/EXE (ms) ).
NOTE
i 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/104 Direction IEC 61850 ASCI Service

1 Execute Activation → Select
1 ← 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).
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 183
Error ENUMERATED • No Error

• Unknown
• Timeout Test Not OK
• Operator Test Not OK
Origin Originator
183 MMS name of the Control Object (e.g.: VLC01/XCBR1$Mod$Oper)

DC8-037-2, Edition 11.2020
12.7 IEC 61850
Attribute Name Type Values

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
Monitoring
Client
The protocol element with IEC 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 608705101/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 IEC 61850 remote station [Server] and the CONFIRMATION received from
the IEC 61850 remote station.
The monitoring time can be set with the parameter IEC61850 | Timeout Activation → Confir-
mation (as of IEC 61850 Edition 2: Connection definition | Timeout ACT -> CON (s)).
basic system element by the protocol element.

DC8-037-2, Edition 11.2020
12.7 IEC 61850
• Timeout CONFIRMATION – TERMINATION

For commands, the protocol element with IEC 61850 Client function monitors the time between the
CONFIRMATION received from the IEC 61850 remote station [Server] for the transmitted command and
the TERMINATION received from the 61850 remote station.
The monitoring time can be set with the parameter IEC61850 | Timeout Confirmation →
Termination (as of IEC 61850 Edition 2: Connection definition | Timeout CON → TERM).
If the monitoring time expires, a “negative termination of activation” (ACTTERM-) is transmitted to the
basic system element by the protocol element.
Server
The protocol element with IEC 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 “nega-
tive confirmation of activation” (ACTCON-) is transmitted to the IEC 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 basic system element.
The monitoring time can be set with the parameter IEC61850 | Timeout Activation →
Execute .
IEC 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 IEC
61850 Client by the protocol element.
Direct Control with Normal Security
Client
Step IEC 60870-5-101 Direction IEC 61850 ASCI Service

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

DC8-037-2, Edition 11.2020
12.7 IEC 61850
If all checks are successful, the command is sent and a timeout for the Confirmation is started.
Evaluation for the Confirmation:
Check Behaviour
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 Behaviour
belonging “stVal” changes Termination pos. (COT = 10, PN = 0)
Timeout Termination neg. (COT = 10, PN = 1)
Server
Step IEC 61850 ASCI Service Direction IEC 60870-5-101/104

1 Operate Req → Command Execute, COT = 6
2 Operate Res ± ←

Check Behaviour
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.
Direct Control with Enhanced Security

3 Command Execute, COT = 10, PN = 0,1 ← Command Termination
Client
Check Behaviour
“ctlModel” unequal 1,3 Confirmation neg. (COT = 7, PN = 1)

DC8-037-2, Edition 11.2020
12.7 IEC 61850
Check Behaviour

Check Behaviour
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 gener-
ated by the command return information and not by the Command Termination.
Server

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 Behaviour
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-
The “Access Result” with Operate Res- is always “Object-access-denied”.

If all checks are successful, the command is forwarded (COT = 6).
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.

DC8-037-2, Edition 11.2020
12.7 IEC 61850
Check Behaviour
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 Command Termination± is created by the Termination (COT = 10):
Check Behaviour
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.
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 Behaviour
"ctlModel" unequal 4 Confirmation neg. (COT = 7, PN = 1)
Check Behaviour
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 Behaviour
Execute command has unequal address as the Select Confirmation neg. (COT = 7, PN = 1)
command
Timeout Enable command in the memory

DC8-037-2, Edition 11.2020
12.7 IEC 61850
Check Behaviour

Check Behaviour
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 gener-
ated by the command return information and not by the Command Termination.
Termination of the Command (Deactivation COT = 8)
Check Behaviour
Command is not running Deactivate Confirmation neg. (COT = 9, PN = 1)
Server
Only one SBO with value (SBOw) is supported.
Step IEC 61850 ASCI Service Direction IEC 60870-5-101/104
1 Select with Value Req → Command Select, COT = 6
2 Select with Value Res ± ← Command Select, COT = 7, PN = 0,1
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 Behaviour
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).

DC8-037-2, Edition 11.2020
12.7 IEC 61850
Check Behaviour
AddCause = Select Failed
Operate Res-
Operate Res-

The following steps are performed, if the written attribute is "Oper":
Check Behaviour
Operate Res-
Command is 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).
Check Behaviour
Operate Res-
Operate Res-
The “Object-access-denied” with Operate Res- is always “Oject-access-denied”.

The Command Termination± is created by the Termination (COT = 10):

DC8-037-2, Edition 11.2020
12.7 IEC 61850
Check Behaviour
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.
The following steps are performed, if the written attribute is “Cancel”:
Check Behaviour
Operate Res-
Command is 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).
Check Behaviour
Operate Res-
Operate Res-
Confirmation pos. (COT = 7, PN = 0) Operate Res +
Control Location [Client only]

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 242: set control
location). 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 acti-
vation (ACTCON-) is sent back immediately by the protocol element to the originator address.
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.

DC8-037-2, Edition 11.2020
12.7 IEC 61850
If the originator address in the spontaneous information object “Command” does not match the control loca-
tion previously set or if no control location has been preset:
• the command is rejected
• a negative confirmation of the activation is transmitted (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.
Set control location

The control location is set on the PRE with a PRE-control message (Function = Set control location) either glob-
ally 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 + SICAM A8000 | 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 Not defined
1 ... 127 Remote command
128 ... 255 local command
NOTE
i 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", 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 indi-
vidually or globally for all stations and all control locations.
No confirmation (ACTCON) and no termination (ACTTERM) of the command initiation is created for the infor-
mation object “Control location”.
With each startup of the protocol element, all enabled control locations are reset. The control locations are to
be set again after every startup of the protocol element.
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.
12.7.6.9 File Transfer (Disturbance Records)
In IEC 61850 protection equipment [Server] disturbance records are recorded and stored in the protection
equipment as files in IEEE-Comtrade format.

DC8-037-2, Edition 11.2020
12.7 IEC 61850
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 IEC 61850 Edition 2: Parameter Connection definition | File transfer).
NOTE
i 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 (distur-
bance 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 sepa-
rate ZIP-file)
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
Transfer of Disturbance Records to SICAM DISTO

With the IEC 61850 protocol element [Client] disturbance records can be read out from IEC 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 proce-
dure 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 "distur-
bance record container" is carried out in the OPM II in the master station in the process-technical parameteri-
zation in transmit direction (to SICAM DISTO) with the category firmware/ ET03/
Fault_record_Trans_IEC61850 and in receive direction (from SICAM_DISTO) with the category firm-
ware/ ET03/Fault_record_Trans_IEC61850.

DC8-037-2, Edition 11.2020
12.7 IEC 61850
NOTE
i Redundant configurations with SICAM DISTO are not supported!
[dw_61850_disto_configuration, 1, en_US]
Figure 12-3 Configurations with SICAM DISTO
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 spon-
taneously 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.

DC8-037-2, Edition 11.2020
12.7 IEC 61850
[dw_ET03_Ablauf_zu_DISTO, 1, en_US]
Transmission of Disturbance Records [SICAM RTUs = Server]
NOTE
i The protocol element for IEC 61850 [Server] does not presently support any transfer of disturbance records
according to IEC 61850!
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 communica-
tion routes.
The following redundancy modes are supported:

DC8-037-2, Edition 11.2020
12.7 IEC 61850
• SICAM RTUs 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 real-
ized.
12.7.7.1 SICAM RTUs Redundancy
With the redundancy mode “SICAM RTUs Redundancy”, one remote terminal unit is connected with one or
several master stations over several logical connections. The data transmission takes place over all connec-
tions.
The switchover of the redundancy state ("ACTIVE" ⇔ "PASSIVE") takes place system-internal through redun-
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
NOTE
i Redundant configurations with SICAM DISTO are not supported!
12.7.7.2 Server Redundancy
Special functions are implemented in the protocol element for the support of redundant configurations of
SICAM RTUs devices with IEC 61850 Server function.
So that a fast switchover between the servers can be performed during redundancy switchover from "PASSIVE
→ ACTIVE", the connection to both IEC 61850 Servers must be established and the IEC 61850 communication
must be completely initialized.
The IEC 61850 Client has no information about which IEC 61850 Server is "ACTIVE". The transmission of spon-
taneous data (Reports) is only carried out by the "ACTIVE" IEC 61850 Server.
After initialization is complete, the spontaneous transmission of data (Reports) is deactivated by the protocol
element of the "PASSIVE" IEC 61850 Server.
The switchover of the redundancy state ("ACTIVE" ↔ "PASSIVE") takes place system-internal through redun-
Functions in the redundancy state "PASSIVE":

DC8-037-2, Edition 11.2020
12.7 IEC 61850
• 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 IEC
61850 Server function with the parameter IEC61850 | Server | Redundancy for Server .
12.7.7.3 GOOSE Redundancy
For the support of redundant configurations of SICAM RTUs components with IEC 61850 Server function,
special functions are implemented in the protocol element for the GOOSE message transfer during transmis-
sion (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.
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) .
The switchover of the redundancy state takes place system-internal by means of redundancy control
messages.
Functions during the switchover from the redundancy state "ACTIVE" → "PASSIVE":

DC8-037-2, Edition 11.2020
12.7 IEC 61850
• 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.

The passive server subscribes to the own GOOSE messages, thereby the Publish messages of the active server
are listened, and the state and sequence number of the active server for each GOOSE application is taken over.
This is necessary for the switchover in order that the server newly becoming active is able to use the correct
state and sequence number, and thereby the Subscribers will not detect a failure or error.
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
i IEC 61850 Ed.1: 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!
IEC 61850 Ed.1: The "State Number" in the GOOSE message (change counter) is synchronized between the
redundant devices. This enables a faultless switching over without detection of additional changed data.

DC8-037-2, Edition 11.2020
12.7 IEC 61850
12.7.8.1 General
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 from the protocol element according to the transmission procedure
according to IEC 61850 converted by the protocol element to the internal IEC 60870-5-101/104 format and
then transferred 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 IEC 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 IEC 61850 Server Function

firmware/ ET03/Server_Trans_IEC61850
firmware/ ET03/Server_Rec_IEC61850
firmware/ ET03/Server_Trans_Goose_IEC61850 184
firmware/ ET03/Server_Rec_Goose_IEC61850 184
firmware/ ET03/Server_Trans_default_value_IEC61850 184
Protocol Element with IEC 61850 Client Function

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
NOTE
i A general interrogation is always replied to by the protocol element from the internal process image of the
protocol element with the actual time.
184 only Edition 1

DC8-037-2, Edition 11.2020
12.7 IEC 61850
Protocol Element with IEC 61850 Server Function

When data change, with IEC 61850 all attributes of the same "Functional Constraint" group are always trans-
mitted. 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.
12.7.8.2 Conversion IEC 60870-5-101/104 ↔ IEC 61850
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
INT128 -2127 bis +2127 - 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
IEC 61850: Common ACSI Types
IEC 61850: Time Quality
IEC 61850 IEC 60870-5-101/104 supported

Attribute Name Type Values Ed.1 Ed.2
LeapSecondsKnown BOOLEAN 185
ClockFailure BOOLEAN CP56Time2a IV ✓ ✓

ClockNot Synchronized BOOLEAN CP56Time2a IV ✓ ✓ 186
TimeAccuracy CODED ENUM significant bits in Frac- 1 ms resolution ✓ ✓
tionOfSeconds matches approx. 10
bits
Edition 2: applies only for Client
IEC 61850: Time Stamp

SecondsSinceEpoch INT32 Seconds since CP56Time2a ✓ ✓
01.01.1970 00:00
185 applies only for Server

186 applies only in receive direction

DC8-037-2, Edition 11.2020
12.7 IEC 61850

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.
IEC 61850: Common Data Attribute Types
IEC 61850: Quality

validity CODED ENUM good NT = 0 ✓ ✓
invalid NT = 1
reserved IV
questionable
detailQual PACKED LIST
overflow BOOLEAN OV 187 188 ✓ ✓
outOfRange BOOLEAN 189 ✓ ✓
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 ✓ ✓
IEC 61850: AnalogueValue

i INT32 ✓
f FLOAT32 ✓ ✓
IEC 61850: Vector

mag AnalogueValue ✓ ✓
ang AnalogueValue ✓
187 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)
188 applies only for Server: with OV = 1 validity is set to invalid additionally
189 applies only for Client: all these bits are ORed to the IV bit

DC8-037-2, Edition 11.2020
12.7 IEC 61850
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 ✓ 190 ✓ 190
D 191
Description of the originator: refer to Control Model, Page 943, Causes of Transmission (origin).
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:
VLC01/XCBR1.Pos.ctlVal (command)
VLC01/XCBR1.Pos.stVal (return information)
All Activation, Confirmation, Termination messages are indirectly via a change of the orIdent attribute sponta-
neous 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 TI45, 46: "0" = OFF, "1" = ON / TI47: "0" = LOWER "1" = HIGHER / TI49, 50: decimal value (-12, 12.3,
1.2E-2)
zzz = Origin address of the command
NOTE
i 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:
190 applies only for Client: all these bits are ORed to the IV bit

DC8-037-2, Edition 11.2020
12.7 IEC 61850
IEC 61850: Step position with transient indication

posVal INT8 -64…+63 VTI ✓ ✓
transInd BOOLEAN VTI ✓ ✓ 192
IEC 61850: 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.
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 the basic system element
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.
192 for transInd a single-point information (TI 30) can be generated in the Client

DC8-037-2, Edition 11.2020
12.7 IEC 61850
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.
Overview of the Supported Formats
IEC 61850 Common FC IEC 60870-5-101/104 193 Cs Se Ce Ss SsG SrG

Data Class [CDC]
SPC Controllable CO <TI=30> Single-point information ✓ ✓
Single Point <TI=31> Double-point information
<TI=45> Single command ✓ ✓
ST <TI=30> Single-point information ✓ ✓ ✓ ✓
<TI=31> Double-point information
DPC Controllable CO <TI=30> Single-point information ✓ ✓
Double Point <TI=31> Double-point information
INC Controllable CO <TI=30> Single-point information ✓
Integer <TI=31> Double-point information
Status <TI=45> Single command ✓ ✓
<TI=49> Setpoint command, scaled 194 ✓ ✓
<TI=50> setpoint command, floating
point 194
<TI=31> Double-point information 195
<TI=35> measured value, scaled 194 ✓ ✓ ✓ ✓

195
<TI=36> measured value, floating point
194
ENC Controllable CO <TI=30> Single-point information ✓

Enumerated <TI=31> Double-point information 195
Status <TI=45> Single command ✓ ✓

195 195
195 195
point 194
ST <TI=30> Single-point information ✓ ✓ ✓
195 195 195
<TI=35> measured value, scaled 194 ✓ ✓ ✓
195 195 195
194
193 all with time mark CP56Time2a; only TI 30 and TI 31 are GI capable
194 for this values a measured value adaption (scaling) is not supported
195 applies only for Edition 2

DC8-037-2, Edition 11.2020
12.7 IEC 61850

Data Class [CDC]
APC Controllable CO <TI=49> Setpoint command, scaled 194 ✓ ✓
Enumerated <TI=50> setpoint command, floating
195 195
Status point 194

ST <TI=35> measured value, scaled 194 ✓ ✓
195 195
194
SPS Single-Point ST <TI=30> Single-point information ✓ ✓ ✓ ✓

Status
DPS Double-Point ST <TI=31> Double-point information ✓ ✓ ✓ ✓
status
INS Integer ST <TI=30> Single-point information ✓ ✓ ✓ ✓
Status <TI=31> Double-point information 195

195
194
ENS Enumerated ST <TI=30> Single-point information ✓ ✓ ✓ ✓

Status <TI=31> Double-point information 195 195 195 195

195 195 195 195
194
ACT Protection ST <TI=30> Single-point information ✓ ✓ ✓ ✓

Activation <TI=38> Event of protection equipment ✓ ✓ ✓ ✓
Information <TI=39> Blocked activation of the protec-
<TI=40> tion
Blocked triggering of the protec-
tion
ACD Directional ST <TI=30> Single-point information ✓ ✓ ✓ ✓
Protection <TI=31> Double-point information ✓
Activation
<TI=38> Event of protection equipment ✓ ✓ ✓ ✓
Information
<TI=39> Blocked activation of the protec-
<TI=40> tion
Blocked triggering of the protec-
tion
SGCB Setting SP <TI=30> Single-point information ✓ ✓ ✓
Group <TI=31> Double-point information
Control Block <TI=35> Measured value, scaled value 194 ✓ ✓
194

point 194
BCR Binary ST <TI=37> Integrated totals ✓ ✓
Counter
Reading

DC8-037-2, Edition 11.2020
12.7 IEC 61850

Data Class [CDC]
BSC Binary ST <TI=30> Single-point information ✓ ✓
Controlled <TI=32> Step position information 194
Step Position
CO <TI=47> Regulating step command ✓ ✓
ISC Integer ST <TI=30> Single-point information ✓ ✓
Controlled <TI=32> Step position information 194
Step Position
CO <TI=49> Setpoint command, scaled 194 ✓ ✓
point 194
ASG Analogue SP <TI=35> measured value, scaled ✓ ✓
Setting <TI=36> measured value, floating point 195

195
point 194
ING Integer SP <TI=35> measured value, scaled ✓ ✓
Setting <TI=36> measured value, floating point 195

195
point 194
MV Measured MX <TI=34> measured value, normalized ✓ ✓ ✓ ✓
Value <TI=35> measured value, scaled
<TI=36> Measured value Floatingpoint
CMV Complex MX <TI=34> measured value, normalized ✓ ✓ ✓ ✓
Measured <TI=35> measured value, scaled
Value <TI=36> measured value, floating point
SAV Sampled MX <TI=34> measured value, normalized ✓ ✓ ✓ ✓
Value <TI=35> measured value, scaled
WYE Collection Of MX <TI=34> measured value, normalized ✓ ✓ ✓ ✓
Measurands <TI=35> measured value, scaled
DEL Delta MX <TI=34> measured value, normalized ✓ ✓ ✓ ✓
<TI=35> measured value, scaled
SEQ Sequence MX <TI=34> measured value, normalized ✓ ✓ ✓ ✓
<TI=35> measured value, scaled
DPL Device Name only used on the protocol firmware ✓
Plate
LPL Logical Node only used on the protocol firmware ✓
Name Plate
SPG Single Point SP <TI=30> Single-point information ✓ ✓
Setting <TI=45> Single command ✓ ✓
Legend:
FC Functional Constraint
Cs Client in Transmit Direction

DC8-037-2, Edition 11.2020
12.7 IEC 61850
Se Server in Receive Direction

Ce Client in Receive Direction
Ss Server in Transmit Direction
SsG GOOSE Server transmit direction
SrG GOOSE Server receive direction
NOTE
i As shown in the following tables, edition 2 applies only for the IEC 61850 Client.
IEC 61850: Controllable Single Point (SPC)
IEC 61850 IEC supported Rout

60870-5-101/104
Attribute Name Type FC Values Ed.1 Ed.2
ctlVal BOOLEAN CO TI 30: SPI 196 ✓ ✓ TI 30
TI 31: DPI 196 TI 31
TI 45: SCS 196 TI 45
TI 46: DCS 196 TI 46
operTim TimeStamp CO
origin Originator CO see Control Model, ✓ ✓
ST Page 943, Cause of
transmission (origin)
ctlNum INT8U CO ✓ ✓
ST
stVal BOOLEAN ST TI 30: SPI 197 198 ✓ ✓ TI 30
TI 31: DPI 197 198 TI 31
q Quality ST TI 30: SIQ 197 198 ✓ ✓
TI 31: DIQ 197 198
t TimeStamp ST CP56Time2a 197 198 ✓ ✓
stSeld BOOLEAN ST TI 30: SPI 197 ✓ TI 30
subEna BOOLEAN SV
subVal BOOLEAN SV
subQ Quality SV
subID STRING64 SV
pulseConfig PulseConfig CF
ctlModel ENUMERATED CF status-only 199 settable in the ✓
200
direct-with-normal- detailed routing
security
direct-with-
enhanced-sec.
sbo-with-enhanced-
sec.
sboTimeout INT32U CF
196 applies only for Client in transmit direction and Server in receive direction
197 applies only for Client in receive direction and Server in transmit direction
198 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
199 Server in transmit direction: status only is only then set, if no CO is present

DC8-037-2, Edition 11.2020
12.7 IEC 61850

60870-5-101/104
sboClass STRING256 CF
d STRING256 DC
dU USTRING256 DC
cdcNs STRING256 EX
cdcName STRING256 EX
dataNs STRING256 EX
IEC 61850: Controllable Double Point (DPC)

60870-5-101/104
ctlVal BOOLEAN CO TI 30: SPI 196 ✓ ✓ TI 30
TI 31: DPI 196 TI 31
TI 45: SCS 196 TI 45
TI 46: DCS 196 TI 46
ST
stVal CODED ENUM ST TI 30: SPI 197 201 202 ✓ ✓ TI 30
TI 31: DPI 2) 3) TI 31
q Quality ST TI 30: SIQ 197 201 ✓ ✓
TI 31: DIQ 197 201
t TimeStamp ST CP56Time2a 197 201 ✓ ✓
subEna BOOLEAN SV
subVal BOOLEAN SV
subQ Quality SV
subID STRING64 SV
204
security
direct-with-
enhanced-sec.
sbo-with-enhanced-
sec.
d STRING256 DC
201 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
202 with the 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

DC8-037-2, Edition 11.2020
12.7 IEC 61850

60870-5-101/104
dU USTRING256 DC
cdcNs STRING256 EX
dataNs STRING256 EX
IEC 61850: Controllable Integer Status (INC)

60870-5-101/104
ctlVal INT32 CO TI 30: SPI 205 ✓ ✓ TI 30
TI 31: DPI 205 TI 31
TI 45: SCS 196 206 207 ✓ ✓ TI 45
TI 46: DCS 196 206 207 TI 46
TI 49: SVA 196 TI 49
TI 50: R32-IEEE 196 TI 50
ST
stVal INT32 ST TI 30: SPI 197 206 207 ✓ ✓ TI 30
TI 31: DPI 197 206 207 TI 31
TI 33: BSI TI 33
TI 35: SVA 197 TI 35
TI 36: R32-IEEE 197 TI 36
q Quality ST TI 30: SIQ 197 ✓ ✓

TI 31: DIQ 197
TI 33: QDS 197

TI 35: QDS 197
TI 36: QDS 197
t TimeStamp ST CP56Time2a 197 ✓ ✓
subEna BOOLEAN SV
subVal BOOLEAN SV
subQ Quality SV
subID STRING64 SV
205 applies only for Client in transmit direction

206 transmit direction: for the ON state the parameterized IEC 61850 value is used
207 receive direction: for the parameterized IEC 61850 value the ON command is generated

DC8-037-2, Edition 11.2020
12.7 IEC 61850

60870-5-101/104
209
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
IEC 61850: Controllable Enumerated Status (ENC)

60870-5-101/104
ctlVal INT32 CO TI 30: SPI 205 ✓ ✓ TI 30
TI 31: DPI 205 TI 31
TI 45: SCS 196 206 207 ✓ ✓ TI 45
TI 46: DCS 196 206 207 TI 46
TI 49: SVA 196 TI 49
TI 50: R32-IEEE 196 TI 50
ST
stVal INT32 ST TI 30: SPI 197 206 207 ✓ ✓ TI 30
TI 31: DPI 197 206 207 TI 31
TI 33: BSI TI 33
TI 35: SVA 197 TI 35
TI 36: R32-IEEE 197 TI 36
q Quality ST TI 30: SIQ 197 ✓ ✓

TI 31: DIQ 197
TI 33: QDS 197
TI 35: QDS 197
TI 36: QDS 197

DC8-037-2, Edition 11.2020
12.7 IEC 61850

60870-5-101/104
subEna BOOLEAN SV
subVal BOOLEAN SV
subQ Quality SV
subID STRING64 SV
211
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
IEC 61850: Controllable Integer Status (APC)

60870-5-101/104
ctlVal AnalogueValue CO TI 49: SVA 196 ✓ TI 49
TI 50: R32-IEEE 196 TI 50
origin Originator CO see Control Model, ✓
ctlNum INT8U CO transmission (origin) ✓
ST
mxVal AnalogueValue ST TI 35: SVA 197 ✓ TI 35
TI 36: R32-IEEE 197 TI 36
q Quality ST TI 30: SIQ 197 ✓
TI 31: DIQ 197
TI 35: QDS 197

TI 36: QDS 197
t TimeStamp ST CP56Time2a 197 ✓
stSeld BOOLEAN ST TI 30: SPI 197 TI 30
subEna BOOLEAN SV
subVal AnalogueValue SV

DC8-037-2, Edition 11.2020
12.7 IEC 61850

60870-5-101/104
subQ Quality SV
subID STRING64 SV
213
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
IEC 61850: Single Point Status (SPS)

60870-5-101/104
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.

DC8-037-2, Edition 11.2020
12.7 IEC 61850
IEC 61850: Double Point Status (DPS)

60870-5-101/104
stVal CODED ENUM ST intermediate-state TI 31: SPI ✓ ✓ TI 31
off
on
bad-state
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.
IEC 61850: Integer Status (INS)

60870-5-101/104
stVal INT32 ST TI 30: SPI 214 ✓ ✓ TI 30
TI 31: DPI 214 TI 31
TI 33: BSI TI 33
TI 35: SVA TI 35
TI 36: R32-IEEE TI 36
TI 31: DIQ
TI 33: QDS
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
214 for the respective ON state the parameterized IEC 61850 value is used

DC8-037-2, Edition 11.2020
12.7 IEC 61850

60870-5-101/104
dataNs STRING256 EX
IEC 61850: Enumerated Status (ENS)

60870-5-101/104
stVal INT32 ST TI 30: SPI 214 ✓ TI 30
TI 31: DPI 214 TI 31
TI 33: BSI TI 33
TI 35: SVA TI 35
q Quality ST TI 30: SIQ ✓
TI 31: DIQ
TI 33: QDS
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
IEC 61850: Protection Activation Information (ACT)

60870-5-101/104
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

DC8-037-2, Edition 11.2020
12.7 IEC 61850

60870-5-101/104
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.
IEC 61850: Directional Protection Activation Information (ACD)

60870-5-101/104
General BOOLEAN ST TI 30: SPI ✓ ✓ TI 30
TI 31: DPI 197 TI 31
TI 38: ES TI 38
TI 39: GS TI 39
TI 40: GC TI 40
dirGeneral ENUMERATED ST unknown fixed “unknown” 215 ✓ 216 ✓ 216
forward
backward
both
215 applies only for Server in transmit direction

216 applies for Client in receive direction: if TI 31 is used

DC8-037-2, Edition 11.2020
12.7 IEC 61850

60870-5-101/104
phsA BOOLEAN ST TI 30: SPI ✓ ✓ TI 30
TI 31: DPI 197 TI 31
TI 38: ES TI 38
TI 39: SL1
TI 40: CL1
dirPhsA ENUMERATED ST unknown fixed “unknown” 215 ✓ 216 ✓ 216
forward
backward
both
phsB BOOLEAN ST TI 30: SPI ✓ ✓ TI 30
TI 31: DPI 197 TI 31
TI 38: ES TI 38
TI 39: SL2
TI 40: CL2
dirPhsB ENUMERATED ST unknown fixed “unknown” 215 ✓ 216 ✓ 216
forward
backward
both
phsC BOOLEAN ST TI 30: SPI ✓ ✓ TI 30
TI 31: DPI 197 TI 31
TI 38: ES TI 38
TI 39: SL3
TI 40: CL3
dirPhsC ENUMERATED ST unknown fixed “unknown” 215 ✓ 216 ✓ 216
forward
backward
both
neut BOOLEAN ST TI 30: SPI ✓ 217 ✓ 218 TI 30
TI 31: DPI 197 TI 31
TI 38: ES TI 38
TI 39: SIE
dirNeut ENUMERATED ST unknown fixed “unknown” 215 ✓ 216 ✓ 216
forward
backward
both
TI 31: DIQ 197
TI 38: SEP
TI 39: QDP
TI 40: QDP
operTim STRING256 CF
d STRING256 DC
dU USTRING256 DC
217 does not apply for TI 31

218 does not apply for TI 31

DC8-037-2, Edition 11.2020
12.7 IEC 61850

60870-5-101/104
cdcNs STRING256 EX
dataNs STRING256 EX

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
State Direction information TI 31: DPI
AUS (0) unknown (0) DIFF (00)
forward (1) DIFF (00)
backward (2) DIFF (00) D
both (3) DIFF (00)
ON (1) unknown (0) ON (10)
forward (1) ON (10)
backward (2) AUS (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 separate single-point information can be derived from the status + direction information (max. 4 single-
point information items).
By means of the option “transient” in the message address conversion the following behavior can be adjusted:
• without transient
if the information is ON and an additional ON information with different direction occurs, then both
IEC 60870-5-104 information items are set to ON
• with transient
if the information is ON and an additional ON information with different direction occurs, then the
previous IEC 60870-5-104 information is set to OFF and the new information is set to ON; thereby always
only 1 information item out of the possible 4 information items is ON
IEC 61850 direction information ON info on IEC 61850 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.

DC8-037-2, Edition 11.2020
12.7 IEC 61850
IEC 61850: Setting Group (SGCB)

60870-5-101/104
NumOfSG INT8U TI 35: SVA 197 ✓ ✓ TI 35
TI 36: R32-IEEE 197 TI 36
ActSG INT8U TI 30: SPI 197 219 206 ✓ ✓ TI 30
TI 31: DPI 197 219 206 TI 31
TI 35: SVA 197 TI 35
TI 36: R32-IEEE 197 TI 36
TI 45: SCS 196 206 220 ✓ 221 ✓ 221 TI 45

TI 46: DCS 196 206 220 TI 46
TI 49: SVA 196 TI 49
TI 50: R32-IEEE 196 TI 50
EditSG INT8U
CnfEdit BOOLEAN
LActTm TimeStamp CP56Time2a 197 ✓ ✓
For further details refer to section Server ↔ Client Data Transmission, Page 936, 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.: VLC01/LLN0.SGCB).
Values of the SGCB are not assigned to a dataset resp. Unbuffered Control Block (no spontaneous transmis-
sion).

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.
IEC 61850: Binary Counter Reading (BCR)

60870-5-101/104
actVal INT128 ST TI 37: BCR 222 ✓ ✓ TI 37
frVal INT128 ST TI 37: BCR 223 ✓ ✓ TI 37
frTm TimeStamp ST CP56Time2a 223 ✓ ✓
q Quality ST IV 222 223 ✓ ✓
units Unit CF
pulsQty FLOAT 32 CF ✓224
219 applies also for Client in transmit direction

220 receive direction: for the parameterized IEC 61850 value the ON command is generated
221 transmit direction: no SEL/EXE permissible, but only EXE
222 is used with use of the attribute "actVal"
223 is used with use of the attribute "frVal"
224 for Client Ed.2 only; can be enabled for each data point, value = Value * pulsQty

DC8-037-2, Edition 11.2020
12.7 IEC 61850

60870-5-101/104
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

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.
IEC 61850: Binary Controlled Step Position Information (BSC)

60870-5-101/104
ctlVal CODED_ENUM CO stop TI 47: RCO 196 225 ✓ ✓ TI 47
lower
higher
ctlNum INT8U CO transmission (origin) ✓ ✓
ST
valWTr INT8U ST TI 32: VTI 197 ✓ ✓ TI 32
q Quality ST QDS 197 ✓ ✓
stSeld BOOLEAN ST
subEna BOOLEAN SV
subVal BOOLEAN SV
subQ Quality SV
subID STRING64 SV
persistent BOOLEAN CF
direct-with-normal- detailed routing 227
security
direct-with-
enhanced-sec.
sbo-with-enhanced-
sec.
225 the status "stop" is generated with the not permissible value "00" acc. to IEC 60870-5-101/104

DC8-037-2, Edition 11.2020
12.7 IEC 61850

60870-5-101/104
minVal INT8 CF
maxVal INT8 CF
stepSize INT8U CF
d STRING256 DC
dU USTRING256 DC
cdcNs STRING256 EX
dataNs STRING256 EX
IEC 61850: Integer Controlled Step Position Information (ISC)

60870-5-101/104
ctlVal INT8 CO -64…+63 TI 49: SVA 196 228 ✓ ✓ TI 49
TI 50: R32 – IEEE 196 TI 50
229
ST
valWTr ValWithTrans ST TI 32: VTI 197 ✓ ✓ TI 32
q Quality ST QDS 197 ✓ ✓
stSeld BOOLEAN ST
subEna BOOLEAN SV
subVal BOOLEAN SV
subQ Quality SV
subID STRING64 SV
persistent BOOLEAN CF
direct-with-normal- detailed routing 231
security
direct-with-
enhanced-sec.
sbo-with-enhanced-
sec.
minVal INT8 CF
maxVal INT8 CF
228 in contrast to the standard the maximum values can be in the range -128… +127

DC8-037-2, Edition 11.2020
12.7 IEC 61850

60870-5-101/104
stepSize INT8U CF
d STRING256 DC
dU USTRING256 DC
cdcNs STRING256 EX
dataNs STRING256 EX
IEC 61850: Analogue Setting (ASG)

60870-5-101/104
setMag Analogue SP TI 49: SVA 196 ✓ ✓ TI 49
Value TI 50: R32-IEEE 196 TI 50
TI 35: SVA 197 ✓ ✓ TI 35
TI 36: R32-IEEE 197 TI 36
units Unit CF
sVC Select Value CF
Config
minVal Analogue CF
Value
maxVal Analogue CF
Value
stepSize Analogue CF
Value
d STRING256 DC
dU USTRING256 DC
cdcNs STRING256 EX
dataNs STRING256 EX

With writing of the value no Setting Group setting is performed, however, a simple write process.
IEC 61850: Integer Setting (ING)

60870-5-101/104
setVal INT32 SP TI 49: SVA 196 ✓ ✓ TI 49
TI 50: R32-IEEE 196 TI 50
TI 35: SVA 197 ✓ ✓ TI 35
TI 36: R32-IEEE 197 TI 36
setVal INT32 SG,
SE
minVal INT32 CF
maxVal INT32 CF
stepSize INT32 CF
d STRING256 DC

DC8-037-2, Edition 11.2020
12.7 IEC 61850

60870-5-101/104
dU USTRING256 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.
IEC 61850: Measured Value (MV)

60870-5-101/104
instMag AnalogueValue MX ✓ TI 34
TI 35
TI 36
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 ScaledValue- CF
Config
rangeC RangeConfig CF
smpRate INT32U CF
d STRING256 DC
dU USTRING256 DC
cdcNs STRING256 EX
dataNs STRING256 EX
IEC 61850: Complex Measured Value (CMV)

60870-5-101/104
instCVal Vector MX ✓ TI 34
TI 35
TI 36

DC8-037-2, Edition 11.2020
12.7 IEC 61850

60870-5-101/104
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 ScaledValue- CF
Config
angSVC ScaledValue- CF
Config
angRef ENUMERATED CF - V
-A
- ...
smpRate INT32U CF
d STRING256 DC
dU USTRING256 DC
cdcNs STRING256 EX
dataNs STRING256 EX
IEC 61850: Sampled Value (SAV)

60870-5-101/104
instMag AnalogueValue MX TI 34: NVA ✓ ✓ TI 34
TI 35: SVA TI 35
units Unit CF
sVC ScaledValue- CF
Config
min AnalogueValue CF
max AnalogueValue CF
d STRING256 DC
dU USTRING256 DC
cdcNs STRING256 EX

DC8-037-2, Edition 11.2020
12.7 IEC 61850

60870-5-101/104
dataNs STRING256 EX
IEC 61850: Collection Of Measurands (WYE)

60870-5-101/104
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
IEC 61850: Delta (DEL)

60870-5-101/104
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

DC8-037-2, Edition 11.2020
12.7 IEC 61850

60870-5-101/104
dU USTRING256 DC
cdcNs STRING256 EX
dataNs STRING256 EX
IEC 61850: Sequence (SEQ)

60870-5-101/104
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
IEC 61850: Device Name Plate (DPL)

60870-5-101/104
vendor STRING256 DC fix "SIEMENS" ✓
hwRev STRING256 DC ✓
swRev STRING256 DC Revision ETxx 232 ✓
serNum STRING256 DC
model STRING256 DC
location STRING256 DC
cdcNs STRING256 EX
dataNs STRING256 EX
232 xx = 03, 83 (dependent on the respective firmware)

DC8-037-2, Edition 11.2020
12.7 IEC 61850
IEC 61850: Logical Node Name Plate (LPL)

60870-5-101/104
vendor STRING256 DC fix "SIEMENS" ✓
swRev STRING256 DC Revision ETxx 232 ✓
d STRING256 DC 233 ✓
dU USTRING256 DC
configRev STRING256 DC fix 0 234 ✓
ldNs STRING256 EX fix "IEC 61850-7-4: ✓
2002" 234
lnNs STRING256 EX
cdcNs STRING256 EX
dataNs STRING256 EX
IEC 61850: Single Point Setting (SPG)

60870-5-101/104
setVal Boolean SP TI 45: SPC ✓
TI 30: SPI ✓
setVal Boolean SG,
SE
d STRING256 DC
dU USTRING256 DC
cdcNs STRING256 EX
dataNs STRING256 EX
Mapping IEC 61850 → MMS

By means of the mapping from IEC 61850 to MMS, new “Extended Common Data Classes” result.
NOTE
i The “Extended Common” Data Classes serve only for the transmission on the line.
Extended Common Data Classes
Select with Value (SBOw), Operate (Oper), Cancel (Cancel)
Attribute Name Type supported

Ed.1 Ed.2
ctlVal 235 ✓ ✓
setMag
233 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. VLC01/Q0XCBR1)
234 only with LNN0
235 is adopted from the Basis Common Data Class

DC8-037-2, Edition 11.2020
12.7 IEC 61850
Attribute Name Type supported

operTm TimeStamp
origin Originator ✓ ✓
ctlNum INT8U ✓ ✓
T TimeStamp 236 ✓ ✓
Test BOOLEAN ✓ ✓
Check PACKED LIST 236 237 ✓ ✓
12.7.8.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).
Client in Transmit 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 value adapta- Value adaptation limits
tion_X_0%
Measured value adapta-
tion_X_100%
tion_Y_0%
tion_Y_100%
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
236 is not evaluated

237 for Cancel not present

DC8-037-2, Edition 11.2020
12.7 IEC 61850

CDC Common Data Class 238
12 = SPC
13 = DPC
14 = INC
20 = SGCB
21 = BSC
22 = ISC
23 = ASG
24 = ING
25 = APC
27 = ENC
29 = SPG
IEC61850_command_qualifier 0 = via IEC 60870-5-101/104 qualifier of command ✓
239
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_O 240 ✓
N
IEC61850_value_at_TI45/46_OF 240 ✓
F
TIO Con->Term without syncro- 241 ✓
check
TIO Con->Term with syncro- 241 ✓
check
238 The belonging CDC must be parameterized here. Always the hierarchical most significant CDC must be parameterized. Example:
VLC01/CSWI1.Pos.ctlVal = DPC (Pos = DPC), VLC01/MMXU1.A.phsA.cVal.mag.f (A = WYE)
239 The attribute “Check” is affected by means of that. The default entry is 0 (control by the IEC 60870 -5 -101/104 qualifier of command,
refer to Control Model, Page 943, Command Output Time (QU)).
240 This value is transmitted instead of ON (1) or OFF (0) and can be used for the CDCs “INS”, “INC” and “SGCB”; as of IEC 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.
241 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.

DC8-037-2, Edition 11.2020
12.7 IEC 61850

IM_CASDU1_ON Address of the interlocking information for the ON ✓
IM_CASDU2_ON command 242
IM_IOA1_ON
IM_IOA2_ON
IM_IOA3_ON
IM_CASDU1_OFF Address of the interlocking information for the OFF ✓
IM_CASDU2_OFF command 242
IM_IOA1_OFF
IM_IOA2_OFF
IM_IOA3_OFF
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
Client in Receive Direction

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
tion_X_0%
tion_X_100%
tion_Y_0%
tion_Y_100%
thresh_uncond Absolute value 243
thresh_additive Absolute value 243
242 By means of respectively one single-point information (TI 30) for the ON resp. the OFF command an overlapping interlocking opera-
tion 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. Note: The interlock only works if the signals are also sent to the PRE (pass-through filter/selective routing).
243 The measured value change monitoring occurs on the raw value (= received value from the Server).

DC8-037-2, Edition 11.2020
12.7 IEC 61850

45 = Single command
46 = Double command
47 = Regulating step command
CDC Common Data Class 244
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
29 = SPG
ON-info_on_IEC61850_value 245 ✓
Usage_on_informa- 0 = event ✓
tion_IEC61850_ 1 = IEC61850 value bit 0
2 = IEC61850 value bit 1
244 The belonging CDC must be parameterized here. Always the hierarchical most significant CDC must be parameterized. Example:
VLC01 / XCBR1.Pos.stVal = DPC (Pos = DPC), VLC01 / MMXU1.TotW.mag.f = MV (TotW = MV), VLC01 / MMXU1.A.phsA.cVal.mag.f =
WYE (A = WYE)
245 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 IEC 61850 Ed. 2: "ENS", "ENC"). For the CDC “ACD” the direction information can be evaluated with the values 2, 3, 4, 5 (IEC 61850:
Common Data Classes, Page 966, IEC 61850: Directional Protection Activation Information (ACD)

DC8-037-2, Edition 11.2020
12.7 IEC 61850

type_of_binary_information coming/going 246 ✓
Coming
pulsQty yes ✓
no
Client – Disturbance Record in Transmit Direction

CASDU2
IOA1
IOA2
IOA3
TI 142 = user data container
File transfer mode Client
Client – Disturbance Record in Receive Direction

CASDU2
IOA1
IOA2
IOA3
TI 142 = user data container
File transfer mode Client
Server in Transmit Direction

CASDU2
IOA1
IOA2
IOA3
IEC61850_Address 68 bytes ASCII characters
tion_X_0%
tion_X_100%
tion_Y_0%
tion_Y_100%
Selectivity To all remote stations/selective
246 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).

DC8-037-2, Edition 11.2020
12.7 IEC 61850

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 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
29 = SPG
IEC61850_value_at_TI30/31_O 247 ✓
N
F
Usage_IEC61850_value_off 0 = IEC61850 value at TI30/31 OFF not used ✓
1 = IEC61850 value at TI30/31 OFF used
247 This value is transmitted instead of ON and can be used for the CDCs “INC”, “INS” (Ed. 1) resp. “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.
248 This value is transmitted instead of OFF and can be used for the CDCs “INC”, “INS” (Ed. 1) resp. “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.

DC8-037-2, Edition 11.2020
12.7 IEC 61850

Goose_Attr1_Datasetpos 249 Selection 0…255 ✓
Goose_Attr2_Datasetpos 249
Goose_Attrib1 249 GOOSE attribute (refer to GOOSE Attributes, ✓
Goose_Attrib2 249 Page 1002)
Goose_Attrib3 249
Goose_Attrib4 249
Goose_Attrib5 249
Goose_Idx 249 Selection 0…255 ✓
Server in Receive Direction

CASDU2
IOA1
IOA2
IOA3
Controltype - Direct Control With Normal Security
- Direct Control With Enhanced Security
- SBO Control With Enhanced Security
tion_X_0%
tion_X_100%
tion_Y_0%
tion_Y_100%
45 = Single command
46 = Double command
249 only Edition 2

DC8-037-2, Edition 11.2020
12.7 IEC 61850

CDC 0 = Standard
12 = SPC
13 = DPC
14 = INC
21 = BSC
22 = ISC
23 = ASG
24 = ING
25 = APC
27 = ENC
29 = SPG
ON- 250 ✓
command_on_IEC61850_value
Goose_Attr1_Datasetpos 249 Selection 0…255 ✓
Goose_Attrib1 249 GOOSE attribute (refer to GOOSE Attributes, ✓
Goose_Attrib3 249
Goose_Attrib4 249
Goose_Attrib5 249
Goose_Idx 249 Selection 0…255
Server in Transmit Direction + Goose [only Edition 1]

CASDU2
IOA1
IOA2
IOA3
tion_X_0%
tion_X_100%
tion_Y_0%
tion_Y_100%
250 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",
"SGCB"; as of IEC 61850 Ed. 1) resp. “ENC“, “ENS“ (Ed. 2), "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.

DC8-037-2, Edition 11.2020
12.7 IEC 61850

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
IEC61850_value_at_TI30/31_O 251 ✓
N
F
Goose_Attrib1 249 GOOSE attribute (refer to GOOSE Attributes,
Goose_Attrib3 249
Goose_Attrib4 249
Goose_Attrib5 249
Goose_Index_A GOOSE Index in the system technique 0…255
Goose_Index_B
Goose_Index_C
251 This value is transmitted instead of ON (1) and can be used for the CDCs "INC", "INS" (Ed. 1) resp. “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.
252 This value is transmitted instead of OFF and can be used for the CDCs "INC", "INS" (Ed. 1) resp. “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.

DC8-037-2, Edition 11.2020
12.7 IEC 61850

Goose_Attr1_Data- Dataset Position 0…255 253 ✓
setpos_Index_A
Goose_Attr1_Data-
setpos_Index_B
Goose_Attr1_Data-
setpos_Index_C
Goose_Attr2_Data-
setpos_Index_A
Goose_Attr2_Data-
setpos_Index_B
Goose_Attr2_Data-
setpos_Index_C
Goose_Attr3_Data-
setpos_Index_A
Goose_Attr3_Data-
setpos_Index_B
Goose_Attr3_Data-
setpos_Index_C
Goose_Attr4_Data-
setpos_Index_A
Goose_Attr4_Data-
setpos_Index_B
Goose_Attr4_Data-
setpos_Index_C
Goose_Attr5_Data-
setpos_Index_A
Goose_Attr5_Data-
setpos_Index_B
Goose_Attr5_Data-
setpos_Index_C
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 OFF used
253 The dataset position must be parameterized ascending from 0 and must not have breaks.

DC8-037-2, Edition 11.2020
12.7 IEC 61850
Server in Receive Direction + Goose [only Edition 1]

CASDU2
IOA1
IOA2
IOA3
Controltype - Direct Control With Normal Security
- Direct Control With Enhanced Security
- SBO Control With Enhanced Security
tion_X_0%
tion_X_100%
tion_Y_0%
tion_Y_100%
Thresh_uncond Absolute value 254
Thresh_additive Absolute value 254
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- 255 ✓
command_on_IEC61850_value
254 The measured value change monitoring occurs on the raw value (= received value).
255 With the value for TI 45, TI46 can be parameterized, at which IEC 61850 value the ON command is to be generated. The corre-
sponding OFF command is generated automatically by the firmware as soon as another value is received (applies only for the CDCs
"INC", "INS", "SGCB"; as of IEC 61850 Ed. 1) resp. “ENC“, “ENS“ (Ed. 2) and "SGCB").

DC8-037-2, Edition 11.2020
12.7 IEC 61850

Goose_Attrib1 249 GOOSE attribute (refer to GOOSE Attributes,
Goose_Attrib3 249
Goose_Attrib4 249
Goose_Attrib5 249
Goose_Index_A GOOSE Index in the system technique 0…255
Goose_Attr1_Data- Dataset Position 0…255 256 ✓
setpos_Index_A
Goose_Attr2_Data-
setpos_Index_A
Goose_Attr3_Data-
setpos_Index_A
Goose_Attr4_Data-
setpos_Index_A
Goose_Attr5_Data-
setpos_Index_A
Station_A Selection station 0…99 255 = to all stations ✓
Station_B
Station_C
Station_D
Station_E
Station_F
Station_G
Station_H
Station_I
Station_J
256 The dataset position must be parameterized ascending from 0 and must not have breaks.

DC8-037-2, Edition 11.2020
12.7 IEC 61850
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
mag.i MV
cVal.mag.f CMV
cVal.mag.i CMV
instMag.f SAV
phsA.cVal.mag.f WYE
phsA.cVal.mag.i WYE
phsB.cVal.mag.f WYE
phsB.cVal.mag.i WYE
phsC.cVal.mag.f WYE
phsC.cVal.mag.i WYE
neut.cVal.mag.f WYE
neut.cVal.mag.i WYE
net.cVal.mag.f WYE
net.cVal.mag.i WYE
res.cVal.mag.f WYE
res.cVal.mag.i 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

DC8-037-2, Edition 11.2020
12.7 IEC 61850
GOOSE Attribut Common Data Class (CDC)

phsAB.cVal.mag.f DEL
phsAB.cVal.mag.i DEL
phsBC.cVal.mag.f DEL
phsBC.cVal.mag.i DEL
phsCA.cVal.mag.f DEL
phsCA.cVal.mag.i DEL
phsAB.q DEL
phsAB.t DEL
phsBC.q DEL
phsBC.t DEL
phsCA.q DEL
phsCA.t DEL
c1.cVal.mag.f SEQ
c1.cVal.mag.i SEQ
c2.cVal.mag.f SEQ
c2.cVal.mag.i SEQ
c3.cVal.mag.f SEQ
c3.cVal.mag.i 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
SPC (stVal, q, t) SPC 257
DPC (stVal, q, t) DPC 257
ENC (stVal, q, t) ENC 257
INC (stVal, q, t) INC 257
SPS (stVal, q, t) SPS 257
DPS (stVal, q, t) DPS 257
ENS (stVal, q, t)
ENS 257
INS (stVal, q, t)
INS 257
Server in Transmit Direction – Default Values

257 In Ed. 2 these attributes can be received/sent as data structures in GOOSE

DC8-037-2, Edition 11.2020
12.7 IEC 61850

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
Value Default value (30 characters)
With this routing the Data Attribute Name must be named always.
For the following Basic Types (refer to IEC 61850: Basic Types, Page 963) a default value can be parameter-
ized, 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
GOOSE Properties (System Technique)
Routing element Edition 1 Edition 2

GOOSE Index 0…99 0…99
GoCBRef 65 Byte ASCII 258 128 Byte ASCII 258
GoID 65 Byte ASCII 259 129 Byte ASCII 259
DataSet 68 Byte ASCII 260 128 Byte ASCII 260
MAC Address 12 Byte ASCII 261 12 Byte ASCII 261
AppID 0…3FFF 262 0…3FFF 262
configRev 0…4294967295 263 0…4294967295 263
258 reference to the GOOSE Control Block, e.g.: VLC01/LLN0.gcST

259 unambiguous identification of the GOOSE message
260 name of the Data Set, e.g.:VLC01/ds2
261 see section Data Transmission Server ↔« Server with "GOOSE" [Server only], Page 938
262 should be unambigousg over all GOOSE messages and unequally 0 (attention: HEX)
263 32 bit value, the SICAM TOOLBOX II supports only a 16 bit value (0…65535)

DC8-037-2, Edition 11.2020
12.7 IEC 61850
Routing element Edition 1 Edition 2

VLAN Vid 0…4096 264 0…4096 264
VLAN Priority 0…7 265 0…7 265

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
• 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 61850
• Automatic Load Shedding
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 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
Signaling / Measured Value Disabling [Client only]

The signaling / measured value disabling is a function of the protection equipment and can be activated glob-
ally (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 func-
tion 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 direc-
tion. The protocol element evaluates the attribute of the respective logical node with higher priority than the
attribute of the logical node LLN0.
264 should be unequally 0

265 default 4

DC8-037-2, Edition 11.2020
12.7 IEC 61850
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 IEC 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 IEC 61850 Edition 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)

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 IEC 61850 Server function from the IEC 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
i • In the SICAM RTUs protocol element with IEC 61850 Server function, no special functionality is imple-
mented 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 interroga-
tion 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 IEC 61850 to the
Client. On deactivation of the signaling / measured value disabling, all signals/measured values are
transmitted spontaneously with the status “spontaneous”.
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 IEC 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 milli-
seconds.
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.
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 IEC 61850 Server
function to the internal IEC 60870-5-101/104 format can be selected with the parameter IEC 61850 |
Client | Advanced parameters | Behavior of Beh.stVal=5 (OFF) (as of IEC 61850 Edition 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)

DC8-037-2, Edition 11.2020
12.7 IEC 61850
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.
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
i 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 IEC 61850 Server function from the IEC
61850 Clients and the data transferred spontaneously:
• Change of the attribute “Beh.StVal” form OFF → ON
• Change of the attribute “Beh.StVal” form OFF → TEST
• Change of the attribute “Beh.StVal” form OFF → TEST-BLOCKED
Technological adaptation for measured values

The technological adaptation enables the measured value supplied by the connected devices to be trans-
formed 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 Identification (IEC Spontaneous Informa- Value Range Meaning
60870-5-104) tion Object
<TI:=34> Measured value, normal- - 1 ... + 1-2-15 normalized, percental
ized value representation
<TI:=35> Measured value, scaled - 32768 technological, integer
value ...
+ 32767
<TI:=36> Measured value, short - 8,43 ⋅ 10-37 technological, floating
floating point ... point
+ 3,37 ⋅ 1038
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.
Bipolar measured values without zero-range suppression and plausibility check
Example: Value Meaning Parameters

X0 -2000 lower boundary of the measuring range (set by Measured value adapta-
parameter) tion_X_0%
X100 +2000 upper boundary of the measuring range (set by Measured value adapta-
parameter) tion_X_100%

DC8-037-2, Edition 11.2020
12.7 IEC 61850
Example: Value Meaning Parameters

Y0 -1 technological value at X0 Measured value adapta-
tion_Y_0%
Y100 +1 technological value at X100 Measured value adapta-
tion_Y_100%
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

In the system element specific processing grid the measured value is monitored for change. If the deviation
from the last spontaneously transmitted measured value is greater than the parameterized
thresh_uncond , the new measured value is transmitted immediately. Otherwise, in the parameterized

DC8-037-2, Edition 11.2020
12.7 IEC 61850
processing grid the deviations from the last spontaneously transmitted measured value are totalled according
to the polarity sign. First when the amount of this total exceeds the parameterized Thresh_additive is the
current measured value spontaneously transmitted.
Thresh Thresh addi- Processing
uncond tive
0 0 value will be sent to BSE immediately after change
0 ≠0
≠0 0 value will be sent to BSE immediately after change
≠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
procedure.
By means of parameterization it is established:
• Processing grid 0.1 s…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 parameter 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.
The following example shows a normal case, where the adaption 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)
Example 1:
threshold) and subsequently remains 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
Example 2:
threshold) and subsequently remains constant. The measured value is transmitted after 10 minutes.

DC8-037-2, Edition 11.2020
12.7 IEC 61850
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
Monitoring Intermediate and Faulty Positions of Double Point Information [Client only]
Double-point information that are transmitted from the connected IEC 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 a double-point information with intermediate or faulty position, the suppression 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 suppression time is stopped and
the double-point information is transferred with the valid binary information state.
The time tag after suppression of intermediate and faulty position corresponds to the original time tag+ the
parameterized suppression time (Example: Intermediate position at 12:01:02.123 with 10 seconds suppres-
sion time, message transfer after 10 second with time 12:01:12.123).
The suppression time for intermediate position is to be parameterized for all double-point informations
together with the parameter IEC61850 | Client | Intermediate position suppression time
(as of IEC 61850 Edition 2: Connection definition | Intermediate position suppression
time (s) ).
The suppression time for faulty position is to be parameterized for all double-point informations together with
the parameter IEC61850 | Client | faulty state suppression time (as of IEC 61850 Edition 2:
Connection definition | Faulty position suppression time (s) ).
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 /... /firm-
ware/ ....
Logging of the Remote Commands at the Local Control Center [Server only]
For documentation or traceability, a logging of operator inputs to an existing local control center is often
required.
So that remote commands can be logged at a local control center connected in the IEC 61850 network, the
remote commands must also be sent to the local control center. However with IEC 61850, due to the Server/
Client communication this is not possible without additional measures!
For configurations with SICAM RTUs components as IEC 61850 Client and the control centre system SICAM
SCC as local control centre, the logging of remote commands via IEC 61850 is possible by means of a propri-
etary (non-compatible) procedure, if an unambiguously assigned return information is available for every
remote command (assignment: ctlVal ⇔ stVal).

DC8-037-2, Edition 11.2020
12.7 IEC 61850
With function activated, the protocol element with IEC 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, Higher/Lower,…)
• Originator address
The function can be activated with the parameter IEC61850 | Server | Advanced parameters |
Log remote commands on local SCADA system .
Remote parameterization/diagnostic of SICAM RTUs components via 61850

If SICAM RTUs components are used as IEC 61850 Client and as IEC 61850 Server, then a remote parameteriza-
tion/diagnostic of the SICAM RTUs components can be performed over the LAN connection and the IEC 61850
protocol element.
The remote parameterization/diagnostic is activated automatically by the IEC 61850 protocol element, as soon
as the connection is established and a SICAM RTUs component with IEC 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 parameteri-
zation/diagnostic takes place over TCP/IP with messages defined especially for this purpose.
Automatic Load Shedding

Critical events with sudden significant loss of generated power are a serious threat for the stability of industry
grids. Such disturbance of the balance between generated power and load typically results in a frequency drop
and the risk of activation of generator protection relays. As these relays protect running generators their trip
causes even more decline of frequency and finally resulting in a total blackout. This so called “domino-effect”
has to be avoided to make sure, that at least the main production works uninterrupted.
The only way to prevent deep drops in system frequency and a frequency collapse following a large distur-
bance is to employ automatic fast shedding of low priority loads.
The function Automatic Load Shedding aims to maintain stability of electrical grids in industry, especially in
critical situations like a generator trip or loss of the tie-line to an external utility. Thereby consumer feeders
with low priority will be switched off in order to establish the balance of generated and consumed loads.
Set Loads
Up to 300 loads (Load 1 to Load X) can be configured, each load has a trip matrix.

DC8-037-2, Edition 11.2020
12.7 IEC 61850
[dw_ETx5_load_shedding, 1, en_US]
Required Settings
• CASDU1, CASDU2
IOA1, IOA2, IOA3
IEC 60870-5-101/104 address that adjusts the bitmask resp. takeover information, test information
• TI
30 for the takeover information, test information (load number, GOOSE information is not evaluated)
33 for the bitmask
• Signal_type
Matrix, enable, test
• Load_Number
1 ... 300
• Rückmeldung_CASDU1, Rückmeldung_CASDU2
Rückmeldung_IOA1, Rückmeldung_IOA2, Rückmeldung_IOA3
Address of the return information for trip matrix resp. trip matrix takeover (if desired) resp. test mode
• RI_TI
30 for the takeover information, test information
33 for the bitmask
• Load_Trip_CASDU1, Load_Trip_CASDU2
Load_Trip_IOA1, Load_Trip_IOA2, Load_Trip_IOA3
IEC 60870-5-101/104 address of the trip to the load in order to trip the circuit breaker
• Trip_load_TI
30 for the trip in direction BSE

DC8-037-2, Edition 11.2020
12.7 IEC 61850
• Match_contingency_CASDU1, Match_contingency_CASDU2
Match_contingency_IOA1, Match_contingency_IOA2, Match_contingency_IOA3
IEC 60870-5-101/104 address of the return information load tripped through contingency trip
• Match_contingency_TI
30 for the trip in direction GOOSE
• Send_trip_for_test
Trip to the load in order to trip the circuit breaker in test mode
• Trip_load_pulse_duration
Output time for the GOOSE information
• Contingency_number
1…30
Set trip matrix

The trip matrix can be set with a TI 33 information. The information can be received by the BSE (application
program) or by GOOSE (CDC = INC, INS).
[sc_ETx5_load_shedding_01, 1, en_US]

DC8-037-2, Edition 11.2020
12.7 IEC 61850
Trip Matrix Enable

The setting of the bit combination for each load is only active, if a coming edge of a load-overlapping enable
information of the BSE or by GOOSE was received (the new bit combinations are written into the memory as
prepared and copied with the enable information for all loads in the active memory. Thereby it is assured that
all loads have the correct state simultaneously).
With the coming enable information (takeover new trip matrix) all current set new bit combinations will be
sent as return information (TI 33) spontaneously in direction BSE, these return information items are GI-
capable. The enable information will be sent spontaneously as return information in direction BSE and is GI-
capable.
Test Mode
A load-overlapping test information is sent spontaneously as return information in direction BSE.

DC8-037-2, Edition 11.2020
12.7 IEC 61850
Contingency Trip
Per contingency a trip impulse is received by GOOSE. If a corresponding bit for each load is set to 1, a GOOSE
information is generated and also an information in direction BSE. The GOOSE information (CB Trip) is only
generated, if the Test bit is set to 0 or if the GOOSE trigger was parameterized to Yes with Test (for each
load). The information in direction BSE is always generated (if the status TEST is active, the coming informa-
tion is provided with the Test bit, this can be evaluated in the application program).

DC8-037-2, Edition 11.2020
12.7 IEC 61850
The GOOSE applications and information items must be configured via the normal way of the Server parame-
terization (SICAM TOOLBOX II and Sysconf).
The information in direction BSE will be generated with ON and OFF, whereby the time tag is +10 ms between
the both information items.
The GOOSE information is set to ON for the adjustable time Trip_load_pulse_duration (n⋅100 ms) and
thereafter to OFF again (minimal time 200 ms).
Quality Bit Handling
• If the bitmask is provided with the NT or IV bit, the status will be taken over anyway
• If the Test information is provided with the NT or IV bit, the status will be taken over anyway
• If the enable information is provided with the NT or IV bit, all bitmasks (actual and prepared) are set to 0
Time Supervision
If the enable information does not have a rising edge per all 5 seconds, all active bitmasks will be set to 0, the
prepared bitmasks will be maintained.
Example: Bitmasks are set per IEC 60870-5-104
Type 104 address Load IEC 61850 binary infor- 104 address trip 104 address
mation trip return information
Bitmask TI = 33, CASDU, IOA 1 IED1CTRL/GGIO1. TI = 30, CASDU, IOA TI = 33, CASDU, IOA
SPCSO1.stVal
SPCSO2.stVal
SPCSO3.stVal
Takeover TI = 30, CASDU, IOA - - - TI = 30, CASDU, IOA
Test TI = 30, CASDU, IOA - - - TI = 30, CASDU, IOA

DC8-037-2, Edition 11.2020
12.7 IEC 61850
IEC 61850 trigger Load

IED1CTRL/GGIO1.SPCSO88.stVal 1
Sequence:
Direction
BSE → PRE Setting bitmask load 1 (is copied into prepared memory without test bit)
BSE → PRE Takeover ON (all loads are copied from the prepared memory into the active
memory)
PRE → BSE Return information takeover ON (spontaneous)
PRE → BSE Return information bitmask load 1 (spontaneous)
BSE → PRE Takeover OFF
PRE → BSE Return information takeover OFF (spontaneous)
GOOSE → PRE Trigger 1 (load 1 triggers)
PRE → GOOSE Trip load 1
PRE → BSE Trip load 1 (spontaneous) (test bit = 0)
BSE → PRE Test ON (all test bits of all loads are set to 1)
PRE → BSE Return information Test ON (spontaneous)
BSE → PRE Test OFF (all test bits of all loads are set to 0)
PRE → BSE Return information Test OFF (spontaneous)
Example: Bitmasks are set per IEC 61850
Type IEC 61850 trigger Load IEC 61850 binary infor- 104 address trip 104 address
mation trip return information
Bitmask IED1CTRL/GGIO7. 1 IED1CTRL/GGIO1. TI, CASDU, IOA TI = 33, CASDU, IOA
ISCSO8.stVal SPCSO1.stVal
Takeover IED5CTRL/GGIO7. - - - TI = 30, CASDU, IOA
SPCSO78.stVal
Test IED9CTRL/GGIO7. - - - TI = 30, CASDU, IOA
SPCSO70.stVal
IEC 61850 trigger Load


DC8-037-2, Edition 11.2020
12.7 IEC 61850
Sequence:
Direction
GOOSE → PRE Setting bitmask load 1 (is copied into prepared memory without test bit)
PRE → BSE Setting bitmask load 1 through normal GOOSE reception
GOOSE → PRE Setting bitmask load 2(is copied into prepared memory without test bit)
GOOSE → PRE Setting bitmask load 3 (is copied into prepared memory without test bit)
GOOSE → PRE Takeover ON (all loads are copied from the prepared memory into the active
memory)
PRE → BSE Takeover ON through normal GOOSE reception
PRE → BSE Return information takeover ON (spontaneous)
GOOSE → PRE Takeover OFF
PRE → BSE Takeover OFF through normal GOOSE reception
PRE → BSE Return information takeover OFF (spontaneous)
PRE → GOOSE Trip load 1
GOOSE → PRE Test ON (all test bits of all loads are set to 1)
PRE → BSE Test ON through o normal GOOSE reception
PRE → BSE Return information Test ON (spontaneous)
GOOSE → PRE Test OFF (all test bits of all loads are set to 0)
PRE → BSE Test OFF through normal GOOSE reception
PRE → BSE Return information Test OFF (spontaneous)


• ---
Block Diagram

DC8-037-2, Edition 11.2020
12.7 IEC 61850
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 deter-
mined by the protocol element used.
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.
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.
Possible Client functions

SF Station Z-Par FI
Connection Setup
START connection to server Start connection to server
128 0-99 -
("Initiate") controlled by IEC 61850 client → IEC
61850 server
Connection release
Stop connection to server
controlled by IEC 61850 client → IEC
STOP connection to server
129 0-99 - 61850 server
("Conclude")
Comment:
present station fault will not be
changed.

DC8-037-2, Edition 11.2020
12.7 IEC 61850

SF Station Z-Par FI
Send (general) interrogation 240 This function is processed on the BSE
- - system message and not using PRE-
control message!
CASDU = BROADCAST
Send (general) interrogation 241 This function is processed on the BSE
command for GI-group to own and not sent to the protocol element
BSE - - as PRE-control message!
(=simulate received general inter-
rogation command for GI group)
Set control location 266 SCS=<ON>: set control location (HKA)
65535
(all stations)
65535 (HKA)
(all stations)
242
65535
(selective station)
0-99 SCS=<OFF>: reset control location
65535 (HKA)
(selective station)
command
control message!
CASDU = selective
Legend:
SF Control function_(PRE)
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
Presently the LAN protocol element does not support any protocol return information messages!
266 - 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

DC8-037-2, Edition 11.2020
12.7 IEC 61850
12.7.10 Web Server
12.7.10.1 IEC 61850 Edition 1 [Client + Server]
A web server is integrated into the protocol firmware for internal diagnostic information. 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 (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 inter-
face of the automation unit.
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
i 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”.
Via the integrated web server the following information can be read out:

DC8-037-2, Edition 11.2020
12.7 IEC 61850
• 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 | Direc-
tories 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.
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 parameter-
ized with the parameter IEC61850 | Server | IED Name . This IED Name is only used for the ICD
file import (as of IEC 61850 Edition 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.

DC8-037-2, Edition 11.2020
12.7 IEC 61850
• 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 revi-
sion 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 automati-
cally by the SICAM TOOLBOX II is displayed for the relevant parameter blocks.
NOTE
i The "configRev" is the unambiguous identifier of the parameter status of a IEC 61850 device and for SICAM
RTUs components is listed for each Physical Device (all logical devices of a physical device have the same
revision).
NOTE
i 61850 devices of some manufacturers check that revision of the parameter status (configRev) imported
from the ICD-File for connected IEC 61850 devices with that parameter status used in the connected IEC
61850 device (configRev is read out and compared).
→ IEC 61850 devices of some manufacturers terminate the complete function if the configRev no longer
corresponds!
NOTE
i 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.
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 IEC 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.

DC8-037-2, Edition 11.2020
12.7 IEC 61850
Connection Information ("Connections")

On the web page Diagnosis | Connections the status information of the parameterized connections is
displayed.
Connection-specific status information:
• Station (SICAM RTUs internal station number)

is assigned to an IP address.
• IP Address
The field "IP Address" displays the IP address of the remote station parameterized in the parameters for
connection definitions . 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 imple-
mented in the remote station is displayed.
• Dir Ind. [Server only]

The field "Dir Ind." is only used for SICAM RTUs components with IEC 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 IEC
61850 station (remote station) is displayed.
• Dir ID [Server only]

The field "Dir ID" (Directory ID) is only used for SICAM RTUs components with IEC 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 IEC
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)

DC8-037-2, Edition 11.2020
12.7 IEC 61850
• 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 IEC 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 IEC 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, 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.
Named Variables Directory of the Station [Client only]
Via the web page Diagnosis | Connections | Req. Dir. (NV) of the IEC 61850 Client, the Named
Variables Directory of the IEC 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 Messwert- Erfassung
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.

DC8-037-2, Edition 11.2020
12.7 IEC 61850
The current states of the data attributes of the Named Variables ("Data Attribute Reference") can be read out
directly from the IEC 61850 remote station (Server) with "Read" via the web page in the IEC 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 IEC 61850 device cannot be deleted unintentionally.
File Directory of the Station [Client only]

On the web page Diagnosis | Connections | File Dir. the File Directory of the IEC 61850 remote
station (Server) can be displayed in the IEC 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 IEC 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.

DC8-037-2, Edition 11.2020
12.7 IEC 61850
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 IEC 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.

DC8-037-2, Edition 11.2020
12.7 IEC 61850
• 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 IEC 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
• 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.
• IEC 61850 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]
60870-5-101/104 format in receive direction is parameterized with the SICAM TOOLBOX II in the OPM 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.

DC8-037-2, Edition 11.2020
12.7 IEC 61850
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.
With incorrect IEC 61850 address an error message is displayed in the field "Error". The IEC 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.

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

DC8-037-2, Edition 11.2020
12.7 IEC 61850
Control Location [Client only]

On this web page the control locations set for the client are displayed. If the function "control location" is acti-
vated, 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 Transmis-
sion/Control Location".
Directories Server [Server only]

On this web page the directories created in the server are displayed.
The directories for the IEC 61850 Server are generated by the protocol element from the process-technical
parameters (=SIP message address conversion) for the IEC 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 IEC 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 directo-
ries is displayed.

DC8-037-2, Edition 11.2020
12.7 IEC 61850
• Directory ID
The field "Directory ID" (directory identification number) is only displayed for SICAM RTUs components
with IEC 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 IEC 61850
station (remote station) is displayed.
• Directory Info
The field "Directory Info" (Directory Information) is only displayed for SICAM RTUs components with IEC
61850 Server function.
By clicking the mouse button on "Show" in the field "Directory Info", detailed information of the IEC
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.
• 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 anal-
ysis.
Directory Server "Plain" [Server only]
On this web page the selected directory of the server is displayed in alphabetical order. The Plain format
displays the data in alphabetical order.
Directory-specific information:

DC8-037-2, Edition 11.2020
12.7 IEC 61850
• “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 IEC 61850 Server to one IEC
61850 Client.
For data in the direction IEC 61850 Server → IEC 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.
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 IEC
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 communica-
tion 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 parameter-
ized 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.

DC8-037-2, Edition 11.2020
12.7 IEC 61850
• 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.
GOOSE [Server only]

On this web page, details of the GOOSE header information are displayed. The datasets for the GOOSE applica-
tions 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.

DC8-037-2, Edition 11.2020
12.7 IEC 61850
• goID
In the field "goID" an unambiguous GOOSE identification reference is displayed. This identifier is unam-
biguous for each device and for each network and is also transmitted with GOOSE.
• dsRef
For every GOOSE application a specific dataset is created in the SICAM RTUs Server. In the field "dsRef" the
Dataset Reference per device is displayed.
• 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 trans-
mitted 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 trans-
mitted 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.
The structure of the GOOSE datasets is displayed for each GOOSE-Index (GOOSE application) as follows.
Example: "GOOSE Application Index-1,2,4"

DC8-037-2, Edition 11.2020
12.7 IEC 61850
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 parame-
ters 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".
Example: "GoCBRef" = MEAS/LLN0$GO$gcb01
→ GOOSE Control Block

DC8-037-2, Edition 11.2020
12.7 IEC 61850
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.
12.7.10.2 IEC 61850 Edition 2 [Client + Server]
A web server is integrated into the protocol firmware for internal diagnostic information. 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 (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 inter-
face of the automation unit.
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
Via the integrated web server the following information can be read out:

DC8-037-2, Edition 11.2020
12.7 IEC 61850
• 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)
• Load shedding control

– Parameters and values (Load Shedding | Settings)
– Display of the status information (Load Shedding| State )
• System-internal data for development specialists

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

DC8-037-2, Edition 11.2020
12.7 IEC 61850
• 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, SSE, IP address, Default gateway, Subnetmask, 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".
READY ……………………..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.
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 .
By clicking the mouse button on the IP address, via a link the web page of a web server possibly imple-
mented 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)

DC8-037-2, Edition 11.2020
12.7 IEC 61850
• Data [Client only]

The field "Data" is OK if all IEC 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 IEC 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.
Client - Named Variables Directory of the Station
Via this web page of the IEC 61850 Client, the Named Variables Directory of the IEC 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

DC8-037-2, Edition 11.2020
12.7 IEC 61850
The current states of the data attributes of the Named Variables ("Data Attribute Reference") can be read out
directly from the IEC 61850 remote station (Server) with Read via the web page in the IEC 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 at the bottom. Through the
readout, data in the IEC 61850 device cannot be deleted unintentionally.
Client - File Directory of the Station
On this web page the File Directory of the IEC 61850 remote station (Server) can be displayed in the IEC
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 IEC 61850 remote station.

DC8-037-2, Edition 11.2020
12.7 IEC 61850
Client - Routing Transmit, Client - Routing Receive

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.

DC8-037-2, Edition 11.2020
12.7 IEC 61850
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
60870 -5 -101/104 addresses (e.g. Mod.ctlVal from single commands).
• IEC61850 Address
• CDC
In this field the parameterized IEC 61850 Common Data Class of the data point is displayed.

DC8-037-2, Edition 11.2020
12.7 IEC 61850
• 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.
• 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.
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 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.


DC8-037-2, Edition 11.2020
12.7 IEC 61850
The display below describes the state of the last/current data transmission.
For details on the function “File Transfer” refer to section File Transfer (Disturbance Records).
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.



In this field the parameterized IEC 61850 address of the data point is displayed.
• 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.

DC8-037-2, Edition 11.2020
12.7 IEC 61850
Server - Routing Transmit, Server - Routing Receive

On the web page Server - Routing transmit all routing information generated for the protocol
element in transmit direction are displayed.
On the web page Server - Routing receive all routing information converted for the protocol element
in receive direction are displayed.
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

DC8-037-2, Edition 11.2020
12.7 IEC 61850
• 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
60870 5 101/104 addresses (e.g. Mod.ctlVal from single commands).

• CDC
In this field the parameterized IEC 61850 Common Data Class of the data point is displayed.
• Ctrltype
displayed.
• 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.
Server - Directory
On this web page, detailed information of the data model generated for the selected directory of the IEC
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.

DC8-037-2, Edition 11.2020
12.7 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.
Server - Directory plain view
On this web page the selected directory of the server is displayed in alphabetical order.

DC8-037-2, Edition 11.2020
12.7 IEC 61850
In the list "Datasets" all datasets generated for the selected server directory are displayed.
Datasets are only created for those data, that are to be transmitted from one IEC 61850 Server to one IEC
61850 Client. For data in the direction IEC 61850 Server → IEC 61850 Client, no data sets are created.
• 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.
Server - Directory tree view
On this web page, the selected server directory is displayed in hierarchically structured form.

DC8-037-2, Edition 11.2020
12.7 IEC 61850
Server - GOOSE
On this web page, details of the GOOSE header information are displayed. The datasets for the GOOSE applica-
tions 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
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.

DC8-037-2, Edition 11.2020
12.7 IEC 61850
• 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 unam-
biguous 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.
• 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.

DC8-037-2, Edition 11.2020
12.7 IEC 61850
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.

DC8-037-2, Edition 11.2020
12.7 IEC 61850
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.



In this field the parameterized IEC 61850 address of the data point is displayed.
• 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

DC8-037-2, Edition 11.2020
12.7 IEC 61850
Load Shedding - Settings

On this web page, the settings of the special function “Automatic Load Shedding” are displayed, if this is para-
meterized.
[sc_ETx5_load_shedding_05_q, 1, en_US]
In the list “Trip matrix enable signal“ the settings of the takeover information are displayed.
• No
In this field a consecutive number is displayed.

DC8-037-2, Edition 11.2020
12.7 IEC 61850
• TI,CASDU1, CASDU2, IOA1, IOA2, IOA3

In this field the type identification and 5-stage address according to IEC 60870-5-101/104 is displayed. ·
• TI_RI, CASDU1 RI, CASDU2 RI, IOA1 RI, IOA2 RI, IOA3 RI
In this field the type identification and 5-stage address according to IEC 60870-5-101/104 of the return
information is displayed.
In the list “Test mode” the settings of the test information are displayed.
• No
• TI,CASDU1, CASDU2, IOA1, IOA2, IOA3

In this field the type identification and 5-stage address according to IEC 60870-5-101/104 is displayed.
In the list “Trip matrix settings and feedback” the settings of the trip matrix for the load are displayed.
• No
• Load
In this field the number for the respective load is displayed.

• TI match, CASDU1 match, CASDU2 match, IOA1 match, IOA2 match, IOA3 match
information “load tripped through contingency trip” is displayed.
• TI trip, CASDU1 trip, CASDU2 trip, IOA1 trip, IOA2 trip, IOA3 trip
In this field the type identification and 5-stage address according to IEC 60870-5-101/104 of the trip to
the load in order to trip the circuit breaker is displayed.
• Trip test
In this field the trip to the load in order to trip the circuit breaker in test mode is displayed.
• Pulse
In this field the output time for the GOOSE information is displayed.

DC8-037-2, Edition 11.2020
12.7 IEC 61850
In the list “Contingency trip signals” the settings of the signals for the contingency trip are displayed.
• No
• Contingency
In this field the number for the respective contingency is displayed.


DC8-037-2, Edition 11.2020
12.7 IEC 61850
Load Shedding - State

On this web page, the last trips through the special function “Automatic Load Shedding” are displayed, if this is
parameterized.
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.
Special Function Wireshark

Upon problems with the communication via IEC 61850 it is necessary that a Wireshark recording will be
performed. It can be operated remotely via the web server of the affected firmware without having to discon-
nect a cable or a restart. A recording on site is not required.
The recording can be started for each parameterized station, if needed also the initialization procedure can be
recorded. The recorded data will be stored in a Wireshark compatible file which can be downloaded via the
web server.
[sc_Wireshark_01, 1, --_--]

DC8-037-2, Edition 11.2020
12.7 IEC 61850
Function in Wireshark:
[sc_Wireshark_02, 1, --_--]

DC8-037-2, Edition 11.2020
12.8 Modbus RTU
12.8 Modbus RTU
12.8.1 Introduction
The Modbus RTU protocol is a standardized serial transmission protocol for communication with remote
stations with multi-point traffic (master/slave principle; “Partyline”).
For CP-8000/CP-802x, the following protocol firmware for Modbus RTU is available:
MODMT2 CP-8000 Modbus RTU Master (incl. SICAM FCM integration)
CP-802x
MODST0 CP-8000 Modbus RTU (ASCII) Slave
CP-802x
The Modbus RTU protocol defines the data exchange of 16 bit register values or of coils (binary information)
between systems via a serial communication connection.
The Modbus RTU protocol is standardized by the user organization www.modbus.org.
The Modbus protocol was originally defined for serial transmission, later Modbus TCP was defined for the
transmission of data via LAN/WAN (Ethernet).
The message structure is very similar between “Modbus RTU” and “Modbus TCP”.
The protocol element MODMT2 in CP-8050 enables the serial communication of one component as master
station (= Master) with up to 100 remote terminal units (= Slaves) with the Modbus RTU protocol on a
common line.
The protocol element MODST0 in CP-8050 enables the serial communication of one component as remote
terminal unit (= Slave) with a master station (= Master) with the Modbus RTU protocol on a common line with
up to a maximum of 247 remote terminal units (Slaves).
In multi-point traffic the central station and the remote terminal units operate with a serial communication
protocol according to Modicon Modbus (RTU-Mode).
The supported functionality (interoperability) is determined in the chapter 12.8.7 Interoperability Modbus
RTU.
one or several remote terminal units over a communications link in a line or star configuration. The data traffic
is controlled by the master station.
An unambiguous station number in the range 1 - 247 is assigned to every remote terminal unit. The station
number "0" is used for the simultaneous addressing of all stations (= Broadcast-addressing). With Broadcast-
addressing no reply (Response Message) is transmitted from the Slaves to the Master.
NOTE
i Broadcast-addressing is supported by the Modbus RTU in CP-8000/CP-802x with restrictions !
A transmission of data can always only be initiated by the master station. A data transmission consists either
of a “Request-Response Sequence” (= Query/Response) to selectively addressed slaves or of a simultaneous
addressing of all connected remote terminal units (= Broadcast/No-Response).
Depending on the case of application the master station can transmit a further message immediately
following reception of a valid response message from a remote terminal unit or with lack of a response after a
configurable TIMEOUT.

DC8-037-2, Edition 11.2020
12.8 Modbus RTU
The requests (Read Registers/Read Coils) or data messages (Write Registers/Write Coils) provided for the
Modbus communication protocol are transmitted from the master station. Data from the remote terminal unit
to the master station can only be transmitted as a response to a request.
[dw_Modbus_RTU_config, 1, en_US]
Figure 12-4 Modbus RTU Configuration
In multi-point traffic an “unbalanced transmission procedure” is used. That means, that as primary station
(Master) the master station initiates all message transmissions, while as secondary stations (Slaves) the
remote terminal units 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.
12.8.2 Functions
Functions of the master station - Modbus TCP Master (MODMT2)

Communication of a central station with up to 100 substations.
• Serial communication according to Modicon MODBUS RTU Master (serial)
• MODBUS protocol with half duplex link transmission procedure

– MODBUS RTU Mode
• Max. connections (number of supported MODBUS Slaves): 100 267

– Max. number of SICAM FCMv2 devices per interface without SICAM FCMv2 parameter loading: 100
– Max. number of SICAM FCMv2 devices per interface with SICAM FCMv2 parameter loading: 5 to 100
(5 parameter sets for SICAM FCM devices; each parameter set either for single SICAM FCM device or
parameter set for group of SICAM FCM devices)
• Message Protection
– CRC16 + Parity (optional) “RTU-Mode”
• Network Configurations
– Multiple point-to-point configuration (separate interface for each single point-to-point configuration
required)
– Multipoint-star
– Data concentrator
267 This specification refers to the max. number of possible stations for MODBUS Master per communication interface. Due to perform-
ance and required response time, in most cases only a few stations are possible (Typically 20-30); The Modbus protocol itself defines
a max. possible number of stations of 247 stations per line.

DC8-037-2, Edition 11.2020
12.8 Modbus RTU
• MODBUS Slave Adresse 0 (Broadcast) 268
• MODBUS Slave address 1 to 247
• Physical Interface
– RS-232 – unbalanced interface according to V.24/V.28
– RS-485 – balanced interface according to V.11 269
– RS-422 - balanced interface according V.11 standard 269
– 50, 75, 100, 110, 134.5, 150, 200, 300, 600, 1050, 1200, 1800, 2000, 2400, 4800, 9600, 19200,
38400, 57600 Bit/s
• Byte Frame
– | 8N1, 8E1, 8O1 | 8N1.5, 8E1.5, 8O1.5 | 8N2, 8E2, 8O2 | 270
• Interoperability according to Chapter 12.8.7.1 Interoperability Modbus RTU Master
• MODBUS Register
– MODBUS Register “16 Bit”
– MODBUS register-addresses: 1 (0) bis 65535
– MODBUS register addressing - according Modbus standard (YES/NO) (selective station)
• MODBUS Funktions Codes 271

– 01 = READ COILS
– 02 = READ DISCRETE INPUTS
– 03 = READ HOLDING REGISTERS
– 04 = READ INPUT REGISTERS
– 05 = WRITE SINGLE COIL
– 06 = WRITE SINGLE REGISTER
– 15 = WRITE MULTIPLE COILS
– 16 = WRITE MULTIPLE REGISTERS
• MODBUS Exception Codes

– 01 = ILLEGAL FUNCTION
– 02 = ILLEGAL DATA ADDRESS
– 03 = ILLEGAL DATA VALUE
268 BROADCAST addressing is only restricted supported by master!

269 external converters (V.24/V.28 ↔ V.11) are required in some cases
270 Byte frame according Modbus Standard for RTU mode: 8E1 (1 start bit, 8 data bits, 1 parity bit „even parity“, 1 stop bit) For maximum
compatibility with other devices also odd parity and no parity, as well 1.5 stop bits and 2 stop bits is also supported. The use of no
parity requires 2 stop bits! In old configurations byte frame "8N2" (8 data bits, no parity, 2 stop bits) is used typically for Modbus RTU
mode.
271 in addition to the supported MODBUS function codes the supported data formats in the MODBUS registers are also relevant!

DC8-037-2, Edition 11.2020
12.8 Modbus RTU
• Data formats (MODBUS register)

– INT16 Signed Integer 16 Bit
– UINT16 Unsigned Integer 16 Bit
– INT32 (H/L) Signed Integer 32 Bit (HIGH before LOW)
– UINT32 (H/L) Unsigned Integer 32 Bit (HIGH before LOW)
– INT32 (L/H) Signed Integer 32 Bit (LOW before HIGH)
– UINT32 (L/H) Unsigned Integer 32 Bit (“LOW before HIGH“)
– FLOAT32 Short Floating Point (IEEE 754)
– FLOAT32 (swapped) Short Floating Point (IEEE 754) “Swapped”
– Bitstring of 16 Bit 272
– 1BIT SPI single-point information
– 2BIT DPI (1=off, 2=on) double-point information (OFF before ON) 272
– 2BIT DPI (1=on, 2=off) double-point information (ON before OFF) 272
– 3BIT/MCU 3 Bit Indication - Siemens MCU (Motor Control Unit) 272
– SC single command (1 Bit) 273
– SC (pulse) single command (pulse 1 Bit) 273
– DC1 double command (1 Bit) 273
– DC2 (pulse) double command (pulse 2 Bit) 273
– SC1n16R Single command - 1 of 16 (register) 273
– DC1n16R double command - 1 of 16 (register) 273
– DTx – Date + Time (free configurable) 273
– DTFCM Date and time (SICAM FCM) 273 274
• Supported IEC60870-5-101/104 Message Formats in “Command- or Control Direction” (Master transmit

direction | Slave receive direction)
– <TI:=30> ... Single-point information with time tag CP56Time2a
– <TI:=34> … Measured value, normalized value with time tag CP56Time2a (15 Bit + sign)
– <TI:=36> ... Measured value, short floating point number with time tag CP56Time2a
– <TI:=45> … Single command
– <TI:=46> … Double command
– <TI:=48> … Setpoint command, normalized value
– <TI:=49> ... Setpoint command, scaled value
– <TI:=50> ... Setpoint command, short floating point number
272 only in receive direction!

273 only in transmit direction!
274 time + date formats only in transmit direction for setting the time of the remote station. Data with time tagging is not supported
(except Alarm Panel)!

DC8-037-2, Edition 11.2020
12.8 Modbus RTU
• Supported IEC60870-5-101/104 Message Formats in “signaling or monitoring direction” (Master receive

direction | Slave transmit direction)
– <TI:=31> Double-point information with time tag CP56Time2a
– <TI:=33> Bitstring of 32 bits with time tag CP56Time2a
– <TI:=37> … Counter value with time tag CP56Time2a (31 Bit + sign with sequence number)
• General interrogation, substation interrogation
• Clock synchronization for selected MODBUS Slave Devices

– Clock synchronization - selectable for each MODBUS Slave
– Clock synchronization for SICAM FCM
– Clock synchronization for Modbus Slaves “free definable”

– 5 V power supply for connected external modem (via RS232 status line)

Protocol element return information
– Station status
– Station failure
– SICAM FCM Parameter loading (SICAM FCM V2.00, V2.10, V2.20, V2.30, V2.40, V2.50, V2.60,
V2.61, V3.10)
– SICAM FCM Firmware loading (SICAM FCM ≥ V2.00)
• Engineering
– SICAM TOOLBOX II + OPM II
– Web engineering
Functions of the substation - Modbus TCP Master (MODST0)

Communication of a substation with a central station.
• Serial communication according to Modicon MODBUS RTU Slave (serial)
• MODBUS protocol with half duplex link transmission procedure

– MODBUS RTU Mode
– MODBUS ASCII Mode
• Max. connections: 1 275
275 From the perspective of the remote terminal unit the max. number of stations per line is not relevant.

DC8-037-2, Edition 11.2020
12.8 Modbus RTU
• Message Protection
– CRC16 + Parity (optional) “RTU-Mode”
– LRC + Parity (optional) “ASCII-Mode”
• Network Configurations
– Multiple point-to-point configuration (separate interface for each single point-to-point configuration
required)
– Multipoint-star
– Data concentrator
• MODBUS Slave address 0 “broadcast“
• MODBUS Slave address 1 to 247
– RS-485 – balanced interface according to V.11 269
– RS-422 - balanced interface according V.11 standard 269
– 50, 75, 100, 110, 134.5, 150, 200, 300, 600, 1050, 1200, 1800, 2000, 2400, 4800, 9600, 19200
Bit/s
• Byte Frame
– MODBUS RTU Mode 270
| 8N1, 8E1, 8O1 | 8N1.5, 8E1.5, 8O1.5 | 8N2, 8E2, 8O2 |
– MODBUS ASCII Mode 276
| 7N1, 7E1, 7O1 | 7N1.5, 7E1.5, 7O1.5 | 7N2, 7E2, 7O2 |
• Interoperability according to Chapter 12.8.7.2 Interoperability Modbus RTU Slave
• MODBUS Register
MODBUS Register “16 Bit”
MODBUS register-addresses: 1 (0) bis 65535
Modbus register addressing – according Modbus standard (YES/NO) (global for all slaves)
276 Byte frame according Modbus Standard for RTU mode: 7E1 (1 start bit, 7 data bits, 1 parity bit (even parity), 1 stop bit) For maximum
compatibility with other devices also odd parity and no parity, as well 1.5 stop bits and 2 stop bits is also supported. The use of no
parity requires 2 stop bits! In old configurations byte frame "7N2" (7 data bits, no parity, 2 stop bits) is used typically for Modbus
ASCII mode.

DC8-037-2, Edition 11.2020
12.8 Modbus RTU
• MODBUS Funktions Codes 277

– 01 = READ COILS
– 08 = DIAGNOSTICS (SUB-Code 00-18,20) “Return Query Data” (LOOPBACK CHECK)
• MODBUS Exception Codes

– 02 = ILLEGAL DATA ADDRES
– 04 = SLAVE DEVICE FAILURE 278
• Data formats (MODBUS register)

– INT16 Signed Integer 16 Bit
– UINT16 Unsigned Integer 16 Bit
– INT32 (H/L) Signed Integer 32 Bit (HIGH before LOW)
– UINT32 (H/L) Unsigned Integer 32 Bit (HIGH before LOW)
– INT32 (L/H) Signed Integer 32 Bit (LOW before HIGH)
– UINT32 (L/H) Unsigned Integer 32 Bit (“LOW before HIGH“)
– FLOAT32 Short Floating Point (IEEE 754)
– FLOAT32 (swapped) Short Floating Point (IEEE 754) “Swapped”
– 32BIT/OMVZ OMV Counter Value Format 273
– 16BIT/H&B Hartmann & Braun measured value format (0 to 4000)
– 1BIT SPI single-point information
– SC single command (1 Bit) 272
– SC (pulse) single command (pulse 1 Bit)
– DC1 double command (1 Bit) 272
– DC1 (pulse) double command (pulse 1 Bit)
– Date and time (BCD) “OMV” 273 274
– Format-121: Date and time (BCD reverse) “OMV” 279 274
277 in addition to the supported MODBUS function codes the supported data formats in the MODBUS registers are also relevant!
278 only with activated system technical parameter for data points marked faulty!
279 only in transmit direction

DC8-037-2, Edition 11.2020
12.8 Modbus RTU
• Supported IEC60870-5-101/104 Message Formats in “Command- or Control Direction”

(MASTER transmit direction| SLAVE receive direction)
• Supported IEC60870-5-101/104 Message Formats in “Signaling- or Monitoring Direction”

(MASTER receive direction| SLAVE transmit direction)
– <TI:=31> ... Double-point information with time tag CP56Time2a
• Clock synchronization for selected MODBUS Slave Devices

– Clock synchronization for OMV

– 5 V power supply for connected external modem (via RS232 status line)
• Engineering
– SICAM TOOLBOX II + OPM II
– Web engineering
Restrictions
• Real-time data via Modbus RTU are not supported!
• Emulation of IEC 60870-5-101/-104 ACTTERM for commands and setpoint values are not supported!
• Listening mode is not supported by Modbus RTU!

DC8-037-2, Edition 11.2020
12.8 Modbus RTU
• Redundancy is only partially supported!
• Modbus Function Codes / Exception Codes are not fully supported!
• Only selective data formats in the Modbus registers are supported!

– The Modbus protocol itself does not define any data formats in the Modbus registers.
– The supported Modbus data formats are described in chapter 12.8.8 Modbus data formats .
NOTE
i The Modbus RTU protocol in SICAM A8000 does not support full functionality according to Modbus RTU.
The Modbus protocol defines only the transmission of coils and 16 Bit register values, but not the data
formats in the Modbus registers!
The Modbus RTU protocol in SICAM A8000 supports many of the commonly used data formats.
For the coupling of devices with Modbus RTU protocol it is always necessary to check first whether the
required functionality and the required data formats are supported in the central station and in the substa-
tion!
ment.
optional DTE
Unbalanced interchange circuit X2 RXD, TXD, CTS280, RTS, DCD, DTR,
(2-wire)/ RS-422 (4-wire) asynchronous (CM-0819) 281) DSR/VCC, GND (to CM-08x9)
Unbalanced interchange X6282 RXD, TXD, CTS, RTS, DCD, DTR,
(2-wire)/RS-422 (4-wire) asynchronous TXD+, TXD-, RXD+, RXD- (4-wire)
NOTE


DC8-037-2, Edition 11.2020
12.8 Modbus RTU
Own Station (Central Station – Modbus RTU Master)

SICAM A8000 Series CP-8000/CPC80 MODMT2
CP-8021/CPC80
CP-8022/CPC80
Remote Station (Substation – Modbus RTU Slave)

SICAM A8000 Series CP-8000/CPC80 MODST0
CP-8021/CPC80
CP-8022/CPC80
SICAM A8000 Series CP-8050/CPCI85 MODSI0
SICAM AK 3 CP-2016/CPCX26 SM-2551/MODSA0
CP-2019/PCCX26 SM-0551/MODSA0
Legacy systems CP-20xx SM-2551/MODSA0
(SICAM AK, SICAM TM, CP-60xx SM-0551/MODSA0
SICAM BC, SICAM EMIC) CP-50xx MODST0
12.8.7.1 Interoperability
Modbus RTU Master
Modbus RTU Master
Own Station (Substation – Modbus RTU Slave)

SICAM A8000 Series CP-8000/CPC80 MODST0
CP-8021/CPC80
CP-8022/CPC80
Remote Station (Central station – Modbus RTU Master)

SICAM A8000 Series CP-8000/CPC80 MODMT2
CP-8021/CPC80
CP-8022/CPC80
SICAM A8000 Series CP-8050/CPCI85 MODMI0
SICAM AK 3 CP-2016/CPCX26 SM-2551/MODMA0
CP-2019/PCCX26 SM-0551/MODMA0
Legacy systems CP-20xx SM-2551/MODMA0
(SICAM AK, SICAM TM, CP-60xx SM-0551/MODMA0
SICAM BC, SICAM EMIC) CP-50xx MODMT2
Siemens devices – – Interoperability according
to 12.8.7.2 Interopera-
bility Modbus RTU Slave
Third-party system – – Interoperability according
bility Modbus RTU Slave

DC8-037-2, Edition 11.2020
12.8 Modbus RTU
12.8.5 Communication according to Modbus RTU
Overview
The Modbus protocol defines the data exchange of 16 bit register values or of coils (binary information)
between systems.
Message formats for Modbus “serial”:
• RTU Mode
The message format on the line is “determined by agreement”. For the communication with Modbus all partic-
ipants must use the same message format.
With Modbus "serial" the message protection takes place by means of the CRC/LRC (in ASCII mode by the LRC)
at the end of the message and optionally with the Parity-Bit for each byte in the message.
Structure of the Message
[dw_modbus_serial_message, 1, --_--]
Figure 12-5 Modbus serial message structure
Length Note
Field [Bytes] Description
Slave ID 1 Modbus Slave Address 1 to 247 (0 = Broadcast)
FCode 1 Modbus Function Code
Data n Data bytes max. 253 Bytes
CRC 2 Message protection RTU Mode 16 Bit value
LRC 1 Message protection ASCII Mode 8 Bit binary value
Used Interface Lines (Modbus “serial”)

With RS-232 following V.24 interface lines are used:
Number of the interface Designation Use
line
TxD <103> TRANSMIT DATA Transmit data
RxD <104> RECEIVE DATA Receive data
GND <102> SIGNAL GROUND
RTS <105> REQUEST TO SEND Switching on the transmit signal level of
the transmission facility
DCD <109> DATA CARRIER Detecting the receive signal level of the
DETECT transmission facility
If Modbus devices with RS-485 are to be connected to the serial RS-232 interface, then external converters
must also be used!
Byte Frame (Modbus “serial”)

The byte frame can be parameterized (system technical parameter).
This byte frame contains:
1 Start bit
7/8 Data bits (RTU-Mode: 8, ASCII-Mode: 7)
1/NO parity bit (even, odd, no parity)
1/2 Stop bits

DC8-037-2, Edition 11.2020
12.8 Modbus RTU
Because of start- and stop bits of the byte frame the synchronization of the receiver happens new with each
byte.
[dw_modbus_rtu_ascii_byte_frame, 1, en_US]
Figure 12-6 Modbus serial byte frame
Message transmission in Modbus RTU Mode

In RTU Mode all items of information are transmitted in 8 Bit binary encoded characters.
• Modbus message must be transmitted as a continuous stream (without gaps between the bytes).
• The pause time (“silent interval”) between two Modbus messages must be at least 3.5 UART characters.
For Modbus protocol firmware in SICAM RTUs the minimum required “silent interval“ will be generated by
protocol firmware automatically or must be set by user with the parameter Common settings | free
defineable interface modem | Pause time "time base" (tp).
• If a silent interval of more than 1.5 UART character times occurs between 2 UART characters of a Modbus
message, the message frame is declared as incomplete and will be discarded by the receiver.
Note:
The message gap monitoring (“silent interval between two characters of a Modbus message frame”) is set
with the parameter Advanced parameters | Monitoring times | Character monitoring
time.
With message interruption the receive processing in progress is aborted and the message is discarded.
Message transmission in Modbus ASCII Mode

In ASCII Mode every item of information to be transmitted (8 Bit) is split into 2 parts and transmitted as 2 ASCII
signs (hexadecimal). As a result, in ASCII Mode twice as many characters are required for a message transmis-
sion as in RTU Mode
In ASCII Mode the message is initiated with the ASCII character “:”. The end of the message is indicated with
<CR> <LF>.
Modbus Slave Address

For Modbus “serial”, the individual slave address (“Slave Node Address”) is set in the range 1 to 247. The slave
address "0" is defined as a BROADCAST address.
Limitation: BROADCAST addressing is not supported in SICAM A8000!

DC8-037-2, Edition 11.2020
12.8 Modbus RTU
Modbus Function Codes (FC)

The Modbus message formats are differentiated by the Modbus Function Code (FC).
Supported Modbus function codes:
Function code Designation Description
01 READ COILS Read binary marker
02 READ DISCRETE INPUTS Read binary inputs
03 READ HOLDING REGISTERS Read internal register
04 READ INPUT REGISTERS Read input register
05 WRITE SINGLE COIL Write binary outputs
06 WRITE SINGLE REGISTER Write register
08 DIAGNOSTICS 283
15 WRITE MULTIPLE COILS Write binary outputs
16 WRITE MULTIPLE REGISTERS Write register
Modbus Address (Register/Coils)

Addressing according to Modbus for register values:
• One Modbus register address addresses one 16 Bit register
• The Modbus register address begins with 1 (or 0)
• For each Modbus register the MSB is transmitted first and then the LSB
• Address range for Modbus register address: (0),1 to 65535

With the protocol firmware for SICAM A8000 the address range for Modbus registers is organized sepa-
rately per Modbus function code and limited only by free internal memory. Some third-party systems
have only one common address range, common for all Modbus function codes – thereby an offset is
defined per function code for the Modbus register address.
Addressing according to Modbus for “Coils”:
• One Modbus coil address addresses one coil “Binary states” (ON/OFF)
• The Modbus coil address begins with 1 (or 0)
• Address range for coils: (0),1 to 65535

According to the Modbus definition, the addressing of the Modbus registers begins from address 1, but on the
line the address 0 is transmitted for Modbus register address 1.
Modbus Register Addressing (typical):
Modbus Function Modbus Modbus
Function code Register Address Register Address
(address list) [dec] (in message) [dec]
01 READ COILS 00001 to 10000 0000 to 9999
02 READ DISCRETE INPUTS 10001 to 20000 0000 to 9999
03 READ HOLDING REGISTERS 40001 to 50000 0000 to 9999
04 READ INPUT REGISTERS 30001 to 40000 0000 to 9999
05 WRITE SINGLE COIL 00001 to 10000 0000 to 9999
06 WRITE SINGLE REGISTER 40001 to 50000 0000 to 9999
15 WRITE MULTIPLE COILS 00001 to 10000 0000 to 9999
16 WRITE MULTIPLE REGISTERS 40001 to 50000 0000 to 9999
283 only Sub-Function 0000 .. Return Query Data (LOOPBACK CHECK) is supported!

DC8-037-2, Edition 11.2020
12.8 Modbus RTU
NOTE
i The addressing of the Modbus registers is implemented differently depending on manufacturer and must
be looked up in the device descriptions!
Some manufacturers also specify the Modbus register address on the line in the address list!
Deviating from the definition for the Modbus protocol, some remote terminal units use the Modbus register
start address in the Modbus message on the line starting from 1 instead of starting from 0.
The addressing according to Modbus standard can be set in the parameters of the Station definition in
the field Addressing MODBUS Standard per station.
Example:
Modbus Address in Message
Modbus Address Addressing Addressing
Modbus Standard = <yes> Modbus Standard = <no>
1 0 1
75 74 75
1000 999 1000
1374 1373 1374
Modbus Data (Register/Coils)

The Modbus data essentially contain the contents of the Modbus registers or the contents of the Modbus
Coils.
The supported Modbus data formats are described in chapter 12.8.8 Modbus data formats, 12.8.7.1 Interoper-
ability Modbus RTU Master and 12.8.7.2 Interoperability Modbus RTU Slave.
The Modbus data format is defined for each data point in the message conversion at the protocol element.
Modbus REQUEST or RESPONSE messages typically contain slave address, function code, coil / register address,
number of bytes and data.
The exact Modbus message structure is documented for each function code in the section Modbus Request /
Response Services.
NOTE
i The Modbus protocol does not define the data formats in the Modbus registers!
The addressing of the Modbus registers is implemented differently depending on manufacturer and must
Message Protection
In the case of Modbus RTU, the message protection is carried out by a LRC or CRC.
at the message end and optionally by one parity bit per message byte.
Modbus Request/Response Services

For the supported Modbus function codes, the message formats are shown schematically in the following
description for Modbus RTU.

DC8-037-2, Edition 11.2020
12.8 Modbus RTU

Function- Designation Description
code
READ COILS, READ DISCRETE INPUTS [FC = 01, 02]

In the query message of the master station (Modbus RTU Master) the starting address and the number of data
points to be transmitted is specified.
Station address [Slave Address] 1 to 247, (BROADCAST not supported)
Function code [Function Code] 01 (READ COILS)
02 (READ DISCRETE INPUTS)
Start address [Starting Address] 0 to 65535
Number of queried data points 1 to 127
Byte count [Byte Count] 1 to 16
Data [Data Coil Status] 8 states (binary information) per byte
Request (Query Message, Read Request)

Example: Request of Bits 20 to 56 from the slave 17 with function code 01 or 02.
Field Name Example Example Description
[HEX] [DEC]
Slave Address 11 17
Function Code 01 / 02 1/2
Starting Address Hi 00 0
Starting Address Lo 13 19
Number of Points Hi 00 0
Number of Points Lo 25 37
Error Check (LRC or CRC) xx,xx xx,xx
Response (Response Message)

Example: Response to the request of Bits 20 to 56 from the slave 17 with function code 01 or 02.
[HEX] [DEC]
Slave Address 11 17
Byte Count 05 5
Data (Coils 27 to 20) CD 205 1100 1101
Data (Coils 35 to 28) 6B 107 0110 1011
Data (Coils 43 to 36) B2 178 1011 0010
Data (Coils 51 to 44) 0E 14 0000 1110
Data (Coils 56 to 52) 1B 27 0001 1011

DC8-037-2, Edition 11.2020
12.8 Modbus RTU
In the response message each binary information is transmitted with 1 Bit. (0 = binary information OFF; 1 =
binary information ON)
The number of data points requested refers to the individual items of binary information. The least significant
bit in the 1st data byte contains the status of the addressed binary information.
READ HOLDING REGISTERS / READ INPUT REGISTERS [FC = 03, 04]

In the query message of the master station (Modbus RTU Master) the starting address and the number of data
points to be transmitted is specified.
Function code [Function Code] 03 (READ HOLDING REGISTERS)
04 (READ INPUT REGISTERS)

Example: Request of Register 108 to 110 from the slave 17 with function code 03 or 04.
[HEX] [DEC]
Slave Address 11 17
Starting Address Lo 6B 107

Example: Response to the request of the Register 108 to 110 from the slave 17 with function code 03
or 04.
[HEX] [DEC]
Slave Address 11 17
Byte Count 06 6
Data Hi (Register 108) 02 2 0000 0010
Data Lo (Register 108) 2B 43 0010 1011
Data Hi (Register 109) 00 0 0000 0000
Data Lo (Register 109) 00 0 0000 0000
Data Hi (Register 110) 00 0 0000 0000
Data Lo (Register 110) 64 100 0110 0100
WRITE SINGLE COIL [FC = 05]

Binary information, commands from the master station are only transmitted to the remote terminal units
(Slave) as “single point information”. The query message contains the data point address and the state.
Function code [Function Code] 05 (WRITE SINGLE COIL)

DC8-037-2, Edition 11.2020
12.8 Modbus RTU
Data point address [Coil Address] 0 to 65535

Status [WRITE Data] 0x00 = OFF; 0xFF = ON
Write (Write Request)

Example: Writing of the address 173 in slave 17 with function code 05.
[HEX] [DEC]
Slave Address 11 17
Function Code 05 05
Coil Address Hi 00 00
Coil Address Lo AC 172
WRITE Data Hi FF 255 ON
WRITE Data Lo 00 00

Example: Response to the writing of the address 173 in slave 17 with function code 05.
[HEX] [DEC]
Slave Address 11 17
Function Code 05 5
WRITE Data Lo 00 0
With station-selective addressing the content of the query message is sent back by the Slave station as
response to the master station.
WRITE SINGLE REGISTER [FC = 06]

Measured values and setpoint values are transmitted from the master station (Modbus RTU Master) to the
slave stations with the message WRITE SINGLE REGISTER. The query message contains the data point address
and the state. A maximum of 1 value is transmitted per message.
Function code [Function Code] 06 (WRITE SINGLE REGISTER)
Data point address [Register Address] 0 to 65535

Example: Write the value 0003 into the register 0x0002 of the slave station 17 with function code 06.
[HEX] [DEC]
Slave Address 11 17
Function Code 06 6
Register Address Hi 00 0
Register Address Lo 01 1
Preset Data Hi 00 0
Preset Data Lo 03 3

DC8-037-2, Edition 11.2020
12.8 Modbus RTU

Example: Response to writing the value 0003 into the register 0x0002 of the slave station 17 with func-
tion code 06.
[HEX] [DEC]
Slave Address 11 17
Function Code 06 6
Preset Data Hi 00 0
Preset Data Lo 03 3
NOTE
i Modbus RTU (Master, Slave) in SICAM A8000 does not support double register values (such as: FLOAT32,
INT32, UINT32,...) with function code = 06 "WRITE SINGLE REGISTER"!
DIAGNOSTICS [FC = 08]

The master station can perform a station-selective diagnostic function of the remote terminal unit (Slave). The
diagnostic function is specified by the Sub-Function. The master station function in SICAM RTUs use FC=8
(DIAGNOSTICS/LOOPBACK CHECK) optionally only in the redundancy state “Passive” for monitoring communi-
cation to remote terminal units.
Sub function 0000: RETURN QUERY DATA

Function code [Function Code] 08 (DIAGNOSTICS)
Sub function [Sub-Function] 00 (RETURN QUERY DATA) (= LOOPBACK CHECK)
Request (Query Message)

Example: Request RETURN QUERY DATA to the remote terminal 17 with function code 08.
[HEX] [DEC]
Slave Address 11 17
Function Code 08 8
Subfunction Hi 00 0
Subfunction Lo 00 0
Data Hi xx xx
Data Lo xx xx

DC8-037-2, Edition 11.2020
12.8 Modbus RTU

Example: Answer to RETURN QUERY DATA from the remote terminal 17 with function code 08.
[HEX] [DEC]
Slave Address 11 17
Function Code 08 8
Subfunction Hi 00 0
Subfunction Lo 00 0
Data Hi xx xx
Data Lo xx xx
WRITE MULTIPLE COILS [FC = 15]

Multiple binary information / command states can be transmitted from the master station (Modbus RTU
Master) to the remote terminal units (Slave) with one message. Specified in the query message is the 1st data
point address, the number of coils to be written and the status of every individual coil.
(Coil 1 is addressed with "0").
Function code [Function Code] 15 (WRITE MULTIPLE COILS)
Number of Coils [Quantity of Coils] 1
Restriction with Modbus RTU Master:
With FC = 15 only one coil can be transmitted!
Status [WRITE Data] 0 = OFF; 1 = ON (1 Bit per coil state)

Example: Write 10 coils with the data 0xCD01 from coil address 20 in the slave 17 with function code
15.
[HEX] [DEC]
Slave Address 11 17
Function Code 0F 15
Coil Address Lo 13 19
Quantity of Coils Hi 00 0
Quantity of Coils Lo 0A 10
Byte Count 02 2
WRITE Data Hi (Coils 27-20) CD 205
WRITE Data Lo (Coils 29-28) 01 1

Error Check LRC or (CRC) xx,xx xx,xx

Example: Response for write request of 10 coils with the data 0xCD01 from coil address 20 in the slave
17 with function code 15.
[HEX] [DEC]
Slave Address 11 17
Function Code 0F 15

DC8-037-2, Edition 11.2020
12.8 Modbus RTU

Example: Response for write request of 10 coils with the data 0xCD01 from coil address 20 in the slave
17 with function code 15.
[HEX] [DEC]
WRITE MULTIPLE REGISTERS [FC = 16]

Multiple consecutive 16 bit register values can be transmitted from the master station (Modbus RTU Master) to
the remote terminal units (Slaves) with one message. Specified in the query message is the 1st Data point
address (Number of location), the number of registers to be written and the register status.
Station address [Slave Address] 1 to 247 (BROADCAST only with time synchronization)
Function code [Function Code] 16 (WRITE MULTIPLE REGISTERS)
Number of registers [No. of Regis- 1 to 2
ters] Restriction with Modbus RTU Master:
With FC=16 only 1 value can be transmitted (e.g. 1 Register with
INT16/UINT16 or 2 Register with Float, INT32/UINT32).
Exception: With time synchronization via Modbus, all required regis-
ters are transmitted in one message with FC = 16.

Example: Write 2 registers in slave 17 with function code 16 from register address 0x0002 with 00 0A
and 01 02.
[HEX] [DEC]
Slave Address 11 17
Function Code 10 16
Number of Registers Hi 00 0
Number of Registers Lo 02 2
Byte Count 04 4
Data Hi 00 0
Data Lo 0A 10
Data Hi 01 1
Data Lo 02 2

DC8-037-2, Edition 11.2020
12.8 Modbus RTU

Example: Respones to writing 2 registers in slave 17 with 00 0A and 01 0" from register address
0x0002.
[HEX] [DEC]
Slave Address 11 17
Function Code 10 16
Exception Response
If a slave station has not implemented the query data from the master station or the queried data is not avail-
able, an exception code (EXCEPTION Response) is transmitted instead of the data (Response Message).
Supported Modbus Exception Codes:
EXCEPTION Designation Description MODMT2 MODST0
01 ILLEGAL FUNCTION Function code not implemented ✓ ✓
02 ILLEGAL DATA ADDRESS Data point not available ✓ ✓
03 ILLEGAL DATA VALUE Illegal data ✓ -
04 Slave DEVICE FAILURE An error has occurred during the ✓ ✓ 284
request
05 ACKNOWLEDGE The remote terminal unit ✓ -
acknowledges, but cannot reply
to the request immediately
06 Slave DEVICE BUSY The slave station is busy ✓ -
07 NAK-NEGATIVE ACKNOWLEDGE Function cannot be executed ✓ -
08 MEMORY PARITY ERROR Parity error detected in memory ✓ -
The Modbus master accepts every exception response (the exception code will not be checked in detail). On
reception of exception response the requested data will be marked as not topical.
If the request of the master is answered with an Exception Response, the
NT-bit is set SICAM A8000 internal for these data and distributed further.
12.8.6.1 Overview
Data in transmit direction are transferred from the basic system element to the protocol element in SICAM
A8000 internal IEC 60870-5-101/104 (without 101/104 blocking) format. The conversion of the data formats
IEC 60870-5-101/104 ↔ Modbus RTU is performed by the protocol element. The transmission of the data
towards the Modbus RTU is controlled by the protocol element.
Data in receive direction are converted by the protocol element from the Modbus RTU format → SICAM A8000
internal IEC 60870-5-101/104 format and transferred to the basic system element (no 101/104 blocking). The
transmission of the data on the Modbus RTU is controlled by the protocol element.
The conversion of the SICAM A8000 internal IEC 60870-5-101/104 ↔ Modbus RTU data format and the
conversion of the address information are called message conversion.
284 only with activated system technical parameter for data points marked faulty

DC8-037-2, Edition 11.2020
12.8 Modbus RTU
The parameterization of the conversion from SICAM A8000 internal IEC 60870-5-101/104 ↔ Modbus RTU
(including address and data format) is to be done with SICAM TOOLBOX II (OPM) using "SIP Message Address
Conversion".
Supported processing types for message conversion:
Data Direction Category MODMT MODST0

2
Binary information Receive direction firmware /Rec_binary_information ✓ ✓
Commands Receive direction firmware /Rec_command ✓
Measured values Receive direction firmware /Rec_measured value ✓
Measured values Receive direction firmware /Rec_Value ✓
Setpoint values Receive direction firmware /Rec_Value ✓
Integrated totals Receive direction firmware /Rec_counter_value ✓ ✓
Binary information Transmit direction firmware /Trans_binary_information ✓
Binary information Transmit direction firmware /Trans_binary ✓
Commands Transmit direction firmware /Trans_binary ✓
Commands Transmit direction firmware /Trans_command ✓
Measured values Transmit direction firmware /Trans_value ✓
Measured values Transmit direction firmware /Trans_measured value ✓
Setpoint values Transmit direction firmware /Trans_value ✓
Setpoint values Transmit direction firmware /Trans_setpoint_command ✓
Integrated totals Transmit direction firmware /Trans_counter_value ✓
Time synchroniza- Transmit direction firmware /Trans_timesynchronisation ✓
tion
General description of the parameters and properties (valid for each type of processing):
Parameters
MODBUS_Station Addresse of the Modbus Slave (SICAM A8000 internal):
0 to 99
Note:
This Modbus station number is only used internally by SICAM A8000 for telegram
conversion and internal system functions. This Modbus station number is not trans-
mitted on the line!
MODBUS_Address Modbus Address (Coil- or Register Address):
0 to 65535
Note:
The Modbus address (= coil or register address) which is specified in the device descrip-
tions in the Register-MAPs is always parameterized.
According to the Modbus standard, the Modbus register address on the line is always
transmitted with offset = -1.
Example: parametrized Modbus Register Address = 0001
→ Modbus Register Address = 0000 on the line
Some device manufacturers do not always adhere to the standard on this point and
require "parameterized Modbus address" = "Modbus address on the line"
In the parameters of the connection definition the Modbus addressing on the line per
Modbus station can be set.
– Addressing Modbus Standard = YES (=Default)
– Addressing Modbus Standard = NO

DC8-037-2, Edition 11.2020
12.8 Modbus RTU
12.8.6.2 MASTER: Telegram Conversion in Transmit Direction (Master → Slave)

Telegram conversion in transmit direction: IEC 60870-5-101/104 → Modbus RTU
SICAM A8000: IEC 60870-5-101/104 → Modbus RTU Format
Type ID Designation FC Note
<TI:=30> single-point indication with 05, 15 -
CP56Time2a time tag
<TI:=34> Measured value, normalized value 06, 16 -
with time marker CP56Time2a
<TI:=35> Measured value, scaled value with 06, 16 -
time marker CP56Time2a
<TI:=36> Measured value, short floating-point 06, 16 -
number with time marker
CP56Time2a
<TI:=45> Single command 05, 06, 15 -
<TI:=46> Double command 05, 06, 15 -
<TI:=48> Setpoint adjusting command, 06, 16 -
normalized value
<TI:=49> Set point command, scaled value 06, 16 -
<TI:=50> Set point command, short floating 06, 16 -
point number
- - 08 DIAGNOSTICS 285
- GI system telegram 286 - -
- Counter interrogation (internally - -
generated) (only used internally in
PRE)
<TI:=45> Single command “time synchroniza- 16 -
tion” (internal protocol)
Modbus function codes (FC):

05 .. WRITE SINGLE COIL
06 .. WRITE SINGLE REGISTER
08 .. DIAGNOSTICS
15 .. WRITE MULTIPLE COILS
16 .. WRITE MULTIPLE REGISTERS
Commands
The address and telegram conversion for commands in the transmit direction are parameterized using the
SICAM Device Manager with the “signals” function or using SICAM TOOLBOX II, OPM II or for engineering via
SICAM WEB with the transmit detailed routing parameters.
285 is only transmitted by the SICAM A8000 master station in the “passive” redundancy status for monitoring failed substations (only
subfunction 0000 .. RETURN QUERY DATA = LOOPBACK CHECK). This telegram is only mirrored by the substation.
286 The Modbus protocol does not define a general interrogation. In the case of SICAM A8000 internal general interrogation, the data
that has been queried by the master station is forwarded to the base system element at the next query with the cause of transmis-
sion COT=20 (queried via station interrogation).

DC8-037-2, Edition 11.2020
12.8 Modbus RTU
Parameter category:
firmware /Trans_command
Parameter
• <TI:=45> .. Single command

• <TI:=46> .. Double command
CASDU, IOA SICAM A8000 internal IEC 60870-5-101/104 message address
Transmit priority The transmit priority can be used to set how each data point is supposed to be
transmitted.
• Spontaneous
Command_type_(MODM) Supported command types:
• Pulse command
• Persistent command
• Command - 1 of 16 (register)

DC8-037-2, Edition 11.2020
12.8 Modbus RTU
Parameter
Command_state_MODM Command status:
• unused
• OFF
• ON
Station number Modbus station number on the line:
• 1 to 247
Function_Code Supported Modbus function codes:
• FC = 05 .. WRITE SINGLE COIL

• FC = 06 .. WRITE SINGLE REGISTER
• FC = 15 .. WRITE MULTIPLE COILS [max. 1 coil available]
[Only 1 coil address is used for a double command]
Mod_Addr Modbus address:
• 0 to 65535
(Address 0 is not available for query mode according to Modicon!)
Mod_Bit_No Modbus bit number: [only for Command_type_(MODM) = Command - 1 out
of 16 (register)]
• 0 [for Command_Type_(MODM) = Pulse command/persistent

command]
• 0 to 14 [only for a double command]
• 0 to 15 [only for a single command]
Supported data formats
Format Modbus data format IEC 60870-5-101/104 data

format (TI)
SC Single command (1 bit) 45
SC (pulse) Single pulse command (1 bit) 45
DC1 Double command (1 bit) 46
DC2 (pulse) Double command “pulse” (2-bit) 46
SC1n16R Single command - 1 out of 16 (register) 45
DC1n16R Double command - 1 out of 16 (register) 46
NOTE
i As Modbus protocol does not define how data in coils/registers are represented, the Modbus format must
be specified for the telegram conversion. For supported Modbus data formats, see 12.8.8 Modbus data
formats.
Control location / control location check

The “control location” function is used to ensure that commands are only transmitted from authorized sources.
If the function is activated, commands are only transmitted from the protocol element to the remote partner if
the control location (originator address) has been released.

DC8-037-2, Edition 11.2020
12.8 Modbus RTU
Command output time for single/double commands

Commands can be transmitted on the Modbus as pulses (1 or 2 bits). The protocol element maps the
command output as a pulse to 1 or 2 coil addresses of the Modbus slave with the associated command output
time.
The pulse duration for commands with command qualifier = <0> “no additional definition” can be set on the
protocol element with the system parameter [PRE] | Advanced parameters | Command output
times | Commands without an identifier (sec).
The pulse duration for commands with a command qualifier = <1> “short command execution time” must be
set on the protocol element with the system parameter [PRE] | Advanced parameters | Command
output times | Commands with a short output time (sek).
The pulse duration for commands with a command qualifier = <2> “long command execution time” must be
set on the protocol element with the system parameter [PRE] | Advanced parameters | Command
output times | Commands with long output time (sec).
Max. 10 commands (single-, double-commands) can be active at the same time.
SC single command
The ON status as a coil = ON and the OFF status as a coil = OFF is transmitted with the same parameterized
Modbus address for a single command.
The command output time is not evaluated.
Modbus data format Command Status Command output 1 bit as a
coil
SC SCS = ON
x ... Command = ON
SCS = OFF
x ... Command = OFF
Note: The parameter Command_state_MODM must be set to unused.

SC single command (pulse)
A single command with command state SCS= ON is transmitted on the Modbus on the parameterized coil
address “n” as a pulse with the set command output time. The SCS = OFF command status is not evaluated. A
pulse command with Modbus function code = 6 (WRITE SINGLE REGISTER) is not supported!
The command will be terminated automatically after the command output duration has timed out.
Modbus data format Command status Command output 1 bit as a
coil
SC (pulse) SCS = ON
tp ... Command output time

(pulse duration)
x ... Command = ON
SCS = OFF The OFF state is not evaluated!
If a new command is triggered for sending the with same IEC 60870-5-101/104 address while a pulse output
is in progress, an additional pulse command output is also started for the pulse output that is in progress. The
pulse command is terminated once the remaining shorter command output time has elapsed.
Note: The parameter Command_status_MODM must be set to unused for single commands!

DC8-037-2, Edition 11.2020
12.8 Modbus RTU
DC double command
The ON status as a coil = ON and the OFF status as a coil = OFF is transmitted with the same parameterized
Modbus address for a double command.
Modbus data format Command status Command output 2 bit as a
coil
DC DCS = ON
x ... Command = ON
DCS = OFF
x ... Command = OFF

DC DCS = ON
= OFF
x ... Command = ON
DCS = OFF
x ... Command = OFF
Note: The parameter Command_state_MODM must be set to unused.
Double command DC (pulse)

A double command with the command status DCS = ON/OFF is issued on Modbus on the parameterized coil
address “n” or “n+1” as a pulse with the set command output time.
The command will be terminated automatically after the command output duration has timed out.
coil
DC (pulse) DCS = ON
command_status_MO
DM = ON

(pulse duration)
x ... Command = ON
DCS = OFF

(pulse duration)
x ... Command = OFF

DC8-037-2, Edition 11.2020
12.8 Modbus RTU

coil
DC (pulse) DCS = ON
command_status_MO
DM = OFF

(pulse duration)
x ... Command = ON
DCS = OFF

(pulse duration)
x ... Command = OFF
If a new command is initiated for sending with the same IEC 60870-5-101/104 address during a pulse output
in progress, an additional pulse command output is started.
The pulse command is terminated once the remaining shorter command output time has elapsed.
Single command - 1 out of 16 (register)

Up to 16 single commands (or mixed with double commands) can be located in the same Modbus register,
but only one command is active at the same time (“1 out of n”). A single command will be converted to 1 bit
(Mod_Bit_No) in the Modbus register. All the bits in the Modbus register are transmitted with 0!
Modbus data format Command Status Command output 1 bit in the
Modbus register
Command - 1 of 16 SCS = ON
(register)
x ... Command = ON
SCS = OFF
x ... Command = OFF
Double command - 1 out of 16 (register)

Up to 8 double commands (or mixed with single commands) can be located in the same Modbus register but
only one command will be active at the same time (“1 out of n”). A double command is always converted to 2
bit in the same Modbus register, where the 1st bit with Mod_Bit_No and the 2nd bit is converted to the
following bit Mod_Bit_No +1. All the bits in the Modbus register are transmitted with 0!

DC8-037-2, Edition 11.2020
12.8 Modbus RTU
Modbus data format Command Status Command output 1 bit in the

Modbus register
Command – 1 out of 16 DCS = ON
(register) with
command_status_MO
DM = ON
x ... Command = ON
DCS = OFF
x ... Command = OFF

Command – 1 out of 16 DCS = ON
(register) with
Command_status_MO
DM = OFF
x ... Command = ON
DCS = OFF
x ... Command = OFF
Telegram conversion
The table describes the elements of the IEC 60870-5-101/104 telegram that are evaluated during telegram
conversion.
Telegram elements
TI .. Type Identification • <TI:=45> .. Single command
CASDU, IOA .. Message address Configurable
06 .. activation is evaluated
(only “activation” is permitted)
xx .. other COTs not supported
T .. Test not supported
Information
SCO/DCO
SCS Single command status [only <TI:=45>]
0 .. OFF is evaluated
1 .. ON is evaluated
DCS double command state [only <TI:=46>]
0 .. not allowed not supported
3 .. not permitted not supported
QOC S/E
0 .. Execute Is checked for “execution”
1 .. Select not supported

DC8-037-2, Edition 11.2020
12.8 Modbus RTU
Telegram elements
QU Command qualifier 287
0 .. no additional defini- is evaluated
tions
1 .. short pulse duration is evaluated
2 .. long pulse duration is evaluated
3 .. Persistent command not supported
NOTE
i Elements of the IEC 60870-5-101/104 telegram that are not listed are not evaluated/not supported!
Indications
The address and telegram conversion for indications in the transmit direction are parameterized using the
Parameter category:
firmware /
Trans_binary_information
Parameter
• <TI:=30> .. single-point indication with CP56Time2a time tag

transmitted.
• Spontaneous
• 1 to 247
287 The command qualifier is only evaluated with pulse commands (see also parameter for command output times)

DC8-037-2, Edition 11.2020
12.8 Modbus RTU
Parameter

• FC = 15 .. WRITE MULTIPLE COILS [max. 1 coil available]
• 0 to 65535

format (TI)
SPI Single-point indication 30
NOTE
formats.
Telegram conversion
conversion.
Telegram elements
TI .. Type Identification <TI:=30> .. single-point indication with CP56Time2a time tag
QDS .. Quality descriptor
BL .. blocked not evaluated
SB .. substituted not evaluated
NT .. not topical NT = 1: Binary information is not transmitted! (Telegram is
discarded without an error message)
IV .. invalid IV = 1: Binary information is not transmitted! (Telegram is
discarded without an error message)
xx .. not evaluated
T .. Test not evaluated
Information
Single-point indication status
SPI 0 .. OFF is evaluated
Time_marker
CP56Time2a .. Date + time not evaluated
NOTE

DC8-037-2, Edition 11.2020
12.8 Modbus RTU
Measured Values
The address and telegram conversion for measured values, setpoints, bit strings in the transmit direction are
parameterized using the SICAM Device Manager with the “signals” function or using SICAM TOOLBOX II, OPM II
or for engineering via SICAM WEB with the transmit detailed routing parameters.
Parameter category:
firmware /Trans_meas-
ured_value
Parameter
• <TI:=34> .. Measured value, normalized value with time marker CP56Time2a

• <TI:=35> .. Measured value, scaled value with time marker CP56Time2a
• <TI:=36> .. Measured value, short floating-point number with time marker
CP56Time2a
transmitted.
• Spontaneous
Modbus_Format Modbus data format:
For supported Modbus formats for each internal IEC 60870-5-101/104 data
format, see the following table “Supported data formats”
X_0%, X_100% Parameters for value adaptation:
Y_0%, Y_100%
• <TI:=34> .. X_0% and X_100% may not be greater or less than ± 1
• <TI:=35> .. X_0% and X_100% must not be less than -32768 or greater than
+32767 and must be an integer value
• 1 to 247

DC8-037-2, Edition 11.2020
12.8 Modbus RTU
Parameter

• FC = 16 .. WRITE MULTIPLE REGISTERS [max. 2 registers are available]
• 0 to 65535

format (TI)
INT16 Signed Integer 16 Bit 34, 35, 36
INT32 (H/L) Signed integer 32 bit (HIGH before LOW) 34, 35, 36
INT32 (L/H) Signed integer 32 bit (LOW before HIGH) 34, 35, 36
UINT16 Unsigned Integer 16 Bit 34, 35, 36
UINT32 (H/L) Unsigned integer 32 bit (HIGH before LOW) 34, 35, 36
UINT32 (L/H) Unsigned integer 32 bit (LOW before HIGH) 34, 35, 36
FLOAT32 Short floating point (IEEE 754) 34, 35, 36
FLOAT32 Short floating point (IEEE 754) “Swapped” 34, 35, 36
(swapped)
NOTE
formats.
Value adaptation
Value adaption is defined by the parameters X_0%, X_100%, Y_0%, Y_100%.

DC8-037-2, Edition 11.2020
12.8 Modbus RTU
Telegram conversion
conversion.
Telegram elements
TI .. Type Identification • <TI:=34> .. Measured value, normalized value with time
marker CP56Time2a
• <TI:=35> .. Measured value, scaled value with time marker
CP56Time2a
• <TI:=36> .. Measured value, short floating-point number
NT .. not topical NT = 1: Value is not transmitted! (Telegram is discarded without
an error message)
IV .. invalid IV = 1: Value is not transmitted! (Telegram is discarded without
an error message)
OV .. overflow not evaluated
xx .. other COTs Not evaluated [only <TI:=33, 34, 35, 36, 37>]
Information

DC8-037-2, Edition 11.2020
12.8 Modbus RTU
Telegram elements
Value.. • Normalized value
• Scaled value
S .. Sign • IEEE STD 754 = short floating point number
Time_marker
NOTE
Setpoints
The address and telegram conversion for setpoints in transmit direction can be parameterized using the SICAM
TOOLBOX II, OPM II or for engineering via SICAM WEB with the transmit detailed routing parameters.
Parameter category:
firmware /Trans_setpoint
Parameter
• <TI:=48> .. setpoint command, normalized value

• <TI:=49> .. Setpoint adjusting command, scaled value
• <TI:=50> .. Setpoint adjusting command, short floating-point number
transmitted.
• Spontaneous
Modbus_Format Modbus data format:
For supported Modbus formats for each internal IEC 60870-5-101/104 data
format, see the following table “Supported data formats”

DC8-037-2, Edition 11.2020
12.8 Modbus RTU
Parameter
Y_0%, Y_100%
• <TI:=34> .. X_0% and X_100% may not be greater or less than ± 1
+32767 and must be an integer value
• 1 to 247

• FC = 16 .. WRITE MULTIPLE REGISTERS [max. 2 registers are available]
• 0 to 65535

format (TI)
INT32 (H/L) Signed integer 32 bit (HIGH before LOW) 48, 49, 50
INT32 (L/H) Signed integer 32 bit (LOW before HIGH) 48, 49, 50
UINT32 (H/L) Unsigned integer 32 bit (HIGH before LOW) 48, 49, 50
UINT32 (L/H) Unsigned integer 32 bit (LOW before HIGH) 48, 49, 50
FLOAT32 Short floating point (IEEE 754) 48, 49, 50
FLOAT32 Short floating point (IEEE 754) “Swapped” 48, 49, 50
(swapped)
NOTE
formats.

The “control location” function is used to ensure that setpoints are only transmitted from authorized sources. If
the function is activated, set point step adjusting commands are only transmitted from the protocol element
to the remote partner if the control location (originator address) has been released.
Value adaptation
Value adaption is defined by the parameters X_0%, X_100%, Y_0%, Y_100%.

DC8-037-2, Edition 11.2020
12.8 Modbus RTU
Telegram conversion
conversion.
Telegram elements
TI .. Type Identification • <TI:=48> .. setpoint command, normalized value
• <TI:=49> .. Setpoint adjusting command, scaled value
• <TI:=50> .. Setpoint adjusting command, short floating-
point number
S/E .. select/execute is evaluated (only “execute” is permitted)
06 .. activation is evaluated (only “activation” is permitted)
xx .. other COTs not accepted (only “activation” is permitted)
Information
• Scaled value
S .. Sign • IEEE STD 754 = short floating point number
NOTE

DC8-037-2, Edition 11.2020
12.8 Modbus RTU
Time synchronization
The address and telegram conversion for time synchronization in the transmit direction are parameterized
using the SICAM Device Manager with the “signals” function or using SICAM TOOLBOX II, OPM II or for engi-
neering via SICAM WEB with the transmit detailed routing parameters.
Parameter category:
firmware /Trans_time-
synchronisation
Parameter

• 1 to 247
• 0 to 65535

DC8-037-2, Edition 11.2020
12.8 Modbus RTU
Parameter
Time synchroniza- Time for time synchronization:
tion
• immediate spontaneous
• cyclical for each 1 minute (offset = 0 s)
• cyclical for each 1 minute (offset = 30 s)
• cyclic each 5th Minute (offset = 0 s)
spontaneous .. Transmission is spontaneously controlled by the single command
<TI:=45>
Offset = 0 s .. Transmission after minute change at 0th Second
Register_1 (high) Modbus time element:
Register_1 (low)
• Year (high)
Register_2 (high)
Register_2 (low)
• Year (low)
Register_3 (high) • Year - 2000 (high)
Register_3 (low) • Year - 2000 (low)

Register_4 (high) • Month
Register_4 (low) • Day
Register_5 (high) • Weekday
Register_5 (low)
• Day + day of week
Register_6 (high)
Register_6 (low)
• Hour
• Hour + SU
• Minute
• Minute + IV
• Second
• Millisecond (high)
• Millisecond (low)
• Ticks (10ms)
• Ticks (100ms)
• End identifier
NOTE
i For details on the “Modbus time element”, see 12.8.8 Modbus data formats.
The freely definable Modbus time synchronization telegram is sent out excluding the end identifier. If the end
identifier is in a Register_n (low), then this part of the Modbus register is transferred with the value 0.

format (TI)
DTx Date and time (freely definable) 45

DC8-037-2, Edition 11.2020
12.8 Modbus RTU
NOTE
formats.
Freely definable time synchronization format (example)
• Time synchronization controlled by <TI:= 45> single command with the address CASDU = 150, IOA = 145
on the Modbus address 1500.
Telegram conversion
conversion.
Telegram elements
TI .. Type Identification <TI:=45> .. Single command
Information
SCO
SCS Single command status
0 .. OFF not evaluated
1 .. ON not evaluated
QOC S/E
0 .. Execute Is checked for “execution”
1 .. Select not supported

DC8-037-2, Edition 11.2020
12.8 Modbus RTU
Telegram elements
QU Command qualifier
tions
NOTE
12.8.6.3 MASTER: Message Conversion in Receive Direction (Master ← Slave)

Message Conversion in receive direction: IEC 60870-5-101/104 ← Modbus RTU
IEC 60870-5-101/104 ← Modbus RTU Format
<TI:=30> Single-point information with 01, 02, 03, 04 -
CP56Time2a time tag
<TI:=31> Double-point information with time 01, 02, 03, 04 -
tag CP56Time2a
<TI:=33> Bit sting of 32 Bit with time tag 03, 04 -
CP56Time2a
time tag CP56Time2a
<TI:=36> Measured value, short floating point 03, 04 -
number with time tag CP56Time2a
<TI:=37> Integrated totals with time tag - -
CP56Time2a
Modbus Function Codes (FC):

01 .. READ COILS
02 .. READ DISCRETE INPUTS
03 .. READ HOLDING REGISTERS
04 .. READ INPUT REGISTERS
08 .. DIAGNOSTICS
Binary information
The parameterization of the address and message conversion for binary information in receive direction is to
be done with the SICAM Device Manager with the function “Signale” or the SICAM TOOLBOX II / OPM or with
the parameters for receive detail routing when using WEB engineering.
288 is sent from the SICAM RTU master station only in redundancy state "passive" for monitoring failed remote terminal units (only sub-
function 0000 .. RETURN QUERY DATA = LOOPBACK CHECK) This message is only mirrored back by the RTU.

DC8-037-2, Edition 11.2020
12.8 Modbus RTU
Parameter Category:
firmware /
Rec_binary_information
Parameters
TI Supported Type Identifications:
• <TI:=30> .. Single-point information with CP56Time2a time tag

• <TI:=31> .. Double-point information with time tag CP56Time2a
1 to 247
MODBUS_Func- Supported Modbus function codes:
tion_code
• FC = 01 .. READ COILS
• FC = 02 .. READ DISCRETE INPUTS
• FC = 03 .. READ HOLDING REGISTERS
• FC = 04 .. READ INPUT REGISTERS
Mod_Adr Modbus Address (Register Address):
• 0 to 65535
(in interrogation mode according Modicon address 0 is not possible!)

DC8-037-2, Edition 11.2020
12.8 Modbus RTU
Parameters
Mod_Bit_Nr Modbus bit number: [only for FC = 03, 04]
• 0 to 15 (only with single-point information)

• 0 to 14 (only with double-point information)
Ind-format_(MODM) Data format on the Modbus:
• 1 Bit
• 2 Bit (1 = OFF, 2 = ON)
• 2 Bit (1 = ON, 2 = OFF)
• MCU-Disconnector (3 Bit)
• MCU-Ground conector (3 Bit)
intermediate_pos_t Intermediate position suppression time for double point indication:
0 to 255 s
faulty_pos_t Faulty position suppression time for double point indication:
0 to 255 s
Supported Data Formats
Format Modbus Data Format IEC 60870-5-101/104 Data

format (TI)
SPI Single-point information 30, 31
DPI (1 = OFF, 2 = Double-Point Information (OFF before ON) 31
ON)
DPI (1 = ON, 2 = Double-Point Information (ON before OFF) 31
OFF)
3BIT/MCU 3-Bit-binary information - Siemens MCU (“Motor 31
Control Unit”) [only with FC = 01, 02]
NOTE
i As Modbus protocol does not define representation of data in coil/registers the Modbus format must be
specified for the message conversion. Supported Modbus data formats see 12.8.8 Modbus data formats.
Modbus-Format: 1 Bit
1 Bit as coil (n + 0) or 1 bit in a Modbus register will be processed as 1 Bit binary information (=Single Point
Information). Value range: 0 to 1.
Bit (n+0) Coding
(IEC 60870-5-101/104)
0 0 OFF
1 1 ON
Modbus Format: 2 Bit (1 = OFF, 2 = ON), 2 Bit (1 = ON, 2 = OFF)

2 neighboring coils addresses (n + 0, n + 1) or 2 neighboring bits (n + 0, n + 1) in in a Modbus register are
processed as 2-bit- binary information(= double-point information). Value range: 0 to 3.
Bit (n+1) Bit (n+0) Coding OFF before ON Coding ON before OFF
(IEC 60870-5-101/104)
0 0 0 DIFF DIFF
1 0 1 OFF ON
2 1 0 ON OFF
3 1 1 ERR ERR

DC8-037-2, Edition 11.2020
12.8 Modbus RTU
DIFF .. Intermediate position (indeterminate or intermediate state)

FAULT .. Faulty position (indeterminate state)
A suppression of intermediate-/faulty-position state can be enabled for double point informations.
Modbus Format: 3 Bit Siemens MCU (“Motor Control Unit”)

3 neighboring coil addresses (n + 0, n + 1, n + 2) are processed as 3-Bit-binary information. Value range: 0 to
7.
Note: This format is used for “Coils” only!
Modbus Data Format (IEC 60870-5-101/104) Double-point information
[DPI]
OFF (n+2) Grounding Discon- Disconnector [IEC DPI] Grounding Connector
Connector nector (n+0) [IEC DPI]
(n+1)
0 0 0 0 DIFF DIFF
1 0 0 1 ON OFF
2 0 1 0 OFF ON
3 0 1 1 ERR ERR
4 1 0 0 OFF OFF
5 1 0 1 ERR ERR
6 1 1 0 ERR ERR
7 1 1 1 ERR ERR
Disconnecter [IEC DPI] .. Disconnecter as IEC 60870-5-101/104 double point information

Grounding Connector [IEC DPI] ..... Disconnecter as IEC 60870-5-101/104 double point information
NOTE
i If MCU-Disconnecter (3 bit) and MCU-Earth (3 bit) will be used, same Modbus address must be set for both
data points (grounding switch and disconnecter)!
Example: Parameter setting of the 3-Bit-binary information (Siemens MCU)

DC8-037-2, Edition 11.2020
12.8 Modbus RTU
Parameter Category:
firmware /
Monitoring intermediate- and faulty positions

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) from PRE → BSE is suppressed for a parameterizable time.
For the suppression of the intermediate position an intermediate-position suppression time (Parameter
intermediate_pos_t) can be parameterized for each double-point information.
For the suppression of the faulty position a faulty position suppression time (Parameter faulty_pos_t) can
be parameterized for each double-point information.

DC8-037-2, Edition 11.2020
12.8 Modbus RTU
Message Conversion
The table describes the evaluated elements of the IEC 60870-5-101/104 message during message conversion.
Elements of the message
TI .. Type Identification • TI 30 .. Single-point information with CP56Time2a time tag
• TI 31 .. Double-point information with time tag CP56Time2a
CASDU, IOA .. Message address Parameter-settable
QDS ..Quality descriptor
BL .. blocked
only supported with format “SI/DI + IEC-State” (otherwise BL = 0)
SB .. substituted
only supported with format “SI/DI + IEC-State” (otherwise SB = 0)
NT .. not topical only supported with format “SI/DI + IEC-State” (otherwise NT = 0)
or on reception of Exception Response NT = 1
IV .. invalid
only supported with format “SI/DI + IEC-status” (otherwise IV = 0)
03 .. spontaneous upon change of information state or quality descriptor
20 .. Interrogated by station interrogation On reception of a GI request
Information
Single point information
SPI 0 .. OFF supported
1 .. ON supported
Double point information

DC8-037-2, Edition 11.2020
12.8 Modbus RTU

DPI 0 .. indeterminate or supported
intermediate state
1 .. OFF supported
2 .. ON supported
3 .. indeterminate state supported
Time tag
CP56Time2a .. Date + Time PRE internal time (receive time)
NOTE
i Not listed elements of the IEC 60870-5-101/104 message are not rated / not supported!
Measured Value
The parameterization of the address and message conversion for measured values and bit pattern in receive
direction is to be done with the SICAM Device Manager with the function “Signals” or the SICAM TOOLBOX II /
OPM or with the parameters for receive detail routing when using WEB engineering.
Parameter Category:
firmware/Rec_meas-
ured_value
Parameters
• <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 number with time tag
CP56Time2a
• 1 to 247

DC8-037-2, Edition 11.2020
12.8 Modbus RTU
Parameters
Function_code Supported Modbus function codes:

Mod_Adr Modbus address:
• 0 to 65535
Interrogation With interrogation priority It can be set, if and how often the data point is interro-
priority gated:
• Basic cycle
Modbus_Format Data format on Modbus:
supported Modbus data formats for each SICAM A8000 internal IEC
60870-5-101/104 data format see following table “supported data formats”
X_0%, X_100%, Y_0%, Parameters for value adaption (scaling)
Y_100% <TI:=34> .. Y_0% and Y_100% must not be greater or less than ± 1
<TI:=35> .. Y_0% und Y_100% must not be smaller than - 32768 and not greater
than +32767 and must be an integer value
thresh_uncond Value will be sent to BSE immediately when change of value > thresh_uncond.
thresh_additive When changing the value ≤ thres_ uncond, the value is not immediately
forwarded to the BSE and the additive change monitoring is performed.
Additive Change Monitoring: If the summed changes (= sign correct addition of
changes since the last transfer) > thres_additive, the value is passed to the
BSE.
thresh_unit • absolute value
• %

format (TI)
INT32 (H/L) Signed Integer 32 Bit (HIGH before LOW) 34, 35, 36
INT32 (L/H) Signed Integer 32 Bit (LOW before HIGH) 34, 35, 36
UINT32 (H/L) Unsigned Integer 32 Bit (HIGH before LOW) 34, 35, 36
UINT32 (L/H) Unsigned Integer 32 Bit (LOW before HIGH) 34, 35, 36
FLOAT32 Short Floating-Point (IEEE 754) 34, 35, 36
FLOAT32 Short Floating-Point (IEEE 754) “swapped” 34, 35, 36
(swapped)
NOTE
Value Adaption
The value adaption is defined by the parameters X_0%, X_100%, Y_0%, Y_100%.

DC8-037-2, Edition 11.2020
12.8 Modbus RTU
Message Conversion
TI .. Type Identification • 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 number with
time tag CP56Time2a
BL .. blocked not supported
SB .. substituted not supported
NT .. not topical NT = 1 if Exception Response *)
IV .. invalid only supported with floating point values, if the value = NAN
(“Not A Number”) *)
OV .. overflow OV = 1:
SICAM A8000 value is out of range of the selected type identifi-
cation

DC8-037-2, Edition 11.2020
12.8 Modbus RTU

03 .. spontaneous Alteration of the measured value depending on the thresholds or
alteration of the quality descriptor
Information
• scaled value
S .. sign • IEEE STD 754 = short floating point number
Time tag
NOTE
*) The conversion of invalid FLOAT-values in receive direction can be parameterized with the parameter
advanced parameters | Modbus specific settings | conversion of invalid
FLOAT-values (receive dir.).
Possible settings:
• Forwarding wit value = NAN; IV = 1

• Forwarding with freeze value; IV = 1
• Forwarding with freeze value; NT = 1
• Forwarding with freeze value; NT = 1, IV = 1
Bitstring
The parameterization of the address and message conversion for bit pattern in receive direction is to be done
with SICAM TOOLBOX II, OPM II or with the parameters for receive detail routing when using SICAM WEB for
engineering.

DC8-037-2, Edition 11.2020
12.8 Modbus RTU
Parameter Category:
firmware/Rec_meas-
ured_value
Parameters
• <TI:=33> .. Bit sting of 32 Bit with time tag CP56Time2a

• 1 to 247

• 0 to 65535
Interrogation With interrogation priority It can be set, if and how often the data point is interro-
priority gated:
• Basic cycle
X_0%, X_100%, Y_0%, not used
Y_100%
thresh_uncond not used
thresh_additive not used
thresh_unit not used

format (TI)
BS16 Bit string of 16 bit 33

DC8-037-2, Edition 11.2020
12.8 Modbus RTU
NOTE
specified for the message conversion. Supported data formats see 12.8.8 Modbus data formats.
Message Conversion
TI .. Type Identification <TI:=33> .. Bit sting of 32 Bit with time tag CP56Time2a
NT .. not topical NT = 1 if exception response
IV .. invalid not supported
OV .. overflow not supported
03 .. spontaneous if change of data
Information
Bitstring .. Bit string 32 bit
Time tag
NOTE
Integrated totals
The parameterization of the address and message conversion for integrated totals in receive direction is to be
done with the SICAM Device Manager with the function “Signale” or the SICAM TOOLBOX II / OPM or with the
parameters for receive detail routing when using WEB engineering.

DC8-037-2, Edition 11.2020
12.8 Modbus RTU
Parameter Category:
firmware /
Rec_counter_value
Parameters
• <TI:=37> .. Integrated totals with time tag CP56Time2a

• 1 to 247

• 0 to 65535
Transmit Definition for transmit integrated totals to BSE (counter freeze and read):
• Counter interrogation
• cyclic each 1, 2, 3, 5, 10, 15, 30, 60 minutes
IEC-group Request Counter Group:
Group 1 to 4
Overflow Overflow for integrated totals at:
• 24, 31 bit integer

• 2, 3, 4, 5, 6, 7, 8, 9 decades BCD

format (TI)
INT16 Signed Integer 16 Bit 37
INT32 (H/L) Signed Integer 32 Bit (HIGH before LOW) 37
INT32 (L/H) Signed Integer 32 Bit (LOW before HIGH) 37

DC8-037-2, Edition 11.2020
12.8 Modbus RTU

format (TI)
UINT16 Unsigned Integer 16 Bit 37
UINT32 (H/L) Unsigned Integer 16 Bit (HIGH before LOW) 37
UINT32 (L/H) Unsigned Integer 32 Bit (LOW before HIGH) 37
FLOAT32 Short Floating-Point (IEEE 754) 37
FLOAT32 Short Floating-Point (IEEE 754) “swapped” 37
(swapped)
NOTE
Message Conversion
TI .. Type Identification <TI:=37> .. Integrated totals with time tag CP56Time2a
Quality information for data
Sequence number With each trigger for latching for a group the sequence number
is increased in the range from 1 to 31.
CY .. Carry On overflow of the count in the associated count period
CA .. Presets not supported
IV .. invalid supported
03 .. spontaneous for transmit = periodic forwarding
37 .. requested by general counter inter- for general request counter (all counter groups)
rogation
38 to 41 .. interrogated by group 1 to 4 for request counter group (1 to 4)
interrogation
Information
Value.. Binary counter reading
S .. sign
Time tag
CP56Time2a .. Date + Time PRE internal time
NOTE
Message Conversion Counter Interrogation Command (SICAM A8000 internal only)

TI .. Type Identification <TI:=101> .. Counter Interrogation Command
CASDU, IOA .. Message address Defined
QCC .. Identifier counter interrogation

DC8-037-2, Edition 11.2020
12.8 Modbus RTU

FRZ RQT FRZ .. Freeze (= latch)
RQT .. Request (= requirement)
1 to 4 read (no freeze or reset)
Counter interrogation (1 to 4)
0
5 read (no freeze or reset)
general request counter
1 to 4 Counter freeze without reset
1
5 Counter freeze without reset
all counter groups
1 to 4 Counter freeze with reset
2
all counter groups
1 to 4 Reset counter
Counter interrogation group (1 to 4)
3
5 Reset counter
all counter groups
x 0; 6 to 63 not supported
06 .. activation must be set
12.8.6.4 SLAVE: Message Conversion in Transmit Direction (Slave → Master)

Message conversion in transmit direction: IEC 60870-5-101/104 → Modbus RTU
CP56Time2a time tag
tag CP56Time2a
(15 Bit + polarity sign)
time tag CP56Time2a (15 Bit + sign)
<TI:=36> Measured value, short floating point 03, 04 -
<TI:=37> Integrated totals with time tag 03, 04 -
CP56Time2a
(31 Bit + polarity sign + sequence
number)
<TI:=45> Single command 01, 02, 03, 04 -
<TI:=46> Double command 01, 02, 03, 04 -
<TI:=48> Set point command, normalized 03, 04 -
value
<TI:=49> Setpoint command, scaled value 03, 04 -

DC8-037-2, Edition 11.2020
12.8 Modbus RTU

<TI:=50> Set point command, short floating 03, 04 -
point number

01 .. READ COILS
08 .. DIAGNOSTICS
NT-Bit and IV-Bit Handling:

In the SICAM A8000 remote terminal unit it can be determined on the protocol element, whether or not the
invalid-Bit (IV = 1) and the not topical (NT = 1) are to be evaluated for the data in transmit direction BSE →
PRE).
This function can be parameterized on the protocol element for Modbus Slave serial with the parameter
advanced Parameter | Modbus specific settings | IV and NT-bit assessment or on the
protocol element for Modbus TCP Slave with the parameters in the Station definition ( connection
definition) in the field MODS-IV V and NT-bit handling .
Invalid-Bit (IV = 1) and Not-Topical-Bit (NT = 1) are not evaluated:

The data are stored in the protocol element internal data base (Modbus Register/Coils) for transmission and
marked internally as “not faulty”.
During the interrogation by the master station the current state is transmitted as response.
Invalid-Bit (IV = 1) and Not-Topical-Bit (NT = 1) are evaluated:

Dependent from parameterization following values can be sent for faulty data (NT = 1 or IV = 1):
• Exception Code = 4 (Slave DEVICE ERROR)
• Faulty value (substitute value)
• Last valid value
• With floating-point values NAN (“Not A Number”)
Exception Code = 4 (Slave DEVICE ERROR)

In the SICAM A8000 remote terminal unit it can be determined on the protocol element, if an exception code
= 4 (Slave DEVICE ERROR) should be sent instead of data when invalid-Bit “IV=1” or not topical “NT=1”. This
function can be parameterized on the protocol element for Modbus Slave serial with the parameter advanced
Parameter | Modbus specific settings | Faulty values for Modbus formats | use
exception code 4 or on the protocol element for Modbus TCP Slave with the parameters of the Station
definition (connection definition) in the field MODS-Exception Code 4.
Parameter Send Exception Code 04 = yes:

the data are entered in the internal process image of the protocol element (MODBUS Register) for transmis-
sion and marked internally as “faulty”.
during the interrogation of faulty data an Exception Code 04 (SLAVE DEVICE FAILURE) is transmitted by the
remote terminal unit as reply
Parameter Send Exception Code 04 = no:
289 is sent from the SICAM A8000 master station only in redundancy state “passive” for monitoring failed remote terminal units (only
sub-function 0000 .. RETURN QUERY DATA = LOOPBACK CHECK) This message is only mirrored back by the RTU.

DC8-037-2, Edition 11.2020
12.8 Modbus RTU
Instead of the data to be sent the substitute value (or for formats without assigned substitute value, the last
state) is entered in the internal process image of the protocol element (Modbus Register) for transmission and
marked internally as “faulty”.
During the interrogation of faulty data either a substitute value or the last state is transmitted by the remote
terminal unit as reply. The substitute value is to be parameterized globally (and not for each selective data
point) for selected Modbus data formats.
Note: In the case of binary information the last transmitted value (before the fault) is retained and this value is
transmitted for the interrogation by the master station.
Example:
16 single-point information are transmitted in a Modbus register address (Bit 0 to 15) in transmit direction.
Invalid-Bit (IV = 1) and Not-Topical-Bit (NT = 1) are evaluated (Send Exception Code 04 = no):
• faulty binary information are transmitted with the last current state before the fault
• non-faulty binary information are transmitted with the current state
• Binary information that have not yet been received by the basic system element after startup, are stored
in the protocol element internal data base for transmission with the state = "0" and marked internally as
“faulty”.
Substitute value
When reading disturbed data from the Modbus registers, the remote terminal unit answers with the response
message defined for the Modbus function code used, but instead of the data a substitute value is transmitted
for the disturbed values.
In the substation for Modbus “serial” this function is set with parameter advanced parameters | Modbus
specific settings | Faulty values for Modbus formats | Faulty value handling
receive direction | use exception code 4 (= no.
During writing of data in the Modbus registers of the RTU by the master station the remote terminal unit can
also carry out a handling for disturbed values itself. The detection of disturbed values takes place through
comparison with a parameter-settable substitute value.
This function is set in the substation with parameter advanced parameters | Modbus specific
settings | Faulty values for Modbus formats | Faulty value handling receive
direction.
On the protocol element for Modbus “serial” Slave (remote terminal unit) the substitute values are to be para-
meterized for the following selected Modbus formats in the system-technical parameters:
• Modbus-Format: 16 bit signed integer

Parameter for substitute value: advanced parameters | Modbus specific settings |
Faulty values for Modbus formats | faulty value for integer 16 bit signed
• Modbus-Format: 16 bit unsigned integer

Faulty values for Modbus formats | faulty value for integer 16 bit unsigned
• Modbus-Format: 32 Bit signed integer (HIGH before LOW)

Faulty values for Modbus formats | faulty value for integer 32 bit signed
HIGH before LOW
• Modbus-Format: 32 bit signed integer (LOW before HIGH)

Faulty values for Modbus formats | faulty value for integer 32 bit signed LOW
before HIGH
• Modbus-Format: 32 bit unsigned integer (HIGH before LOW)

Faulty values for Modbus formats | faulty value for integer 32 bit unsigned
HIGH before LOW

DC8-037-2, Edition 11.2020
12.8 Modbus RTU
• Modbus-Format: IEEE Floating-Point 754

For floating point either a “substitute value” or the special floating point value “NAN” (=not a number; all
bytes of FLOAT value set to FF FF FF FF) can be sent as substitute value.
The selection, which value shall be sent, takes place with parameter advanced parameters |
Modbus specific settings | Faulty values for Modbus formats | faulty art for
floating point format.
Faulty values for Modbus formats | faulty value for floating point format
Note:
There is no substitute value defined for all other Modbus formats. With these formats (e.g. binary information
with Modbus serial) the last status is transmitted.
Binary information
The parameterization of the address and message conversion for binary information in transmit direction is to
the parameters for transmit detail routing when using WEB engineering.
Parameter Category:
firmware / Trans_binary
Parameters

• <TI:=31> .. double-point information with time tag CP56Time2a
• 0 to 65535
Mod_Bit_Nr Modbus bit number:
• 0 to 15 [only with FC = 03, 04]

DC8-037-2, Edition 11.2020
12.8 Modbus RTU

format (TI)
NOTE
Mapping of double-point information (2 Bit states)

With MODBUS function code FC=3 or FC=4 double-point information can be converted to either 1 Bit or to 2
Bits in a MODBUS register (Bit# n, n + 1).
With Modbus function code FC = 1 or FC = 2 can be converted to either 1 or 2 Coils (Coil Addresses) (Address
n, n+1).
This function can be parameterized at the protocol element of the remote terminal unit for Modbus serial
globally for all double-point information in transmit direction with the parameter advanced Parameter |
Modbus specific settings | Definition DPI transforming | DPI in send direction.
Message Conversion
TI .. Type Identification • <TI:=30> .. Single-point information with CP56Time2a time
tag
• <TI:=31> .. Double-point information with time tag
CP56Time2a
BL .. blocked Modbus data format SPI/DPI+ IEC status: BL-Bit will be sent within
Modbus data format.
With other Modbus data formats BL-Bit is not evaluated.
SB .. substituted Modbus data format SPI/DPI+ IEC status: SB-Bit will be sent within
Modbus data format.
With other Modbus data formats SB-Bit is not evaluated.
NT .. not topical Modbus data format SPI/DPI+ IEC status: NT-Bit will be sent
within Modbus data format.
With other Modbus data formats it can be parameterized if the
IV-bit should be evaluated and which value (last valid value,
substituted value, exception code) should be sent if IV = 1. (see
NT-Bit and IV-Bit handling in transmit direction)
IV .. invalid Modbus data format SPI/DPI+ IEC status: IV-Bit will be sent within
Modbus data format.
With other Modbus data formats it can be parameterized if the
IV-bit should be evaluated and which value (last valid value,
substituted value, exception code) should be sent if IV = 1. (see
“NT-Bit and IV-Bit handling in transmit direction”)
xx .. not evaluated
Information

DC8-037-2, Edition 11.2020
12.8 Modbus RTU

SPI 0 .. OFF evaluated
1 .. ON evaluated
intermediate state
1 .. OFF evaluated
2 .. ON evaluated
3 .. indeterminate state evaluated
Time tag
CP56Time2a .. Date + Time not evaluated
NOTE
Commands
The parameterization of the address and message conversion for commands in transmit direction is to be
parameters for transmit detail routing when using WEB engineering.
Parameter Category:
firmware / Trans_binary
Parameters


DC8-037-2, Edition 11.2020
12.8 Modbus RTU
Parameters
• 0 to 65535
Mod_Bit_Nr Modbus bit number:
• 0 to 15 [only with FC = 03, 04]

format (TI)
SC (pulse) Single Command Pulse (1 Bit) 45
DC1 (pulse) Double command pulse (1 Bit) 46
NOTE
specified for the message conversion. Supported data formats see 12.8.8 Modbus data formats.
Mapping of double command (2 Bit states)

With double commands the command state (two command bits) is represented on 1 bit in Modbus Register or
on one coil.
Only the ON-state is evaluated for commands (same for single and double commands). Depending on the
command output time, with is part of the SICAM A8000 internal message - but at least for one interrogation
cycle - a ON pulse is generated in Modbus Register or as coil. The pulse duration can be parameterized with
the parameters advanced Parameter | command pulse duration.
Max. 10 commands (single-, double commands) can be active at the same time.
Message Conversion
06 .. activation not evaluated
xx .. other COTs not evaluated
Information
SCO/DCO
SCS Single command state [only <TI:=45>]
1 .. ON Pulse command 290
290 The parameterized bit is set in the Modbus register for the parameterized command duration. After expiry of the command output
time the Bit in the Modbus register is reset (pulse commands in transmit direction are held to the state ON for the time of the quali-
fier of command). The duration of the pulse is o be set with the parameters advanced parameters | command pulse duration.

DC8-037-2, Edition 11.2020
12.8 Modbus RTU

DCS Double command state [only <TI:=46>]
0 .. not allowed not evaluated
2 .. ON Pulse command 290
3 .. not allowed not evaluated
QOC S/E
0 .. execute not evaluated
1 .. select not evaluated
QU Qualifier of command
0 .. no additional defini- 290
tions
1 .. short pulse duration 290
2 .. long pulse duration 290
NOTE
Measured values ,Setpoint values, Binary information, Bit pattern

The parameterization of the address and message conversion for measured values, setpoint values, integrated
totals and bit patterns in transmit direction is to be done with the SICAM Device Manager with the function
“Signale” or the SICAM TOOLBOX II / OPM or with the parameters for transmit detail routing when using WEB
engineering.
Parameter Category:
firmware /Trans_value

DC8-037-2, Edition 11.2020
12.8 Modbus RTU
Parameters

CP56Time2a
• <TI:=48> .. Setpoint command, normalized value
• <TI:=49> .. Set point command, scaled value
• <TI:=50> .. Set point command, short floating point number
X_0%, X_100% Parameters for value adaption (scaling)
Y_0%, Y_100%
• valid range of value for X_0% and X_100% see 12.8.8 Modbus data formats
• <TI:=34> .. X_0% and X_100% must not be greater or less than ± 1.
+32767.

• 0 to 65535
MODS01_Format Data format on Modbus:
supported Modbus data formats for each SICAM RTUs internal 101/104 data
format see following table “supported data formats”

format (TI)
INT16 Signed Integer 16 Bit 34, 35, 36, 48, 49, 50
UINT16 Unsigned Integer 16 Bit 34, 35, 36, 48, 49, 50
INT32 (H/L) Signed Integer 32 Bit (HIGH before LOW) 34, 35, 36, 48, 49, 50
INT32 (L/H) Signed Integer 32 Bit (LOW before HIGH) 34, 35, 36, 48, 49, 50
UINT32 (H/L) Unsigned Integer 16 Bit (HIGH before LOW) 34, 35, 36, 48, 49, 50
UINT32 (L/H) Unsigned Integer 32 Bit (LOW before HIGH) 34, 35, 36, 48, 49, 50
FLOAT32 Short Floating-Point (IEEE 754) 34, 35, 36, 48, 49, 50
16BIT/H&B HARTMANN & BRAUN measured value format (0 to 34, 35, 36, 48, 49, 50
4000)
NOTE
Value Adaption

DC8-037-2, Edition 11.2020
12.8 Modbus RTU
Message Conversion
TI .. Type Identification • <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 number
NT .. not topical With parameters it will be defined if the NT-Bit should be evalu-
ated and which value (last valid value, substituted value, excep-
tion code) should be sent when NT = 1.
(see NT-Bit and IV-Bit handling in transmit direction)
IV .. invalid With parameters it will be defined if the IV-Bit should be evalu-
tion code) should be sent when IV = 1.
(see “NT-Bit and IV-Bit handling in transmit direction”)
Information

DC8-037-2, Edition 11.2020
12.8 Modbus RTU

• scaled value
Time tag
NOTE

TI .. Type Identification • <TI:=48> .. Setpoint command, normalized value
QOS .. qualifier of setpoint command
QL .. not evaluated
S/E .. select/execute not evaluated
06 .. activation not evaluated
Information
• scaled value
Time tag
NOTE
Integrated totals
The parameterization of the address and message conversion for integrated totals in transmit direction is to be
done with SICAM TOOLBOX II, OPM II or with the parameters for transmit detail routing when using SICAM
WEB for engineering.

DC8-037-2, Edition 11.2020
12.8 Modbus RTU
Parameter Category:
firmware /
Trans_counter_value
Parameters


• 0 to 65535

format (TI)
NOTE
Message Conversion

DC8-037-2, Edition 11.2020
12.8 Modbus RTU

Sequence number not evaluated
CY .. Carry not evaluated
CA .. Presets not evaluated
IV .. invalid With parameters it will be defined if the IV-Bit should be evalu-
tion code) should be sent when IV = 1.
(see “NT-Bit and IV-Bit handling in transmit direction”)
03 .. spontaneous not evaluated
37 .. requested by general counter inter- not evaluated
rogation
38 to 41 .. interrogated by group 1 to 4 not evaluated
interrogation
Information
S .. sign
Time tag
NOTE
12.8.6.5 SLAVE: Message Conversion in Receive Direction (Slave ← Master)

Message Conversion in receive direction: IEC 60870-5-101/104 ← Modbus RTU
SICAM A8000 IEC 60870-5-101/104 ← Modbus RTU Format
CP56Time2a time tag
tag CP56Time2a
<TI:=34> measured value, normalized value 06, 16 -
time tag CP56Time2a
<TI:=36> Measured value, floating point 06, 16 -
<TI:=37> Integrated totals with time tag 06, 16 -
CP56Time2a
<TI:=45> Single command 05, 06, 15, 16 -
<TI:=46> Double command 05, 06, 15, 16 -
<TI:=48> Setpoint command, normalized value 06, 16 -
<TI:=49> Setpoint command, scaled value 06, 16 -

DC8-037-2, Edition 11.2020
12.8 Modbus RTU
SICAM A8000 IEC 60870-5-101/104 ← Modbus RTU Format

<TI:=50> Setpoint command, short floating 06, 16 -
point number

01 .. READ COILS
05 .. WRITE SINGLE COIL
06 .. WRITE SINGLE REGISTER
15 .. WRITE MULTIPLE COILS
16 .. WRITE MULTIPLE REGISTERS
Commands
The parameterization of the address and message conversion for binary informations and commands in
receive direction is to be done with the SICAM Device Manager with the function “Signale” or the SICAM
TOOLBOX II / OPM II or with the parameters for transmit detail routing when using WEB engineering.
Parameter Category:
firmware /Rec_command
Parameters

Quali- Qualifier of command:
fier_of_command
• no additional definition
• short pulse duration
• long pulse duration
291 is sent from the SICAM RTU master station only in redundancy state "passive" for monitoring failed remote terminal units (only sub-
function 0000 .. RETURN QUERY DATA = LOOPBACK CHECK) This message is only mirrored back by the RTU.

DC8-037-2, Edition 11.2020
12.8 Modbus RTU
Parameters

• FC = 15 .. WRITE MULTIPLE COILS [max. 1 coil possible]
only 1 coil address is used for a double command
• 0 to 65535
Message Conversion
NOTE

06 .. activation supported
T ..Test not supported
Information
(SCO/DCO)
0 .. OFF Transfer of command with command state = OFF
1 .. ON Transfer of command with command state = ON
1 .. OFF Transfer of command with command state = OFF
2 .. ON Transfer of command with command state = ON
3 .. not allowed supported
not supported
QOC S/E
0 = execute supported
1 = select not supported
0 .. no additional defini- Parameter Qualifier_of_command in firmware /
tions Rec_command
1 .. short pulse duration Parameter Qualifier_of_command in firmware /
Rec_command
2 .. long pulse duration Parameter Qualifier_of_command in firmware /
Rec_command

DC8-037-2, Edition 11.2020
12.8 Modbus RTU
NOTE
Binary information
be done with SICAM TOOLBOX II, OPM II or with the parameters for transmit detail routing when using SICAM
Parameter Category:
firmware /
Parameters


• FC = 15 .. WRITE MULTIPLE COILS [max. 1 coil possible]
• FC = 16 .. WRITE MULTIPLE REGISTERS [max. 2 register possible]
• 0 to 65535
Mod_Bit_Nr Modbus bit number: [only for FC = 06, 16]
• 0 to 15
Mapping of double-point information (2 Bit states)

With protocol element for Modbus slave “serial” it can be parameterized with the parameter advanced
Parameter | Modbus specific settings | Definition DPI transforming | DM in
receive direction (FC15) if double-point information on Modbus protocol are represented as 1 bit or
on 2 bits.

DC8-037-2, Edition 11.2020
12.8 Modbus RTU
DPI Designation Modbus double

point information
1 Bit 2 Bit
0 indeterminate state or intermediate posi- - 0 0
tion
1 defined state OFF 0 0 1
2 defined state ON 1 1 0
3 indeterminate state - 1 1
Message Conversion
tag
CP56Time2a
BL .. blocked not supported (BL = 0)
SB .. substituted not supported (SB = 0)
NT .. not topical not supported (NT =0)
IV .. invalid not supported (IV = 0)
03 .. spontaneous upon change of information state
Information
1 .. ON supported
intermediate state
1 .. OFF supported
2 .. ON supported
Time tag
NOTE

DC8-037-2, Edition 11.2020
12.8 Modbus RTU
Measured Values / Setpoint Values

The parameterization of the address and message conversion for measured values and setpoint values in
receive direction is to be done with the SICAM Device Manager with the function “Signals” or the SICAM
TOOLBOX II / OPM or with the parameters for transmit detail routing when using WEB engineering.
Parameter Category:
firmware /Rec_value
Parameters

CP56Time2a
• <TI:=48> .. Setpoint command, normalized value with time tag CP56Time2a
Y_0%, Y_100%
• <TI:=34> .. Y_0% and Y_100% must not be greater or less than ± 1
• <TI:= 35> .. Y_0% and Y_100% must not be less than -32768 or greater than
+32767.
thresh_uncond Value will be sent to BSE immediately when change of value > thresh_uncond.
thresh_additive Value will not be sent immediately to BSE when change of value <=
thresh_uncond. Additive change monitoring will be activated.
Additive Change Monitoring:
If the summed changes (= sign correct addition of changes since the last transfer)
> thres_additive, the value is passed to the BSE.
thresh_unit • absolute value
• %

DC8-037-2, Edition 11.2020
12.8 Modbus RTU
Parameters

• 0 to 65535

format (TI)
FLOAT32 Short Floating-Point (IEEE 754) 34, 35, 36, 48, 49, 50
16BIT/H&B HARTMANN & BRAUN measured value format (0 to 34, 35, 36, 48, 49, 50
4000)
NOTE
Value Adaption

DC8-037-2, Edition 11.2020
12.8 Modbus RTU
Message Conversion
CP56Time2a
CP56Time2a
NT .. not topical not supported
IV .. invalid With Disturbed value treatment = Yes data will be sent
to BSE with last valid state and IV = 1 if received value is equal
with parameterized Disturbed value or equal with NAN (Not A
Number) for floating point values.
OV .. overflow OV = 1 if the converted value is outside the valid range of the
selected type identification.

DC8-037-2, Edition 11.2020
12.8 Modbus RTU

Information
• scaled value
Time tag
NOTE

TI .. Type Identification • <TI:=48> .. Setpoint command, normalized value
QOS .. qualifier of setpoint command
S/E [select/execute]
0 = execute supported
QL
1 to 63 .. reserved not supported
64 to 127 .. reserved not supported
Information
• scaled value
Time tag
NOTE

DC8-037-2, Edition 11.2020
12.8 Modbus RTU
Integrated totals
Parameter Category:
firmware /
Rec_counter_value
Parameters


• 0 to 65535
Transmit Definition for transmit integrated totals to BSE (counter freeze and read):
• periodic forwarding: 1, 2, 3, 5, 10, 15, 30, 60 minute(s)
IEC-group Request Counter Group:
• Request counter group 1, 2, 3, 4

Overflow • 24, 31 bit integer
• 2, 3, 4, 5, 6, 7, 8, 9 decades BCD

format (TI)

DC8-037-2, Edition 11.2020
12.8 Modbus RTU

format (TI)
32BIT/OMVZ OMV Counter Value Format 37
NOTE
Message Conversion
IV .. invalid supported
03 .. spontaneous for transmit = periodic forwarding
rogation
interrogation
Information
S .. sign
Time tag

TI .. Type Identification <TI:=101> .. Counter Interrogation Command
FRZ RQT FRZ .. Freeze (latch)
RQT .. Request
0

DC8-037-2, Edition 11.2020
12.8 Modbus RTU

1
all counter groups
2
all counter groups
3
5 Reset counter
all counter groups
NOTE
FRZ = freeze
<0> .. latch counter without resetting (latched values represent counts)
<1> .. latch counter without resetting (latched values represent counts)
<2> .. latch counter with resetting (latched values represent incremental values)
<3> .. Reset counter
RQT .. Request
31 … public range
<0> .. no counter interrogation (not used)
<1> .. counter interrogation group 1
<5> .. general counter interrogation
6 to 31 .. reserved for standard definitions of this companion standard (compatible range)
32 to 63 .. reserved for special use (private range)
Counter interrogation mode:
• local latching + spontaneous transmission
• Remote latching and remote read out
12.8.7 Interoperability Modbus RTU
12.8.7.1 Interoperability Modbus RTU Master

The companion standard defined presents sets of parameters and alternatives from which subsets have to be
selected to implement particular telecontrol systems. Other parameters, such as the listed set of different

DC8-037-2, Edition 11.2020
12.8 Modbus RTU
Modbus Function Codes or Modbus Data Formats in command and in monitor direction allow the specification
of the complete set or subsets, as appropriate for given applications. This clause summarizes the parameters
of the previous clauses to facilitate a suitable selection for a specific application. If a system is composed of
equipment stemming from different manufacturers it is necessary that all partners agree on the selected
parameters.
Function is not supported
Function is supported
Function not defined for this application!
Note:
values.
Network Configurations
Configuration Note
Multipoint-Partyline
Point-to-Point
(half duplex) with only one Slave
RS-232 or RS-485 (or RS-422)
Multiple Point-to-Point RS-232 or RS-485 (or RS-422)
Multipoint-Partyline RS-485 or RS-422
Multipoint-Star RS-232 or RS-485 (or RS-422)
Data Concentrator
Multipoint-Ring
Dial in
Dial out
Modem Bank

DC8-037-2, Edition 11.2020
12.8 Modbus RTU
Physical layer
Configuration Note
V.24/V.28 Standard
RS-232
• Point-to-Point
(Master with 1 Slave)
V.11 (4 wire) 292
RS-422
(Master with n Slave)
• Point-to-Point
V.11 (2 wire) 292
RS-485
• Point-to-Point
Transmission rate
• The Modbus protocol use only unbalanced communication procedures.
• The transmission speed is same for both directions (transmit/receive)
Speed Note Speed Note
50 Bit/s 1800 Bit/s
75 Bit/s 2000 Bit/s
100 Bit/s 2400 Bit/s
134.5 Bit/s 9600 Bit/s
150 Bit/s 19200 Bit/s
200 Bit/s 38400 Bit/s
300 Bit/s 56000 Bit/s
600 Bit/s 57600 Bit/s
1050 Bit/s 64000 Bit/s
1200 Bit/s 115200 Bit/s
292 Some applications require external converter (RS-232 ↔ RS-485/RS-422)!

DC8-037-2, Edition 11.2020
12.8 Modbus RTU
Link Layer
Transmission Mode
RTU Mode
ASCII Mode
RTU Mode
Byte asynchronous data transmission is used in in RTU-Mode (Least Significant Bit sent 1st for each byte).
Byte frame Note
1 Start bit
8 Data bits
Parity bit “even”
Parity bit “odd”
No parity bit
1 Stop bit
1.5 stop bits
2 stop bits
Note:
Byte frame for Modbus RTU mode according Modbus standard: 8E1 (1 start bit, 8 data bits, 1 parity bit „even
parity“, 1 stop bit)
For maximum compatibility with other devices “odd parity”, “no parity” and “1.5 stop bits”, “2 stop bits” is also
supported.
With “no parity” 2 Stopbits must be used!
In old configurations with Modbus RTU mode typically the byte frame 8N2 (8 data bits, no parity, 2 stop bits) is
used.
Modbus-Settings Note
Modbus Slave Address (8 Bit)
Modbus Function code (8 Bit)
Address will address a 16 Bit Modbus register

Modbus Register Address (16 Bit)
Cyclical Redundancy Check (CRC) (16 Bit)
ASCII Mode
Byte asynchronous data transmission is used in in ASCII-Mode (Least Significant Bit sent 1st for each byte).

DC8-037-2, Edition 11.2020
12.8 Modbus RTU
Byte frame Note
1 Start bit
7 Data bits
No parity bit
1 Stop bit
1.5 stop bits
2 stop bits
Note:
Byte frame for Modbus ASCII mode according Modbus standard: 7E1 (1 start bit, 7 data bits, 1 parity bit (even
parity), 1 stop bit.
supported.
In old configurations with Modbus ASCII mode typically the byte frame 7N2 (7 data bits, no parity, 2 stop bits)
is used.
Modbus Slave Address - 2 CHARS (8 Bit)
Modbus Function Code - 2 CHARS (8 Bit)
Address will address a 16 Bit Modbus register

Modbus Register Address - 4 CHARS (16 Bit)
Longitudinal Redundancy Check (LRC) - 2 CHARS (8

Bit)
Link Layer
Semantics Note
Unbalanced Master / Slave Communication
Modbus Master (halv duplex)
Modbus Slave

DC8-037-2, Edition 11.2020
12.8 Modbus RTU
Frame length
Semantics Note
RTU Mode:
Maximum Message length 253 Bytes (without
Address and CRC Bytes)
ASCII Mode: max. frame length is configurable
Maximum Message length 0 up to 2*252 CHARS
(without Start, Address, Function, LRC and End
Characters)
Address of the link layer
Semantics Note
1 octet (8 Bit) … RTU Mode Modbus Slave address (1 to 247)
2 CHAR …..…. ASCII Mode Modbus Slave address (1 to 247)
BROADCAST Addressing Mode Modbus Slave Address (0)
Application Layer
Modbus function codes
Modbus Function code - description Data-Formats

Data access (read/write Bit)
<20> SPI
01 = READ COILS
<21> DPI (1=off, 2=on)
<22> DPI (1=on, 2=off)
<20> SPI
02 = READ DISCRETE INPUTS
<21> DPI (1=off, 2=on)
<22> DPI (1=on, 2=off)
<20> SPI
05 = WRITE SINGLE COIL
<30> SC
<31> SC (pulse)
<35> DC2 (pulse)
<20> SPI
15 = WRITE MULTIPLE COILS
<30> SC
<31> SC (pulse)
<32> DC
<35> DC2 (pulse)
Data access (16 Bit read/write)

DC8-037-2, Edition 11.2020
12.8 Modbus RTU

<01> INT16
03 = READ HOLDING REGISTERS
<02> UINT16
<03> INT32 (H/L)
<04> UINT32 (H/L)
<05> INT32 (L/H)
<06> UINT32 (L/H)
<7a> FLOAT32
<7b> FLOAT32 (swapped)
<16> BS16
<20> SPI
<21> DPI (1=off, 2=on)
<22> DPI (1=on, 2=off)
<23> INT16 + IV
<24> UINT16 + IV
<50> SPI + IV
<51> DPI (1=off, 2=on) + IV
<52> DPI (1=on, 2=off) + IV
<01> INT16
04 = READ INPUT REGISTERS
<02> UINT16
<03> INT32 (H/L)
<04> UINT32 (H/L)
<05> INT32 (L/H)
<06> UINT32 (L/H)
<7a> FLOAT32
<16> BS16
<20> SPI
<21> DPI (1=off, 2=on)
<22> DPI (1=on, 2=off)
<23> INT16 + IV
<24> UINT16 + IV
<50> SPI + IV
<51> DPI (1=off, 2=on) + IV
<52> DPI (1=on, 2=off) + IV
<01> INT16
06 = WRITE SINGLE REGISTER
<02> UINT16
<16> BS16
<20> SPI 293
<30> SC 293
<31> SC (pulse) 293
<32> DC 293
<35> DC2 (pulse) 293
293 only 1 data point is supported per Modbus register!

DC8-037-2, Edition 11.2020
12.8 Modbus RTU

<01> INT16
16 = WRITE MULTIPLE REGISTERS
<02> UINT16
<03> INT32 (H/L)
<04> UINT32 (H/L)
<05> INT32 (L/H)
<06> UINT32 (L/H)
<7a> FLOAT32
<16> BS16
<20> SPI 293
<30> SC 293
<31> SC (pulse) 293
<32> DC 293
<35> DC2 (pulse) 293
<1xx> DTx
22 = MASK WRITE REGISTER
23 = READ / WRITE MULTIPLE REGISTERS
24 = READ FIFO QUEUE
Data access (File read/write)
20 = READ FILE RECORD
21 = WRITE FILE RECORD
Diagnostics
07 = READ EXCEPTION STATUS
08 = DIAGNOSTICS (SUB-Code 00 to 18, 20)
11 = GET COM EVENT COUNTER
12 = GET COM EVENT LOG
17 = REPORT SLAVE ID
43 = READ DEVICE Identification (SUB-Code = 14)
Other
43 = Encapsulated Interface Transport (SUB-Code = 13,
14)

DC8-037-2, Edition 11.2020
12.8 Modbus RTU
Modbus Exception Status
Modbus Exception Code Description Note

Modbus Function Code not implemented
01 = ILLEGAL FUNCTION
Requested Data Address not implemented

02 = ILLEGAL DATA ADDRESS
03 = ILLEGAL DATA VALUE
04 = SLAVE DEVICE FAILURE
05 = ACKNOWLEDGE
06 = SLAVE DEVICE BUSY
07 = NEGATIVE ACKNOWLEDGE (NAK)
08 = MEMORY PARITY ERROR
10 (0x0A) = GATEWAY PATH UNAVAILABLE
11 (0x0B) = GATEWAY TARGET DEVICE FAILED TO

RESPOND
Note:
• Requested data which are answered by the Modbus RTU slave with exception code, are emulated in
SICAM RTUs with “NT = 1” (not topical).
The Modbus RTU Master does not do any retries.
• The exception codes are not specially evaluated by the Modbus RTU master - a received exception code is
rated as negative acknowledgment.
12.8.7.2 Interoperability Modbus RTU Slave

parameters.
Note:
values.

DC8-037-2, Edition 11.2020
12.8 Modbus RTU
Network configuration
Configuration Note
Multipoint-Partyline
Point-to-Point
(half duplex) with only one Slave
RS-232 or RS-485 (or RS-422)
Multiple Point-to-Point RS-232 or RS-485 (or RS-422)
Multipoint-Partyline RS-485 or RS-422
Multipoint-Star RS-232 or RS-485 (or RS-422)
Data concentrator
Multipoint-Ring
Dial in
Dial out
Modem Bank
Physical layer
Configuration Note
V.24/V.28 Standard
RS-232
• Point-to-Point
V.11 (4-wire) 1)
RS-422
• Point-to-Point
V.11 (2-wire) 1)
RS-485
• Point-to-Point
Note:
Some applications require external converter (RS-232 ↔ RS-485/RS-422)
Transmission rate
Note:
• The Modbus protocol uses only one "unbalanced communication procedure".
• The transmission speed is same for both directions (transmit/receive)

DC8-037-2, Edition 11.2020
12.8 Modbus RTU
Speed Note Speed Note
50 Bit/s 1800 Bit/s
75 Bit/s 2000 Bit/s
134.5 Bit/s 9600 Bit/s
150 Bit/s 19200 Bit/s
200 Bit/s 38400 Bit/s
300 Bit/s 56000 Bit/s
600 Bit/s 57600 Bit/s
1050 Bit/s 64000 Bit/s
1200 Bit/s 115200 Bit/s
Link Layer
Transmission Mode
RTU Mode
ASCII Mode
RTU Mode
Byte asynchronous data transmission is used in in RTU-Mode (Least Significant Bit sent 1st for each byte).
Byte frame Note
1 Start bit
8 Data bits
No parity bit
1 Stop bit

DC8-037-2, Edition 11.2020
12.8 Modbus RTU
Byte frame Note
1.5 stop bits
2 stop bits
Note:
Byte frame for Modbus RTU mode according Modbus standard: 8E1 (1 start bit, 8 data bits, 1 parity bit “even
parity”, 1 stop bit)
supported.
In old configurations with Modbus RTU mode typically the byte frame 8N2 (8 data bits, no parity, 2 stop bits) is
used.
Modbus Function Code (8 Bit)
Modbus Register Address (16 Bit) Address will address a 16 Bit Modbus register
Cyclical Redundancy Check (CRC) (16 Bit)
ASCII Mode
Byte asynchronous data transmission is used in in ASCII-Mode (Least Significant Bit sent 1st for each byte).
Byte Frame Note
1 Start bit
7 Data bits
Parity Bit “even”
No parity bit
1 Stop bit
1.5 stop bits
2 stop bits
Note:
Byte frame for Modbus ASCII mode according Modbus standard: 7E1 (1 start bit, 7 data bits, 1 parity bit (even
parity), 1 stop bit)
supported.

DC8-037-2, Edition 11.2020
12.8 Modbus RTU
In old configurations with Modbus ASCII mode typically the byte frame 7N2 (7 data bits, no parity, 2 stop bits)
is used.
Procedure Note
Modbus Slave Address - 2 CHARS (8 Bit)
Modbus Function Code - 2 CHARS (8 Bit)
Modbus Register Address - 4 CHARS (16 Bit) Address will address a 16 Bit Modbus register
Longitudinal Redundancy Check (LRC) - 2 CHARS (8

Bit)
Link Layer
Semantics Note
Modbus Master (halv duplex)
Modbus Slave
Frame length
Semantics Note
RTU Mode:
Maximum Message length 253 Bytes (without
Address and CRC Bytes)
ASCII Mode: max. frame length is configurable
Maximum Message length 0 up to 2*252 CHARS
(without Start, Address, Function, LRC and End
Characters)
Semantics Note
1 octet (8 Bit) … RTU Mode Modbus Slave address (1 to 247)
2 CHAR …..…. ASCII Mode Modbus Slave address (1 to 247)
BROADCAST Addressing Mode Modbus Slave Address (0)
Application Layer

<20> SPI
01 = READ COILS
<21> DPI (1=off, 2=on)
<22> DPI (1=on, 2=off)

DC8-037-2, Edition 11.2020
12.8 Modbus RTU

<20> SPI
<21> DPI (1=off, 2=on)
<22> DPI (1=on, 2=off)
<20> SPI
<30> SC
<31> SC (pulse)
<35> DC2 (pulse)
<20> SPI
<21> DPI (1=off, 2=on)
<22> DPI (1=on, 2=off)
<30> SC
<31> SC (pulse)
<32> DC
<35> DC2 (pulse)
<01> INT16
<02> UINT16
<03> INT32 (H/L)
<04> UINT32 (H/L)
<05> INT32 (L/H)
<06> UINT32 (L/H)
<7a> FLOAT32
<16> BS16
<20> SPI
<21> DPI (1=off, 2=on)
<22> DPI (1=on, 2=off)
<23> INT16 + IV
<24> UINT16 + IV
<50> SPI + IV
<51> DPI (1=off, 2=on) + IV
<52> DPI (1=on, 2=off) + IV

DC8-037-2, Edition 11.2020
12.8 Modbus RTU

<01> INT16
<02> UINT16
<03> INT32 (H/L)
<04> UINT32 (H/L)
<05> INT32 (L/H)
<06> UINT32 (L/H)
<7a> FLOAT32
<16> BS16
<20> SPI
<21> DPI (1=off, 2=on)
<22> DPI (1=on, 2=off)
<23> INT16 + IV
<24> UINT16 + IV
<50> SPI + IV
<51> DPI (1=off, 2=on) + IV
<52> DPI (1=on, 2=off) + IV
<01> INT16
<02> UINT16
<20> SPI 294
<21> DPI (1=off, 2=on) 294
<22> DPI (1=on, 2=off) 294
<30> SC 294
<31> SC (pulse) 294
<32> DC 294
<35> DC2 (pulse) 294
<01> INT16
<02> UINT16
<03> INT32 (H/L)
<04> UINT32 (H/L)
<05> INT32 (L/H)
<06> UINT32 (L/H)
<7a> FLOAT32
<20> SPI 294
<21> DPI (1=off, 2=on) 294
<22> DPI (1=on, 2=off) 294
<30> SC 294
<31> SC (pulse) 294
<32> DC 294
<35> DC2 (pulse) 294
294 per Modbus register several data points are supported!

DC8-037-2, Edition 11.2020
12.8 Modbus RTU
Diagnostics
43 = READ DEVICE Identification (SUB-Code = 14)
Other
43 = Encapsulated Interface Transport (SUB-Code = 13,
14)


05 = ACKNOWLEDGE

RESPOND
Note: Not supported Exception Codes are handled as “no response”.

DC8-037-2, Edition 11.2020
12.8 Modbus RTU
12.8.8 Modbus data formats
Supported Modbus data formats

Format # Format Designation Register Coil
General formats
1 INT16 Signed Integer 16 Bit ✓ –
2 UINT16 Unsigned Integer 16 Bit ✓ –
3 INT32 (H/L) Signed Integer 32 Bit (HIGH before LOW) ✓ –
4 UINT32 (H/L) Unsigned Integer 32 Bit (HIGH before ✓ –
LOW)
5 INT32 (L/H) Signed Integer 32 Bit (LOW before HIGH) ✓ –
6 UINT32 (L/H) Unsigned Integer 32 Bit (LOW before ✓ –
HIGH)
7a FLOAT32 Short Floating-Point (IEEE 754) ✓ –
7b FLOAT32 (swapped) Short Floating-Point (IEEE 754) “swapped” ✓ –
16 Bitstring 16 Bit Bit string of 16 bit ✓ –
20 SPI Single-point information ✓ ✓
21 DPI (1 = off, 2 = on) Double-Point Information (OFF before ON) ✓ ✓
22 DPI (1 = on, 2 = off) Double-Point Information (ON before OFF) ✓ ✓
30 SC Single command ✓ ✓
31 SC (pulse) Single Command “pulse” ✓ ✓
32 DC Double command ✓ ✓
33 DC1 Double Command (1 bit) ✓ ✓
35 DC2 (pulse) Double Command “pulse” ✓ ✓
Device specific formats
50 SPI + IV Single-point information + invalid-identi- ✓ –
fier
51 DPI (1 = off, 2 = on) + IV Double-Point Information (OFF before ON) ✓ –
+ Invalid-identifier
52 DPI (1 = on, 2 = off) + IV Double-Point Information (ON before OFF) ✓ –
53 INT16 + IV Signed Integer 16 Bit + Invalid-identifier ✓ –
54 UINT16 + IV Signed Integer 16 Bit + Invalid-identifier ✓ –
1xx DTx Date & Time (free parameter-settable) ✓ –
Data formats in a Modbus register are always displayed/transmitted in “Big Endian” (HIGH before LOW order).
Data in Modbus Register:

DC8-037-2, Edition 11.2020
12.8 Modbus RTU
Format-1: INT16 – Signed Integer 16 Bit
VZ (Sign): <0> = "+"; <1> = "-"

Value range: -32768 0 to +32767
Note: Negative values will be stored in two's complement.
Format-2: UINT16 – Unsigned Integer 16 Bit
Value range: 0 to 65535
Format-3: INT32 (H/L) – Signed Integer 32 Bit (HIGH before LOW)
VZ (Sign): <0> = "+"; <1> = "-"

Value range: -2 147 483 648 to 0 to +2 147 483 647
Format-4: UINT32 (H/L) – Unsigned Integer 32 Bit (HIGH before LOW)

DC8-037-2, Edition 11.2020
12.8 Modbus RTU
Value range: 0 to 4 294 967 295
Format-5: INT32 (L/H) – Signed Integer 32 Bit (LOW before HIGH)
VZ (Sign): <0> = "+"; <1> = "-"

Value range: -2 147 483 648 to 0 to +2 147 483 647
Format-6: UINT32 (L/H) – Unsigned Integer 32 Bit (LOW before HIGH)
Value range: 0 to 4 294 967 295
Format-7a: FLOAT32 – Short Floating Point (IEEE 754)
Value range: ∼1.1 ⋅ 10-38 bis ∼ 3.4 ⋅ 1038

VZ (Sign): <0> = "+"; <1> = "-"
Exponent: <255> = "NaN" (not a number) or ∞

DC8-037-2, Edition 11.2020
12.8 Modbus RTU
Format-7b: FLOAT32 (swapped) – Short Floating Point (IEEE 754) "swapped"
Value range: ∼1.1 ⋅ 10-38 bis ∼ 3.4 ⋅ 1038

VZ (Sign): <0> = "+"; <1> = "-"
Format-16: Bitstring 16 Bit – Bitstring of 16 Bit
Format-20: SPI - Single-point information

Single-point information as coil or 1 bit in Modbus register.
Value range: 0, 1

DC8-037-2, Edition 11.2020
12.8 Modbus RTU
SPI - Single-point information

<0> = OFF
<1> = ON
Bit (n+0) Coding (IEC 60870-5-101/104)
0 OFF
1 ON
Format 21: DPI (1=off, 2=on) – Double-point information (OFF before ON)
Format 22: DPI (1=on, 2=off) – Double-point information (ON before OFF)
Double-point information in 2 adjacent bits in the Modbus register or as 2 adjacent bits as coil.
Note:
The 2 bits of DPI must be located always in same byte of a Modbus register.
Value range: 0 to 3
DPI - Double-Point Information (OFF before ON) - DPI (1 = off, 2 = on)

<0> = indeterminate or intermediate state
<1> = OFF
<2> = ON
<3> = indeterminate state
DPI - Double-Point Information (ON before OFF) - DPI (1 = on, 2 = off)

<1> = ON
<2> = OFF

DC8-037-2, Edition 11.2020
12.8 Modbus RTU
(IEC 60870-5-101/104)
0 0 0 DIFF DIFF
1 0 1 OFF ON
2 1 0 ON OFF
3 1 1 ERR ERR

Format-30: SC – Single Command

A single command with command state ON or OFF can be sent as coil (1 bit) or as 1 bit Modbus register.
Value range: 0, 1
SCS - Single Command State

<0> = OFF
<1> = ON
Command Modbus Format Command transmission
Single command "ON" SC COIL (n); Register/Bit (n) = ON
Single command OFF SC COIL (n); Register/Bit (n) = “OFF“

DC8-037-2, Edition 11.2020
12.8 Modbus RTU
Modbus Format Command state Command Output

SC as Coil or 1 Bit in Modbus Register
SC SCS = ON
x ... Command = ON
SCS = OFF
x ... Command = OFF
Format-31: SC (pulse) – Single Command (pulse)

A single command with command state ON can be sent as pulse with the parametrized command output time
as coil (1 bit) or as bit in the Modbus register .
The command state OFF is not evaluated.
The command state will be set to INAKTIV after command output time.
Value range: 0, 1
SCP – Command State (Pulse)

<0> = inactive
<1> = active
Single command "ON" SC (pulse) COIL (n); Register/Bit (n) = pulse

DC8-037-2, Edition 11.2020
12.8 Modbus RTU

SC (pulse) SCS = ON
tp ... command output time (pulse duration)

x ... Command = ON
SCS = OFF The <OFF> state is not evaluated!
Format-32: DC – Double Command (2 Bit)

The command state of a double command resp. regulating step command (2 bit) is transferred with 2 consec-
utive bits as coils or bits in the Modbus register.
Value range: 0 to 3
DCS - Double command state [Modbus_command_state = OFF]

<1> = OFF
<2> = ON
DCS - Double command state [Modbus_command_state = ON]

<1> = ON
<2> = OFF
(IEC 60870-5-101/104)
[Modbus_command_state = OFF] [Modbus_command_state = ON]
0 0 0 not permitted not permitted
1 0 1 OFF ON
2 1 0 ON OFF

DC8-037-2, Edition 11.2020
12.8 Modbus RTU

2 Bit as Coil or 2 Bit in Modbus Register
DC DCS = ON
Modbus_command_state = ON RCS = HIGHER
x ... Command = ON
DCS = OFF
RCS = LOWER
x ... Command = OFF

DC DCS = ON
Modbus_command_state = OFF RCS = HIGHER
x ... Command = ON
DCS = OFF
RCS = LOWER
x ... Command = OFF
Format-33: DC1 – Double Command (1 Bit)

A double command with command state ON or OFF can be sent as coil (1 bit) or as 1 bit Modbus register.
Value range: 0, 1

DC8-037-2, Edition 11.2020
12.8 Modbus RTU
DCS – Double command state (1 Bit)

<0> = OFF
<1> = ON
Double command ON DC1 COIL (n); Register/Bit (n) = ON
Double command OFF DC1 COIL (n); Register/Bit (n) = “OFF“

DC as Coil or 1 Bit in Modbus Register
DC1 DCS = ON
x ... Command = ON
DCS = OFF
x ... Command = OFF
Format-35: DC2 (pulse) – Double Command (Pulse)

A double command or regulating step command with the command state DCS=<ON>/<OFF> or RCS=<higher>/
<lower> is transferred on Modbus with the set command output time as pulse (2 bits) with 2 coils or 2 bits in
the Modbus register.
The command state <ON> or <HIGH> is transmitted as 1-bit pulse on coil address (n+0 or n+1) or in register
address/bit (n+0 or n+1).
The command state <OFF> or <LOWER> is transmitted as 1-bit pulse on coil address (n+1 or n+0) or in register
Value range: 0 to 3

DC8-037-2, Edition 11.2020
12.8 Modbus RTU
DCP – Double command (Pulse) – per bit

<0> = INAKTIVE
<1> = AKTIV
DC2 (pulse) DCS = ON

x ... Command = ON
DC2 (pulse) DCS = OFF
Modbus_command_state = ON RCS = LOWER

x ... Command = OFF

x ... Command = ON
Modbus_command_state = OFF RCS = LOWER

x ... Command = OFF
Format 50: SPI + IV – Single-point information + Invalid-identifier
IV (Invalid-identifier):
<0> = valid
<1> = invalid
SPI (Single-point information):

<0> = OFF
<1> = ON

DC8-037-2, Edition 11.2020
12.8 Modbus RTU
Note:
• IV bit applies to all binary information in the Modbus register.
• Unused SPI's/bits are transferred with <0>.
• In a Modbus register several single- and double-point information can be transmitted mixed.
Format 51: DPI (1=off, 2=on) + IV - Double-point information (OFF before ON) + Invalid-identifier
Format 52: DPI (1=on, 2=off) + IV - Double-point information (ON before OFF) + Invalid-identifier
<0> = valid
<1> = invalid
Double-Point Information (OFF before ON) DPI (1 = off, 2 = on)

<1> = OFF
<2> = ON
Double-Point Information (ON before OFF) DPI (1 = on, 2 = off)

<1> = ON
<2> = OFF
(IEC 60870-5-101/104)
0 0 0 DIFF DIFF
1 0 1 OFF ON
2 1 0 ON OFF
3 1 1 ERR ERR

Note:
• Double-point information must always be transferred completely in a Modbus register byte.

DC8-037-2, Edition 11.2020
12.8 Modbus RTU
Format 53: INT16 + IV – Signed Integer 16 Bit + Invalid-identifier
<0> = valid
<1> = invalid
VZ (Sign):
<0> = "+"
<1> = "–"
Value range: -16384 0 to +16383
Format 54: UINT16 + IV – Unsigned Integer 16 Bit + Invalid-identifier
<0> = valid
<1> = invalid

DC8-037-2, Edition 11.2020
12.8 Modbus RTU
Format-1xx: DTx – Date + Time (free configurable)
Note:
• Only the configured number of bytes will be sent.
• If “End of Frame” is in the HIGH data byte, then the Modbus register will not be sent.
• If “End of Frame” is in the LOW data byte, then the Modbus register will be sent and in the LOW data byte
“0“ will be sent.
Byte sending order:

Data byte 0 (MSB of 1st Modbus register) is sent as 1st data byte.
Data byte 1 (LSB of 1st Modbus register) is sent as 2nd data byte.
Data byte 2 (MSB of 2nd Modbus register) is sent as 3rd data byte.
:
:
Data byte n will be sent as last byte.
Time Element Value Range Example

Not used Dummy: UI8 [7 to 0] <0>
year (high) year (high) [7 to 0] <0 to 255> year = 2016 = 07E0 [HEX]
→ year (high) = 0x07 [HEX]
year (low) year (low) [7 to 0] <0 to 255> year = 2016 = 07E0 [HEX]
→ year (low) = 0xEX [HEX]
year - 2000 year 2000 (high) [7 to 0] <0 to 255> year = 2016 → 2016 - 2000 = 16 = 0x0010
(high) [HEX]
→ year - 2000 (high) = 0x00 [HEX]

DC8-037-2, Edition 11.2020
12.8 Modbus RTU

year - 2000 (low) year 2000 (high) [7 to 0] <0 to 255> year = 2016 → 2016 - 2000 = 16 = 0x0010
[HEX]
→ year - 2000 (low) = 0x10 [HEX]
Month Month [7 to 0] <1 to 12> Month = 12 (December) → Month = 0x0C [HEX]
Day Day [7 to 0] <1 to 31> Day = 23 → Day = 0x17 [HEX]
Day of week Day of week [7 to 0] <1 to 7> Day of week = Tuesday → Day off week = 0x02
<1> = Monday; <2> = Tuesday; ... <7> = [HEX]
Sunday
day + day of Day [4 to 0] <1 to 31>
week Day of week [7 to 5] <1 to 7>
<1> = Monday; <2> = Tuesday; ... <7> =
Sunday
Hour Hour [7 to 0] <0 to 23> hour = 21 = 0x15 [HEX]
hour + SU Hour [4 to 0] <0 to 23>
summer time (SU) [7] <0, 1>
SU <0> = standard time (winter time)
SU <1> = summer time
Minute Minute [5 to 0] <0 to 59> minute = 59 = 0x3B [HEX]
minute + IV Minute [6 to 0] <0 to 59>
Invalid (IV) [7] <0, 1>
IV <0> = valid
IV <1> = invalid
second second [7 to 0] <0 to 59> second = 32 = 0x20 [HEX]
millisecond millisecond n ⋅ 1 ms (high) [7 to 0] <0 to milliseconds = 998 = 03E6 [HEX]
(high) 255> → millisecond (high) = 0x03 [HEX]
n <0 to 59999> = range including
seconds
millisecond (low) milliseconds n ⋅ 1 ms (low) [7 to 0] <0 to milliseconds = 998 = 03E6 [HEX]
255> → millisecond (low) = 0xE6 [HEX]
seconds
Ticks (10 ms) milliseconds n ⋅ 10 ms [7 to 0] <0 to 99> milliseconds = 998
→ Ticks (10 ms) = 99 = 0x63 [HEX]
→ milliseconds n ⋅ 100 ms = 9 = 0x09 [HEX]
EOF (End of Note: This time element defines the end of the
Frame) freely configurable time format - this data byte
is no longer sent!
Legend: [7 to 0] = bit position in data byte of Modbus register

< > = valid range of value

DC8-037-2, Edition 11.2020
12.9 Modbus TCP
12.9 Modbus TCP
12.9.1 Introduction
The Modbus TCP protocol is a standardized transmission protocol (TCP/IP) for communication with devices in
the network (LAN, WAN).
For SICAM A8000 CP-8000, CP-8021, CP-8022 the following protocol firmware for Modbus TCP are available:
MBCiT0 CP-8000, CP-8021, Modbus TCP Master (“Client”)
CP-8022
MBSiT0 CP-8000, CP-8021, Modbus TCP Slave (“Server”)
CP-8022
The Modbus TCP protocol defines the data exchange of 16 bit register values or of coils (binary information)
between systems via a LAN/WAN communication connection.
The Modbus TCP protocol is standardized by the user organization www.modbus.org and by IEC 61158 Digital
data communication for measurement and control - Fieldbus for use in industrial control systems (CFP15/1
Modbus/TCP).
The Modbus protocol was originally defined for serial transmission, later Modbus TCP was defined for the
transmission of data via LAN/WAN (Ethernet).
The message structure is very similar between “Modbus seriell” and “Modbus TCP”. With Modbus TCP in addi-
tion to the Modbus data (PDU) the Modbus TCP specific MBAP-Header is transmitted.
The protocol element MBCiT0 enables the LAN/WAN communication of one component as central station
(=Master/Client) with up to 100 remote terminal units (=Slaves/Server).
The protocol element MBSiT0 enables the LAN/WAN communication of one component as substation (=Slave/
Server) with up to 100 central stations (=Master/Clients).
The master station and the remote terminal units operate with the Ethernet based LAN/WAN communication
protocol according to Modbus TCP.
The supported functionality (interoperability) is described in the chapter 12.9.7 Interoperability Modbus TCP.
With Modbus TCP the data transfer is controlled by the central station (master).
With Modbus TCP every RTU is assigned an unambiguous IP address.
Substations can only transfer data if the data is requested by the central station (READ Register, Read Coils).
Sub-stations with serial interface can be connected to a Modbus TCP master via a serial Ethernet converter
(with Modbus TCP functionality).

DC8-037-2, Edition 11.2020
12.9 Modbus TCP
Schematic configuration with Modbus TCP:
[Modbus_TCP_config_CP-8000_CP-802x, 1, en_US]
Figure 12-7 Modbus TCP Configuration
12.9.2 Functions
Functions of the Master Station - Modbus TCP Master (MBCiT0)
• LAN/WAN communication protocol according to Modbus TCP

– Modbus TCP “client”
– Port number = 502
– Communication with up to 100 Modbus TCP slaves
– max. number of connections = 100
– max. number of supported data points (all connections) = 10000
– Supported Modbus slave addresses 1 to 247
– Modbus Unit Identifier 1 to 247, 255
– Modbus TCP with half duplex link transmission procedure
– “Pre-Fetched Polling” (Number of max. “Client transactions” = 5
– Modbus TCP message protection by TCP/IP Layer

DC8-037-2, Edition 11.2020
12.9 Modbus TCP
• Network configuration
– LAN/WAN
– Ethernet Speed/Duplex
– 100 Mbit/s (full duplex)
– Auto Negotiation, Auto-MDIX (Auto Medium Dependent Interface Crossover)
– Auto Negotiation (100 Mbit/s full duplex), Auto-MDIX
– Auto Negotiation (100 Mbit/s half duplex), Auto-MDIX
– 100 Mbit/s full duplex, Auto-MDIX
– 100Mbit/s half duplex, Auto-MDIX
– TCP/IP Optimierungsparameter
– MTU size (Maximum Transmission Unit)
– TCP min. expected acknowledgment time
• Interoperability according to Section 12.9.7.1 Interoperability Modbus TCP Master “Client“ (MBCiI0)
• Modbus register/coil addressing

– 16-bit Modbus register
– Modbus register-addresses: 1 (0) to 65535
– Modbus coil-addresses: 1 (0) to 65535
– Modbus register addressing - according to Modbus Standard (YES/NO - station selective)
(Modbus standard addressing = beginning from address 1)
• Modbus function codes

– 01 = READ COILS
• Modbus Exception Codes

– 04 = Slave DEVICE FAILURE

DC8-037-2, Edition 11.2020
12.9 Modbus TCP
• Modbus data formats

– INT16: Signed Integer 16 Bit
– UINT16: Unsigned Integer 16 Bit
– INT32 (H/L): Signed integer 32 bit (HIGH before LOW)
– UINT32 (H/L): Unsigned integer 32 bit (HIGH before LOW)
– INT32 (L/H): Signed integer 32 bit (LOW before HIGH)
– UINT32 (L/H): Unsigned integer 32 bit (LOW before HIGH)
– FLOAT32: Short floating point (IEEE 754)
– FLOAT32 (swapped): Short floating point (IEEE 754) “Swapped”
– FLOAT32 (little-endian): Short Floating Point (IEEE 754) “Little-endian”
– BS16: Bitstring 16 Bit
– SPI: Single-point indication
– DPI: Double-Point Information (OFF before ON)
– DPI: Double-Point Information (ON before OFF)
– SC: Single command
– SC: Single command “pulse”
– DC: Double command
– DC: Double Command “pulse”
• IEC 60870-5-101/104 data formats in transmit direction (signaling/monitoring direction)

– <TI:=30> ... Single-point indication with time marker CP56Time2a
– <TI=31> ... Double-point indication with time marker CP56Time2a
– <TI=33> ... Bitstring of 32 bits with time marker CP56Time2a
– <TI:=34> ... Measured value, normalized value with time marker CP56Time2a
– <TI:=35> ... Measured value, scaled value with time marker CP56Time2a
– <TI:=36> ... Measured value, short floating-point number with time marker CP56Time2a
– <TI:=45> ... Single command
– <TI:=46> ... Double command
– <TI:=48> … Setpoint adjusting command, normalized value
– <TI:=49> Setpoint adjusting command, scaled value
– <TI=50> … Setpoint adjusting command, short floating-point number
• IEC 60870-5-101/104 data formats in receive direction (command/control direction)

– <TI:=37> ... Metered values with time marker CP56Time2a

DC8-037-2, Edition 11.2020
12.9 Modbus TCP
• Data acquisition by querying

– Reading out the Modbus registers/coils in the base cycle
– Reading out the Modbus registers/coils in a time-controlled manner
– Modbus Response Re-Assembling (if the response is transmitted by the Modbus TCP slave in several
TCP telegrams)
– Data is provided in Modbus registers or coils for queries by the Modbus TCP master
– Conversion of the Modbus Register/Coil data to IEC 60870-5-101/104 data formats
– Scaling of values
– Suppression of intermediate and faulty position for double-point information
– SICAM A8000 internal emulation of the ICE 60870-5-101/-104 general interrogation (the current
values of the Modbus registers/coils are read and forwarded during general queries)
– Time synchronization via time format in Modbus register FC 16 (WRITE MULTIPLE REGISTERS)
– Time synchronization can be selected for each Modbus TCP slave
– Clock synchronization always station selective
– Time synchronization with freely definable time format in Modbus telegram
– Converting IEC 60870-5-101/104 commands to commands in the Modbus register/coils
– Control location (Set, check control location)
– Emulating ACTCON for commands/setpoint values (according to IEC 60870-5-101/104)
– Emulating ACTCON for commands/setpoints (according to IEC 60870-5-101/104), if a command is
discarded by a control location that has not been released
• Counter transmission
– For counter interrogation command (Modbus querying the counters in basic cycle)
– Spontaneous (cyclical/time-controlled Modbus queries)
– Converting the Modbus register data → IEC 60870-5-101/104 metered values
• Redundancy
– Redundant connections

– Protocol element control messages
– Station status
– Station failure

DC8-037-2, Edition 11.2020
12.9 Modbus TCP
Substation Functions - Modbus TCP Slave (MBSiT0)
• LAN/WAN communication protocol according to Modbus TCP

– Modbus TCP “Server”
– Port number = 502
– Communicating with up to 100 Modbus TCP masters
– max. number of connections = 100
– max. number of supported data points (all connections) = 10000
– Supported Modbus slave addresses 1 to 247
– Modbus Unit Identifier 1 to 247, 255
– Modbus TCP with half duplex link transmission procedure
– “ Pre-Fetched Polling” (Number of max. “Client transactions” = 16
– Modbus TCP message protection by TCP/IP Layer
– LAN/WAN
– Ethernet Speed/Duplex
– 100 Mbit/s (full duplex)
– Auto Negotiation, Auto-MDIX (Auto Medium Dependent Interface Crossover)
– Auto Negotiation (100 Mbit/s full duplex), Auto-MDIX
– Auto Negotiation (100 Mbit/s half duplex), Auto-MDIX
– 100 Mbit/s full duplex, Auto-MDIX
– 100Mbit/s half duplex, Auto-MDIX
– TCP/IP Optimierungsparameter
– MTU size (Maximum Transmission Unit)
– TCP min. expected acknowledgment time
• Interoperability according to Section 12.9.7.2 Interoperability Modbus TCP Slave “Server“
• Modbus register/coil addressing

– 16-bit Modbus register
– Modbus register-addresses: 1 (0) to 65535
– Modbus coil-addresses: 1 (0) to 65535
– Modbus register addressing - according to Modbus Standard (YES/NO - station selective)
(Modbus standard addressing = beginning from address 1)

DC8-037-2, Edition 11.2020
12.9 Modbus TCP
• Modbus function codes

– 01 = READ COILS
• Modbus Exception Codes

– 04 = Slave DEVICE FAILURE
• Modbus data formats

– INT16: Signed Integer 16 Bit
– UINT16: Unsigned Integer 16 Bit
– INT32 (H/L): Signed integer 32 bit (HIGH before LOW)
– UINT32 (H/L): Unsigned integer 32 bit (HIGH before LOW)
– INT32 (L/H): Signed integer 32 bit (LOW before HIGH)
– UINT32 (L/H): Unsigned integer 32 bit (LOW before HIGH)
– FLOAT32: Short floating point (IEEE 754)
– FLOAT32 (swapped): Short floating point (IEEE 754) “Swapped”
– FLOAT32 (little-endian): Short Floating Point (IEEE 754) “Little-endian”
– BS16: Bitstring 16 Bit
– SPI: Single-point indication
– DPI: Double-Point Information (OFF before ON)
– DPI: Double-Point Information (ON before OFF)
– SC: Single command
– SC: Single command “pulse”
– DC: Double command
– DC: Double Command “pulse”
– SPI + IV: Single-point indication with invalidity recognition
– DPI + IV: Double-Point Information (OFF before ON) with invalidity recognition
– DPI + IV: Double-Point Information (ON before OFF) with invalidity recognition

DC8-037-2, Edition 11.2020
12.9 Modbus TCP
• IEC 60870-5-101/104 data formats in transmit direction (signaling/monitoring direction)

– <TI:=37> ... Metered values with time marker CP56Time2a
• IEC 60870-5-101/104 data formats in receive direction (command/control direction)

– <TI:=45> ... Single command
– <TI:=46> ... Double command
– <TI:=48> … Setpoint adjusting command, normalized value
– <TI:=49> Setpoint adjusting command, scaled value
– <TI=50> … Setpoint adjusting command, short floating-point number
• Data acquisition by querying

– Data are provided for queries by the Modbus master in Modbus registers or coils
– Converting the IEC 60870-5-101/104 data formats to Modbus register/coils
– Scaling of values
– SICAM A8000 internal emulation of the ICE 60870-5-101/-104 general interrogation with the
current values in the Modbus register/coils
– Time synchronization for the SICAM A8000 substation via NTP
(clock synchronization via Modbus Register is not supported!)
– Conversion of commands in Modbus Register/Coils to IEC 60870-5-101/104 commands
(No emulation of ACTCON/ACTTERM in the Modbus Register/Coils!)
• Counter transmission
– Integrated totals are provided in Modbus Registers for polling by the Modbus TCP Master
• Redundancy
– Redundant connections

DC8-037-2, Edition 11.2020
12.9 Modbus TCP

– Station status
– Station failure
Constraints
• Mode UDP is not supported!
• The "Fragmenting" Modbus telegram is not supported! (the Modbus telegram must be fully transmitted in
a TCP telegram)
• Real-time data via Modbus TCP are not supported!
• Emulation of IEC 60870-5-101/-104 ACTTERM for commands and setpoint values are not supported!
• Listening mode is not supported by Modbus TCP!
• Redundancy is only partially supported!
• BROADCAST addressing at TCP/IP level is not supported!
• BROADCAST addressing with Unit Identifier (station address = 0) is not supported!
• Modbus Function Codes / Exception Codes are not fully supported!
• Only selective data formats in the Modbus registers are supported!

– the Modbus protocol itself does not define any data formats in the Modbus registers
– the supported Modbus data formats are documented in chapter 12.9.8 Modbus data formats .
NOTE
i The Modbus TCP protocol in SICAM A8000 does not support full functionality according to Modbus TCP.
The Modbus protocol defines only the transmission of coils and 16 Bit register values, but not the data
formats in the Modbus registers!
The Modbus TCP protocol in SICAM A8000 supports many of the commonly used data formats.
→ To couple devices using the Modbus TCP protocol, it is always required to check first whether the
required functionality and the required data formats are supported in the master station and in the substa-
tion!

optional DTE
(twisted pair) X4

DC8-037-2, Edition 11.2020
12.9 Modbus TCP
Own Station (Central Station – Modbus TCP Master "Client")

SICAM A8000 Series CP-8000/CPC80 MBCiT0 max. 100 Slaves
CP-8021/CPC80
CP-8022/CPC80
Remote Station (Substation – Modbus TCP Slave "Server")

SICAM A8000 Series CP-8050/CPCI85 MBSiI0 max. 100 Master
SICAM A8000 Series CP-8000/CPC80 MBSiT0 max. 100 Master
CP-8021/CPC80
CP-8022/CPC80
SICAM AK 3 CP-2016/CPCX26 SM-2558/MBSiA0 max. 100 Master
CP-2019/PCCX26
Legacy systems CP-20xx SM-2558/MBSiA0 max. 100 Master
(SICAM AK, SICAM TM, CP-60xx
SICAM BC) CP-50xx
Modbus TCP Master
“Client“ (MBCiI0)
Modbus TCP Master
“Client“ (MBCiI0)
Own Station (Substation – Modbus TCP Slave "Server")

SICAM A8000 Series CP-8000/CPC80 MBSiT0 max. 100 Master
CP-8021/CPC80
CP-8022/CPC80
Remote Station (Central Station – Modbus TCP Master "Client")

SICAM A8000 Series CP-8050/CPCI85 MBCiI0 max. 100 Slaves
SICAM A8000 Series CP-8000/CPC80 MBCiT0 max. 100 Slaves
CP-8021/CPC80
CP-8022/CPC80
SICAM AK 3 CP-2016/CPCX26 SM-2558/MBCiA0 max. 100 Master
CP-2019/PCCX26
Legacy systems CP-20xx SM-2558/MBCiA0 max. 100 Master
(SICAM AK, SICAM TM, CP-60xx
SICAM BC) CP-50xx

DC8-037-2, Edition 11.2020
12.9 Modbus TCP

Siemens devices – – Interoperability according
bility Modbus TCP Slave
“Server“
Third-party system – – Interoperability according
bility Modbus TCP Slave
“Server“
12.9.5 Communication according to Modbus TCP
TCP connection, TCP port number
• The Modbus TCP master in CP-8000/CP-802x establishes a TCP connection to the configured IP address
with the configured TCP port number for each configured Modbus TCP slave (if data is configured in the
send or receive direction).
• After startup, the Modbus TCP slave in CP-8000/CP-802x waits for a TCP connection to be established by
the Modbus TCP master with the configured IP address and the configured TCP port number.
• By default, the port number = 502 is used for Modbus TCP (With default parameter = 0 for TCP the port
number 502 is used). The port number for Modbus TCP can be parameterized for special applications.
Station definition for Modbus TCP Master:
[sc_MBCiT0_station_definition, 1, en_US]
Station definition for Modbus TCP Slave:
[sc_MBSiT0_station_definition, 1, en_US]
Message Description
Structure of the Message

A Modbus TCP message consists of the MBAP-Header, the Modbus function code and the Modbus data.

DC8-037-2, Edition 11.2020
12.9 Modbus TCP
Length
Field [Bytes] Description
FCode 1 Modbus Function Code
Data n Data bytes max. 253
Byte Count 1 Length of answer bytes
MBAP-Header
Length
Field [Bytes] Description Client Server
Transaction Identi- 2 Unambiguous identification Initialized by Mirrored back transaction
fier of a Modbus the Client number of Request
Request/Response Transac-
tion 295
Protocol Identifier 2 = 0000 Initialized by Mirrored back Protocol Identi-
(Modbus Protokoll) the Client fier of Request
Length 2 Number of following bytes Initialized by Initialized by the Server
the Client (Response)
(Request)
Unit Identifier 296 1 Modbus Slave Address for Initialized by Mirrored back Unit Identifier
serial connected device the Client of Request
295 permissible implementation of the transaction identifier: REQUESTs from the MASTER are numbered in ascending order (selectively
per RTU), identical REQUESTs from the MASTER are always sent with the same Transaction-ID.
296 Modbus TCP central stations usually use "Unit Identifier = 255 (0xFF)" for end-end configurations (Master + 1 Slave).

DC8-037-2, Edition 11.2020
12.9 Modbus TCP
Modbus Slave Adresse (“Slave Node Address”, “Unit Identifier”)

With Modbus TCP, a Modbus Slave is addressed only by the unique IP address.
The “Modbus Unit Identifier” (Unit-ID) in the Modbus TCP message format is usually not used.
Possible use of the Unit Identifier (Unit-ID):
Modbus Note
Unit-ID
255 Used in case of single Modbus TCP device (Slave) is connected to Modbus TCP Master ("End-End")
and the connected Modbus TCP Slave supports addressing via IP address.
1 to 247 Used in case of single Modbus TCP device (Slave) is connected to Modbus TCP Master ("End-End")
297 and the connected Modbus Slave does not supports addressing only via IP address.
255 Used when several Modbus TCP devices (Slaves) are connected to a Modbus TCP master and the
connected Modbus Slaves only support addressing via the IP address.
1 to 247 Used if several Modbus TCP devices (Slaves) are connected to a Modbus TCP master and the
297 connected Modbus Slaves do not support addressing only via the IP address.
1 to 247 Used when serial Modbus devices are connected to a Modbus TCP Master via a Serial-Ethernet
297 converter.
NOTE
i Restrictions
• Broadcast addressing with Unicast/Multicast addressing at TCP/IP level is not supported!
• Broadcast addressing with Unit Identifier = 0 is not supported!

The protocol element for Modbus TCP slave supports max. 1 station address per connection.
With Unit-ID = 255 the Modbus station address assigned to the connection will be used.
Modbus Function Codes (FC)

The Modbus message formats are differentiated by the Modbus Function Code (FC).
Function code Designation Description
Modbus register/coil address

Addressing according to Modbus for register values:
• One Modbus register address addresses one 16 Bit register
• The Modbus register address begins with 1 (or 0)
• For each Modbus register the MSB is transmitted first and then the LSB
297 Modbus Slave Station address

DC8-037-2, Edition 11.2020
12.9 Modbus TCP
• Address range for Modbus register address: (0),1 to 65535

With the protocol firmware for SICAM A8000 the address range for Modbus registers is organized sepa-
rately per Modbus function code and limited only by free internal memory. Some third-party systems
have only one common address range, common for all Modbus function codes. Thereby an offset is
defined per function code for the Modbus register address.
Addressing according to Modbus for “Coils”:
• One Modbus coil address addresses one coil “Binary states” (ON/OFF)
• The Modbus coil address begins with 1 (or 0)
• Address range for coils: (0),1 to 65535

According to the Modbus definition, the addressing of the Modbus registers begins from address 1, but on the
line the address “0” is transmitted for Modbus register address 1.
Modbus Register Addressing (typical):

Modbus Function Modbus Modbus
Function code Register Address Register Address
(address list) [dec] (in message) [dec]
1 READ COILS 00001 to 10000 0000 to 9999
2 READ DISCRETE INPUTS 10001 to 20000 0000 to 9999
3 READ HOLDING REGISTERS 40001 to 50000 0000 to 9999
4 READ INPUT REGISTERS 30001 to 40000 0000 to 9999
5 WRITE SINGLE COIL 00001 to 10000 0000 to 9999
6 WRITE SINGLE REGISTER 40001 to 50000 0000 to 9999
15 WRITE MULTIPLE COILS 00001 to 10000 0000 to 9999
16 WRITE MULTIPLE REGISTERS 40001 to 50000 0000 to 9999
: : :
NOTE
i The addressing of the Modbus registers is implemented differently depending on manufacturer and must
Deviating from the definition for the Modbus protocol, some remote terminal units use the Modbus register
start address in the Modbus message on the line starting from 1 instead of starting from 0.
The addressing according to Modbus standard can be set in the parameters of the Station definition
(Connection definition) in the field Addressing MODBUS Standard per station.
[sc_MBSiT0_Adressing_modbus_standard_red, 1, en_US]
Example:
1 0 1
75 74 75

DC8-037-2, Edition 11.2020
12.9 Modbus TCP

1000 999 1000
1374 1373 1374
Modbus Data (Register/Coils)

The Modbus data essentially contain the contents of the Modbus registers or the contents of the Modbus
Coils.
The supported Modbus data formats are documented in chapter 12.9.8 Modbus data formats and chapter
12.9.7 Interoperability Modbus TCP.
The Modbus data format is defined for each data point in the message conversion at the protocol element.
Modbus REQUEST or RESPONSE messages typically contain slave address, function code, coil / register address,
number of bytes and data.
The exact Modbus message structure is documented for each function code in the section Modbus Request /
Response Services.
NOTE
i The Modbus protocol does not define the data formats in the Modbus registers!
The addressing of the Modbus registers is implemented differently depending on manufacturer and must
Message Protection
Modbus TCP does not use additional method for message protection.
With Modbus TCP the message protection takes place by means of the CRC in the TCP/IP-Header.
Modbus Request/Response Services

For the supported Modbus function codes, the message formats are shown schematically in the following
description for Modbus TCP (without TCP/IP frame).
Function Designation Description
code
All Examples for Modbus TCP Request/Response services are shown with Unit-ID=255, but message formats
are also same for Unit-ID 1 to 247.
Modbus TCP Master - MBAB-Header for Read-/Write Request:

DC8-037-2, Edition 11.2020
12.9 Modbus TCP
Request (Query Message)

[HEX] [DEC]
Transaction Identifier Hi xx xx Unambiguous identification of a Modbus Request/
Transaction Identifier Lo xx xx Response Transaction by the Master.
Protocol Identifier Hi 00 0 Protocol Identifier
Protocol Identifier Lo 00 0 Modbus TCP = 0000
Length Hi xx xx Number of bytes starting from (including) Unit-ID
Length Lo xx xx field
Unit Identifier FF, 255 255 …..…. not used
1 to F7 1 to 247 1 to 247 .. Modbus RTU station address
Function Code
Starting Address Hi
Starting Address Lo
Data [n]
Modbus TCP Slave - MBAB-Header of Response for Read-/Write Request:

[HEX] [DEC]
Transaction Identifier Hi xx xx Transaction identifier included in request message
Transaction Identifier Lo xx xx will be sent back in response message (“mirrored”)
Protocol Identifier Hi 00 0 Protocol Identifier
Protocol Identifier Lo 00 0 Modbus TCP = 0000
Length Hi xx xx Number of bytes starting from (including) Unit-ID
Length Lo xx xx field
Unit Identifier FF, 255 255 …..…. not used
1 to F7 1 to 247 1 to 247 .... Modbus RTU station address
Function Code : :
Byte Count : :
Data [n]
NOTE
i BROADCAST addressing is not supported with Modbus TCP!
Modbus TCP transmission: Re-Assembling of the Modbus Response Messages

SICAM A8000 always sends Modbus requests/response messages in a TCP/IP frame.
Some Modbus devices do not send the Modbus Response in a TCP/IP frame. The Modbus TCP/IP master in
SICAM A8000 reassembles a Modbus Response telegram, which is split over several TCP/IP frames (“Re-Assem-
bling”).
Modbus TCP transmission: Polling delay (limitation of the number of Modbus request messages)
Some Modbus devices only allow a limited number of queries within a specified time.
The Modbus TCP/IP master in SICAM A8000 sends a new interrogation or a new telegram to a Modbus substa-
tion only after the expiry of the set “Polling Delay” time.

DC8-037-2, Edition 11.2020
12.9 Modbus TCP
READ COILS, READ DISCRETE INPUTS [FC = 1, 2]

In the query message of the master station (Modbus TCP Master) the starting address and the number of data
points to be transmitted are specified.
Modbus station address [Unit Identifier] 255; 1 to 247, (BROADCAST not supported)
Function code [Function Code] 01 (READ COILS)
02 (READ DISCRETE INPUTS)
Data [Data Coil Status] 8 states (binary information) per byte

Example: Request of Bits 20 to 56 from the slave 17 (Unit-ID = 255) with function code 1 or 2.
[HEX] [DEC]
Transaction Identifier Hi xx xx
Transaction Identifier Lo xx xx
Protocol Identifier Hi 00 0
Protocol Identifier Lo 00 0
Length Hi 00 0
Length Lo 06 6
Unit Identifier FF 255

Example: Response for request for Bit 20 to 56 from slave 17 (Unit-ID = 255) with function code 1 or 2.
[HEX] [DEC]
Length Hi 00 0
Length Lo 08 8
Byte Count 05 5
Data (Coils 27 to 20) CD 205 1100 1101
Data (Coils 35 to 28) 6B 107 0110 1011
Data (Coils 43-36) B2 178 1011 0010
Data (Coils 51-44) 0E 14 0000 1110
Data (Coils 56-52) 1B 27 0001 1011
In the response message each binary information is transmitted with 1 Bit. (0 = binary information OFF; 1 =
binary information ON)
The number of data points requested refers to the individual items of binary information.

DC8-037-2, Edition 11.2020
12.9 Modbus TCP
The least significant bit in the 1st data byte contains the status of the addressed binary information.
READ HOLDING REGISTERS / READ INPUT REGISTERS [FC = 3, 4]

In the query message of the master station (Modbus TCP Master) the starting address and the number of data
points to be transmitted are specified.
Function code [Function Code] 03 (READ HOLDING REGISTERS)
04 (READ INPUT REGISTERS)

Example: Request of Register 108 to 110 from slave 17 (Unit-ID = 255) with function code 3 or 4.
[HEX] [DEC]
Length Hi 00 0
Length Lo 06 6
Starting Address Lo 6B 107

Example: Response for request of register 108 to 110 from slave 17 (Unit-ID = 255) with function code 3
or 4.
[HEX] [DEC]
Length Hi 00 0
Length Lo 09 9
Byte Count 06 6
Data Hi (Register 108) 02 2 0000 0010
Data Lo (Register 108) 2B 43 0010 1011
Data Hi (Register 109) 00 0 0000 0000
Data Lo (Register 109) 00 0 0000 0000
Data Hi (Register 110) 00 0 0000 0000
Data Lo (Register 110) 64 100 0110 0100

DC8-037-2, Edition 11.2020
12.9 Modbus TCP
WRITE SINGLE COIL [FC = 5]

From the Modbus TCP master, binary information and commands are transmitted only as single point informa-
tion to the remote terminal units (slave). The query message contains the data point address and the state.
Function code [Function Code] 5 (WRITE SINGLE COIL)
Status [WRITE Data] 0x00 = OFF; 0xFF = ON

Example: Write request of single coil address 173 in slave 17 (Unit-ID = 255) with function code 5.
[HEX] [DEC]
Length Hi 00 0
Length Lo 06 6
Function Code 05 05
WRITE Data Lo 00 00

Example: Response to write request of single coil address 173 in slave 17 (Unit-ID = 255) with function
code 5.
[HEX] [DEC]
Length Hi 00 0
Length Lo 06 6
Function Code 05 5
WRITE Data Lo 00 0
WRITE SINGLE REGISTER [FC = 6]

Measured values and setpoint values are transmitted from the master station (Modbus TCP Master) to the
slave stations with the message WRITE SINGLE REGISTER. The query message contains the data point address
and the state. A maximum of 1 value is transmitted per message.

DC8-037-2, Edition 11.2020
12.9 Modbus TCP
Function code [Function Code] 6 (WRITE SINGLE REGISTER)
Data point address [Register Address] 0 to 65535
Request (Write Request)

Example: Write the value 0003 into the register 0x0002 of the slave station 17 (Unit-ID = 255) with
function code 6.
[HEX] [DEC]
Length Hi 00 0
Length Lo 06 6
Function Code 06 6
Preset Data Hi 00 0
Preset Data Lo 03 3

Example: Response to writing the value 0003 into the register 0x0002 of the slave station 17 (Unit-ID =
255) with function code 6.
[HEX] [DEC]
Length Hi 00 0
Length Lo 06 6
Function Code 06 6
Preset Data Hi 00 0
Preset Data Lo 03 3
NOTE
i Modbus TCP (Master, Slave) in SICAM A8000 does not support double register values (such as: FLOAT32,
INT32, UINT32,...) with function code = 06 WRITE SINGLE REGISTER!

DC8-037-2, Edition 11.2020
12.9 Modbus TCP
WRITE MULTIPLE COILS [FC = 15]

Multiple binary information / command states can be transmitted from the Modbus TCP master to the remote
terminal units (Slave) with one message. Specified in the query message is the 1st data point address, the
number of coils to be written and the status of every individual coil.
(Coil 1 is addressed with "0").
Function code [Function Code] 15 (WRITE MULTIPLE COILS)
Number of Coils [Quantity of Coils] 1 to 2
Restriction with Modbus RTU Master:
With FC=15 only 1 single command (= 1 Coil) resp. 1 double
command (=2 Coils) can be transmitted!
Status [WRITE Data] 0 = OFF; 1 = ON (1 Bit per coil state)

Example: Write request for multiple coils (10 coils) starting at coil address 20 in slave 17 (Unit-ID = 255)
with coil data 0xCD01 and function code 15.
[HEX] [DEC]
Length Hi 00 0
Length Lo 09 9
Function Code 0F 15
Byte Count 02 2
WRITE Data Hi (Coils 27-20) CD 205
WRITE Data Lo (Coils 29-28) 01 1

Example: Response for write request for multiple coils (10 coils) starting at coil address 20 in slave 17
(Unit-ID = 255) with coil data 0xCD01 and function code 15.
[HEX] [DEC]
Length Hi 00 0
Length Lo 06 6
Function Code 0F 15

DC8-037-2, Edition 11.2020
12.9 Modbus TCP

Example: Response for write request for multiple coils (10 coils) starting at coil address 20 in slave 17
(Unit-ID = 255) with coil data 0xCD01 and function code 15.
[HEX] [DEC]
WRITE MULTIPLE REGISTERS [FC = 16]

Multiple consecutive 16 bit register values can be transmitted from the Modbus TCP master to the remote
terminal units (Slaves) with one message. Specified in the query message is the 1st Data point address, the
number of registers to be written and the register status.
Function code [Function Code] 16 (WRITE MULTIPLE REGISTERS)
Number of registers [No. of Registers] 1 to 125
Number of registers [No. of Registers] 1 to 2
Restriction with Modbus TCP Master:
With FC=16 only 1 value can be transmitted (e.g. 1 Register
with INT16/UINT16 or 2 Register with Float, INT32/UINT32).
Exception: With time synchronization, all required registers are
transmitted in one message with FC = 16.
No. of bytes [Byte Count] 2 to 4

Example: Write request for 2 registers starting at register address 0x0002 with value 00 0A and 01 02
in slave 17 (Unit-ID = 255) with function code 16.
[HEX] [DEC]
Length Hi 00 0
Length Lo 0B 11
Function Code 10 16
Number of Registers Li 02 2
Byte Count 04 4
Data Hi 00 0
Data Lo 0A 10
Data Hi 01 1
Data Lo 02 2

DC8-037-2, Edition 11.2020
12.9 Modbus TCP

Example: Response for write request for 2 registers starting at register address 0x0002 with value 00
0A and 01 02 in slave 17 (Unit-ID = 255) with function code 16.
[HEX] [DEC]
Length Hi 00 0
Length Lo 06 6
Function Code 10 16
Exception Response
If a slave station has not implemented the data queried from the master station or the queried data is not
available, an exception code (EXCEPTION Response) is transmitted instead of the data (Response Message).
Supported Modbus Exception Codes:
EXCEPTION Designation Description MBCiI0 MBSiI0
01 ILLEGAL FUNCTION Function code not implemented ✓ ✓
02 ILLEGAL DATA ADDRESS Data point not available ✓ ✓
03 ILLEGAL DATA VALUE Illegal data
04 Slave DEVICE FAILURE An error has occurred during the ✓ 298 ✓ 298
request
05 ACKNOWLEDGE The remote terminal unit
acknowledges, but cannot reply
to the request immediately
06 Slave DEVICE BUSY The slave station is busy
07 NAK-NEGATIVE ACKNOWLEDGE Function cannot be executed
08 MEMORY PARITY ERROR Parity error detected in memory
12.9.6.1 Overview
IEC 60870-5-101/104 ↔ Modbus TCP is performed by the protocol element. The transmission of the data
towards the Modbus TCP is controlled by the protocol element.
Data in receive direction are converted by the protocol element from the Modbus TCP format → SICAM A8000
internal IEC 60870-5-101/104 format and transferred to the basic system element (no 101/104 blocking). The
transmission of the data on Modbus TCP is controlled by the protocol element.
The conversion of the SICAM A8000 internal IEC 60870-5-101/104 message format ↔ Modbus TCP data
format and the conversion of the address information are called message conversion.
298 only with activated system technical parameter for data points marked faulty

DC8-037-2, Edition 11.2020
12.9 Modbus TCP
The parameterization of the conversion from SICAM A8000 internal IEC 60870-5-101/104 ↔ Modbus TCP
(including address and data format) is to be done with SICAM TOOLBOX II (OPM) using "SIP Message Address
Conversion".
Data Direction Processing type Master Slave

Binary information Receive direction firmware /Rec_binary_information ✓ ✓
Commands Receive direction firmware /Rec_binary_information ✓
Measured values Receive direction firmware /Rec_Values ✓
Setpoint values
Measured values Receive direction firmware /Rec_Measured_Values ✓
Integrated totals Receive direction firmware /Rec_counter_value ✓
Binary information Transmit direction firmware /Trans_binary_information ✓
Commands
Message Transmit direction firmware /Trans_binary_information ✓
Measured values Transmit direction firmware /Trans_Values ✓ ✓
Setpoint values Transmit direction firmware /Trans_Values ✓
Bitstring Transmit direction firmware /Trans_value ✓ ✓
Integrated totals Transmit direction firmware /Trans_value ✓
Time synchroniza- Transmit direction firmware /Trans_timesynchronisation ✓
tion
Parameters
Lk_Reg Link Region Number
The data point assigned to automation unit with the selected region number.
Lk_Comp Link Component Number
The data point assigned to automation unit with the selected component number.
Lk_BSE Link BSE
The data point is assigned to the basic system element in selected automation unit.
Lk_SSE Link SSE
The data point assigned to the selected supplementary system element of the selected
basic system element in the selected automation unit.
Lk_DS Link Destination Station Number
The data point is assigned to selected destination station of the selected supplemen-
tary system element of the selected basic system element in the selected automation
unit.
Lk_Cat Link Category

DC8-037-2, Edition 11.2020
12.9 Modbus TCP
Parameters
0 to 99
Note:
• This Modbus station number is only used internally by SICAM A8000 for telegram
conversion and internal system functions. This Modbus station number is not
transmitted on the line!
• With Modbus TCP the Modbus station will be addressed by the IP address (Unit ID
= 255).
• if a Modbus slave device with serial interface is connected via a Device Server (=
converter “Modbus serial ↔ Modbus TCP), the UNIT-ID is used as Modbus slave.
• The unit ID must be individually parameterized for each connection in the connec-
tion definition parameters of the Modbus TCP/IP master.
MODBUS_Address Modbus Address (Coil- or Register Address):
1 to 65534 (65535)
Note:
• The Modbus address (= coil or register address) which is specified in the device
descriptions in the Register-MAPs is always parameterized.
• According to the Modbus standard, the Modbus register address on the line is
always transmitted with offset = -1
e.g..: parametrized Modbus Register Address = 0001
→ Modbus Register Address = 0000 on the line
• Some device manufacturers do not always adhere to the standard on this point
and require "parameterized Modbus address" = "Modbus address on the line"
→ In the parameters of the connection definition the Modbus addressing on the
line per Modbus station can be set
- Addressing Modbus Standard = YES (Default)
- Addressing Modbus Standard = NO
12.9.6.2 MASTER: Telegram Conversion in Transmit Direction (Master → Slave)

Telegram conversion in transmit direction: IEC 60870-5-101/104 → Modbus TCP
SICAM A8000: IEC 60870-5-101/104 → Modbus TCP Format
Type ID Designation FC Data format
<TI:=30> single-point indication with 05, 06, 15, 16 SPI
CP56Time2a time tag
<TI:=33> Bit string of 32 bits with time marker 06, 16 Bitstring 16 Bit
CP56Time2a
<TI:=34> measured value, normalized value 06 INT16, UINT16
with time tag CP56Time2a 16 INT16, INT32 (H/L), INT32 (L/H),
UINT16, UINT32 (H/L), UINT32 (L/H),
FLOAT32, FLOAT32 (swapped),
FLOAT32 (little-endian)
<TI:=35> Measured value, scaled value with 06 INT16, UINT16
time marker CP56Time2a 16 INT16, INT32 (H/L), INT32 (L/H),

DC8-037-2, Edition 11.2020
12.9 Modbus TCP

<TI:=36> Measured value, floating point 06 INT16, UINT16
number with time tag CP56Time2a 16 INT16, INT32 (H/L), INT32 (L/H),
<TI:=45> Single command 05, 06, 15, 16 SC, SC (pulse)
<TI:=46> Double command 05, 06, 15, 16 DC, DC (pulse), SC
<TI:=47> Incremental command 05, 06, 15, 16 DC, DC (pulse), SC
<TI:=48> Set point command, normalized 06 INT16, UINT16
value 16 INT16, INT32 (H/L), INT32 (L/H),
<TI:=49> Set point command, scaled value 06 INT16, UINT16
16 INT16, INT32 (H/L), INT32 (L/H),
<TI:=50> Set point command, short floating 06 INT16, UINT16
point number 16 INT16, INT32 (H/L), INT32 (L/H),
<TI:=51> Bit string of 32 bit 06, 16 Bitstring 16 Bit
<TI=:100> (General) interrogation command -
299
<TI:=101> Counter Interrogation Command -

<TI:=45> Single command “Time synchroniza- DTx
tion”
Modbus function codes (FC):

<01> ... READ COILS
<02> ... READ DISCRETE INPUTS
<03> ... READ HOLDING REGISTERS
<04> ... READ INPUT REGISTERS
<05> ... WRITE SINGLE COIL
<06> ... WRITE SINGLE REGISTER
<15> ... WRITE MULTIPLE COILS
<16> ... WRITE MULTIPLE REGISTERS
Commands
The address and telegram conversion for commands in the transmit direction are parameterized using the
299 The Modbus protocol does not define general interrogation; in the case of SICAM A8000 internal general queries, the data that has
been queried by the master station is transmitted to the base system element during the next query with the cause of transmission
COT = 20 (queried via station query).

DC8-037-2, Edition 11.2020
12.9 Modbus TCP
Parameter category:
Parameter

• <TI:=47> .. Incremental command
• 0 to 99
tion_code
• FC = 06 .. WRITE SINGLE REGISTER 300
• FC = 15 .. WRITE MULTIPLE COILS
• FC = 16 .. WRITE MULTIPLE REGISTER 300
MODBUS_Address Modbus address (register or coil address):
• 1 to 65535 (single command; double command for FC = 06, 16)

• 1 to 65534 (double command for FC = 05, 15)
The bits of a double command are always next to each other.
MODBUS_Bit-Offset Bit number in the corresponding Modbus register:
• 0 .. Single command, double command [for FC = 05, 15]

• 0 to 15 .. Single command [only FC = 06, 16]
• 0 to 14 .. Double command [only FC = 06, 16]
Double commands use 2 contiguous bits in the same Modbus register.
It is the 1st bit of the double command that is always specified with the
Modbus bit offset.

DC8-037-2, Edition 11.2020
12.9 Modbus TCP
Parameter
MODBUS_Data_Format Data format on the Modbus:
• SC .. Single command
• DC .. Double command [only FC = 15; 06, 16]
• SC (pulse) .. Single command “pulse”
• DC (pulse) .. Double Command “pulse”
MODBUS_Command_Stat Modbus command status: <only double commands>
e
• OFF
• ON
On the parameterized Modbus address/Modus bit offset, the Modbus command
status that has been selected is transmitted (the command output may be
inverted)
Not used with single commands!

format (TI)
SC Single command 45, 46, 47
DC Double command 46, 47
SC (pulse) Single command “pulse” 45
DC (pulse) Double Command “pulse” 46, 47
Note:
As Modbus protocol does not define how data in coils/registers are represented, the Modbus format must be
specified for the telegram conversion. For supported Modbus data formats, see 12.9.8 Modbus data formats.

The “control location” function is used to ensure that commands are only transmitted from authorized sources.
If the function is activated, commands are only transmitted from the protocol element to the remote partner if
the control location (originator address) has been released.
Command output time for single/double commands

Commands can be transmitted on the Modbus as pulses (1 or 2 bits). The protocol element maps the
command output as a pulse to 1 or 2 bits in the Modbus register or 1 or 2 coil addresses of the Modbus slave
with the associated command output time.
The pulse duration for commands with a command qualifier = <0> “no additional definition” must be set on
the protocol element with the system parameter [PRE] MODBUS | Communication functions |
Command transmission | Command output times | Commands without an identifier
(sec).
The pulse duration is set for commands with command qualifier = <1> “short command execution time” on
the protocol element with the system parameter [PRE] MODBUS | Communication functions |
Command transmission | Command pulse duration | Command with short output time
(sec) .
The pulse duration is set for commands with command qualifier = <2> “long command execution time” on the
protocol element with the technical system parameter [PRE] MODBUS | Communication functions |

DC8-037-2, Edition 11.2020
12.9 Modbus TCP
Command transmission | Command output times | Command with long output time
(sec).
Max. 10 commands (single-, double-, regulating step commands) can be active at the same time.
SC single command
A single command with the status SCS = ON or SCS = OFF is transmitted on the Modbus with the current
status.
Modbus data format Command status Command output 2-bit as a
coil or 2-bit in the Modbus
register
SC SCS = ON
x ... Command = ON
SCS = OFF
x ... Command = OFF
SC single command (pulse)

A single command with SCS = ON status will be output on the Modbus as a pulse with the parameterized
command output time.
register
SC (pulse) SCS = ON

(pulse duration)
x ... Command = ON
If a further command with the same IEC 60870-5-101/104 address is initiated during command output in
progress, this one will be discarded with a negative confirmation to the BSE (ACTCON-).
The current pulse output of the command is not affected.
DC double command
A double command or Incremental command is issued as a status on the Modbus with the status DCS =
ON/OFF or RCS = HIGHER/LOWER.

DC8-037-2, Edition 11.2020
12.9 Modbus TCP

register
DC DCS = ON
Modbus_command_sta RCS = HIGHER
te = ON
x ... Command = ON
DCS = OFF
RCS = LOWER
x ... Command = OFF

DC DCS = ON
te = OFF
x ... Command = ON
DCS = OFF
RCS = LOWER
x ... Command = OFF
Double command DC (pulse)

A double command or Incremental command with the status DCS=ON/OFF or RCS=HIGHER/LOWER is trans-
mitted on the Modbus as a pulse with the set command output time.
register
DC (pulse) DCS = ON
te = ON

(pulse duration)
x ... Command = ON
DC (pulse) DCS = OFF
Modbus_command_sta RCS = LOWER
te = ON

(pulse duration)
x ... Command = OFF

DC8-037-2, Edition 11.2020
12.9 Modbus TCP

register
DC (pulse) DCS = ON
te = OFF

(pulse duration)
x ... Command = ON
te = OFF

(pulse duration)
x ... Command = OFF
If an additional command with the same IEC 60870-5-101/104 address is initiated during a pulse output in
progress, this will be discarded with a negative confirmation to the BSE (ACTCON-).
Telegram conversion
conversion.
Telegram elements
• <TI:=47> .. Incremental command
06 .. activation BSE→PRE: is evaluated on the PRE
(only “activation” is permitted)
07 .. Confirmation of activation PRE→BSE:
08 .. Abortion of activation BSE→PRE: not supported.
is confirmed negative (ACTCON-)
09 .. Confirmation of the abortion of acti- PRE→BSE: Abortion of the activation is confirmed negative
vation (ACTCON-)
10 .. Termination of the activation not supported
xx .. other COTs Not accepted/not supported
Information
SCO/DCO/RCO
SCS Single command status [only <TI:=45>]
0 .. OFF Is evaluated (only relevant for single command)

DC8-037-2, Edition 11.2020
12.9 Modbus TCP
Telegram elements
DCS double command state [only <TI:=46>]
RCS Regulating step command [only <TI:=47>]
status
1 .. next step lower is evaluated
2 .. next step higher is evaluated
QOC S/E
0 = execute Is checked for “execution”
1 = select not supported; is confirmed negative (ACTCON-)
tions
Elements of the IEC 60870-5-101/104 telegram that are not listed are not evaluated/not supported!
Indications
The address and telegram conversion for indications in the transmit direction are parameterized using the
Parameter category:
firmware /
Trans_binary_information
Parameter
• <TI:=30> .. single-point indication with CP56Time2a time tag


DC8-037-2, Edition 11.2020
12.9 Modbus TCP
Parameter
• 0 to 99
tion_code
• FC = 16 .. WRITE MULTIPLE REGISTERS
MODBUS_Address Modbus address (coil address register):
• 1 to 65535
• 0 .. Single-point indication [only FC = 05, 15]

• 0 to 15 .. Single-point indication [only FC = 06, 16]
• SPI .. Single-point indication
NOTE
i Indications are only transmitted by the Modbus TCP master if NT = 0 und IV = 0.

format (TI)
SPI Single-point indication 30
Note:
Telegram conversion
conversion.
Telegram elements
TI .. Type Identification • <TI:=30> .. single-point indication with CP56Time2a time
tag
NT .. not topical NT = 1:
Binary information is not transmitted!
IV .. invalid IV = 1:
Binary information is not transmitted!
xx .. not evaluated
Information

DC8-037-2, Edition 11.2020
12.9 Modbus TCP
Telegram elements
SPI 0 .. OFF is evaluated
Time_marker
Measured Values, Setpoints, Bitstrings

The address and telegram conversion for measured values, setpoints, bit strings in the transmit direction are
parameterized using the SICAM Device Manager with the “signals” function or using SICAM TOOLBOX II, OPM II
or for engineering via SICAM WEB with the transmit detailed routing parameters.
Parameter category:
Parameter
• <TI:=33> .. Bit string of 32 bits with time marker CP56Time2a

• <TI:=34> .. Measured value, normalized value with time marker CP56Time2a
• <TI:=35> .. Measured value, scaled value with time marker CP56Time2a
• <TI:=36> .. Measured value, short floating-point number with time marker
CP56Time2a
• <TI:=48> .. Setpoint adjusting command, normalized value
• <TI:=51> .. Bit string of 32 bit
• 0 to 99
tion_code

DC8-037-2, Edition 11.2020
12.9 Modbus TCP
Parameter
MODBUS_Address Modbus Address (Register Address):
• 1 to 65535
• INT16
• INT32 (H/L) [only FC = 16]
• INT32 (L/H) [only FC = 16]
• UINT16
• UINT32 (H/L) [only FC = 16]
• UINT32 (L/H) [only FC = 16]
• FLOAT32 [only FC = 16]
• FLOAT32 (swapped) [only FC = 16]
• FLOAT32 (little-endian) [only FC = 16]
• Bitstring 16 Bit
Y_0%, Y_100%
• For a valid range of values for X_0% and X_100%, see 12.9.8 Modbus data
formats
• <TI:=34, 48> .. Y_0% and Y_100% must not be greater or less than ± 1
• <TI:=35, 49> .. Y_0% and Y_100% must not be less than -32768 or greater
than +32767.
• Value adjustment inactive at Y_0% = 0 and Y_100% = 0
NOTE
i Measured values/setpoints/bitstrings are only transmitted by the Modbus TCP master if NT = 0 und IV = 0.

format (TI)
INT32 (H/L) Signed integer 32 bit (HIGH before LOW) 34, 35, 36, 48, 49, 50
INT32 (L/H) Signed integer 32 bit (LOW before HIGH) 34, 35, 36, 48, 49, 50
UINT32 (H/L) Unsigned integer 16 bit (HIGH before LOW) 34, 35, 36, 48, 49, 50
UINT32 (L/H) Unsigned integer 32 bit (LOW before HIGH) 34, 35, 36, 48, 49, 50
FLOAT32 Short floating point (IEEE 754) 34, 35, 36, 48, 49, 50
FLOAT32 Short floating point (IEEE 754) “Swapped” 34, 35, 36, 48, 49, 50
(swapped)
FLOAT 32 (little- Short Floating Point (IEEE 754) “Little-endian” 34, 35, 36, 48, 49, 50
endian)
Bitstring 16 Bit 16 bit bitstring 33, 51
Note:

DC8-037-2, Edition 11.2020
12.9 Modbus TCP

The “control location” function is used to ensure that setpoints are only transmitted from authorized sources. If
the function is activated, set point step adjusting commands are only transmitted from the protocol element
to the remote partner if the control location (originator address) has been released.
Value adaptation [not for <TI:=33, 51>]

The adaption is only carried out if Y_0% or Y_100% <> 0 has been parameterized.
NOTE
i • If adaption is activated and the raw value of the SICAM A8000 is less than Y_0% or greater than
Y_100%, then the value is limited to X_0% or X_100% and also transmitted.
• If adaptation is not activated (= direct transfer, Y_0% = 0, Y_100% = 0) and the SICAM A8000 raw
value is outside the value range of the selected Modbus data format, then the telegram conversion is
aborted and the error message Format conversion error in transmit direction is set.
Telegram conversion
conversion.

DC8-037-2, Edition 11.2020
12.9 Modbus TCP
Telegram elements
TI .. Type Identification • <TI:=33> .. Bit string of 32 bits with time marker
CP56Time2a
• <TI:=34> .. Measured value, normalized value with time
marker CP56Time2a
• <TI:=35> .. Measured value, scaled value with time marker
CP56Time2a
• <TI:=36> .. Measured value, short floating-point number
• <TI:=48> .. Setpoint adjusting command, normalized value
• <TI:=51> .. Bit string 32 bit
Value is not transmitted!
Value is not transmitted!
[only <TI:=48, 49, 50, 51>]
08 .. Abortion of activation BSE→PRE: not supported
is confirmed negative (ACTCON-)
09 .. Confirmation of the abortion of acti- PRE→BSE: Abortion of the activation is confirmed negative
vation (ACTCON-)
xx .. other COTs not evaluated [only <TI:=33, 34, 35, 36, 37>]
Information
• Scaled value
• IEEE STD 754 = short floating point number
S .. Sign
• Binary counter reading
• Bit string 32 bit
Only bits 0 to 15 are used. Bits 16 to 31 are not evaluated.
QOS S/E [only <TI:=48, 49, 50>]
Time_marker

DC8-037-2, Edition 11.2020
12.9 Modbus TCP
The address and telegram conversion for time synchronization in the transmit direction are parameterized
using the SICAM Device Manager with the “signals” function or using SICAM TOOLBOX II, OPM II or for engi-
neering via SICAM WEB with the transmit detailed routing parameters.
Parameter category:
firmware /Trans_time-
synchronisation
Parameter

• 0 to 99
A different telegram format for time synchronization can be defined for each
Modbus station.
The transmission of the Modbus time synchronization message always takes
place station-selective.
tion_code
• 1 to 65535

DC8-037-2, Edition 11.2020
12.9 Modbus TCP
Parameter
Time synchroniza- When will the time synchronization be performed:
tion
• immediate spontaneous
• cyclic for each 1st Minute (offset = 0 s)
• cyclic for each 1st minute (offset = 30 s)
spontaneous .. Transmission is spontaneously controlled by the single command
<TI:=45>
Offset = 30 s .. Transmission after minute change at 30th second (for SICAM
A8000 systems)
Register_1 (high) Modbus time element:
Register_1 (low)
• Year (high)
Register_2 (high)
Register_2 (low)
• Year (low)
Register_3 (high) • Year - 2000 (high)
Register_3 (low) • Year - 2000 (low)

Register_4 (high) • Month
Register_4 (low) • Day
Register_5 (high) • Weekday
Register_5 (low)
• Day + day of week
Register_6 (high)
Register_6 (low)
• Hour
• Hour + SU
• Minute
• Minute + IV
• Second
• Millisecond (high)
• Millisecond (low)
• Ticks (10ms)
• Ticks (100ms)
• End identifier
NOTE
i For details on the “Modbus time element”, see 12.9.8 Modbus data formats. The freely definable Modbus
time synchronization telegram is sent out excluding the end identifier. If the end identifier is in a Register_n
(low), then this part of the Modbus register is transferred with the value "0".

format (TI)
DTx Date and time (freely definable) 45
Note:

DC8-037-2, Edition 11.2020
12.9 Modbus TCP
Freely definable time synchronization format (example)

Time synchronization controlled by <TI:= 45> single command with the address CASDU = 150, IOA = 145 on
the Modbus address 1500.
Telegram conversion
conversion.
Telegram elements
TI .. Type Identification <TI:=45> .. Single command
Information
SCO
1 .. ON not evaluated
QOC S/E

DC8-037-2, Edition 11.2020
12.9 Modbus TCP
Telegram elements
tions
12.9.6.3 MASTER: Message Conversion in Receive Direction (Master ← Slave)

Message Conversion in receive direction: IEC 60870-5-101/104 ← Modbus TCP
SICAM A8000: IEC 60870-5-101/104 ← Modbus TCP Format
<TI:=30> Single-point information with 01, 02, 03, 04 SPI
CP56Time2a time tag 03, 04 SPI + IV
<TI:=31> Double-point information with time 01, 02, 03, 04 DPI (1 = off, 2 = on)
tag CP56Time2a DPI (1 = on, 2 = off), SPI
03, 04 DPI (1 = off, 2 = on) + IV
DPI (1 = on, 2 = off) + IV
<TI:=33> Bit sting of 32 Bit with time tag 03, 04 Bitstring 16 Bit
CP56Time2a
<TI:=34> measured value, normalized value 03, 04 INT16, INT16 + IV,
with time tag CP56Time2a INT32 (H/L), INT32 (L/H),
UINT16, UINT16 + IV,
UINT32 (H/L), UINT32 (L/H),
FLOAT32 (little endian)
<TI:=35> Measured value, scaled value with 03, 04 INT16, INT16 + IV,
time tag CP56Time2a INT32 (H/L), INT32 (L/H),
<TI:=36> Measured value, floating point 03, 04 INT16, INT16 + IV,
number with time tag CP56Time2a INT32 (H/L), INT32 (L/H),
<TI:=37> Integrated totals with time tag 03, 04 INT16, INT32 (H/L), INT32 (L/H),
CP56Time2a UINT16, UINT32 (H/L), UINT32 (L/H),

<01> ... READ COILS

DC8-037-2, Edition 11.2020
12.9 Modbus TCP
Binary information
Parameter Category:
firmware/Rec_binary_information
Parameters

• 0 to 99
tion_code
• 1 to 65535
• 1 to 65534 [only for double-point information with FC = 01, 02]
The bits of a double-point information are always next to each other.

DC8-037-2, Edition 11.2020
12.9 Modbus TCP
Parameters
• 0 to 15 … Single-point information [only FC=03, 04]

• 0 to 14 … Double-point information [only FC=03, 04]
• 0 to 14 ... Single-point information + IV [only FC = 03, 04]
• 0 to 13 ... Double-point information + IV [only FC = 03, 04]
Both bits of a double-point information must always be in the same Modbus
register!
With the Modbus Bit-Offset always the 1. message of the double-point infor-
mation.
MODBUS_data_format Data format on the Modbus:
• SPI
• DPI (1 = off, 2 = on)
• DPI (1 = on, 2 = off)
• SPI + IV
• DPI (1 = off, 2 = on) + IV
• DPI (1 = on, 2 = off) + IV
Query_cycle Query cycle:
• Basic cycle
• Query cycle 1
• Query cycle 2
• Query cycle 3
• Query cycle 4
Basic cycle: continuous query of all parameterized data.
Query cycle 1 to 4: Query of the parameterized data in the adjustable time frame.
The time grid for query cycle 1 to 4 can be set in the system-technical parame-
ters.
intermediate_pos_t Intermediate position suppression time
• 0 to 255 s
faulty_pos_t faulty position suppression time
• 0 to 255 s

format (TI)
SPI + IV Single-point information + invalid-identifier 30
DPI (1 = off, 2 = Double-Point Information (OFF before ON) 31
on)
DPI (1 = on, 2=off) Double-Point Information (ON before OFF) 31
DPI (1 = off, 2 = Double-Point Information (OFF before ON) + Invalid- 31
on) + IV identifier
DPI (1 = on, 2 = Double-Point Information (ON before OFF) + Invalid- 31
off) + IV identifier
Note:

DC8-037-2, Edition 11.2020
12.9 Modbus TCP
As Modbus protocol does not define representation of data in coil/registers the Modbus format must be speci-
fied for the message conversion. Supported Modbus data formats see 12.9.8 Modbus data formats.

The forwarding of a double-point information from PRE to the BSE with intermediate state (information is not
“ON” and not “OFF”) or faulty state (information is “ON” and “OFF”) will be suppressed for a parameterizable
time.
For the suppression of the intermediate position an intermediate-position suppression time (Parameter
intermediate_pos_t) can be parameterized for each double-point information.
For the suppression of the faulty position a faulty position suppression time (Parameter faulty_pos_t) can
be parameterized for each double-point information.
Message Conversion
tag
CP56Time2a

DC8-037-2, Edition 11.2020
12.9 Modbus TCP

NT .. not topical NT=1 if SPI + IV=1 resp. if DPI + IV=1 (else NT=0)
or
upon receiving Exception Response
Information
1 .. ON supported
intermediate state
1 .. OFF supported
2 .. ON supported
Time tag
Not listed elements of the IEC 60870-5-101/104 message are not rated / not supported!
Measured Value, Bit String

The parameterization of the address and message conversion for measured values and bit pattern in receive
direction is to be done with the SICAM Device Manager with the function “Signals” or the SICAM TOOLBOX II /
OPM or with the parameters for transmit detail routing when using WEB engineering.
Parameter Category:
firmware /Rec_meas-
ured_value

DC8-037-2, Edition 11.2020
12.9 Modbus TCP
Parameters

CP56Time2a
• 0 to 99
tion_code
• 1 to 65535
• INT16
• INT32 (H/L)
• INT32 (L/H)
• UINT16
• UINT32 (H/L)
• UINT32 (L/H)
• FLOAT32
• FLOAT32 (swapped)
• FLOAT32 (little endian):
• INT16 + IV
• UINT16 + IV
Query_cycle Query cycle:
• Basic cycle
• Query cycle 1
• Query cycle 2
• Query cycle 3
• Query cycle 4
Basic cycle: continuous query of all parameterized data.
Query cycle 1 to 4: Query of the parameterized data in the adjustable time frame.
The time grid for query cycle 1 to 4 can be set in the system-technical parame-
ters.

DC8-037-2, Edition 11.2020
12.9 Modbus TCP
Parameters
Y_0%, Y_100%
+32767.
• Value adoption inactive at X_0% = 0 and X_100% = 0
thresh_uncond When changing the value > thres_ uncond, the received value is immediately
forwarded to the BSE.
thresh_additive When changing the value ≤ thres_ uncond, the received value is not immediately
forwarded to the BSE and the additive change monitoring is performed.
Additive Change Monitoring:
If the summed changes (= sign correct addition of changes since the last transfer)
> thres_additive, the received value is passed to the BSE.
thresh_unit • Absolute value [received value from Modbus]
• %

format (TI)
INT16 + IV Signed Integer 16 Bit + Invalid-identifier 34, 35, 36
INT32 (H/L) Signed Integer 32 Bit (HIGH before LOW) 34, 35, 36
INT32 (L/H) Signed Integer 32 Bit (LOW before HIGH) 34, 35, 36
UINT16 + IV Signed Integer 16 Bit + Invalid-identifier 34, 35, 36
UINT32 (H/L) Unsigned Integer 16 Bit (HIGH before LOW) 34, 35, 36
UINT32 (L/H) Unsigned Integer 32 Bit (LOW before HIGH) 34, 35, 36
FLOAT32 Short Floating-Point (IEEE 754) 34, 35, 36
FLOAT32 Short Floating-Point (IEEE 754) “swapped” 34, 35, 36
(swapped)
FLOAT32 (little Short Floating Point (IEEE 754) “Little Endian” 34, 35, 36
endian):
Bitstring 16 Bit Bit string of 16 bit 33
Note:
Value Adaption [not for <TI:=33>]

DC8-037-2, Edition 11.2020
12.9 Modbus TCP
The value adaption is only performed if X_0% or X_100% <> 0 is parameterized.
NOTE
i • If the Modbus value is outside the value range of the selected IEC 60870-5-101/104 type identifier
when the value adoption (= direct transfer) is not activated, then OV = 1 is set.
Change Monitoring
In order to avoid unnecessarily burdening the SICAM A8000 internal and further communication, the meas-
ured value is monitored for changes according to the following rules:
• The first value determined after startup is transmitted immediately
• Each change of quality descriptors IV triggers an immediate transfer, the quality descriptors OV does not
initiate a transfer

Upon receiving, the measured value is monitored for changes. If the deviation from the last spontaneously
transmitted measured value is greater than the parameterized thresh_uncond , then the new measured
value is transmitted immediately to the BSE. Otherwise, the deviation is added to the last spontaneously trans-
mitted measured value, with the correct sign. Only when the amount of this sum exceeds the parameterizable
thresh_additive, the current measured value is spontaneously transmitted to the BSE.

DC8-037-2, Edition 11.2020
12.9 Modbus TCP
Thresh uncond Thresh additive Processing

0 0 → Value is transmitted to the BSE with every change
0 ≠0
≠0 0 • Change greater or equal than thresh_uncond:
→ Value is transmitted to the BSE
≠0 ≠0 • Change greater or equal than thresh_uncond:
→ Value is transmitted to the BSE
• Change less than thresh_uncond
procedure.
The thresholds are to be parameterized for every measured value with the parameter thresh_additive
and the parameter thresh_uncond .
Message Conversion
TI .. Type Identification • <TI:=33> .. Bit sting of 32 Bit with time tag CP56Time2a
• <TI:=34> .. Measured value, normalized value with time tag
CP56Time2a
CP56Time2a
NT .. not topical NT = 1
• at Modbus Format INT16+IV, UINT16+IV if IV=1

• FLOAT32 Format with the value = NAN (Not A Number)
• Reception of Exception Response
IV .. invalid IV = 0
Without value adaption:
• Modbus value outside the range of the selected type identi-

fication
With value adaption:
• Modbus value less than X_0% or greater X_100%

Information

DC8-037-2, Edition 11.2020
12.9 Modbus TCP

S .. sign • scaled value
Only bit 0 to 15 used. Bit 16 to 31 are not evaluated.
Time tag
Integrated totals
Parameter Category:
firmware /
Rec_counter_value
Parameters

• 0 to 99
tion_code
• 1 to 65535

DC8-037-2, Edition 11.2020
12.9 Modbus TCP
Parameters
• INT16
• INT32 (H/L)
• INT32 (L/H)
• UINT16
• UINT32 (H/L)
• UINT32 (L/H)
• FLOAT32
Transmit Counter transmission at:
• cyclic each 1, 2, 3, 5, 10, 15, 30, 60 minutes
IEC-group IEC 60870-5-101/104 counter group:
• Group 1 to 4
Overflow Overflow treatment at:
• 24, 31 bit integer

• 2, 3, 4, 5, 6, 7, 8, 9 decades BCD

format (TI)
FLOAT32 Short Floating-Point (IEEE 754) “swapped” 37
(swapped)
FLOAT32 Short Floating Point (IEEE 754) “Little Endian” 37
(little endian)
Note:
Message Conversion
TI .. Type Identification • <TI:=37> .. Integrated totals with time tag CP56Time2a

DC8-037-2, Edition 11.2020
12.9 Modbus TCP

IV .. invalid IV = 1
• FLOAT32 Format with the value = NAN (Not A Number)

• Reception of Exception Response
03 .. spontaneous when transmitting = periodical data transfer (cyclic each 1, 2, 3,
5, 10, 15, 30, 60 minutes)
rogation
interrogation
Information
S .. sign
Time tag

TI .. Type Identification • <TI:=101> .. counter interrogation command
FRZ RQT FRZ … Freeze
RQT … Request
0
1
all counter groups
2
all counter groups
3
5 Reset counter
all counter groups

DC8-037-2, Edition 11.2020
12.9 Modbus TCP

12.9.6.4 SLAVE: Message Conversion in Transmit Direction (Slave → Master)

Message conversion in transmit direction: IEC 60870-5-101/104 → Modbus TCP
<TI:=30> Single-point information with 01, 02, 03, 04 SPI
CP56Time2a time tag SPI + IV
<TI:=31> Double-point information with time 01, 02, 03, 04 DPI (1 = off, 2 = on) , DPI (1 = on, 2 =
tag CP56Time2a off)
DPI (1 = off, 2 = on) + IV, DPI (1 = on,
2 = off) + IV
<TI:=33> Bit sting of 32 Bit with time tag 03, 04 Bitstring 16 Bit
CP56Time2a
<TI:=34> measured value, normalized value 03, 04 INT16, INT16 + IV,
with time tag CP56Time2a INT32 (H/L), INT32 (L/H),
<TI:=35> Measured value, scaled value with 03, 04 INT16, INT16 + IV,
time tag CP56Time2a INT32 (H/L), INT32 (L/H),
<TI:=36> Measured value, floating point 03, 04 INT16, INT16 + IV,
number with time tag CP56Time2a INT32 (H/L), INT32 (L/H),
<TI:=37> Integrated totals with time tag 03, 04 INT16, INT16 + IV,
CP56Time2a INT32 (H/L), INT32 (L/H),
<TI:=45> Single command 01, 02, 03, 04 SC (pulse)
<TI:=46> Double command 01, 02, 03, 04 DC (pulse)
<TI:=47> Regulating step command 01, 02, 03, 04 DC (pulse)
<TI:=48> Setpoint command, normalized value 03, 04 INT16, INT32 (H/L), INT32 (L/H),

DC8-037-2, Edition 11.2020
12.9 Modbus TCP

<TI:=49> Setpoint command, scaled value 03, 04 INT16, INT32 (H/L), INT32 (L/H),
<TI:=50> Setpoint command, short floating 03, 04 INT16, INT32 (H/L), INT32 (L/H),
point number UINT16, UINT32 (H/L), UINT32 (L/H),
<TI:=100> (General) interrogation command -
The general interrogation command is processed internally on the protocol element and not transmitted to
the remote station. The next time the data is received on the Modbus interface, they are transmitted in
response to the general interrogation command from PRE → BSE.

<01> ... READ COILS
Binary information
Parameter Category:
firmware /Trans_binary_information

DC8-037-2, Edition 11.2020
12.9 Modbus TCP
Parameters

• <TI:=31> .. double-point information with time tag CP56Time2a
• 0 to 99
tion_code
MODBUS_Address Modbus Address (Register - or Coil address):
• 1 to 65535 (single-point information; double-point information with FC =

03, 04)
• 1 to 65534 (double-point information with FC = 01, 02)
The bits of a double-point information are always next to each other.
• 0 .. Single-point information, double-point information [with FC = 01 02]

• 0 to 14 .. Double-point information [only FC = 03, 04]
Both bits of a double-point information are in the same Modbus register!
With the Modbus Bit-Offset always the 1. bit of the double-point informa-
tion.
• SPI
• SPI + IV [only FC = 03, 04]
• DPI (1 = off, 2 = on)
• DPI (1 = on, 2 = off)
• DPI (1 = off, 2 = on) + IV [only FC = 03, 04]
• DPI (1 = on, 2 = off) + IV [only FC = 03, 04]
Transient storage Transient storage:
• Yes [only single-point information]

• No
With transient storage, a message change is saved until transfer (with multiple
changes up to transfer only 1 change is transferred)
Error Behavior Output on Modbus if NT = 1 or IV = 1:
• Keep value
• Output substitute value
Substitute value Substitute value if error behavior is set to Output substitute value.
Valid range of values see 12.9.8 Modbus data formats.
The parameterized substitute value is also used as the initial value.
MODBUS_Command_Stat not used!
e

DC8-037-2, Edition 11.2020
12.9 Modbus TCP
NOTE
i The parameters substitute value and error_behavior must be adapted to the requirements of the
application!

format (TI)
SPI Single-point information 30
SPI + IV Single-point information + invalid-identifier 30
on)
DPI (1 = on, 2 = Double-Point Information (ON before OFF) 31
off)
DPI (1 = off, 2 = Double-Point Information (OFF before ON) + Invalid- 31
on) + IV identifier
DPI (1 = on, 2 = Double-Point Information (ON before OFF) + Invalid- 31
off) + IV identifier
Note:
Message Conversion
tag
CP56Time2a
Depending on the parameter error behavior, either the current
state is kept or the parameterized substitute value is output.
Depending on the parameter error behavior, either the current
state is kept or the parameterized substitute value is output.
xx .. not evaluated
Information
1 .. ON evaluated

DC8-037-2, Edition 11.2020
12.9 Modbus TCP

DPI 0 .. indeterminate or evaluated
intermediate state
1 .. OFF evaluated
2 .. ON evaluated
Time tag
Commands
Parameter Category:
Parameters

• <TI:=47> .. Regulating step command
• 0 to 99
tion_code

DC8-037-2, Edition 11.2020
12.9 Modbus TCP
Parameters
• 1 to 65535 [single command; double command with FC = 03, 04]

• 1 to 65534 [double command with FC = 01, 02]
The bits of a double command are always next to each other.
• 0 .. Single command, Double command [with FC = 01, 02]

• 0 to 14 .. Double command [only FC = 03, 04]
Both bits of a double command must always be in the same Modbus
register!
With the Modbus Bit-Offset always the 1. bit of the double command is
given.
• SC (pulse) .. Single Command pulse

• DC (pulse) .. Double Command pulse
Transient storage not used!
Error Behavior not used!
Substitute value not used!
MODBUS_Command_Stat Modbus Command State: <only double commands>
e
• OFF
• ON
On the parameterized Modbus_Address / Modbus_Bit-Offset the selected
Modbus_ command_state is output (possible inversion of the command output)

format (TI)
SC (pulse) Single Command pulse 45
DC (pulse) Double Command pulse 46, 47
Note:
Command Output Time for Single-/Double Commands

Commands can be transmitted on the Modbus as pulse(s) (1 or 2 bits). The protocol element maps the
command output to 1 or 2 bits in the Modbus register of the Modbus slave with the assigned command
output time.
The command output time (duration of the pulse) is set for commands with qualifier of command = <0> “no
additional definition“ on protocol element with the system technical parameter advanced parameters |
command pulse duration | Command with no addt’l def. (sec) .
The command output time (duration of the pulse) is set for commands with qualifier of command = <1> “short
command execution time“ on protocol element with the system technical parameter advanced parame-
ters | command pulse duration | Command with short pulse duration (sec) .
The pulse duration of commands with qualifier of command = <2> “long pulse duration“ must be set on the
protocol element with the system technical parameter advanced Parameter | command pulse duration |
Commands with long pulse duration (sec) .

DC8-037-2, Edition 11.2020
12.9 Modbus TCP
Max. 10 commands as pulse command (single-, double commands) executed at the same time will be
supported.
Single command SC (pulse)

A single command with command state SCS = ON will be output on the Modbus Register (or Coil) as pulse
with the parametrized command output time.
The command output time must be set so that the command pulse in the Modbus register (or coil) is read out
at least once from the master station (Modbus master) (depending on the interrogation cycle of the Modbus
master).
Modbus Data Format Command state Command output 1 Bit as Coil
or 1 Bit in Modbus Register
SC (pulse) SCS = ON
tp .. command output time

(pulse duration)
x .. Command = ON
Double Command DC (pulse)

A double command or regulating step command with the status DCS = ON/OFF or RCS = higher/lower is output
on the parameterized Modbus Register (or Coil) as pulse with the set command output time.
The command output time must be set so that the command pulse in the Modbus register (or coil) is read out
at least once from the master station (Modbus master) (depending on the interrogation cycle of the Modbus
master).
Modbus Data Format Command state Command Output 2 Bit as Coil
DC (pulse) DCS = ON
te = ON

(pulse duration)
x .. Command = ON
te = ON
tp ... command output time

(pulse duration)
x .. Command = OFF

DC8-037-2, Edition 11.2020
12.9 Modbus TCP
Modbus Data Format Command state Command Output 2 Bit as Coil

DC (pulse) DCS = ON
te = OFF

(pulse duration)
x .. Command = ON
te = OFF

(pulse duration)
x .. Command = OFF
Message Conversion
• <TI:=47> .. Regulating step command
06 .. activation BSE→PRE:
is evaluated on the BSE (only “activation” allowed)
• ACTCON+ when the Modbus Register/Coil is read by the

master during the pulse duration.
• ACTCON- if the Modbus register/coil is not read by the
master during the pulse duration.
08 .. Abortion of activation BSE→PRE: not supported.
09 .. Confirmation of the abortion of acti- PRE→PRE: Abortion of the activation is confirmed negative
vation (ACTCON-)
xx .. other COTs not accepted / not supported
Information
SCO/DCO/RCO
1 .. ON evaluated

DC8-037-2, Edition 11.2020
12.9 Modbus TCP

1 .. OFF evaluated
2 .. ON evaluated
RCS regulating step command [only <TI:=47>]
state
1 .. next step lower evaluated
2 .. next step higher evaluated
QOC S/E
0 = execute Is checked for “execute”
0 .. no additional defini- evaluated
tions
1 .. short pulse duration evaluated
2 .. long pulse duration evaluated
Measured values ,Setpoint values, Binary information, Bit pattern

The parameterization of the address and message conversion for measured values, setpoint values, integrated
totals and bit patterns in transmit direction is to be done with the SICAM Device Manager with the function
“Signale” or the SICAM TOOLBOX II / OPM or with the parameters for transmit detail routing when using WEB
engineering.
Parameter Category:

DC8-037-2, Edition 11.2020
12.9 Modbus TCP
Parameters

CP56Time2a
• <TI:=48> .. Set point command, normalized value
• <TI:=49> .. Setpoint command, scaled value
• 0 to 99
tion_code
• 1 to 65535
• 1 to 65534 [for all Modbus Double register formats (e.g.:FLOAT32)]
• INT16
• INT16 + IV [only <TI:=34, 35, 36, 37>]
• INT32 (H/L)
• INT32 (L/H)
• UINT16
• UINT16 + IV [only <TI:=34, 35, 36, 37>]
• UINT32 (H/L)
• UINT32 (L/H)
• FLOAT32
Error Behavior Output on Modbus if NT = 1 or IV = 1:
• Keep value
• Output substitute value

DC8-037-2, Edition 11.2020
12.9 Modbus TCP
Parameters
Substitute value Substitute value if error behavior is set to Output substitute value.
Valid range of values see 12.9.8 Modbus data formats.
Y_0%, Y_100%
• <TI:=35> .. Y_0% and Y_100% must not be less than -32768 or greater than
+32767.
• Value adjustment inactive at Y_0% = 0 and Y_100% = 0
NOTE
i The parameters substitute value and error_behavior must be adapted to the requirements of the
application!

format (TI)
INT16 Signed Integer 16 Bit 34, 35, 36, 37, 48, 49, 50
INT16 + IV Signed Integer 16 Bit + Invalid-identifier 34, 35, 36, 37
INT32 (H/L) Signed Integer 32 Bit (HIGH before LOW) 34, 35, 36, 37, 48, 49, 50
INT32 (L/H) Signed Integer 32 Bit (LOW before HIGH) 34, 35, 36, 37, 48, 49, 50
UINT16 Unsigned Integer 16 Bit 34, 35, 36, 37, 48, 49, 50
UINT16 + IV Signed Integer 16 Bit + Invalid-identifier 34, 35, 36, 37
UINT32 (H/L) Unsigned Integer 16 Bit (HIGH before LOW) 34, 35, 36, 37, 48, 49, 50
UINT32 (L/H) Unsigned Integer 32 Bit (LOW before HIGH) 34, 35, 36, 37, 48, 49, 50
FLOAT32 Short Floating-Point (IEEE 754) Normal 34, 35, 36, 37, 48, 49, 50
FLOAT32 Short Floating-Point (IEEE 754) “swapped” 34, 35, 36, 37, 48, 49, 50
(swapped)
FLOAT32 (little Short Floating Point (IEEE 754) “Little Endian” 34, 35, 36, 37, 48, 49, 50
endian):
Bitstring 16 Bit Bit string of 16 bit 33
Note:
Value Adaption [not for <TI:=33, 37>]

DC8-037-2, Edition 11.2020
12.9 Modbus TCP
The adaption is only performed if Y_0% or Y_100% <> 0 is parameterized.
• If, when the value adjustment is active, the SICAM A8000 raw value is smaller than Y_0% or greater
Y_100%, then:
– no conversion is carried out
– the error message Format conversion error in transmit direction is set
– on the Modbus, either the parameterized substitute value or, for Modbus TCP, data formats with IV:
→ IV=1; X_0% oder X_100% is output
• If, when the value adjustment is not active (= direct transfer), the SICAM A8000 raw value is outside of
the value range of the selected Modbus TCP data format, then:
– no conversion is carried out
– the error message Format conversion error in transmit direction is set
– on the Modbus, either the parameterized substitute value or, for Modbus TCP, data formats with IV:
→ IV=1; min. or max. Modbus value for the selected Modbus RTU data format is output
• Modbus-formats with IV:

Regardless of the value adjustment, the NT/IV-bit is taken over into the IV-bit of the Modbus format.
Message Conversion

DC8-037-2, Edition 11.2020
12.9 Modbus TCP

TI .. Type Identification • <TI:=33> .. Bit string of 32 bit with time tag CP56Time2a
• <TI:=34> .. Measured value, normalized value with time tag
CP56Time2a
CP56Time2a
Depending on the parameter error behavior, either the
current state is kept or the parameterized substitute value is
output.
Depending on the parameter error behavior, either the
current state is kept or the parameterized substitute value is
output.
Information
• scaled value
S .. sign
• Binary counter reading
QOS S/E [only <TI:=48, 49, 50>]
Time tag

TI .. Type Identification • <TI:=48> .. Set point command, normalized value
06 .. activation BSE→PRE:
is evaluated on the BSE (only “activation” allowed)

DC8-037-2, Edition 11.2020
12.9 Modbus TCP

• ACTCON+ if the Modbus Register is read by the master

within 60 seconds.
• ACTCON- if the Modbus register is not read by the master
within 60 seconds.
08 .. Abortion of activation BSE→PRE: not supported
09 .. Confirmation of the abortion of acti- PRE→PRE:
vation Abortion of the activation is confirmed negative (ACTCON-)
xx .. other COTs not accepted / not supported
Information
QOS ... qualifier of setpoint command
S/E 0 = execute Is checked for “execute”
QL not evaluated
Value • Normalized value
Time tag
12.9.6.5 SLAVE: Message Conversion in Receive Direction (Slave ← Master)

Message Conversion in receive direction: IEC 60870-5-101/104 ← Modbus TCP
<TI:=30> Single-point information with 05, 06,15,16 SPI
CP56Time2a time tag
<TI:=31> Double-point information with time 05, 06,15,16 DPI (1 = off, 2 = on),
tag CP56Time2a DPI (1 = on, 2 = off), SPI
<TI:=34> measured value, normalized value 06, 16 INT16, INT32 (H/L), INT32 (L/H),
with time tag CP56Time2a UINT16, UINT32 (H/L), UINT32 (L/H),
<TI:=35> Measured value, scaled value with 06, 16 INT16, INT32 (H/L), INT32 (L/H),
time tag CP56Time2a UINT16, UINT32 (H/L), UINT32 (L/H),
<TI:=36> Measured value, floating point 06, 16 INT16, INT32 (H/L), INT32 (L/H),
number with time tag CP56Time2a UINT16, UINT32 (H/L), UINT32 (L/H),
<TI:=45> Single command 05, 06, 15, 16 SC, SC (pulse)
<TI:=46> Double command 05, 06, 15, 16 DC, DC (pulse)

DC8-037-2, Edition 11.2020
12.9 Modbus TCP

<TI:=48> Setpoint command, normalized value 06, 16 INT16, INT32 (H/L), INT32 (L/H),
<TI:=49> Setpoint command, scaled value 06, 16 INT16, INT32 (H/L), INT32 (L/H),
<TI:=50> Setpoint command, short floating 06, 16 INT16, INT32 (H/L), INT32 (L/H),
point number UINT16, UINT32 (H/L), UINT32 (L/H),
Time synchronization of the SICAM A8000 component via NTP server (time synchronization with internal
system message).
<01> ... READ COILS
Indications, Commands
The parameterization of the address and message conversion for binary information and commands in receive
direction is to be done with the SICAM Device Manager with the function “Signale” or the SICAM TOOLBOX II /
OPM or with the parameters for transmit detail routing when using WEB engineering.
Parameter Category:
firmware /Rec_binary_information

DC8-037-2, Edition 11.2020
12.9 Modbus TCP
Parameters

• 0 to 99
tion_code
• 1 to 65535 (FC = 06, 16; Single-point information, Single command with FC

= 05, 15)
• 1 to 65534 (double-point information; double command with FC = 05, 15)
The bits of a double-point information/double command are always next to
each other.
• 0 .. [if FC = 05, 15]

• 0 to 15 .. Single-point information/Single command [only FC = 06, 16]
• 0 to 14 .. Double-point information/double command [only FC = 06, 16]
both bits of a double-point information/double command are in the same
Modbus register!
With the Modbus Bit-Offset always the 1. bit of the double-point informa-
tion/double command.
• SPI .. Single-point information

• DPI (1 = off, 2 = on) .. Double-point information [only FC = 06, 16]
• DPI (1 = on, 2 = off) .. Double-point information [only FC = 06, 16]
• SC .. Single command
• DC .. Double command
• SC (pulse) .. Single Command pulse
• DC (pulse) .. Double Command pulse

DC8-037-2, Edition 11.2020
12.9 Modbus TCP
Parameters
IEC-Qualifier of IEC-Qualifier of command: [only <TI:=45, 46>]
command
• none
• short
long•
MODBUS_Command_Stat Modbus Command State: [only double command <TI:=46>]
e
• OFF
• ON
On the parameterized Modbus_Adresse/Modbus_Bit-Offset the parameter-
ized Modbus_ command_state is output (=inversion of the command output)

format (TI)
SPI Single-point information 30
on)
DPI (1 = on, 2 = Double-Point Information (ON before OFF) 31
off)
SC Single command 45
DC Double command 46
SC (pulse) Single Command pulse 45
DC (pulse) Double Command pulse 46
Note:
Single-point information SPI, Double-point information DPI

In receive direction, each binary information state is forwarded 1:1 on change to the BSE. For double-point
information, no intermediate position suppression and no suppression time for faulty state is performed in the
receive direction!

DC8-037-2, Edition 11.2020
12.9 Modbus TCP
Modbus Data Format Modbus Binary Informa- Binary information state in IEC 60870-5-101/104
tion State Modbus Coil/Register
SPI SPI: SPI:
Bit n+0 <0> .. OFF
<0>: 0 .. OFF SPI .. 1 Bit as Coil or 1 Bit in <1> .. ON
<1>: 1 .. ON Modbus Register
DPI DPI: Coding OFF before ON DPI:
(1 = off, 2 = on) (IEC 60870-5-101/104) <0>: .. DIFF
Bit n+1 | n+0 <1>: .. OFF
<0>: 0 | 0 .. DIFF <2>: .. ON
<1>: 0 | 1 .. OFF DPI .. 2 Bit as Coils or 2 Bit in
<3>: .. ERR
Modbus Register
<2>: 1 | 0 .. ON
<3>: 1 | 1 .. ERR
DPI DPI: Coding OFF before ON DPI:
(1 = on, 2 = off) (IEC 60870-5-101/104) <0>: .. DIFF
Bit n+1 | n+0 <1>: .. OFF
<0>: 0 | 0 .. DIFF <2>: .. ON
<1>: 0 | 1 .. ON DPI .. 2 Bit as Coils or 2 Bit in
<3>: .. ERR
Modbus Register
<2>: 1 | 0 .. OFF
<3>: 1 | 1 .. ERR
Legend:
DIFF .. indeterminate or intermediate state
FAULT .. indeterminate state
Single Command SC, Double Command DC

In receive direction, the command state is always forwarded to the BSE on receipt 1:1 without change compar-
ison. Commands are not forwarded to the BSE during general interrogation!

DC8-037-2, Edition 11.2020
12.9 Modbus TCP
SC SC: SCS:
Bit n+0 <0> .. OFF
<0>: 0 .. OFF SC .. 1 Bit as Coil or 1 Bit in <1> .. ON
t1 .. <1> ON command is
forwarded
t2 .. <0> OFF command is
forwarded
DC Modbus_command_state DCS/RCS:
= OFF <0>: .. n.a.
DC: <1>: .. OFF / LOWER
Bit n+1 | n+0 <2>: .. ON / HIGHER
<0>: 0 | 0 .. n.a. DPI .. 2 Bit as Coils or 2 Bit in <3>: .. n.a.
<1>: 0 | 1 .. OFF Modbus Register
<2>: 1 | 0 .. ON t1 .. <2> ON command is
forwarded
<3>: 1 | 1 .. n.a.
t2 .. <1> OFF command is
forwarded
t3 .. <0> n.a. is forwarded
DC Modbus_command_state DCS/RCS:
= ON <0>: .. n.a.
DC: <1>: .. OFF / LOWER
Bit n+1 | n+0 <2>: .. ON / HIGHER
<0>: 0 | 0 .. n.a. DPI .. 2 Bit as Coils or 2 Bit in <3>: .. n.a.
<1>: 0 | 1 .. ON Modbus Register
<2>: 1 | 0 .. OFF t1 .. <1> OFF command is
forwarded
<3>: 1 | 1 .. n.a.
t2 .. <2> ON command is
forwarded
Legend:
n.a. .. not permitted!
Single command SC (Pulse), Double command DC (Pulse)

In receive direction, the ON command state is always transferred to the BSE on receipt 1:1 without change
comparison. The OFF command state is not transferred.
Commands are not forwarded during general interrogation.

DC8-037-2, Edition 11.2020
12.9 Modbus TCP
SC (pulse) SC (pulse): SCS:
Bit n+0 <1> .. ON
<0>: 0 .. OFF SC .. 1 Bit as Coil or 1 Bit in
t1 .. ON command is
forwarded
t2 .. OFF command is not
forwarded
DC (pulse) DC (pulse): DCS/RCS:
Bit n+1 | n+0 <0>: .. n.a.
<0>: 0 | 0 .. n.a. <1>: .. OFF / LOWER
<1>: 0 | 1 .. OFF <2>: .. ON / HIGHER
SC .. 1 Bit as Coil or 1 Bit in
<2>: 1 | 0 .. ON <3>: .. n.a.
Modbus Register
<3>: 1 | 1 .. n.a.
t1 .. ON command is
forwarded
t2 .. OFF command is
forwarded
Legend:
n.a. .. not permitted!
Message Conversion
tag
CP56Time2a
03 .. spontaneous upon change of information state
Information
1 .. ON supported

DC8-037-2, Edition 11.2020
12.9 Modbus TCP

intermediate state
1 .. OFF supported
2 .. ON supported
Time tag

Information (SCO/DCO)
Single command state [only <TI:=45>]
SCS 0 .. OFF supported
1 .. ON supported
Double command state [only <TI:=46>]
DCS 0 .. not allowed supported
1 .. OFF supported
2 .. ON supported
S/E
QOC 0 = execute supported
Qualifier of command
QU 0 .. no additional defini- supported
tions
1 .. short pulse duration supported
2 .. long pulse duration supported

receive direction is to be done with the SICAM Device Manager with the function “Signals” or the SICAM
TOOLBOX II / OPM or with the parameters for transmit detail routing when using WEB engineering.

DC8-037-2, Edition 11.2020
12.9 Modbus TCP
Parameter Category:
firmware /Rec_value
Parameters

CP56Time2a
• 0 to 99
tion_code
• 1 to 65535
• 1 to 65534 [for all Modbus Double register formats (e.g.:FLOAT32)]

DC8-037-2, Edition 11.2020
12.9 Modbus TCP
Parameters
• INT16
• INT32 (H/L) [only FC = 16]
• INT32 (L/H) [only FC = 16]
• UINT16
• UINT32 (H/L) [only FC = 16]
• UINT32 (L/H) [only FC = 16]
• FLOAT32 [only FC = 16]
• FLOAT32 (swapped) [only FC = 16]
• FLOAT32 (little endian) [only FC = 16]
Y_0%, Y_100%
+32767.
• Value adoption inactive at X_0% = 0 and X_100% = 0

format (TI)
FLOAT32 Short Floating Point (IEEE 754) 34, 35, 36, 48, 49, 50
FLOAT32 Short Floating Point (IEEE 754) “Swapped” 34, 35, 36, 48, 49, 50
(swapped)
FLOAT32 (little Short Floating Point (IEEE 754) “Little Endian” 34, 35, 36, 48, 49, 50
endian):
Note:
NOTE
i Modbus data formats that require multiple registers (e.g. FLOAT32) must always be transmitted in the
same Modbus message!
Value Adaption

DC8-037-2, Edition 11.2020
12.9 Modbus TCP
The value adaption is only performed if X_0% or X_100% <> 0 is parameterized.
NOTE
i If the Modbus value is outside the value range of the selected IEC 60870-5-101/104 type identifier when
the value adoption (= direct transfer) is not activated, then OV = 1 is set.
Change Handling
Received values are only passed on to the basic system element by the Modbus slave protocol element if they
are changed.
Since measured values from the Modbus Master → Slave with FC=06, 16 are usually only transmitted sponta-
neously when changed, a measured value change handling with additive threshold value procedure with
thres_uncond and thres_additive is not implemented in Modbus TCP Slave for SICAM A8000.
Message Conversion

DC8-037-2, Edition 11.2020
12.9 Modbus TCP

CP56Time2a
CP56Time2a
NT .. not topical NT = 1 if
• FLOAT32 Format with the value = “NAN“ (“Not A Number“)

or with the vale = ∞
(the last received valid value is passed with NT=1)
• Without value adaption:

– Modbus value outside the range of the selected type
identification
• With value adaption:
– Modbus value less than X_0% or greater X_100%
[only <TI:=34, 35, 36>]
06 .. activation supported [only <TI:=48, 49, 50>]
20 .. Interrogated by station interrogation after receipt of a GI request [only <TI:=34, 35, 36>]
Information
Time tag
12.9.7 Interoperability Modbus TCP
12.9.7.1 Interoperability Modbus TCP Master “Client“


DC8-037-2, Edition 11.2020
12.9 Modbus TCP
parameters.
Note:
values.
Configuration Note
LAN / WAN
Physical layer
Configuration Note
Ethernet (electrical)
For Ethernet (optical) external converters are

Ethernet (optical)
required!
Transmission Speed
Transmission rate Note
10 Mbps
100 Mbps
1000 Mbps
TCP-Port
TCP-Port Note
Registered port number for Modbus TCP.
502
The port number for Modbus TCP IP is fixed by
default.
1 to 65535 User specific port number for Modbus TCP.

DC8-037-2, Edition 11.2020
12.9 Modbus TCP
Connections
Number of Connections Note
max. 100
Note:
each connection can be used as “Server” with individual data base, unique Modbus-Slave Address and unique
TCP/IP-address of the “Client”.
Link Layer (Modbus)
Transmission Mode
TCP/IP Mode
UDP Mode
TCP Mode
Byte Frame Note
8 Data Bits
Procedure Note
Modbus Transaction Number (16 Bit) MBAP Header
Protocol Identifier = "0" (16 Bit) MBAP Header
Length (16 Bit) MBAP Header
Unit Identifier (8 Bit) MBAP Header
CRC is not used by Modbus/TCP

Cyclical Redundancy Check "CRC" (16 Bit)
(TCP-Checksum used only)
MBAP Header … Modbus Application Protocol Header
Link Layer
Semantics Note
Modbus TCP Master (=Client)
Modbus TCP Slave (=Server)

DC8-037-2, Edition 11.2020
12.9 Modbus TCP
Frame length
Semantics Note
TCP Mode:
Maximum Message length 253 Bytes
Semantics Note
Unit Identifier (1 to 247, 255)
1 octet (8 Bit) … Unit Identifier
(Modbus Slave address 1 to 247)
BROADCAST Addressing Mode
Application Layer
Modbus Function code - description Data formats

<20> SPI
01 = READ COILS
<21> DPI (1 = off, 2 = on)
<22> DPI (1 = on, 2 = off)
<20> SPI
<21> DPI (1 = off, 2 = on)
<22> DPI (1 = on, 2 = off)
<20> SPI
<30> SC
<31> SC (pulse)
<35> DC2 (pulse)
<20> SPI
<30> SC
<31> SC (pulse)
<32> DC
<35> DC2 (pulse)

DC8-037-2, Edition 11.2020
12.9 Modbus TCP

<01> INT16
<02> UINT16
<03> INT32 (H/L)
<04> UINT32 (H/L)
<05> INT32 (L/H)
<06> UINT32 (L/H)
<7a> FLOAT32
<7c> FLOAT32 (little endian)
<16> BS16
<20> SPI
<21> DPI (1 = off, 2 = on)
<22> DPI (1 = on, 2 = off)
<23> INT16 + IV
<24> UINT16 + IV
<50> SPI + IV
<51> DPI (1 = off, 2 = on) + IV
<52> DPI (1 = on, 2 = off) + IV
<01> INT16
<02> UINT16
<03> INT32 (H/L)
<04> UINT32 (H/L)
<05> INT32 (L/H)
<06> UINT32 (L/H)
<7a> FLOAT32
<16> BS16
<20> SPI
<21> DPI (1 = off, 2 = on)
<22> DPI (1 = on, 2 = off)
<23> INT16 + IV
<24> UINT16 + IV
<50> SPI + IV
<51> DPI (1 = off, 2 = on) + IV
<52> DPI (1 = on, 2 = off) + IV
<01> INT16
<02> UINT16
<16> BS16
<20> SPI 301
<30> SC 301
<31> SC (pulse) 301
<32> DC 301
<35> DC2 (pulse) 301

DC8-037-2, Edition 11.2020
12.9 Modbus TCP

<01> INT16
<02> UINT16
<03> INT32 (H/L)
<04> UINT32 (H/L)
<05> INT32 (L/H)
<06> UINT32 (L/H)
<7a> FLOAT32
<16> BS16
<20> SPI 301
<30> SC 301
<31> SC (pulse) 301
<32> DC 301
<35> DC2 (pulse) 301
<1xx> DTx
Diagnostics
43 = READ DEVICE Identification (Sub-Code 14)
Other
43 = Encapsulated Interface Transport (Sub-Code 13,14)

DC8-037-2, Edition 11.2020
12.9 Modbus TCP


04 = SERVER (Slave) DEVICE FAILURE
05 = ACKNOWLEDGE
06 = SERVER (Slave) DEVICE BUSY
Retry through the Modbus TCP Master for

serial Modbus slaves (connected via
gateway)
Retry through the Modbus TCP Master for
serial Modbus slaves (connected via
RESPOND
gateway)
Note:
• Requested data which are answered by the Modbus TCP slave with exception code (except 10, 11), are
mapped in CP-8050 with NT = 1 (not topical) - no retries on Modbus TCP level.
• The exception codes are not specially evaluated by the Modbus TCP/IP master - a received exception code
is rated as negative acknowledgment.
12.9.7.2 Interoperability Modbus TCP Slave “Server“

parameters.
Note:
values.

DC8-037-2, Edition 11.2020
12.9 Modbus TCP
Configuration Note
LAN / WAN
Physical layer
Configuration Note
Ethernet (electrical)
For Ethernet (optical) external converters are

Ethernet (optical)
required!
Transmission Speed
Transmission rate Note
10 MBit/s
100 MBit/s
1000 MBit/s
TCP-Port
TCP-Port Note
Registered port number for Modbus TCP.
502
The port number for Modbus TCP IP is fixed by
default.
1 to 65535 User specific port number for Modbus TCP.
Connections
Number of Connections Note
max. 100
Note:
each connection can be used as “Server” with individual data base, unique Modbus-Slave Address and unique
TCP/IP-address of the “Client”.
Link Layer (Modbus)
Transmission Mode
TCP/IP Mode
UDP Mode

DC8-037-2, Edition 11.2020
12.9 Modbus TCP
TCP Mode
Byte Frame Note
8 Data Bits
Procedure Note
Modbus Transaction Number (16 Bit) MBAP Header
Protocol Identifier = "0" (16 Bit) MBAP Header
Length (16 Bit) MBAP Header
Unit Identifier (8 Bit) MBAP Header
CRC is not used by Modbus/TCP

Cyclical Redundancy Check "CRC" (16 Bit)
(TCP-Checksum used only)
Link Layer
Semantics Note
Modbus TCP Master (=Client)
Modbus TCP Slave (=Server)
Frame length
Semantics Note
TCP Mode:
Maximum Message length 253 Bytes
Semantics Note
Unit Identifier (1 to 247, 255)
1 octet (8 Bit) … Unit Identifier
(Modbus Slave address 1 to 247)
BROADCAST Addressing Mode

DC8-037-2, Edition 11.2020
12.9 Modbus TCP
Application Layer

<20> SPI
01 = READ COILS
<21> DPI (1 = off, 2 = on)
<22> DPI (1 = on, 2 = off)
<20> SPI
<21> DPI (1 = off, 2 = on)
<22> DPI (1 = on, 2 = off)
<20> SPI
<30> SC
<31> SC (pulse)
<35> DC2 (pulse)
<20> SPI
<21> DPI (1 = off, 2 = on)
<22> DPI (1 = on, 2 = off)
<30> SC
<31> SC (pulse)
<32> DC
<35> DC2 (pulse)
<01> INT16
<02> UINT16
<03> INT32 (H/L)
<04> UINT32 (H/L)
<05> INT32 (L/H)
<06> UINT32 (L/H)
<7a> FLOAT32
<16> BS16
<20> SPI
<21> DPI (1=off, 2=on)
<22> DPI (1=on, 2=off)
<23> INT16 + IV
<24> UINT16 + IV
<50> SPI + IV
<51> DPI (1 = off, 2 = on) + IV
<52> DPI (1 = on, 2 = off) + IV

DC8-037-2, Edition 11.2020
12.9 Modbus TCP

<01> INT16
<02> UINT16
<03> INT32 (H/L)
<04> UINT32 (H/L)
<05> INT32 (L/H)
<06> UINT32 (L/H)
<7a> FLOAT32
<16> BS16
<20> SPI
<21> DPI (1 = off, 2 = on)
<22> DPI (1 = on, 2 = off)
<23> INT16 + IV
<24> UINT16 + IV
<50> SPI + IV
<51> DPI (1 = off, 2 = on) + IV
<52> DPI (1 = on, 2 = off) + IV
<01> INT16
<02> UINT16
<20> SPI 302
<21> DPI (1=off, 2=on) 302
<22> DPI (1=on, 2=off) 302
<30> SC 302
<31> SC (pulse) 302
<32> DC 302
<35> DC2 (pulse) 302
<01> INT16
<02> UINT16
<03> INT32 (H/L)
<04> UINT32 (H/L)
<05> INT32 (L/H)
<06> UINT32 (L/H)
<7a> FLOAT32
<20> SPI 302
<21> DPI (1=off, 2=on) 302
<22> DPI (1=on, 2=off) 302
<30> SC 302
<31> SC (pulse) 302
<32> DC 302
<35> DC2 (pulse) 302
302 per Modbus register several data points are supported!

DC8-037-2, Edition 11.2020
12.9 Modbus TCP
Diagnostics
43 = READ DEVICE Identification (Sub-Code 14)
Other
43 = Encapsulated Interface Transport (SUB-Code 13, 14)
01 = ILLEGAL FUNCTION Modbus Function Code not implemented

(not available) or Modbus data formats via
several register/coils (e.g.: FLOAT32,
INT32, DP,…) not completely queried.
If the slave internal status for queried data

IV = 1, then: - Old value / substitute value
or - Exception Code = 4 is transmitted
(parameterizable)
05 = ACKNOWLEDGE

DC8-037-2, Edition 11.2020
12.9 Modbus TCP

RESPOND
12.9.8 Modbus data formats
Supported Modbus data formats

Format # Format Designation Register Coil
General formats
1 INT16 Signed Integer 16 Bit ✓ –
2 UINT16 Unsigned Integer 16 Bit ✓ –
3 INT32 (H/L) Signed Integer 32 Bit (HIGH before LOW) ✓ –
4 UINT32 (H/L) Unsigned Integer 32 Bit (HIGH before ✓ –
LOW)
5 INT32 (L/H) Signed Integer 32 Bit (LOW before HIGH) ✓ –
6 UINT32 (L/H) Unsigned Integer 32 Bit (LOW before ✓ –
HIGH)
7a FLOAT32 Short Floating-Point (IEEE 754) ✓ –
7b FLOAT32 (swapped) Short Floating-Point (IEEE 754) “swapped” ✓ –
7c FLOAT32 (little endian): Short Floating Point (IEEE 754) “Little ✓ –
Endian”
16 Bitstring 16 Bit Bit string of 16 bit ✓ –
20 SPI Single-point information ✓ ✓
21 DPI (1 = off, 2 = on) Double-Point Information (OFF before ON) ✓ ✓
22 DPI (1 = on, 2 = off) Double-Point Information (ON before OFF) ✓ ✓
30 SC Single command ✓ ✓
31 SC (pulse) Single Command “pulse” ✓ ✓
32 DC Double command ✓ ✓
33 DC1 Double Command (1 bit) ✓ ✓
35 DC2 (pulse) Double Command “pulse” ✓ ✓
Device specific formats
50 SPI + IV Single-point information + invalid-identi- ✓ –
fier
51 DPI (1 = off, 2 = on) + IV Double-Point Information (OFF before ON) ✓ –
52 DPI (1 = on, 2 = off) + IV Double-Point Information (ON before OFF) ✓ –
53 INT16 + IV Signed Integer 16 Bit + Invalid-identifier ✓ –
54 UINT16 + IV Signed Integer 16 Bit + Invalid-identifier ✓ –
1xx DTx Date & Time (free parameter-settable) ✓ –
Data formats in a Modbus register are always displayed/transmitted in “Big Endian” (HIGH before LOW order).
Data in Modbus Register:

DC8-037-2, Edition 11.2020
12.9 Modbus TCP
Format-1: INT16 – Signed Integer 16 Bit
VZ (Sign): <0> = "+"; <1> = "-"

Value range: -32768 0 to +32767
Format-2: UINT16 – Unsigned Integer 16 Bit
Format-3: INT32 (H/L) – Signed Integer 32 Bit (HIGH before LOW)
VZ (Sign): <0> = "+"; <1> = "-"

Value range: -2 147 483 648 to 0 to +2 147 483 647

DC8-037-2, Edition 11.2020
12.9 Modbus TCP
Format-4: UINT32 (H/L) – Unsigned Integer 32 Bit (HIGH before LOW)
Value range: 0 to 4 294 967 295
Format-5: INT32 (L/H) – Signed Integer 32 Bit (LOW before HIGH)
VZ (Sign): <0> = "+"; <1> = "-"

Value range: -2 147 483 648 to 0 to +2 147 483 647
Format-6: UINT32 (L/H) – Unsigned Integer 32 Bit (LOW before HIGH)
Value range: 0 to 4 294 967 295

DC8-037-2, Edition 11.2020
12.9 Modbus TCP
Format-7a: FLOAT32 – Short Floating Point (IEEE 754)
Value range: ∼1.1 ⋅ 10-38 bis ∼ 3.4 ⋅ 1038

VZ (Sign): <0> = "+"; <1> = "-"
Format-7b: FLOAT32 (swapped) – Short Floating Point (IEEE 754) "swapped"
Value range: ∼1.1 ⋅ 10-38 bis ∼ 3.4 ⋅ 1038

VZ (Sign): <0> = "+"; <1> = "-"
Format-7c: FLOAT32 (little endian) – Short Floating Point (IEEE 754) "swapped"
Value range: ∼1.1 ⋅ 10-38 bis ∼ 3.4 ⋅ 1038

VZ (Sign): <0> = "+"; <1> = "-"

DC8-037-2, Edition 11.2020
12.9 Modbus TCP
Format-16: Bitstring 16 Bit – Bitstring of 16 Bit
Format-20: SPI - Single-point information

Single-point information as coil or 1 bit in Modbus register.
Value range: 0, 1
SPI - Single-point information

<0> = OFF
<1> = ON
Bit (n+0) Coding (IEC 60870-5-101/104)
0 OFF
1 ON
Format 21: DPI (1=off, 2=on) – Double-point information (OFF before ON)
Format 22: DPI (1=on, 2=off) – Double-point information (ON before OFF)
Double-point information in 2 adjacent bits in the Modbus register or as 2 adjacent bits as coil.
Note:
The 2 bits of DPI must be located always in same byte of a Modbus register.

DC8-037-2, Edition 11.2020
12.9 Modbus TCP
Value range: 0 to 3
DPI - Double-Point Information (OFF before ON) - DPI (1 = off, 2 = on)

<1> = OFF
<2> = ON
DPI - Double-Point Information (ON before OFF) - DPI (1 = on, 2 = off)

<1> = ON
<2> = OFF
(IEC 60870-5-101/104)
0 0 0 DIFF DIFF
1 0 1 OFF ON
2 1 0 ON OFF
3 1 1 ERR ERR

Format-30: SC – Single Command

A single command with command state ON or OFF can be sent as coil (1 bit) or as 1 bit Modbus register.

DC8-037-2, Edition 11.2020
12.9 Modbus TCP
Value range: 0, 1
SCS - Single Command State

<0> = OFF
<1> = ON
Single command "ON" SC COIL (n); Register/Bit (n) = ON
Single command OFF SC COIL (n); Register/Bit (n) = “OFF“

SC SCS = ON
x ... Command = ON
SCS = OFF
x ... Command = OFF
Format-31: SC (pulse) – Single Command (pulse)

A single command with command state ON can be sent as pulse with the parametrized command output time
as coil (1 bit) or as bit in the Modbus register .
The command state OFF is not evaluated.

DC8-037-2, Edition 11.2020
12.9 Modbus TCP
Value range: 0, 1
SCP – Command State (Pulse)

<0> = inactive
<1> = active
Single command "ON" SC (pulse) COIL (n); Register/Bit (n) = pulse

SC (pulse) SCS = ON

x ... Command = ON
SCS = OFF The <OFF> state is not evaluated!
Format-32: DC – Double Command (2 Bit)

The command state of a double command resp. regulating step command (2 bit) is transferred with 2 consec-
utive bits as coils or bits in the Modbus register.

DC8-037-2, Edition 11.2020
12.9 Modbus TCP
Value range: 0 to 3
DCS - Double command state [Modbus_command_state = OFF]

<1> = OFF
<2> = ON
DCS - Double command state [Modbus_command_state = ON]

<1> = ON
<2> = OFF
(IEC 60870-5-101/104)
[Modbus_command_state = OFF] [Modbus_command_state = ON]
1 0 1 OFF ON
2 1 0 ON OFF

DC8-037-2, Edition 11.2020
12.9 Modbus TCP

DC DCS = ON
x ... Command = ON
DCS = OFF
RCS = LOWER
x ... Command = OFF

DC DCS = ON
x ... Command = ON
DCS = OFF
RCS = LOWER
x ... Command = OFF
Format-33: DC1 – Double Command (1 Bit)

A double command with command state ON or OFF can be sent as coil (1 bit) or as 1 bit Modbus register.
Value range: 0, 1

DC8-037-2, Edition 11.2020
12.9 Modbus TCP
DCS – Double command state (1 Bit)

<0> = OFF
<1> = ON
Double command ON DC1 COIL (n); Register/Bit (n) = ON
Double command OFF DC1 COIL (n); Register/Bit (n) = “OFF“

DC as Coil or 1 Bit in Modbus Register
DC1 DCS = ON
x ... Command = ON
DCS = OFF
x ... Command = OFF
Format-35: DC2 (pulse) – Double Command (Pulse)

A double command or regulating step command with the command state DCS=<ON>/<OFF> or RCS=<higher>/
<lower> is transferred on Modbus with the set command output time as pulse (2 bits) with 2 coils or 2 bits in
the Modbus register.
The command state <ON> or <HIGH> is transmitted as 1-bit pulse on coil address (n+0 or n+1) or in register
The command state <OFF> or <LOWER> is transmitted as 1-bit pulse on coil address (n+1 or n+0) or in register
Value range: 0 to 3

DC8-037-2, Edition 11.2020
12.9 Modbus TCP
DCP – Double command (Pulse) – per bit

<0> = INAKTIVE
<1> = AKTIV

x ... Command = ON
Modbus_command_state = ON RCS = LOWER

x ... Command = OFF

x ... Command = ON
Modbus_command_state = OFF RCS = LOWER

x ... Command = OFF
Format 50: SPI + IV – Single-point information + Invalid-identifier
<0> = valid
<1> = invalid
SPI (Single-point information):

<0> = OFF
<1> = ON

DC8-037-2, Edition 11.2020
12.9 Modbus TCP
Note:
Format 51: DPI (1=off, 2=on) + IV - Double-point information (OFF before ON) + Invalid-identifier
Format 52: DPI (1=on, 2=off) + IV - Double-point information (ON before OFF) + Invalid-identifier
<0> = valid
<1> = invalid
Double-Point Information (OFF before ON) DPI (1 = off, 2 = on)

<1> = OFF
<2> = ON
Double-Point Information (ON before OFF) DPI (1 = on, 2 = off)

<1> = ON
<2> = OFF
(IEC 60870-5-101/104)
0 0 0 DIFF DIFF
1 0 1 OFF ON
2 1 0 ON OFF
3 1 1 ERR ERR

Note:
• Double-point information must always be transferred completely in a Modbus register byte.

DC8-037-2, Edition 11.2020
12.9 Modbus TCP
Format 53: INT16 + IV – Signed Integer 16 Bit + Invalid-identifier
<0> = valid
<1> = invalid
VZ (Sign):
<0> = "+"
<1> = "–"
Value range: -16384 0 to +16383
Format 54: UINT16 + IV – Unsigned Integer 16 Bit + Invalid-identifier
<0> = valid
<1> = invalid

DC8-037-2, Edition 11.2020
12.9 Modbus TCP
Format-1xx: DTx – Date + Time (free configurable)
Note:
• Only the configured number of bytes will be sent.
• If “End of Frame” is in the HIGH data byte, then the Modbus register will not be sent.
• If “End of Frame” is in the LOW data byte, then the Modbus register will be sent and in the LOW data byte
“0“ will be sent.
Byte sending order:

Data byte 0 (MSB of 1st Modbus register) is sent as 1st data byte.
Data byte 1 (LSB of 1st Modbus register) is sent as 2nd data byte.
Data byte 2 (MSB of 2nd Modbus register) is sent as 3rd data byte.
:
:
Data byte n will be sent as last byte.

Not used Dummy: UI8 [7 to 0] <0>
year (high) year (high) [7 to 0] <0 to 255> year = 2016 = 07E0 [HEX]
→ year (high) = 0x07 [HEX]
year (low) year (low) [7 to 0] <0 to 255> year = 2016 = 07E0 [HEX]
→ year (low) = 0xEX [HEX]
year - 2000 year 2000 (high) [7 to 0] <0 to 255> year = 2016 → 2016 - 2000 = 16 = 0x0010
(high) [HEX]
→ year - 2000 (high) = 0x00 [HEX]

DC8-037-2, Edition 11.2020
12.9 Modbus TCP

year - 2000 (low) year 2000 (high) [7 to 0] <0 to 255> year = 2016 → 2016 - 2000 = 16 = 0x0010
[HEX]
→ year - 2000 (low) = 0x10 [HEX]
Month Month [7 to 0] <1 to 12> Month = 12 (December) → Month = 0x0C [HEX]
Day Day [7 to 0] <1 to 31> Day = 23 → Day = 0x17 [HEX]
Day of week Day of week [7 to 0] <1 to 7> Day of week = Tuesday → Day off week = 0x02
<1> = Monday; <2> = Tuesday; ... <7> = [HEX]
Sunday
day + day of Day [4 to 0] <1 to 31>
week Day of week [7 to 5] <1 to 7>
<1> = Monday; <2> = Tuesday; ... <7> =
Sunday
Hour Hour [7 to 0] <0 to 23> hour = 21 = 0x15 [HEX]
hour + SU Hour [4 to 0] <0 to 23>
summer time (SU) [7] <0, 1>
SU <0> = standard time (winter time)
SU <1> = summer time
Minute Minute [5 to 0] <0 to 59> minute = 59 = 0x3B [HEX]
minute + IV Minute [6 to 0] <0 to 59>
Invalid (IV) [7] <0, 1>
IV <0> = valid
IV <1> = invalid
second second [7 to 0] <0 to 59> second = 32 = 0x20 [HEX]
millisecond millisecond n ⋅ 1 ms (high) [7 to 0] <0 to milliseconds = 998 = 03E6 [HEX]
(high) 255> → millisecond (high) = 0x03 [HEX]
seconds
millisecond (low) milliseconds n ⋅ 1 ms (low) [7 to 0] <0 to milliseconds = 998 = 03E6 [HEX]
255> → millisecond (low) = 0xE6 [HEX]
seconds
→ Ticks (10 ms) = 99 = 0x63 [HEX]
→ milliseconds n ⋅ 100 ms = 9 = 0x09 [HEX]
EOF (End of Note: This time element defines the end of the
Frame) freely configurable time format - this data byte
is no longer sent!
Legend: [7 to 0] = bit position in data byte of Modbus register

< > = valid range of value
12.9.9 Web Server
A web server for internal diagnostics and statistics information is built into the protocol firmware. The web
server itself is implemented on the basic system element - the PRE-specific web pages are only provided by the
protocol element.

DC8-037-2, Edition 11.2020
12.9 Modbus TCP
System Firmware Designation Pre-specific web pages

CP-8000 MBCiT0 Modbus TCP/IP master (Client) ✓
CP-8021 MBSiT0 Modbus TCP/IP slave (Server) ✓
CP-8022
The PRE-specific web pages can be displayed with a common web browser.
The web server is accessed via the HTTP (Hyper Text Transfer Protocol) communication protocol with the port
number 80 or the HTTPS (Hyper Text Transfer Protocol over SSL/TLS) communication protocol with the port
number 443.
With the SICAM Device Manager the integrated web server is called directly via links under the Protocol
details.
[AGPMI0_WEB_DM_start_Webserver, 2, en_US]
With the SICAM TOOLBOX II or with SICAM WEB the integrated web server is called by specifying the IP address
of the automation unit and the protocol element number.
Example:
• https://10.9.19.32/pre0 (pre1, pre2, pre3)
• http://10.9.19.32/pre0 (pre1, pre2, pre3)
NOTE
i By default the integrated web server is deactivated for security reasons. If desired, it can be released for
access by the user using the parameter [PRE] | Advanced parameters | Web server | HTTP
web server.
Supported PRE-specific web pages:

PRE-specific Web Page MBSiT0 MBCiT0
• Overview ✓ ✓
– Connections ✓ ✓
– Routing Transmit ✓ ✓
– Routing Receive ✓ ✓
• Developer Information ✓ ✓
– Dataflow Test ✓ ✓
– Diagnosis (IDE) ✓ ✓
– Diagnosis (IDR) ✓ ✓
– Exception Response ✓ –

DC8-037-2, Edition 11.2020
12.9 Modbus TCP
NOTE
values on a web page are not updated automatically!
The web page shown in the web browser can be updated for example, by starting the web browser’s
update function.
The web pages are displayed in English only!
12.9.9.1 Overview
On the web page Overview general information of the firmware is displayed.
Field Meaning
Firmware Name of the firmware
Protocol Designation of the protocol
Revision Revision of the firmware
Hardware Hardware number (system internal)
Firmware number Firmware number (system internal)
Date and time Current date + time of firmware
Region number Region number (system internal)
Component number Component number (system internal)
BSE Basic system element number (system internal)
ZBG Supplementary system element number “SSE”
(internal)
IP address Own IP address of the assigned interface
Default gateway Default gateway of the assigned interface
Subnet mask Subnet mask of the assigned interface
MAC address MAC address of the assigned interface
Redundancy Current redundancy status of the firmware

DC8-037-2, Edition 11.2020
12.9 Modbus TCP
[MBSiT0_WEB_01_overview, 1, --_--]
[MBCiT0_WEB_01_overview, 1, --_--]

DC8-037-2, Edition 11.2020
12.9 Modbus TCP
NOTE
i In the following sections, screenshots are exemplarily shown only for the firmware MBSiT0 – but apply
accordingly, unless otherwise described – also for the firmware MBCiT0.
12.9.9.2 Connections
The web page Connections displays information on the connection status for each Modbus connection.
Field Remarks
Connection# Firmware internal connection number (with same IP address the same
Connection# is used)
IP address:Port IP address and port number of the connection
Connection TCP Status of the Modbus connection:
connected = TCP connection established
waiting for connection = TCP connection not established
Modbus station SICAM A8000 internal station number (0 to 99)
Unit-ID Modbus unit ID 255;1 to 254
Station state Status of the Modbus station:
OK = Modbus station OK
NOK = Modbus station NOK (failed or not accessible)
#Polls Number of the Modbus “Requests” (since last restart of the firmware)
#Responses Number of the received Modbus “Responses” (since last restart of the firm-
ware)
#Except.returned Number of the received Modbus “Exception Responses” (since last restart of
the firmware)
[MBSiT0_WEB_02_connections, 1, --_--]
[MBSiT0_WEB_02_connections_NOK, 1, --_--]
12.9.9.3 Routing Transmit

Information on the parameterized data points in transmit direction is displayed for each parameterized
Modbus station on the Routing Transmit web page.

DC8-037-2, Edition 11.2020
12.9 Modbus TCP
Field Note
Count Number of parameterized data points in transmit direction (overall for all
stations)
Modbus station Modbus station address (information for routing transmit will be displayed
in groups for each station)
Error Error numbers for MBCiT0
ERR = 0 ....... No error
ERR = 1 ....... SICAM type identification (TI) invalid
ERR = 2 ....... SICAM sub adress invalid
ERR = 3 ....... SICAM address twice used
ERR = 4 ....... MODBUS format faulty
ERR = 5 ....... MODBUS function code not valid
ERR = 7 ....... Bit offset not valid
ERR = 8 ....... MODBUS address mulitple used
ERR = 9 ....... MODBUS address overlap
ERR = 10 ..... MODBUS station number invalid/not configured
ERR = 11 ..... Assignment SICAM TI to MODBUS format faulty
ERR = 12 ..... Type of SIP message adress conversion invalid
ERR = 13 ..... Parameters of adaptation invalid
ERR = 16 ..... Adaptation not permitted
ERR = 21 ..... Transmit priority faulty
ERR = 22 ..... Command state faulty
ERR = 23 ..... MODBUS format with function code=06 not permitted
ERR = 24 ..... Time synch.: period faulty
ERR = 25 ..... Time synch.: time element(s) faulty
ERR = 26 ..... Time synch.: command multiple used
ERR = 28 ..... Double command with function code=05 not permitted
ERR = 29 ..... MODBUS address not permitted
ERR = 31 ..... SICAM type identification (TI) is not supported

DC8-037-2, Edition 11.2020
12.9 Modbus TCP
Field Note
Error Error numbers for MBSiT0:
ERR = 5 ....... Function code faulty
ERR = 6 ....... Assignment of function code to format not allowed
ERR = 7 ....... Assignment of type ident. to MODBUS format inv.
ERR = 8 ....... MODBUS station invalid
ERR = 11 ..... MODBUS address out of range (0-65535)
ERR = 12 ..... MODBUS address overlap
ERR = 13 ..... MODBUS address mulitple used
ERR = 14 ..... Bit offset for indications invalid
ERR = 15 ..... Bit offset invalid (must be 0)
ERR = 17 ..... Substitute value inv. not in range of data format
ERR = 18 ..... Mixed use of indications with/without live-bit
ERR = 20 ..... Transient storage not allowed for type-id
ERR = 22 ..... Error at generation of data base - meas. values
ERR = 23 ..... Error at generation of data base - integ. totals
ERR = 25 ..... FC=01 not allowed when report func. activated
CASDI1, CASDU2 IOA1, IOA2, SICAM A8000 internal IEC60870-5-101/-104 data point address
IOA3
TI IEC60870-5-101/-104 type identification (SICAM A8000 internal)
Format Modbus data format in Modbus register
FC Modbus function code:
Modbus address Modbus address (register or coil address):
• Commands, indications: 1 or 2 bit as a coil or 1 or 2 bit in Modbus

register
• Measured values, integrated totals: 1 or 2 Modbus registers
Value Value in Modbus register [decimal]
Value [Hex] Value in Modbus register [HEX]
Request time Time of last transmission for this data point

DC8-037-2, Edition 11.2020
12.9 Modbus TCP
Routing Transmit (filter not used)
[MBSiT0_WEB_03_routingTransmit_Fehler, 1, --_--]
Routing Transmit - with text filter (the filter affects all fields of the table)
[MBSiT0_WEB_03_routingTransmitFilterText_red, 1, --_--]

DC8-037-2, Edition 11.2020
12.9 Modbus TCP
Routing Transmit - with filter for incorrectly parameterized data points
[MBSiT0_WEB_03_routingTransmit_Filter_Fehler, 1, --_--]
12.9.9.4 Routing Receive

Information on the parameterized data points in receive direction is displayed for each parameterized Modbus
station on the Routing Receive web page.
Field Note
Count Number of parameterized data points in receive direction (overall for all
stations)
Modbus station Modbus station address (information for routing receive will be displayed in
groups for each station)

DC8-037-2, Edition 11.2020
12.9 Modbus TCP
Field Note
Error Error numbers for MBCiT0
ERR = 5 ....... MODBUS function code not valid
ERR = 6 ....... Assignment MODBUS format to function code faulty
ERR = 7 ....... Bit offset not valid
ERR = 8 ....... MODBUS address mulitple used
ERR = 9 ....... MODBUS address overlap
ERR = 10 ..... MODBUS station number invalid/not configured
ERR = 11 ..... Assignment MODBUS format to SICAM TI faulty
ERR = 14 ..... Error at generation of data base - meas. values
ERR = 15 ..... Error at generation of data base - integ. totals
ERR = 17 ..... Thresholds (uncon./add) faulty
ERR = 18 ..... Unit of thresholds not valid
ERR = 19 ..... Query cycle faulty (interrogation)
ERR = 20 ..... DPI suppression time not valid
ERR = 29 ..... MODBUS address not permitted
ERR = 31 ..... SICAM type identification (TI) is not supported
Error Error numbers for MBSiT0:
ERR = 5 ....... Function code faulty
ERR = 6 ....... Assignment of function code to format not allowed
ERR = 7 ....... Assignment of type ident. to MODBUS format inv.
ERR = 8 ....... MODBUS station invalid
ERR = 11 ..... MODBUS address out of range (0-65535)
ERR = 12 ..... MODBUS address overlap
ERR = 13 ..... MODBUS address mulitple used
ERR = 14 ..... Bit offset for indications invalid
ERR = 15 ..... Bit offset invalid (must be 0)
ERR = 16 ..... Command Qualifier not valid
ERR = 19 ..... Command state not valid acc. MODBUS format
ERR = 22 ..... Error at generation of data base - meas. value
CASDI1, CASDU2 IOA1, IOA2, SICAM A8000 internal IEC60870-5-101/-104 data point address
IOA3
TI IEC60870-5-101/-104 type identification (SICAM A8000 internal)
Format Describes how the data is shown in the registers

DC8-037-2, Edition 11.2020
12.9 Modbus TCP
Field Note
FC Modbus function code:
Modbus address Modbus address (register or coil address):
• Commands, indications: 1 or 2 bit as a coil or 1 or 2 bit in Modbus

register
• Measured values, integrated totals: 1 or 2 Modbus registers
Value Value in Modbus register [decimal]
Value [Hex] Value in Modbus register [HEX]
Exception Value not available
Exception codes:
• 01 = ILLEGAL FUNCTION
• 02 = ILLEGAL DATA ADDRESS
• 03 = ILLEGAL DATA VALUE
• 04 = Slave DEVICE FAILURE
• 05 = ACKNOWLEDGE
• 06 = Slave DEVICE BUSY
• 07 = NEGATIVE ACKNOWLEDGE (NAK)
• 8 = MEMORY PARITY ERROR
Request time Time of last reception for this data point
Routing Receive (filter is not used)
[MBSiT0_WEB_04_routingReceive_Fehler, 1, --_--]

DC8-037-2, Edition 11.2020
12.9 Modbus TCP
Routing Receive - with text filter (the filter affects all fields of the table)
[MBSiT0_WEB_04_routingReceive_FilterText_red, 1, --_--]
Routing Receive - with filter for incorrectly parameterized data points
[MBSiT0_WEB_04_routingReceive_Filter_Fehler, 1, --_--]
12.9.9.5 Developer Information – Dataflow Test

The web page Developer Information – Dataflow Test displays the messages transmitted on the internal
interface from PRE ↔ BSE.
The last 200 received or transmitted messages are displayed.
Field Note
No. Message number
Dir Transmission direction
• PRE → BSE: Received data

• BSE → PRE: Transmitted data
DFT Time Logging time
TI IEC 60870-5-101/104 type identification (SICAM A8000 internal)
CASDU1, CASDU2 SICAM A8000 internal IEC 60870-5-101/104 Address of the data point
IOA1, IOA2, IOA3
Station SICAM A8000 internal station number of connection

DC8-037-2, Edition 11.2020
12.9 Modbus TCP
Field Note
COT IEC 60870-5-101/104 cause of transmission (SICAM A8000 internal) (COT =
cause of transmission)
Origin IEC 60870-5-101/104 originator address (SICAM A8000 internal) (Origin =
originator)
Data IEC 60870-5-101/104 status of data point (SICAM A8000 internal)
Quality IEC 60870-5-101/104 quality descriptor of the data point (SICAM A8000
internal)
Time Reception time (MODBUS)
[MBSiT0_WEB_05_dataflowTest, 1, --_--]
“Monitoring Filter“ for Logging

With filter enabled, only messages are logged which are selected by filter. If no filter is selected, all messages
are logged.
The filter must be activated with set filter.
The filters are cleared with Clear all monitoring filters.

DC8-037-2, Edition 11.2020
12.9 Modbus TCP
[MBSiT0_WEB_05_dataflowTestFilter_MonitoringFilter, 1, --_--]
“Suppress Filter“ for Logging

With filter enabled, messages selected by filter are suppressed from logging. If no filter is selected, all
messages are logged.
The filter must be activated with set filter.
The filters are cleared with Clear all suppress filters.
The suppress filter has a higher priority than the monitoring filter. Messages that are to be displayed according
to the monitoring filter and that are to be suppressed according to the suppress filter are not displayed.
[MBSiT0_WEB_05_dataflowTestFilter_MonitorAndSuppressFilter, 1, --_--]

DC8-037-2, Edition 11.2020
12.9 Modbus TCP
12.9.9.6 Developer Information – Diagnosis (IDR)

The web page Developer Information - Diagnosis (IDR) displays basic system element and protocol element
internal diagnosis information.
[MBSiT0_WEB_06_idr, 1, --_--]
Deletion of the IDR diagnosis information on the BSE (“BSE clear diagnosis“)
The IDR diagnosis information on the BSE can be cleared under BSE clear diagnosis with Clear.
Common information of the BSE firmware (“BSE general Information“)
Field Remarks
HW-TYP Hardware type of the BSE firmware
FW-TYP Firmware type of the BSE firmware
Rev: Revision of the BSE firmware
IDR diagnosis information of the BSE firmware (“BSE diagnosis information (IDR)“)
Field Remarks
No Consecutive number
Time Date + time of IDR logging
Name Diagnosis text
Format Format of diagnosis information in next column
• CHAR, HEX8, HEX16, HEX32, DEC8, DEC16, DEC32, FLOAT32

Diagnosis Detail information for IDR diagnosis
Deletion of the IDR diagnosis information on the PRE (“PRE clear diagnosis“)
The IDR diagnosis information on the PRE can be cleared under PRE clear diagnosis with Clear.

DC8-037-2, Edition 11.2020
12.9 Modbus TCP
Common information of the PRE firmware (“PRE general Information“)
Field Remarks
HW-TYP Hardware type of the PRE firmware
FW-TYP Firmware type of the PRE firmware
Rev: Revision of the PRE firmware
IDR diagnosis information of the PRE firmware (“PRE diagnosis information (IDR)“)
Field Remarks
Name Diagnosis text


DC8-037-2, Edition 11.2020
12.9 Modbus TCP
12.9.9.7 Developer Information – Diagnosis (IDE)

The web page Developer Information – Diagnosis (IDE) displays protocol element internal diagnosis and
statistics information.
[MBSiT0_WEB_07_ide, 1, --_--]
Deletion of the IDE diagnostic information on the PRE (“Clear diagnosis“)

The IDE diagnosis information on the PRE can be cleared under Clear diagnosis with Clear.
Common information on the IDE diagnosis (“General information“)
Field Remarks
Cleared at Date + time of the last deletion of the IDE diagnosis information
Query at Last query time of the IDE diagnosis information
Redundancy state Current redundancy status of the PRE firmware

DC8-037-2, Edition 11.2020
12.9 Modbus TCP
Common information on the IDE diagnosis (“Polling“)
Field Remarks
Min. cycle time (all stations OK) Minimum cycle time of all stations that are OK
Max. cycle time (all stations OK) Maximum cycle time of all stations that are OK
Min. cycle time Minimum cycle time
Avg. cycle time (last 10 cycles) Average cycle time (of the last 10 cycles)
Information on the control location function of the PRE (“Control location“)
Field Remarks
If the control location function is activated, the activated control locations
are displayed.
Note: this function is currently not supported with MODMT2!
Receive error statistics (“Receive Errors“)
Field Remarks
Parity error Number of detected “parity errors”
Framing error Number of detected “byte frame errors”
Overrun error Number of detected “overflow errors”
With overflow error the system load is too high – the received bytes can no
longer be processed correctly.
Sync character invalid Number of detected “synchronization character errors”
End character invalid Number of detected “end character errors"
Receive buffer full Number of detected “receive buffer full” errors
Length invalid Number of detected "length wrong” errors
Checksum error Number of detected “checksum errors”
Invalid gap Number of detected errors for impermissible gap in the message (gap
between 2 bytes within a message)
NOTE
i With Ethernet protocols these points of information are not relevant (=0)!
Status of the communication connection (“Station state“)

For each station the current status and the statistics on the number of failures and retries are displayed.
Field Remarks
Station Station number (internal)
State OK ….… Communication connection OK
NOK ..… Communication connection NOK (failed)
Retry count Number of retries since the last Clear diagnosis
NOK count Number of failures of the communication connection since the last Clear
Diagnosis
Retry rate Number of retries in % since the last Clear diagnosis

DC8-037-2, Edition 11.2020
12.9 Modbus TCP
Chronological list of retries and station failures (“Station History”)
Field Remarks
Time Date + time of the communication fault (OK, NOK, Retry)
State Status:
• Retry no x … Retry number x

• Station OK
• Station NOK

DC8-037-2, Edition 11.2020
12.10 DNP3
12.10 DNP3
12.10.1 Introduction
The DNP3 protocol is a standardized serial or LAN communication protocol for devices communicating point-
to-point, multi-point traffic or via LAN.
For CP-8000, CP-8021, CP-8022 the following protocol firmware for DNP3 are available:
DNPST0 CP-8000, CP-8021, CP-8022 DNP3 Slave “serial”
DNPMT0 CP-8000, CP-8021, CP-8022 DNP3 Master “serial”
DNPiT1 CP-8000, CP-8021, CP-8022 DNP3 TCP/IP Slave
DNPiT2 CP-8000, CP-8021, CP-8022 DNP3 TCP/IP Master
The DNP3 protocol (Distributed Network Protocol) is an official communication standard for telecontrol. The
protocol is used as transmission protocol between control systems and remote stations.
Typically the messages are transmitted over serial connections (ITU-T V.24 (EIA-232) / ITU-T V.28 (EIA-422) as
well as over a network (TCP/IP) based infrastructure. The DNP3 telecontrol protocol is standardized and further
developed by the DNP Users Group.
The DNP3 protocol defines one controlling station with one or multiple controlled stations.
The controlling station and the controlled stations work with a communication protocol according to DNP3 in
multi-point traffic.
The supported functionality (interoperability) of the various devices can be seen in the devicespecific "DNP3
Device Profile Document" – for SICAM A8000 in section 12.10.8 Interoperabilität (DNP3 Device Profile Docu-
ment).
Multi-point traffic describes a communication 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 controlling station, whereby with DNP3, in contrast to other protocols, the controlled station
can also send unsolicited spontaneous data (=unsolicited responses).
The protocol element DNPMT0 supports the communication of a single MASTER with up to max. 20 remote
stations (Slaves) on a communication line.
Every controlled station is assigned an unambiguous station number (DNP source address) in the range 0 to
65519. The controlling station is also assigned an unambiguous station number in the range 0 to 65519.
The station number 65535 (0xFFFF) is used for the simultaneous addressing of all stations (= BROADCAST).
With Broadcast no reply (Response Message) is transmitted from the Slaves to the Master.
The protocol element DNPST0 enables the serial communication of one controlled station with one controlling
station.
As “Multi-Slave” the protocol element DNPiT1 enables the communication of one or multiple controlled
station(s) with one or multiple controlling stations over Ethernet (LAN/WAN). A controlled station can only
communicate with one unambiguous controlling station.
With DNP3 a transmission of data can be initiated not only by the Master-station but also by the Slave-station.
A data transmission consists either of a “Request-Reply Sequence” (= Query/Response Type) to selectively
addressed slaves or of a simultaneous addressing of all connected remote terminal units (= Broadcast/No
Response Type).
The cyclic queries or data messages provided for the DNP3 communication protocol are transmitted by the
controlling station. Data from the controlled station to the controlling station can be transmitted either as
direct response to a query or as spontaneous data without preceding query.
Schematic configuration DNP3 “seriell”:

DC8-037-2, Edition 11.2020
12.10 DNP3
Schematic configuration DNP3 TCP/IP:
On the application layer the DNP3 communication protocol uses the “unbalanced transmission procedure”, in
order to communicate with more than one slave. However on the link layer the communication between the
two stations takes place as “balanced transmission procedure”. As a result it is also possible for the slave to
send spontaneous data, so-called (unsolicited responses), without preceding call of the master.
That means either, that as primary station the controlling station initiates messages transmissions and the
controlled station processes these and replies or that, in the case of unsolicited responses, the controlled
station starts the message transmission spontaneously and the controlling station processes these and replies
or acknowledges.
In multi-point traffic with polling mode the DNP3 protocol requires only a “half duplex” transmission medium
and can be used in a star or linear structure.
If the controlled stations use the spontaneous data transmission (=unsolicited responses), then with a “half
duplex” transmission medium collisions can occur in the message traffic. Either because multiple controlled
stations or the master and one controlled station begin with the data transmission at the same time. If colli-
sions are to be completely avoided, then this is only achieved with a “voll duplex” transmission medium and
only one controlled station may be connected to one master.
In all other cases collisions can occur and consequently the data transmission can be impaired.

DC8-037-2, Edition 11.2020
12.10 DNP3
12.10.2 Functions
Communication between one central station and one or several substations.
• Unbalanced multi-point traffic according to DNP3

DNPMT0 is central station (Master), DNPST0 is substation (Slave)
– Data Acquisition by Polling (Station Interrogation)
– Acquisition of events (transmission of data ready to be sent, unsolicited responses)
– General interrogation, Outstation interrogation
• Max. connections (number of supported DNP Slaves): 100303
– RS-485 – balanced interface according to V.11
• Interoperability according to Chapter 12.10.8 Interoperabilität (DNP3 Device Profile Document)
Communication between one central station and one or several substations via Ethernet (TCP/IP).
• Unbalanced multi-point traffic according to DNP3

DNPiT2 is central station (Master), DNPiT1 is substation (Slave)
– Acquisition of events (transmission of data ready to be sent, unsolicited responses)
– LAN (TCP/IP)
• Interoperability according to Chapter 12.10.8 Interoperabilität (DNP3 Device Profile Document)
• Clock synchronization according to NTP (Network Time Protocol) according to RFC 1305
– NTP Client: Clock synchronization with one or several NTP-Server
– NTP Server: integrated NTP server for clock synchronization of one or several NTP clients
• SICAM TOOLBOX II connection over LAN/WAN (“remote connection”)

– connection via proprietary TCP/IP protocol (one SICAM TOOLBOX II session can be served at the
same time)
303 because of performance, required response time and limited storage capacity fewer max. 20

DC8-037-2, Edition 11.2020
12.10 DNP3
• Web Server
– Integrated web server to display connection-/statistic-/developer information
– Access to the web server with standard web browser via HTTP (Hyper Text Transfer Protocol)
Restrictions
• Only selected DNP3 function codes are supported
• The supported DNP3 functionality (Object/Variation, …) is documented in chapter 12.10.8 Interoperabi-

lität (DNP3 Device Profile Document) .
• File transfer is not supported
• max. data index (per data type) = 65535
NOTE
i SICAM A8000 as DNP3 TCP/IP slave may only be connected once to a master station. In the station defini-
tion (connection definition), the DNP destination address and DNP source address may always only occur
once. It is not possible to connect multiple substations (e.g., DNP source address 1000, 1001, and 1002) to
the same master station (e.g., DNP destination address 10). If this is still necessary, a substitute value for
the DNP destination address and DNP source address can be set for a maximum of 4 connections.
Serial Communication
ment.
optional DTE
Unbalanced interchange circuit (V.24/V.28) RS 232 X2 RXD, TXD, CTS 304, RTS, DCD, DTR,
asynchronous DSR/VCC, GND
Balanced interface (V.11) RS-485 (2-wire) / RS-422 X3 TXD+/RXD+, TXD-/RXD- (2-wire)
(4-wire) asynchronous TXD+, TXD-, RXD+, RXD- (4-wire)
Balanced interface (V.11) RS-485 (2-wire) / RS-422 X2 → CM-0829 RXD, TXD, CTS, RTS, DCD, DTR, DSR/
(4-wire) asynchronous (CM-0819 305) VCC, GND (to CM-08x9)
Optical interface (multimode fibre optic) ring X2 → CM-0821 RXD, TXD, CTS, RTS, DCD, DTR, DSR/
VCC, GND (to CM-0821)
Unbalanced interchange circuit (V.24/V.28) RS 232 X6306 RXD, TXD, CTS, RTS, DCD, DTR, DSR,
asynchronous GND
LAN/WAN Communication (TCP/IP)

optional DTE
(twisted pair) X4

305 does not support RS-422

DC8-037-2, Edition 11.2020
12.10 DNP3
Own Station (Central station - DNP3 Master serial)

SICAM A8000 Series CP-8000/CPC80 DNPMT0 max. 10 Slaves
CP-8021/CPC80
CP-8022/CPC80
Remote station (Substation - DNP3 Slave serial)

SICAM A8000 Series CP-8050/CPCI85 DNPSI0 max. 1 Master
SICAM A8000 Series CP-8000/CPC80 DNPST0 max. 1 Master
CP-8021/CPC80
CP-8022/CPC80
SICAM AK 3 CP-2016/CPCX26 SM-2551/DNPSA0 max. 1 Master
CP-2019/PCCX26 SM-0551/DNPSA0
Legacy systems (SICAM CP-20xx SM-2551/DNPSA0 max. 1 Master
AK, SICAM, TM SICAM BC, CP-50xx SM-0551/DNPSA0
SICAM EMIC) CP-60xx DNPST0
12.10.8 Interoperabilität
(DNP3 Device Profile
Document)
Own station (substation - DNP3 slave serial)

SICAM A8000 Series CP-8000/CPC80 DNPST0 max. 1 Master
CP-8021/CPC80
CP-8022/CPC80
Remote station “Central station“ (DNP3 Master serial)

SICAM A8000 Series CP-8050/CPCI85 DNPMI0 max. 100 Slaves
SICAM A8000 Series CP-8000/CPC80 DNPMT0 max. 10 Slaves
CP-8021/CPC80
CP-8022/CPC80
SICAM AK 3 CP-2016/CPCX26 SM-2551/DNPMA0 max. 20 Slaves
CP-2019/PCCX26 SM-0551/DNPMA0
Legacy systems CP-20xx SM-2551/DNPMA0 max. 20 Slaves
(SICAM AK, SICAM TM, CP-60xx SM-0551/DNPMA0
SICAM BC) CP-50xx

DC8-037-2, Edition 11.2020
12.10 DNP3

Document)
Document)
Own Station (Central station - DNP3 TCP/IP Master)

SICAM A8000 Series CP-8000/CPC80 DNPiT2 max. 4 Slaves
CP-8021/CPC80
CP-8022/CPC80
Remote station (Substation - DNP3 TCP/IP Slave)

SICAM A8000 Series CP-8050/CPCI85 DNPiI1 max. 100 Master
SICAM A8000 Series CP-8000/CPC80 DNPiT1 max. 4 Master
CP-8021/CPC80
CP-8022/CPC80
SICAM AK 3 CP-2016/CPCX26 SM-2558/DNPiA1 max. 100 Slaves
CP-2019/PCCX26 SM-2551/DNPSA0 307 max. 1 Master
SM-0551/DNPSA0 307
Legacy systems (SICAM CP-20xx SM-2558/DNPiA1 max. 100 Slaves
AK, SICAM TM, SICAM BC, CP-60xx SM-2551/DNPSA0 307 max. 1 Master
SICAM EMIC) CP-50xx SM-0551/DNPSA0 307
DNPiT0 max. 2 Slaves
Document)
Document)
Own station (Substation - DNP3 TCP/IP Slave)

SICAM A8000 Series CP-8000/CPC80 DNPiT1 max. 4 Master
CP-8021/CPC80
CP-8022/CPC80
307 additional serial/Ethernet converter (device server) is required

DC8-037-2, Edition 11.2020
12.10 DNP3
Remote station (Central station DNP3 TCP/IP Master)

SICAM A8000 Series CP-8050/CPCI85 DNPiI2 max. 100 Slaves
SICAM A8000 Series CP-8000/CPC80 DNPiT2 max. 4 Slaves
CP-8021/CPC80
CP-8022/CPC80
SICAM AK 3 CP-2016/CPCX26 SM-2551/DNPMA0 307 max. 20 Slaves
CP-2019/PCCX26 SM-0551/DNPMA0 307
Legacy systems CP-20xx SM-2551/DNPMA0 307 max. 20 Slaves
(SICAM AK, SICAM TM, CP-60xx SM-0551/DNPMA0 307
SICAM BC) CP-50xx
Document)
Document)
12.10.5 Communication according to DNP3
Bit transmission layer (DNP3 serial)

The bit-transmission layer deals primarily with the physical media over which the protocol is transmitted. The
bit transmission layer handles e.g. the state of the media (free or busy) and the synchronization via the media
(start and stop).
Most commonly, DNP3 is used over a simple, asynchronous, serial transmission such as RS-232 or RS-485 with
the physical media wire line and fiber optic. In addition, transmission can be made via Ethernet.

DC8-037-2, Edition 11.2020
12.10 DNP3
[dwdalila-030314.vsd, 1, en_US]
Figure 12-8 Bit transmission layer
Data transmission package begins with a data header and a 16-bit CRC (cyclic redundancy check) of all 16
bytes of the package is performed.
A package is part of a complete message submitted through the physical layer. The maximum size of the data
package is 256 Byte. Each package has a 16-bit source address and a 16-bit destination address, which can
also be a common address (0xFFFF).
The 10-byte link layer header contains:
• The address information
• A 16-bit start code
• The package length
• A data transfer control byte

DC8-037-2, Edition 11.2020
12.10 DNP3
The data transmission control byte indicates the cause of the data transmission and the status of the logical
connection. The data transmission control byte can have the following values:
• ACK (data transmission confirmation)
• NACK (negative confirmation)
• Connection needs reset
• Connection is reset
• Request data transmission confirmation of the package

If a data transmission acknowledgment is requested, the receiver must respond with an ACK data package
when the package is received and the CRC checks were successful. If no data transmission confirmation is
requested, no response is required.
Pseudo Transport Layer

The pseudo-transport layer segments application messages into multiple data transmission packages.
The pseudo transport layer introduces a single byte function code for each package. The byte function code
indicates what the data transmission package is:
• The 1st package of a message
• The last package of a message
• Both (for individual message packages)

The function code provides a continuous packet sequence number. This package sequence number is incre-
mented with each package and allows the transport layer of the recipient to analyze the package.
[dwtrfnct-030314, 1, en_US]
Figure 12-9 Pseudo Transport Layer
Application Layer
The application layer responds to received messages and creates messages based on the necessity and availa-
bility of the user data. As soon as messages are available, they are sent to the pseudo transport layer. The
messages are segmented here, sent to the data link layer and transferred through the physical layer.
If the data that is to be sent is too large for an individual application message, a number of application
messages can be created and sent in a sequential manner. Each message is an independent application
message. Their only connection with each other is the label in all messages that says that more messages will
follow. Only the last message does not contain this label. Each application message refers to a fragment due
to the fact that the user data may be fragmented. A message can thus be a single fragment message or a
multi-fragment message.
Application packages from DNP3 slaves are normally responses to queries. A DNP3 slave can also send a
message without a request, thus, an unsolicited response.
As in the data link layer, application fragments can be sent with a confirmation request. An application confir-
mation indicates that a message was not only received, but rather it was also syntactically analyzed without
any errors. A data transmission confirmation or an ACK indicate only that the transmission package was
received and that the CRC checks were error-free. Each application package begins with an application layer
header, followed by one or more object heads/object data. The application layer header contains an applica-
tion control code and an application function code.
If one of the following conditions is fulfilled, then the application control code contains labels:

DC8-037-2, Edition 11.2020
12.10 DNP3
• The package is a multi-package message.
• An application layer acknowledgment is requested for the package.
• The package is not requested.

The application control code contains a continual application layer number. With this application layer
number, the receiving application layer can recognize alien packages or lost packages.
The application function code in the header of the application layer indicates the cause or the requested func-
tion in the message. While DNP3 allows a number of data types in a single message, it also allows only an
individual query for a data type within the message.
Examples for application function codes include:
• Acknowledgments for confirmation on the application layer
• Read and write
• Select and execute (SBO (select before operate), controls)
• Direct control (for switching objects without SBO)
• Save and delete (for counters)
• Restart (both cold and warm)
• Enable and disable non-requested messages
• Selection of the classes

The application function code in the header of the application layer applies for all object headers. Thus, the
application function code applies for all data within the message package.

DC8-037-2, Edition 11.2020
12.10 DNP3
[dwaplay1-030314.vsd, 1, en_US]
Figure 12-10 Application Layer – Part 1

DC8-037-2, Edition 11.2020
12.10 DNP3
[dwaplay2-040314.vsd, 1, en_US]
Figure 12-11 Application Layer – Part 2
12.10.6 Parameters and Properties
12.10.6.1 Parameter and Functions DNP3 Slave serial

[PRE] | Common settings
Note: Some parameters may not be displayed until the interface is selected.
Address of the link layer Permitted range = 1 to 65519
Interface Possible interface selection: Permitted range = X2, X3, X6
CP-8000: X2, X3 Default setting = not used
CP-8021: X2, X3
CP-8022: X2, X3, X6

DC8-037-2, Edition 11.2020
12.10 DNP3

Baud Rate The DNP3 slave protocol in SICAM Permitted range = 50, 75, 100,
A8000 supports baud rates in the 134.5, 150, 200, 300, 600, 1050,
range of 50 Bd to 38400 Bd. 1200, 1800, 2000, 2400, 4800,
9600, 19200, 38400
Data bits Number of data bits per data byte Permitted range = 5, 6, 7, 8 Bit
on the bit transmission layer. Standard setting = 8 Bit
Parity Parity bit for data bytes on the bit Permitted range = no, even, odd
transmission layer. parity
Default setting = no parity
Stop bits Stop bits for data bytes on the bit Permitted range = 1, 1.5, 2 Bit
transmission layer. Standard setting = 1 Bit
Transmission facility Most of the time settings are fixed Permitted range:
and cannot be changed for the
predefined transmission facilities.
• freely definable
Connection of the transmission • Direct connection (RS-232)
facilities as described (additional • Direct connection (RS-485)
adapters / cables are sometimes
required) • Direct connection (RS-422)
• Direct connection (RS-485
with CM-08x9)
• Direct connection (optical)
with CM-0847
default setting = freely definable
[PRE] | Common settings | free defineable interface modem
DCD-evaluation The status line DCD (Data Carrier Permitted range =
Detect) can be used for message
synchronization in receive direction
• disabled
and for “Collision Detection”. • enabled
Default setting = disabled
Continuous level moni- If the DCD signal is active longer Permitted range =
toring time (tcl) than the set time, a continuous 0 … no continuous level moni-
level error is reported. toring
0.1 to 6553.5 s
Default setting = 10.0 s
Run out time (tn) After the message transmission has Permitted range = 0 to 32767 ms
ended the transmit signal level Default setting = 11ms
(RTS) is first switched off after
expiry of the run-out time.
Pause time (tp) Before a message transmission, a Permitted range = 0 to 32767 ms
parameter-settable pause time is Default setting = 30 ms
maintained before the transmission
level is switched on with RTS.
Bounce suppression time If the DCD signal is used by very old Permitted range = 0 to 65535 ms
(tbounce) modems (usually relay output) Default setting = 10 ms
then a bouncing of the DCD signal
can be suppressed. The DCD signal
is evaluated only after the bounce
suppression time.

DC8-037-2, Edition 11.2020
12.10 DNP3

Transmission delay at If a continuous level on the line has Permitted range =
level (tcldly) been detected (for example DCD 0 … no transmission delay at level
signal active) and after the trans- 0.1 to 6553.5 s
mission delay has elapsed, it will be
Default setting = 0.2 s
sent anyway so that a defective
DCD input does not result in a
blockade of the transmitter.
Disable time (tdis) After receiving a message, the Permitted range = 0 to 32767 ms
receiver can be disabled for the Default setting = 0 ms
disable time so that incorrect char-
acters - caused by switching off the
transmission level controlled by the
remote station - are not processed.
Stability monitoring time Stability monitoring time (tstab) Permitted range = 0 to 65535 ms
(tstab) The new DCD state is only used for
message synchronization after the
stability monitoring time has
expired.
Set-up time (tv) After switching on the transmission Permitted range = 0 to 32767 ms
level with RTS, the message trans- Default setting = 100ms
mission is started after the set-up
time has expired.
X2: DTR/VCC Pin as output Power supply for the transmission Permitted range =
for device at interface X2 (e.g.
CM-0829).
• DTR state line according to
V.24/V.28 [not with CP-8021,
D-SUB 9-pole: Voltage via DTR (5V/ CP-8022]
10V)
Pin RJ45: Voltage via VCC Pin
• 5V supply voltage for ext.
transmission facilities
[CP-8021, CP-8022]
• 10V supply voltage for ext.
transmission facilities
[PRE] | HTTP Webserver
HTTP web server With a web browser protocol- Permitted range = disabled,
internal information can be enabled
displayed. Default setting = disabled
Note:
For safety reasons, the web server
should be disabled in a system in
operation.
[PRE] | Redundancy
Listening mode (failure Failure monitoring time in listening Permitted range = 0, 1 to 60000 s
monitoring time) mode. 0 .. monitoring disabled
1 to 60000 .. monitoring time

DC8-037-2, Edition 11.2020
12.10 DNP3

Operation if passive DNP3 protocol functionality on the Permitted range =
line in the redundant state passive.
• Transmitter active, normal
• Transmitter active, normal mode
mode
•
Transmitter active, listening
– The DNP3 protocol works mode
identically as in the • Transmitter “tristate”, listening
redundancy state active. mode
– Received data is passed Standard setting = 0
on by the BSE with the
status R=1. These
messages can be filtered
out by the BSE during
transmission at inter-
faces.
• Transmitter active, listening

mode
• Transmitter “tristate”, listening

mode
– the electrical interface is
switched to “tristate”.
– the electrical interfaces
of redundant compo-
nents can be switched in
parallel.
– Failure monitoring via
listening mode
Delay time passive → With redundancy switching from Permitted range = 0, 1 to 2000 s
aktive passive → active, the protocol 0 .. no delay
element is switched to active with 1 to 2000 … delay time
delay.
[PRE] | message repetitions
Retries for data message The number of maximum message Permitted range = 0 to 255
SEND/CONFIRM (station repetitions to be performed. Standard setting = 2
selective)
Retries for data messages The number of maximum message Permitted range = 0 to 255
SEND/NO REPLY (broadcast) repetitions to be performed. Standard setting = 2
Retries for INIT-messages The number of maximum message Permitted range = 0 to 255
SEND/CONFIRM (station repetitions to be performed. Standard setting = 1
selective)
[PRE] | Advanced parameters
Startup delay This delay is used to update the Permitted range = 5 to 200 s
process image on the PRE after a Default setting = 20 s
restart before the communication
is started.
[PRE] | Advanced Parameter | DNP time settings
Max. random transmission To avoid collisions, a random Permitted range = 0 to 1000 ms
delay number in the range from 0 to the
maximum is determined and added
to the configured transmission
delay.

DC8-037-2, Edition 11.2020
12.10 DNP3

Timeout SELECT → OPERATE Maximum waiting time between a Permitted range = 0.1 to 6553.5 s
SELECT and an OPERATE for a valid Default setting = 20 s
command.
Timeout emulate SELECT Waiting time to simulate a SELECT Permitted range = 0.1 to 6553.5 s
command if SELECT before Default setting = 2 s
OPERATE is not supported by the
master but is still needed.
With an OPERATE command, a
SELECT is first generated and then
an EXECUTE after this time has
expired.
Timeout transmit delay Only after this timeout, the data Permitted range = 0.01 to 655.35 s
will be sent. This is to avoid colli- Standard setting = 0
sions. This time should be set
differently for all connected substa-
tions.
Timeout application expected acknowledgment time for Permitted range = 0.1 to 6553.5 s
confirmation the acknowledgment of the appli-
cation layer. This acknowledgment
can only be sent after a complete
fragment has been received. The
time must be adjusted accordingly.
[PRE] | Advanced Parameter | Default data object settings
For binary input (object Data types are referenced with Permitted range =
1) Object/Variation. A request for data
without a defined variation (any
• binary input
variation) is answered with the • binary input with status
default object variant parameter- default setting = binary input
ized here.
For binary input change Data types are referenced with Permitted range =
(object 2) Object/Variation. A request for data
• binary input without time
variation) is answered with the • binary input with time
default object variant parameter- • binary input with relative time
ized here.
default setting = binary input with
time
For double binary input Data types are referenced with Permitted range =
• binary input
ized here.
change (object 4) Object/Variation. A request for data
default object variant parameter- • binary input with relative
ized here.
time

DC8-037-2, Edition 11.2020
12.10 DNP3

For binary output (object Data types are referenced with Permitted range =
• binary output
variation) is answered with the • binary output with status
default object variant parameter- default setting = binary output with
ized here. status
For binary counter (object Data types are referenced with Permitted range =
• 16 bit counter
variation) is answered with the • 16 bit counter with status
default object variant parameter- • 32 bit counter
ized here.
• 32 bit counter with status
default setting = 32 bit counter
with status
For frozen binary counter Data types are referenced with Permitted range =
• 16 bit counter
ized here.
with status
For binary counter change Data types are referenced with Permitted range =
event (object 22) Object/Variation. A request for data
• 16 bit counter with time
default object variant parameter- • 32 bit counter with time
ized here.
with status
ized here.
with status
For analog input (object Data types are referenced with Permitted range =
• 16 bit analog input with status
variation) is answered with the • 16 bit analog input without
default object variant parameter- status
ized here. • 32 bit analog input with status
• 32 bit analog input without
status
• short floating point
default setting = 32 bit analog
input with status

DC8-037-2, Edition 11.2020
12.10 DNP3

For analog input change Data types are referenced with Permitted range =
• 16 bit analog change event
with time
variation) is answered with the
default object variant parameter- • 16 bit analog change event
ized here. without time
with time
without time
• short floating point analog
change event without time
change event with time
For analog input deadband Data types are referenced with Permitted range =
• 16 bit analog input deadband
variation) is answered with the • 32 bit analog input deadband
default object variant parameter- • short floating point analog
ized here. input deadband
input deadband
For analog output status Data types are referenced with Permitted range =
• 16 bit analog output status
variation) is answered with the • 32 bit analog output status
ized here. output status
output status
[PRE] | Advanced Parameter | Settings time management
Correction time for clock The time in the clock synchroniza- Permitted range = - 60.00 to +
synchronization command tion command is changed by the 60.00 ms
automatically determined transmis- Default setting = 0 s
sion time and correction time.
Time format in receive The DNP3 protocol uses UTC time Permitted range =
direction format on the line.
This parameter defines how the
• use received time without
(conversion)
time format is converted from
DNP3 to SICAM A8000. • from UTC to local time with
DST correction
• from UTC to local time
without DST correction
default setting = from UTC to local
time with DST correction

DC8-037-2, Edition 11.2020
12.10 DNP3

Time format in transmit The DNP3 protocol uses UTC time Permitted range =
• use local time
time format is converted from • from local time incl. DST

SICAM A8000 to DNP3. correction to UTC
• from local time without DST
correction to UTC
default setting = from local time
incl. DST correction to UTC
Cycle time for sending Time grid for cyclic time setting.
Permitted range = 0 to 65535 s
clock synchronization 0 .. no cyclic time setting
command Default setting = 300 s
[PRE] | Advanced Parameter | Settings in receive direction
Maximum application frag- Maximum byte number of a DNP3 Permitted range = 100 to 2048
ment size fragment in receive direction Standard setting = 2048
Maximum link fragment size Maximum link fragment size of a
Permitted range = 20 to 292
DNP3 message in receive direction
[PRE] | Advanced Parameter | Settings in transmit direction
ment size fragment in transmit direction Standard setting = 2048
Maximum link fragment size Maximum link fragment size of a Permitted range = 20 to 292
DNP3 message in transmit direction Standard setting = 292
[PRE] | Advanced Parameter | Settings unsol. message
Number of class 1 events Permitted range = 0 to 100
for transmission
for transmission
for transmission
Data class 1 as unsol. Permitted range =
message
• wait for release from the
remote station
Data class 2 as unsol.
message
Data class 3 as unsol.
message
Send data as unsolicited Permitted range = yes, no
messages Default setting = yes
Retrycount for unsolicited Permitted range = 0 to 255
messages Standard setting = 5
Send static data as unso- Permitted range = yes, no
licited messages Default setting = no
Timeout unsolicited Permitted range = 0, 0.1 to 6553.5
messages offline retry . s
Timeout unsolicited Permitted range = 0, 0.1 to 6553.5
messages retry . s

DC8-037-2, Edition 11.2020
12.10 DNP3

Behavior unsol. messages Permitted range =
after startup
• yes, transmit immediately
• only after time setting is
complete
• only after request data class 0
is complete
Default setting = yes, transmit
immediately
Delay of class 1 events Permitted range = 0 to 65535 s
for transmission
for transmission
for transmission
[PRE] | Advanced parameters | Software test points
… The software test points may only Permitted range = yes, no
be used under the guidance of Default setting = no
experts for error detection! Once
the fault isolation is completed,
software checkpoints must always
be turned off.
[PRE] | Advanced Parameter | common DNP settings
Failure management in Permitted range =
transmit direction
• NT-Bit = 1
• IV-Bit = 1
• NT-Bit and/or IV-Bit = 1
Standard setting = NT-Bit = 1
CROB command mode According to DNP3 standard, no Permitted range =
other telegrams may be received
between SELECT and OPERATE,
• DNP3 compliant
otherwise the current SELECT will • non DNP3 compliant
be deleted. default setting = non DNP3
In case of non DNP3 compliant, compliant
SELECT will not be cleared.
DNP3 Source address Address of the DNP3 Slaves Permitted range = 1 to 65519
(Link address of the own station) Standard setting = 1
DNP3 Destination address Address of the DNP3 Master Permitted range = 1 to 65519
(Address of the remote station) Standard setting = 1
Send multifragments Permitted range = yes, no
Default setting = yes
Conversion of NT-Bit Conversion of NT-Bit (IEC Permitted range =
60870-5-101/104) to DNP3 state.
• to DNP3 status “offline“
• to DNP3 status “communica-
tion lost“
tion lost“ and “offline“
default setting = to DNP3 status
“communication lost”

DC8-037-2, Edition 11.2020
12.10 DNP3

Data link layer confirma- Selection of the DNP3 acknowledg- Permitted range =
tion ment for sent data.
With no acknowledgment an
• no acknowledgment
“Application Confirmation” is • only for multi fragments
expected for multi fragments. • always expect acknowledg-
ment
Default setting = no acknowledg-
ment
Delete oldest event if If the event buffer overflows, Permitted range = yes, no
event buffer overflow depending on the selection Default setting = yes
• the oldest data will be deleted
•
the newest data will be
deleted
[PRE] | Advanced Parameter | project specific DNP settings
Force binary input varia- If the default data type for “binary Permitted range = yes, no
tion 1 input (object 1)” is set to “binary Default setting = no
input”, this release causes a
suppression of the automatic
switchover to “binary input varia-
tion 2” All DNP3 states are replaced
by “online”.
Keep/holding back event If the event memory for single / Permitted range = yes, no
data on BSE - binary indi- double messages on the DNP3 Default setting = no
cation protocol is full, this data can be
restored to the BSE.
The following priority levels must
be parameterized for this:
• Indications: High priority class

1
Keep/holding back event If the event memory for measured Permitted range = yes, no
data on BSE - measured values on the DNP3 protocol is full, Default setting = no
values this data can be restored to the
BSE.
The following priority levels must
be parameterized for this:
• Measured values: Low priority

class 2
• Integrated totals: Middle
priority class 2
Save events on SD card Permitted range = yes, no
Default setting = no
Enable SCBO (check back When this function is enabled, the Permitted range = yes, no
before operate) commands (SELECT + OPERATE) are Default setting = no
processed differently from the
DNP3 standard.
While a SELECT is running, a new
received SELECT is discarded and
the old one remains active.
An OPERATE is valid for the first
SELECT.

DC8-037-2, Edition 11.2020
12.10 DNP3

Optimized indexing Permitted range = yes, no
Redundancy used as hot Enable the hot standby redundancy Permitted range =
standby function.
• normal redundancy mode
• hot standby active data base
• hot standby passive data base
Default setting = normal redun-
dancy mode
Target BSE for hot standby Basic system element with redun- Permitted range =
container dant DNP3 protocol in hot standby
mode.
• unused
• own BSE
• BSE 01 to BSE 20
Default setting = unused
Target SSE for hot standby Supplementary system element Permitted range =
container with redundant DNP3 protocol in
hot standby mode.
• unused
• PRE 00 to PRE 03
Default setting = unused
Data compression for Should only the last measured Permitted range = yes, no
analog change events value event of a data point be Default setting = no
transferred or should all changes
be transferred?
• yes = only pass on the last

change (condensed)
•
no = pass on all changes
[PRE] | Advanced parameters | Monitoring times
Monitoring timeout Permitted range = 0 to 65535 s
Idle monitoring time After transmission disturbances or Permitted range = 0 to 32767 Bit
message interruption the idle state Standard setting = 33 Bit
is monitored. After expiry of the
monitoring time the receiver is
resynchronized.
Expected_ack_time_corr_fac Extension of the automatically Permitted range = 0 to 655.35 s
tor determined expected acknowl- Default setting = 2 s
edgement time (required if the
transmission is delayed by trans-
mission equipment or slow-
responding remote stations).
Interface monitoring time Cycle time for interface monitoring Permitted range = 0 to 65535 s
"cycle time" by the service function “Test func- 0 = monitoring disabled
tion for link layer”. Default setting = 100 s
Timeout application expected acknowledgment time for Permitted range = 0, 0.1 to 6553.5
confirmation the acknowledgment of the appli- s
cation layer. Default setting = 10 s

DC8-037-2, Edition 11.2020
12.10 DNP3

Character Monitoring Time Message gap monitoring Maximum Permitted range = 0 to 32767 Bit
pause between successive bytes of Standard setting = 33 Bit
a message Idle monitoring time is
started after detection of message
interruption.
Send cyclic link layer Permitted range =
messages as
• Query link status
• Query test link
12.10.6.2 Parameter and Functions DNP3 Slave TCP/IP

[PRE] DNP3 | Settings in receive direction
ment size fragment in receive direction Standard setting = 2048
DNP3 message in receive direction Standard setting = 292
[PRE] DNP3 | Settings in transmit direction
ment size fragment in transmit direction Standard setting = 2048
DNP3 message in transmit direction Standard setting = 292
[PRE] | DNP3 | Slave | DNP time settings
Timeout SELECT → OPERATE Maximum waiting time between a Permitted range = 0.1 to 6553.5 s
SELECT and an OPERATE for a valid Default setting = 20 s
command.
Timeout emulate SELECT Waiting time to simulate a SELECT Permitted range = 0.1 to 6553.5 s
command if SELECT before Default setting = 2 s
OPERATE is not supported by the
master but is still needed.
With an OPERATE command, a
SELECT is first generated and then
an EXECUTE after this time has
expired.
[PRE] | DNP3 | Slave | Settings default data types
For binary input (object Data types are referenced with Permitted range =
• binary input
ized here.
For binary input change Data types are referenced with Permitted range =
default object variant parameter- • binary input with relative time
ized here.
time

DC8-037-2, Edition 11.2020
12.10 DNP3

• binary input
ized here.
change (object 4) Object/Variation. A request for data
default object variant parameter- • binary input with relative
ized here.
time
For binary output (object Data types are referenced with Permitted range =
• binary output
variation) is answered with the • binary output with status
default object variant parameter- default setting = binary output with
ized here. status
For binary counter (object Data types are referenced with Permitted range =
• 16 bit counter
ized here.
with status
• 16 bit counter
ized here.
with status
For binary counter change Data types are referenced with Permitted range =
ized here.
with status
ized here.
with status

DC8-037-2, Edition 11.2020
12.10 DNP3

For analog input (object Data types are referenced with Permitted range =
• 16 bit analog input with status
variation) is answered with the • 16 bit analog input without
default object variant parameter- status
ized here. • 32 bit analog input with status
• 32 bit analog input without
status
• short floating point
input with status
For analog input change Data types are referenced with Permitted range =
with time
variation) is answered with the
default object variant parameter- • 16 bit analog change event
ized here. without time
with time
without time
change event without time
For analog input deadband Data types are referenced with Permitted range =
• 16 bit analog input deadband
variation) is answered with the • 32 bit analog input deadband
ized here. input deadband
input deadband
For analog output status Data types are referenced with Permitted range =
• 16 bit analog output status
variation) is answered with the • 32 bit analog output status
ized here. output status
output status
[PRE] | DNP3 | Slave | Settings unsol. message
for transmission
for transmission
for transmission

DC8-037-2, Edition 11.2020
12.10 DNP3

Retrycount for unsolicited Permitted range = 0 to 255
messages Standard setting = 5
Send static data as unso- Permitted range = yes, no
licited messages Default setting = no
Timeout unsolicited Delay for sending unsol. messages Permitted range = 0, 0.1 to 6553.5
messages offline retry . if a communication failure has s
already been detected. Default setting = 5 s
Timeout unsolicited Delay for the repetition of a non- Permitted range = 0, 0.1 to 6553.5
messages retry . acknowledged unsol. message. s
Behavior unsol. messages Permitted range =
after startup
• yes, transmit immediately
• only after time setting is
complete
• only after request data class 0
is complete
Default setting = yes, transmit
immediately
for transmission
for transmission
for transmission
[PRE] | DNP3 | Slave | common DNP3 settings
Monitoring timeout Permitted range = 0 to 65535 s
Failure management in Permitted range =
transmit direction
• NT-Bit = 1
• IV-Bit = 1
• NT-Bit and/or IV-Bit = 1
Standard setting = NT-Bit = 1
CROB command mode According to DNP3 standard, no Permitted range =
other telegrams may be received
between SELECT and OPERATE,
• DNP3 compliant
otherwise the current SELECT will • non DNP3 compliant
be deleted. default setting = non DNP3
In case of non DNP3 compliant, compliant
SELECT will not be cleared.
Startup delay This delay is used to update the Permitted range =
process image on the PRE after a 5 to 200 s
restart before the communication
is started.

DC8-037-2, Edition 11.2020
12.10 DNP3

Conversion of NT-Bit Conversion of NT-Bit (IEC Permitted range =
60870-5-101/104) to DNP3 state.
• to DNP3 status “offline“
tion lost“
tion lost“ and “offline“
default setting = to DNP3 status
“communication lost”
Send cyclic link layer Permitted range =
messages as Query link status
Query test link
Delete oldest event if If the event buffer overflows, Permitted range = yes, no
event buffer overflow depending on the selection Default setting = yes
• the oldest data will be deleted
•
the newest data will be
deleted
[PRE] | DNP3 | Slave | common DNP3 settings | software test points
… The software test points may only Permitted range = yes, no
be used under the guidance of Default setting = no
be turned off.
[PRE] | DNP3 | Slave | project specific settings
Force binary input varia- If the default data type for “binary Permitted range = yes, no
tion 1 input (object 1)” is set to “binary Default setting = no
input”, this release causes a
suppression of the automatic
switchover to “binary input varia-
tion 2” All DNP3 states are replaced
by “online”.
Save events on SD card Permitted range = yes, no
Enable SCBO (check back When this function is enabled, the Permitted range = yes, no
before operate) commands (SELECT + OPERATE) are Default setting = no
processed differently from the
DNP3 standard.
While a SELECT is running, a new
received SELECT is discarded and
the old one remains active.
An OPERATE is valid for the first
SELECT.
Optimized indexing Permitted range = yes, no
Data compression for Should only the last measured Permitted range = yes, no
analog change events value event of a data point be Default setting = no
transferred or should all changes
be transferred?
• yes = only pass on the last

change (condensed)
• no = pass on all changes

DC8-037-2, Edition 11.2020
12.10 DNP3

[PRE] | DNP3 | Slave | project specific settings | Replace DNP3 source/target
address for station a, b, c, d
Station number (internal) Station number (internal) in the Permitted range =
connection definition for which the 0 to 99 ... internal station number
DNP3 source address and DNP3 255 … not used (default)
destination address should be
replaced.
new DNP3 source address In the transmit direction, the new Permitted range = 0 to 65519
DNP destination address is trans- Standard setting = 0
mitted instead of the DNP destina-
tion address for the selected
station number (internally).
Note:
This function is required if several
remote stations use the same DNP
source address.
For this purpose, different DNP
source addresses are parameter-
ized in the connection definition -
when transmitting in the sending
direction, the DNP source address is
replaced by the new DNP source
address.
(This feature is supported for a
maximum of 4 connections).
new DNP3 destination In the transmit direction, the new Permitted range = 0 to 65519
address DNP destination address is trans- Standard setting = 0
mitted instead of the DNP destina-
tion address for the selected
station number (internally).
Note:
This function is required if several
remote stations use the same DNP
destination address. For this
purpose, different DNP destination
addresses are parameterized in the
connection definition - when trans-
mitting in the sending direction,
the DNP destination address is
replaced by the new DNP destina-
tion address.
(This feature is supported for a
maximum of 4 connections).
[PRE] | HTTP Webserver
HTTP web server With a web browser protocol- Permitted range = disabled,
internal information can be enabled
displayed. Default setting = disabled
Note:
For safety reasons, the web server
operation.

DC8-037-2, Edition 11.2020
12.10 DNP3

[PRE] | Time management | DNP3 time management
Enable time setting Enable which time setting method Permitted range =
is to be used (time setting via the
DNP protocol or via an NTP server).
• via DNP Protocol
• via NTP Server
Time format in receive The DNP3 protocol uses UTC time Permitted range =
• use received time without
(conversion)
time format is converted from
DNP3 to SICAM A8000. • from UTC to local time with
DST correction
• from UTC to local time
without DST correction
default setting = from UTC to local
time with DST correction
Time format in transmit The DNP3 protocol uses UTC time Permitted range =
• use local time
time format is converted from • from local time incl. DST

SICAM A8000 to DNP3. correction to UTC
• from local time without DST
correction to UTC
default setting = from local time
incl. DST correction to UTC
[PRE] | Time management | DNP3 time management | Settings SLAVE
Correction time for clock The time in the clock synchroniza- Permitted range = - 60.00 to +
synchronization command tion command is changed by the 60.00 ms
automatically determined transmis- Default setting = 0 s
sion time and correction time.
Link address for taking Time synchronization is only Permitted range = 0 to 65519
over the time synchroniza- carried out for this link address Standard setting = 0
tion (DNP source address)
generating the cyclic time setting
request (IIN bit)
Acceptance of the time setting tele-
gram received, but only if no NTP
synchronization is used
Cycle time for sending Time grid for cyclic time setting. Permitted range = 0 to 65535 s
clock synchronization 0 .. no cyclic time setting
command Default setting = 300 s
12.10.7.1 Overview
IEC 60870-5-101/104 ↔ DNP3 is performed by the protocol element. The transmission of the data to the
remote station according to DNP3 is controlled by the protocol element.
Data in receive direction are converted by the protocol element from the DNP3 format → SICAM A8000
internal IEC 60870-5-101/104 format and transferred to the basic system element (no 101/104 blocking).

DC8-037-2, Edition 11.2020
12.10 DNP3
The conversion of the CP-8050 internal IEC 60870-5-101/104 message format ↔ DNP3 data format and the
The parameterization of the conversion from IEC 60870-5-101/104 ↔ DNP3 (address and message format) is
to be done with SICAM Device Manager with function “Signals” or SICAM TOOLBOX II / OPM using "SIP
Message Address Conversion".
Data Direction Processing type DNPSI0 DNPiI1

Commands Receive direction firmware /Rec_command ✓ ✓
Setpoint values Receive direction firmware /Rec_setpoint_value ✓ ✓
Binary informa- Transmit direction firmware /Trans_binary_informa- ✓ ✓
tion tion
Measured Transmit direction firmware /Trans_measured value ✓ ✓
values
Integrated Transmit direction firmware /Trans_counter_value ✓ ✓
totals
Parameters
The data is transmitted according to DNP3 with the set Own station
number to the remote station with the set Station number of the
remote station.
DNP3_Data_index DNP3 Data index:
• 0 to 65535
Each data object is defined by the used object type and object variant.
Within an object type, the data objects are distinguished by the data
index. This data index can by definition be a maximum of
42949671295. The DNP3 firmwares only support a maximum data
index of 65535. Thus, a maximum of 65536 data points can be used
for an object type. For different object types, the same data index may
be used, since the differentiation of the data is made possible by the
object type.
With DNP3, the data is addressed (DNP object) with “Object/Variation” and
“data index”. The central station query of the data may be either specific
(e.g., “Binary Input with Status”) or with a general query (e.g., “Binary Input
- Any Variation”).
The default data types for queries with “Any Variation” are set in the firm-
ware for DNP3 slave with the following parameters: [PRE] DNP3 |
Communication functions | Data base management DNP3 |
Default data object settings

DC8-037-2, Edition 11.2020
12.10 DNP3
Parameters
DNP3_Object_variant DNP3 Object variant:
• 32 bit measured value

• Measured value short floating point
• binary output event
• binary output command event
• analog output event
• analog output command event
• binary input
• double binary input
• Measured value short floating point
• 32 bit measured value (sags & swells)
• 16 bit measured value (sags & swells)
• short floating point (sags & swells)
• 32 bit integrated total
• 16 bit integrated total
• 32 bit integrated total delta
• 16 bit integrated total delta
DNP3_Event_class DNP3 Eventclass:
• Data class 1
• Data class 2
• Data class 3
12.10.7.2 Message Conversion in Transmit Direction (Slave → Master)

Message Conversion in Transmit Direction IEC 60870-5-101/104 → DNP3
SICAM A8000: IEC 60870-5-101/104 DNP3
Type Designation Designation Object Object
Identifi- type variant
cation
<TI:=30> Single-point information with • Binary Input 1 0, 1, 2
CP56Time2a time tag
• Binary Input Change 2 0, 1, 2, 3
<TI:=31> Double-point information with time tag • Binary Input 1 0, 1, 2
CP56Time2a
• Binary Input Change 2 0, 1, 2, 3
3 0, 1, 2
• Double Binary Input
4 0, 1, 2, 3
• Double Binary Input
Change
<TI:=34> Measured value, normalized value with • Analog Input 30 0, 1, 2, 3, 4
time tag CP56Time2a
• Analog Change Event 32 0, 1, 2
<TI:=35> Measured value, scaled value with time • Analog Input 30 0, 1, 2, 3, 4
tag CP56Time2a

DC8-037-2, Edition 11.2020
12.10 DNP3
SICAM A8000: IEC 60870-5-101/104 DNP3

<TI:=36> Measured value, short floating point • Analog Input 30 0, 1, 2, 3, 4
<TI:=37> Integrated totals with time tag • Binary Counter 20 0, 1, 5
CP56Time2a
• Frozen Counter 21 0, 1, 5, 9
23 0, 1, 5
• Frozen Counter Event
Time synchronization • Time Delay Fine 308 52 2
Binary information
The parameterization of the address and message conversion for binary information in transmit direction
takes place for DNP3 Slave with SICAM TOOLBOX II, OPM II (object oriented process data manager).
Parameter Category:
308 The message is generated by the protocol firmware

DC8-037-2, Edition 11.2020
12.10 DNP3
Measured values
The parameterization of the address and message conversion for measured values in transmit direction takes
place for DNP3 Slave with SICAM TOOLBOX II, OPM II (object oriented process data manager).
Parameter Category:
firmware /Trans_measured_value
Integrated totals
The parameterization of the address and message conversion for integrated totals in transmit direction takes
Parameter Category:
firmware /Trans_counter_value
12.10.7.3 Message Conversion in Receive Direction (Slave ← Master)

Message Conversion in Receive Direction IEC 60870-5-101/104 ← DNP3

DC8-037-2, Edition 11.2020
12.10 DNP3
SICAM A8000: IEC 60870-5-101/104 DNP3

Type Designation Designation Object Object
Identifi- type variant
cation
<TI:=45> Single command • Control Relay Output Block 12 1
<TI:=46> Double-point information • Control Relay Output Block 12 1
<TI:=48> Set point command, normalized • 32 Bit Analog Output Block 41 1
value
• 16 Bit Analog Output Block 41 2
41 3
• Short Floating Point Analog
Output Block
<TI:=49> Setpoint command, scaled value • 32 Bit Analog Output Block 41 1
41 3
Output Block
<TI:=50> Set point command, short floating • 32 Bit Analog Output Block 41 1
point number
41 3
Output Block
Time Synchronization • Request 60 309 1, 2, 3, 4
Data class 0, 1 , 2 or 3
• Enable/disable unsolicited 60 309 2, 3, 4
messages for data class 1, 2
or 3. Enable/disable sponta-
neous message transmission
• Assign Class 309
Assign the given data to class

1, 2 or 3
• Delay Measurement 309
Runtime measurement
• Time and Date 50 309 1
Commands
The parameterization of the address and message conversion for commands in receive direction takes place
for DNP3 Slave with SICAM TOOLBOX II, OPM II (object oriented process data manager).
309 This telegram is only evaluated on the PRE

DC8-037-2, Edition 11.2020
12.10 DNP3
Parameter Category:
Setpoint values
The parameterization of the address and message conversion for setpoint values in receive direction takes
Parameter Category:
firmware /Rec_setpoint_value

DC8-037-2, Edition 11.2020
12.10 DNP3
12.10.8 Interoperabilität (DNP3 Device Profile Document)
Revision History
VERSION Date Reason for Changes

1.00 2018-08-30 Initial Version for SICAM A8000 CP-8000/802x with DNPST0 firmware or
DNPiT0 firmware using the Triangle MicroWorks, Inc. DNP3 Slave Source
Code Library Version 3.22.0000
Note:
Initial version of DNP3 Device Profile Document for SICAM A8000
CP-8000/802x is based on DNP3 Device Profile Document based on
template DNP3Spe_DeviceProfile_April2016.docx
1.03 2019-04-24 Firmwares for DNP3 Master ("serial") and DNP3 Master (TCP) added.
DNP3 Profile Document valid for following firmwares:
• DNPST0 … DNP3 Slave ("serial")

• DNPMT0 … DNP3 Master ("serial")
• DNPiT1 … DNP3 Slave (TCP)
• DNPiT2 … DNP3 Master (TCP)
Note:
DNP3 firmwares using the Triangle MicroWorks, Inc. DNP3 Master/Slave
Source Code Library Version 3.22.0000.
Vendors must produce a Device Profile Document for each device they manufacture implementing DNP3. The
Device Profile Document clearly identifies any deviations from the implementation levels described in this
document and any other issues that may arise when determining the device’s compatibility with another
device.
The instructions for completing Device Profile Forms and information are given in Clause 14 of the specifica-
tion - Interoperability.
Note: there are empty "placeholder" sections in the Device Profile document. These are intentionally blank,
being used so that section numbering does not change when entries are deleted from the document. Like-
wise, to ensure existing section numbers do not change, all new entries are added at the end of the relevant
section.
1 Device Properties
This document is intended to be used for several purposes, including:
• Identifying the capabilities of a DNP3 device (Master Station or Outstation)
• Recording the settings of a specific instance of a device (parameter settings for a specific instance of the
device in the user’s total DNP3 estate)
• Matching user requirements to product capabilities when procuring a DNP3 device

The document is therefore structured to show, for each technical feature, the capabilities of the device (or
capabilities required by the device when procuring).
It is also structured to show the current value (or setting) of each of the parameters that describe a specific
instance of the device. This "current value" may also show a functional limitation of the device. For example
when implementing secure authentication it is not required that all DNP3 devices accept aggressive mode
requests during critical exchanges (see Device Profile 1.12.4), in which case a vendor would mark this current
value as "No – does not accept aggressive mode requests".
Additionally, the current value may sometimes be used to show a value that a device can achieve because of
hardware or software dependencies. Users should note that if an entry in the capabilities column of the Device

DC8-037-2, Edition 11.2020
12.10 DNP3
Profile is grayed-out then there may be information in the current value column that is pertinent to the devi-
ce’s capabilities.
Unless otherwise noted, multiple boxes in the second column below should be selected for each parameter to
indicate all capabilities supported or required. Parameters without checkboxes in the second column do not
have capabilities and are included so the current value may be shown in the third column.
The items listed in the capabilities column below may be configurable to any of the options selected, or set to
a fixed value when the device was designed. Item 1.1.10 contains a list of abbreviations for the possible ways
in which the configurable parameters may be set. Since some parameters may not be accessible by each of
these methods supported, an abbreviation for the configuration methods supported by each parameter is
shown in the fourth column of the tables below.
If this document is used to show the current values, the third column should be filled in even if a fixed param-
eter is selected in the capabilities section ("N/A" may be entered for parameters that are Not Applicable).
If this document is used to show the current value of parameters, then column 3 applies to a single connec-
tion between a master and an outstation.
1.1 DEVICE IDENTIFICATION Capabilities Current Value If configu-

rable, list
methods
1.1.1 Device Function: ● Master ● Master
Masters send DNP requests, while ● Outstation ● Outstation
Outstations send DNP responses. If a
single physical device can perform both
functions, a separate Device Profile Docu-
ment must be provided for each func-
tion.
1.1.2 Vendor Name: Siemens AG
The name of the organization producing Humboldstraße 59
the device. 90459 Nuremberg
Note: The current value of this outstation Germany
parameter is available remotely using
protocol object Group 0 Variation 252.
1.1.1 Device Name: SICAM A8000
The model and name of the device, suffi- CP-8000/802x
cient to distinguish it from any other with
device from the same organization. DNPST0 or DNPiT1
Note: The current value of this outstation or DNPMT0 or
parameter is available remotely using DNPiT2 firmware.
1.1.4 Device manufacturer’s hardware CP-8000:
version string: 6MF21010AB10
Note: The current value of this outstation CP-8021:
parameter is available remotely using 6MF28021AA00
protocol object Group 0 Variation 243. CP-8022:
6MF28022AA00

DC8-037-2, Edition 11.2020
12.10 DNP3

rable, list
methods
1.1.5 Device manufacturer’s software DNPST0 V6.30 (1)
version string: DNPiT1 V2.40 (2)
Note: The current value of this outstation DNPMT0 V2.40 (3)
parameter is available remotely using DNPiT2 V2.40 (4)
(1) DNP3 Slave

"serial"
(2) DNP3 Slave
"TCP"
(3) DNP3 Master
"serial"
(4) DNP3 Master
"TCP"
1.1.6 Device Profile Document Version V1.03
Number:
Version of the Device Profile Document is
indicated by a whole number incre-
mented with each new release. This
should match the latest version shown in
the Revision History at the beginning of
this document.
1.1.7 DNP Levels Supported for: Masters only
Indicate each DNP3 Level to which the Requests Response
device conforms fully. For Masters, ☐ ........... ☐ ............. None
requests and responses can be indicated ☒ ........... ☒ ............. Level 1
independently.
☒ ........... ☒ ............. Level 2
☐ ........... ☐ ............. Level 3
☐ ........... ☐ ............. Level 4
Outstations Only
Note:
Requests and Responses
Most but not all of
☐ ....... None level 3 features are
☒ ....... Level 1 also supported.
☒ ....... Level 2
☐ ....... Level 3
☐ ....... Level 4
1.1.8 Supported Function Blocks: ☐ Self-Address Support
☐ Data Sets
☐ File Transfer
☐ Virtual Terminals
☐ Mapping to IEC 61850 Object Models
defined in a DNP3 XML file
☐ Function code 31, activate configura-
tion
☐ Authentication (if checked then see
1.12)

DC8-037-2, Edition 11.2020
12.10 DNP3

rable, list
methods
1.1.9 Notable Additions:
Note:
A brief description intended to quickly
Most but not all of
identify (for the reader) the most obvious
level 3 features are
features the device supports in addition
also supported.
to the Highest DNP Level Supported. The
complete list of features is described in
the Implementation Table.
1.1.10 Methods to set Configurable ☐ XML – Loaded via DNP3 File Transfer
Parameters: ☐ XML – Loaded via other transport
mechanism
☐ Terminal – ASCII Terminal Command
Line 1
☒ Software – Vendor software named
- SICAM Device Manager or
- SICAM TOOLBOX II
☐ Proprietary file loaded via DNP3 file
transfer
☐ Proprietary file loaded via other trans-
port mechanism
☐ Direct – Keypad on device front panel
☐ Factory – Specified when device is
ordered
☐ Protocol – Set via DNP3 (e.g. assign
class)
☐ Other, explain
_______________________
1.1.11 DNP3 XML files available On-Line: Rd Wr Filename Description of Note:
XML configuration files names that can Contents DNP3 XML files not
be read or written through DNP3 File ☐ dnpDP.xml Complete Device Profile supported
Transfer to a device. ☐ dnpDPcap.xml Device Profile Capabili-
A device’s currently running configura- ties
tion is returned by DNP3 on-line XML file ☐ dnpDPcfg.xml Device Profile config.
read from the device. values
DNP3 on-line XML file write to a device
will update the device’s configuration
when the Activate Configuration (func-
tion code 31) is received.
1.1.12 External DNP3 XML files available Rd Wr Filename Description of Note:
Off-line: Contents DNP3 XML files not
XML configuration file names that can be ☐ ☐ dnpDP.xml Complete Device Profile supported
read or written from an external system, ☐ ☐ dnpDPcap.xml Device Profile Capa-
typically from a system that maintains bilities
the outstation configuration. ☐ ☐ dnpDPcfg.xml Device Profile config.
External off-line XML file read permits an values
XML definition of a new configuration to
be supplied from off-line configuration
tools.
External off-line XML file write permits an
XML definition of a new configuration to
be supplied to off-line configuration
tools.

DC8-037-2, Edition 11.2020
12.10 DNP3

rable, list
methods
1.1.13 Connections Supported: ☒ Serial (complete section 1.2) - DNPST0 = ser. (1)
☒ IP Networking (complete section 1.3) - DNPMT0 = ser. (2)
☐ Other, explain - DNPiT1 = IP (3)
________________________ - DNPiT2 = IP (4)
(1) DNP3 Slave

"serial"
(2) DNP3 Master
"serial"
(3) DNP3 Slave
"TCP/UDP"
(4) DNP3 Master
"TCP/UDP"
1.1.14 Conformance Testing: ☒ Self-tested, version
Where conformance testing has been DNP3 Slave tested by SIEMENS AG
completed for the outstation or master Austria according "DNP3 IED
station, specify the version of the Certification Procedure Subset
published DNP3 test procedures that was
Level 2 Version 2.7 2-March-2016"
successfully passed. If independently
tested, identify the organization that ☐ Independently tested, version
performed the test. ______________
Test organization name
__________________
1.2 SERIAL CONNECTIONS Capabilities Current Value If configu-

rable, list
methods
1.2.1 Port Name: CP-8000: DNPMT0,
Name used to reference the communica- - Port X2: RS-232 DNPST0
tion port defined in this section. - Port X3: RS-422 mapping to
one of avail-
- Port X3: RS-485
able serial
CP-8021: ports.
- Port X2: RS-232
- Port X3: RS-422
- Port X3: RS-485
CP-8022:
- Port X2: RS-232
- Port X3, X6:
RS-422
- Port X3, X6:
RS-485
1.2.2 Serial Connection Parameters: ☒ Asynchronous - 8 Data Bits, 1 Start Bit, 8 Data Bits, 1 Start
1 Stop Bit, No Parity Bit, 1 Stop Bit, No
☒ Other, explain Parity
- Asynchronous - 8 Data Bits, 1 Start Bit,
1/2 Stop Bit, Even/Odd Parity

DC8-037-2, Edition 11.2020
12.10 DNP3

rable, list
methods
1.2.3 Baud Rate: ☐ Fixed at _______ 9600
☐ Configurable, range ____ to ____
☒ Configurable, selectable from
50, 75, 100, 134.5, 150, 200, 300,
600, 1050, 1200, 1800, 2000, 2400,
4800, 9600, 19200, 38400, 56000,
57600, 64000, 115200
☐ Configurable, other, describe
_______________

DC8-037-2, Edition 11.2020
12.10 DNP3

rable, list
methods
1.2.4 Hardware Flow Control (Hand- ☐ None
shaking):
Describe hardware signaling require- RS-232 / V.24 / V.28 Options:
ments of the interface.
Asserts:
Where a transmitter or receiver is
☒ RTS before Tx
inhibited until a given control signal is
☐ DTR before Tx
asserted, it is considered to require that
☐ RTS before Rx Note:
signal prior to sending or receiving char-
acters. ☐ DTR before Rx "always RTS" and
Where a signal is asserted prior to trans- ☒ Always RTS "always DTR" is
mitting, that signal will be maintained ☒ Always DTR only possible with
active until after the end of transmission. parameter
Where a signal is asserted to enable tv=0 ("RTS before
Requires before Tx: Tx").
reception, any data sent to the device
when the signal is not active could be CTS ☐ Asserted ☐ Deasserted
discarded. DCD ☐ Asserted ☒ Deasserted
DSR ☐ Asserted ☐ Deasserted
RI ☐ Asserted ☐ Deasserted
Requires Rx inactive before Tx
Requires before Rx:

CTS ☐ Asserted ☐ Deasserted
DCD ☐ Asserted ☐ Deasserted
DSR ☐ Asserted ☐ Deasserted
RI ☐ Asserted ☐ Deasserted
Always ignores:
☒ CTS
☐ DCD
☒ DSR
☒ RI
☐ Other, explain ____________
RS-422 / V.11 Options:

☐ Requires Indication before Rx
☒ Asserts Control before Tx
RS-485 Options:
☒ Requires Rx inactive before Tx
☐ Other, explain

DC8-037-2, Edition 11.2020
12.10 DNP3

rable, list
methods
1.2.5 Interval to Request Link Status: ☐ Not Supported 0 seconds
Indicates how often to send Data Link ☐ Fixed at_________ seconds
Layer status requests on a serial connec- ☒ Configurable, range 0 to 65535
tion. This parameter is separate from the seconds
TCP Keep-alive timer. ☐ Configurable, selectable from
___,___,___ seconds
☐ Configurable, other,
describe________________
1.2.6 Supports DNP3 Collision Avoidance: ☐ No 30 ms
Indicates whether a device uses a colli- ☒ Yes, using Back-off time = (Min +
sion avoidance algorithm. Random) method
Collision avoidance may be implemented
by a back-off timer with two parameters
Minimum Back-off time:
that define the back-off time range or by
☐ Fixed at_________ ms
some other vendor-specific mechanism.
☒ Configurable, range 0 to 65535 ms
The recommended back-off time is speci-
fied as being a fixed minimum delay plus ☐ Configurable, selectable from
a random delay, where the random delay ___,___,___ ms
has a maximum value specified. This ☐ Configurable, other,
defines a range of delay times that are describe________________
randomly distributed between the
minimum value and the minimum plus
Maximum Random Back-off time compo-
the maximum of the random value.
nent:
If a back-off timer is implemented with
☒ Fixed, range 20 to 120 ms
only a fixed or only a random value,
select the Back-off time method and set ☐ Configurable, range _____ to ______
the parameter that is not supported to ms
"Fixed at 0 ms". ☐ Configurable, selectable from
___,___,___ ms
describe________________
☐ Other, explain
________________________

DC8-037-2, Edition 11.2020
12.10 DNP3

rable, list
methods
1.2.7 Receiver Inter-character Timeout: ☐ Not checked 100 Bit
When serial interfaces with asynchronous ☐ No gap permitted
character framing are used, this param- ☐ Fixed at _____ bit times
eter indicates if the receiver makes a ☐ Fixed at _____ ms
check for gaps between characters (i.e.
☒ Configurable, range 0 to 32767 bit
extension of the stop bit time of one
times
character prior to the start bit of the
following character within a message). If ☐ Configurable, range ____ to ____ ms
the receiver performs this check and the ☐ Configurable, Selectable from
timeout is exceeded then the receiver ___,___,___bit times
discards the current data link frame. A ☐ Configurable, Selectable from ____,
receiver that does not discard data link ____, ____ ms
frames on the basis of inter-character ☐ Configurable, other, describe
gaps is considered to not perform this __________________
check.
☐ Variable, explain ____
Where no asynchronous serial interface is
fitted, this parameter is not applicable. In
this case none of the options shall be
selected.
1.2.8 Inter-character gaps in transmis- ☒ None (always transmits with no inter-
sion: character gap)
When serial interfaces with asynchronous ☐ Maximum _____ bit times
character framing are used, this param- ☐ Maximum _____ ms
eter indicates whether extra delay is ever
introduced between characters in the
message, and if so, the maximum width
of the gap.
Where no asynchronous serial interface is
fitted, this parameter is not applicable. In
this case none of the options shall be
selected.
1.3 IP NETWORKING Capabilities Current Value If configu-

rable, list
methods
1.3.1 Port Name: CP-8000:
Name used to reference the communica- - Port X1, X4:
tion port defined in this section. Ethernet
CP-8021:
- Port X1, X4:
Ethernet
CP-8022:
- Port X1, X4:
Ethernet
1.3.2 Type of End Point: ☒ TCP Initiating (list all active)
☒ TCP Listening
☒ TCP Dual Default:
☒ UDP Datagram TCP Listening
1.3.3 IP Address of this Device: configurable
1.3.4 Subnet Mask: configurable
1.3.5 Gateway IP Address: configurable

DC8-037-2, Edition 11.2020
12.10 DNP3

rable, list
methods
1.3.6 Accepts TCP Connections or UDP ☐ Allows all (show as *.*.*.* in 1.3.7) Wildcard IP address
Datagrams from: ☐ Limits based on an IP address = 0.0.0.0
☒ Limits based on list of IP addresses
☒ Limits based on a wildcard IP address Supported only for
☐ Limits based on list of wildcard IP one connection
addresses using TCP listening.
☐ Other, explain_________________
1.3.7 IP Address(es) from which TCP
Connections or UDP Datagrams are
accepted:
1.3.8 TCP Listen Port Number: ☐ Not Applicable (Master w/o dual end Default: 20000
If Outstation or dual end point Master, point)
port number on which to listen for ☐ Fixed at 20,000
configurable for
incoming TCP connect requests. Required ☒ Configurable, range 1024 to 65535 each connection.
to be configurable for Masters and ☐ Configurable, selectable from
recommended to be configurable for ____,____,____
Outstations.
describe________________
1.3.9 TCP Listen Port Number of remote ☐ Not Applicable (Outstation w/o dual Default: 20000
device: end point)
If Master or dual end point Outstation, ☐ Fixed at 20,000
configurable for
port number on remote device with ☒ Configurable, range 1024 to 65535 each connection.
which to initiate connection. ☐ Configurable, selectable from
Required to be configurable for Masters ____,____,____
and recommended to be configurable for ☐ Configurable, other,
Outstations. describe_______________
1.3.10 TCP Keep-alive timer: ☒Timer disabled
The time period for the keep-alive timer ☐ Fixed at ___________ms
on active TCP connections. ☐ Configurable, range _______ to
_______ms
☐ Configurable, selectable from
____,____,____ms
describe_______________
1.3.11 Local UDP port: ☐ Fixed at 20,000
Local UDP port for sending and/or ☐ Configurable, range _______ to
receiving UDP datagrams. Master may let _______
system choose an available port. Outsta- ☐ Configurable, selectable from
tion must use one that is known by the ____,____,____
master. ☐ Configurable, other,
describe_______________
☐ Let system choose (Masters only)
1.3.12 Destination UDP port for DNP3 ☐ Fixed at 20,000
Requests (Masters only): ☐ Configurable, range _______ to
_______
____,____,____
describe_______________

DC8-037-2, Edition 11.2020
12.10 DNP3

rable, list
methods
1.3.13 Destination UDP port for initial ☐ None
unsolicited null responses (UDP only ☐ Fixed at 20,000
Outstations): ☐ Configurable, range _______ to
The destination UDP port for sending _______
initial unsolicited Null response. ☐ Configurable, selectable from
____,____,____
describe_______________
1.3.14 Destination UDP port for ☐ None Default: 20000
responses (UDP only Outstations): ☐ Fixed at 20,000 configurable for
The destination UDP port for sending all ☒ Configurable, range 1024 to 65535 each connection.
responses other than initial unsolicited ☐ Configurable, selectable from
Null response. ____,____,____
describe_______________
☐ Use local port number (as specified in
1.3.11)
1.3.15 Multiple outstation connections ☒ Supports multiple outstations (Masters max. 100 connec-
(Masters only): only) tions supported
Indicates whether multiple outstation
connections are supported.
1.3.16 Multiple master connections ☒ Supports multiple masters (Outsta- max. 100 connec-
(Outstations Only): tions only) tions supported,
Indicates whether multiple master If supported, the following methods may requiring different
connections are supported and the be used: destination link
method that can be used to establish ☒ Method 1 (based on IP address) - addresses.
connections. required
☒ Method 2 (based on IP port number) - Note:
recommended max. 4 connections
☐ Method 3 (browsing for static data) - supported with
optional identical destina-
tion link address
1.3.17 Time synchronization support: ☒ DNP3 LAN procedure (function code DNP3 LAN only
24) supported by DNP3
☐ DNP3 Write Time (not recommended TCP Slave/Master.
over LAN) 1
☒ Other, explain: DNP3 Write Time
- NTP only supported by
- SNTP DNP3 Serial Slave/
☐ Not Supported Master.

DC8-037-2, Edition 11.2020
12.10 DNP3
1.4 LINK LAYER Capabilities Current Value If configu-

rable, list
methods
1.4.1 Data Link Address: ☐ Fixed at______
Indicates if the link address is configu- ☒ Configurable, range 0 to 65519
rable over the entire valid range of 0 to ☐ Configurable, selectable from
65,519. Data link addresses 0xFFF0 ____,____,____
through 0xFFFF are reserved for broad- ☐ Configurable, other,
cast or other special purposes. describe________________
1.4.2 DNP3 Source Address Validation: ☐ Never Always configurable
Indicates whether the device will filter ☒ Always, one address allowed (shown (single address) via SICAM
out messages not from a specific source in 1.4.3) Device
address. ☐ Always, any one of multiple addresses Manager or
allowed (each selectable as shown in SICAM
1.4.3) TOOLBOX II
☐ Sometimes, explain________________
1.4.3 DNP3 Source Address(es) expected ☐ Configurable to any 16 bit DNP Data configurable
when Validation is Enabled: Link Address value via SICAM
Selects the allowed source address(es). ☒ Configurable, range 0 to 65519 Device
☐ Configurable, selectable from Manager or
____,____,____ SICAM
TOOLBOX II
describe________________
1.4.4 Self Address Support using address ☐ Yes (only allowed if configurable)
0xFFFC: ☒ No
If an Outstation receives a message with
a destination address of 0xFFFC it shall
respond normally with its own source
address. It must be possible to disable
the feature if supported.
1.4.5 Sends Confirmed User Data ☒ Never Default = Never configurable
Frames: ☒ Sometimes, only for multi fragments via SICAM
A list of conditions under which the ☒ Always Device
device transmits confirmed link layer Manager or
services (TEST_LINK_STATES, SICAM
RESET_LINK_STATES, TOOLBOX II
CONFIRMED_USER_DATA).
1.4.6 Data Link Layer Confirmation ☐ None configurable
Timeout: ☐ Fixed at______ ms via SICAM
This timeout applies to any secondary ☒ Configurable, range 0 to 65535ms Device
data link message that requires a confirm Manager or
or response (link reset, link status, user SICAM
___,___,___ms
data, etc) TOOLBOX II
describe________________
☐ Variable, explain
_______________________
1.4.7 Maximum Data Link Retries: ☐ Never Retries 2 configurable
The number of times the device will ☐ Fixed at ___________ via SICAM
retransmit a frame that requests Link ☒ Configurable, range 0 to 255 Device
Layer confirmation. Manager or
SICAM
____,____,____
TOOLBOX II
describe______________

DC8-037-2, Edition 11.2020
12.10 DNP3
1.4 LINK LAYER Capabilities Current Value If configu-

rable, list
methods
1.4.8 Maximum number of octets Trans- ☐ Fixed at ___________ 292 configurable
mitted in a Data Link Frame: ☒ Configurable, range 20 to 292 via SICAM
This number includes the CRCs. With a ☐ Configurable, selectable from Device
length field of 255, the maximum size ____,____,____ Manager or
would be 292. SICAM
Configurable, other,
TOOLBOX II
describe________________
1.4.9 Maximum number of octets that ☐ Fixed at ___________ 292 configurable
can be Received in a Data Link Frame: ☒Configurable, range 20 to 292 via SICAM
This number includes the CRCs. With a ☐ Configurable, selectable from Device
length field of 255, the maximum size ____,____,____ Manager or
would be 292. The device must be able SICAM
to receive 292 octets to be compliant. TOOLBOX II
describe_______________
1.5 APPLICATION LAYER Capabilities Current Value If configu-

rable, list
methods
1.5.1 Maximum number of octets Trans- ☐ Fixed at ___________ 2048 configurable
mitted in an Application Layer Fragment ☒ Configurable, range 100 to 2048 via SICAM
other than File Transfer: ☐ Configurable, selectable from Device
This size does not include any transport ____,____,____ Manager or
or frame octets. SICAM
TOOLBOX II
• Masters must provide a setting less describe_______________
than or equal to 249 to be
compliant.
• Outstations must provide a setting
less than or equal to 2048 to be
compliant.
Note: The current value of this outstation
1.5.2 Maximum number of octets Trans- ☐ Same current value as 1.5.1
mitted in an Application Layer Fragment ☐ Fixed at ___________
containing File Transfer: ☐ Configurable, range ________ to
_______
____,____,____
describe_______________

DC8-037-2, Edition 11.2020
12.10 DNP3

rable, list
methods
1.5.3 Maximum number of octets that ☐ Fixed at ___________ 2048 configurable
can be Received in an Application Layer ☒ Configurable, range 100 to 2048 via SICAM
Fragment: ☐ Configurable, selectable from Device
This size does not include any transport ____,____,____ Manager or
or frame octets. SICAM
TOOLBOX II
• Masters must provide a setting describe_______________
greater than or equal to 2048 to be
compliant.
• Outstations must provide a setting
greater than or equal to 249 to be
compliant.
Note: The current value of this outstation
1.5.4 Timeout waiting for Complete ☐ None configurable
Application Layer Fragment: ☐ Fixed at______ ms via SICAM
Timeout if all frames of a message frag- ☒ Configurable, range 100 to 6553500 Device
ment are not received in the specified ms Manager or
time. Measured from time first frame of a SICAM
fragment is received until the last frame TOOLBOX II
___,___,___ms
is received.
describe________________
_______________________
1.5.5 Maximum number of objects ☒ Fixed at 10 (enter 0 if controls are not
allowed in a single control request for supported for CROB)
CROB (group 12): ☐ Configurable, range ________ to
Note: _______
The current value of this outstation ☐ Configurable, selectable from
parameter is available remotely using ____,____,____
protocol object Group 0 Variation 216. ☐ Configurable, other,
describe_______________
_______________________
☐ Same current value as 1.5.3
allowed in a single control request for supported for Analog Outputs)
Analog Outputs (group 41): ☐ Configurable, range ________ to
_______
____,____,____
describe_______________
_______________________

DC8-037-2, Edition 11.2020
12.10 DNP3

rable, list
methods
allowed in a single control request for supported for Data Sets)
Data Sets (groups 85, 86, 87): ☐ Configurable, range ________ to
_______
____,____,____
describe_______________
☐Variable, explain
_______________________
Same current value as 1.5.3
1.5.8 Supports mixing object groups ☐ Not applicable – controls are not
(AOBs, CROBs and Data Sets) in the same supported
control request: ☒ Yes
☐ No
1.5.9 Control Status Codes Supported: ☒ 1 – TIMEOUT
Indicates which control status codes are☒ 2 – NO_SELECT
supported by the device: ☒ 3 – FORMAT_ERROR
• Masters must indicate which control ☒ 4 – NOT_SUPPORTED
status codes they accept in outsta- ☒ 5 – ALREADY_ACTIVE
tion responses. ☒ 6 – HARDWARE_ERROR
• Outstations must indicate which ☒ 7 – LOCAL
control status codes they generate ☒ 8 – TOO_MANY_OBJS
in responses. ☒ 9 – NOT_AUTHORIZED
Control status code 0 (success) must be ☒ 10 – AUTOMATION_INHIBIT
supported by Masters and Outstations. ☐ 11 – PROCESSING_LIMITED
☐ 12 – OUT_OF_RANGE
☐ 13 – DOWNSTREAM_LOCAL
☐ 14 – ALREADY_COMPLETE
☐ 15 – BLOCKED
☐ 16 – CANCELLED
☐ 17 – BLOCKED_OTHER_MASTER
☐ 18 – DOWNSTREAM_FAIL
☐ 126 – RESERVED
☐ 127 – UNDEFINED

DC8-037-2, Edition 11.2020
12.10 DNP3
1.6 FILL OUT THE FOLLOWING ITEMS Capabilities Current Value If configu-
FOR MASTERS ONLY rable, list
methods
1.6.1 Timeout waiting for Complete ☐ None Default: 5000 ms configurable
Application Layer Response(ms): ☐ Fixed at______ ms via SICAM
Timeout on Master if all fragments of a ☒ Configurable, range 0 to 65535 ms Device
response message are not received in the Manager or
specified time. SICAM
___,___,___ms
TOOLBOX II
describe________________
_______________________
1.6.2 Maximum Application Layer Retries ☐ None
for Request Messages: ☒ Fixed at 2
The number of times a Master will ☐ Configurable, range _______ to
retransmit an application layer request _______
message if a response is not received. ☐ Configurable, selectable from
This parameter must never cause a ___,___,___
Master to retransmit time sync messages.
describe_______________
_______________________
1.6.3 Timeout waiting for First or Next ☐ None see 1.6.1
Fragment of an Application Layer ☐ Fixed at______ ms
Response: ☐ Configurable, range _______ to
Timeout between a request and the first _______ms
fragment of a response, or between ☐ Configurable, selectable from
subsequent fragments of the same ___,___,___ms
response, or between an Application
Layer Confirmation and a subsequent
describe________________
fragment.
_______________________
1.6.4 Issuing controls to off-line devices: ☐ Not applicable – controls are not
Indicates if the Master issues control supported
requests to devices that are thought to ☐ Yes
be off-line (i.e. the Master has not seen ☒ No
responses to previous Master requests).
1.6.5 Issuing controls to off-scan devices: ☐ Not applicable – controls are not
Indicates if the Master issues control supported
requests to devices that are currently off- ☒ Yes
scan (i.e. the Master has been configured ☐ No
not to issue poll requests to the device).
1.6.6 Maximum Application Layer Retries ☐ None (required)
for Control Select Messages (same ☒ Fixed at 2
sequence number): ☐ Configurable, range _______ to
Indicates the number of times a Master _______
will retransmit an application layer ☐ Configurable, selectable from
control select request message if a ___,___,___
response is not received – using the
same message sequence number.
describe_______________
_______________________

DC8-037-2, Edition 11.2020
12.10 DNP3
FOR MASTERS ONLY rable, list
methods
1.6.7 Maximum Application Layer Retries ☒ None (required)
for Control Select Messages (new ☐ Fixed at______
sequence number): ☐ Configurable, range _______ to
Indicates the number of times a Master _______
will retransmit an application layer ☐ Configurable, selectable from
control select request message if a ___,___,___
response is not received – using a new
message sequence number.
describe_______________
_______________________
1.6.8 Item deleted
1.6.9 Item deleted
1.6.10 Item deleted
1.6.11 Item deleted
FOR OUTSTATIONS ONLY rable, list
methods
1.7.1 Timeout waiting for Application ☐ None Default = 10 sec configurable
Confirm of solicited response message: ☐ Fixed at______ ms via SICAM
☒ Configurable, range 100 to Device
6553500ms Manager or
SICAM
TOOLBOX II
___,___,___ms
describe________________
_______________________
1.7.2 How often is time synchronization ☐ Never needs time Default = 300 sec configurable
required from the master: ☐ Within ______ seconds after IIN1.4 is 0=no time via SICAM
Details of when the master needs to set synchronization Device
perform a time synchronization to ensure ☐ Periodically, fixed at _______ seconds over DNP3 Manager or
that the outstation clock does not drift SICAM
☒ Periodically, between 0 and 65535
outside of an acceptable tolerance. If the TOOLBOX II
seconds
option to relate this to IIN1.4 is used then
details of when IIN1.4 is asserted are in
section 1.10.2.
1.7.3 Device Trouble Bit IIN1.6: ☒ Never used
If IIN1.6 device trouble bit is set under ☐ Reason for
certain conditions, explain the possible setting_________________________
causes.

DC8-037-2, Edition 11.2020
12.10 DNP3
methods
1.7.4 File Handle Timeout: ☒ Not applicable, files not supported
If there is no activity referencing a file ☐ Fixed at______ ms
handle for a configurable length of time, ☐ Configurable, range _______ to
the outstation must do an automatic _______ms
close on the file. The timeout value must ☐ Configurable, selectable from
be configurable up to 1 hour. When this ___,___,___ms
condition occurs the outstation will send
a File Transport Status Object (group 70
describe________________
var 6) using a status code value of file
handle expired (0x02). ☐ Variable, explain
_______________________
1.7.5 Event Buffer Overflow Behavior: ☒ Discard the oldest event Default = discard configurable
☒ Discard the newest event oldest via SICAM
☐ Other, explain Device
_________________________ Manager or
SICAM
TOOLBOX II

DC8-037-2, Edition 11.2020
12.10 DNP3
methods
1.7.6 Event Buffer Organization: ☒ Per Object Group (see part 3)
Explain how event buffers are arranged
(per Object Group, per Class, single
☐ Per Class
buffer, etc) and specify the number of
Class 1:
events that can be buffered.
☐ Fixed at______
☐ Configurable, range _______ to
_______
___,___,___
describe_____________
Class 2:
☐ Fixed at______
_______
___,___,___
describe_____________
Class 3:
☐ Fixed at______
_______
___,___,___
describe_____________
☐ Single Buffer
☐ Fixed at______
_______
___,___,___
describe_____________
☐ Other, describe ___________

1.7.7 Sends Multi-Fragment Responses: ☒ Yes Yes configurable
Indicates whether an Outstation sends ☐No via SICAM
multi-fragment responses (Masters do Device
not send multi-fragment requests). Manager or
SICAM
TOOLBOX II

DC8-037-2, Edition 11.2020
12.10 DNP3
methods
1.7.8 Last Fragment Confirmation: ☒ Always Never configurable
Indicates whether the Outstation ☐ Sometimes, explain via SICAM
requests confirmation of the last frag- _____________________ Device
ment of a multi-fragment response. ☒ Never Manager or
SICAM
TOOLBOX II
1.7.9 DNP Command Settings preserved ☒ Assign Class
through a device restart: ☒ Analog Deadbands
If any of these settings are written ☐ Data Set Prototypes
through the DNP protocol and they are ☐ Data Set Descriptors
not preserved through a restart of the
☐ Function Code 31 Activate Configura-
Outstation, the Master will have to write
tion
them again after it receives a response in
which the Restart IIN bit is set.
1.7.10 Supports configuration signature: ☐ Configuration signature supported
Indicates whether an Outstation supports
the Group 0 device attribute "Configura-
If configuration signature is supported,
tion signature" (variation 200). If yes, list
then the following algorithm(s) are avail-
the vendor-defined name(s) of the algo-
able for calculating the signature:
rithm(s) available to calculate the signa-
Algorithm Name: ____________________
ture.
Note: The algorithm used for calculating
the signature is identified by name in a
string that can be determined remotely
using protocol object Group 0 Variation
201. If only a single algorithm is avail-
able, identifying that algorithm in this
object is optional.
1.7.11 Requests Application Confirma- For event responses:
tion: ● Yes
Indicate if application confirmation is ○ No
requested: ○ Configurable
• when responding with events For non-final fragments:
• when sending non-final fragments ● Yes
of multi-fragment responses ○ No
Note: to be compliant both must be ○ Configurable
selected as "yes".
1.7.12 Supports Clock Management ☒ Yes
Indicates whether the Outstation ☐ No
supports the clock management func-
tionality:
• supports timestamped object varia-

tions required for its subset level
with a time accuracy that is consis-
tent with section 1.10 of this Device
Profile
• if the outstation asserts IIN1.4
[NEED_TIME], it shall support DNP3
time synchronization functionality

DC8-037-2, Edition 11.2020
12.10 DNP3
1.8 OUTSTATION UNSOLICITED Capabilities Current Value If configu-

RESPONSE SUPPORT rable, list
methods
1.8.1 Supports Unsolicited Reporting: ☐ Yes Yes
When the unsolicited response mode is ☐ No
configured "off", the device is to behave ☒ Configurable, selectable from On and
exactly like an equivalent device that has Off
no support for unsolicited responses. If
set to On, the Outstation will send a null
Unsolicited Response after it restarts,
then wait for an Enable Unsolicited
Response command from the master
before sending additional Unsolicited
Responses containing event data.
1.8.2 Master Data Link Address: ☐ Fixed at______
The destination address of the master ☒ Configurable, range 0 to 65519
device where the unsolicited responses ☐ Configurable, selectable from
will be sent. ____,____,____
describe________________
1.8.3 Unsolicited Response Confirmation ☐ Fixed at______ ms 10000 ms
Timeout: ☒ Configurable, range 0 to 655350 ms
This is the amount of time that the ☐ Configurable, selectable from
outstation will wait for an Application ___,___,___ms
Layer confirmation back from the master ☐ Configurable, other,
indicating that the master received the describe________________
unsolicited response message. As a
minimum, the range of configurable
_______________________
values must include times from one
second to one minute. This parameter
may be the same one that is used for
normal, solicited, application confirma-
tion timeouts, or it may be a separate
parameter.
1.8.4 Number of Unsolicited Retries: ☐ None 5
This is the number of retries that an ☐ Fixed at ___________
outstation transmits in each unsolicited ☒ Configurable, range 0 to 255
response series if it does not receive ☐ Configurable, selectable from
confirmation back from the master. ____,____,____
The configured value includes identical ☐ Configurable, other,
and regenerated retry messages. To be describe______________
compliant, one of the choices must
☐ Unlimited
provide for an indefinite (and potentially
infinite) number of transmissions.

DC8-037-2, Edition 11.2020
12.10 DNP3

RESPONSE TRIGGER CONDITIONS rable, list
methods
1.9.1 Number of class 1 events: ☐ Class 1 not used to trigger Unsolicited
Responses
☒ Fixed at DNPST0 = 10; DNPiT1 = 70
☐ Configurable, range ________ to
_______
____,____,____
describe______________
Responses
_______
____,____,____
describe______________
Responses
_______
____,____,____
describe______________
1.9.4 Total number events from any ☐ Total Number of Events not used to
class: trigger Unsolicited Responses
☐ Fixed at ___________
_______
____,____,____
describe______________
1.9.5 Hold time after class 1 event: ☐ Class 1 not used to trigger Unsolicited
A value of 0 indicates that responses are Responses
not delayed due to this parameter. ☒ Fixed at 1500 ms
_______ ms
____,____,____ ms
describe______________
☐ Use value specified in section 1.9.8

DC8-037-2, Edition 11.2020
12.10 DNP3

RESPONSE TRIGGER CONDITIONS rable, list
methods
_______ ms
____,____,____ ms
describe______________
_______ ms
____,____,____ ms
describe______________
1.9.8 Hold time after event assigned to ☐ Class events not used to trigger Unsoli-
any class: cited Responses
A configured value of 0 indicates that ☒ Fixed at 1500 ms
responses are not delayed due to this ☐ Configurable, range ________ to
parameter. _______ ms
____,____,____ ms
describe______________
1.9.9 Retrigger Hold Timer: ☐ Hold-time timer will be retriggered for
The hold-time timer may be retriggered each new event detected (may get more
for each new event detected (increased changes in next response)
possibly of capturing all the changes in a ☒ Hold-time timer will not be retriggered
single response) or not retriggered for each new event detected (guaranteed
(giving the master a guaranteed update update time)
time).
1.9.10 Other Unsolicited Response ____________________________
Trigger Conditions:

DC8-037-2, Edition 11.2020
12.10 DNP3
1.10 OUTSTATION PERFORMANCE Capabilities Current Value If configu-

rable, list
methods
1.10.1 Maximum Time Base Drift (milli- ☐ Fixed at 1 ms 1 ms
seconds per minute): ☐ Range ________ to _______ ms
If the device is synchronized by DNP, ☐ Selectable from ____,____,____ ms
what is the clock drift rate over the full ☐ Other, describe______________
operating temperature range.
1.10.2 When does outstation set IIN1.4: ☐ Never 300 seconds
When does the outstation set the internal ☐ Asserted at startup until first Time
indication IIN1.4 NEED_TIME. Synchronization request received
☐ Periodically every____ seconds
☒ Periodically, range 0 to 65535 seconds
☐ Periodically, selectable from
____,____,___ seconds ____ seconds after
last time sync
☐ Range ____to____ seconds after last
time sync
☐ Selectable from___,___,___ seconds
after last time sync
☐ When time error may have drifted by
____ ms
range ____to____ ms
selectable from ____,____,___ ms
1.10.3 Maximum Internal Time Refer- ☒ Fixed at 1 ms 100 ms
ence Error when set via DNP (ms): ☐ Range ________ to _______ ms
The difference between the time set in a ☐ Selectable from ____,____,____ ms
DNP Write Time message, and the time ☐ Other, describe______________
actually set in the Outstation.
1.10.4 Maximum Delay Measurement ☐ Fixed at ___________ ms +10 ms
error (ms): ☒ Range -20 ms to +20 ms
The difference between the time ☐ Selectable from ____,____,____ ms
reported in the delay measurement ☐ Other, describe
response and the actual time between
receipt of the delay measurement
request and issuing the delay measure-
ment reply.
1.10.5 Maximum Response time (ms): ☒ Fixed at 1000 ms 1000 ms
The amount of time an Outstation will ☐ Range ________ to _______ ms
take to respond upon receipt of a valid ☐ Selectable from ____,____,____ ms
request. This does not include the ☐ Other, describe______________
message transmission time.
1.10.6 Maximum time from start-up to ☒ Fixed at 0 ms 0 ms
IIN 1.4 assertion (ms): ☐ Range ________ to _______ ms
☐ Selectable from ____,____,____ ms
☐ Other, describe
until start up delay is finished

DC8-037-2, Edition 11.2020
12.10 DNP3
1.10 OUTSTATION PERFORMANCE Capabilities Current Value If configu-

rable, list
methods
1.10.7 Maximum Event Time-tag error ☒ Fixed at 100 ms 100 ms
for local Binary and Double-bit I/O (ms): ☐ Range ________ to _______ ms
The error between the time-tag reported ☐ Selectable from ____,____,____ ms
and the absolute time of the physical ☐ Other, describe
event. This error includes the Internal
Time Reference Error.
Note: The current value of this parameter
is available remotely using protocol
object Group 0 Variation 217.
1.10.8 Maximum Event Time-tag error ☒ Fixed at 100 ms 100 ms
for local I/O other than Binary and ☐ Range ________ to _______ ms
Double-bit data types (ms): ☐ Selectable from ____,____,____ ms
☐ Other, describe
1.11 INDIVIDUAL FIELD OUTSTATION PARAMETERS: Value of Current Setting If configurable, list
methods
1.11.1 User-assigned location name or code string (same as not supported
g0v245):
1.11.2 User-assigned ID Code/number string (same as g0v246): not supported
1.11.3 User-assigned name string for the outstation (same as not supported
g0v247):
1.11.4 Device Serial Number string (same as g0v248): not supported
1.11.5 User-assigned secondary operator name (same as not supported
g0v206):
1.11.6 User-assigned primary operator name (same as g0v207): not supported
1.11.7 User-assigned system name (same as g0v208): not supported
1.11.8 User-assigned owner name (same as g0v244): not supported

DC8-037-2, Edition 11.2020
12.10 DNP3
1.12 SECURITY PARAMETERS Capabilities Current Value If configu-

rable, list
methods
1.12.1 DNP3 device support for secure Supported version(s): not supported
authentication: ☐ Fixed at ___________
If the device does not support secure ☐ Configurable, selectable from
authentication then ignore the rest of ____,____,____
this section.
If the device does support secure authen-
tication then specify the version(s) that
are supported in the device. The version
number is an integer value defined in the
DNP3 Specification. The Secure Authenti-
cation procedure defined in IEEE
1815-2010 is version 2. The Secure
Authentication procedure defined in IEEE
1815-2012 is version 5.
1.12.2 Maximum number of users: ☐ Fixed at ___________ not supported
The secure authentication algorithm ☐ Configurable, range _______ to
provides support for multiple users. The _______
device must support details for each user
(update keys, session keys, etc). A user is
identified by a 16-bit user number,
allowing a maximum of 65535 users.
Devices are not mandated to support this
number of potential users. Indicate here
the actual limit to the number of simulta-
neous users that can be supported.
1.12.3 Security message response ☐ Fixed at ___________ ms not supported
timeout: ☐ Configurable, range _______ to
Authentication of critical messages may _______ ms
involve additional message exchanges ☐ Configurable, selectable from
(challenges and responses) which can ____,____,____ ms
require an extension to the normal DNP3 ☐ Configurable, other,
message response timeout. This timeout describe_______________
specifies an additional time to be used
when the extra security transactions are
involved. The maximum allowable
timeout extension should not exceed
120 seconds.
1.12.4 Aggressive mode of operation ○ Yes - accepts not supported
(receive): aggressive mode
DNP3 devices may (optionally) accept requests
"aggressive" mode requests, where chal- ● No – does not
lenge data used for authentication is accept aggressive
appended to a critical message rather mode requests
than needing to be solicited via a sepa-
rate message exchange.

DC8-037-2, Edition 11.2020
12.10 DNP3

rable, list
methods
1.12.5 Aggressive mode of operation ○ Yes - issues not supported
(issuing): aggressive mode
DNP3 devices must support the issuing of requests
"aggressive" mode of operation, where ● No – does not
challenge data used for authentication is issue aggressive
appended to a critical message rather mode requests
than needing to be solicited via a sepa-
rate message exchange. Specific
instances of devices may have the use of
aggressive mode switched off.
1.12.6 Session Key change interval: ☐ Can be disabled not supported
To counter an attack that compromises
the session key, the session key is
When enabled:
changed at regular intervals. The
maximum interval is 2 hours. Outstation
_______seconds
devices invalidate the current set of
session keys if they have not been
changed by the master station after a
period of twice this configured value.
To accommodate systems with infre-
quent communications, this change
interval can be disabled and just the
session key change message count used
(see 1.12.7)
1.12.7 Session Key change message ☐ Configurable, range _______ to not supported
count: _______
In addition to changing the session key at
regular intervals, the key shall also be
changed after a specified number of
messages have been exchanged. The
maximum allowable value for this
message count is 10,000
1.12.8 Maximum error count (SAv2 ☐ Not applicable (not using SAv2) not supported
only):
To assist in countering denial of service
attacks when using SAv2, a DNP3 device
_______
shall stop replying with error codes after
a number of successive authentication
failures. This error count has a maximum
value of 10. Setting the error count to
zero inhibits all error messages.
See 1.12.21 for error counts when using
SAv5

DC8-037-2, Edition 11.2020
12.10 DNP3

rable, list
methods
1.12.9 MAC algorithm requested in a ☐ SHA-1 (truncated to the leftmost 4 not supported
challenge exchange: octets)
Part of the authentication message is ☐ SHA-1 (truncated to the leftmost 8
hashed using an MAC algorithm. Secure octets)
Authentication version 2 specifies that ☐ SHA-1 (truncated to the leftmost 10
DNP3 devices must support SHA-1 and octets)
may optionally support SHA-256 for this ☐ SHA-256 (truncated to the leftmost 8
hashing process. Secure Authentication octets)
version 5 specifies that SHA-256 is the
☐ SHA-256 (truncated to the leftmost 16
default. The output of the MAC algorithm
octets)
is truncated (the resulting length
dependent on the media being used). ☐ AES-GMAC
☐ Other, explain _______________
1.12.10 Key-wrap algorithm to encrypt ☐ AES-128 not supported
session keys: ☐ AES-256
During the update of a session key, the ☐ Other, explain ______________
key is encrypted using AES-128 or
optionally using other algorithms.
1.12.11 Cipher Suites used with DNP ☐ Not relevant – TLS is not used not supported
implementations using TLS:
When TLS is supported, DNP3 Secure
☐ TLS_RSA encrypted with AES128
Authentication mandates the support of
☐ TLS_RSA encrypted with RC4_128
TLS_RSA_WITH_AES_128_SHA. The speci-
fication has a number of recommended ☐ TLS_RSA encrypted with
cipher suite combinations. Indicate the 3DES_EDE_CBC
supported Cipher Suites for implementa- ☐ TLS_DH, signed with DSS, encrypted
tions using TLS. with 3DES_EDE_CBC
☐ TLS_DH, signed with RSA, encrypted
with 3DES_EDE_CBC
☐ TLS_DHE, signed with DSS, encrypted
with 3DES_EDE_CBC
☐ TLS_DHE, signed with RSA, encrypted
with 3DES_EDE_CBC
☐ TLS_DH, signed with DSS, encrypted
with AES128
☐ TLS_DH, signed with DSS, encrypted
with AES256
☐ TLS_DH encrypted with AES128
☐ TLS_DH encrypted with AES256
☐ Other, explain _______________
1.12.12 Change cipher request timeout: ☐ Not relevant – TLS is not used not supported
Implementations using TLS shall termi-
nate the connection if a response to a
☐ Fixed at ___________
change cipher request is not seen within
this timeout period.
_______
____,____,____
describe_______________

DC8-037-2, Edition 11.2020
12.10 DNP3

rable, list
methods
1.12.13 Number of Certificate Authori- not supported
ties supported:
Implementations using TLS shall support
at least 4 Certificate Authorities. Indicate
the number supported.
1.12.14 Certificate Revocation check ☐ Not relevant – TLS is not used not supported
time:
Implementations using TLS shall evaluate
☐ Fixed at __________ hours
Certificate Revocation Lists on a periodic
basis, terminating a connection if a certif-
_______hours
icate is revoked.
____,____,____hours
describe_______________
1.12.15 Additional critical function Additional function codes that are to be not supported
codes: considered as "critical":
The DNP3 specification defines those ☐ 0 (Confirm)
messages with specific function codes ☐ 1 (Read)
that are critical and must be used as part ☐ 7 (Immediate freeze)
of a secure authentication message
☐ 8 (Immediate freeze – no ack)
exchange. Messages with other function
codes are optional and changes to this ☐ 9 (Freeze-and-clear)
list should be noted here. ☐ 10 (Freeze-and-clear – no ack)
Note: Secure Authentication version 5 ☐ 11 (Freeze-at-time)
defines additional functions as critical ☐ 12 (Freeze-at-time – no ack)
that were not considered critical in ☐ 22 (Assign Class)
version 2. These are shown in the next
☐ 23 (Delay Measurement)
column annotated with "V2 only".
☐ 25 (Open File) – V2 only
☐ 26 (Close File) – V2 only
☐ 27 (Delete File) – V2 only
☐ 28 (Get File Info) – V2 only
☐ 30 (Abort File) – V2 only
☐ 129 (Response)
☐ 130 (Unsolicited Response)
1.12.16 Other critical fragments: Describe any other critical fragment not supported
Other critical transactions can be defined exchanges:
and should be detailed here. Examples
could be based on time (for example: the
first transaction after a communications
session is established). Other examples
could be based on specific data objects
(for example: the reading of specific data
points).

DC8-037-2, Edition 11.2020
12.10 DNP3

rable, list
methods
1.12.17 Support for remote update key ☐ Remote update key change by not supported
changes: symmetric cryptography.
Devices implementing secure authentica- Supported key change methods:
tion version 5 or later have the option to ☐ AES-128 key wrap with SHA-1-HMAC
support remote update key changes. If ☐ AES-256 key wrap with SHA-256-
remote update key change is supported HMAC
then the procedure using symmetric
☐ AES-256 key wrap with AES-GMAC
cryptography is mandatory. Additional
support for the procedure using asym-
metric (public key) cryptography is ☐ Remote update key change by asym-
optional. metric cryptography
Supported key change methods:
☐ RSAES-OAEP-1024/SHA-1 with DSA
SHA-1 and SHA-1-HMAC
SHA-256 and AES-GMAC
SHA-256 and AES-GMAC
1.12.18 "Default" user credentials are ☐ Yes not supported
permitted to expire: ☐ No
1.12.19 Secure Authentication enabled: ☐ Configurable, selectable from On and not supported
Off
☐ Always On

DC8-037-2, Edition 11.2020
12.10 DNP3

rable, list
methods
1.12.20 Length of the challenge data: ☐ Fixed at ___________ octets not supported
The length of the challenge data used ☐ Configurable, range _______ to
when setting up session keys shall be _______ octets
between a minimum length of 4 octets ☐ Configurable, selectable from
and a maximum length of 32 octets. ____,____,____ octets
describe______________
1.12.21 Maximum statistic counts Max Authentication Failures: not supported
(SAv5):
☐ Not applicable (not using SAv5)
The SAv5 specification allows event
☐Configurable, range _______ to
objects to be generated when the statis-
_______
tics reach certain threshold values. Indi-
cate here how these thresholds are set if
using SAv5.
Max Reply Timeouts:
Note that "Max Rekeys Due to Restarts"
only applies to Masters and can be ☐ Not applicable (not using SAv5)
omitted from the Device Profile for ☐Configurable, range _______ to
Outstations. _______
Max Authentication Rekeys:

_______
Max Error Messages Sent:

_______
Max Rekeys Due to Restarts:

☐Not applicable (not using SAv5)
_______
1.13 BROADCAST FUNCTIONALITY Capabilities Current Value If configu-

rable, list
methods
This section indicates which functions are supported by the device when using broadcast addresses.
Note that this section shows only entries that may have a meaningful purpose when used with broadcast requests.
1.13.1 Support for broadcast function- ○ Disabled
ality: ● Enabled
○ Configurable

DC8-037-2, Edition 11.2020
12.10 DNP3

rable, list
methods
1.13.2 Write functions (FC = 2) Write clock (g50v1 with qualifier code
supported with broadcast requests: 07):
○Disabled
● Enabled
○ Configurable, other (described else-
where)
Write last recorded time (g50v3 with

qualifier code 07):
○ Disabled
● Enabled
where)
Clear RESTART (g80v1 with qualifier code

00 and index = 7, value = 0):
○ Disabled
● Enabled
where)
Write of any other group / variation /

qualifier code
○ Disabled
● Enabled
where)
1.13.3 Direct operate functions (FC = 5) ○ Disabled
supported with broadcast requests: ● Enabled
where)
1.13.4 Direct operate, no acknowledg- ○ Disabled
ment functions (FC = 6) supported with ● Enabled
broadcast requests: ○ Configurable, other (described else-
where)
1.13.5 Immediate freeze functions (FC = ○ Disabled
7) supported with broadcast requests: ● Enabled
where)
1.13.6 Immediate freeze, no acknowl- ○ Disabled
edgment functions (FC = 8) supported ● Enabled
with broadcast requests: ○ Configurable, other (described else-
where)
1.13.7 Freeze and clear functions (FC = ○ Disabled
9) supported with broadcast requests: ● Enabled
where)

DC8-037-2, Edition 11.2020
12.10 DNP3

rable, list
methods
1.13.8 Freeze and clear, no acknowledg- ○ Disabled
ment functions (FC = 10) supported with ● Enabled
where)
1.13.9 Freeze at time functions (FC = 11) ● Disabled
supported with broadcast requests: ○ Enabled
where)
1.13.10 Freeze at time, no acknowledg- ● Disabled
ment functions (FC = 12) supported with ○ Enabled
where)
1.13.11 Cold restart functions (FC = 13) ○ Disabled
where)
1.13.12 Warm restart functions (FC = 14) ○ Disabled
where)
1.13.13 Initialize data functions (FC = 15) ● Disabled
where)
1.13.14 Initialize application functions ● Disabled
(FC = 16) supported with broadcast ○ Enabled
requests: ○ Configurable, other (described else-
where)
1.13.15 Start application functions (FC = ● Disabled
17) supported with broadcast requests: ○ Enabled
where)
1.13.16 Stop application functions (FC = ● Disabled
18) supported with broadcast requests: ○ Enabled
where)
1.13.17 Save configuration functions (FC ● Disabled
= 19) supported with broadcast requests: ○ Enabled
where)

DC8-037-2, Edition 11.2020
12.10 DNP3

rable, list
methods
1.13.18 Enable unsolicited functions (FC Enable unsolicited by event Class (g60v2,
= 20) supported with broadcast requests: g60v3 and g60v4 with qualifier code 06):
○ Disabled
● Enabled
where)
Enable unsolicited for any other group /

variation / qualifier code:
○ Disabled
● Enabled
where)
1.13.19 Disable unsolicited functions (FC Disable unsolicited by event Class
= 21) supported with broadcast requests: (g60v2, g60v3 and g60v4 with qualifier
code 06):
○ Disabled
● Enabled
where)
Disable unsolicited for any other group /

variation / qualifier code:
○ Disabled
● Enabled
where)
1.13.20 Assign class functions (FC = 22) ○ Disabled
where)
1.13.21 Record current time functions ○ Disabled
(FC = 24) supported with broadcast ● Enabled
requests: ○ Configurable, other (described else-
where)
1.13.22 Activate configuration (FC = 31) ● Disabled
where)
2 Mapping to IEC 61850 Object Models

This optional section allows each configuration parameter or point in the DNP Data map to be tied to an attribute in the
IEC 61850 object models.
Earlier versions of this section (up to version 2.07) used mappings based on an "access point" section 2.1.1 and then a
series of XPath references (section 2.1.2).
Section 2.1.2 has been superseded in version 2012 onwards with mappings defined using either predefined rules
(section 2.1.3) or specified as an equation (section 2.1.4). The list of pre-defined rules is found in the IEEE 1815-1 docu-
ment.

DC8-037-2, Edition 11.2020
12.10 DNP3
TREE MAPPING BETWEEN DNP3 AND IEC 61850 OBJECTS

2.1.1 Access Point:
2.1.2 Mapping (section superseded)
2.1.3 Rule based mapping
Use this element when mapping to/from IEC 61850 using one of the predefined rules in IEEE 1815.1
Mapping is bi-directional.
IEC 61850 Object DNP Xpath Reference

MyIED
- LLN0
- Mod
- stVal Rule is: BOOLEAN_TO_BI
dnp:dataPointsList/dnp:binaryInputPoints/dnp:dataPoints/dnp:bina-
ryInput[dnp:index=0]/dnp:dnpData/dnp:state
-q Rule is: QUALITY_TO_BIN_FLAG
ryInput[dnp:index=0]/dnp:dnpData/dnp:quality
-t Rule is: TIME_TO_TIME
ryInput[dnp:index=0]/dnp:dnpData/dnp:timestamp
- Mod1
- stVal Rule is: DPS_TO_2_BI
-q Rule is: QUALITY_TO_BIN_FLAG
ryInput[dnp:index=1]/dnp:dnpData/dnp:q
ryInput[dnp:index=2]/dnp:dnpData/dnp:q
- LLN1
- Mod1.t
-t Rule is: TIME_TO_TIME
2.1.4 Equation based mapping

Use this element when mapping to/from IEC 61850 using an equation to map 0 or more input parameters to a single
output parameter. Direction of mapping is determined by the variable on the left hand side of the equation.
Equation DNP Xpath Reference / IEC 61850 FC CDC Data Type enumTypeId
parameter Path reference
Mapping Equation: celsius = ((value * scale) - 32) / 1.8
scale dnp:dataPointsList/dnp:analogInputPoints/dnp:dataPoints/dnp:analogInput[dnp:index=9]/dnp:scaleFactor
value dnp:dataPointsList/dnp:analogInputPoints/dnp:dataPoints/dnp:analogInput[dnp:index=10]/dnp:dnpData/
dnp:value
celsius MyIED/LLN0.Mod.mag MX MV FLOAT32

DC8-037-2, Edition 11.2020
12.10 DNP3
Equation DNP Xpath Reference / IEC 61850 FC CDC Data Type enumTypeId
parameter Path reference
Mapping Equation: value = ((celsius * 1.8) + 32) / scale
value dnp:dataPointsList/dnp:analogInputPoints/dnp:dataPoints/dnp:analogInput[dnp:index=11]/dnp:dnpData/
dnp:value
celsius MyIED/LLN0.Mod.mag MX MV FLOAT32
scale MyIED/LLN0.Mod.scaleFactor MX MV FLOAT32
3 Capabilities and Current Settings for Device Database (Outstations Only)

The following tables identify the capabilities and current settings for each DNP3 data type. Details defining the data
points available in the device are shown in part 5 of this Device Profile.
3.1 BINARY INPUTS Capabilities Current Value If configu-

Static (Steady-State) Group Number: 1 (leave tick-boxes blank if this data type rable, list
Event Group Number: 2 is not supported) methods
3.1.1 Static Variation reported when ☒ Variation 1 – packed format Variation 1
variation 0 requested or in response to ☒ Variation 2 – with flag
Class polls: ☐ Based on point Index (add column to
table in part 5)
3.1.2 Event Variation reported when ☒ Variation 1 – without time Variation 2
variation 0 requested or in response to ☒ Variation 2 – with absolute time
Class polls: ☒ Variation 3 – with relative time
Note: The support for binary input events ☐ Based on point Index (add column to
can be determined remotely using table in part 5)
3.1.3 Event reporting mode: ☐ Only most recent
When responding with event data and ☒ All events
more than one event has occurred for a ☐ Based on point Index (add column to
data point, an Outstation may include all table in part 5)
events or only the most recent event. "All
events" must be checked to be
compliant.
3.1.4 Binary Inputs included in Class 0 ☒ Always
response: ☐ Never
☐ Only if the point is assigned to a class
☐ Based on point Index (add column to
table in part 5)
3.1.5 Binary Inputs Event Buffer Organi- ☒ Fixed at DNPST0 = 250; DNPiT1 = 2000
zation: ☐ Configurable, range _______ to
When event buffers are allocated per _______
object group (see part 1.7.6), indicate ☐ Configurable, selectable from
the number of events that can be ____,____,____
buffered for Binary Inputs. If event ☐ Configurable, other,
buffers are not allocated per object group describe_______________
then set "Fixed at 0".

DC8-037-2, Edition 11.2020
12.10 DNP3
3.2 DOUBLE-BIT BINARY INPUTS Capabilities Current Value If configu-

Static (Steady-State) Group Number: 3 (leave tick-boxes blank if this data type rable, list
Event Group Number: 4 is not supported) methods
variation 0 requested or in response to ☒ Variation 2 – with flag
Note: The support for double-bit binary table in part 5)
inputs can be determined remotely using
3.2.2 Event Variation reported when ☒ Variation 1 – without time Variation 2
variation 0 requested or in response to ☒ Variation 2 – with absolute time
Class polls: ☒ Variation 3 – with relative time
table in part 5)
3.2.3 Event reporting mode: ☒ Only most recent
When responding with event data and ☐ All events
events or only the most recent event. "All
events" must be checked to be
compliant.
3.2.4 Double-bit Binary Inputs included in ☒ Always
Class 0 response: ☐ Never
table in part 5)
3.2.5 Double-bit Binary Inputs Event ☒ Fixed at DNPST0 = 250; DNPiT1 = 2000
Buffer Organization: ☐ Configurable, range _______ to
buffered for Double-bit Binary Inputs. If ☐ Configurable, other,
event buffers are not allocated per object describe_______________
group then set "Fixed at 0".
3.3 BINARY OUTPUT STATUS AND Capabilities Current Value If configu-

CONTROL RELAY OUTPUT BLOCK (leave tick-boxes blank if this data type rable, list
Binary Output Status Group Number: is not supported) methods
10
Binary Output Event Group Number:
11
CROB Group Number: 12
Binary Output Command Event Group
Number: 13
3.3.1 Minimum pulse time allowed with ☒ Fixed at 100 ms (hardware may limit
Trip, Close, and Pulse On commands: this further)
table in part 5)
3.3.2 Maximum pulse time allowed with ☒ Fixed at 60000 ms (hardware may
Trip, Close, and Pulse On commands: limit this further)
table in part 5)

DC8-037-2, Edition 11.2020
12.10 DNP3

10
11
Number: 13
3.3.3 Binary Output Status included in ☒ Always
table in part 5)
3.3.4 Reports Output Command Event ☒ Never
Objects: ☐ Only upon a successful Control
☐ Upon all control attempts
variation 0 requested or in response to ☒ Variation 2 – output status with flags
table in part 5)
3.3.6 Event Variation reported when ☐ Variation 1 – status without time Not supported
variation 0 requested or in response to ☐ Variation 2 – status with time
Note: The support for binary output table in part 5)
events can be determined remotely using
3.3.7 Command Event Variation reported ☐ Variation 1 – command status without Not supported
when variation 0 requested or in time
response to Class polls: ☐ Variation 2 – command status with
time
table in part 5)
3.3.8 Event reporting mode: ☐ Only most recent Not supported
more than one event has occurred for a
data point, an Outstation may include all
events or only the most recent event
3.3.9 Command Event reporting mode: ☐ Only most recent Not supported
events or only the most recent event

DC8-037-2, Edition 11.2020
12.10 DNP3

10
11
Number: 13
3.3.10 Maximum Time between Select ☐ Not Applicable 20 seconds
and Operate: ☐ Fixed at _____ seconds
☒ Configurable, range 0.1 to 6553.5
seconds
☐ Configurable, selectable
from___,___,___ seconds
describe________________
_______________________
table in part 5)
3.3.11 Binary Outputs Event Buffer ☐ Fixed at ___________ Not supported
Organization: ☐ Configurable, range _______ to
object group (see part 1.7.6), indicate ☐Configurable, selectable from
buffered for Binary Outputs. If event ☐ Configurable, other,
3.3.12 Binary Output Commands Event ☐ Fixed at ___________ Not supported
buffered for Binary Output Commands. If ☐ Configurable, other,

DC8-037-2, Edition 11.2020
12.10 DNP3
3.4 COUNTERS/FROZEN COUNTERS Capabilities Current Value If configu-

Counter Group Number: 20 (leave tick-boxes blank if this data type rable, list
Frozen Counter Group Number: 21 is not supported) methods
Counter Event Group Number: 22
Frozen Counter Event Group Number:
23
3.4.1 Static Counter Variation reported ☒ Variation 1 – 32-bit with flag Variation 1
when variation 0 requested or in ☒ Variation 2 – 16-bit with flag
response to Class polls: ☒ Variation 5 – 32-bit without flag
☒ Variation 6 – 16-bit without flag
table in part 5)
3.4.2 Counter Event Variation reported ☒ Variation 1 – 32-bit with flag Variation 1
when variation 0 requested or in ☒ Variation 2 – 16-bit with flag
response to Class polls: ☒ Variation 5 – 32-bit with flag and time
Note: The support for counter events can ☒ Variation 6 – 16-bit with flag and time
be determined remotely using protocol
object Group 0 Variation 227.
table in part 5)
3.4.3 Counters included in Class 0 ☒ Always
response: ☐ Never
table in part 5)
3.4.4 Counter Event reporting mode: ☐ Only most recent (value at time of
When responding with event data and event)
more than one event has occurred for a ☒ Only most recent (value at time of
data point, an Outstation may include all response)
events or only the most recent event. ☐ All events
Only the most recent event is typically ☐ Based on point Index (add column to
reported for Counters. When reporting table in part 5)
"only most recent", the counter value
reported in the response may be the
value at the time of the original event or
it may be the value at the time of the
response.
3.4.5 Static Frozen Counter Variation ☒ Variation 1 – 32-bit with flag Variation 1
reported when variation 0 requested or ☒ Variation 2 – 16-bit with flag
in response to Class polls: ☐ Variation 5 – 32-bit with flag and time
☐ Variation 6 – 16-bit with flag and time
table in part 5)
3.4.6 Frozen Counter Event Variation ☒ Variation 1 – 32-bit with flag Variation 1
reported when variation 0 requested or ☒ Variation 2 – 16-bit with flag
in response to Class polls: ☒ Variation 5 – 32-bit with flag and time
Note: The support for frozen counter ☒ Variation 6 – 16-bit with flag and time
table in part 5)

DC8-037-2, Edition 11.2020
12.10 DNP3

23
3.4.7 Frozen Counters included in Class 0 ☐ Always
response: ☒ Never
table in part 5)
3.4.8 Frozen Counter Event reporting ☐ Only most recent frozen value
mode: ☒ All frozen values
When responding with event data and ☐ Based on point Index (add column to
more than one event has occurred for a table in part 5)
events or only the most recent event. All
events are typically reported for Frozen
Counters.
3.4.9 Counters Roll Over at: ☒ 16 Bits (65,535) 32 Bits
☒ 32 Bits (4,294,967,295)
☐ Other Fixed Value _________
☐ Configurable; range _________
to__________
___,___,___
describe________________
table in part 5)
3.4.10 Counters frozen by means of: ☒ Master Request
☐ Freezes itself without concern for time
of day
☐ Freezes itself and requires time of day
☐ Other, explain
_____________________________
3.4.11 Counters Event Buffer Organiza- ☒ Fixed at DNPST0 = 250; DNPiT1 = 2000
tion: ☐ Configurable, range _______ to
buffered for Counters. If event buffers ☐ Configurable, other,
are not allocated per object group then describe_______________
set "Fixed at 0".

DC8-037-2, Edition 11.2020
12.10 DNP3

23
3.4.12 Frozen Counters Event Buffer ☒ Fixed at DNPST0 = 250; DNPiT1 = 2000
buffered for Frozen Counters. If event ☐ Configurable, other,
3.4.13 Reports counter events for change ☒ Yes for all counters
of value: ☐ No for all counters
Indicate if counter events are created ☐ Configurable, based on point Index
when the counter value changes. (add column to table in part 5)
3.5 ANALOG INPUTS / FROZEN ANALOG Capabilities Current Value If configu-

INPUTS (leave tick-boxes blank if this data type rable, list
Static (Steady-State) Group Number: is not supported) methods
30
Static Frozen Group Number: 31
Event Group Number: 32
Frozen Analog Input Event Group
Number: 33
Deadband Group Number: 34
3.5.1 Static Variation reported when ☒ Variation 1 – 32-bit with flag Variation 1
variation 0 requested or in response to ☒ Variation 2 – 16-bit with flag
Class polls: ☒ Variation 3 – 32-bit without flag
☒ Variation 5 – single-precision floating
point with flag
☐ Variation 6 – double-precision floating
point with flag
table in part 5)
3.5.2 Event Variation reported when ☒ Variation 1 – 32-bit without time Variation 3
variation 0 requested or in response to ☒ Variation 2 – 16-bit without time
Class polls: ☒ Variation 3 – 32-bit with time
Note: The support for analog input ☒ Variation 4 – 16-bit with time
point w/o time
point w/o time
point with time
point with time
table in part 5)

DC8-037-2, Edition 11.2020
12.10 DNP3

30
Number: 33
3.5.3 Event reporting mode: ☐ Only most recent (value at time of All events
When responding with event data and event)
more than one event has occurred for a ☒ Only most recent (value at time of
data point, an Outstation may include all response)
events or only the most recent event. ☒ All events
Only the most recent event is typically ☐ Based on point Index (add column to
reported for Analog Inputs. When table in part 5)
reporting "only most recent", the analog
value reported in the response may be
the value at the time of the original
event or it may be the value at the time
of the response.
3.5.4 Analog Inputs Included in Class 0 ☒ Always
response: ☐ Never
table in part 5)
3.5.5 How Deadbands are set: ☐ A. Global Fixed
☒ B. Configurable through DNP
☐ C. Configurable via other means
☒ D. Other, explain configurable via
SICAM Device Manager or
SICAM TOOLBOX II
☐ Based on point Index - column in part
5 specifies which of the options applies,
B, C, or D
3.5.6 Analog Deadband Algorithm: ☒ Simple
simple - just compares the difference ☐ Integrating
from the previous reported value ☐ Other, explain
integrating - keeps track of the accumu- _____________________________
lated change ☐ Based on point Index (add column to
other - indicating another algorithm table in part 5)

DC8-037-2, Edition 11.2020
12.10 DNP3

30
Number: 33
3.5.7 Static Frozen Analog Input Varia- ☐ Variation 1 – 32-bit with flag Not supported
tion reported when variation 0 requested ☐ Variation 2 – 16-bit with flag
or in response to Class polls: ☐ Variation 3 – 32-bit with time-of-
freeze
☐ Variation 4 – 16-bit with time-of-
freeze
☐ Variation 5 – 32-bit without flag
☐ Variation 6 – 16-bit without flag
☐ Variation 7 – Single-precision, floating-
point with flag
☐ Variation 8 – Double-precision,
floating-point with flag
table in part 5)
3.5.8 Frozen Analog Input Event Varia- ☐ Variation 1 – 32-bit without time Not supported
tion reported when variation 0 requested ☐ Variation 2 – 16-bit without time
or in response to Class polls: ☐ Variation 3 – 32-bit with time
Note: The support for frozen analog ☐ Variation 4 – 16-bit with time
input events can be determined remotely
using protocol object Group 0 Variation
point without time
230.
floating-point without time
point with time
floating-point with time
table in part 5)
3.5.9 Frozen Analog Inputs included in ☐ Always Not supported
table in part 5)
3.5.10 Frozen Analog Input Event ☐ Only most recent frozen value Not supported
reporting mode: ☐ All frozen values
When responding with event data and ☐ Based on point Index (add column to
more than one event has occurred for a table in part 5)
events or only the most recent event. All
events are typically reported for Frozen
Analog Inputs.

DC8-037-2, Edition 11.2020
12.10 DNP3

30
Number: 33
3.5.11 Analog Inputs Event Buffer Organ- ☒ Fixed at DNPST0 = 250; DNPiT1 = 2000
ization: ☐ Configurable, range _______ to
buffered for Analog Inputs. If event ☐ Configurable, other,
3.5.12 Frozen Analog Inputs Event Buffer ☐ Fixed at ___________ Not supported
buffered for Frozen Analog Inputs. If ☐ Configurable, other,
3.6 ANALOG OUTPUTS / ANALOG Capabilities Current Value If configu-

OUTPUT COMMANDS (leave tick-boxes blank if this data type rable, list
Analog Output Status Group Number: is not supported) methods
40
Analog Outputs Group Number: 41
Analog Output Events Group Number:
42
Analog Output Command Events
Group Number: 43
3.6.1 Static Analog Output Status Varia- ☒ Variation 1 – 32-bit with flag Variation 1
tion reported when variation 0 requested ☒ Variation 2 – 16-bit with flag
or in response to Class polls: ☒ Variation 3 – single-precision floating
point with flag
point with flag
table in part 5)
3.6.2 Analog Output Status Included in ☒ Always
table in part 5)
3.6.3 Reports Output Command Event ☒ Never
Objects: ☐ Only upon a successful Control
☐ Upon all control attempts

DC8-037-2, Edition 11.2020
12.10 DNP3

40
42
Group Number: 43
3.6.4 Event Variation reported when ☐ Variation 1 – 32-bit without time Not supported
variation 0 requested or in response to ☐ Variation 2 – 16-bit without time
Class polls: ☐ Variation 3 – 32-bit with time
Note: The support for analog output ☐ Variation 4 – 16-bit with time
☐ Variation 5 – single-precision floating
point w/o time
point w/o time
point with time
point with time
table in part 5)
3.6.5 Command Event Variation reported ☐ Variation 1 – 32-bit without time Not supported
when variation 0 requested or in ☐ Variation 2 – 16-bit without time
response to Class polls: ☐ Variation 3 – 32-bit with time
☐ Variation 4 – 16-bit with time
point w/o time
point w/o time
point with time
point with time
table in part 5)
events or only the most recent event.
3.6.7 Command Event reporting mode: ☐ Only most recent Not supported

DC8-037-2, Edition 11.2020
12.10 DNP3

40
42
Group Number: 43
3.6.8 Maximum Time between Select ☐ Not Applicable 20 seconds
and Operate: ☐ Fixed at _____ seconds
☒ Configurable, range 0.1 to 6553.5
seconds
___,___,___seconds
describe________________
_______________________
table in part 5)
3.6.9 Analog Outputs Event Buffer ☐ Fixed at ___________ Not supported
buffered for Analog Outputs. If event ☐ Configurable, other,
3.6.10 Analog Output Commands Event ☐ Fixed at ___________ Not supported
buffered for Analog Output Commands. ☐ Configurable, other,
If event buffers are not allocated per describe_______________
object group then set "Fixed at 0".
3.7 FILE CONTROL Capabilities Current Value If configu-

Group Number: 70 rable, list
methods
3.7.1 File Transfer Supported: Supported (as defined in section 1.1.8)
If not supported then do not complete
other entries in section 3.7)
3.7.2 File Authentication: ☐ Always
Indicates whether a valid authentication ☐ Sometimes, explain
key must be obtained prior to open and _____________________
delete requests. ☐ Never
3.7.3 File Append Mode: ☐ Always
Indicates if a file can be opened and ☐ Sometimes, explain
appended to versus just overwritten. _____________________
☐ Never

DC8-037-2, Edition 11.2020
12.10 DNP3
3.7 FILE CONTROL Capabilities Current Value If configu-

methods
3.7.4 Permissions Support: ☐ Owner Read Allowed: 0x0100
Indicates the device is capable of using ☐ Owner Write Allowed: 0x0080
the indicated permissions. ☐ Owner Execute Allowed: 0x0040
☐ Group Read Allowed: 0x0020
☐ Group Write Allowed: 0x0010
☐ Group Execute Allowed: 0x0008
☐ World Read Allowed: 0x0004
☐ World Write Allowed: 0x0002
☐ World Execute Allowed: 0x0001
3.7.5 Multiple Blocks in a Fragment: ☐ Yes
File data is transferred in a series of ☐ No
blocks of a maximum specified size. This
indicates whether only a single block or
multiple blocks will be sent in fragment.
3.7.6 Max number of Files Open at one ☐ Fixed at _________
time: ☐ Configurable, range ________ to
_______
____,____,____
describe______________
3.8 OCTET STRING & EXTENDED OCTET Capabilities Current Value If configu-
STRING POINTS (leave tick-boxes blank if this data type rable, list
110, 114
Event Group Number: 111, 115
3.8.2 Octet Strings Included in Class 0 ☐ Always Not supported
response: ☐ Never
table in part 5)

DC8-037-2, Edition 11.2020
12.10 DNP3
3.8 OCTET STRING & EXTENDED OCTET Capabilities Current Value If configu-
STRING POINTS (leave tick-boxes blank if this data type rable, list
110, 114
Event Group Number: 111, 115
3.8.3 Octet Strings Event Buffer Organi- ☐ Fixed at ___________ Not supported
zation: ☐ Configurable, range _______ to
buffered for Octet Strings. If event ☐ Configurable, other,
3.8.4 Object Group Selection ☐ Fixed, group 110 for all objects Not supported
Indicate which object group is used to ☐ Fixed, group 114 for all objects
transport octet string objects. ☐ Configurable, group 110 or 114 for all
objects
table in part 5)
3.9 VIRTUAL TERMINAL PORT NUMBERS Capabilities Current Value If configu-

(POINTS) rable, list
Static (Steady-State) Group Number: methods
112
3.9.1 Virtual Terminals Event Buffer ☐ Fixed at ___________ Not supported
buffered for Virtual Terminals. If event ☐ Configurable, other,
3.10 DATA SET PROTOTYPE Capabilities Current Value If configu-

Variation Number: 1 methods
This version of the Device Profile document has no requirement for describing Data Set Prototype capabilities
and current settings. This page is intentionally left blank, existing as a placeholder for future use.
3.11 DATA SET DESCRIPTOR CONTENTS Capabilities Current Value If configu-
AND CHARACTERISTICS rable, list
Group Number: 86 methods
Variation Numbers: 1 and 2
This version of the Device Profile document has the requirement for describing Data Set Descriptor capabilities being
repeated for each Data Set (details can be found in section 5.11).
4 IMPLEMENTATION TABLE
The following implementation table identifies which object groups and variations, function codes and qualifiers the
device supports in both requests and responses. The Request columns identify all requests that may be sent by a Master,
or all requests that must be parsed by an Outstation. The Response columns identify all responses that must be parsed by
a Master, or all responses that may be sent by an Outstation.

DC8-037-2, Edition 11.2020
12.10 DNP3
NOTE The implementation table must list all functionality implemented in the Device.
4.1 DNP3 OBJECT GROUP & VARIATION

The following table identifies the objects variations, function codes, and qualifiers supported by the DNP3 Master imple-
mentation for CP-8000/802x (using Triangle MicroWorks, Inc. DNP3 Slave Source Code Library) in both request messages
and in response messages.
OBJECT REQUEST RESPONSE

(Library may send) (Library will parse)
Object Varia- Description Function Codes Qualifier Codes Function Codes Qualifier Codes
Number tion (dec) (hex) (dec) (hex)
Number
1 0 Binary Input – Any Varia- 1 (read) 00, 01 (start-
tion 22 (assign class) stop)
06 (no range, or
all)
07, 08 (limited
qty)
17, 28 (index)
1 1 Binary Input 1 (read) 00, 01 (start- 129 (response) 00, 01 (start-stop)
stop) 17, 28(index)
06 (no range, or
all)
07, 08 (limited
qty)
17, 28 (index)
1 2 Binary Input with Status 1 (read) 00, 01 (start- 129 (response) 00, 01 (start-stop)
stop) 17, 28(index)
06 (no range, or
all)
07, 08 (limited
qty)
17, 28 (index)
2 0 Binary Input Change – 1 (read) 06 (no range, or
Any Variation all)
07, 08 (limited
qty)
2 1 Binary Input Change 1 (read) 06 (no range, or 129 (response) 17, 28 (index)
without Time all) 130 (unsol. resp)
07, 08 (limited
qty)
with Time all) 130 (unsol. resp)
07, 08 (limited
qty)
with Relative Time all) 130 (unsol. resp)
07, 08 (limited
qty)

DC8-037-2, Edition 11.2020
12.10 DNP3

3 0 Double Bit Input – Any 1 (read) 00, 01 (start-
Variation 22 (assign class) stop)
06 (no range, or
all)
07, 08 (limited
qty)
17, 28 (index)
3 1 Double Bit Input 1 (read) 00, 01 (start- 129 (response) 00, 01 (start-stop)
stop) 17, 28(index)
06 (no range, or
all)
07, 08 (limited
qty)
17, 28 (index)
3 2 Double Bit Input with 1 (read) 00, 01 (start- 129 (response) 00, 01 (start-stop)
Status stop) 17, 28(index)
06 (no range, or
all)
07, 08 (limited
qty)
17, 28 (index)
4 0 Double Bit Input Change 1 (read) 06 (no range, or
– Any Variation all)
07, 08 (limited
qty)
4 1 Double Bit Input Change 1 (read) 06 (no range, or 129 (response) 17, 28 (index)
without Time all) 130 (unsol. resp)
07, 08 (limited
qty)
with Time all) 130 (unsol. resp)
07, 08 (limited
qty)
with Relative Time all) 130 (unsol. resp)
07, 08 (limited
qty)
10 0 Binary Output – Any 1 (read) 00, 01 (start-
06 (no range, or
all)
07, 08 (limited
qty)
17, 28 (index)

DC8-037-2, Edition 11.2020
12.10 DNP3

10 1 Binary Output 1 (read) 00, 01 (start- 129 (response) 00, 01 (start-stop)
stop) 17, 28(index)
06 (no range, or
all)
07, 08 (limited
qty)
17, 28 (index)
1 (write) 00, 01 (start-
stop)
10 2 Binary Output Status 1 (read) 00, 01 (start- 129 (response) 00, 01 (start-stop)
stop) 17, 28(index)
06 (no range, or
all)
07, 08 (limited
qty)
17, 28 (index)
12 1 Control Relay Output 3 (select) 17, 28 (index) 129 (response) echo of request
Block 4 (operate)
5 (direct op)
6 (dir. op, no 17, 28 (index)
ack)
20 0 Binary Counter – Any 1 (read) 00, 01 (start-
06 (no range, or
all)
07, 08 (limited
qty)
17, 28 (index)
7 (freeze) 00, 01 (start-
8 (freeze no ack) stop)
9 (freeze and 06 (no range, or
clear) all)
10 (frz. cl. no 07, 08 (limited
ack) qty)
17, 28 (index)
20 1 32-Bit Binary Counter 1 (read) 00, 01 (start- 129 (response) 2020
(with Flag) stop)
06 (no range, or
all)
07, 08 (limited
qty)
17, 28 (index)
20 2 16-Bit Binary Counter 1 (read) 00, 01 (start- 129 (response) 20
(with Flag) stop)
06 (no range, or
all)
07, 08 (limited
qty)
17, 28 (index)

DC8-037-2, Edition 11.2020
12.10 DNP3

20 5 32-Bit Binary Counter 1 (read) 00, 01 (start- 129 (response) 00, 01 (start-stop)
without Flag stop) 17, 28(index)
06 (no range, or
all)
07, 08 (limited
qty)
17, 28 (index)
20 6 16-Bit Binary Counter 1 (read) 00, 01 (start- 129 (response) 00, 01 (start-stop)
06 (no range, or
all)
07, 08 (limited
qty)
17, 28 (index)
21 0 Frozen Counter – Any 1 (read) 00, 01 (start-
06 (no range, or
all)
07, 08 (limited
qty)
17, 28 (index)
21 1 32-Bit Frozen Counter 1 (read) 00, 01 (start- 129 (response) 00, 01 (start-stop)
(with Flag) stop) 17, 28(index)
06 (no range, or
all)
07, 08 (limited
qty)
17, 28 (index)
(with Flag) stop) 17, 28(index)
06 (no range, or
all)
07, 08 (limited
qty)
17, 28 (index)
with Time Of Freeze stop) 17, 28(index)
06 (no range, or
all)
07, 08 (limited
qty)
17, 28 (index)
with Time Of Freeze stop) 17, 28(index)
06 (no range, or
all)
07, 08 (limited
qty)
17, 28 (index)

DC8-037-2, Edition 11.2020
12.10 DNP3

06 (no range, or
all)
07, 08 (limited
qty)
17, 28 (index)
06 (no range, or
all)
07, 08 (limited
qty)
17, 28 (index)
22 0 Counter Change Event – 1 (read) 06 (no range, or
Any Variation all)
07, 08 (limited
qty)
22 1 32-Bit Counter Change 1 (read) 06 (no range, or 129 (response) 17, 28 (index)
Event all) 130 (unsol. resp)
without Time 07, 08 (limited
qty)
qty)
with Time 07, 08 (limited
qty)
qty)
23 0 Frozen Counter Event 1 (read) 06 (no range, or 17, 28 (index)
(Variation 0 is used to all)
request default variation) 07, 08 (limited
qty)
23 1 32-Bit Frozen Counter 1 (read) 06 (no range, or 129 (response) 17, 28 (index)
07, 08 (limited
qty)
07, 08 (limited
qty)
qty)

DC8-037-2, Edition 11.2020
12.10 DNP3

qty)
30 0 Analog Input - Any Varia- 1 (read) 00, 01 (start-
tion 22 (assign class) stop)
06 (no range, or
all)
07, 08 (limited
qty)
17, 28 (index)
30 1 32-Bit Analog Input 1 (read) 00, 01 (start- 129 (response) 00, 01 (start-stop)
stop) 17, 28(index)
06 (no range, or
all)
07, 08 (limited
qty)
17, 28 (index)
stop) 17, 28(index)
06 (no range, or
all)
07, 08 (limited
qty)
17, 28 (index)
06 (no range, or
all)
07, 08 (limited
qty)
17, 28 (index)
06 (no range, or
all)
07, 08 (limited
qty)
17, 28 (index)
30 5 short floating point 1 (read) 00, 01 (start- 129 (response) 00, 01 (start-stop)
stop) 17, 28(index)
06 (no range, or
all)
07, 08 (limited
qty)
17, 28 (index)
32 0 Analog Change Event – 1 (read) 06 (no range, or
Any Variation all)
07, 08 (limited
qty)

DC8-037-2, Edition 11.2020
12.10 DNP3

32 1 32-Bit Analog Change 1 (read) 06 (no range, or 129 (response) 17, 28 (index)
qty)
qty)
qty)
qty)
32 5 short floating point 1 (read) 06 (no range, or 129 (response) 17, 28 (index)
Analog Change Event all) 130 (unsol. resp)
qty)
32 7 short floating point 1 (read) 06 (no range, or 129 (response) 17, 28 (index)
Analog Change Event all) 130 (unsol. resp)
qty)
34 0 Analog Input Deadband 1 (read) 00, 01 (start-
(Variation 0 is used to stop)
request default variation) 06 (no range, or
all)
07, 08 (limited
qty)
17, 28 (index)
34 1 16 bit Analog Input 1 (read) 00, 01 (start- 129 (response) 00, 01 (start-stop)
Deadband stop) 17, 28(index)
06 (no range, or
all)
07, 08 (limited
qty)
17, 28 (index)
2 (write) 17, 28 (index)
34 2 32 bit Analog Input 1 (read) 00, 01 (start- 129 (response) 00, 01 (start-stop)
Deadband stop) 17, 28(index)
06 (no range, or
all)
07, 08 (limited
qty)
17, 28 (index)

DC8-037-2, Edition 11.2020
12.10 DNP3

34 3 Short Floating Point 1 (read) 00, 01 (start- 129 (response) 00, 01 (start-stop)
Analog Input Deadband stop) 17, 28(index)
06 (no range, or
all)
07, 08 (limited
qty)
17, 28 (index)
40 0 Analog Output Status 1 (read) 00, 01 (start-
(Variation 0 is used to 22 (assign class) stop)
request default variation) 06 (no range, or
all)
07, 08 (limited
qty)
17, 28 (index)
40 1 32-Bit Analog Output 1 (read) 00, 01 (start- 129 (response) 00, 01 (start-stop)
06 (no range, or
all)
07, 08 (limited
qty)
17, 28 (index)
40 2 16-Bit Analog Output 1 (read) 00, 01 (start- 129 (response) 00, 01 (start-stop)
06 (no range, or
all)
07, 08 (limited
qty)
17, 28 (index)
40 3 short floating point 1 (read) 00, 01 (start- 129 (response) 00, 01 (start-stop)
Analog Output Status stop) 17, 28(index)
06 (no range, or
all)
07, 08 (limited
qty)
17, 28 (index)
41 1 32-Bit Analog Output 3 (select) 17, 28 (index) 129 (response) echo of request
Block 4 (operate)
5 (direct op)
ack)
41 2 16-Bit Analog Output 3 (select) 17, 28 (index) 129 (response) echo of request
Block 4 (operate)
5 (direct op)
ack)

DC8-037-2, Edition 11.2020
12.10 DNP3

41 3 short floating point 3 (select) 17, 28 (index) 129 (response) echo of request
Analog Output Block 4 (operate)
5 (direct op)
ack)
50 1 Time and Date 1 (read) 07 (limited qty = 129 (response) 07 (limited quan-
1) tity = 1)
2 (write) 07 (limited qty =
1)
51 1 Time and Date CTO 129 (response) ) 07 (limited quan-
130 (unsol. resp) tity = 1)
51 2 Unsynchronized Time 129 (response) ) 07 (limited quan-
and Date CTO 130 (unsol. resp) tity = 1)
52 1 Time Delay Coarse 129 (response) 07 (limited quan-
tity = 1)
52 2 Time Delay Fine 129 (response) 07 (limited quan-
tity = 1)
60 1 Class 0 Data 1 (read) 06 (no range, or
all)
all)
07, 08 (limited
qty)
20 (enable. 06 (no range, or
unsol.) all)
21 (disable
unsol.)
22 (assign class)
all)
07, 08 (limited
qty)
unsol.) all)
21 (disable
unsol.)
22 (assign class)
all)
07, 08 (limited
qty)
unsol.) all)
21 (disable
unsol.)
22 (assign class)
80 1 Internal Indications 1 (read) 00, 01 (start- 129 (response) 00, 01 (start-stop)
stop)
2 (write) 00 (start-stop)
index = 4 or 7

DC8-037-2, Edition 11.2020
12.10 DNP3
4.2 FUNCTION CODES
Application Layer Function Codes

Functioncode Mnemonic Description
0 Confirm Message Application Confirmation
1 Read Request/Response of data objects
2 Write Store data objects, reply with status (only for write data and time,
write analog deadband and clear internal indication bit restart)
3 Select SBO Control Select – reply with status
4 Operate SBO Operate – reply with status
5 Direct Operate Select and Operate relays – reply with status (IIN)
6 Direct Operate - Select and Operate relays – no status reply
no Acknowledgement
7 Immediate Freeze Copy specified objects to freeze buffer, reply with status (IIN)
8 Immediate Freeze - Copy objects to freeze buffer, no status reply
no Acknowledgement
9 Freeze and Clear Copy objects to freeze buffer then reset objects and reply (IIN)
10 Freeze & Clear – Copy to freeze buffer and reset objects, no status reply
no Acknowledgement
13 Cold Start Initiate desired reset, reply with time till available
14 Warm Start Initiate partial reset, reply with time till available
20 Enable Unsolicited Messages Enable spontaneous reporting of the specified objects
21 Disable Unsolicited Messages Disable spontaneous reporting of the specified objects
22 Assign Class Assign objects to a particular class
23 Delay Measurement Calculate communication line round-trip message delay
129 Response A reply to a specific request message
130 Unsolicited Message Unsolicited response message
5 DATA POINTS LIST (OUTSTATIONS ONLY)

This part of the Device Profile shows, for each data type, a table defining the data points available in the device or a
description of how this information can be obtained if the database is configurable.
5.1 Definition of Binary Input Point List: ☐ Fixed, list shown in table below
List all addressable points. Points that do not exist (for ☒ Configurable (current list may be shown in table below)
example, because an option is not installed) shall be ☐ Other, explain_____________________
omitted from the table.
Note: the number of binary inputs present in the device,
and the maximum binary input index, are available
remotely using object Group 0 Variations 239 and 238.
Binary Input points list:
Point Name Event Class Name for State Name for State Description
Index Assigned when value is 0 when value is 1
(1, 2, 3 or none)
0 Single binary 1 Off On Any binary indication
example 1
example 2

DC8-037-2, Edition 11.2020
12.10 DNP3
Point Name Event Class Name for State Name for State Description
Index Assigned when value is 0 when value is 1
(1, 2, 3 or none)
example 3
: Add more rows
: as necessary
5.2 Definition of Double-bit Input Point List: ☐ Fixed, list shown in table below
Note: the number of double-bit inputs present in the
device, and the maximum double-bit input index, are avail-
able remotely using object Group 0 Variations 236 and 235.
Double-bit Input points list:
Poi Name Event Class Name for Name for Name for Name for Description
nt Assigned State when State when State when State when
Ind (1, 2, 3 or value is 0 value is 1 value is 2 value is 3
ex none) (Inter- (Off) (On) (Indetermi-
mediate) nate)
0 Double 1 Intermediate Off On Indeterminate Circuit Breaker
binary
input
example 1
1 Double 1 Intermediate Open Closed Indeterminate Disconnector
binary
input
example 2
2 Double 1 Intermediate Open Closed Indeterminate Disconnector
binary
input
example 3
: Add more
: rows as
necessary
5.3 Definition of Binary Output Status/Control relay ☐ Fixed, list shown in table below
output block (CROB) Point List: ☒ Configurable (current list may be shown in table below)
List all addressable points. Points that do not exist (for ☐ Other, explain_____________________
example, because an option is not installed) shall be
Note: the number of binary outputs present in the device,
and the maximum binary output index, are available
Binary Output Status and CROB points list:

DC8-037-2, Edition 11.2020
12.10 DNP3
Event Class
Supported Control Operations Assigned

(1, 2, 3 or
none)
Cancel Currently Running Operation

Name for Name for
State State
Name Description
when when
Direct Operate – No Ack
value is 0 value is 1
Select/Operate
Direct Operate
Point Index
Command
Count > 1
Latch Off
Pulse Off
Latch On
Pulse On
Change
Close
Trip
Binary
0 Command X X X X Off On None None Any binary command
example 1
Binary
1 Command X X X None None Any binary command
example 2
Binary
2 Command X X X Off On None None Any binary command
example 3
Binary
2 X X X None None Any binary command
Command
example 4
Add more
:
rows as
:
necessary
5.4 Definition of Counter/Frozen Counter Point List: ☐ Fixed, list shown in table below
Note: the number of counters present in the device, and
the maximum counter index, are available remotely using
object Group 0 Variations 229 and 228.
Counter / Frozen Counter points list:
Name Event Class Frozen Counter Event Class Description

Exists Assigned to
Point Index
Assigned
(1, 2, 3 or none) (Yes or No) Frozen Counter
Events
(1, 2, 3 or none)
0 Binary Counter 3 Yes 3 Any binary counter
example 1
example 2

DC8-037-2, Edition 11.2020
12.10 DNP3
Name Event Class Frozen Counter Event Class Description

Exists Assigned to
Point Index
Assigned
(1, 2, 3 or none) (Yes or No) Frozen Counter
Events
(1, 2, 3 or none)
example 3
: Add more rows
: as necessary
5.5 Definition of Analog Input Point List: ☐ Fixed, list shown in table below
Note: the number of analog inputs present in the device,
and the maximum analog input index, are available
Name Event Class Transmitted Scaling Dead- Units Resolution Description

Value band
Point Index
Assigned Min Max Multi- Offset

(1, 2, 3 or plier
none)
0 Analog 2 -32768 32767 1 0 150 Any analog
Input input
example 1
1 Analog 2 0 10000 1 0 60 Any analog
Input input
example 2
2 Analog 2 -1 1 1 0 0,02 Any analog
Input input
example 3
: Add more
: rows as
necessary
5.6 Definition of Analog Output Status/Analog Output ☐ Fixed, list shown in table below
Block Point List: ☒ Configurable (current list may be shown in table below)
Note: the number of analog outputs present in the device,
and the maximum analog output index, are available
Analog Output points list:

DC8-037-2, Edition 11.2020
12.10 DNP3
Supported Transmitted Scaling Event Class

Control Value
Operations Assigned
(1, 2, 3 or
none)
Direct Operate – No Ack

Name Units Resolution Description
Multiplier
Offset
Select/Operate
Direct Operate
Max
Min
Point Index
Command
Change
Analog
0 Output X -32768 32767 1 0 None None Any analog output
example 1
Analog
1 Output X 0 100 1 0 None None Any analog output
example 2
Analog
2 Output X -5 5 1 0 None None Any analog output
example 3
Add more
:
rows as
:
necessary
5.7 Definition of File Names that may be read or written: ☐ Fixed, list shown in table below
☐ Configurable (current list may be shown in table below)
☐ Other, explain_____________________
Sequential Files list:
File Name Event Class Authentication Required Description

Assigned for:
(1, 2, 3 or none)
Read Write Delete
Add more rows

as necessary
5.8 Definition of Octet String and Extended Octet String ☐ Fixed, list shown in table below
Point List: ☐ Configurable (current list may be shown in table below)
Octet String and Extended Octet String points list:
Point Name Event Class Group Number Description

Index Assigned used to trans-
(1, 2, 3 or none) port
the object
0
1

DC8-037-2, Edition 11.2020
12.10 DNP3
Point Name Event Class Group Number Description

Index Assigned used to trans-
(1, 2, 3 or none) port
the object
2
: Add more rows
: as necessary
5.9 Definition of Virtual Terminal Port Numbers: ☐ Fixed, list shown in table below
List all addressable points. Points that do not exist (for ☐ Configurable (current list may be shown in table below)
Ports list:
Virtual Name Event Class Description

Port Assigned
Numb (1, 2, 3 or none)
er
(Point
Index)
0
1
2
: Add more rows as
: necessary
5.10 Definition of Data Set Prototypes: ☐ Fixed, list shown in table below
List of all data set prototypes. The following table is ☐ Configurable, list methods: (a list of currently defined
repeated for each Data Set Prototype defined. Data Set Prototypes may be shown in tables below)
Note: the numbers of data set prototypes known to the ☐ Other, explain_____________________
device are available remotely using the protocol object
Group 0 Variations 212 and 213.
Prototype Description:
Descriptor Code Data Type Code Ancillary Value:

(check one) (check one)
ID = Identifier number
UUID = UUID value
Maximum Data length
Element
NSPC = Prototype namespace
Description
Element Number
NAME = Prototype name

DAEL = Data element name
CTLS = Control status name

NAME
NONE
UNCD
NSPC
OSTR
DAEL
UUID
VSTR
TIME
CTLV
BSTR
UINT
CTLS
FLT
INT
CTLV = Control value name

ID
Mandatory DNP
0 X X
identifier
1 UUID assigned to
X X
prototype

DC8-037-2, Edition 11.2020
12.10 DNP3
2
: Add more rows
: as necessary
5.11 Definition of Data Set Descriptors: ☐ Fixed, Data Set Descriptors are shown in table below
List of all data set descriptors. The following table is ☐ Configurable (current list may be shown in table below)
repeated for each Data Set Descriptor defined. Note: the ☐ Other, explain_____________________
numbers of data sets known to the device are available
remotely using the protocol object Group 0 Variations 214
and 215.
Data Set Description:
5.11.1 Data Set Properties: ☐ Readable

☐ Writable
☐ Outstation maintains a static data set
☐ Outstation generates a data set event
☐ Data set defined by master
5.11.2 Event Class Assigned: ☐ Class 1
☐ Class 2
☐ Class 3
5.11.3 Static Data Set included in Class 0 response: ☐ Always
☐ Never
☐ Only if assigned to a class
Descriptor Code Data Type Code Ancillary Value:

(check one) (check one)
ID = Identifier number
NAME = Data Set name
Maximum Data length
Element
DAEL = Data element name
Element Number
Description
CTLS = Control status name
CTLV = Control value name

NAME
NONE
UNCD
OSTR
DAEL
VSTR
TIME
CTLV
BSTR
PTYP
UINT
CTLS
FLT
INT
PTYP = UUID and (optional) instance name

ID
Mandatory DNP
0 X X
identifier
1
Add more rows
:
as necessary
5.12 Data Set Descriptor – Point Index Attributes

The following table is optional and correlates data set elements to point indexes of standard DNP3 Data Objects. The
element number below refers to the position in the present value (object 87) or event (object 88) data set and will not
match the element number in the data set descriptor or data set prototype tables above.
Duplicate this table for each Data Set Descriptor defined
Data Set Description:

DC8-037-2, Edition 11.2020
12.10 DNP3
Element DNP3 Group Number Point Index

Number
0
1
2
: Add more rows as necessary
:
12.10.9 Web Server
A web server for internal diagnostic and statistical information is integrated in the protocol firmware. The web
server itself is implemented on the basic system element - the PRE-specific websites are only provided by the
protocol element.
System Firmware Designation PRE specific Web Pages
CP-8000 DNPMT0 DNP3 Master serial ✓
CP-8021 DNPST0 DNP3 Slave serial ✓
CP-8022 DNPiT2 DNP3 TCP/IP Master ✓
DNPiT1 DNP3 TCP/IP Slave ✓
The PRE-specific websites can be displayed with a standard web browser.

For the access to the web server the communication protocol HTTP (Hyper Text Transfer Protocol) is used with
the port number 80 or the communication protocol HTTPS (Hyper Text Transfer Protocol over SSL/TLS) is used
with the port number 443.
With the SICAM Device Manager, the integrated web server is called up directly via links under the Protocol
details.
With the SICAM TOOLBOX II or a web browser, the integrated web server is addressed by specifying the IP
address of the automation unit.
With the CP-8000/CP-802x, the web server for the protocol elements on PRE0 to PRE3 can be reached as
follows (example):
NOTE
i 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 [PRE] | Advanced parameters | Webserver | HTTP-
Webserver .

DC8-037-2, Edition 11.2020
12.10 DNP3
12.10.9.1 Web Server

Supported PRE specific web pages:
PRE specific web page for DNPST0, DNPiT1 DNPMT0, DNPiT2
• Overview ✓ ✓
– Routing Receive ✓ ✓
• Developer Information ✓ ✓
– Freespace ✓ ✓
– Diagnosis (IDH) – –
– Diagnosis (IDZ) – –
– Diagnosis (IDE) – –
NOTE
An updating of the web page displayed in the web browser can be performed e.g. by means of a refresh of
the web browser.
The web pages will be displayed only in English language!
12.10.9.2 Overview

Field Note
Firmware Name of firmware
Revision Revision of firmwareHardware
Date and time actual date + time of firmware
ZBG Supplementary system element number “SSE” (internal)
Redundancy actual date + time of firmware
• Firmware active = Firmware “active“

Firmware status State of the firmware:
• Ready = Firmware ready for operation

DC8-037-2, Edition 11.2020
12.10 DNP3
On the web page Connections Information about the status of the connection to the DNP3 central station is
displayed.
Field Note
Connection DNP3 link layer OK = DNP3 Link Layer connected
NOK = DNP3 Link Layer not connected
DNP3 master station (destina- DNP3 destination address
tion)
DNP3 slave station (source) DNP3 source address
Events disabled DNP3 events “Disabled“

DC8-037-2, Edition 11.2020
12.10 DNP3
On the web page Routing Transmit information is displayed in the send direction for each parameterized
DNP3 data point.
Field Note
Count Number of data points in transmit direction "total sum"
Count indications Number of data points in transmit direction "binary information sum"
Count measurements Number of data points in transmit direction "measured value sum"
Count running counters Number of data points in transmit direction "integrated totals sum"
Count errors Sum of faulty data points in transmission direction

DC8-037-2, Edition 11.2020
12.10 DNP3
Field Note
Error Error number
• ERR = 0 ... No error

• ERR = 1 ... Typ identification DR-record wrong
• ERR = 2 ... wrong subadress
• ERR = 3 ... wrong DR-type in transmit direction
• ERR = 5 ... not supported type identification
• ERR = 6 ... not supported info art
• ERR = 7 ... info art wrong
• ERR = 8 ... wrong digital conversion
• ERR = 15 ... double Ax-adress
• ERR = 16 … double foreign-address
• ERR = 17 … Linear adaption parameter wrong
• ERR = 18 … foreign-address overlap (float, 31 bit value)
• ERR = 19 … threshold is par. but no linear adaption
• ERR = 23 ... no link address, wrong link address
• ERR = 100 … Process image no. larger than measured value no.
• ERR = 101 … x0,x100 equal parameterized
• ERR = 102 … x0 must be smaller than x100
• ERR = 103 … y0,y100 equal parameterized
• ERR = 104 … Unconditional treshold larger than 103 %
• ERR = 105 … Additional treshold larger than 1000 %
• ERR = 106 … Integrated total: count group wrong
• ERR = 107 ... Integrated total: transmit event wrong
• ERR = 108 ... Linear adaption parameter wrong
• ERR = 109 ... prozess image no. larger than integrated total no.
TI IEC 60870-5-101/104 Type identification (SICAM A8000 internal)
CASDU1, CASDU2 IOA1, IOA2, SICAM A8000 internal IEC 60870-5-101/104 Address of the data point
IOA3
DNP3 data index DNP3 address of the data point
Object variation DNP3 data point type
Event class DNP3 event class of the data point
Last time sent Last transmission time of specific data point
Last COT sent Last transmitted cause of transmission
Last dp qual sent Last sent quality descriptor for the value
Last value sent Last value sent

DC8-037-2, Edition 11.2020
12.10 DNP3
Routing Transmit (Filter not used)
Routing Transmit - with text filter

Note: The filter affects all fields of the table.
On the web page Routing Receive information is displayed in the receive direction for each parameterized
DNP3 data point.

DC8-037-2, Edition 11.2020
12.10 DNP3
Field Note
Count Number of data points in receive direction "total sum"
Count commands Number of data points in receive direction "command sum"
Count setpoints Number of data points in receive direction "setpoint value sum"
Count errors Sum of faulty data points in receive direction
Error Error number
• ERR = 0 ... No error

• ERR = 1 ... Typ identification DR-record wrong
• ERR = 2 ... wrong subadress
• ERR = 4 ... wrong DR-type in receive direction
• ERR = 5 ... not supported type identification
• ERR = 11 ... commandtype wrong
• ERR = 15 ... double Ax-adress
• ERR = 16 … double foreign-address
• ERR = 18 ... foreign-address overlap (float, 31 bit value)
• ERR = 19 … threshold is par. but no linear adaption
• ERR = 23 ... no link address, wrong link address
• ERR = 100 ... Process image no. larger than measured value no.
• ERR = 101 … x0,x100 equal parameterized
• ERR = 102 ... x0 must be smaller than x100
• ERR = 103 ... y0,y100 equal parameterized
• ERR = 104 ... Unconditional treshold larger than 103 %
• ERR = 105 ... Additional treshold larger than 1000 %
• ERR = 106 ... Integrated total: count group wrong
• ERR = 107 ... Integrated total: transmit event wrong
• ERR = 109 ... prozess image no. larger than integrated total no.
CASDU1, CASDU2 IOA1, IOA2, SICAM A8000 internal IEC 60870-5-101/104 Address of the data point
IOA3
DNP3 data index DNP3 address of the data point
Object variation DNP3 data point type
last time rec Last reception time for this data point
last COT rec Last received cause of transmission
last dp qual rec Last received quality descriptor for the value
last value rec Last value received

DC8-037-2, Edition 11.2020
12.10 DNP3
Routing Receive (Filter not used)
Routing Receive - with text filter

12.10.9.6 Developer Information - Freespace
On the web page Developer Information - Freespace internal information "Freespace DNP3-Stack" of the
firmware is displayed.
These informations are helpful for the developer in case of problems.

DC8-037-2, Edition 11.2020
12.10 DNP3
Field Note
Count malloc Internal informations
Count free Internal informations
Heap complete (Bytes) Internal informations
Heap internal (Bytes) Internal informations
Heap DNP3 protocol stack Internal informations
(Bytes)
On the web page Developer Information – Dataflow Test the telegrams transmitted on the internal interface
from PRE ↔ BSE are displayed.
The last 200 messages transmitted from PRE <-> BSE will be displayed..
Field Note
No. Message number
Dir Direction (Dir = Direction)

IOA1, IOA2, IOA3
COT IEC 60870-5-101/104 Cause of transmission (SICAM A8000 internal)
(COT = Cause Of Transmission)
Origin IEC 60870-5-101/104 Originator address (SICAM A8000 internal)
(origin = Originator)
Data IEC 60870-5-101/104 State of data point (SICAM A8000 internal)

DC8-037-2, Edition 11.2020
12.10 DNP3
Field Note
Quality IEC 60870-5-101/104 Quality descriptor of the data point
Time Last received quality descriptor for the value (DNP3)
“Monitoring Filter“ for Logging

With filter enabled, only messages will be logged which are selected by filter. If no filter is selected all
messages will be logged.
The filter will be activated by set filter.
The filters will be cleared with Clear all monitoring filters.
“Suppress Filter“ for Logging

With filter enabled, messages selected by filter will be suppressed from logging. If no filter is selected all
The filters will be cleared with Clear all suppress filters.

DC8-037-2, Edition 11.2020
12.10 DNP3
With web page Developer Information - Diagnosis (IDR) internal diagnosis information of protocol elements
(PRE) will be displayed.
Deletion of the IDR-diagnostic information on PRE (“PRE clear diagnosis“)

The IDR diagnostic information on the PRE can be deleted under "PRE clear diagnostics" with Clear.
PRE general Information
Field Note
HW-TYP Hardware type of PRE firmware
FW-TYP Firmware type of PRE firmware
Rev Revision of PRE firmware
FWName Name of firmware
Build Generation date of the firmware revision

DC8-037-2, Edition 11.2020
12.10 DNP3
State of the PRE-Firmware (“PRE state“)
Field Note
PRE state State of the PRE firmware
• Ready
PRE diagnosis information (IDR)
Field Note
Name Diagnosis text


DC8-037-2, Edition 11.2020
12.11 SINAUT ST1
12.11 SINAUT ST1
The SINAUT ST1 (TIM11) slave protocol is used to connect SICAM A8000 automation units to telecontrol
central stations, front ends and control systems in multi-point traffic.
Multi-point traffic describes a serial communication protocol with which a central station is connected with
one or multiple substations over a communication connection in a linear or star configuration. The data traffic
is controlled by the central station.
The ST1ST0 protocol element enables a substation to communicate with a central station, and with up to 254
substations on a common line. Each substation is assigned an unambiguous station number in the range of 0
to 254. Station number 0 is used to address all stations at the same time (“Broadcast”). No response (response
message) is transmitted from the substations to the central station for this type of addressing.
Either data messages or station interrogation messages are transmitted by the central station. Data from the
substation to the central station can only be transmitted as a response to a station interrogation.
Configuration
[ST1Sx0_config, 1, en_US]
An unbalanced transmission procedure is used in multi-point traffic. That means that the central station
initiates all message transfers as a primary station while the substations are only allowed to transfer when
they are called, as they are secondary stations.
Multi-point traffic only requires a "half duplex" transmission medium and can be used in a star or linear struc-
ture.
12.11.2 Functions
Master station communicating with one or several substations.
• Unbalanced multi-point traffic according to Siemens SINAUT ST1 (TIM 11)

ST1ST0 is the substation
– Recording events (transferring data ready for sending)
– Metered value transmission
• Physical interface
– RS-232 - unbalanced interface according to V.24/V.28
– RS-485 - balanced interface according to V.11

DC8-037-2, Edition 11.2020
12.11 SINAUT ST1
• Supported functionality as per Siemens SINAUT ST1 (TIM11)protocol definitions (with constraints)
• Optimized Parameters for Selected Transmission Facilities
• Telegram implementation IEC 60870-5-101 ⇔ Siemens SINAUT ST1 (TIM11)
The operating mode of the interface is determined by the protocol element parameters and optional equip-
ment.
optional DCE
Unbalanced interchange circuit (V.24/V.28) X2 RXD, TXD, CTS310, RTS, DCD, DTR,
Balanced interface (V.11) RS-485 (2-wire)/ RS-422 X3 TXD+/RXD+, TXD-/RXD- (2-wire)
Balanced interface (V.11) RS-485 (2-wire)/ RS-422 X2 → CM-0829 RXD, TXD, CTS, RTS, DCD, DTR,
(4-wire) asynchronous (CM-0819311) DSR/VCC, GND (for CM-08x9)
Optical interface (multimode fiber optic) ring X2 → CM-0821 RXD, TXD, CTS, RTS, DCD, DTR,
DSR/VCC, GND (for CM-0821)
Unbalanced interchange circuit (V.24/V.28) X6312 RXD, TXD, CTS, RTS, DCD, DTR,
RS-232 asynchronous DSR, GND
NOTE
i For details on how to implement various operating modes, see manual SICAM RTUs platforms – Config-
uring automation units and automation networks.
System System Element Protocol Element Remarks

SICAM A8000 CP-8000/CPC80 ST1ST0
CP-802x/CPC80
310 cannot be used (reserved for SICAM TOOLBOX II)

311 doesn’t support RS-422
312 only CP-8022 (switchable operating mode via parameter)

DC8-037-2, Edition 11.2020
12.11 SINAUT ST1

SICAM AK 3 CP-2016/CPCX26 SM-2551/ST1MA0
CP-2019/PCCX26 SM-0551/ST1MA0
Legacy systems CP-20xx SM-2551/ST1MA0 in acc. with Siemens
(SICAM AK CP-50xx SM-0551/ST1MA0 SINAUT ST1 (TIM11)
SICAM TM CP-60xx SM-2541/ST1M00
SICAM BC)
Third-party system - - in acc. with Siemens
SINAUT ST1 (TIM11)
12.11.5 Protocol Description
Substation addresses • 0 to 254

• 0 = BROADCAST
Physical interface • RS-232
• RS-485 (with CM-0829), 2-wire or 4-wire
Supported baud rates 50, 75, 100, 110, 134.5, 150, 200, 300, 600, 1050, 1200, 1800, 2000, 2400,
4800, 9600, 19200
Byte frame • 8E1
SIEMENS SINAUT ST1 Data communication
protocol
• Master - Slave (request - response)
• Half duplex
Telegram protection Parity + checksum
Supported SINAUT ST1 • Pulse command
message formats in
receive direction SICAM
• Setpoints
A8000 ← SINAUT ST1 • Organizational messages

(command or control – GI request (ORG = 08)
direction)
– Time synchronization (ORG = 10)
Supported SINAUT ST1 • Binary information (16-bit, 32-bit)
message formats in
transmit direction SICAM
• Measured values (raw values, fixed point format)
A8000 → SINAUT ST1 • Integrated totals (28-bit)

(signaling or monitoring
direction)
Supported IEC • <TI:=45> ... Single command
60870-5-101/104messag
e formats in receive direc-
• <TI:=46> ... Double command
tion SICAM A8000 ← • <TI:=47> ... Regulating step command

SINAUT ST1 (command or • <TI:=48> … Setpoint adjusting command, normalized value
control direction)
• <TI:=49> ... Setpoint adjusting command, scaled value
• <TI=50> … Setpoint adjusting command, short floating-point number

DC8-037-2, Edition 11.2020
12.11 SINAUT ST1
supported IEC • <TI:=30> ... Single-point information with time tag CP56Time2a
60870-5-101/104
message format in
• <TI:=31> ... Double-point information with time tag CP56Time2a
transmit direction SICAM • <TI:=34> ... Measured value, normalized value with time tag CP56Time2a
A8000 → SINAUT ST1 (15-bit + sign)
(signaling or monitoring • <TI:=35> … Measured value, scaled value with time tag CP56Time2a a (15-
direction) bit + sign)
• <TI:=36> ... Measured value, short floating-point number with time tag
CP56Time2a
• <TI:=37> … Integrated totals with time tag CP56Time2a (31-bit + sign with
sequence number)
Redundancy –
Parameterization • System-technical parameters with SICAM TOOLBOX II
• Process-technical parameters with SICAM TOOLBOX II - parameterizable
address conversion in transmit and receive direction with OPM II
Restrictions
• No GI completeness check
• No emulation for confirmation / termination according to IEC 60870-5-101
• No redundancy functions
There is a wide variety of organizational messages in SINAUT ST1 that are used for monitoring the system as
well as for additional system concepts (general interrogation, diagnostics, synchronization). The organiza-
tional messages are only supported subject to certain conditions!
NOTE
i As a third-party adaptation system, this protocol element only implements part of the functionality and the
data formats of the third-party interface. Therefore, you need to check to what extent the real require-
ments match the functionality that has been implemented here and to what extent additional expansions
or adaptations are required for a specific application.
12.11.5.2 PCMBA Modulation Method

The data is pulse-code modulated in groups of 7 to 8 bit and transmitted asynchronously. A USART building
block in asynchronous mode provides each byte with a byte frame in the process.
1 Start bit
8 Data bits
1 Parity bit (even parity)
1 Stop bit
The byte frame can be parameterized (system parameter).

byte.

DC8-037-2, Edition 11.2020
12.11 SINAUT ST1
Byte frame description
[7-8-Bit_Information, 1, en_US]
Figure 12-12 SINAUT ST1 Byte Frame
12.11.5.3 Interface Lines Used

The following V.24 interface lines are used:
TxD <103> Transmit data
RxD <104> Receive data
GND <102> Signal ground
The following V.24 interface signals can be used as an option:

RTS <105> Used to switch on the transmit signal level of the transmission facility
DCD <109> Used to detect the receive signal level from the transmission facility
12.11.5.4 Optimized Parameters for Selected Transmission Facilities

The protocol element supports selected transmission facilities – for which the parameters are fixed – and the
transmission facilities are selected using the parameter Common settings | interface modem. Certain
parameters can be customized by selecting freely definable transmission facility.
The physical interface must also be selected with the parameter Common settings | Interface
In most cases transmission facilities support only particular baud rates or combinations of baud rates in send/
receive direction – these must be taken from the descriptions for the transmission facility. The transmission
rate (baud rate) is to be set for transmit/receive direction together with the parameter Common settings |
baud rate .
predefined or if modified parameters are to be used for predefined transmission facilities. To ensure that you
can select a freely definable transmission facility, the parameter Common settings | interface modem
must be set to freely definable
Only then are all supported parameters displayed and can be parameterized with the required values (refer to
table with default parameters for transmission facilities).

DC8-037-2, Edition 11.2020
12.11 SINAUT ST1
The following parameters can be set individually for the adaptation to various modems or time requirements
of external systems:
• Common settings | free definable interface modem | DCD handling
• Common settings | free definable interface modem | Pause time (tp),
• Common settings | free definable interface modem | Set up time (tv),
• Common settings | free definable interface modem | Run out time (tn),
• Common settings | free definable interface modem | Bounce suppression time

(tbounce)
• Common settings | free definable interface modem | Disable time (tdis),
• Common settings | free definable interface modem | Stability monitoring time

(tstab)
• Common settings | free definable interface modem | Continuous level moni-

toring time (tcl)
• Common settings | free definable interface modem | Transmission delay if

continous level (tcldly)
• Common settings | free definable interface modem | X2: DTR/VCC pin as output
for
How the individual time settings become effective for data transmission can be seen on the following page in
the timing diagram.
In addition, the following parameters are available for the adaptation of the protocol to the transmission
medium used or to the time behavior of the connected remote station:
• Advanced parameters | Monitoring times | Call-up monitoring time

When the station call-up monitoring time elapses (substation is no longer called up by the central
station), then an interface failure is signaled.
• Advanced parameters | Monitoring times | Idle monitoring time

After transmission disturbances or message interruption the idle state is monitored. The receiver is
synchronized again once the monitoring time elapses. Synchronization can be carried out again more
quickly by using the DCD input.
• Advanced parameters | Monitoring times | Character monitoring time

Message gap monitoring maximum pause between successive bytes of a message. Idle monitoring time
is started after detection of message interruption.
The character monitoring time is used for the message interruption monitoring and message resynchroniza-
tion in receive direction. A message interruption is identified if the time between 2 bytes of a message is
greater than the set character monitoring time. In the event of a message interruption the on-going receive
handling is canceled and the message is discarded. After a message interruption has been identified a new
message is only accepted on the line in receive direction after an idle time.
The protocol element – insofar as the transmission facility (VFT channel) provides this signal on the receive
side – can evaluate the DCD interface signal and for example, utilize it for monitoring functions.

DC8-037-2, Edition 11.2020
12.11 SINAUT ST1
Default parameters for transmission facilities with ST1ST0
[sc_transmission_facilities_ST1ST0, 2, en_US]
Legend:
RTS ↑↓ = RTS is scanned for each message to control the modem's level scan (ON/OFF)
tp Pause time (tp) parameter
tv Setup time (tv) parameter
tn Run out time (tn) parameter
tdis Disable time (tdis) parameter
DCD DCD handling parameter
tbs Bounce suppression time (tbounce) parameter
tstab Parameter Stability monitoring time (tstab)
tduration Continuous level monitoring time (tduration) parameter
tdelay Transmission delay if continous level (tdelay) parameter
V Parameter X2: DTR/VCC pin as an output for a power supply for external transmis-
sion facilities

DC8-037-2, Edition 11.2020
12.11 SINAUT ST1

DC8-037-2, Edition 11.2020
12.11 SINAUT ST1
12.11.6 Communication according to SINAUT ST1

The data is transmitted from the substations to the central station via station selective station interrogations
(interrogation procedure, polling), which are controlled by the central station, this means that data that has
changed is stored in the substation and transmitted to the central station if this substation is interrogated.
The interrogation procedure of the central station ensures that substations are interrogated on a sequential
basis. Substations may only transmit when they are called up.
In every substation, a station-selective address must be set with the parameter Common settings | Own
station number. This address must be unambiguous for each multi-point traffic line.
12.11.6.2 Acknowledgement Procedure

Received messages are acknowledged with single characters (that is, E5H) if there is no user data to be sent,
or using a long message if there is user data to be sent.
The protocol element for the SINAUT ST1 substation in the SICAM A8000 acknowledges or responds to each
command message or call-up message that is received without error.
12.11.6.3 Failure Monitoring in the Substation

The interface is monitored in the substation by monitoring for cyclic telegram reception using station interrog-
ation or station-selective data messages.
The monitoring time is to be set in the substation with the parameter advanced parameters | Moni-
toring times | call monitoring time. The monitoring timeout is normally only retriggered in the
substation with station-selective call messages or station-selective data messages.
The monitoring time in the substation must be set sufficiently high, so that this does not inadvertently elapse
when transmitting large quantities of data from other substation (for example, during general interrogation).
If the interface fails, data to be transmitted is stored in the data storage system on the basic system element
(BSE) of the substation until it is deleted by the dwell time monitoring or can be transmitted to the central
station.

The SINAUT ST1 protocol does not use station initialization.
12.11.6.5 Acquisition of Events (Transferring Data Ready for Sending)

Substation data that is ready to be transmitted is stored in the substation until transmission takes place.
Process image (on the protocol element)

The protocol element manages an internal process image to form the blocked SINAUT ST1 message formats
from the internal SICAM A8000 IEC message formats. The process image is initialized with the “0” value after
system startup; the F error bit (open circuit) is also set for measured values.
General interrogation is always responded to by the protocol element from the internal process image.
After the protocol element has started up, a start-up delay is used to update the process image (no call ups are
accepted from the central station during this time). The start-up delay duration is set using the parameter
advanced parameters | advanced time settings | Startup delay.
Message from the Substation to the Central Station

Messages are transmitted from the substation to the central station when the station is interrogated. A quick-
check procedure for speeding up the transmission of data is not implemented.
12.11.6.6 General Interrogation (Substation Interrogation)

The general interrogation (substation interrogation) function is used to update the central station after the
internal station initialization or after the central station has detected a loss of information.
General interrogation is always responded to by the protocol element from the internal process image.

DC8-037-2, Edition 11.2020
12.11 SINAUT ST1
During general interrogation, the data is transmitted in the following ascending order as per SINAUT ST1
address:
• All binary information
• All measured values
• All integrated totals (optional)

You can set whether integrated totals should also be transmitted during general interrogation using the
parameter advanced parameters | GI counter value transfer.

The time synchronization command is transmitted by the central station cyclically (preset value: every 24
hours) or after a going communication fault.
The protocol element carries out an automatic time correction by the message transfer time (usually the trans-
mission rate and a fixed message length).
The protocol element can carry out an additional time correction to compensate the transfer times from trans-
mission facilities. The correction time must be set using the parameter advanced parameters |
advanced time settings | correction time for clock synchronization command
If the time synchronization of the substation is carried out via other interfaces, the time synchronization via
the interface with the SINAUT ST1 protocol can be deactivated using the parameter advanced parameters
| time synchronization.
The protocol element independently carries out a daylight saving time/standard time switchover in advance.
Message from the Central Station selectively to a Substation

sion in progress.

The counter interrogation command (organization telegram) is not supported by the substation protocol
element.
Integrated totals are provided by the substation at specific restore times (tariff times) for transmission. The
Integrated totals are then transmitted in the interrogation cycle.
Integrated totals can also be transmitted from the substation during general interrogations. You can set
whether integrated totals should also be transmitted during general interrogations using the parameter
advanced parameters | GI counter value transfer.
The functionality implemented in the SICAM A8000 system in relation to the integrated totals is documented
in the document Common Functions Peripheral Elements according to IEC 60870-5-101/104, chapter Inte-
grated Totals via Count Pulses.
12.11.7 Message Description
12.11.7.1 Message Structure

The interface transmission formats and rules are based on the international standard IEC 60870-5-1 Telecon-
trol Equipment and Systems TC 57 Part 5.1, Transmission Frame Formats, format class FT1.2 with deviations
that are specific to SINAUT ST1 in relation to using the F field (control field).

DC8-037-2, Edition 11.2020
12.11 SINAUT ST1
[FT1_2, 1, en_US]
The following message formats are used:

Message format IEC 60870-5-1 / FT1.2 Used for SINAUT ST1 (unbalanced)
messages with a fixed block length Messages for traffic management (station interroga-
tions)
Messages with a variable block length User data messages
Single character 1 Acknowledgment message (no control field informa-
tion)
Single character 2 Not used
The message formats can be distinguished by their different start characters, for instance.
Message format IEC 60870-5-1 / FT1.2 Start character / Message frame / Stop character
Messages with a fixed block length 10H xxH xxH CS 16H
Messages with a variable block length 68H LLH LLH 68H xxH xxH .......... CS 16H
Single character 1 E5H
Single character 2 A2H
Legend:
CS ..... Checksum (HEX)
xxH .... Data byte (HEX)
LLH .... Quantity (=length) of user data bytes (HEX)
Showing a byte (LSB shown right-aligned):
[sc_LSB_shown_right-aligned, 2, en_US]
D1 generally shows the least significant bit (LSB).
Representation of a byte “Bit sequence on the line”: (Example for single character 1)

DC8-037-2, Edition 11.2020
12.11 SINAUT ST1
[sc_Bit_sequence_on_the_line, 2, en_US]
Legend:
STA ...Start bit (is transmitted as the 1st bit on the line)
STP ... Stop bit
P ....... Parity bit (even)
All message formats (except for single characters) are protected against erroneous information and block shift
(synchronization errors) with the specified transmission rules and character definitions with d = 4.
Message Format with a Fixed Block Length

This dataset is used in the call-up direction as a call-up message to request data.
Formats with a fixed block length consist of a start character, a fixed L quantity of user data bytes, a checksum
and a stop character.
[sc_Formats_with_fixed_block_length, 2, en_US]
The number of bytes for the A field and the F field for the “format with fixed block length” is 2 byte (control
field and address field) for the transmission protocol according to SINAUT ST1 based on IEC60870-5-2.
A field: The A field contains the participant address (in the application, this is the SINAUT ST1
station number or communication address)
Range of values: 0 to 254
Station number 0 is used to call up all stations
Transmission rules for message formats with a fixed block length
R1 The idle state on the line corresponds to a 1 signal.

R2 Each USART character has a start bit (0 signal), 8 information bits, a parity bit (even) and a stop bit (1
signal)
R3 Idle states are not permitted between the USART characters of a message
R4 A minimum number of 33 bits in idle state are required between the formats (blocks) in the event of a
synchronization loss.
R5 The user data is monitored by a checksum. The checksum is the arithmetic sum without taking the
carryovers into account for all user data (no start or stop character).
R6 The receiver checks for each USART character: start bit, stop bit and parity bit (even parity).
Special checks in receive direction for variable block length message format:
• The specified start character at the start and the end of the header part (10H)
• The number of user data bytes received (2 USART characters)

DC8-037-2, Edition 11.2020
12.11 SINAUT ST1
• The checksum
• The stop character (16H)

Error processing:
After an error has been detected, the received data is discarded and the received data line is monitored for a
pause of at least 33 bit to re-synchronize the receiver.
Note for R4:
This time is generated by the transmitter, and always before transmitting the next message in normal opera-
tion after detecting that there is an acknowledgment missing.
Message Format with a Variable Block Length

This dataset is used to transmit several user data bytes. How it’s used does not depend on the data contents
and the transfer direction.
These formats consist of an initial start character, two of the same characters in which the L number of the
user data bytes is transmitted, and a second start character. User data L is usually in the range 0 to 255 (for
SINAUT ST1 protocol, L is used in the range 1 < = L < = 255).
[sc_Format_with_variable_Block_Length, 2, en_US]
The number of bytes for the A field and the F field for the “format with variable block length” is 2 byte for the
transmission protocol according to SINAUT ST1 based on IEC60870-5-2.
Transmission rules for message formats with a variable block length

The transmission rules R1 to R6 and error processing apply similarly as with the “message format with a fixed
block length”.
• The specified start character at the start and the end of the header part (68H xx xx 68H)
• The identity of the two length bytes (68H xx xx 68H)

The L field specifies the number (0 to 126) of user data bytes and thus determines the message length
• That the number of received characters is equal to L+6

DC8-037-2, Edition 11.2020
12.11 SINAUT ST1
• The checksum
Arithmetic sum without taking the carryovers into account for all user data bytes (= modulo 256 addi-
tion)
• The stop character (16H)
Single Character (Short Message)

The single characters can be used as per the standard for special information to ensure efficient data commu-
nication control.
Single character-1: (E5H)
Single character-1 (E5H) is used for the SINAUT ST1 protocol (multi-point traffic) as follows:
• Slave ⇒ Master:
ACK acknowledgement message
[sc_single_sign_1, 2, en_US]
Single character-2: (A2H)

Single character-2 (A2H) is not used for the SINAUT ST1 protocol (multi-point traffic)!
[sc_single_sign_2, 2, en_US]
Transmission rules for single characters

The transmission rules R1 to R4 and R6 and error processing apply similarly as with the “message format with a
fixed block length”.
12.11.7.2 SINAUT ST1 Function Fields
Function Field (F Field)
[sc_function_field, 2, en_US]
Function field elements (F field)

RB … Direction bit RB = 0: Message from substation → central station (= response
direction)
RB = 1: Message from central station → substation (= call-up
direction)
AE … Address-field extension AE = 0: SINAUT ST1 without address-field extension = default
setting
AE = 1: SINAUT ST1 with address-field extension (address-field
extension by “object” and “index”)
AE = 2: Not supported!
AE = 3: Not supported!

DC8-037-2, Edition 11.2020
12.11 SINAUT ST1
Function field elements (F field)

FA … Function selection FA = 0: Call-up control code applies to the TIM
FA = 1: Call-up control code applies to the base device
Is only used in data messages, when call-up message is FA = 0
KC … Check code Call-up direction: (central station → substation)
KC = 0: Normal message
KC = 1: Message after call-up
Response direction: (substation → central station)

KC = 0: nth message
KC = 1: last message
TZ … Message counter TZ = 0: Start-up identifier
TZ = 1 to 7: 1st to 7th message
Message Type (TA), Additional Identifier
[sc_Message-type_Additional-identifier, 2, en_US]
Field elements for TA and additional identifier

TA … Message type TA = 0: Organizational message (for example, GI request)
TA = 0: Free
TA = 2: Data message
TA = 3: Queried data message (not in control direction)
Message from central station → substation (= call-up direction)

ZK … Additional identifier for message For organizational messages (TA = 0) the individual messages
type are differentiated based on the additional identifier.
TA = 0, ZK = 8: General interrogation
TA = 0, ZK = 10: Time synchronization
The additional identifier is used in different ways, depending on the address-field extension (AE).
Additional identifier for data messages (TA = 2 or 3) in the event of AE = 0
[sc_Additional-identifier_AE0, 2, en_US]

S … Disabled S = 0: Message enabled
S = 1: Message disabled
Z … Time tag Z = 0: Message without time tag
Z = 1: Message with time tag
P P = 1: Message must be permanently (cyclically) transmitted
U U = 1: Message is spontaneously transmitted, without being
subject to certain conditions

DC8-037-2, Edition 11.2020
12.11 SINAUT ST1

B B = 1: Message is spontaneously transmitted subject to certain
conditions
PR … Message transmission principle PR = 0: Image storage principle
PR = 1: Transmit buffer principle
Additional identifier for data messages in the event of AE = 1
[sc_Additional-identifier_AE1, 2, en_US]

S … Enabled/disabled S = 0: Message enabled
S = 1: Message disabled
Z … Time tag Z = 0: Message without time tag
Z = 1: Message with time tag
PACK … Number of user data bits of each Number of bits = 4 x 2PACK
object PACK = 0: 4 bit user data for each object
PACK = 1: 8 bit user data for each object
PACK is not used in the control direction
Example:
If the substation transmits a binary information message with 32
bit (= 4 byte) and PACK = 0 (4 bit/object), then the central station
generates 8 objects from the received message with ascending
object numbers.
PR … Message transmission principle PR = 0: Image storage principle
PR = 1: Transmit buffer principle
SINAUT ST1 Message Address
[sc_ST1_Message-address, 2, en_US]
ST1 message address

ST1 message address Possible: 0 to 255 (used: 2 to 250)
The message address is always unambiguously assigned in
standard mode (no address-field extension).
The following are addressed for each message address:
16 or 32-bit binary information
2 or 4 analog values
1 integrated total
1 setpoint
Group of 8 commands

DC8-037-2, Edition 11.2020
12.11 SINAUT ST1
SINAUT ST1 Object / Index (only if Address-field Extension AE=1)

The “object number” and the “index” are used to extend the address field. The object number is always only
parameterized as a “start object” in the substation. The number of objects is then derived in the central station
using PACK.
“Object” and “Index” are always only parameterized for each ST1 message (for example, 32-bit binary informa-
tion, 4 analog values).
The index is used to distinguish between types of data.
Index: 2 … Commands
3 … Binary information
4 … Measured values
5 … Integrated totals
6 … Setpoint values
SINAUT ST1 Time Tag

If the Z time identifier has been set in the additional identifier, a time tag that is 8 bytes in length follows after
the user data information.
SINAUT ST1 time tag:
[sc_ST1_Time-tag, 2, en_US]
Time status byte allocation

Bit 0: 1 = Clock unclear, TIM time has not been set yet after a start-up
Bit 1: 1 = Clock is set by the AG as per control statement
Bit 2: 1 = Clock set via ORG message
Bit 3: 1 = Clock synchronization has not occurred in the last 24 hours
Bit 4: 0 = Standard time
1 = Daylight saving time
Bit 5: Not currently used
Bit 6: 1 = SYN display; the bit changes the value for each STEL process
Bit 7: 1 = STEL display; the bit changes the value for each STEL process

DC8-037-2, Edition 11.2020
12.11 SINAUT ST1
Data in transmit direction is transferred bythe basic system element to the protocol element in SICAM A8000
internal IEC 60870-5-101-/104 format. The data is converted by the protocol element to the SIEMENS SINAUT
ST1 (TIM11) message format on the line and transmitted according to the protocol’s transmission procedure.
Data in receive direction is converted by the protocol element from the message format using the transmis-
sion line to a SICAM A8000-internal IEC 60870-5-101/104 format and the data is transferred to the basic
system element.
Converting the SICAM A8000 message formats ↔ SIEMENS SINAUT ST1 data formats and converting the
address information is designated as message conversion.
The message conversion for IEC 60870-5-101/104 ↔ SIEMENS SINAUT ST1 is parameterized with the SICAM
TOOLBOX II, OPM II with the “SIP message address conversion”, or with SICAM WEB.
Master - Categories for SIP message address conversion

Data Direction Category
Command Receive Direction firmware / Rec_command
Setpoint value Receive Direction firmware / Rec_setpoint_value
Binary information Transmit Direction firmware / Trans_Fr
Measured value Transmit Direction firmware / Trans_Fr
Integrated total Transmit Direction firmware / Trans_Fr
The following parameters apply to all parameter categories:

Parameter
Lk_Reg Link region number
The data point is assigned to the automation unit with the selected region number.
Lk_Comp Link component number
The data point is assigned to the automation unit with the selected component
number.
Lk_BSE Link basic system element
The data point is assigned to the selected basic system element in the selected auto-
mation unit.
Lk_SSE Link supplementary system element
The data point is assigned to the selected supplementary system element in the
selected automation unit.
Lk_DS Link destination station
The data point is assigned to the selected destination station in the selected automa-
tion unit.
Lk_Cat Link category
Lk_Prep Link prepared
• Data point prepared: signal will not be loaded into destination system
• Data point activated: signal is activated and will be loaded upon conversion into
destination system

DC8-037-2, Edition 11.2020
12.11 SINAUT ST1
12.11.9 Message Conversion In Transmit Direction (SICAM A8000 → ST1)
Message conversion in transmit direction: IEC60870-5-101/104 → SINAUT ST1
IEC 60870-5-101/104 → SINAUT ST1

Type Designation TA ZK Designation
identifi-
cation
<TI:=30> Single-point information with time tag 2, 3 0 16-bit information without time
CP56Time2a 32-bit information without time
<TI:=30> Single-point information with time tag 2, 3 1 16-bit information with time
CP56Time2a 32-bit information with time
<TI:=31> Double-point information with time tag 2, 3 0 16-bit information without time
CP56Time2a 32-bit information without time
<TI:=31> Double-point information with time tag 2, 3 1 16-bit information with time
CP56Time2a 32-bit information with time
<TI:=34> Measured value, normalized value with 2, 3 0 Analog value 1 MV
time tag CP56Time2a (15 bit + sign) Analog value 2 MV
Analog value 4 MV
<TI:=35> Measured value, scaled value with time 2, 3 0 Analog value 1 MV
tag CP56Time2a (15 bit + sign) Analog value 2 MV
Analog value 4 MV
<TI:=36> Measured value, short floating point 2, 3 0 Analog value 1 MV
number with time tag CP56Time2a Analog value 2 MV
Analog value 4 MV
<TI:=37> Integrated total with time tag CP56Time2a 0 10 Counter value 1 CV
(31 bit + sign)
TA … SINAUT ST1 message type

ZK … SINAUT ST1 additional identifier
12.11.9.1 Binary information

Binary information transmission for SINAUT ST1:
• 16- or 32-bit for each SINAUT ST1 message
• Without time or with time
• Spontaneously or in the event of a general interrogation

ST1 message format for binary informations (AE = 0)
[sc_binary_information_AE0, 1, en_US]
TA = 2 … Spontaneous message

DC8-037-2, Edition 11.2020
12.11 SINAUT ST1
TA = 3 … Requested message (general interrogation)

ST1 message format for binary informations (AE = 1)
[sc_binary_information_AE1, 1, en_US]
TA = 3 … Requested message (general interrogation)
PACK … 0: 4-bit for each object → 8 objects for every 4 bits
1: 8-bit for each object → 4 objects for every 8 bits
2:16 bit for each object → 2 objects for every 16 bits
Address Conversion between SINAUT ST1 → SICAM A8000

The address and message conversion for binary information in transmit direction can be parameterized using
the SICAM TOOLBOX II, OPM II or for engineering via SICAM WEB with the transmit detailed routing parame-
ters.
Parameter category:
firmware /Trans_Fr

DC8-037-2, Edition 11.2020
12.11 SINAUT ST1
Parameter Meaning
CASDU1 5-stage freely parameterizable SICAM A8000 address
CASDU2 possible: 0 to 255
IOA1
IOA2
IOA3
TI Type identification
• Single-point information <TI:=30>

• Double-point information <TI:=31>
ST1_tel_no_(ST1Sxx) ST1 message number
2 to 255
ST1_object_(ST1Sxx) Used together with the ST1 index for address-field extension
0 to 255 (0 = no address-field extension)
ST1_index_(ST1Sxx) Used to distinguish between the various data types
ST1_data_index_(ST1Sxx) Bit position for binary information or value numbers for measured values
0 to 31
ST1_tel_type_(ST1Sxx) ST1 message type
• 16 bit information
• Analog value 1 MV
• Counter value 1 CV
Pack_(ST1Sxx) Bit count for each object
• 4
• 8
• 16
• Unused/automatic
Telegram with Transmit message with or without time tag
timetag_(ST1Sxx) yes/no
ST1_format_(ST1Sxx) ST1 data format
• Single-point information
• Double-point information I/O
• Double-point information O/I
• Measured value 12-bit, left-aligned
• Measured value 15-bit + sign
• Metered value + 28-bit binary
X_0% Value adaptation (must be left at a preset value = 0)
Y_0% Value adaptation (must be left at a preset value = 0)
Spontaneous message forwarding

This table describes the data point quality descriptor and the cause of transmission according to
IEC 60870-5-101/104.

DC8-037-2, Edition 11.2020
12.11 SINAUT ST1
Message elements
TI .. type identification <TI:=30> Single-point information with time tag CP56Time2a
<TI:=31> Double-point information with time tag CP56Time2a
CASDU, IOA .. message address Configurable
SPI .. single point information 0 .. OFF
1 .. ON
DPI .. double point information ON/OFF double-point information
OFF/ON double-point information
QDS .. quality descriptor
BL .. blocked Not supported
SB .. substituted Not supported
NT .. not topical Not supported
IV .. invalid Not supported
02 .. background scan Not supported
03 .. spontaneous When the information status or the quality code changes
05.. requested Not supported
11 .. return information, caused by a Not supported
remote command
12 .. return information, caused by a local Not supported
command
20 .. interrogated by station interrogation Upon receipt of a GI request
21 to 36 interrogated by group interroga- Not supported
tion 1 to 16
T .. Test Not supported
12.11.9.2 Measured Values (Analog Values)

Measured value transmission is defined as follows:
• 2 or 4 measured values for each SINAUT ST1 message
• with or without a time marker
• Spontaneously or in the event of a general interrogation
• Encoding as raw values or fixed point formats
ST1 message format for measured values (AE = 0)
[sc_measured_value_AE0_en, 1, en_US]
O … Overflow
F … Open circuit, is set if SICAM A8000 NT = 1 or IV = 1

DC8-037-2, Edition 11.2020
12.11 SINAUT ST1
TA = 3 … Interrogated message (general interrogation)
ST1 message format for measured values (AE = 1)
[sc_measured_value_AE1_en, 1, en_US]
O … Overflow
F … Open circuit, is set if SICAM A8000 NT = 1 or IV = 1
Measured value encoding

Raw values: -2048 to 0 to +2048 (= -100 % to 0 to +100 %)
Example:
Name Range Raw value Value on the control
system
ND tank pressure 0 to 40 mbar 0x2F00 29.4
ND tank contents 0 to 150000 cbm 0x1500 49365
Fixed point format

The measured value is represented as a scaled value in the range of -32768 to +32767
Example:
Name Range Raw value Value on the control
system
BHKW4 flow temp. 0 to 99 0x001F 31
Total elec. power -5500 to +5500 0xFFDB -37
Address conversion between SINAUT ST1 → SICAM A8000

The address and message conversion for measured values (analog values) in transmit direction can be para-
meterized using the SICAM TOOLBOX II, OPM II or for engineering via SICAM WEB with the transmit detailed
routing parameters.

DC8-037-2, Edition 11.2020
12.11 SINAUT ST1
Parameter category:
firmware /Trans_Fr
Parameter Meaning
IOA1
IOA2
IOA3
• Measured value 15-bit + normalized sign <TI:=34>

• Measured value 15-bit + scaled sign <TI:=35>
• Measured value - short floating-point number <TI:=36>
2 to 255
ST1_data_index_(ST1Sxx) Bit position for binary information or value numbers for measured values
0 to 31

DC8-037-2, Edition 11.2020
12.11 SINAUT ST1
Parameter Meaning
• 4
• 8
• 16
Telegram with Transmit message with or without time marker
ST1_format_(ST1Sxx) ST1 data format
X_0% Value adaptation
Lower limit of the range of values used in the external format (protocol-specific).
The corresponding internal value is configured at Y_0%.
Possible options: -32768 to +32767
Upper limit of the range of values used in the external format (protocol-specific).
Y_0% Value adaptation
Lower limit of the range of values used in the selected internal format. The
internal format is specified by the TI (type identification). The corresponding
external value is configured at X_0%.
Possible options:
<TI:=34>: -1 to +1
<TI:=35>: -32768 to +32767
<TI:=36>: no test
Upper limit of the range of values used in the selected internal format. The
Possible options:
<TI:=34>: -1 to +1
<TI:=35>: -32768 to +32767
<TI:=36>: no test
Spontaneous message forwarding

This table describes the data point quality descriptor and the cause of transmission according to
IEC 60870-5-101/104.

DC8-037-2, Edition 11.2020
12.11 SINAUT ST1
Message elements
TI .. type identification <TI:=34> .. Measured value, normalized value with time marker
CP56Time2a
<TI:=35> .. Measured value, scaled value with time marker
CP56Time2a
<TI:=36> .. Measured value, short floating-point number with
time tag CP56Time2a
CASDU, IOA .. message address Configurable
BL .. blocked Not supported
SB .. substituted Not supported
NT .. not topical F … open circuit = 1, if SICAM A8000 NT = 1
IV .. invalid F … open circuit = 1, if SICAM A8000 NT = 1
OV .. overflow Non-linearized value outside the parameterized measurement
range (X0, X100) or conditioned value outside the range (Y0,
Y100).
The conditioned value is limited to Y0, Y100.
03 .. spontaneous
20 .. interrogated
Measured Value Conversion in Transmit Direction

ST1Sx0 supports the following measured value formats:
• Measured value 12-bit Left-aligned -2048 to 0 to +2048

+ sign
• Measured value 15-bit -32768 to 0 to +32767
+ sign
The ST1 measured value format can be converted to 3 SICAM A8000 type identifications:
• Measured value - normalized <TI:=34> Value range : -1 to +1

• Measured value - scaled <TI:=35> Value range: -32768 to +32767
• Measured value - short floating-point number Value range: -3.4⋅1038 to +3.4⋅1038
<TI:=36>
A linear adaptation can be parameterized for each measured value. Linear adaptation is defined by the param-
eters X_0%, X_100%, Y_0%, Y_100%.
As the protocol firmware only defines two measured value formats, the following range of values results for
the parameters X_0% and X_100%:
Measured value 12-bit Left-aligned -2048 to 0 to +2048
+ sign
Measured value 15-bit -32768 to 0 to +32767
+ sign
The following also applies: X_100% > X_0%

The parameters Y_0% und Y_100% are determined by the SICAM A8000 internal type identification.
Measured value - normalized: -1 to +1
Measured value - scaled -32768 to +32767
Measured value - short floating- no test
point number:
Linear adaptation is activated if X_0% or X_100% has been parameterized as not 0.

DC8-037-2, Edition 11.2020
12.11 SINAUT ST1
Conversion without Linear Adaptation
• Measured value - normalized <TI:=34>

– 11-bit measured value:
value SICAM A8000 = value ST1 / 2048
value ST1 < -2048 ⇒ value SICAM A8000 = -1, OV = 1
value ST1 > +2048 ⇒ value SICAM A8000 = 1, OV = 1
– 15-bit measured value:

value SICAM A8000 = value ST1 / 32767
value ST1 < -32768 ⇒ value SICAM A8000 = -1, OV = 1
value ST1 > +32767 ⇒ value SICAM A8000 = 1, OV = 1
• Measured value - scaled <TI:=35>

value SICAM A8000 = value ST1

value SICAM A8000 = value ST1
The received binary value is converted to a floating-point number.
Conversion with Linear Adaptation

Adaptation is activated if X_0% or X_100% has been parameterized as not 0.
Value SICAM A8000 = k ⋅ value ST1 + d
whereby:
k = (Y100 – Y0) / (X100 – X0)
d = Y0 – k ⋅ X0
NOTE
i Value ST1 < X0 ⇒ value SICAM A8000 = Y0, OV = 1

Value ST1 > X100 ⇒ value SICAM A8000 = Y100, OV = 1

DC8-037-2, Edition 11.2020
12.11 SINAUT ST1
Example: Bipolar measured values
[dw_bipolar_mv_conditioning, 1, en_US]
X0, X100: ST1 value (for example,: X0 = -2048, X100 = 2048)

Y0, Y100: SICAM A8000 value (for example: short floating Point, Y0 = -100, Y100 = 100)
X_0% and Y_0% must be parameterized as 0 for unipolar measured values.
12.11.9.3 Integrated Totals

Integrated total transmission is defined as follows:
• 1 integrated total for each SINAUT ST1 message
• With time tag
• Transmission every minute, derived from the time in the substation
• Even in the event of general interrogation (last value including the time from the process image)
• Encoding: 28-bit + 2 additional bits

DC8-037-2, Edition 11.2020
12.11 SINAUT ST1
ST1 message format for metered values (AE = 0)

(Representation without a time tag)
[sc_counter_value_AE0, 1, en_US]
US … Freezing identifier, changes for each transmission trigger (not for general interrogations)
A … Update status bit (1st metered value after restart: A= 0)
ST1 message format for metered values (AE = 1)

(Representation without a time tag)
[sc_counter_value_AE1, 1, en_US]
US … Freezing identifier, changes for each transmission trigger (not for general interrogations)
A … Update status bit (1st metered value after restart: A = 0)

The address and message conversion for integrated totals in transmit direction can be parameterized using the
SICAM TOOLBOX II, OPM II or for engineering via SICAM WEB with the transmit detailed routing parameters.

DC8-037-2, Edition 11.2020
12.11 SINAUT ST1
Parameter category:
firmware /Trans_Fr
Parameter Meaning
IOA1
IOA2
IOA3
• 31-bit metered value + sign <TI:=37>

2 to 255
ST1_data_index_(ST1Sxx) Bit position for informations or value numbers for measured values
0 to 31

DC8-037-2, Edition 11.2020
12.11 SINAUT ST1
Parameter Meaning
• 4
• 8
• 16
Telegram with Transmit message with or without time tag
ST1_Format_ST1Sxx ST1 data format
12.11.10Message Conversion In Receive Direction (SICAM A8000 ← ST1)
Message conversion in receive direction: IEC60870-5-101/104 ← SINAUT ST1
IEC 60870-5-101/104 ← SINAUT ST1

Type Designation TA ZK Designation
identifi-
cation
<TI:=45> Single command 2 0 Command
<TI:=46> Double command 2 0 Command
<TI:=47> Regulating step command 2 0 Command
<TI:=48> Setpoint command, normalized value 2 0 Setpoint value
<TI:=49> Setpoint command, scaled value 2 0 Setpoint value
<TI:=50> Setpoint command, short floating-point 2 0 Setpoint value
number
TA … SINAUT ST1 message type

ZK … SINAUT ST1 additional identifier
12.11.10.1 Commands
Command transmission is defined as follows:
• Spontaneous
• 8 commands for each SINAUT ST1 message (“1 out of 8”)

DC8-037-2, Edition 11.2020
12.11 SINAUT ST1
ST1 message format for commands (A = 0)
[sc_command_AE0, 1, en_US]
Additional identifier = 0
ST1 message format for commands (AE = 1)
[sc_command_AE1, 1, en_US]

The address and message conversion for commands in receive direction can be parameterized using the
Parameter category:

DC8-037-2, Edition 11.2020
12.11 SINAUT ST1
Parameter Meaning
IOA1
IOA2
IOA3

• Measured value for short floating point <TI:=36>
2 to 255
ST1_command_bit_(ST1S Bit position for binary information or value numbers for measured values
xx) 0 to 7
IEC_quali- Command output time to be added
fier_of_command
• No definition
• Short
• Long
IEC-command_state Assignment between the IEC command status and ST1 command bit
• NOT USED
• OFF
• ON
12.11.10.2 Setpoint Values

Setpoint value transmission is defined as follows:
• Spontaneous
• 1 setpoint value for each SINAUT ST1 message (non-linearized values, 100% = 2048 bit)
ST1 message format for setpoints (AE = 0)
[sc_setpoint_value_AE0, 1, en_US]
Additional qualifier = 0!

DC8-037-2, Edition 11.2020
12.11 SINAUT ST1
ST1 message format for setpoints (AE = 1)
[sc_setpoint_value_AE1, 1, en_US]
Raw value representation:

Setpoint input from the control system:
Setpoint = 25000 (100 % = 65000) => Raw value = 0x1898 (=787 dec)
Setpoint = 18000 (100 % = 65000) => Raw value = 0x11B8 (567 dec)
Address conversion between SINAUT ST1 → SICAM A8000s
The address and message conversion for commands in receive direction can be parameterized using the
Parameter category:

DC8-037-2, Edition 11.2020
12.11 SINAUT ST1
Parameter Meaning
IOA1
IOA2
IOA3
• 15-bit setpoint value + normalized sign <TI:=48>

• 15-bit setpoint value + normalized sign <TI:=49>
• Setpoint value, short floating-point number <TI:=50>
2 to 255
ST1_format_sv_(ST1Sxx) Setpoint value format
Setpoint value 12-bit + sign, left-aligned
Possible options: -2048 to + 2047
Possible options:
<TI:=34>: -1 to +1
<TI:=35>: -32768 to +32767
<TI:=36>: no test
Possible options:
<TI:=34>: -1 to +1
<TI:=35>: -32768 to +32767
<TI:=36>: no test
Setpoint Value Conversion

Value range: -2048 to +2048
The following SICAM A8000 type identifications can be converted to ST1 setpoint format:

DC8-037-2, Edition 11.2020
12.11 SINAUT ST1
• Setpoint command - normalized <TI:=48> Value range: -1 to +1

• Setpoint command - scaled <TI:=49> Value range: -32768 to +32767
• Setpoint command - short floating-point number Value range: -3.4⋅1038 to +3.4⋅1038
<TI:=50>
A linear adaptation can be parameterized for each setpoint value. The linear adaptation is defined by the
parameters X_0%, X_100%, Y_0%, Y_100%.
As only one setpoint format is defined in the ST1 protocol, the following range of values results for the param-
eters X_0% and X_100%:
X_0%, X_100% = -32768 to +32767
The following also applies: X_100% > X_0%
The parameters Y_0% und Y_100% are determined by the type identification used inside the SICAM A8000.
Setpoint value - normalized: -1 to +1
Setpoint value - scaled: -2048 to +2048
Setpoint value - short floating- no test
point number:
Linear adaptation is activated if Y_0% or Y_100% has been parameterized as not 0.
Conversion without Linear Conversion
• Setpoint command - normalized <TI:=48>

– SICAM A8000 - value range: -1 to +1
value ST1 = value SICAM A8000 ⋅ 2048
• Setpoint command - scaled <TI:=49>

– SICAM A8000 - value range: -32768 to +32767
value ST1 = value SICAM A8000
• Setpoint command - short floating-point number <TI:=50>

– SICAM A8000 - value range: -3.4⋅1038 to +3.4⋅1038
value ST1 = value SICAM A8000
A conversion is carried out from the floating-point value to a binary value. If the SICAM A8000 value is greater
than 2048 or less than -2048, the setpoint value is discarded with the error message Error format
conversion in transmit direction.

Adaptation is activated if Y_0% or Y_100% has been parameterized as not 0.
Value SICAM A8000 = k ⋅ value ST1 + d
whereby:
k = (X100 – X0) / (Y100 – Y0)
d = X0 – k ⋅ Y0
If the setpoint value cannot be adapted (setpoint < Y_0% or setpoint > Y_100%), the setpoint value is
discarded with the error message Error format conversion in transmit direction.

DC8-037-2, Edition 11.2020
12.11 SINAUT ST1
Bipolar setpoints
[dw_bipolar_sp_conditioning, 1, en_US]
X0, X100: ST1 value (for example: X_0% = -2000, X_100% = 2000)
Y0, Y100: SICAM A8000 value (for example: normalized, Y_0% = -1, Y_100% = 1)
X_0% und Y_0% must be parameterized as 0 for unipolar setpoints.
12.11.11Organizational Messages (System Messages)
There is a wide variety of organizational messages in SINAUT ST1 that are used for monitoring the system as
well as for additional system concepts (general interrogation, diagnostics, time synchronization).
The following organizational messages are currently supported:
• General interrogation (ORG = 08)
• Time synchronization (ORG = 10)

All other messages are acknowledged at “protocol level”, but are not evaluated.
General Interrogation (Master Station → Substation)

message structure:

DC8-037-2, Edition 11.2020
12.11 SINAUT ST1
[sc_general_interrogation, 2, en_US]
If a substation receives an organizational message with ORG = 08, then the firmware transmits its entire
process image as follows:
• All indications (ascending according to ST1 address)
• All measured values (ascending according to ST1 address)
• All metered values (ascending according to ST1 address)

Metered value transmission can be adjusted; the last 1 minute value is transmitted, the freeze identifier
and time are not redefined.
[sc_time_synchronization, 2, en_US]
Assigning the additional time identifier:

Bit 4 = 0: Standard time
Bit 4 = 1: Daylight saving time
Bit 6 = 1: SYN bit; TIM clock is synchronized
Bit 7 = 1: STEL bit; TIM clock is set
The SINAUT ST1 controller periodically transmits this command according to an adjustable time grid (preset:
24 hours). In addition, it is always transmitted to the relevant station after an outgoing communication fault.
The time synchronization is transmitted twice at 1 to 2 second intervals (SYN bit changes)

DC8-037-2, Edition 11.2020
12.11 SINAUT ST1
NOTE
i The substation must correct the time received by the message runtime!
The set time message does not contain any milliseconds.
12.11.12Protocol Element Control and Return Information
This function is used for the user-specific influencing of the functions of the protocol elements. It contains two
parts that are independent of one another:

• Applicational control of station interrogation
• Testing the availability of stations
• The suppression of errors with intentionally switched-off stations (Station Service)

• Using state of certain state lines as process information
• Obtaining information about the station statue/failure
Block diagram
[dw_protocol_control, 2, en_US]

The protocol element control is not supported by the protocol element for SIEMENS SINAUT ST1 TIM11 slave
(substation function)!

DC8-037-2, Edition 11.2020
12.11 SINAUT ST1

information in monitoring direction and thereby enables protocol element statuses to be
• Status of the status lines

The messages with process information are assigned to the feedback on the base system element
using the system parameters for the SICAM A8000 system data protocol element return informa-
tion.
The source from which the parameterized return information should be generated can be set using the param-
eters Supplementary system element and Station number.
Messages for the protocol element return information are transmitted to the basic system element from the
protocol element spontaneously if there is a change, or as a response to a general interrogation command.
Possible master station return information:

Station
Status DTR 255 1 = status line active
States of the status lines are transmitted to the basic
system element by the protocol element spontane-
ously upon a change or as reply to a general interrog-
ation command. The spontaneous transmission of the
current states takes place internally in a 100 ms grid.
⇒ Status line changes shorter than 100 ms are not
always transmitted!
Status DSR 255 1 = status line active
always transmitted!
Station status 0 to 99 1 = Station enabled for access cycle
Station failure 0 to 99 1 = Station failed
Legend:
0 to 99 ..... of the selected protocol element
255 .......... Station number not used!

DC8-037-2, Edition 11.2020
12.12 Telegyr TG800
12.12 Telegyr TG800
The Landis & Gyr TELEGYR 800 slave protocol is used for interfacing of CP-8000/CP-802x to telecontrol centers,
frontends and control systems by using multi-point traffic.
one or several substations over a communications link in a line or star configuration. The data traffic is
controlled by the master station.
Configuration
Single Configuration
[sc_single_configuration, 1, en_US]
Multi-Hierarchical Configuration
[sc_multi_hierarchical_configuration, 1, en_US]

DC8-037-2, Edition 11.2020
12.12 Telegyr TG800
• Connection of TG80x RTUs to the SICAM A8000 RTU is not possible (reason: transit concept of TG800).
• Each SICAM A8000 station must correspond system-technically and process-technically to a TG800
station.
Substation with Interfacing of Protection Equipment or Bay Control Units
[sc_RTU_interfacing_protection_equipment_bay_control_units, 1, en_US]
The data of the protection equipment or bay control units shall be transmitted with the same TG800 station
number to the frontend, as the data of the substation itself.
The substation connected at the TG800 frontend “conceals” the subordinate protection equipment or bay
control units and reports the datapoints in the local address range (all datapoints have the same TG800 station
number). In this case a (connection) failure of a protection equipment or bay control unit amounts to the
failure of a local module.
12.12.2 Functions
Communication of a central station with one or more substations.
• Unbalanced multi-point traffic according to L&G TG800

TG8ST0 is substation
– Data acquisition by polling (station interrogation)
– Acquisition of events (transmission of data ready to be sent)
– General interrogation, substation interrogation
• Supported functionality according document

– SICAM RTUs TG800 Interoperability
• Spontaneous transmission of commands and set points in command direction
• Spontaneous transmission of indications, measured values and integrated totals (counter values) in
monitoring direction
• Multi-hierarchical configurations possible
• Tme synchronization via communication
• Transmission of messages and measured values in command direction
• Subset of TG800 system indications
• Radio spontaneous mode

DC8-037-2, Edition 11.2020
12.12 Telegyr TG800
ment.
optional DCE
Optical interface (multimode fiber optic) ring X2 →CM-0821 RXD, TXD, CTS, RTS, DCD, DTR,
NOTE
may be needed.

SICAM A8000 CP-8000/CPC80 TG8ST0
CP-802x/CPC80 TG8ST0

SICAM AK 3 CP-2016/CPCX26 SM-2551/TG8MA0
CP-2019/PCCX26 SM-0551/TG8MA0
Legacy systems CP-20xx SM-2551/TG8MA0
(SICAM AK CP-50xx SM-0551/TG8MA0
SICAM TM CP-60xx SM-2541/TG8M00
SICAM BC
Ax 1703)
Third-party system - - acc. to SICAM RTUs
TG800ST1 Interoperability


DC8-037-2, Edition 11.2020
12.12 Telegyr TG800
Transmission rate 50, 110, 150, 200, 300, 600, 1200, 1800, 2000, 2400, 4800, 9600
Modulation PCM byte asynchronous
Transmission mode Half-duplex
Character representation Refer to DIN 66022
Bit transmit sequence: LSB (least significant bit) is transmitted first
Message protection • HA = 4
• HA = 8 (only commands and setpoint values)
Message structure DIN 19244 (issue January 1986)
Message formats in monitoring Indication without time tag, IAC = 1
direction (= transmit direction) Blocks of GA indications, IAC = 15
Block with system indications, IAC = 18
Indications with time tag , IAC = 2
Measured values, IAC = 3
Blocks of GI measured values, IAC = 16
Single current counter values call up, IAC = 10
Double current counter values call up, IAC = 11
Own station number, IAC = 25
GI Instruction to the master - for indications, IAC = 158
GI Instruction to the master – for measured values, IAC = 159
Message formats in command Pulse command, IAC = 128
direction (= receive direction) Permanent command, IAC = 129
Stop-permanent command, IAC = 130
Setpoint, IAC = 131
PBN-command, IAC = 134
Time synchronization, IAC = 135
Counter value request F, IAC = 140 (without address field extension)
Counter value request FR, IAC = 141 (without address field extension)
Counter value request FT, IAC = 142 (without address field extension)
Counter value request FRT, IAC = 143 (without address field extension)
Counter value request T, IAC = 144 (without address field extension)
GI request for indications, IAC = 160
GI request for measured values, IAC = 161
GI request for system indication block, IAC = 162
System indication block - acknowledge, IAC = 163
Transmit own station number, IAC = 165 (without address field exten-
sion)
Indications in command direction without time tag , IAC = 1
Blocks of GI indications, IAC = 15
Measurands in command direction with time tag, IAC = 2
Measurands in command direction on event, IAC = 3
Blocks of GI measurands, IAC = 16
Support of multi-hierarchical Using the address field extension in command direction, TG800 failure
TG800-network configurations concept
Transmission of the system Single system indications or collective system
Radio spontaneous mode

DC8-037-2, Edition 11.2020
12.12 Telegyr TG800
Restrictions
• Only listed IACs (information type) are supported
• No GI-completeness check
• No process image in receive direction – data are forwarded with each reception
• No Confirmation/Termination handling according to IEC 60870-5-101
• The TG800 address (cubical no., chassis no., slot no. and point no.) must be unique about all information
types (IAC) (is checked by the firmware)
• Restricted support of the address field extension (in multi-hierarchical configurations) in command direc-
tion
• No address field extension (= transit information) in monitoring direction
• Operating mode only as a multi-point traffic slave
• Transmission of the indication with time tag (IAC = 2) always with full time
• No setting of counter values
• No counter value formatting; counter value range in TG800: 0 to 9999999

value range must already be formatted at the aquisition (caution: interfacing third party system)
• PBN-commands:
– only program number = 1, 2 supported
– each event leads to a communication link
• Radio spontaneous mode:

– DCD and DSR always necessary
– each event leads to a communication link
NOTE
i This protocol element implements only part of the functionality and the data formats of the third-party
interface. For a concrete application case therefore, it should be verified to what extent the actual require-
ments correspond with the functionality implemented here and to what extent additional expansions or
adaptations are necessary. The following manual descripes the functionality of the latest firmware revision.
Instruction for Parameterization
• Single-point information <TI:=30>, double-point information <TI:=32> and integrated totals <TI:=37>
must always be transmitted with 7 octett time tag; (IEC 60870-5-101/104 parameter standard setting).
• Blocking (between PRE and BSE) must be activated - but message length is limited up to 60 byte.
Asynchronous Transmission
The data are pulse-code modulated in groups of 8 bits and transmitted asynchronous. A UART-module in asyn-
chronous mode thereby provides each byte with a byte frame (BR).
This byte frame contains: 1 Start bit
8 Data bits
1 Stop bit
The start and stop bit of the byte frame ensure that the receiver is synchronized again for each byte.

DC8-037-2, Edition 11.2020
12.12 Telegyr TG800
[sc_asynchronous_transmission, 1, en_US]
Isochronous Transmission
In "isochronous" transmission mode the individual bytes are transmitted by using an external clock, which is
delivered by a communication system (isochronous = clock and data is transmitted on different lines). The
clock delivered by the communication system must be connected to V.24 interface line CTS.
The byte frame is equal to the byte frame in the asynchronous mode.
Parameterization of isochronous mode:
[sc_isochronous_transmission_1, 2, en_US]

DC8-037-2, Edition 11.2020
12.12 Telegyr TG800
[sc_isochronous_transmission_2, 2, en_US]

CCITT USA Line Designation Direction
V.24 Rem.
102 GND Signal Ground Signal Ground
103 TD Transmit Data Transmit Data → DCE
104 RD Receive Data Receive Data ← DCE
105 RTS Switch on transmit par Request to send → DCE
106 CTS Clear to send Clear to send ← DCE
109 DCD Receive signal level Data carrier detect ← DCE
107 DSR Data Set Ready Data Set ready ← DCE
12.12.5.4 Transmission protocol and message formats

Generally, every message consists of two parts:
• A protocol-dependent part (message frame)
• A non-protocol-dependent part (message data)

The message structure relates to the DIN-standard 19244 (Transmission Protocol for the format class F 1.2),
issue January 1986.
The transmission protocol defines the rules for the message structure and the transmission procedure. The
telecontrol message is structured such that the allocation to the ISO layers, see DIN ISO 7498, Connection,
Network and Transport, on the one hand, and to the higher layers, on the other hand, becomes recognizable.
Basic message format:

DC8-037-2, Edition 11.2020
12.12 Telegyr TG800
Header for Communication Unit (KE)

(Connection, Network and
Transport layer)
Header for Process Unit (PE)

(higher layers)
Information part
End part for Communication Unit (KE)
Message Formats
The message formats and rules refer to the standard: "Telecontrol Equipment and Systems TC 57: Transmis-
sion Protocols" for Format Class FT 1.2.
Formats for fixed and variable message length as well as single character are defined. Among other things, the
formats differ through different start characters.
Rules for Formats with Fixed Block Length
• Block Length <> 0

For TG800, the format has a fixed length of 5 bytes and consists of one start character, 2 user bytes, one
check byte and one stop byte.
This format is used by the master station for cyclic request to a remote terminal unit, if no information for
the higher level communication layers has to be transmitted.
[sc_rules_fixed_block_length, 1, en_US]
Note:
Generally, D1 is the least significant bit (LSB).
Representation of a byte (LSB shown right-aligned):
[sc_representation_byte_LSB, 1, en_US]

DC8-037-2, Edition 11.2020
12.12 Telegyr TG800
• Single Character (block length = 0)

It is used as short reply by the RTU (positive acknowledgement).
[sc_single_character_block_length, 1, en_US]
• Transmission Rules for Formats with Fixed Block Length
1. Line idle is binary 1.

2. Each UART character consists of one start bit (0), 8 Information bits, one parity bit (even) and one stop
bit (binary 1).
3. No line idle intervals are admitted between characters of a frame. This is necessary (acc. to DIN) due
to the required hamming distance = 4.
4. If a new message is to be received, a receive disable time is activated if the carrier is detected. On
expiry of this time, the start bit of the first character of the message is expected. The receive disable
time is used to bridge the transients on the line and is essentially dependent on the channel.
Hint:
The receive disable time must be activated via parameter.
Parameter protocol enabling/receiver disable (at DCD) receive disable time =
bounce suppression time (tbounce) + stabling monitoring time (tstab))
In case of a loss of synchronization, the master station must wait at least receive disable time and
further 33 bits (after activating the carrier) with the transmission of the message. The receiver can
synchronize during this time, this means, after it has received at least 33 Idle bits, it expects a start
character. A loss of synchronization is regarded as being a negative result of the checks under Point 6.
In such a case, the receiver does not answer the request, which is detected by the master station.
5. The user data bytes are monitored by the checksum. The checksum is the arithmetic sum of all user
data bytes without consideration of those carried over (without start and stop).
6. The receiver checks:
• per UART character: start bit, stop bit and parity bit (even).
• per message: start character, checksum and stop character
If one of these checks produces a negative result, then the whole message is discarded. The remaining
sequence is as described under Point 4 for loss of synchronization, this means, the message is not
acknowledged (by the remote terminal unit) and must be repeated. With a positive check result, the
information is forwarded to the next higher level of the communication.
Rules for Formats with Variable Block Length

The format consists of one initial start character, two identical characters in which specify the number L of
user data bytes, one second start character, the user data, the checksum and the stop character. The number L
of user data bytes is within the range of 0 to 255.
This format is used for the data transmission in command direction as well as in the monitoring direction. Here
one regards data as being information, which is transmitted between higher levels of the communication
systems of two stations.

DC8-037-2, Edition 11.2020
12.12 Telegyr TG800
[sc_rules_variable_block_length, 1, en_US]
• Transmission Rules for Formats with Variable Block Length

The rules and regulations 1 to 5 listed under Formats with Fixed Block Length are also applicable here.
6. The receiver checks:
• per UART character: start bit, stop bit and parity bit (even)
• per message:
– the defined start character at the beginning and after the two L-bytes
– the identity of the two length bytes L
– whether the number of characters received (bytes) equals L + 6
– the checksum
– the stop character
If one of these checks produces a negative result, then the whole message is discarded. The remaining
sequence is as described for loss of synchronization under Point 4 Formats with Fixed Block Length,
this means, the message is not acknowledged (by the remote terminal unit) and must be repeated.
With a positive check result, the information is forwarded to the next higher level of the communica-
tion and the message is acknowledged to the transmitter station.
By complying the above rules and character definitions, all formats according to DIN-standard are protected
against faulty information as well as displacements (synchronization errors).

DC8-037-2, Edition 11.2020
12.12 Telegyr TG800
Used Message Formats

To enable an efficient transmission of information, three message formats (two with fixed length and one
with variable length) are used.
• Long Record
In monitoring direction:
– Event data with/without operation request (indications with/without time, measured values, etc.)
– Data after special interrogation with/without operation request (counter values, GI indications, GI-
measured values, etc.)
A long record in monitoring direction can contain information from several stations!
In command direction:
– Event data in command direction, (commands, set points, etc.)
– "Broadcast" information such as counter value requests, commands, time synchronization, etc.
These data are not acknowledged by the remote terminal units.
A long record in command direction always contains information for only one station!
• Short Record
In command direction:
– Request to RTU to transmit events from it.
– State interrogation to RTU (On-Off-Line).
– Reset security bit (record sequence bit)
In monitoring direction:
– Acknowledgement of the RTU to state interrogation (RTU is offline)
• Single Character
Only in monitoring direction as reply from the remote terminal unit (positive acknowledgement) after a
request of the master station, if:
– no event information is present
– as acknowledgement with additional information (for instance for received commands, setpoints,
etc.)
– as acknowledgement of the remote terminal unit to state interrogation (RTU is online)
12.12.5.5 Length, Address and Function Fields
Layout of the Length-(L)-Field

The length-field defines the number of user data bytes. Values between (0) and 255 are possible. In practice,
the maximum length L is limited by the network configuration (i.e. call distance) and by the communication
quality (number of message retries). If required, it should be able to be adapted.
[sc_layout_length_L_Field, 1, en_US]
The maximum length can be parameterized.
Layout of the A-Field and Device Address

In both command and monitoring direction, the A-field contains the device address. The device is identified
with this on the communication line. According to Landis & Gyr terminology this device address is the COM

DC8-037-2, Edition 11.2020
12.12 Telegyr TG800
number (link address) on the communication line. Up to 255 devices can be connected to one communication
master (firmware supports only 100).
[sc_layout_A_Field_device_address, 1, en_US]
Remarks about device address:

On a line, each station must know which messages are directed to it and where they are coming from. A
helpful fact is, that communication only takes place between master and slave but not between slaves. In all
messages it is therefore sufficient to specify the slave concerned, whether it is now transmitter or receiver.
• Every message received by master is directed to it.
• The slave number in the message received by the master identifies the transmitter.
• If the slave receives a message with its number, it is directed to it by the master (other numbers can origi-
nate from the master or from another slave).
As already mentioned, for the exchange of messages on a line, the address of a slave is called COM-number
(communications number) and is located in the A-field of the message. Since it is only used on one line, it can
be shorter than the station number unique in the entire network. The master needs no COM number.
A "broadcast" message is transmitted by the master with the special COM number = 255, evaluated by all
slaves but acknowledged by none (example: time synchronization).
Layout of the F-Field in Command Direction

Besides other functions, the function-(F)-field contains the acknowledgement bit. Erroneous communication is
deteced and repaired with it.
[sc_layout_F_Field_command_direction, 1, en_US]
Meaning of the fields in the F-field in command direction:

DC8-037-2, Edition 11.2020
12.12 Telegyr TG800
RB = 1 Direction bit of the information (= 1 in command direction)

AE Address field extension – used for transit information:
In the address field extension is then the destination station number
00 = no extension
01 = extension by 1 address byte
10 = extension by 2 address bytes
11 = Special SBB extension extended by 1 byte COM number
Attention: The address field expansion is supported only restrictedly.

FA Function selection:
not used (state is not evaluated)
0 = Request control code is for the communication unit (communication layer 1 to 4 in accordance
with OSI).
1 = Request control code is for the process unit (communication layer 5 to 7 in accordance with
OSI).
Function selection is not evaluated by the firmware..
Request control code
D8 D7 D6 D5 Meaning: Meaning:
to communication unit VE (FA = 0) to process unit PE (FA = 1)
0 0 0 0 Reset of VE –
0 0 0 1 Status request of VE –
0 1 1 0 – Write with SFB = 0 (e.g. commands)
0 1 1 1 – Write with SFB = 1 (e.g. commands)
1 0 1 0 – Read event data SFB = 0
1 0 1 1 – Read event data SFB = 1
Conventions:
• At D5 is also the block sequence bit (SFB) see Security Bit (SFB) in the F-Field, Page 1453.
• The status of the FA bit in the F field is not evaluated.
NOTE
i The request control code of "0 0 0 0 " (reset) is used in the TG800 only to reset the communication unit
(not to reset the automation unit).
Layout of the F-Field in Monitor Direction
[sc_layout_F_Field_monitor_direction, 1, en_US]
Meaning of the fields in the F-field in monitoring direction:

DC8-037-2, Edition 11.2020
12.12 Telegyr TG800
RB = 0 Direction bit of the information (= 0 in monitoring direction)

AE Address field extension – used for transit information:
In the address field extension is then the destination station number
00 = no extension
01 = extension by 1 address byte
10 = extension by 2 address bytes
11 = Special SBB extension extended by 1 byte COM number
Attention: The address field extension "01" and "10" in monitoring direction is not supported!
AS Request inhibit (not used in TG800)
AQ Order acknowledgement (not used in TG800)
OF State of the TG809-RTU (special in TG800, not according to DIN standard)
0 = online
1 = offline
The firmware only supports OF = 0 (= online).

BA Communication request to the master
0 = no (more) event data available

1 = (more) event data available
It depends on the master station to reach to this request or not.
Security Bit (SFB) in the F-Field

The security bit (block sequence bit SFB) protects the communication against loss of information or duplica-
tion. With the SFB in the request control code of the F-field in command direction, it is possible to repeat the
message on OSI layer 1 to 4 without unnecessary forwarding to the higher Layer 5 to 7.
The SFB is set in the F-field of the request by the calling station (master) for each remote station.
The remote stations interpret a new SFB which is different to the previous, as positive acknowledgement for
their last sent information. Up until this moment, they hold the last sent information ready for a possible
repeat.
For each station there is only one valid state of the security bit, independent of whether the master sends an
instruction command for “Writing” or “Reading”.
Activities of the RTU in the SFB-management:
• Store the SFB state of the last information received.
• On reception of a new information, the SFB received is compared with the stored SFB state:
– changed SFB = Positive acknowledgement for the last information sent. The repeat buffer can be
overwritten.
– unchanged SFB = Negative acknowledgement. The last information must be transmitted again to
the master, or an already initiated command is not executed again.
• Reception of a broadcast information with A-field 0xFF:

The received SFB contents may not be noticed and do not have influence on the SFB status stored in the
RTU.
The broadcast information is not acknowledged by any RTU.

DC8-037-2, Edition 11.2020
12.12 Telegyr TG800
• Reception of a Status Request

The status request has no influence on the SFB bit; the firmware always acknowledges with the single
character E5.
• Reception of a Reset of VE
The SFB status stored in the RTU is set on 0; the firmware always acknowledges with the single character
E5.
Attention: The repeat buffer is deleted.
Address Field Extension

Contrary to DIN standard, TG800 does not use this field for the representation of a strict addressing hierarchy.
For TG800 the address field extension is used, if information needs to be sent to a station which is not
connected on the communication line. Normally this concerns the transmission of information in a communi-
cation line on another hierarchy level.
This has the advantage, that the messages are shorter, as well as that the transmitter station does not need to
know the precise structure of the network.
• Destination station number = 0 to 255
[sc_address_field_extension_1, 1, en_US]
• Destination station number = 256 to 1023
[sc_address_field_extension_2, 1, en_US]

DC8-037-2, Edition 11.2020
12.12 Telegyr TG800
• COM-Line number
The COM Line number is used for extendion of the link address in a TG800 network.
The COM Line number makes it possible to get an unique link address in a TG800 network if more than
255 RTUs are connected via serveral communication lines to one control center.
[sc_com_line_number, 1, en_US]
12.12.5.6 Addressing of the Information
General
The information objects of the whole network must able to be unambiguously identified for the transmission.
This information includes:
• Station
• Information type
• Hardware address or software address

The aim of the system is to transmit the whole information as fast as possible, i.e. in the shortest possible
messages. Thereby frequent information must be more greatly considered. The most frequent information
are: indications without time tag, indications with time tag and measured values.
In addition, in most cases this information originates from the local stations. If the station number is missing
in a message in monitoring direction, then this concerns information from the local station.
Object Identification in TG800 System

All information existing in a TG800 System have within the station, addresses structured as follows:
Identification of the Hardware Objects
[sc_identification_hardware_objects, 1, en_US]
The meaning thereby:

Station number Unique station number in the system: 0 to 1020.
The station number 1023 (-1) is reserved for broadcast commands.
SW-Bit = 0 The following address in the bits 0 to 16 is the HW-address of the information.
SW-Bit = 1 The following address in the bits 0 to 14 is a SW-address of the information.
Cub. Cubicle number 0 to 3; in the TG809 substation always = 0, since there is only one
cubicle.
Chas.No. Chassis number 0 to 4; per cubicle up to 5 chassis are possible (valid for TG809 + TG820).
Slot-No. Slot number 0 to 15 in the chassis
Point-No. Output point number 0 to 31 (normal) and 0 to 255 for matrix command output card.

DC8-037-2, Edition 11.2020
12.12 Telegyr TG800
Identification of the Software Objects
[sc_identification_software_objects, 1, en_US]

Station number Unique station number in the system: 0 to 1020.
The station number 1023 (-1) is reserved for broadcast commands.
SW-Bit = 1 The following address in the bits 0 to 14 is the SW-address of the information.
SW-Bit = 0 The following address in the bits 0 to 16 is a HW-address of the information.
Point-No. 0 to 32767 of the SW-Information. One particular SW-point number may only be used for
one information type (e.g. indication 123 and measured value 123 not possible).
Transmission Addresses in TG800 System

The following illustrated address blocks are structured in such a way, that the most frequent information,
above all for bursts, can be transmitted in the shortest possible information blocks.
The following conventions apply:
• The communication unit always selects the shortest possible address format. Therefore the information
type (IAC), the station number, the cubicle number and the point number are taken into consideration.
• If the station number is missing in an information address, then the directly connected transmitter
station is regarded as originator station for this information (not applicable for commands and input
values in command direction).
• In the IAC-field only the following entries are possible (refer also to Information types):
IAC = 1 indication without time tag
IAC = 2 indication with time tag
IAC = 3 measured value (on event)
IAC = 0 extension of IAC in next field (remaining information types)
Short HW-Address – without Station Number
[sc_short_HW_adress_without_station_number, 1, en_US]

E=0 Address extension bit, 0 = short address (and short station number, if existing)
S=0 Station bit, 0 = no station number in address block. The originator station (source of the infor-
mation) is the station communicating directly with the master (parameter of master).
Cubicle No. 0 (missing - default)
Chassis No. 0 to 4 in cabinet no 0
Slot No. 0 to 15, where Slh = slot no high

DC8-037-2, Edition 11.2020
12.12 Telegyr TG800
Point No. 0 to 31
SW-Bit missing = address of the information is HW address
Short HW Address – with Station Number 0 to 255
[sc_short_HW_address_with_station_number, 1, en_US]

E=0 Address extension bit, 0 = short address (and short station number)
S=1 Station bit, 1 = station number follows:
Station No. 0 to 255 originator station number
Cubicle No. 0 (missing - default)
Chassis No. 0 to 4 in cubicle no. 0
Slot No. 0 to 15, where Slh = slot No. high
Point No. 0 to 31
SW-Bit missing = address of the information is HW address
Long HW-Address - without Station Number
[sc_long_HW_address_without_station_number, 1, en_US]

E=1 Address extension bit, 1 = long address (and long station number, if available)
SW = 0 SW-Bit, 0 = HW information with the following HW address
CuH, CuL Cubicle no. (high and low) = 0 to 3
Chassis No. 0 to 4
Slot No. 0 to 15
Point No. 0 to 255

DC8-037-2, Edition 11.2020
12.12 Telegyr TG800
Long HW-Address - with Station Number
[sc_long_HW_address_with_station_number, 1, en_US]

E=1 Address extension bit, 1 = long address (and long station number)
SW = 0 SW bit, 0 = HW Information with the following HW address
CuH, CuL Cubicle No. (high and low) = 0 to 3
Chassis No. 0 to 4
Slot No. 0 to 15
Point No. 0 to 255
SW-Address – without Station Number
[sc_SW_address_without_station_number, 1, en_US]

E=1 Address extension bit, 1 = long address (and long station number, if available)
SW = 1 SW bit, 1 = SW information with the following SW address
Point No. 0 to 32767

DC8-037-2, Edition 11.2020
12.12 Telegyr TG800
SW-Address – with Station Number
[sc_SW_address_with_station_number, 1, en_US]

E=1 Address extension bit, 1 = long address (and long station number)
SW = 1 SW bit, 1 = SW information with the following SW address
Point No. 0 to 32767
Information Types
The information type must be identified in the message in such a way, that the entirety of the messages trans-
mitted is as short as possible. One achieves this by making the field for the information type short for the
common information.
Short Format (0 < IAC < 4):
[sc_information_types_short_format, 1, en_US]
1 = Indication without time tag

2 = Indication with time tag
3 = Measured value
Long Format:
[sc_information_types_long_format, 1, en_US]

DC8-037-2, Edition 11.2020
12.12 Telegyr TG800
Information in monitoring direction (IAC or IAC-extension):

3 = Measured value
10 = Counter value single current, requested

11 = Counter value double current, requested
15 = Blocks of indications (GI)

16 = Blocks of analog measured values (GI)
18 = Block of system indications (GI)
25 = Own station number
158 = GI instruction to the master – for indications
159 = GI instruction to the master – for measured values
Information in command direction (IAC or IAC-extension):

128 = Pulse command
129 = Permanent command
130 = Stop-permanent command
131 = Setpoint
134 = PBN-command
135 = Time for synchronization
140 = Counter value-request F (freeze without reset without transmission)

141 = Counter value-request FR (freeze with reset without transmission)
142 = Counter value-request FT (freeze without reset with transmission)
143 = Counter value-request FRT (freeze with reset with transmission)
144 = Counter value-request T (transmission of the local freezed CVs)
160 = GI-instruction to slave units for indications

161 = GI-instruction to slave units for measured values
162 = GI-instruction to slave units for system indication block
163 = Acknowledgement system indication block
165 = Instruction - send own station number

3 = Measured value
15 = Blocks of Indications (GI)
16 = Blocks of analog measured values (GI)

DC8-037-2, Edition 11.2020
12.12 Telegyr TG800
12.12.6 Communication according to Telegyr TG800
12.12.6.1 General
Since the TG800 protocol uses the “unbalanced mode”, the data communication control is always controlled
from the “unbalanced primary” (= central station); the “unbalanced secondaries” (substations) respond only to
requests of the central station.
Based on the request control codes of the function field used in TG800, the following services are used for the
transmission of process data:
• Reading of event data (Code = 0x0A, 0x0B)

With this service, all user data of the substation is interrogated and transmitted to the central station. The
central station sends a message with fixed block length, which in all cases must be acknowledged by the
substation. If there is user data present in the substation, then this sends a long message, otherwise the
acknowledgement takes place by means of single character E5. The proper transmission is ensured by the
SFB bit.
• Writing (Code = 0x06, 0x07)

With this service, user data (commands, general interrogation, etc.) is sent from the central station to the
substation. This service must also be acknowledged by the substation, unless it concerns broadcast user
data (COM number = 255). The substation acknowledges with the single character E5, if there is no user
data present.
In contrast to IEC 60870-5-101, the substation may also reply with a long message, if there is data for
transmission present.
The proper transmission is also ensured by the SFB bit, this means, if the substation receives user data
with unchanged SFB bit, then no data transfer takes place and the message from the repeat buffer is
acknowledged.

DC8-037-2, Edition 11.2020
12.12 Telegyr TG800
12.12.6.2 Startup Procedure of TG800 Communication
[sc_startup_procedure_TG800_communication, 1, en_US]
NOTE
i The service “Reset VE” causes the remote terminal unit to initialize its communication, i.e., the "SFB-Bit" as
well as the message repeat buffer are deleted → loss of information!
12.12.6.3 Process Image

The firmware manages a process image, in order to
• monitor indications and measured values for change, and
• transmit indications and measured values directly from the image in case of general interrogation.
A process image is created for each record in the SIP message address conversion (= data point). Besides the
state (1 or 2 bits for indication, 2 bytes for measured values), the process image contains the following data
point quality identifiers:
• NT bit (not topical)
• IV bit (invalid)
• BL bit (blocked - descriptor only for bouncing signal)
• OV bit (overflow – only for measured values)
In the TG800 protocol there is only one IV identifier (= invalid).

DC8-037-2, Edition 11.2020
12.12 Telegyr TG800
IV (TG800) = NT or IV or BL or OV
Counter values are not recorded in the process image. After a firmware restart, the process image is initialized
with the state = 0 and NT = 1 (not topical), as well as the startup delay started (parameter-settable).
The startup delay serves to update the process image. During this time, no communication takes place to the
master (receiver is disabled). Changes in process state that occur are not stored.
12.12.6.4 Data Transmission Procedure and Preparation

The firmware (protocol element = PRE) may only send events to the central station, if it has received a corre-
sponding call (“request”). The data management or prioritization of the data, however, takes place on the
basic system element (BSE). If the PRE is allowed to transmit data to the central station, then the firmware
requests data from the BSE (“give me data”).
The BSE now decides based on the priority control, which data is sent to the PRE. For the optimal utilization of
the internal interface, the blocking of data on the BSE must be parameterized according to IEC
60870-5-101/104; however, the maximum message length must not exceed 60 bytes (is checked by the firm-
ware).
In addition, in contrast to IEC 60870-5-101, objects of different data types (indication, measured value,
counter value, etc.) may be transmitted in one TG800 message.
Likewise, the number of chaining operations (“give me data”) can be parameterized, in order to utilize the data
transmission on the TG800 protocol efficiently (default = 10).
The maximum message length is also parameterized on the TG800 protocol (default = 32).
The reason for limiting the internal chaining operations lies in the required message preparation time, since
the reply to the call can be delayed for a relatively long time at TG800 protocol level.
If the PRE receives an internal blocked SICAM A8000 message, then
• the internal message is unblocked
• a change comparison is performed
• the individual objects are converted to the TG800 format
• the process image is updated
• the internal blocked SICAM A8000 message is immediately positively acknowledged to the BSE.
If the maximum TG800 message length is not reached, then a further chaining operation is initiated, unless
the parameterized number of chaining operations has also been reached.
If the maximum TG800 message length is now exceeded through the additional chaining operation, then the
transmission on the TG800 protocol takes place in several blocks. The transmission of the subsequent blocks
takes place with the further requests of the central station with highest priority.

DC8-037-2, Edition 11.2020
12.12 Telegyr TG800
12.12.6.5 Multi-Hierarchical Configuration

In the TG800 system, it is possible to connect further substations to the station connected directly to the Fron-
tend (control center). In Landis & Gyr terminology, the directly connected station is called a Transit Station or
Data Concentrator.
[sc_multi_hierarchical_configuration_general, 1, en_US]
The transit station communicates with the Frontend by using the TG800 protocol.
The addressing in the TG800 system takes place by means of TG800 station number (0 to 1020), which must
be unique in the entire system.
The transit station transmits its local information without station number (S = 0), since this is known in the
Frontend (parameter = own TG800 station number).
The data of the lower-level stations is always transmitted with station number (S = 1). In command direction,
the address field expansion is used, if information is to be sent to the lower-level stations (refer to chapter
12.12.5.5 Length, Address and Function Fields).
The address field expansion, however, is not used for indications and measured values in command direction.
12.12.6.6 Failure Concept

In the TG800 system the system information USAN (indication with software address = 7) is used to signal the
failure of lower-level stations.
USAN … substation does not reply
If a TG800 system receives a USAN signal with the state = "1", then all data points of the corresponding station
are flagged with USAN and “invalid”, as well as this station flagged as USAN.
Further data should no longer be transmitted to the central station, since this can only concern invalid data.
Some control systems make a distinction between USAN and “invalid”.
If a TG800 system receives a USAN signal with the state = "0", then only the USAN identifier of the station is
removed (the data continue to remain invalid). The Invalid identifier of the data is first updated again through
a transmission of the data from the substation.
Failure concept of SICAM A8000

In the SICAM A8000 system, in case of a failure of an input board or communication breakdown, all data
points affected by the failure are flagged as “Not Topical” (NT bit according to IEC 60870-5-101/104). The NT
bit reproduction can be delayed in every automation unit (default = 30 s).

DC8-037-2, Edition 11.2020
12.12 Telegyr TG800
Realization
The realization of the USAN information (substation does not reply) in multi-hierarchical configurations should
take place by means of the existing system concepts of SICAM A8000 without additional functions (CAEx or
derived indications). For this, the AU failure bit of the AU sum error record of the automation unit is used.
However, since the addressing of the AU sum error record is done system-technical (region, component), an
assignment must takes place between Region + Component and TG800 station number (system-technical
parameterization – TG800 station number assignment).
NOTE
i • The AU sum error record of the own AU may not be entered.
• This assignment is also used for the formation of the system information HW faulty or missing
and System initialised.
Example:
[sc_realization, 1, en_US]
TG800 station number assignment
[sc_TG800_station_number_assignment, 1, en_US]

DC8-037-2, Edition 11.2020
12.12 Telegyr TG800
If the communication fails to substation R# 102, C# 42, then the higher-level system (R# 249, C# 3) sets the
bit AU failure in the AU sum error record of R# 102, C# 42. The USAN information of the TG800 station 814 is
derived automatically from the AU failure bit.
Rising failure (USAN = ON)

If the firmware receives an AU sum error record with AU failure bit set, then
• the system information USAN = ON of the corresponding station is sent to the central station (IAC = 2, SW
= 1, Point# = 7, State = ON).
• the entire process image of the corresponding station is flagged with NT (own status bit in the process
image).
The data generated through the NT bit reproduction is no longer sent to the TG800 central station, since the
NT bit is already set in the process image. However, if valid data is received, then this is indeed sent to the
central station, as well as the process image updated.
NOTE
i As of firmware version 03, the handling of information concerning the failure can be parameterized.
[sc_rising_failure_USAN_ON, 1, en_US]
• Only USAN Ind: handling as described above
• USAN Ind + INFO invalid:

Only system indications of the concerning station are flagged with NT. The data generated through the
NT bit reproduction (system function of SICAM A8000) is sent as TG800 single objects with IV = 1 to the
central station as the process information is not flagged with NT = 1 at USAN = 1 (except integrated totals
and system indications).
Falling failure (USAN = OFF)

If the firmware receives an AU sum error record with AU failure bit deleted and if the TG800 station is set to
USAN, then
• the system information USAN = OFF of the corresponding station is sent to the master (IAC = 2, SW = 1,
Point# = 7, State = OFF).
• all data points are sent to the central station spontaneously as TG800 single objects due to the general
interrogation triggered to this station (system concept “General Interrogation” from SICAM A8000).

DC8-037-2, Edition 11.2020
12.12 Telegyr TG800
12.12.6.7 General
System indications are used for the transmission of self-detected system errors. System indications are single-
point information with software address (SW = 1) beginning with point number 0.
For each TG800 station type there exists a fixed number of system indications, whose meanings are identical
over all systems (TG809: 64 system indications, all other systems: 48). → Meaning of the system indications:
refer to 12.12.9 System Indications and Collective System Indications.
The transmission of the system indication occurs:
• Spontaneous with IAC = 1 (without time tag) or IA2 = 2 (with time tag)
• Due to a general interrogation for indications (IAC = 15)
• Single or collective (= can be set globally – Parameter = System Indication Transmission).
Supported system indication:

TG800 Designation Sys-No. Formation
System initialised 0 From Startup of the AU sum error record 316
Hardware missing or faulty 4 From Board failure of the AU sum error record
USAN (RTU does not reply) 7 From AU-failure of the AU sum error record 317
Command/Setpoint discarded 21 Directly from the firmware 318
GI in progress 33 Directly from the firmware 318
All other system indications can be generated as applicable and converted to the TG800 protocol by SIP-
message address conversion.
In case of a general interrogation, the firmware only transmits used (parameterized) system indications; the
first indication group (= Point# 0 to 7) is always transmitted.
Collective System Indications

Collective system indications were defined to reduce the memory requirements and the generating work
(number of information objects) in the control center. Previously 64 (TG809), respectively 48 (TG803/801)
system indications per remote terminal unit needed to be defined in the control center; with collective system
indications, it is only 8 of these.
In all remote terminal units, each of the up to 64 system indications is assigned to one of six new collective
system indications by means of a fixed defined table.
One of these six collective system indications is transmitted spontaneously to the control center when a
system indications changes its state in the remote terminal unit.
The collective system indication numbers have the following meaning:
0: System initialized (restart)
1: General interrogation in progress
2: Hardware fault
3: Process and installation fault
4: Database and operation fault
5: CONCAP/LAF fault
6: Offline 319
7: USAN (remote terminal unit does not reply) 319
Formation of the collective system indication: refer to 12.12.9 System Indications and Collective System Indi-
cations.
316 system indication is also generated after every firmware restart with own TG800 station number
317 only possible for TG800 stations in multi-hierarchical configurations; not for own TG800 station (refer to Failure Concept, chapter
12.12.6.6 Failure Concept
318 only supported for own TG800 station
319 this information is always generated by higher-level systems (failure of a connected substation)

DC8-037-2, Edition 11.2020
12.12 Telegyr TG800
Since only collective system indication is transmitted, the operator has no knowledge which fault has occured
in the remote terminal unit. In order to determine the precise cause of the fault, the control center sends a GI
instruction for system indication block (IAC = 162) to the concerning remote terminal unit.
The remote terminal unit then immediately transmits its entire block of system indication back to the control
center. From every system indication of the remote terminal unit, both the current status as well as an event-
bit is sent, which indicates, whether the status has switched to ON at any time since the last acknowledge-
ment.
When the operator has taken note of the events, he can send an acknowledgement to the remote terminal
unit by means of an explicit command, through which the event-bits of all system indications are deleted
there.
Management of group system information

As already described, 8 collective system indications are formed from the 48 or 64 system information items.
One collective system indication is a summary (logical OR) of the individual system indications.
The system indication as well as the collective system indications are generated and managed by the firmware
for each TG800 station. A transmission only occurs spontaneously on change or for general interrogation (GI-
instruction for indications).
The acknowledgement, respectively transmission of the system indication with multi-hierarchical configura-
tions takes place by means of the address field extension of the TG800 protocol (address field extension =
TG800 station number). If an acknowledgement, respectively GI instruction for system indication block is
received without address field extension, then the handling only takes place for the own TG800 station.
12.12.6.8 General Interrogation

With the instruction GI for indications and GI for measured values, the central station causes
the substation to transmit the current process state of the required data types. For the transmission of the GI
data, specifically defined message types are used (block of GI indications, respectively GI measured values).
These message types feature a very high transmission efficiency and do not contain any time information
(similar to IEC 60870-5-101).
If the GI instruction is forwarded directly to the substation (= without address field extension), then the
general interrogation is answered directly from the process image of the firmware. The firmware, however,
also sends a GI request (image GI) to the BSE, in order to keep the process image guaranteed synchronous
between BSE and firmware.
The GI data sent by the BSE is only forwarded to the central station upon change (status or IV bit).

DC8-037-2, Edition 11.2020
12.12 Telegyr TG800
[sc_general_interrogation, 1, en_US]
CASDU of the internal GI-request

During startup, the firmware generates an assignment between CASDU and TG800 station number.
If up to 2 CASDUs are assigned to one TG800 station number, then the internal GI request (TI = 100) is always
executed selectively, otherwise the GI request is always addressed "broadcast" (CASDU = 0xFFFF). Every
received GI instruction is always converted to the SICAM A8000 system message General Interrogation
Request.
Processing
If a GI instruction (indications and/or measured values) is received without address field extension, the entire
process image is always transmitted; also from other connected stations (firmware acts as data concentrator).
If a GI instruction is received with address field extension, then only those corresponding GI requests of that
TG800 station addressed in the address field extension are generated.
The GI data arriving on the firmware is monitored for change and only forwarded to the TG800 central station
upon change.
GI instruction with address field extension

As of firmware revision 03, a GI instruction with address field extension (selective TG800 station) is responded
from the firmware-internal process image. However, only information of the corresponding TG800 station,
defined by the address field extension, is transmitted.
Transmission of data for general interrogation

The general interrogation is always processed after the received TG800 instructions (indications/measured
values).

DC8-037-2, Edition 11.2020
12.12 Telegyr TG800
The transmission generally takes place according to increasing TG800 address, whereby hardware addresses
are transmitted before software addresses. Beginning and end of the general interrogation are identified by
the system indication General interrogation in progress (software address = 33).
NOTE
i Spontaneous events are always transmitted with higher priority to the central station.
The firmware answers a GI-instruction for indications as follows:
• All process indications (ascending according to TG800 address)
• All system indications or collective system indications (increasing TG800 station number)
If a GI instruction is initiated for indications and measured values simultaneously, then indications are
processed with higher priority.

The TG800 master (control center or frontend) periodically (period = 1 or 10 minutes) performs a time
synchronization of the remote terminal unit. The time synchronization (IAC = 135) is always transmitted as a
"broadcast" message. The master always sends the local time, this means, also daylight-saving / standard time.
The time synchronization message contains the current time at the moment of the first character (= start bit of
the UART).
Since the time synchronization message has a fixed length (= 16 bytes), the firmware corrects the message
duration automatically.
[sc_time_synchronization, 1, en_US]
Additionally, another correction-time time synchronization can be parameterized, in order to compensate

delays of transmission equipment.
By means of parameter setting it is also defined, whether the time synchronization message received is used
for the time synchronization of the remote terminal unit (substation can also be synchronized with local
DCF77/GPS or NTP).
NOTE
i The TG800 time synchronization message does not contain any daylight-saving / standard time identifier;
this is added by the firmware automatically for the time synchronization of the automation unit.
12.12.6.10 Counter Value (CV) Requests in TG800

The following requests are defined in the TG800 system:
CV request F (Freeze without reset without transmission) IAC = 140
CV request FR (Freeze with reset without transmission) IAC = 141
CV request FT (Freeze without reset with transmission) IAC = 142
CV request FRT (Freeze with reset with transmission) IAC = 143
CV request T (transmission of the saved counts) IAC = 144
Within the request itself, there are another 8 request groups (G0 to G7) defined.
Request group set:

DC8-037-2, Edition 11.2020
12.12 Telegyr TG800
The request group set consists of one set of 8 bits, corresponding to 8 requested groups. Several bits can be
set in the request group set. A set bit states that the corresponding count group (or station group) is affected
by the request.
The conversion of the counter value request from TG800 to SICAM A8000 is performed via a parameter-
settable assignment. There are 5 possible assignments.
TG800 SICAM A8000
Request type Request group IEC-FRZ1 IEC-RQT
F, FR, FT, FRT, T Group 0 to group 7 0 to 3 0 to 63
IEC-FRZ = freezing identifier: 0 ... request (no freeze or reset)

1 ... freeze counter without reset
2 ... freeze counter with reset
3 ... reset counter
IEC-RQT = inquiry identifier: 0 ... no counter interrogation
1 ... counter interrogation group 1
5 ... general counter interrogation
6 to 31 reserved – compatible range
32 to 63 reserved – private range
NOTE
i • Since according to IEC 60870-5-101 there is no simultaneous “freezing + transmitting”, for this func-
tion (CV request FT, FRT) two entries must be parameterized: first “freeze” and then “request”.
• The SICAM A8000 system message Counter Interrogation is always addressed "broadcast"
(CASDU1 = CASDU2 = 255).
• TG800 counter value requests with address field expansion are discarded without any error message.
[sc_TG800_counter_value_requests, 1, en_US]
12.12.6.11 Handling of Process Data with Time Tag

In the TG800 protocol, indications with time tag (IAC = 2) are transmitted in the format “Hours : Minutes :
Seconds . Milliseconds”. Counter values are also transmitted with time tag in the format “Day : Hours :
Minutes”.

DC8-037-2, Edition 11.2020
12.12 Telegyr TG800
In the SICAM A8000 system, all data formats are defined with date + time; during the conversion to the TG800
format, the internal time format must be reduced.
Indications with time tag (IAC = 2) can be transmitted with or without coarse time.
All of the following indications with the same hour and the same minute are now only transmitted with fine
time (= seconds, milliseconds).
NOTE
i The firmware always transmits all indications with coarse time!
• Spontaneous indication transmissions due to an NT bit change (NT = not topical) are always sent without
time tag (IAC = 1).
• Indications with a non-set time (year < 2006 or year > 2080) are also always sent without time tag (IAC =
1).
12.12.6.12 Measured Values in Monitoring Direction
General
Measured values are transmitted (without time) in the TG800 protocol with IAC = 3.
TG800 Measured Value Format
[sc_TG800_measured_value_format_monitoring_direction, 1, en_US]
I .......Invalid
VZ ... sign
In the TG800 measured value format, the representation of the measured values is possible in the range –
32768 to + 32767, whereby always only the even-numbered values are valid. If valid values are converted (NT
= 0, IV = 0 and OV = 0), then the least significant bit in the TG800 format is always set to "0".
The following type identifications can be converted to TG800 measured values:
• Step position information <TI:=32>
• Measured value – normalized <TI:=34>
• Measured value – scaled <TI:=35>
• Measured value – short float <TI:=36>

The data point quality identifier NT (not topical), IV (invalid) and OV (overflow) are converted to the I bit
(TG800).
For step position information <TI:=32>, in addition the moving contact information VTI is converted to the I
bit.
A linear adaptation can be parameterized for each measured value. The linear adaptation is defined through
the following parameters:

DC8-037-2, Edition 11.2020
12.12 Telegyr TG800
X_0% Value adaptation:

Lower limit of the used measuring range in the external (protocol-specific) format.
The corresponding internal value is defined at Y_0%.
Upper limit of the used measuring range in the external (protocol-specific) format.
Y_0% Value adaptation:
Lower limit of the used measuring range in the selected internal format.
The internal format is defined at TI (type identification).
The corresponding external value is defined at X_0%.
Upper limit of the used measuring range in the selected internal format.
As only one measured value format is defined in the TG800 protocol, the parameters X_0% and X_100% are
defined in the range:
X_0%, X_100% = –32768 to +32767
Also valid: Y_100% > Y_0%
The parameters Y_0% and Y_100% are defined by the type identification.
Measured value - normalized: Value range: –1 to +1
Measured value - scaled: Value range: –32768 to +32767
Measured value - short floating No check
point:
Step position information: Value range: –64 to +63
The linear adaptation is activated, if Y_0% or Y_100% is parameterized unequal to "0".
Value Conversion without Linear Adaptation

– SICAM A8000 value range: –64 to +63
Value TG800 = ValueSICAM A8000 ⋅ 2

Value TG800 = Value SICAM A8000 ⋅ 32000
Value SICAM A8000 = 0.76543 → Value TG800 = 24493
Value transmitted = 24492 (0x5FAC)

Value TG800 = Value SICAM A8000

– SICAM A8000 value range: –3.4 ⋅ 1038 to +3.4 ⋅ 1038
A conversion from real format to a binary value takes place. If the SICAM A8000 value is > 32766 or < –32768,
then the I bit is set as well as the value itself set to 32767 or –32768 respectively.

DC8-037-2, Edition 11.2020
12.12 Telegyr TG800
Value Conversion with Linear Adaptation

The adaptation is activated, if Y_0% or Y_100% are parameterized to unequal "0".
Value TG800 = k ⋅ Value SICAM A8000 + d
whereby
k = (X100 – X0) / (Y100 – Y0)
d = X0 – k ⋅ Y0
NOTE
i Value SICAM A8000 < Y0 → Value TG800 = X0 and I = 1

Value SICAM A8000 > Y100 → Value TG800 = X100 and I = 1
Bipolar measured values
[sc_bipolar_measured_value, 1, en_US]
12.12.6.13 Setpoint values
General
Setpoint values are transmitted in the TG800 protocol with IAC = 131.
Value range: -32768 to +32767

DC8-037-2, Edition 11.2020
12.12 Telegyr TG800
The TG800 setpoint format can be converted to 3 type identifications:
• Setpoint command – normalized <TI:=48>: Value range: –1 to +1
• Setpoint command – scaled <TI:=49>: Value range: –32768 to +32767
• Setpoint command – short float <TI:=50>: Value range: –3.4 ⋅ 1038 to +3.4 ⋅ 1038
A linear adaptation can be parameterized for each setpoint. The linear adaptation is determined by the
following parameters:
As only one setpoint format is defined in the TG800 protocol, the parameters X_0% and X_100% are defined
in the range:
X_0%, X_100% = -32768 to +32767
Also valid: X_100% > X_0%
The parameters Y_0% and Y_100% are determined by the type identification used internally.
Setpoint value - normalized: Value range: –1 to +1
Setpoint value - scaled: Value range: –32768 to +32767
Setpoint value - short floating No check
point:
The linear adaptation is activated, if X_0% or X_100% is parameterized unequal to "0".
• Setpoint command - normalized <TI:=48>

–32000 to setpoint value to +32000
Value SICAM A8000 = Value TG800 / 32000
Setpoint value < –32000 or setpoint value > +32000
→ Setpoint value is discarded with the error message Format conversion error in receive
direction.
• Setpoint command - scaled <TI:=49>
Value SICAM A8000 = Value TG800
• Setpoint command – short float <TI:=50>

The binary value received is converted to a real number.

DC8-037-2, Edition 11.2020
12.12 Telegyr TG800

The adaptation is activated, if X_0% or X_100% is parameterized unequal to "0".
Value SICAM A8000 = k ⋅ Value TG800 + d
whereby
k = (Y100 – Y0) / (X100 – X0)
d = Y0 – k ⋅ X0
If the setpoint value cannot be adapted (setpoint value < X_0% or setpoint value > X_100%), then the setpoint
value is discarded with the error message Format conversion error in receive direction.
Bipolar setpoint value
[sc_bipolar_setpoint, 1, en_US]
12.12.6.14 Measured Values in Command Direction
General
Measured values in command direction are transmitted on TG800 protocol spontanous with IAC = 3 and at
general interrogation with IAC 16.

DC8-037-2, Edition 11.2020
12.12 Telegyr TG800
TG800 Measured Value Format
[sc_TG800_measured_value_format_command_direction, 1, en_US]
I ... Invalid
VZ ... sign
In the TG800 measured value format, the representation of the measured values is possible in the range –
32768 to +32767, whereby always only the even-numbered values are valid. If valid values are transmitted,
then the least significant bit in the TG800 format is always set to "0". The I bit (invalid) of TG800 is converted
to the data point qualifier NT (not topical).
The TG800 measured value can be converted to 3 type identifications:
Measured value – normalized Value range: –1 to +1
<TI:=34>
Measured value – scaled <TI:=35> Value range: –32768 to +32767
Measured value – short float Value range: –3.4 ⋅ 1038 to +3.4 ⋅ 1038
<TI:=36>
A linear adaptation can be parameterized for each measured value. The linear adaptation is determined by the
following parameters:
As only one format of measured values defined in the TG800 protocol, the parameters X_0% and X_100% are
defined in the range:
X_0%, X_100% = –32768 to +32767
Also valid: X_100% > X_0%

Measured value - normalized Value range: –1 to +1
<TI:=34>
Measured value - scaled <TI:=35> Value range: –32768 to +32767
Measured value - short floating No check
point <TI:=36>

DC8-037-2, Edition 11.2020
12.12 Telegyr TG800

–32000 to measured value to +32000
Value SICAM A8000 = Value TG800 / 32000
Value TG800 < –32000 => Value SICAM A8000 = –1, OV = 1
Value TG800 > –32000 => Value SICAM A8000 = 1, OV = 1
• Measured value - scaled <TI:=35>


The binary value received is converted to a real number.

The adaptation is activated, if X_0% or X_100% is parameterized unequal to "0".
Value SICAM A8000 = k ⋅ Value TG800 + d
whereby
k = (Y100 – Y0) / (X100 – X0)
d = Y0 – k ⋅ X0
NOTE
i Value TG800 < X0 → Value SICAM A8000 = Y0, OV = 1

Value TG800 > X100 → Value SICAM A8000 = Y100, OV = 1

DC8-037-2, Edition 11.2020
12.12 Telegyr TG800
Bipolar measured value
[sc_bipolar_measured_value_1, 1, en_US]
12.12.6.15 TELEGYR 800 Radio Spontaneous Mode
General
If no leased line for TG800 communication (in polling mode) between control station and remote terminal
unit (substation) is available, radio communication can be used for TG800 communication.
The TG800 protocol has many identical functions in the polling mode and radio spontaneous mode. The
special features of the radio spontaneous mode are described in the following section.
The radio spontaneous mode is a special mode of communication, whereas the radio is used for voice trans-
mission as well for TG800 communication. A link connection is established between two stations for a limited
duration (transmission block, max. 20 seconds).
The link connection can be established by any system (master or slave), but the communication structure is
still hierarchically. That means, a link connection can only be established between a primary station and a
secondary station, but never between two secondary stations. For certain data transmissions, the primary
station can establish a connection with all stations simultaneously.
Architecture Function System
Primary station TG800 master Control center
Secondary station TG800 slave Substation

DC8-037-2, Edition 11.2020
12.12 Telegyr TG800
Modem
In the radio spontaneous mode only the LAVANCHY modem 1754 is used. This modem includes the radio
(high frequency channel) and also the WT channel (frequency shift keying).
[sc_modem_LAVANCHY, 1, en_US]
• The signal RTS SICAM A8000 is used to switch on the radio (PPT) and the WT channel (FSK).
• The signal SQ (Squelch, HF-radio is ON) indicates the use of radio communication (TG800 communica-
tion or voice-transmission is active).
NOTE
i • The DCD signal (from WT channel) must be used in the TG800-radio spontaneous mode.
• If no SQ signal is available, DCD and DSR must be linked together (on the communication board).
Link Connection
A link connection may only be started if the radio channel is not used for at leased 2 seconds. This condition
avoids the interruption of communication sequences (TG800 or voice), if the request-response timeout
(switch over duration) is less than 2 seconds.
The link connection starts with setting on the RTS signal. The transmitter of the radio and the WT channel
(FSK) is switched on. The following transmission delay (set up time) is used for correct detection of the start
character (of the following message), if faulty characters are generated by switching on the WT channel.
The link connection occurs always with the radio call message, which can be sent by the primary station or any
secondary station. After the connection is established the communication between master and slave is done
with the standard TG800-Polling sequence (unbalanced master/slave communication).
All stations which are not addressed by the radio call message or stations which do not understand this
message, discard the received message and disable the receiver until the radio is free (radio pause > 2 s).
• The primary station retransmits the radio call message as long as response is received (= connection is
established), a parameterizeable timeout or the max. transmission block elapses. If the radio call
messages are not responded successfully, the Link is disconnected and the substation is marked as failed.
• The secondary station retransmits the radio call message as long as a response is received (= connection
is established), or if the number of retries of link connection expires. If the radio call messages are not
responded successfully, the link is disconnected (communication failure is set). In this state, the secon-
dary station only waits on a radio call message from the primary station.
Link connection with collision

If radio call messages are sent simultaneously from different stations (collision) there will be no answer from
the requested situation, because the received message is faulty. This stations will retransmit the radio call
message as soon as they detect that radio communication is idle (idle time > 2 s). To avoid collisions again,

DC8-037-2, Edition 11.2020
12.12 Telegyr TG800
each station increments the “radio idle time” by an abnormal time (random), the abnormal time in the primary
station is always smaller than in the secondary station.
Radio call message with collision
[sc_link_connection_with_collision, 1, en_US]
FA1 Radio call message with collision

FA2 Successful retry of the radio call message (without collision)
FA3 Delayed retry of radio call message (radio is used by station A); this radio call message is sent after
the dialogue of station A is finished.
tub Monitoring time “radio is idle”
• at leased 2 s
tubz Monitoring time “radio is idle” for retransmission
• 2.2 to 3.1 s for primary station

• 3.2 to 9.5 s for secondary station
• Random extension in time steps of 100 ms
tu Switch over time < 1500 ms
Switch over time between request and response within a radio communication
Ü1 Message block in monitoring direction
S1 Message block in command direction
Link Disconnection
Each link connection is disconnected by the primary station while the primary station does not continue with
requests (= stop polling cycle) after the recept of responses.
Cause of disconnection:
• The transmission block expires (defined by telecom office, default = 20 s)
• The secondary station responses the requests of the primary station with acknowledge (= no process data
available)
The secondary station detects the disconnection while it is not requested within 1500 ms by the primary
station.
Function Check
The primary station polls the secondary stations periodically for function checks and determines if all stations
are still working. If a secondary station will not respond to the request it is marked as failed.
Broadcasting – Command to All Stations (RTUs)

Broadcasting defines the transmission of messages to all stations.
The primary station executes the link connection and disconnection.
The dialogue starts with a radio short block call message with target address to all, followed by a long block
message that contains the user information (example: time synchronization). Afterwards the connection is
disconnected.

DC8-037-2, Edition 11.2020
12.12 Telegyr TG800
Broadcast command (example: time synchronization)
[sc_broadcast_command, 1, en_US]
FA-SA Radio call message to all stations in control direction (target station = 1023, COM# = 255)
S1Z Long block to all stations (COM# = 255); example: time synchronization (IAC = 135)
tub Monitoring time “radio is idle”
• At least 2 s
The master station transmits periodically the time to all substations. The time message is not acknowledged by
any receiver. The period can be set by parameter in the master station.
Radio Call Message
TG800 message format (incl. message header)
[sc_radio_call_message, 1, en_US]
Concession number 8 digit 0 to 9

Radio group 0 to 255
Source-stations TG800 station number (0 to 1020) of the transmitter (1023 … broadcast)
number The substation puts always BA = 1 (F-field = Ox80)
Note:
The firmware checks always the source station number = TG800 station number of
the central station.

DC8-037-2, Edition 11.2020
12.12 Telegyr TG800
Target-stations TG800 station number (0 to 1020) of the receiver (= target)

number
COM# TG800-COM# of the target, if master transmits the message
TG800-COM# of the source, if slave transmits the message
Function field F-field according TG800 specification (refer to section Layout of the F-Field in
Command Direction, Page 1451) the secondary stations always set BA = 1 (F-field =
0x80)
Description of the Normal Communication

After the link connection is established the data exchange is done with polling; the primary station transmit
requests (with or without information) to the secondary station and the secondary station responds the
request with or without information.
Link connection by master (command)

DC8-037-2, Edition 11.2020
12.12 Telegyr TG800
[sc_link_connection_master, 1, en_US]
1 Long block with own station number (IAC = 25).

If the service “Reset VE” or “Status VE” is used in the radio call message, the secondary station will
respond with a short block (not single character 0x E5!).
tVBG Max. connection duration = transmission block
Normally, the primary station will not terminate the dialog after the transmission of the command immedi-
ately. It will wait a certain time for the return information of the command by polling the substation.
Evaluation of the radio call message:
• Check the concession number and radio group
• TG800 target station number = own station number or 1023 (broadcast)
• TG800 source station number = TG800 station number of the control center

DC8-037-2, Edition 11.2020
12.12 Telegyr TG800
• COM number = own COM-number or 255 (broadcast)
• F field: RB = 1 (message from the master)
When the evaluation fields a positive result, the firmware will answer with a long block own station number
(IAC = 25) or with a short block (dependent of service in the radio call message). If one condition is not
performed, the received message is discarded, the receiver disabled and only “squelch” (DSR = 0, radio is idle)
is observed.
Squelch detection
The idle state of DSR signal (DSR = "0") is observed (> 2 s). If radio is idle is detected, the receiver is enabled at
next positive edge of DCD (after receiver disable time is expired). If a valid message is received, it is forwarded
to the evaluation, described above. If an error is detected (example: voice) and the connection is not estab-
lished, the receiver is disabled again and only squelch is observed.
Link connection by the slave (caused by an event)
[sc_link_connection_slave, 1, en_US]
tVBG Max. connection duration = transmission block

tu Switch-over time
Switch-over time between request and response within a radio dialog.

DC8-037-2, Edition 11.2020
12.12 Telegyr TG800
After the radio call message has been transmitted, the secondary station expects a request (poll request or
information) within 1500 ms from the primary station with the corresponding COM-number. If the timeout
expires, the secondary station must transmit its radio call message, because the primary station has not recog-
nized the request (refer to section Link connection with collision, Page 1480).
If the primary station receives the radio call message correctly, the slave is requested until
• the transmission block expires
• the secondary station responds only with acknowledge (no information)
NOTE
i The firmware initiates a link connection at each event in the automation unit, independently the event is
defined in the SIP-address message conversion. If this effect is not acceptable, the “selective data flow”
must be used.
12.12.7 Message Conversion In Transmit Direction (SICAM A8000 → TG800)
The address in the following information blocks must be input for the HW addresses in the “short, without
station number” version and for the SW addresses in the “no station number” version. However, all address
blocks defined in section 12.12.5.6 Addressing of the Information are available.
The length does not need to be specified in bytes in the following information blocks. The block length is
defined in the block by the IAC and potentially by further specifying the number of pieces of information.
12.12.7.1 Indications (Single/Double-Point Information)

In the TG800 system, spontaneous indication changes are always transmitted in single object format without
time tag (IAC = 1) or with time tag (IAC = 2).
NOTE
i It is not permitted to transmit an indication change with both indication formats (with and without time =
2 data streams). The message format to be used is selectable for each information object.
The indication type (single or double-point information) is transmitted in spontaneous format; in the GI
format, this is not included.
For double-point information, the point number is always used in steps of 2 (0, 2, 4, ...).
Indication without Time Tag

TG800 message format: short hardware address without station number
[sc_indication_without_time_tag, 1, en_US]
E=0 Short address format

S=0 No station number in information

DC8-037-2, Edition 11.2020
12.12 Telegyr TG800
Slh Slot No
high
I Invalid
bit
R Report bit (= 1 ... indication after command, cause of transmission = 11)
V Signalin (= 1 VKM four-contact indication = double-point information)
g type (= 0 ZKM two-contact indication = single-point information)
S State ZKM: 01 = OFF 10 = ON
VKM: 01 = OFF 10 = ON
00 or 11 fault
Indication with Time Tag

[sc_indication_with_time_tag, 1, en_US]

Slh Slot no.
high
I Invalid
bit
R Report bit
(= 1 .. indication after command; cause of transmission = 11)
V Report (= 1 VKM four-contact indication = double-point information)
bit (= 0 ZKM two-contact indication = single-point information)
VKM: 01 = OFF 10 = ON
00 or 11 fault
G Full time bit "1", because only this format supported.
Time error bits:

F ... Fault (possibly totally wrong) – always "0"
U ... inaccurate (not quite synchronous) – f (IV bit of the time tag)
O ... without milliseconds, not supported – always "0"

DC8-037-2, Edition 11.2020
12.12 Telegyr TG800
GI Indications
According to a GI instruction for indications (IAC = 160) all indications are transmitted in blocks
by the substation. All indication groups are transmitted without time.
TG800 message format – short hardware address without station number
[sc_GI_indications, 1, en_US]
MG Indication group
Length Number of indication groups ⋅2 + 4
Qty.MG Number of 1-bits in V-set (1 to 8)
Slh Slot no. high
V Set of the existing indication groups (V) in the information part
S State of the bit (0/1)
I Invalid bit to the of the above state (1 = invalid)
HW-Address Valid for indication group 0 (= bit 0 in V set). The addresses (point number) of the following
indication groups are calculated by increments of 8 to the previous identification (= address),
all per V bit.

DC8-037-2, Edition 11.2020
12.12 Telegyr TG800
Example:
Indication group format with byte 1 and 3 (bits 8 to 15 and 24 to 31).
[sc_indication_group_format_with_byte, 1, en_US]
Address Conversion SICAM A8000 → TG800

The address conversion is parameterized with the SICAM TOOLBOX II, OPM II. For this, in the SIP message
address conversion the detailed routing type firmware / Transmit detailed routing is provided
with the following entries.
Parameter Bedeutung
CASDU1 5-stage freely parameter-settable SICAM A8000 address
CASDU2 0 to 255
IOA1
IOA2
IOA3

IEC_quali- Command output time to be added possible:
fier_of_command
• No definiton
• Short
• Long
Note: Qualifier of command is irrelevant for indications.
TG800-Stat-No. Station number (target):
0 to 1020
TG800-IAC Information type:
• Indication without time tag (IAC = 1)

• Indication with time tag (IAC = 2)

DC8-037-2, Edition 11.2020
12.12 Telegyr TG800
Parameter Bedeutung
TG800-Addr-Type Address type:
• 0 ... hardware address

• 1 ... software address
TG800-Cubicle-No. Cubicle number:
0 to 3 (for software address always "0")
TG800-Chassis-No. Chassis number:
TG800-Slot-No. Slot number in chassis:
TG800-Point.No. Point number:
• 0 to 255 for hardware address

• 0 to 32767 for software address
Attention: For double-point information, the point number may only be parame-
terized in even steps of 2 (0, 2, 4, 6, ...).
NOTE
i The parameters X_0%, X_100%, Y_0% and Y_100% must be left on their default value .
• I (invalid) – TG800 =
NT (not topical) or
IV (invalid) or
BL (blocked)
• R (Report bit) – TG800 =

"1" … Cause of transmission = 11 (return information caused by a remote command)

DC8-037-2, Edition 11.2020
12.12 Telegyr TG800
[sc_address_conversion, 1, en_US]
12.12.7.2 Measured Values
Measured Value – Spontaneous
[sc_measured_value_on_Event, 1, en_US]

Slh Slot No high
State -32000 to +32000, incl. I-bit (= 16 bit dual component)
I Invalid bit
Here it indeed concerns a 16-bit value, however the bit 0 (LSB) is not transmitted, i.e. only even values can be
transmitted.

DC8-037-2, Edition 11.2020
12.12 Telegyr TG800
GA Measured Values (analog) with Hardware Address

[sc_GA_measured_values_with_hardware_address, 1, en_US]
Length Number of measured values ⋅ 2 + 4

Qty.MV Number of 1-bits in the V-set (1 to 8)
Slh Slot no. high
V Set of the existing measured values (V) in the information part
HW-Address Valid for measured value 0 (= bit 0 in V set). The addresses of the following measured values
are calculated by increments of 1 (for analog measured values) to the previous identification
(= address), all per V bit.
State -32000 to +32000, incl. I bit (= 16 bit dual component)
I Invalid bit for MV state (1 = invalid)

DC8-037-2, Edition 11.2020
12.12 Telegyr TG800
Example:
Group format with the analog measured values 10, 13 and 14
[sc_group_format_analog_measured_values, 1, en_US]

address conversion the detailed routing type firmware / Transmit detailed routing is provided with the
following entries.
Parameter Meaning
CASDU2 0 to 255
IOA1
IOA2
IOA3
• Transformer tap position information <TI:=32>

• Measured value 15 bit + sign normalized <TI:=34>
• Measured value 15 bit + sign scaled <TI:= 35>
• Measured value short floating point <TI:=36>
IEC_quali- • No
fier_of_command
• Short
• Long
0 to 1020
Measured value

DC8-037-2, Edition 11.2020
12.12 Telegyr TG800
Parameter Meaning


Attention: For double commands and regulating step commands, the point
number may only be parameterized in even steps of 2 (0, 2, 4, ...).
Lower limit of the used measuring range in the external (protocol-specific)
format. The corresponding internal value is defined at Y_0%.
-32768 to +32767
Upper limit of the used measuring range in the external (protocol-specific)
-32768 to +32767
Lower limit of the used measuring range in the selected internal format. The
internal format is defined at TI (type identification). The corresponding external
value is defined at X_0%.
• <TI:=32>: -64 to 63
• <TI:=34>: -1 to +1
• <TI:=35>: -32768 to +32767
• <TI:=36>: no check
Upper limit of the used measuring range in the selected internal format. The
• <TI:=32>: -64 to +63

• <TI:=34>: -1 to +1
• <TI:=35>: -32768 to +32767
I (Invalid) – TG800 NT (not topical) or

IV (invalid) or
OV (overflow) or
VTI (moving contact information at transformer taps)
Conversion of measured value: refer to section 12.12.6.12 Measured Values in Monitoring Direction.

DC8-037-2, Edition 11.2020
12.12 Telegyr TG800
[sc_conversion_measured_value, 1, en_US]
12.12.7.3 Counter Values, Requested and Archived
Counter Values with Hardware Address

Single current counter values (CV) – IAC = 10
Double current counter values (CV) – IAC = 11

DC8-037-2, Edition 11.2020
12.12 Telegyr TG800
[sc_counter_values_with_hardware_address, 1, en_US]
Length 6 + (Qty.CV ⋅ 4)
Qty.C Number of 1-bits in the V-set (1 to 8)
Slh Slot no. high
V Set of the existing CV (V) in the information part
HW-Address Valid for counter value (CV) 0 (= bit 0 in V-set). The addresses of the following counter values
are calculated by increments of 1 (for single-current) or 2 (for double-current CV) to the
previous identification (= address), all per V-bit.
Each double-current CV occupies 2 input points. The hardware address is valid for the input
point with the lower address.
Day ... Min Request time (time end measuring period)
CV Counter value (0 to 9999999)
ZUE Counter value overflow (over 9.999.999)
SNI New initialization of station

DC8-037-2, Edition 11.2020
12.12 Telegyr TG800
ZNG Counter value never set

FZI Fault at Counter input
Per above-mentioned group format only single current counter values or double current counter values may
be included.
Example:
Group format for single current counter values with the hardware address 24, 28, 29
[sc_group_format_single_current_counter_values, 1, en_US]
Group format for double current counter values with the hardware address 16, 18, 22
[sc_group_format_double_current_counter_values, 1, en_US]

address conversion the detailed routing type firmware / Transmit detailed routing is provided with the
following entries.
Parameter Meaning
CASDU2 0 to 255
IOA1
IOA2
IOA3
Counter value 31 bit + sign with sequence number <TI:=37>
IEC_quali- • No
fier_of_command
• Short
• Long
0 to 1020

DC8-037-2, Edition 11.2020
12.12 Telegyr TG800
Parameter Meaning
• Count single-current
• Count double-current


NOTE
i The parameters X_0%, X_100%, Y_0% and Y_100% must be left on their default value (firmware is
checking).
Counter value conversion
• The range of values must already be adjusted to the area of 0 to 9999999 (7 decades BCD) at the source
(recording). A counter value overflow treatment is not done by the firmware.
• Negative counter values (IEC 60870 format) are rejected with the error message format conversion
in transmit direction.
• Is the time stamp invalid (smaller 1.1.2006 or greater 1.1.1990), the time information is set to "0" in the
TG800 format.
• ZUE (TG800) = CY (SICAM A8000)
• ZNG (TG800) = NOT CA (SICAM A8000)
• FZI (TG800) = IV (SICAM A8000)
• SNI always "0"
[sc_counter_value_conversion, 1, en_US]

DC8-037-2, Edition 11.2020
12.12 Telegyr TG800
Block with System Indications

The TG800 station transmits this data block after it has been requested by the master station by means of GI
instruction system indication block (IAC = 162), however only if collective system indications are
defined.
TG800 message format:
[sc_block_with_system_indications, 1, en_US]
MG Indication group
Length Nnumber of indication groups ⋅ 2 + 5
E=1 Long address format
SW = 1 Software address (source of information)
Point No Always 0!
E Event-bit, indicates whether the state has switched to ON at any time since the last acknowl-
edgement (refer to IAC = 163).
HW-Address Valid for indication group 0 (= bit 0 in V set). The addresses (point number) of the following
indication groups are calculated by increments of 8 to each previous identification (= address),
all per V bit.

DC8-037-2, Edition 11.2020
12.12 Telegyr TG800
12.12.7.4 Own Station Number (and GI Request)

TG800 message format
[sc_own_station_number, 1, en_US]
SG = 1: send GI from the ZS (is not supported, always "0")

Length = 4 bytes
The firmware only transmits this message on request of the master station.
GI Instruction to the Master
With this instruction the substation can request indications and measured values from the master station.
The GI instruction to the master is only transmitted if indications resp. measured values are defined in the SIP-
Message address conversion in receive direction.
[sc_GI_instruction_master, 1, en_US]
GI instruction to the master – for indications: IAC = 158

GI instruction to the master – for measurands IAC = 159
Source station number = always own TG800 station number
12.12.8 Message Conversion In Receive Direction (SICAM A8000 ← TG800)
The hardware addresses in the following illustrated information blocks are entered either in the version “long,
with station number” or “short, without station number”. However, if required, instead of “short, without
station number”, one of the other available address formats can also be used. For commands and setpoints,
for reasons of information security and processing, only the formats shown below are possible. For most types
of information, the information length is determined with the IAC. For the other information types, the length
is visible from a special entry.

DC8-037-2, Edition 11.2020
12.12 Telegyr TG800
NOTE
i The TG800 address, consisting of Station No, Cabinet No, Chassis No, Slot No and Point No, must be unique
for all data points defined in the SIP message address conversion of the OPM II, regardless of the informa-
tion type (= IAC).
12.12.8.1 Pulse and Permanent Commands
Pulse/Permanent Commands with Hardware Address

TG800 message Format:
Pulse command: IAC = 128
Permanent command: IAC = 129
[sc_pulse_permanent_commands_with_hardware_adress, 1, en_US]

S=1 Station number in information (E = S = 1 is fixed!)
CuH Cubicle no. high
CuL Cubicle no. low
SW = 0 Hardware address (command to hardware)
CRC Cyclic redundancy check; code saving through inversion of 16 bit CRC to IEC:
(216 + 214 + 212 + 211 + 29 + 28 + 27 + 24 + 21 + 1)
via Info 0 to 4 whereby MSB of Info 0 is processed first.
The code security with the 16 bit CRC to IEC TC57 for the format FT3 results in a Hamming distance of 8. Only
one command per TG800 message is allowed, otherwise the security would be decreased.
The target station no. = 1023 is used for broadcast commands.
Pulse/Permanent Commands with Software Address

Pulse command: IAC = 128
Permanent command: IAC = 129

DC8-037-2, Edition 11.2020
12.12 Telegyr TG800
[sc_pulse_permanent_commands_with_software_adress, 1, en_US]

SW = 1 Software address (command to LAF)
(216 + 214 + 212 + 211 + 29 + 28 + 27 + 24 + 21 + 1)
one command per TG800 message is allowed, otherwise the security would be decreased.
The target station no. = 1023 is used for broadcast commands.
Stop Permanent Command

This data format is sent to the remote station, where the permanent command is activated. Stop permanent
command causes the immediate deactivation of the permanent command. Only one permanent command
may be activated per communication link.
TG800 does not differ between hardware and software.
[sc_stop_permanent_command, 1, en_US]
Stop Permanent command (IAC = 130) is converted to a double command <TI:=46> or regulating step
command <TI:=47> with state of command = "0" (not defined), assumed a permanent command (IAC = 129)
was received before.
Address Conversion TG800 → SICAM A8000

address conversion the detailed routing type firmware / Rec_binary_information is provided with the
following entries.

DC8-037-2, Edition 11.2020
12.12 Telegyr TG800
Parameter Meaning
CASDU2 0 to 255
IOA1
IOA2
IOA3
• Single command <TI:=45>

• Double command <TI:=46>
• Regulating step command <TI:=47>
Permanent command can not be converted into single commands <TI:=45>
IEC_quali- • No
fier_of_command
• Short
• Long
0 to 1020
• Pulse command
• Permanent command


NOTE
i • All even point numbers (0, 2, 4 = ...) are converted to OFF commands (double commands) and LOWER
commands (regulating step command).
• Using the address field extension, the addressed TG800 station must be equal to the target station
number contained in the command message, otherwise the received message is rejected with the
error message fault format conversion in receive direction as well as the system indi-
cation Command/Setpoint rejected generated.

DC8-037-2, Edition 11.2020
12.12 Telegyr TG800
[sc_rec_binary_information, 1, en_US]
12.12.8.2 Setpoint
Setpoint with Hardware Address

[sc_setpoint_with_hardware_address, 1, en_US]

CuH Cubicle no. high
CuL Cubicle no. low
SW = 0 Hardware address (setpoint to hardware)

DC8-037-2, Edition 11.2020
12.12 Telegyr TG800
Value is 2 Bytes in size -32000 to +32000 (dual complement)

(216 + 214 + 212 + 211 + 29 + 28 + 27 + 24 + 21 + 1)
one setpoint per TG800 message is allowed otherwise the security would be decreased.
Setpoint with Software Address

[sc_setpoint_with_software_address, 1, en_US]

SW = 1 Software address (setpoint to LAF)
Value is 2 Bytes in size -32000 to +32000 (dual complement)
(216 + 214 + 212 + 211 + 29 + 28 + 27 + 24 + 21 + 1)
one setpoint per TG800 message is allowed, otherwise the security would be decreased.

address conversion the detailed routing type firmware / Rec_values is provided with the following entries.

DC8-037-2, Edition 11.2020
12.12 Telegyr TG800
Parameter Meaning
CASDU2 0 to 255
IOA1
IOA2
IOA3
• Setpoint value 15 Bit + sign normalized <TI:=48>

• Setpoint value 15 Bit + sign scaled <TI:=49>
• Setpoint value short floating point <TI:=50>
0 to 1020
Input value


-32768 to +32767
-32768 to +32767

DC8-037-2, Edition 11.2020
12.12 Telegyr TG800
Parameter Meaning
• <TI:=48>: -1 to +1
• <TI:=49>: -32768 to +32767
• <TI:=48>: -1 to +1
• <TI:=49>: -32768 to +32767
Conversion of set point: refer chap. 12.12.6.13 Setpoint values
[sc_conversion_setpoint, 1, en_US]
NOTE
i Using the address field extension, the addressed TG800 station must be equal to the target station number
contained in the setpoint message, otherwise the received message is rejected with the error message
fault format conversion in receive direction as well as the system message Command/
Setpoint rejected generated.

DC8-037-2, Edition 11.2020
12.12 Telegyr TG800
12.12.8.3 Time for Synchronization

TG800 Message Format:
[sc_time_synchronization1, 1, en_US]
MO = Month 1 to 12
Weekday 1 to 7 whereby Monday = 1
The time is always transmitted “broadcast” in a message. This message must not contain any other informa-
tion, since the remote terminal unit, adds a time correction, dependent of the message duration, to the
received time. This correction requires a fixed message length.
The time synchronization is periodically (most by minute) sent from the master station. The contained time is
the time at the time of the start bit of the 1st bytes (= protocol header start signal).
The message duration (= 16 bytes = 293 ms at 600 bit/s) is automatically added by the firmware.
12.12.8.4 GI-Instruction
[sc_GA_instruction, 1, en_US]
GI instruction for indications: IAC = 160

GI instruction for measured values: IAC = 161
Message Conversion TG800 → SICAM A8000

The firmware generates from the received TG800 message, independent whether indications and/or measure-
ments are requested, a GI request of the type “Image GI”.
The processing of the GI is carried out from the internal process image (refer to section 12.12.6.8 General
Interrogation).

DC8-037-2, Edition 11.2020
12.12 Telegyr TG800
12.12.8.5 Counter Value Request (Counter Interrogation)

[sc_counter_value_request, 1, en_US]
Request Group Set:

The request group set consists of a set of 8 bits, corresponding to 8 request groups. Several bits can be set in a
request group set. A set bit states, that the request concerns the corresponding count group.
NOTE
i The counter value request is always transmitted “broadcast” COM-Nr. = 255).
Possible Counter value-Requests:

Short designation Meaning IAC
Counter value-Request F Freeze without reset without transmission 140
Counter value-Request FR Freeze with reset without transmission 141
Counter value-Request FT Freeze without reset with transmission 142
Counter value-Request FRT Freeze with reset with transmission 143
Counter value-Request T Transmission of the C stored in COMO-RUPU in 144
NVRAM
Conversion from TG800 → SICAM A8000:

Refer to section 12.12.6.10 Counter Value (CV) Requests in TG800.
NOTE
i Counter value requests with address field extension are rejected without any error message.
12.12.8.6 GI-Anweisung Systemmeldungsblock

Instruction to the originator station for the transmission of the system indication block for the clarification of
the cause for a collective system indication change in the remote terminal unit.

DC8-037-2, Edition 11.2020
12.12 Telegyr TG800
[sc_GA_instruction_system_indication_block, 1, en_US]
Originator station No. = TG800 station no. of master station (= frontend/control system)
The firmware transmits the message block with system indications, IAC = 18 if the transmission
of the system indication is parameterized collective, refer to section Block with System Indications,
Page 1499.
If the transmission of the system indication is carried out single, then the received instruction is rejected
without error message.
This instruction is only used firmware internal; further the GI instruction is only then processed if the origi-
nator station number is equal to the TG800 station number master station (system technical param-
eter).
If the GI instruction system message block is received without address field extension, then the
system indications of the own TG800 station are transmitted; with address field extension the system indica-
tions of the TG800 station are transmitted addressed by the address field extension.
12.12.8.7 Acknowledgement System Indication Block

If the operator in the control station has taken notice of the events transmitted in the Block with system
indication (IAC = 18), then with this Acknowledgement system information block sent to
the remote terminal unit, he deletes the event-bits of all system indications there.
This acknowledgement is only accepted by the substation, if collective system indications are used.
[sc_acknowledgement_system_indication_block, 1, en_US]
If the transmission of the system indication is carried out single, then the received instruction is rejected
If the Acknowledgement System Indication Block is received without address field extension, then
the system indications of the own TG800 station are acknowledged (reset of the event bits); with address field
extension the system indication of the TG800 station are transmitted addressed by the address field extension.

DC8-037-2, Edition 11.2020
12.12 Telegyr TG800
12.12.8.8 Instruction: Send Own Station Number

[sc_instruction_send_own_station_number, 1, en_US]
Length = 2 bytes
This instruction is reasonable or possible only to stations connected directly. The firmware confirms this
instruction with the TG800 message own station number. This instruction is only used firmware internal.
If the instruction "Send own station number" is received with address field extension, then this is rejected
12.12.8.9 Indications in Command Direction

The TG800 system, spontaneous indication changes are always transmitted in single object format without
time tag (IAC = 1) or with time tag (IAC = 2), at general interrogation in blocked format without time tag (IAC
= 15).
NOTE
i It is not permitted to transform a spontaneous indication with both indication formats (with and without
time = 2 data streams).
The indication type (single or double-point information) is transmitted in spontaneous format; in the GI-
format, this is not included.
For double-point information, the point number is always used in steps of 2 (0, 2, 4, …)
NOTE
i The following indication formats do not differ from the format in monitoring direction, except that the
source station address always must be included.
The station number in the information address may not correspond to the target station.
Address field extension is not supported.

DC8-037-2, Edition 11.2020
12.12 Telegyr TG800
Indication without time tag

TG800 message format: short hardware address with station number
[sc_indication_without_time_tag1, 1, en_US]

S=1 Station number in information (originator, source)
Slh Slot no. high
I Invalid bit
R Report bit (= 1 ... indication after command, cause of transmission = 11)
V Signaling type (= 1 VKM four-contact indication = double-point information)
(= 0 ZKM two-contact indication = single-point information)
VKM: 01 = OFF 10 = ON
00 or 11 fault
Indication with Time Tag

[sc_indication_with_time_tag1, 1, en_US]


DC8-037-2, Edition 11.2020
12.12 Telegyr TG800
Slh Slot no. high

I Invalid bit
R Report bit (= 1 ... indication after command): not evaluated
V Signaling type (= 1 VKM four-contact indication = double-point information)
(= 0 ZKM two-contact indication = single-point information)
VKM: 01 = OFF 10 = ON
00 or 11 fault
G Full time bit = 1
Time error bits:

F ... Fault (possibly totally wrong): is converted to IV bit of time tag
U ... inaccurate (not quite synchroneous): not evaluated
O ... without milliseconds: not evaluated
GI Indications
According to a GI instruction for indications to the master station (IAC = 158) all indications are
transmitted in blocks. All indicated groups are transmitted without time tag.
[sc_GI_indications1, 1, en_US]
MG Indication group
Length Number of indication groups ⋅ 2 + 4

DC8-037-2, Edition 11.2020
12.12 Telegyr TG800
Slh Slot no. high

I Invalid bit to the of the above state (1 = invalid)
HW-Address Valid for indication group 0 (= bit 0 in V-set). The addresses (point number) of the following
indication groups are calculated by increments of 8 to the previous identification (= address),
all per V-bit.
Address Conversion TG800 → SICAM 1703

address conversion the detailed routing type firmware / Rec_binary_information is provided with the
following entries:
Parameter Meaning
CASDU2 0 to 255
IOA1
IOA2
IOA3

IEC_quali- Command output time to be added possible:
fier_of_command
• No definiton
• Short
• Long
Note: Qualifier of command is irrelevant for indications.
0 to 1020
Indication


Attention: For double-point information, the point number may only be parame-
terized in even steps of 2 (0, 2, 4, 6, ...).
SICAM A8000 – NT (not topical) = TG800 – I (invalid)

DC8-037-2, Edition 11.2020
12.12 Telegyr TG800
[sc_qualifier_command_indications, 1, en_US]
12.12.8.10 Measured Values in Command Direction
Measured Value – Spontaneous

[sc_measured_value_on_Event_command_direction, 1, en_US]

Slh Slot no. high
Status = -32000 to +32000 , incl. I-bit (= 16 bit dual component)
I Invalid bit
The format above illustrated does not differ from the format in monitoring direction, except that the source
station number is always included (station number in information object may not correspond to the traget
station).

DC8-037-2, Edition 11.2020
12.12 Telegyr TG800
GI – Measured Values (analog)

TG800 message format: short hardware address with station number:
[sc_GA_measured_values_analog, 1, en_US]
Length Number of measured values ⋅ 2 + 4

Qty.MV Number of 1-bits in the V-set (1 to 8)
Slh Slot no. high
V Set of the existing measured values (V) in the information part
HW- Valid for measured value 0 (= bit 0 in V-set). The addresses of the following measured values are
Address calculated by increments of 1 (for analog measured values) to the previous identification (=
address), all per V-bit.
State -32000 to +32000 , incl. I-bit (= 16 bit dual component)
I Invalid bit for MV state (1 = invalid)
The format above illustrated does not differ from the format in monitoring direction, except that the source
station number is always included (station number in information object may not correspond to the traget
station).

address conversion the detailed routing type firmware / Rec_values is provided with the following entries.

DC8-037-2, Edition 11.2020
12.12 Telegyr TG800
Parameter Meaning
CASDU2 0 to 255
IOA1
IOA2
IOA3

• Measured value 15 bit + sign scaled <TI:= 35>
• Measured value short floating point <TI:=36>
Permanent command can not be converted into single commands <TI:=45>
IEC_quali- • No
fier_of_command
• Short
• Long
0 to 1020
Measured value


-32768 to +32767
-32768 to +32767

DC8-037-2, Edition 11.2020
12.12 Telegyr TG800
Parameter Meaning
• <TI:=34>: -1 to +1
• <TI:=35>: -32768 to +32767
• <TI:=34>: -1 to +1
• <TI:=35>: -32768 to +32767
Conversion of measured value: refer to section 12.12.6.14 Measured Values in Command Direction.
Attention: Address field extension is not supported.
[sc_conversion_measured_value1, 1, en_US]
12.12.8.11 PBN Command

PBN is a process based name and constitutes a string of 12 ASCII characters. PBN commands does not differ
between hardware address and software address.

DC8-037-2, Edition 11.2020
12.12 Telegyr TG800
[sc_PBN_command, 1, en_US]
Originator Source station of command

station-No. Info 2 = high Byte, Info 3 = low Byte
PBN 12 ASCII-characters possible:
valid characters: A…Z, 0…9, $, _
Attribut-Set Bit 3 = 1 = Start
Attention: Attribute Set is not evaluated

DC8-037-2, Edition 11.2020
12.12 Telegyr TG800
Program 0 to 7, 1 = OFF, 2 = ON
number Attention: only program number = 1, 2 is accepted
CRC Cyclic redundancy check; codesaving through inversion of 16 bit CRC to IEC:
(216 + 214 + 212 + 211 + 29 + 28 + 27 + 24 + 21 + 1)
The code security (16 bit CRC) results in a Hamming distance of 8. Only one command per TG800 message is
allowed, otherwise the security would be decreased.
Address conversion TG800 → SICAM A8000

address conversion the detailed routing type firmware / Rec_PBN-command is provided with the following
entries.
Parameter Meaning
CASDU2 0 to 255
IOA1
IOA2
IOA3

If single command <TI:=45> is used, only program number "2" is accepted.
IEC_quali- • No
fier_of_command
• Short
• Long
0 to 1020
PBN command
PBN 12 ASCII characters possible:
A…Z, 0…9, $, _
NOTE
i • "Attribute Set" is not evaluated.
• Program number "1" and "2" is supported.
• No address field extension supported.

DC8-037-2, Edition 11.2020
12.12 Telegyr TG800
[sc_rec_PBN_command, 1, en_US]
12.12.9 System Indications and Collective System Indications
System indications
No. Meaning
0 System initialised
1 Global alarm critical
2 Global alarm noncritical
3 Insufficient RAM
4 HW missing or faulty
5 Parameter error
6 Off-line
7 Remote term. line down
8 Digital input HW error
9 Analogue input HW error
10 Digital output HW error
11 Analogue output HW error
12 Command output HW error
13
14 No supply voltage
15 Station battery error
16 Digital input bouncing
17 Code error in digital ME
18 Metering input error
19 Life zero out of range
20 Com. device circuit error
21 Com. or set pt. discarded
22 SAM matrix error
23 Run time error

DC8-037-2, Edition 11.2020
12.12 Telegyr TG800
No. Meaning
24 NVRAM error
25 ACFAIL
26 Watchdog error
27 Program error
28 VF COMI/O error
29 Clock not sending time
30 Out of paper
31 NVRAM battery
32 CS line down
33 General interrog running
34 Error in COMI telegram
35 Hard time adjustment
36 Clock not receiving
37 Summer/winter time warning
38 Local autom. funct. error
39 Interlock rules not satis.
40 LOG queue full
41 COMO queue (0..3, ZW) full
42 Measurand queue full
43 COMI queue full
44 Indication queue full
45
46
47
48 SD COMI/0 error
49 Error in telg. from SD RTU
50 VF COMI/0 B error
51 CS link down, COMIO B
52 Gen. int. running in B
53 Error in telegram from B
54 COMO queue B (…..) full
55
56 No radio clk for 30 Min
57 No clk rec'n for 150 Min.
58
59
Context TG800 System Indications (Collective System Messages)
No. Indication text

Description
S0 System initialised (restart)
Collective system messages: equals system message no. 0.
S1 General interrogation in progress
Collective system messages: logical OR of the system message no. 33 and 52.
S2 Hardware fault
Collective system messages: logical OR of the system message no. 4, 8, 9, 10, 11, 12, 24, 26, 28,
31, 48 und 50.

DC8-037-2, Edition 11.2020
12.12 Telegyr TG800
No. Indication text

Description
S3 Process and installation fault
Collective system messages: logical OR of the system message no. 14, 15, 16, 17, 18, 19, 20, 22,
23, 25, 29.
S4 Data base and operational fault
Collective system messages: logical OR of the system message no. 3, 5, 21, 27, 30, 32, 34, 35, 36,
37, 40, 41, 42, 43, 44, 45, 47, 49, 51, 53, 54, 56, 57, 60, 61, 62 and 63.
S5 CONCAP/LAF fault
Collective system messages: logical OR of the system message no. 38 and 39.
S6 Offline
Is alway generated by the superior system.
S7 RTLD
Substation does not answer, is alway generated by the superior system.
Used abbreviations
LOG ....... Logbook
GI .......... General interrogation
CC ......... Control center
PDT ..... .. Programming and diagnostic terminal
IBU ......... Queue buffer
SD ...... ... Serial data bus
TG .......... Telegram
RTLD ...... Remote terminal line disturbed
VF .......... Voice frequency channel
MPV ....... Metering pulse value
CS ......... Central station
CSLD ..... Central station line disturbed
12.12.10Interoperability Telegyr TG800 Master
12.12.10.1 Network Configurations
Configuration Remarks
☐ Point-to-point 320 Multipoint-partyline with one Slave
n/i Multiple point-to-point
☐ Multipoint-partyline 320
n/i Multipoint-star
n/i Data concentrator
n/i Multipoint-ring
n/i Dial in
n/i Dial out
n/i Modem bank
☐ Radio spontaneous mode Only for commands and setpoints (project-specific
implementation with realization)
320 The TG800 Master protocol only supports the polling mode (= call up mode) in leased line mode (like IEC 60870-5-101 unbalanced
mode)

DC8-037-2, Edition 11.2020
12.12 Telegyr TG800
12.12.10.2 Physical Layer
Transmission Speed (common for both directions)
Speed Remark Speed Remarks

☐ 50 bit/s ☐ 600 bit/s
☐ 75 bit/s ☐ 1200 bit/s
☐ 110 bit/s ☐ 1800 bit/s
☐ 134 bit/s ☐ 2400 bit/s
☐ 150 bit/s ☐ 4800 bit/s
☐ 200 bit/s ☐ 9600 bit/s
☐ 300 bit/s n/i 19200 bit/s
Transmission Mode
Procedure Remarks
■ Asynchronous
n/i Synchronous
Message Format
Prozedure Remarks
■ IEC standard TC57 for class format FT 1.2
■ Long block (variable length), short block, single character
■ 1 start bit, 8 data bits, even parity, 1 stop bit (standard)
n/i 1 start bit, 8 data bits, no parity, 1 stop bit (GSM modem in RTU)
Link Transmission Procedure
Description Remarks
■ Unbalanced Master (half duplex)
n/i Unbalanced Slave
Frame Length
Description Remarks
■ Maximum frame length = up to 255 octets Max. frame length is configu-
rable
Address Field of the Link
Description Remarks
■ 1 octet
n/i 1 octet + one octet address field extension (hierarchy)
n/i 1 octet + two octets address field extension (hierarchy)
n/i 1 octet + Com-Line number (one octet address field extension for the Especially for SBB
Com-Line number)

DC8-037-2, Edition 11.2020
12.12 Telegyr TG800
Process Information in Monitoring Direction
Description Remarks
□ IAC 321 1: Indications (without time tag)
□ IAC 2: Indications with time tag (SOE)
□ IAC 3: Measurand (on event)
□ IAC 4: Measurand with relative time from protection equipment
□ IAC 6: Indication with relative time from protection equipment
n/i IAC 8: SOE indication for logging TG709 SOE
□ IAC 10: Counter value called up and archived (single current)
□ IAC 11: Counter value called up and archived (double current)
n/i IAC 12: Counter values after check request, before setting
□ IAC 15: GI indications (block of indications)
□ IAC 16: Analog GI measurands (block of measurands)
□ IAC 17: Digital GI measurands (block of measurands)
n/i IAC 166: TG800 Transfer of disturbance data according to VDEW/ZVEI-
IEC 103
System Information in Monitoring Direction
Description Remarks
□ IAC 15: GI block with system indications
□ IAC 1: System indications (without time tag)
□ IAC 2: System indications with time tag
□ IAC 18: Block of system indications Only permitted if the transmis-
sion of system indications is
defined as “collective”
□ IAC 25: Own station number Message is discarded
n/i IAC 35: Request for time from the CS
□ IAC 158: GI request to the CS: Indications
□ IAC 159: GI request to the CS: Measurands
n/i IAC 168: Restart subsystem
n/i IAC 169: Subsystem changeover
n/i IAC 170: TG 809 fault report text transfer to station module
System Indications
Description Remarks
□ Collective system indications (SW address 0 to 7) The 48/64 system indications
are reduced to 8 collective
system indications, the detailed
information (IAC = 18) must be
requested by the control
station.
□ Detailed system indications (IAC = 18) Only possible, if collective
system indications are used
□ System indications as “normal” indications with SW address 0 to 47
resp. 63
321 IAC = Information type character

DC8-037-2, Edition 11.2020
12.12 Telegyr TG800
Parameters in Monitoring Direction
Description Remarks
n/i IAC 175: Parameters
Process Information in Control Direction
Description Remarks
□ IAC 1: Indications in command direction (without time tag)
□ IAC 2: Indications in command direction (with time tag)
□ IAC 3: Measurands (on event) in command direction
n/i IAC 15: GI indications in command direction
n/i IAC 16: Analog GI measurands in command direction
n/i IAC 17: Digital GI measurands in command direction
□ IAC 128: Pulse commands
□ IAC 129: Permanent commands Special handling with control
center required
□ IAC 130: Stop permanent command Special handling with control
center required
□ IAC 131: Setpoint value
n/i IAC 133: PBN setpoint value
□ IAC 134: PBN command
n/i IAC 166: TG800 Transfer of disturbance data according to
VDEW/ZVEI-IEC 103
System Information in Control Direction
Description Remarks
□ IAC 135: Synchronization time
n/i IAC 140: Counter value freeze
n/i IAC 141: Counter value freeze, reset
□ IAC 142: Counter value freeze, transmit
□ IAC 143: Counter value freeze, reset, transmit
n/i IAC 144: Counter value transmit
n/i IAC 145: GI request: Counter value
n/i IAC 146: Single CV call up before CV setting
n/i IAC 148: Single counter value from the MS during CV setting
□ IAC 160: GI request to slaves: Indications
□ IAC 161: GI request to slaves: Measurands
□ IAC 162: GI Request: System indication block
□ IAC 163: System indication block acknowledgement
□ IAC 165: Command: send own station number
Parameters in Control Direction
Description Remarks
□ IAC 175 – Type 11: Reboot online

DC8-037-2, Edition 11.2020
12.12 Telegyr TG800
12.12.11Interoperability Telegyr TG800 Slave
12.12.11.1 Network Configurations
Configuration Remarks
☐ Point-to-point 322 Multipoint-partyline with one Slave
n/i Multiple point-to-point
☐ Multipoint-partyline 322
n/i Multipoint-star
n/i Data concentrator
n/i Multipoint-ring
n/i Dial in
n/i Dial out
n/i Modem bank
☐ Radio spontaneous mode
12.12.11.2 Physical Layer
Transmission Speed (common for both directions)
Speed Remarks Speed Remarks

☐ 50 bit/s ☐ 600 bit/s
☐ 75 bit/s ☐ 1200 bit/s
☐ 110 bit/s ☐ 1800 bit/s
☐ 134 bit/s ☐ 2400 bit/s
☐ 150 bit/s ☐ 4800 bit/s
☐ 200 bit/s ☐ 9600 bit/s
☐ 300 bit/s n/i 19200 bit/s
Transmission Mode
Procedure Remarks
□ Asynchronous
□ Synchronous
Message Format
Procedure Remarks
■ IEC standard TC57 for class format FT 1.2
■ Long block (variable length), short block, single character
■ 1 start bit, 8 data bits, even parity, 1 stop bit (standard)
n/i 1 start bit, 8 data bits, no parity, 1 stop bit (GSM modem in RTU)
322 The TG800 Slave protocol only supports the polling mode (= call up mode) in leased line mode (like IEC 60870-5-101 unbalanced
mode)

DC8-037-2, Edition 11.2020
12.12 Telegyr TG800
Link Transmission Procedure
Description Remarks
n/i Unbalanced Master (half duplex)
■ Unbalanced Slave
Frame Length
Description Remarks
■ Maximum frame length = up to 255 octets Max. frame length is configu-
rable
Address field of the Link
Description Remarks
■ 1 octet
n/i 1 octet + 1 octet address field extension (hierarchy)
n/i 1 octet + 2 octets address field extension (hierarchy)
■ 1 octet + Com-Line number (one octet address field extension Especially for SBB
for the Com-Line number)
Process Information in Monitoring Direction
Description Remarks
□ IAC 323 1: Indications (without time tag)
□ IAC 2: Indications with time tag (SOE)
□ IAC 3: Measurand (on event)
n/i IAC 4: Measurand with relative time from protection equipment
n/i IAC 6: Indication with relative time from protection equipment
n/i IAC 8: SOE indication for logging TG709 SOE
□ IAC 10: Counter value called up and archived (single current) TG800 overflow handling must
be done at the acquisition
board, no SNI
n/i IAC 11: Counter value called up and archived (double current)
n/i IAC 12: Counter values after check request, before setting
□ IAC 15: GI indications (block of indications)
□ IAC 16: Analog GI measurands (block of measurands)
n/i IAC 17: Digital GI measurands (block of measurands) Transmitted with IAC = 16
VDEW/ZVEI-IEC 103
System Information in Monitoring Direction
Description Remarks
□ IAC 15: GI block with system indications
□ IAC 1: System indications (without time tag)
□ IAC 2: System indications with time tag
323 IAC = Information type character

DC8-037-2, Edition 11.2020
12.12 Telegyr TG800
Description Remarks
□ IAC 18: Block of system indications Only permitted if the transmis-
sion of system indications is
defined as “collective”
□ IAC 25: Own station number
n/i IAC 35: Request for time from the CS
□ IAC 158: GI request to the CS: Indications
□ IAC 159: GI request to the CS: Measurands
n/i IAC 170: TG 809 fault report text transfer to station module
System Indications
Description Remarks
□ Collective system indications (SW address 0 to 7) The 48/64 system indications
are reduced to 8 collective
system indications, the detailed
information (IAC = 18) must be
requested by the control station
□ Detailed system indications (IAC = 18) Only possible, if collective
system indications are used
□ System indications as “normal” indications with SW address 0 to 47
resp. 63
Note: Only a subset of the predefined TG800 system indications is supported.
Parameters in Monitoring Direction
Description Remarks
Process Information in Control Direction
Description Remarks
□ IAC 1: Indications in command direction (without time tag)
□ IAC 2: Indications in command direction (with time tag)
□ IAC 3: Measurands (on event) in command direction
□ IAC 15: GI indications in command direction
□ IAC 16: Analog GI measurands in command direction
n/i IAC 17: Digital GI measurands in command direction
□ IAC 128: Pulse commands
□ IAC 129: Permanent commands Restricted use in SICAM A8000
□ IAC 130: Stop permanent command Restricted use in SICAM A8000
□ IAC 131: Setpoint value
n/i IAC 133: PBN setpoint value
□ IAC 134: PBN command Attribute = 0
Program number = 1, 2
VDEW/ZVEI-IEC 103

DC8-037-2, Edition 11.2020
12.12 Telegyr TG800
System Information in Control Direction
Description Remarks
□ IAC 135: Synchronization time
n/i IAC 140: Counter value freeze
n/i IAC 141: Counter value freeze, reset
□ IAC 142: Counter value freeze, transmit 324
□ IAC 143: Counter value freeze, reset, transmit 324
n/i IAC 144: Counter value transmit

n/i IAC 145: GI request: Counter value
n/i IAC 146: Single CV call up before CV setting
n/i IAC 148: Single counter value from the MS during CV setting
□ IAC 160: GI request to slaves: Indications
□ IAC 161: GI request to slaves: Measurands
□ IAC 162: GI request: System indication block
□ IAC 163: System indication block acknowledgement
□ IAC 165: Command: send own station number
Parameter in Control Direction
Description Remarks
324 Functionality must be configured at the acquisition board, function is not done in the Telegyr firmware

DC8-037-2, Edition 11.2020
12.13 ASCII SMS
12.13 ASCII SMS
The protocol is used for SMS alerting using external GSM modem and for serial printer-logging (ASCII) in
SICAM A8000 series.
12.13.2 Features and Functions
Printer logging (ASCII) and SMS alert/control.
• Printer logging
– Serial printer logging with ASCII
– Protocol text can be freely set
• SMS alert
– Send binary information with SMS
– SMS text can be freely set (umlauts are not supported)
– Acquisition time in SMS text
– Send commands with SMS
– Several subscribers
– Modem control with AT-Hayes commands
• SMS control
– Receive commands with SMS
– Command delay monitoring for SMS commands
– Several subscribers
– Modem control with AT-Hayes commands
ment.
optional DCE
Unbalanced interchange circuit (V.24/V.28) X2 →Modem RXD, TXD, CTS, RTS, DCD, DTR,
RS-232 asynchronous (GSM) DSR/VCC, GND
325 only CP-8022 (RS-232 operating mode)

DC8-037-2, Edition 11.2020
12.13 ASCII SMS
Printer Control
Own Station
System Master Module Protocol Element Note

SICAM A8000 CP-8000/CPC80 SMST0
CP-802x/CPC80
Remote Device

3rd-party system - - Serial printer for printer
logging
SMS Alert and Control
Own Station

CP-802x/CPC80
Remote Station

CP-802x/CPC80
SICAM AK 3 CP-2016/CPCX26 SM-2551/SMSA0
CP-2019/PCCX26 SM-0551/SMSA0
Legacy systems CP-20xx SM-2551/SMSA0
(SICAM AK CP-50xx SM-0551/SMSA0
SICAM TM CP-60xx SMST0
SICAM BC SM-2541/SMS00
SICAM EMIC)
3rd-party system - - • Mobile phone (SMS
alert/control)
• 3rd-party system
(SMS alert/control)
12.13.5.1 Overview
The protocol element can be used either for SMS alerting or for printer logging.
• Sending and receiving of up to maximum 500 SMS messages to/from 10 different subscribers by using a
GSM modem.
The sending of SMS messages can only be done with single-point information (TI:=30) and single
commands (TI:=45).
Received SMS messages can only be converted to single commands (TI:=45).
The transmission of SMS messages/alarms is generally “unacknowledged”.

DC8-037-2, Edition 11.2020
12.13 ASCII SMS
• Logging of up to 1500 datapoints (printer logging, simple message logging). The page layout is without
any page formatting and without header/footer lines.
Two different “link categories” are available for logging (printing):
– Logging type 1
Printing of single-point information (TI:=30) and single commands (TI:=45)
– up to 80 characters of parametrizable information text for each datapoint
– up to 10 status texts with 10 characters for each datapoint
– Logging type 2
Printing of single point-information (TI:=30), double-point information (TI:=31), single commands
(TI:= 45 resp. 58) and double commands (TI:= 46 resp. 59)
– up to 50 characters of parametrizable information text for each datapoint
– up to 16 characters for status ON and status OFF for each datapoint
The desired function can be set by parameter (Operating mode = SMS or logging).
Number of subscribers/data points

SMS • max. 10 different subscribers (i.e. max 10 different phone
numbers)
• max. 500 data points in transmission direction
• max. 500 data points in receive direction
Printer logging max. 1500 data points
Interface
Electrical Interface RS-232
Supported Baud Rates • 50, 75, 100, 110, 134.5, 150, 200, 300, 600, 1050, 1200, 1800,
2000, 2400, 4800, 9600, 19200
Byte Frame Adjustable
SMS alert
Data Communication • AT-Hayes (protocol for serial control of modems)
• Half duplex
Transmission procedures • Spontaneous transmission
SMS-Text length • Max. 160 characters
• Character set: ASCII
supported functions • Transmit SMS message
• Receive SMS Message
Printer-logging (ASCII)
Data Communication • Serial printer control with ASCII-protocol
• Printer monitoring by means of status line resp. XON/XOFF
• Half duplex
Transmission procedures Spontaneous transmission
SMS-Text length • Max. 160 characters
• Character set: ASCII
supported functions Logging of binary information and commands
length of text • Max. 80 characters in case of logging type 1
• Max. 50 characters in case of logging type 2

DC8-037-2, Edition 11.2020
12.13 ASCII SMS
Supported IEC60870-5-101/104 message formats in receive direction SICAM A8000 ← SMS (command
or control direction)
Supported IEC60870-5-101/104 message formats in transmit direction SICAM A8000 → SMS (signaling
or monitoring direction)
• <TI:=30> ... Single-point information with time tag CP56Time2a
Supported IEC60870-5-101/104 message formats in transmit direction SICAM A8000 → printer-logging
• <TI:=30> ... Single-point information with time tag CP56Time2a
• <TI:=31> ... Double-point information with time tag CP56Time2a
• <TI:=46> ... Double command
Redundancy
None
Parameter setting
• System-technical parameters with SICAM TOOLBOX II
• Process-technical parameters with SICAM TOOLBOX II
parameter-settable address conversion in transmit and receive
direction with OPM II
NOTE
i This protocol element for interfacing 3rd-party systems supports only restricted functionality and only a
subset of the possible data formats. For using this protocol element in your project, you have to verify if the
supported functionality and supported data formats of the protocol element will be compatible to the
required functionality and data formats for interfacing a specific 3rd-party system.
12.13.5.3 Restrictions
As special-protocol this protocol element implements only the defined functionality. It is therefore to be
checked for a concrete case of application, to what extent the real requirements correspond with the function-
ality implemented here and to what extent additional expansions or adaptations are necessary.
12.13.5.4 SMS Alert

The operating mode for SMS alert must be set with parameter Common Settings | Operating mode =
SMS.
In operating mode for SMS it is possible to transfer via GSM
• maximum 500 SMS messages in transmit direction (freely definable) to 1 subscriber (out of a list of max.
10 subscribers)
• maximum 500 SMS messages in receive direction (freely definable) from 1 subscriber (out of a list of
max. 10 subscribers)
The communication with the modem takes place with AT-Hayes commands.
Supported GSM modems:
• SIEMENS TC35, TC35i326
• CINTERION MC52iT326
326 end of life product

DC8-037-2, Edition 11.2020
12.13 ASCII SMS
• MC Technologies MC55iw Terminal
• Transmission facility compatible with Siemens TC35 SMS functionality
[kompatiblemodems, 1, --_--]
In most cases transmission facilities support only particular transmission rates (these are to be taken from the
descriptions of the transmission facilities).
The transmission rate (baud rate) is to be set for transmit/receive direction together with the parameter
Common settings | Baud rate .
For the data transmission of messages from/to a modem in command and data mode it is possible to set the
byte frame with the parameters Common Settings | Data bits, Common Settings | Parity and
Common Settings | Stop bits.
Required settings for Siemens TC35, Siemens TC35i, Cinterion MC52iT, MC Technologies MC55iw Terminal:
• 9600 bit/s, 8 data bits, no parity, 1 stop bit
[allg_einstellungen_en, 1, en_US]
Figure 12-13 Common modem settings
Used Interface Lines/Circuitry
Table 12-3 Used V.24 interface signals:
RS-232 Signal Direction (DTE) Note

TXD OUT Transmit data
RXD IN Receive data
GND Signal ground
RTS OUT switch on the signal-level of the modem
CTS IN Detection of the reception level of the modem (CP-802x)
DSR IN Detection of the reception level of the modem (CP-8000)
DTR OUT Power supply of the external connected modem <optional> (only for
Siemens TC35, TC35i)
NOTE
i The GSM modem Cinterion MC52iT and the MC Technologies MC55iw Terminal cannot be supplied via
status line because of the higher current consumption!

DC8-037-2, Edition 11.2020
12.13 ASCII SMS
Wiring
CP-8021 [X2], CP-8022 [X2] ⇔ MC55iw Terminal with external power supply of modem
[CP-802x_X2_MC55iw_ENG, 1, en_US]
Figure 12-14 Wiring CP-802x with MC55iw Terminal
NOTE
i If the original power supply adapter is used for the GSM modem, then IGT_IN = V + in the connection cable
is already wired correctly!
With a serial connection via X2 a connection between CTS and GND is required, as far as the interface shall
also be used for the connection with the engineering PC. By means of a special parameter you can define
that the interface X2 is not used for engineering [BSE] Communication settings serial |
Serial engineering interface = disabled. Thereby the connection between CTS and GND is not
required.

DC8-037-2, Edition 11.2020
12.13 ASCII SMS
Table 12-4 Pin Assignment of Connectors
Pin RS-232 Signal RJ45 socket (8-pole) Pin RS-232 Signal 9-pole DSUB (female)
[DTE] CP-802x [X2] [DCE] connector on modem
8 DTR (O) 1 CTS (O)
7 DCD (I) 2 RTS (I)
6 GND 3 DSR (O)
5 RXD (I) 4 TXD (I)
4 TXD (O) 5 RXD (O)
3 VCC (O) 6 GND
2 RTS (O) 7 DCD (O)
1 CTS (I) 8 DTR (I)
Wiring
CP-8022 [X6] ⇔ MC55iw Terminal with external power supply of modem
[CP-8022_X6_MC55iw_ENG, 1, en_US]
Figure 12-15 Wiring CP-8022 with MC55iw Terminal

DC8-037-2, Edition 11.2020
12.13 ASCII SMS
NOTE
Pin RS-232 Signal Push-in terminal (8- Pin RS-232 Signal 9-pole DSUB (female)
[DTE] pole) CP-8022 [X6] [DCE] connector on modem
1 RTS (O) 1 CTS (O)
2 TXD (O) 2 RTS (I)
3 CTS (I) 3 DSR (O)
4 DTR (O) 4 TXD (I)
5 n.c. 5 RXD (O)
6 GND 6 GND
7 DCD (I) 7 DCD (O)
8 RXD (I) 8 DTR (I)
Wiring
CP-8000 ⇔ Siemens TC35, Siemens TC35i; Power supply of modem from AU

DC8-037-2, Edition 11.2020
12.13 ASCII SMS
[CP-8000_X2_TC35_ENG, 1, en_US]
Figure 12-16 Wiring CP-8000 with Siemens TC35
NOTE
i The GSM modem Cinterion MC52iT and the MC Technologies MC55iw Terminal cannot be supplied via the
status line because of the higher current consumption!
Pin RS-232 Signal 9-pole DSUB (male) Pin RS-232 Signal 9-pole DSUB (female)
[DTE] CP-8000 [X2] [DCE] connector on modem
1 DCD (I) 1 CTS (O)
2 RXD (I) 2 RTS (I)
3 TXD (O) 3 DSR (O)
4 DTR, VCC (O) 4 TXD (I)
5 GND 5 RXD (O)
6 DSR (I) 6 GND
7 RTS (O) 7 DCD (O)
8 CTS (I) 8 DTR (I)
9 n.c.

DC8-037-2, Edition 11.2020
12.13 ASCII SMS
Wiring
CP-8000 ⇔ MC55iw Terminal (Cinterion MC52iT) with external power supply of modem
[CP-8000_X2_MC55iw_ENG, 1, en_US]
Figure 12-17 Wiring CP-8000 with MC55iw Terminal
NOTE

DC8-037-2, Edition 11.2020
12.13 ASCII SMS
Pin RS-232 Signal 9-pole DSUB (male) Pin RS-232 Signal 9-pole DSUB (female)
[DTE] CP-8000 [X2] [DCE] connector on modem
1 DCD (I) 1 CTS (O)
2 RXD (I) 2 RTS (I)
3 TXD (O) 3 DSR (O)
4 DTR (O) 4 TXD (I)
5 GND 5 RXD (O)
6 DSR (I) 6 GND
7 RTS (O) 7 DCD (O)
8 CTS (I) 8 DTR (I)
9 n.c.
AT-Hayes Commands
General
Each AT command to be sent ends with <CR> (ASCII character “carriage return”) and <LF> (ASCII character “line
feed”).
The modem confirms the received AT command with OK if the received command is valid; in case of an invalid
command the modem confirms with ERROR.
AT
This command is used for monitoring the communication (between automation unit and modem) and is sent
by the automation unit periodically (time period is configurable). The command must be confirmed from the
modem with OK.
AT + CREG = Network Registration

This command initiates the modem to response the actual network registration. This command is always sent
to the modem after a positive confirmation of the AT command. Thereby the connection (network) to the
provider is checked periodically.
Response: + CREG: <n>; <stat> OK
<stat>:
0 not registered, currently not searching for a new operator
1 registered, home network
2 not registered, currently searching for a new operator
5 registered, roaming
AT + CPIN = Enter PIN Code

Transmission of the PIN code to the modem.
Example: AT + CPIN = "****"
AT + CMGF = Select SMS Message Format

This command sets parameter in the modem which specifies the input and output format of messages to be
used.
Example: AT + CMGF = 1

DC8-037-2, Edition 11.2020
12.13 ASCII SMS
AT + CNMI = New SMS Message Indication

This command selects the procedure how the receipt of new SMS messages from the network are indicated to
the automation unit.
[atcnmi_eng, 1, en_US]
AT + CMGS = Send SMS Message

Command transmits SMS message from the automation unit to the network.
Example:
Request: AT + CMGS =
"00439991234567" <CR>
Hello, how are you? ^Z
Response: + CMGS: <mr> <CR> <LF> <CR> <LF> OK <CR> <LF>
↓→ message reference:
increasing number (0 to 255), assigned to the SMS-message by the modem.
If the network is not available (antenna disconnected) the modem confirms with the response: ERROR
+ CMTI: <mem>, <mr>

This message is routed by the modem to the automation unit, if a new SMS message is ready to be delivered.
This message is only sent if it is configured (new SMS message indication).
[atcmti_eng, 1, en_US]
The message reference is used to read and delete the SMS message.
AT + CMGR = Read SMS Message

This command is used to read the SMS message, after the modem indicates the delivery of a new SMS
message ("+ CMTI"). The modem returns the SMS message with location value <mr> from the message
storage.

DC8-037-2, Edition 11.2020
12.13 ASCII SMS
Request: AT + CMGR = <mr>

Response: + CMGR: "Rec read" or "Rec unread",
"+ 436641703123",
"03/05/26, 15:34:07 + 08" <CR> <LF>
I am fine, thanks <CR> <LF>
<CR> <LF> OK <CR> <LF>
Note: The firmware only accepts SMS messages with status "Rec unread".
If a already deleted message reference is read, the modem confirms with:

+ CMGR 0, 0 <CR> <LF>
<CR> <LF> OK <CR> <LF>
AT + CMGD = Delete SMS Message

This command is used to delete a SMS message specified by the message reference. The message reference
<mr> defines the number (1 to 10) of the SMS message to be deleted. The firmware deletes the SMS message
after it has been read automatically.
AT + CMGD = <mr>
SMS Send/Receive
The following common settings are possible for the protocol function.
PIN Code
When using the transmission facility Siemens TC35 you must set the parameter Advanced parameters |
SMS-send/receive | Pincode when the input of a PIN code is activated in the SIM card of the GSM
network provider.
NOTE
i If the PIN code request is not desired, then you have to insert the SIM card in a mobile phone and deacti-
vate the PIN code request. This setting is stored on the SIM card.
In the protocol element you can switch off the PIN code request by setting the parameter Advanced param-
eters | SMS-send/receive | Pincode to the value (= 4 x blank).
Time in SMS Message

For SMS alert you can optionally add the acquisition time in the SMS text.
The acquisition time will be added at the end of the parameterizable SMS message.
The function Time in SMS message is activated with parameter Advanced parameters | SMS-send/
receive | System time in SMS-message.
If SMS messages with time are sent as SMS commands, then the time will not be evaluated for the comparison
of the SMS text during reception.
Format of time in SMS message: JJJJ-MM-TT HH:MM:SS.ttt
Example: 2010-01-19 13:40:01.000
Retransmission for SMS Messages (Retries)

SMS messages are transmitted from the protocol element to the modem.

DC8-037-2, Edition 11.2020
12.13 ASCII SMS
If a SMS message is confirmed negative by the modem (i.e. no connection to provider) the SMS message is
repeated (retransmit) n times. Number of retries and delay before sending a retry can be set by parameter.
If the last retry is confirmed negative again, the interface is marked as “failed”, as well as the information
object confirmed negative to the BSE. Further the data transfer between BSE and firmware is stopped.
The expected acknowledgment time is set internal fix to 1 s. If necessary, the expected acknowledgment time
can be expanded with parameter Advanced parameters | Monitoring times |
Expected_ack_time_corr_factor.
The number of transmission retries can be set with parameter Advanced parameters | SMS-send/
receive | Number of message-retransmissions (retry).
It is possible to set a parameterizable pause before a transmission retry.
This pause is set with parameter Advanced parameters | SMS-send/receive | Time between 2
SMS-retransmission.
The signal monitoring time is used for the message interruption monitoring and message resynchronization in
receive direction. A message interruption is detected when the time between 2 bytes of a message is greater
than the set signal monitoring time. With message interruption the receive processing in progress is aborted
and the message is discarded. The character monitoring time can be set with the parameter Advanced
parameters | Monitoring times | Character monitoring time and Advanced parameters
| Monitoring times | Character monitoring time "time base".
Monitoring of the Modem

The protocol element monitors cyclic the communication between automation unit and modem by sending
periodically the AT-Hayes command AT This command is confirmed from the modem with OK.
The time frame for the cyclic monitoring is set with parameter Advanced parameters | Cycle time
for modem monitoring.
Cyclic Monitoring if Modem is Logged into Network

The command (AT+ CREG), causes the modem to announce the actual network registration. This command is
always sent to the modem after a positive confirmation of the AT-command. Thereby the connection
(network) to the provider is checked periodically.
If the modem has no more connection to the provider (response from AT + CREG), then the interface will only
be set as failed after n periods (n = number of retries) and the data transfer will be blocked.
Phone Numbers of the Different Subscribers

The protocol element supports sending/receiving of SMS messages to/from up to 10 subscribers. A phone
number must be set for each subscriber. Exactly one subscriber can be assigned to each data point in the
process technique.
The phone numbers of the subscribers can be set with parameter Advanced parameters | SMS-send/
receive | Subscriber list.
NOTE
i The phone numbers of the subscribers must always be set with the country identifier. (coercively necessary
for SMS Reception)
Example: 0043664 .....

DC8-037-2, Edition 11.2020
12.13 ASCII SMS
[teilnehmer_eng, 1, en_US]
Figure 12-18 Subscriber List in OPM II
Send an SMS Message

The firmware manages a data base (= process image) for SMS messages in transmit direction. The data base is
initialized with state = 0 as well as for each indication the data point quality identifier NT (not topical) is set to
1.
The data base is also used for the suppression of information states (example: send SMS only in case of
coming messages).
NOTE
i Commands are handled without data base!
SMS messages are only sent for binary information or command changes at NT = 0 and IV = 0.
No SMS message will be sent for data points with a quality identifier set to (NT = 1 or IV = 1).
The state of the data point and the quality identifier (NT, IV) are stored in the process image.
If a data point is set in the process image with NT = 1 or IV = 1, and this data point is received from the basic
system element with NT = 0 and IV = 0, then you can define with parameter Advanced parameters |
Protocol enabling | Evaluate information after falling NT/IV-bit whether a SMS
message should be sent in this case or not. If no SMS message is sent, then only the process image will be
updated.
The processing of binary information state changes with cause of transmission “background scan” or “interro-
gated by station interrogation” (= 20) can be set by parameter Advanced parameters | Protocol
enabling | Evaluate change of state due general interrogation. An SMS message will be
sent if the function is activated, otherwise only the process image will be updated and no SMS message will be
sent.

DC8-037-2, Edition 11.2020
12.13 ASCII SMS
[protokollfreigaben_eng, 1, en_US]
Figure 12-19 Protocol Enabling in OPM II
You can define in the process technique for each data point which signal state trips a SMS transmission.
Message Conversion
The parameterization of the address and message conversion for SMS in transmit direction is to be done with
the SICAM TOOLBOX II / OPM II or with the parameters for transmit detail routing when using SICAM WEB.
Parameter category:
firmware / Trans_sms
Parameter
• <TI:=30> ... single-point information with time tag CP56Time2a

• <TI:=45> ... single command
• NOT USED
SMS_subscriber Selection of SMS subscriber (receiver of SMS).
The phone number for each subscriber can be set with the parameter [PRE]
Advanced parameters | SMS-send/receive | Subscriber list.
• Subscriber 1 to 0
• NOT USED
If same SMS should be sent to more than one subscribers, SMS must be
included multiple in SIP message conversion detailed routing table.

DC8-037-2, Edition 11.2020
12.13 ASCII SMS
Parameter
text_of_state Selection of the state text for ON/OFF:
• Block 1 to 10
• NOT USED
For indication/command state ON/OFF up to 10 different text blocks can be
defined.
The block number selects the text of state block to be used for SMS informa-
tion (e.g. ON/OFF, RISING/FALLING).
If NOT USED is selected, no state text is sent in the SMS message.
The text of state can be set with the parameter [PRE] Advanced parame-
ters | text of state-SPI/SCI.
attribute_state SMS will be sent only for selected state only:
• each state
• OFF
• ON
• OFF – ON (=change from OFF → ON)
SMS-message Text of SMS:
• max. 160 characters

• valid characters: printable ASCII characters in range of 0x20 to 0x7F
Table 12-8 Valid characters for SMS text message:
[HEX] DEC ASCII [HEX] DEC ASCII [HEX] DEC ASCII [HEX] DEC ASCII
00 0 20 32 Space 40 64 @ 60 96 `
01 1 21 33 ! 41 65 A 61 97 a
02 2 22 34 " 42 66 B 62 98 b
03 3 23 35 # 43 67 C 63 99 c
04 4 24 36 $ 44 68 D 64 100 d
05 5 25 37 % 45 69 E 65 101 e
06 6 26 38 & 46 70 F 66 102 f
07 7 27 39 ' 47 71 G 67 103 g
08 8 28 40 ( 48 72 H 68 104 h
09 9 29 41 ) 49 73 I 69 105 i
0A 10 2A 42 * 4A 74 J 6A 106 j
0B 11 2B 43 + 4B 75 K 6B 107 k
0C 12 2C 44 , 4C 76 L 6C 108 l
0D 13 2D 45 - 4D 77 M 6D 109 m
0E 14 2E 46 . 4E 78 N 6E 110 n
0F 15 2F 47 / 4F 79 O 6F 111 o
10 16 30 48 0 50 80 P 70 112 p
11 17 31 49 1 51 81 Q 71 113 q
12 18 32 50 2 52 82 R 72 114 r
13 19 33 51 3 53 83 S 73 115 s
14 20 34 52 4 54 84 T 74 116 t
15 21 35 53 5 55 85 U 75 117 u
16 22 36 54 6 56 86 V 76 118 v
17 23 37 55 7 57 87 W 77 119 w
18 24 38 56 8 58 88 X 78 120 x

DC8-037-2, Edition 11.2020
12.13 ASCII SMS
19 25 39 57 9 59 89 Y 79 121 y
1A 26 3A 58 : 5A 90 Z 7A 122 z
1B 27 3B 59 ; 5B 91 [ 7B 123 {
1C 28 3C 60 < 5C 92 \ 7C 124 |
1D 29 3D 61 = 5D 93 ] 7D 125 }
1E 30 3E 62 > 5E 94 ^ 7E 126 ~
1F 31 3F 63 ? 5F 95 _ 7F 127
NOTE
i Umlauts are not supported!

Only printable ASCII characters in the range 0x20 to 0x7F are supported.
Text of Information for SMS Message

In the system technique it is possible to set 10 free definable texts (e.g. ON/OFF, RISING/FALLING) for the state
of information text with the parameter Advanced parameters | Text of state-SPI/SCI 10 .
In the process technique you have to choose a predefined state of information text for each datapoint. The
state of information text is attached after the data point specific SMS text.
[zustandstext_eng, 1, en_US]
Figure 12-20 State of information text
ReceiveSMS
The protocol also supports the function to receive SMS messages. Received SMS messages can only be
converted into single commands <TI:=45>.
The firmware only evaluates SMS messages with the state REC UNREAD; the time tag contained in the SMS
message is added to the command.
Cause of transmission: always Activation (= 06)
Qualifier of command: always 0 = no additional definition
Select/Execute (S/E): always Execute (no Select)
Evaluation:
If the received SMS text is found in the SMS parameter setting (process technique), then the received phone
number is compared with the number of the parameterized subscriber. If the SMS message is from the para-
meterized subscriber, then the SMS will be converted into an IEC command message <TI:=45>.
If a SMS message with a SICAM RTUs system time is received, this time will be used in the IEC command
message <TI:=45> generated from this SMS. If a SMS message is transmitted without a SICAM RTUs system
time, then the time of the SMS transmission from the GSM provider will be used for the generated IEC
command message.

DC8-037-2, Edition 11.2020
12.13 ASCII SMS
Message Conversion
The parameterization of the address and message conversion for SMS in receive direction is to be done with
the SICAM TOOLBOX II / OPM II or with the parameters for receive detail routing when using SICAM WEB.
Parameter category:
firmware /Rec_sms
Parameter

• NOT USED
SMS_subscriber Selection of SMS subscriber (sender of the SMS).
The phone number for each subscriber can be set with the parameter [PRE]
Advanced parameters | SMS-send/receive | Subscriber list.
• Subscriber 1
• Subscriber 2 - 20
• NOT USED
SMS in receive direction will be accepted only from parameterized phone
numbers in subscriber list.
SMS-message Text of SMS:

• valid characters: printable ASCII characters in range of 0x20 to 0x7F
For SMS in receive direction the total SMS text including state must be parameter-
ized (e.g. Circuit Breaker 5 ON).
Table 12-9 Valid characters for SMS text message:
00 0 20 32 Space 40 64 @ 60 96 `
01 1 21 33 ! 41 65 A 61 97 a
02 2 22 34 " 42 66 B 62 98 b
03 3 23 35 # 43 67 C 63 99 c
04 4 24 36 $ 44 68 D 64 100 d
05 5 25 37 % 45 69 E 65 101 e
06 6 26 38 & 46 70 F 66 102 f
07 7 27 39 ' 47 71 G 67 103 g

DC8-037-2, Edition 11.2020
12.13 ASCII SMS
08 8 28 40 ( 48 72 H 68 104 h
09 9 29 41 ) 49 73 I 69 105 i
0A 10 2A 42 * 4A 74 J 6A 106 j
0B 11 2B 43 + 4B 75 K 6B 107 k
0C 12 2C 44 , 4C 76 L 6C 108 l
0D 13 2D 45 - 4D 77 M 6D 109 m
0E 14 2E 46 . 4E 78 N 6E 110 n
0F 15 2F 47 / 4F 79 O 6F 111 o
10 16 30 48 0 50 80 P 70 112 p
11 17 31 49 1 51 81 Q 71 113 q
12 18 32 50 2 52 82 R 72 114 r
13 19 33 51 3 53 83 S 73 115 s
14 20 34 52 4 54 84 T 74 116 t
15 21 35 53 5 55 85 U 75 117 u
16 22 36 54 6 56 86 V 76 118 v
17 23 37 55 7 57 87 W 77 119 w
18 24 38 56 8 58 88 X 78 120 x
19 25 39 57 9 59 89 Y 79 121 y
1A 26 3A 58 : 5A 90 Z 7A 122 z
1B 27 3B 59 ; 5B 91 [ 7B 123 {
1C 28 3C 60 < 5C 92 \ 7C 124 |
1D 29 3D 61 = 5D 93 ] 7D 125 }
1E 30 3E 62 > 5E 94 ^ 7E 126 ~
1F 31 3F 63 ? 5F 95 _ 7F 127
NOTE
i Umlauts are not supported!

Only printable ASCII characters in the range 0x20 to 0x7F are supported!
Command Delay Monitoring (GSM Network)

During the transmission of data in the GSM network it is possible that undesired delays can occur during the
SMS transmission.
To ensure, that no undesirable process behavior is caused by a delayed output of commands, the protocol
element can monitor the transmission time (dwell time) of the data in the GSM network for selected process
information in control direction.
This monitoring prevents the output of old commands.
If the command delay monitoring is activated and a command message arrives via the SMS interface, then the
time tag of the telegram is compared with the current time of the component.
If the evaluated command delay time (transmission time of the data in the network) is longer than the para-
meterized command delay monitoring the command message is discarded without an error message.
If the time of the component is not yet set while command delay monitoring activated, then you can set with
the parameter Advanced parameters | SMS-send/receive | Discard command when local
time not set if a received command message is transferred for further processing or deleted.
In case of SMS commands the command unit does not recognize failed command output procedures. This
must be realized applicative if needed!
The time for the command delay monitoring must be set with parameter Advanced parameters | SMS-
send/receive | Command delay supervision.
The command delay monitoring can also be deactivated (command delay monitoring = 0).

DC8-037-2, Edition 11.2020
12.13 ASCII SMS
Error signalization
To localize the error, the number of commands discarded by the command delay monitoring since RESET is
summed and the last discarded command messages are additionally saved in a diagnostic ring. The counters
and the diagnostic ring can be read out with the SICAM TOOLBOX II (ST Emulation).
Monitoring of the command delay time for the following message types:
• SMS commands
NOTE
i The command delay monitoring is only effective when the component has a valid time!
12.13.5.5 Printer Logging (ASCII)

If the operating mode of the firmware is set to “logging” it is possible to print up to 1500 information objects
(indications and commands).
The operation mode for printer logging must be set with parameter Common Settings | Operating
mode.
[allg_einst_protokollierung_eng, 1, en_US]
Figure 12-21 Common settings printer protocoling in OPM II
Used Interface Lines
Table 12-10 Used V.24 interface signals:
RS-232 Signal Direction (DTE) Note

TXD OUT Transmit data
RXD IN Receive data
GND Signal ground
CTS IN Printer ready (SICAM A8000 CP-802x)
DSR IN Printer ready (only SICAM A8000 CP-8000)

DC8-037-2, Edition 11.2020
12.13 ASCII SMS
Wiring: CP-802x ⇔ Printer
[Verdrahtung_CP802x_Drucker_eng, 1, en_US]
Wiring: CP-8000 ⇔ Printer
[Verdrahtung_CP8000_Drucker_eng, 1, en_US]
Formatting of a Line
Possible text objects for printed line:
• Start character (<)
• Date + time
• Information text
• Text for state of information
• Blank (1 character)
• End character (>)
• New line (CR + LF)
• Line feed (LF)
• Carriage return (CR)

DC8-037-2, Edition 11.2020
12.13 ASCII SMS
The order of output can be set with parameter Advanced parameters | Logging | Line format-
ting.
Example:
[zeilenformatierung_eng, 1, en_US]
Figure 12-22 Settings for line formatting in OPM II
Date + Time
Format: MM/DD/YYYY HH:MM:SS.ttt

Example: 11/22/2006 10:36:01 AM.357
2 ASCII characters will be added as prefix for identification of the time information.
1. character: Time tag valid:
* .. time tag not valid
Blank .. time tag valid
2. character: Summer/winter time identifier:
S .. summer time
Blank .. winter time = normal time
Example: * 2001-05-22 00:00:01.356 ... time is not set
Information Text
The information text is freely assignable to any information object in the process technique. The length is
restricted on 80 characters (logging type 1) resp. 50 characters (logging type 2). The used number of charac-
ters for the monitoring must be set with parameter Advanced parameters | Logging | Length of
information text.
Text for State of Information for Category – Logging Type 1

In the system technique it is possible to set 10 free definable texts (e.g. ON/OFF, RISING/FALLING) for the state
of information of a data point.
The state of information text of the monitored data point (i.e. ON/OFF, RISING/FALLING) can be set globally
with parameter Advanced parameters | Text of state-SPI/SCI. The used number of characters for
the monitoring must be set with parameter Advanced parameters | Logging | Length of state
text of information . The parameter setting of the state of information text takes place according to the
possible process states of the data point:

DC8-037-2, Edition 11.2020
12.13 ASCII SMS
Single-point information: State of information OFF: e.g. OFF

State of information ON: e.g. ON
Example:
[zustanstext_beispiel_eng, 1, en_US]
Figure 12-23 Settings of text for state in OPM II
Text for State of Information for Category – Logging Type 2

The state of information text of the monitored data point (i.e. ON/OFF, RISING/FALLING) must be set per data
point in the process technique (max. 16 characters). However, you only have to set the state for OFF (param-
eter = Text-OFF) and for ON (parameter = Text-ON).
The text for invalid states of information (= 00 and 11 at double-point information) is set once globally for all
data points with parameter advanced parameters | Logging | DPI – indeterminate state in
the system-technical parameter settings.
[unbestimmter_zustand_eng, 1, en_US]
Figure 12-24 Setting for DPI indeterminate state in OPM II
NOTE
i Double commands with invalid states (= 00 and 11) are not printed; they are discarded with the error
message Format conversion in transmit direction.
Example for Printer Logging:

DC8-037-2, Edition 11.2020
12.13 ASCII SMS
[druckerprotokollierungbeispiel, 1, --_--]
Figure 12-25 Example of a printer logging
Printer Logging
The firmware manages a data base (= process image) for logging information objects. The data base is initial-
ized with state = 0 as well as for each indication the data point quality identifier NT (not topical) is set to 1.
The data base is also used for the suppression of information states (example: logging just coming messages).
NOTE
i Commands are handled without data base.
Data points are only logged for binary information- or command changes at NT = 0 and IV = 0. Data points
with a quality identifier set to NT = 1 or IV = 1, are not logged. The state of the data point and the quality
identifier (NT, IV) are stored in the process image.
If a data point is set in the process image with NT = 1 or IV = 1, and this data point is received from the basic
system element with NT = 0 and IV = 0, then you can define with parameter Advanced parameters |
Protocol enabling | Evaluate information after falling NT/IV bit whether it should be
logged or not. If no data point is logged, then only the process image will be updated.
The processing of binary information state changes with cause of transmission “background scan” or “interro-
gated by station interrogation” (= 20) can be set with parameter Advanced parameters | Protocol
enabling | Evaluate change of state due general interrogation. The logging takes place
when function is activated, otherwise only the process image will be updated and the data point not logged.
[ProtokollfreigabenGeneralabfrage_eng, 1, en_US]
Figure 12-26 Settings for Protocol enabling general interrogation
In the process technique you can set for each data point the binary information state which shall be logged.
If an event with cause of transmission “background scan” or “interrogated by station interrogation” is printed,
the event is printed with a special identifier:

DC8-037-2, Edition 11.2020
12.13 ASCII SMS
* 11/22/2005 5:10:25 PM.713

↓
Identifier “general interrogation” (equal to time invalid)
Printer Monitoring
The indication of ready to receive of the connected printer can occur on two different ways (configu-
rable, parameter = data flow control):
• Ready/Busy – status line CTS resp. DSR (= DTR line of the printer)
Ready = CTS resp. DSR = 1
• XON/XOFF – printer sends XON if it is ready
NOTE
i CP-8000 uses the status line DSR for printer monitoring, CP-802x uses the status line CTS.
The setting is done with parameter Advanced parameters | Logging | Data flow control .
If the printer indicates not ready to receive (= CTS resp. DSR = 0 or XOFF) the timeout “printer moni-
toring” is started. If timeout occurs, an interface error will be indicated and printing of information is stopped
(data transfer from BSE is stopped). The time for printer monitoring can be set with parameter Advanced
parameters | Logging | Printer monitoring.
Printing of information only occurs if the printer is ready to receive, except the printer monitoring is
deactivated (set to 0).
If the printer indicates not ready to receive during printing a line, printing is immediately stopped. If
the printer is again ready to receive within the printer-monitoring, the transmission of the remaining charac-
ters is continued.
If the printer-monitoring responds, the interface will be marked as failed, and the information is confirmed
negative to the BSE; if the information can be sent complete, the information is always confirmed positive to
the BSE.
Switch ON/OFF Printer Interface

The printer interface can be activated/deactivated dynamically with the parameter Advanced parameters
| Logging | Printer interface.
If the printer interface is deactivated, the following actions are done:
• Reset a possible interface error (printer not ready to receive)
• Set the warning printer interface deactivated
• All information to be printed is discarded (data base is updated)
• Stop the printer monitoring

If the printer interface is activated the following actions are done:
• Reset the warning printer interface deactivated
• Start the printer monitoring
ASCII Character Conversion

The protocol element expects that all parameterized texts (strings of ASCII characters) are coded in Windows
1252 (= Latin 1) character set.

DC8-037-2, Edition 11.2020
12.13 ASCII SMS
The protocol element converts the parameterized characters into two possible printer character sets (= Code
page) of the printer:
• Multilingual (850)
• Norway
The codepage can be chosen with parameter Advanced parameters | Logging | Printer-Code-
page.
The different character sets are illustrated in 12.13.6 Character Sets.
Further you have the possibility to convert up to 16 characters, independent of the used printer character set,
with parameter Advanced parameters | ASCII-Character conversion.
[ascii_conv_eng, 1, en_US]
Figure 12-27 Settings for ASCII character conversion in OPM II
Logging Type 1
The parameterization of the address and message conversion for logging type 1 in transmit direction is to be
done with the SICAM TOOLBOX II / OPM II, or with the parameters for transmit detail routing when using
SICAM WEB.
Parameter category:
firmware / logging_type1

DC8-037-2, Edition 11.2020
12.13 ASCII SMS
Parameter
• <TI:=30> ..... single point information with time tag CP56Time2a

• <TI:=45> ..... single command
• <TI:=160> ..... single command with output time (TI=160)
• NOT USED
A8000_command_num Command number for single command with output time (TI:=160):
• 0 to 15
Must be set to 0 for <TI:=30> single-point information and <TI:=45> single
command.
text_of_state Selection of the state text for ON/OFF:
• Block 1 to 10
• NOT USED
For information/command state ON/OFF up to 10 different text blocks can be
defined.
The block number select the text of state block to be used for logging (e.g. ON/
OFF, RISING/FALLING).
If NOT USED, state of text field for logging is filled up with blank.
The text of state can be set with the parameter [PRE] Advanced parameters
| Text of state-SPI/SCI zu parametrieren.
attribute_state Data point information text will be logged for selected state only:
• each state
• OFF
• ON
• OFF – ON (= change from OFF → ON)
information_text Text for data point to be printed:
• valid characters:
printable ASCII characters in range of 0x20 to 0x7F
• with parameter[PRE] Advanced parameters | ASCII-Character
Conversion language specific characters can be adapted.
Logging Type 2
The parameterization of the address and message conversion for logging type 2 in transmit direction is to be
done with the SICAM TOOLBOX II / OPM II, or with the parameters for transmit detail routing when using
SICAM WEB.

DC8-037-2, Edition 11.2020
12.13 ASCII SMS
Parameter category:
firmware / logging_type2
Parameter
• <TI:=30> ... single point information with time tag CP56Time2a

• <TI:=31> ... double point information with time tag CP56Time2a
• <TI:=46> ... double command
• NOT USED
attribute_state Data point information text will be printed for selected state only:
• each state
• OFF
• ON
• OFF – ON (= change from OFF → ON)
Information_text Text for data point to be printed:
• with parameter [PRE] Advanced parameters | ASCII Character
Conversion language specific characters can be adapted.
text_ON Text to be printed for data point’s status ON:
text_OFF Text to be printed for data point’s status OFF:

DC8-037-2, Edition 11.2020
12.13 ASCII SMS
12.13.6 Character Sets
12.13.6.1 Codepage: Windows 1252 (= Latin 1)
[codepagewindows1252, 1, --_--]

DC8-037-2, Edition 11.2020
12.13 ASCII SMS
12.13.6.2 Codepage: Multilingual
[codepagemehrsprachig, 1, --_--]

DC8-037-2, Edition 11.2020
12.13 ASCII SMS
12.13.6.3 Codepage: Norway
[codepagenorwegen, 1, --_--]
12.13.7 Printer supported for logging
OKI ML1120
[DruckerOKIML1120, 1, --_--]

DC8-037-2, Edition 11.2020
12.13 ASCII SMS
Technical Specifications
• 9-dot matrix printer
• max. column width: 80 characters
• Monochrome
• Continuous paper
Manuals:
• Reference Guide, English
• Bedienungsanleitung, deutsch
https://www.oki.com/de/printing/support/user-manual/dotmatrix/01196101/
Print current printer configurations
• Set the paper sort lever to single sheet, do not load paper, turn off the printer.
• Press and hold the SEL-button and switch on the printer (power switch = ON).
Keep the SEL key pressed down until the SEL LED flashes and the ALARM LED lights up
• Load a single sheet (A4).
• A single sheet is automatically retracted and the firmware details are printed (2 lines).

DC8-037-2, Edition 11.2020
12.13 ASCII SMS
• Press the TEAR key.

The current printer configuration is printed.
[printer_config_1, 1, --_--]
• Switch to “normal operation”:

Keep the TEAR key pressed and then press Load7 Eject-button and LF/FF-button. →, “Menu end” is
printed.
The following settings must be changed:
Paper Out Override (Set-Up): No → Yes

Parity (Serial J/F): No → Even
• Switch off the printer, set the paper sort lever to single sheet (don’t load paper yet).
• Press and hold the SEL-button and switch on the printer (power switch = ON).
Keep the SEL key pressed down until the SEL LED flashes and the ALARM LED lights up.
• Load a single sheet (A4).
• A single sheet is automatically retracted and the firmware details are printed (2 lines).
• Press the SEL key repeatedly until “Set-up Graphics” is printed.

Press the LF/FF key repeatedly until “Set-up Paper Override” is printed.
Switch parameter to YES with the LOAD/EJECT key.

DC8-037-2, Edition 11.2020
12.13 ASCII SMS
• Keep pressing the SEL key until “Serial I/F Parity” is printed.
Switch parameter to EVEN using the LOAD/EJECT key.
• Store the new configuration and switch to normal operation.

Keep the TEAR-button pressed and press afterwards the LOAD/EJECT and LF/FF-button.
“Menu end” is printed.
[printer_config_2, 1, --_--]
Initialize menu settings (load factory defaults)

If parameters were changed inadvertently, you can reset the printer to the factory settings with the following
procedure:
• Switch off the printer (power switch = OFF)
• Press and hold the SEL and LF/FF-button and switch on the printer (power switch = ON.
Example for printer logging
[druckerprotokollierungbeispiel, 1, --_--]

DC8-037-2, Edition 11.2020
12.14 IEC 62056-21 (Meter Protocol)
The IEC 62056-21 protocol is a standardized serial transmission protocol for communication with metering
devices via multi-point traffic (master/slave principle; “Partyline”).
For CP-8000/CP-802x, the following protocol firmware is available:

COUMT0 CP-8000 IEC 62056-21 multi-point traffic Master (interfacing of metering
CP-8021 devices)
CP-8022
For the interfacing of metering devices according to IEC 62056-21 (IEC 61107), a serial communications
protocol is implemented for multi-point traffic, with which one central station is connected with one or several
metering devices (substations) over a communication link in a linear or star configuration.
[dw_COUMT0_configuration, 1, en_US]
Figure 12-28 IEC 62056-21 Configuration
In multi-point traffic an unbalanced transmission procedure is used. That means, that the central station
initiates all message transmissions, while the substations may only transmit when they are called.
12.14.2 Functions
Communication of a central station with up to 10 counter devices.
• Serial communication protocol according to IEC 62056-21 (IEC 61107)

COUMT0 is central station
– Multipoint partyline
– Multipoint star
• Max. connections: 10
• System or device (application function)


DC8-037-2, Edition 11.2020

– Unbalanced interchange circuit according to V.24/V.28 standard
– Transmission medium (half duplex)
– Data flow control bit in receive direction
– Data flow control bit supervision
• Interoperability according to IEC 60870-5-101 Ed. 1
• Interoperability according to the following document:

– SICAM RTUs IEC 60870-5-101/104 Interoperability (DC0-013-2)
• Data acquisition by polling (station interrogation)

– Continuous interrogation of a remote terminal unit
• General interrogation, substation interrogation

– Demand

– IEC 62056-21 (IEC 61107) Mode-C
– EDIS data coding (EDIS = Energy Data Identification System)
– OBIS data coding (OBIS = Objekt Identification System)
•
• Standby transmission line over the public telephone network (PSTN)
• Data transmission using time slot radio
• Co-ordination of several masters

– Main and Standby Transmission Line

DC8-037-2, Edition 11.2020

– NUC redundancy (Norwegian Users Convention)
– NUC redundancy controlling station
– 1703 redundancy
– Listening mode with passive
– Tristate of the RS-232 interfce with passive
The operating mode of the interface is determined by parameters of the protocol element and optional
devices.

optional DTE
Unbalanced interchange circuit X2 RXD, TXD, CTS327, RTS, DCD, DTR,
(2-Draht)/ RS-422 (4-wire) asynchronous TXD+, TXD-, RXD+, RXD- (4-wire)
(2-wire)/ RS-422 (4-wire) asynchronous (CM-0819328) DSR/VCC, GND (to CM-08x9)
Optical interface (multimode fibre optic) ring X2 → CM-0821 RXD, TXD, CTS, RTS, DCD, DTR,
DSR, GND (zu CM-0821)
Unbalanced interchange circuit X6329 RXD, TXD, CTS, RTS, DCD, DTR,
(2-wire)/RS-422 (4-wire) asynchronous TXD+, TXD-, RXD+, RXD- (4-wire)
NOTE
i Details about realization of various operation modes are given in the manual SICAM RTUs Platforms –
may be needed.

328 RS-422 not supported

DC8-037-2, Edition 11.2020

SICAM A8000 CP-8000/CPC80 COUMT0
Remote Station (Counter Device)

Third-party system - - acc. to IEC 62056-21 (IEC
61107) mode C with EDIS/
OBIS data coding

DC8-037-2, Edition 11.2020
12.15 SAT SK 1703
12.15 SAT SK 1703
The SAT SK 1703 protocol is used to control serial message transmission in SAT 1703 standard format
(external data block formats) in multi-point traffic as a substation function.
Multi-point traffic describes a serial communication protocol with which a central station is connected with
one or several substations over a communication connection in a multpoint-line or multipoint-star configura-
tion. The data traffic is controlled by the central station.
Communication is suitable for
• teletransmission
• local transmission
Configuration
[dw_PCBMA0_config, 1, en_US]
Figure 12-29 SAT SK 1703 Configuration
12.15.2 Functions
Communication of a substation with a master station (SAT SK 1703 Slave).
• Multi-point traffic slave for transmitting the SAT 1703 standard formats (external database formats)
PCBST0 is the substation
• Data communication control can take place either according to “SK 1703 multi-point traffic” (master =
PCBM00, PCBM10, PCBMA0) or “wireless relay mode” without a routing method (master = SKSZ40,
SKSZA0)
• Telegram formats according to IEC 60870-5-1/FT1.2
• Pulse code modulation; asynchronous byte
• Transmission rate 50 up to 19200 bit/s
• Protection of telegrams with hamming distance HA = 4
• Controlling data communication using acknowledgment monitoring and telegram retries if the acknowl-
edgment fails
• Checking received telegrams
• Bundling in transmit/receive direction
• Chaining in transmit direction

DC8-037-2, Edition 11.2020
12.15 SAT SK 1703
• Linear measured value adaptation
• Time setting and time synchronization of the automation unit
• Multi-hierarchical configurations are available (additional automation units can be connected to substa-
tions for multi-point traffic)
ment.
optional DCE
Optical interface (multimode fiber optic) ring X2 → CM-0821 RXD, TXD, CTS, RTS, DCD, DTR,
NOTE
may be needed.

SICAM A8000 CP-8000/CPC80 PCBST0
CP-802x/CPC80 PCBST0


DC8-037-2, Edition 11.2020
12.15 SAT SK 1703

AK 1703 CP-2000/MC00 SM-2551/PCBMA0
CP-2002/PCCE00 SM-0551/PCBMA0
CP-2002/CE00
CP-2012/CE20
AMC 1703 CP-4000/CPC4x SM-2551/PCBMA0
SM-0551/PCBMA0
Third-party system - -
Options Chaining (fixed, activated)

Using a DCD input
The time settings are set automatically for predefined transmission
facilities
Packing in transmit/receive direction
Multi-hierarchical multi-point traffic
Transmission rates 50, 75, 110, 134.5, 150, 200, 300, 600, 1050, 1200, 1800, 2000, 2400,
4800, 9600, 19200
Retry count Max. number of message retries for call-up data messages
Component number in the Component no. in the message in transmit direction
message Component no. in the message in receive direction
Component number of the remote Component number to be provided in receive direction (option release)
station
Chaining, bundling Chaining in transmit direction (option release)
Bundling in transmit/receive direction (option release)
Max. data block length in chained format in bytes in transmit direction
Time settings for transmission Pause time (tp): Dead time before switching on the transmit part 333
channels
Set-up time (tv): Transmit delay after switching on the transmit part 333
Run-out time (tn) Pause until the transmit part is switched off 333
RS232 interface status when RTS is ✓
OFF
DCD evaluation, monitoring times Using DCD signal (option enable) 333
Bounce suppression time: (tbounce) 333
Receive disable after transmitting (tdis) 333
Continuous level monitoring time (tcl) 333
Monitoring messages, monitoring Monitoring time for call-ups
times
Station numbers Own station number
Constraints
• Ax redundancy not available
• “Functional redundancy” is not available in the substation
333 The time settings are set automatically for predefined transmission facilities

DC8-037-2, Edition 11.2020
12.15 SAT SK 1703
• Virtual components for the MK 1703 or uK 1703 substations are not emulated; each substation is
mapped to one component in Ax 1703.
• Relay operation:
– Routing is not available
– Only 1 byte link address
– Link address: 0 to 99
• No real-time concept for SK 1703 (ZA, ZSA, etc.)
• No time period message emulation in receive direction
• No real-time remote synchronization with BREAK signal!
• No regulating commands
• No message filter in transmit/receive direction
• Number of records = 1 (external data block formats)
• No emulation of IEC 60870-5-101/104 concepts:

– No emulation of SELECT/EXECUTE for commands, setpoints
– No emulation of ACTCON/ACTTERM for commands, setpoints
• No measured value change monitoring
• The command feedback Breaker tripping (SF) and Switching operation in progress (SL) is
not converted in transmit direction.
• Only selected system messages (DFK = 05) are supported for the external data block formats:
– GI request
– Counter interrogation - only in receive direction
– Error message for adjacent components
– Error message for non-adjacent components
– Interrogation message for time and date - only in transmit direction
– Response message for date - only in receive direction
– “Component X failure” message - only in receive direction
– Time setting - only in receive direction
– System messages for remote maintenance
(DLL messages, remote reset, error interrogation messages)
• BCD values (SK 1703) or floating point values (SK 1703) are not converted to normalized values (TI:=34
or 48) or vice versa
• Process image for max. 500 SK 1703 indication messages in transmit direction (1 indication message =
16 single-point indications or 8 double-point indications or 4 double-point indications with command
return information)
• Process image for max. 500 SK 1703 messages (= indications and values) in receive direction
SK 1703 external data formats that are not supported:
• 16 single-point transient indications (DFK = 23H)
• Combination messages - value + indication

(DFK = 06H or 86H and DFK = 16H or 96H)
• 8 status indications in control direction (DFK = 14H)

DC8-037-2, Edition 11.2020
12.15 SAT SK 1703
• Computer link formats

32-bit binary value + 2 status bytes (DFK = 0FH or 8FH)
32-bit binary value + 2 status bytes (DFK = 1FH or 9FH)
32-bit binary value + 2 status bytes (DFK = 2FH or AFH)
Parameter acknowledgment (DFK = 4FH)
2-57 byte parameter message (DFK = 3FH)
• 1 indication – old SK 1703 real-time spontaneous format (DFK = 33H or B3H)
• Single object formats:

1 single-point indication (DFK = 09H or 89H)
1 double-point indication (DFK = 19H or 99H)
1 double-point indication – BRM (DFK = 29H or A9H)
1 single command (DFK = 39H or B9H)
NOTE
i As a third-party adaptation system, this protocol element only implements part of the functionality and the
data formats of the third-party interface. Therefore, you need to check to what extent the real require-
ments match the functionality that has been implemented here and to what extent additional expansions
or adaptations are required for a specific application.

The following interface lines are used in 24/V.28 mode:
TXD <103> O Transmit data Transmit data
RXD <104> I Receive data Receive data
DCD <109> I Data Carrier Detect for synchronizing the receiver (optional)
CTS <106> I Clear to Send not used
RTS <105> O Request to Send Switching on the transmit signal level
DTR <108> O Data Terminal Ready not used
DSR <107> I Data Set Ready not used
RI <> I Ring Indication not used
GND <102> System Ground Ground
Legend:
O ... Output
I ..... Input

The data are pulse code modulated in groups of 8 Bit and transmitted asynchronous. A USART building block
in asynchronous mode provides each byte with a byte frame in the process.
1 Start bit
8 Data bits
1 Stop bit

DC8-037-2, Edition 11.2020
12.15 SAT SK 1703
byte.
[dw_PCBST0_pcmba_modulation, 1, --_--]
A: Empty line status (binary information “1”), between two messages at least 33 bit (in the event of an error)
B: Start bit ("0")
C: 8-bit data (possibly frame data or message data), LSB (Least Significant Bit) is transmitted first
D: Parity bit (even)
E: 1. Stop bit ("1")
T: Time to transmit a bit (1/transmission speed)
FB: Framing bits for the USART building block
12.15.5.4 Message Structure for SK 1703 Multi-point Traffic

Each message mainly consists of two parts:
• A part that is depending on the protocol (message frame)
• A part that is independent of the protocol (message data)

In the message format that is used (IEC 60870-5-1 / FT 1.2), the section that is independent of the protocol
contains the message control part (header), as well as the message data part as per the SAT nomenclature.
You can split each message into 2 parts irrespective of the byte frame:
• Into a part that is dependent on the protocol (message frame) and
• Into a part that is independent of the protocol (message data)
[dw_PCBST0_message_structure, 1, en_US]
Message frame: Start character, data length, checksum, end character, header
Message data: A data block in the structure shown above in a message
The message control part (header) adopts a special position that is included in the user data in relation to the
TC57 nomenclature, but which is part of the section that depends on the protocol in terms of functionality.

DC8-037-2, Edition 11.2020
12.15 SAT SK 1703
Transmission Formats
The transmission formats and rules meet the IEC 60870 5 101 Telecontrol equipment and systems TC 57 part
5.1, transmission frame formats format class FT 1.2 international standards.
This section of the standard defines the following message formats:
Message format IEC 60870-5-1 / FT1.2 Use
Messages with a fixed block length Call-up message, acknowledgment message
Messages with a variable block length User data message
Single character 1 (E5H) Slave ⇒ Master: “no data”
Single character 2 (A2H) Master ⇒ Slave: “general initialization request”
The message formats according to IEC 60870-5-1 / FT1.2 can be distinguished by their different start charac-
ters, for instance.
Message format IEC 60870-5-1 / FT1.2 Start character / Message frame / Stop character
Messages with a fixed block length 10H xxH xxH CS 16H
Messages with a variable block length 68H LLH LLH 68H xxH xxH .......... CS 16H
Single character 1 (E5H) E5H
Single character 2 (A2H) A2H
Legend:
CS ..... Checksum (HEX)
xxH .... Data byte (HEX)
LLH .... Quantity (= length) of user data bytes (HEX)
Showing a byte (LSB shown right-aligned):
[dw_PCBST0_trans_format_byte, 1, --_--]
D1 generally shows the least significant bit (LSB).

Representation of a byte “Bit sequence on the line” (example of single character 1):
[dw_PCBST0_trans_format_bit_seq, 1, en_US]
Legend:
STA ... Start bit
STP ... Stop bit
P ....... Parity bit (even)
All message formats are protected against erroneous information and block shift (synchronization errors) with
the specified transmission rules and character definitions with d = 4.

DC8-037-2, Edition 11.2020
12.15 SAT SK 1703
Message format with a fixed block length

Formats with a fixed block length consist of a start character, a fixed L quantity of user data bytes, a checksum
and a stop character.
[dw_PCBST0_message_format_fixed, 1, en_US]
The number of user data bytes for the format with a fixed block length is 2 bytes for the SK 1703 multi-point
traffic protocol.
Transmission rules for message formats with a fixed block length:
R1 The idle state on the line corresponds to a 1 signal.
R2 Every USART character has a start bit (0 signal), 8 information bits, a parity bit (even) and a stop bit (1
signal).
R3 Idle states are not permitted between the USART characters of a message.
R4 A minimum number of 33 bits in idle state are required between the formats (blocks) in the event of a
synchronization loss.
This time is generated by the transmitter, and always before transmitting the next message in normal
operation after detecting that there is an acknowledgment missing.
R5 The user data is monitored by a checksum. The checksum is the arithmetic sum without taking the
carryovers into account for all user data (no start or stop character).
R6 The receiver checks for each USART character: Start bit, stop bit and parity bit (even parity).
• Specified start character at the start and the end of the header part (10H)
• Number of user data bytes received (2 USART characters)
• Checksum
• Stop character (16H)

Error processing:
After an error as been detected, the received data is discarded and the received data line is monitored for a
pause of at least 33 bit to re-synchronize the receiver.

DC8-037-2, Edition 11.2020
12.15 SAT SK 1703
Message format with a variable block length

These formats consist of an initial start character, two of the same characters in which the L number of the
user data bytes is transmitted, and a second start character. User data L which is usually in the range 0 to 255
(for SK 1703 multi-point traffic protocol is used in section 1 ≤ L ≤ 63).
[dw_PCBST0_message_format_variable, 1, en_US]
Transmission rules for message formats with a variable block length:

The transmission rules R1 to R6 and error processing apply similarly as with the “message format with a fixed
block length”.
• Specified start character at the start and the end of the header part (68H xx xx 68H)
• Identity of the two length bytes (68H xx xx 68H)
• Number of received characters is equal to L+6
• Checksum
• Stop character (16H)
Single character
The single characters can be used as per the standard for special information to ensure efficient data commu-
nication control.
Single character-1: (E5H)
The single character-1 (E5H) is used as follows for the SK 1703 multi-point traffic protocol:
Slave ⇒ Master: “No more data”
Master ⇒ Slave: not used
[dw_PCBST0_single_character1, 1, en_US]
Single character-2: (A2H)

DC8-037-2, Edition 11.2020
12.15 SAT SK 1703
The single character-2 (A2H) is used as follows for the SK 1703 multi-point traffic protocol:
Slave ⇒ Master: not used
Master ⇒ Slave: “General initialization request” (= initializing all message numbers in transmitter/receiver
direction and deleting all acknowledgment bits)
[dw_PCBST0_single_character2, 1, en_US]
Transmission rules for single characters:

The transmission rules R1 to R4 and R6 and error processing apply similarly as with the “message format with a
fixed block length”.
Structure of User Data

The user data is split into two parts, the message head information (header), as well as the message data.
Messages that only contain the message header information (header) (call-up/acknowledgement messages)
are transmitted with a fixed block length message format in the process. Message length = 2 bytes of user
data.
Messages that have a header and data information (data messages) are transmitted in message format with a
variable block length. The 2 byte header information is transmitted before the message data in the process
and has the same structure as the messages with a fixed block length.
Example for call-up message master → slave:
[dw_PCBST0_request_message, 1, en_US]

DC8-037-2, Edition 11.2020
12.15 SAT SK 1703
Example for information messages in the format of 16 single-point information items for slave → master:
(unbundled, unchained, with component number in the message)
[dw_PCBST0_response_message, 1, en_US]
Header assignment
[dw_PCBST0_header_assignment, 1, en_US]
x ... not used

Station address:
0 to 99 .. Station-selective address
126 ....... Station address for “data acknowledged to all”
125 ....... Station address for “data unacknowledged to all”

DC8-037-2, Edition 11.2020
12.15 SAT SK 1703
M: Master direction bit

M → S: M = 1 ... in master → slave (M → S) messages
S → M: M = 0 ... in slave → master (S → M) messages
A/E: M → S: A = 1) ... call-up bit
S → M: E = 1 ... end of time format (slave does not have any more data to transmit)
TT: Message number bit for user data message in transmit direction
TR: Expected message number bit for user data message in receive direction
IN: M→ S: IN = 1 ... station-selective initialization request to the slave to initialize all message
number bits.
S → M: IN(Q) = 1 ... acknowledgement bit for a general initialization request for message
numbers with single character-2 (A2H).
Q: Acknowledgement bit for station-selective data message
S/C: M → S: C = 0 ... not used!
S → M: S = 1 ... acknowledgement bit for System message acknowledged to all
D: S → M: D = 1 ... acknowledgement bit for Data message acknowledged to all
R: M → S: R = 0 ... not used!
S → M: R = 0 ... not used!
NOTE
i Acknowledgements information from the master → slave may not be transmitted in messages to all
parties!
Before transmitting messages to all, any acknowledgements that may need to be transmitted are to
be transmitted with a station-selective acknowledgement message ( A = 0, Q = 1).
NOTE
i The header bits TT, TR, IN, INq are used to suppress multiple outputs for message retries (“Retries”)!
Managing the Message Numbers

The message number bits in transmit/receive direction (TT, TR) are used for retry suppression (for example, to
ensure that retries do not lead to multiple command outputs in the command direction).
Message number bits in the master

One message number bit is managed for the following message classes in the master:
• Tel# - TT bit for System message acknowledged to all SAA_Q
• Tel# -TT bit for Data message acknowledged to all DAA_Q
• Tel# - TT bit for Message acknowledged to all TAA_NQ
• Tel# - TT and TR bit for station selective data/system message D_Q (station number 0 to 99)

DC8-037-2, Edition 11.2020
12.15 SAT SK 1703
Message number bits in the transmit direction (TT):
[dw_PCBST0_message_number_bits_send, 1, en_US]
Expected message bits in receive direction (TR):
[dw_PCBST0_message_number_bits_receive, 1, en_US]
Message number bits in the slave

One message number bit is managed for the following message classes in the slave:
• Tel# - TR bit for System message acknowledged to all SAA_Q
• Tel# -TR bit for Data message acknowledged to all DAA_Q
• Tel# - TR bit for Message acknowledged to all TAA_NQ
• Tel# - TT and TR bit for station selective data/system message D_Q (for selective station number x)
Message number bit in transmit direction (TT):
[dw_PCBST0_message_number_bit_send-s, 1, en_US]
Expected message number bits in receive direction (TR):
[dw_PCBST0_message_number_bits_receive-s, 1, en_US]

DC8-037-2, Edition 11.2020
12.15 SAT SK 1703
Initializing the message numbers

Initializing the message number bits in the master:
After restarting or after a PASSIVE → ACTIVE redundancy switchover, the message number bits are initialized
for all message classes with “0” [ TTMaster(X) = 0, TRMaster(X) = 0 ].
Initializing the message number bits in the slave:
After restart, the message number bits for all message classes are initialized with “0” [TTSlave = 0 ],
[ TRSlave = 0 ].
When the “general initialization request” is received (with single character 2) the message number bits are
initialized to “0” for all message classes in receive direction [ TRSlave = 0 ].
General initialization request for master → slave:
The “general initialization request” is transmitted after a master restart or a PASSIVE → ACTIVE redundancy
switchover.
The “general initialization request” can also be transmitted before each message to all as an option. They
may only be transmitted when no more acknowledgements are pending for transmission.
Single character 2 (A2H) is used for the “general initialization request”. The single character-2 (A2H) is trans-
mitted several times.
A pause between of at least 33 bit is adhered to between transmitting single characters in the process to
ensure that a reception is still possible in the slaves even if the transmission conditions are poor.
Once the “general initialization request” is received or stored, acknowledgement information is deleted in the
slaves (acknowledgements for SAA_Q, DAA_Q, D_Q).
The confirmation for the “general initialization request” is acknowledged by the slaves in the next station-
selective message (slave → master) using the IN(Q) bit in the function field.
Station-selective initialization request for the master → slave with IN bit = 1:
In call-up messages, the master always transmits the message number bit status [ TTMaster(X) ], at
which point the next data message is transmitted to this station.
The message number bit in receive direction is acknowledged in the slave for the station-selective
data message (TR bit for D_Q) and initialized if messages with bit IN = 1 are received [TRSlave =
TTMaster(X) ].
In addition, the 1st message for each message class (DAA_Q, SAA_Q, TAA_NQ) is accepted without comparing
the message number bits after this initialization, such as after restart.
Synchronizing the message numbers in the slave after restarting the slave:
After restarting the slave, it takes over the 1st message for each message class (DAA_Q, SAA_Q, TAA_NQ, D_Q)
without comparing the message number bits and so synchronizes the relevant message number bit for the
relevant message class [ TRSlave ] with the message number bit that has been received [ TRSlave ] =
[ TTMaster ].
If a slave is called up and it does not expect an acknowledgment for a data message that was previously
submitted, then it always re-synchronizes the message number bit [ TTSlave = TRMaster].
Note:
As the slave is not expecting an acknowledgement for a message that was previously transmitted, there also
cannot be multiple forwarding instances for the master due to retries. The message number in the slave can
be resynchronized to the message number expected by the master for the next message as a result.
The master transmits a station-selective initialization request:
• After master restart (first call-up)
• After passive → active redundancy switchover (first call)
• To failed stations
NOTE
i The exchange of user data is only started after successful initialization (for each station) (station-selective
data block is cancelled).

DC8-037-2, Edition 11.2020
12.15 SAT SK 1703
Managing the message numbers - “Summary”

Data message for slave → master:
The master messagemanages a TR bit (= expected message number bit for data message in receive direction)
per each slave. The TR bit specifies which TT bit the master is expecting from this slave for data messages.
Output suppression (master):
The master acknowledges all received slave data messages.
However, the received data message is only forwarded from the slave from the basic system element (BSE) if
[ TRMaster(X) = TTSlave(X) ].
Switching over the TR bit (in the master):
The master has received a data message and forwarded it to the basic system element [ TRMaster(X) =
NOT TRMaster(X) ].
Updating the TT bit (in the slave):
The TT bit in the slave is only advanced once a data message that was previously transmitted by the master
has been acknowledged. Retries are transmitted from the slave to the master with an unchanged TT bit. The
TT bit is advanced in the slave after a received acknowledgement has been evaluated (the assigned transmit
buffer is enabled by receiving an acknowledgement).
If the transmit buffer is free in the slave, the TT bit in the slave is always synchronized for the message number
bit that the master expects for the next data message from the slave [ TTSlave = TRMaster ]
Initializing the TT bit (in the slave):
After the slave restart, the TT bit is initialized with “0” [ TTSlave = 0 ].
As the transmit buffer is always free after a slave restart, the first message is automatically transmitted from
the slave to the master with the TR bit that is expected by the master (= synchronizing the TT bit) [ TTSlave
= TRMaster ].
Initializing the TR bit (in the master):
in the master with “0”.
As the message number bits [ TRMaster ] and [ TTSlave ] could run alongside one another, the master
accepts the 1st data message from each slave without comparing the message number bits [ TRMaster(X)
=TTSlave(X) ].
Data message master → slave:
Each slave manages a TR bit for each message class (= expected message number bit in receive direction for
SAA_Q, DAA_Q, TAA_NQ, D_Q).
The TR bit in the slave indicates which master TT bit the slave is expecting for the relevant message class.
The master TT bit is managed in the master for station-selective data messages for each slave.
Output suppression:
The slave acknowledges all received master data messages.
However, the data is only forwarded to the basic system element if [ TRSlave = TTMaster(X) ].
Switching over the TR bit (in the slave):
The slave has received a data message and forwarded it to the basic system element. [ TRSLave = NOT
TRSlave ]
Switching over the TT bit (in the master):
When the acknowledgment is received by the slave (exception: Message acknowledged or unacknowledged
for all, and the switchover is carried out immediately after transmission).
Initializing the TR bit (in the slave):
After restarting, the slave takes over the 1st message depending on the message class (DAA_Q, SAA_Q,
TAA_NQ, D_Q) without comparing the message number bits and so synchronizes the relevant message
number bit for the relevant message class with the message number bit that has been received [ TRSlave ]
= [ TTMaster ].
Initializing the TT bit (in the master):
for all message classes with “0”.

DC8-037-2, Edition 11.2020
12.15 SAT SK 1703
Suppressing multiple outputs

In the event of any transmission faults (missing acknowledgements) retries are carried out for data messages
whereby additional measures may need to be put in place to prevent multiple outputs and prevent the same
message going to the receiver (example: The pulse command would be transmitted several times).
The following method is used to prevent these multiple outputs:
• Using the message number bit.
• Each new message is transmitted with an increased message number (modulo 2).
• Retries are transmitted with the same TT bit as the original message in each case.
This ensures that the receiver can detect retries and put appropriate measures in place. Retries are always
acknowledged by the partner receiver but not forwarded to the basic system element.
This method is also used for message retries (= multiple transmissions) for messages to all, but with message
number bits that are managed separately. The acknowledgement for messages that have been acknowledged
to all parties is collated by the master in the following interrogation cycle, whereby the acknowledgement for
messages that have been acknowledged to all parties is only stored by the slaves if the message has also been
forwarded to the basic system element.
[dw_PCBMA0_polling_error_data_m-s, 1, en_US]
Legend:
Z, Ux…. central station, substation x
➊……… data message is forwarded to the basic system element and acknowledged in the slave due to a
message number bit being expected
➋……… message retry (= retry) as acknowledgement is missing in the master
➌……… data message is NOT forwarded in the slave as another message number is expected
➍……… the call-up cycle is continued after receiving acknowledgment
➎……… the next data message to the slave is transmitted with an advanced message bit
NOTE
i After a reset or if a interface fault has been detected, the first message is accepted independently by the T
bit in the received direction, however, messages to all are only accepted (for the slaves) if the relevant
acknowledgement bit for the message class has not been set!
All healthy data messages that have been received are acknowledged by the master and the slave. However,
only messages that are received with the expected message number TT for the respective message class are
forwarded to the basic system element.
Communication Procedures
Data communication control for the SK 1703 multipoint traffic protocol has been designed for half duplex
transmission.

DC8-037-2, Edition 11.2020
12.15 SAT SK 1703
The following data transmission procedures are carried out by the master:
• Data acquisition by polling (station interrogation)

– General initialization after starting up the master
– Station change
– Data message between master → slave acknowledged
– Continuous station interrogation for a substation (demand)
– Data message between slave → master acknowledged
• Data/system message acknowledged to all (master → slave)
• Data/system message unacknowledged to all (master → slave)
• Time synchronization (real-time remote synchronization)
General initialization after starting up the master

The “general initialization request” is transmitted after a restart or a PASSIVE → ACTIVE redundancy switch-
over.
Single character 2 (A2H) is used for the “general initialization request”. The single character-2 (A2H) is trans-
mitted several times by the master in the process.
A pause between 2 RTS gatings is adhered to between transmitting single characters in the process to ensure
that a reception is still possible in the slaves even if the transmission conditions are poor.
Using the “general initialization request”
• All message numbers initialized in transmit/receive direction in the slave
• All acknowledgment bits are deleted.

Reception of the “general initialization request” is acknowledged by the slaves in the next station-selective
message (slave → master direction) using the IN(Q) bit in the function field (see also section “Initializing
message numbers”).
[dw_PCBMA0_polling_init, 1, en_US]
Example: General initialization (for station numbers 0, 30, 99)
[dw_PCBMA0_polling_init_data, 1, --_--]

DC8-037-2, Edition 11.2020
12.15 SAT SK 1703
Station change
Data is only transmitted from a substation to a master station during station interrogation. A substation is
queried by the master until it has no more additional data stored for transmission (payload messages or
acknowledgement information) or until the max number of call-ups has been reached for this substation.
If the substation acknowledges a call up message from the master using a set call-up bit A = 1 with a single
character 1 (E5H) = “no additional data” or with a short message (with acknowledgements for the master),
then the master carries out a station change.
Once the master has reached the max. number of call ups for a substation, then the master acknowledges the
data message that has received most recently from the substation with A = 0 and Q = 1.
This call-up message without an interrogation bit (= acknowledgment message) is no longer answered by the
slave. The master continues with the station interrogation after the pause between 2 RTS gatings with the
next station (see ➋).
The slave requires the pause to synchronize the message to ensure that the DCD signal change is also safely
detected in the substation due to delays in the transmission facilities.
If data needs to be sent from the master to the slave, the master always transmits an acknowledgement that
may be stored first, then the data message. If an acknowledgement and data message need to be transmitted
to the same station address, the acknowledgement is sent along in the data message.
[dw_PCBMA0_polling_station_change, 1, en_US]
Example: Station change (for station numbers 0, 1, 2)
[dw_PCBMA0_polling_station_change_data, 1, --_--]
Data message between master → slave acknowledged

Data messages from the master to the slave are always inserted into the interrogation cycle once the message
sequence that is currently in progress has finished (call-up + acknowledgement including retry handling).
The data message is transmitted from the master to the slave with a set call-up bit A = 1. This is to ensure that
any data that may need to be transmitted in the meantime can be picked up by this slave.
The “continuous substation interrogation” function can be used as an option to ensure that responses to the
data message that has been sent can be quickly transmitted. A time-limited substation interrogation is carried
out in the process. Continuous interrogation is interrupted if another data message needs to be transmitted
(see also section “Continuous substation interrogation”).

DC8-037-2, Edition 11.2020
12.15 SAT SK 1703
Data messages from the master → slave are prioritized in parallel to messages for station interrogation (call up
messages). This means that if data must be sent to the slaves on a continuous basis, a call-up message is
always carried out between the data messages.
After the master → slave data transmission sequence has been ended, station interrogation is continued at
the point where it was interrupted.
[dw_PCBMA0_polling_data_m-s, 1, en_US]
Example: Indication message master → slave
[dw_PCBMA0_polling_data_m-s_data, 1, --_--]
Data message between slave → master acknowledged

Data message is only transmitted from a substation to the master station during station interrogation (see also
section “Station change”).
[dw_PCBMA0_polling_data_s-m, 1, en_US]

DC8-037-2, Edition 11.2020
12.15 SAT SK 1703
Example: Indication message slave → master
[dw_PCBMA0_polling_data_s-m_data, 1, --_--]
Data/system message acknowledged to all (master → slave)

Data/system messages from the master → slave can be acknowledged for all. In doing so, the data/system
message is transmitted to all parties several times (= fixed retries).
Messages acknowledged for all including multiple transmissions are generally transmitted with call-
up bit A = 0 and with an unchanged TT message number bit.
System message acknowledged for all (SAA_Q) and Data message acknowledged for all
(DAA_Q) are each transmitted with their own TT message number bit for SAA_Q or TT for DAA_Q in transmit
direction.
Prior to transmitting a acknowledged for all message, the message numbers can be initialized in the
substations using the “general initialization request”. The initialization is also confirmed by the slaves (S = 1 or
D = 1 and IN = 1).
The acknowledgments for data message acknowledged for all or system message acknowl-
edged for all are collated in the following interrogation cycle.
[dw_PCBMA0_polling_data_m-s_daa_q, 1, --_--]

DC8-037-2, Edition 11.2020
12.15 SAT SK 1703
Example: Counter interrogation with “general initialization request”
[dw_PCBMA0_polling_data_m-s_daa_q_data, 1, --_--]
Data/system message unacknowledged to all (master → slave)

Data/system messages from the master → slave can be unacknowledged for all. In doing so, the data/system
message is transmitted to all parties several times (= fixed retries).
Messages unacknowledged for all including multiple transmissions are generally transmitted with
call-up bit A=0 and with an unchanged TT message number bit.
Messages unacknowledged for all are each transmitted with their own TT message number bit in
transmit direction. No acknowledgments are transmitted.
Prior to transmitting an unacknowledged for all message, the message number bits can be initialized
in the substations using the “general initialization request”. Messages to all are generally transmitted
without a call-up bit (A = 0).
[dw_PCBMA0_polling_data_m-s_daa_nq, 1, --_--]

DC8-037-2, Edition 11.2020
12.15 SAT SK 1703
Example: Master → slave counter interrogation message unacknowledged for all with a “General initialization
request”
[dw_PCBMA0_polling_data_m-s_daa_nq_data_counter, 1, --_--]
Example: Master → slave real-time remote synchronization unacknowledged for all without a “General initiali-
zation request”
[dw_PCBMA0_polling_data_m-s_daa_nq_data_time, 1, --_--]
12.15.5.5 Message Structure – Radio Relay Mode (IEC 60870-5-2)

Communication protocol in line with the standards
• IEC 60870-5-1 (= TC57 Part 5.1; = DIN 19244 Part 51)
• IEC 60870-5-2 (= TC57 Part 5.2; = DIN 19244 Part 52)

Limitation:
• Only 1 byte link address
• Only link address 0 to 99 possible
Control field function codes in primary station messages (PRM = 1)
Function Message type Service function FCV Supported

code no.
0 SEND-CONFIRM expected Normalizing the secondary station 0 ✓
link layer
1 SEND-CONFIRM expected Normalizing the user process 0 –

DC8-037-2, Edition 11.2020
12.15 SAT SK 1703
Function Message type Service function FCV Supported

code no.
2 SEND-CONFIRM expected Reserved for balanced transmis- – –
sion scheme
3 SEND-CONFIRM expected User data 1 ✓
4 SEND-NO REPLY expected User data 0 ✓
5 – Reserved – –
6 to 7 – Reserved for special application on – –
agreement
8 REQUEST after an access demand The access demand is defined in 0 –
the expected response
9 REQUEST-RESPOND expected Querying the status of the link 0 ✓
layer
10 REQUEST-RESPOND expected Querying user data class 1 1 ✓
11 REQUEST-RESPOND expected Querying user data class 2 1 ✓
12 to 13 – Reserved – –
14 to 15 – Reserved for special application on – –
agreement
NOTE
i • No distinction is drawn between class 1 data and class 2 data.
• SEND-CONFIRM is always confirmed by pressing ACK (FC = 0).
• User data query (class 1/class 2) is confirmed with a short acknowledgement (= 0xE5) when there is
no user data available for transmission.
Function codes for the control field in the secondary station messages (PRM = 0)
Function Message type Service function Supported

code no.
0 CONFIRM ACK; positive acknowledgment ✓
1 CONFIRM NACK; message not accepted, link –
layer occupied
2 to 5 – Reserved –
6 to 7 – Reserved for special application on –
agreement
8 RESPOND User data ✓
9 RESPOND NACK; subscribed data not avail- –
able
10 – Reserved –
11 RESPOND Link layer or access demand status ✓
12 – Reserved –
13 – Reserved for special application on –
agreement
14 – Link layer service isn’t working –
15 – Link layer service not available ✓

DC8-037-2, Edition 11.2020
12.15 SAT SK 1703
12.15.6 Communication according to SAT SK 1703
The data is transmitted from the substations to the central station via station-selective station interrogations
(querying, interrogation procedure, polling), which are controlled by the central station. This means that
changed data is stored in the substation and transmitted to the central station if this station is interrogated.
The interrogation procedure of the central station ensures that the substations are interrogated sequentially,
whereby substations with important data can be interrogated more often. Substations may only transmit
when they are called up.
The interrogation procedure can be influenced by the following parameters:
• Priority level assignment

(each station is assigned one of the three priority levels: high priority, medium priority, low priority)
The station-selective address for the link layer in each substation (= multi-point traffic slave) must be set using
the parameter Own station number. This address must be unambiguous for each multi-point traffic line.
12.15.6.1 Structure of Message Data in SAT Standard Format

The message data part consists of one or more data blocks. A data block is structured as follows:
[dw_PCBST0_datablock_structure, 1, en_US]
The structure of the message data part in bundled format differs due to the options “Chaining” and “Missing
component number”. These options can be configured using function enable.
The component number must always be included in the message in receive direction.
You can find all available data formats for the SAT SK 1703 summarized in the document Description Ax 1703
Data Block Formats(MA0-023-1).
Packing/Chaining
The “Data packing” and “Chaining data blocks” methods can be used for SAT standard protocols to ensure that
the transmission routes are used to their full potential.
Packing
Bits that are not used in the individual message formats can be removed by the packing for transmission on
the line and reinserted with the receiver for internal forwarding.
This makes the messages shorter for transmission on the line, which leads to a marked improvement in effi-
ciency if transmission speeds are low. Packing therefore means that the user data is pushed tightly together

DC8-037-2, Edition 11.2020
12.15 SAT SK 1703
and the pieces of partial information can exceed byte limits as a result. The packing can be switched on using
parameters.
Bundling is used in transmit/receive direction when all stations are usually handled in the same way (all
stations use a packed configuration or all stations use an unpacked configuration).
NOTE
i If data communication control is carried out according to “radio relay mode” (without a routing method),
then the unpacked protocol format must generally be used as the central station (SKSZ40, SKSZA0) does
not support the packed protocol format.
Characteristic:
If an existing SK 1703 muli-point traffic line is expanded to an automation unit from the Ax 1703/ACP product
family and if the information is transmitted from this station in real time, then the following issue occurs with
the packeded protocol format:
The I bit for real-time information gets lost in a packed format (historically, this is due to the fact that the I bit
for real-time information "IE" was defined later on).
To prevent this or ensuring that you don't need to adjust all of the existing configuration, the “Generally
transmit station selective messages in an unpacked format” function can be activated in the SK 1703 multi-
point traffic master (PCBM00, PCBM10).
However, messages that are acknowledged for all or unacknowledged for all are transmitted irrespective of
the parameter Packing (yes or no).
If the existing plant uses the bundled protocol format, then the following parameterization must be carried
out:
• Parameterization (general settings)

Packing = selective: no/broadcast: yes
• Parameterization in the SK 1703 master

The Station type must be set to 1 for the relevant station in the section station number (available
stations/station type).
If the unpacked protocol format is used in the existing plant, then the Packing must be set to no.
[dw_PCBSA0_telegramdate_a, 2, en_US]

DC8-037-2, Edition 11.2020
12.15 SAT SK 1703
[dw_PCBSA0_telegramdate_b, 2, en_US]
Chaining
Several data blocks can be transmitted in one message due to the maximum user data length of 63 bytes. This
significantly increases transmission efficiency.
However, please note that the packing is proceeded continuously, even if there are several data blocks in the
message, and each data block needs not start on a byte limit. Therefore, an insignificant overhead can only be
possible in the last data block, as the message data part always ends at a byte limit.
The chained SAT standard message formats are regenerated in receive direction by dechaining handling and
then converted to IEC 60870-5-101 format.
Chaining is only used in the substation → central station direction – chaining in the central station → substa-
tion direction is not provided for the SK 1703 multi-point traffic protocol.
[dw_PCBSA0_telegramdate_c, 2, en_US]

DC8-037-2, Edition 11.2020
12.15 SAT SK 1703
The “chaining” function can be used in conjunction with the “packing” function.
[dw_PCBSA0_telegramdate_d, 2, en_US]
The “chaining” function can be switched off in the substation using parameters. Received messages are always
unchained in the central station.
Component Number in the Message

A component number is always included in message data from the central station to the substation (as
required to ensure that remote maintenance works without any issues).
There are 2 variants for transmitting the component number from the substation to the central station in
message data:
• No multi-hierarchical multi-point traffic

In this case, the component number for SK, MK/µk 1703 substation types are provided by the central
station in receive direction. In SK 1703 substations the “component number in message data in transmit
direction” option must not be enabled.
• Multi-hierarchical multi-point traffic

If the “multi hierarchical multi-point traffic” option is released (in the central station), received messages
are expected from MK/µk 1703 substations with the “no component number in the message” format in
the central station. The component number is provided by the central station, depending on the station
number.
The component number must be included in the message data in transmit direction for SK 1703 substations.
Additional components can be connected to these components.

DC8-037-2, Edition 11.2020
12.15 SAT SK 1703
12.15.6.2 Acknowledgement Procedure
Acknowledging Received Messages

Central station call-up messages are acknowledged by the substation with
• E1 single character (= E5), if no user data or acknowledgments need to be transmitted
• Short message if acknowledgments need to be transmitted, but no user data
• Long message if user data need to be transmitted
The central station expects this special acknowledgement information from the substation for all station-selec-
tive messages as well as for “acknowledged for all” data/system messages.
The substation acknowledges the user data messages it has received (from the central station) as follows:
Q = 1 for selective station messages
D = 1 for data messages “acknowledged for all”
S = 1 for system messages “acknowledged for all”
Acknowledgement transmission can be carried out using a short message (if no data is available for transmis-
sion) or with long messages (with user data to the central station).
Acknowledging Transmitted Messages

The substation always expects an acknowledgement from the central station for each message that is trans-
mitted. The central station acknowledges the substation messages with Q = 1 (in the header byte), either with
a short message or a long message (= Acknowledgement is included in the central station’s user data
message).
The substation expects the next central station message to be acknowledged. If this is not the case, reply
handling is initiated for the message that was transmitted most recently.
NOTE
i There is no number of tries and no expect maintenance time.
In a worst-case scenario, the message is repeated ad infinitum, but is limited by the call-up timeout or call ups
with initialization (IN = 1, only if the monitoring direction fails).
If an acknowledgement is expected for a user data message and the call-up timeout responds, or a call-up
(short or long message) is received with IN = 1, then the transmit buffer is deleted and the user data messages
that have been sent are negatively acknowledged for the basic system element (behavior is the same as IEC
60870-5-101).
12.15.6.3 Acknowledgment Method – Wireless Relay Mode (IEC 60870-5-2)
Acknowledging Received Messages

The central station expects an acknowledgement for all information that is transmitted using the “Send-
Confirm” service. The firmware always confirms using ACK (function code = 0), irrespective of the FCB bit. The
FCB bit is used by the substation to detect repetitions.
Acknowledging Transmitted Messages

The substation always expects an acknowledgement from the central station for each message that is trans-
mitted. The central station acknowledges substation messages with an inverted FCB bit in the next call-up
(short message or long message).
Central station acknowledgement (= inverted FCB bit) is not carried out immediately after the information has
been transmitted by the substation, instead, it can occur at any time later on (in the normal polling cycle).

DC8-037-2, Edition 11.2020
12.15 SAT SK 1703
In a worst-case scenario, the message is repeated ad infinitum, but is limited by the call-up timeout or
“normalizing the link layer”.
If an acknowledgement is expected for a user data message and the call-up timeout responds, or “Normalizing
the link layer” is received, then the transmit buffer is deleted and the user data messages that have been sent
are negatively acknowledged for the basic system element (behavior is the same as IEC 60870-5-101).
12.15.6.4 Failure Monitoring in the Remote Terminal Unit

The interface is monitored in the substation by monitoring for cyclical station interrogation. The monitoring
time must be set in the substation using the parameter Call monitoring time.
The monitoring time in the substation must be set sufficiently high, so that this does not inadvertently elapse
when transmitting large quantities of data from other substations (for example, during general interroga-
tions).
With failed interface, data to be transmitted is stored in the data storage on the basic system element (BSE) of
the substation until these are deleted by the dwell time monitoring or can be transmitted to the central
station.
NOTE
i • The call timeout is only retriggered in the “SK 1703 slave” operating mode for messages (from the
master) with IN = 0. This causes the call timeout to respond if the monitoring direction fails, but the
command direction is intact.
• The call timeout is only triggered in the “wireless relay” operating mode when the FCB bit is changed.
12.15.6.5 Acquisition of Events

Data that is supposed to be transmitted from the substation to the central station is stored in the substation
until transmission.
Message from the Substation and the Master Station

Messages from the substation to the central station are only transmitted with station interrogation. A quick-
check procedure for speeding up the transmission of data is not implemented.
12.15.6.6 General Interrogation, Substation Interrogation

The general interrogation function (substation interrogation) is used for updating the central station after the
internal station initialization, or after the central station has detected a loss of information. The function
“general interrogation” of the master station requests the substation to transmit the actual values of all its
process variables.
GI Request in Receive Direction

A GI request in receive direction is always converted into a compliant GI request “to all” (CASDU = 0xFFFF).
All GI-compatible data is transmitted (in transmit direction).
Reason: If a GI request is transmitted to selective components in the SK 1703, then it is passed on to Param-
eter M37 most of the time. If another SK 1703 is connected to the site of components, the GI request
normally forwards these onto the connected components.
If a GI request is received during when a general interrogation is running, then this general interrogation is
retriggered.
For information handling during a general interrogation, see information handling section.
GI Request in Transmit Direction

The parameter comp-no. of the remote station is always used for the GI request as a target compo-
nent number.

DC8-037-2, Edition 11.2020
12.15 SAT SK 1703

The time information in the SICAM A8000 system consists of the date and daylight saving time/standard time
detection alongside the time itself. This information is only transmitted to the SK 1703 systems on request, so
the time master component number (radio clock DCF77) must be known to the protocol element (parameter
comp-no. of time master).
In addition, the type of time synchronization for the automation unit must be parameterized (parameter
remote time synchronization).
The following variants are supported by the protocol element:
• Non, or the AU is synchronized locally
[dw_PCBSA0b, 1, --_--]
– The SK 1703 master cannot send any time information as it is a “no time” plant or
– The automation unit is “time synchronized” by a local radio clock, by NTP or via another communica-
tion method
• Remote synchronization
[dw_PCBSA0b_1, 1, --_--]
The time of the connected automation unit is set as well as synchronized by the SK 1703 master. Synchroniza-
tion, which is also called remote synchronization in the SK 1703 is used to ensure long-term accuracy
(compensating for quarz inaccuracy).
Time setting and synchronization

The clocks are set and synchronized in the SICAM A8000 system with the internal SICAM A8000 “Time
synchronization” data format (FC = 156 matches the type identifier = 103 according to IEC 60870-5-101).
This data format contains the following:
• 4-octet time (hour, minute, millisecond)
• 3-octet time (year, month, day, day of the week)
• Daylight saving time/standard time identifier

This information is transmitted in the SK 1703 system using various system messages (data type = 0).

DC8-037-2, Edition 11.2020
12.15 SAT SK 1703
Description QB# QW# Time information Transmission

Time synchroniza- 0 4 Hour, minute • when changing the time for DCF77
tion command
• going restart information from FtbK
• going real-time error message from
FtbK
Response message 0 6 Year, month, day, • only on request from DCF77
for date day of the week
Response message 0 5 Daylight saving • only on request from DCF77
for time time/standard time
identifier
Remote synchroniza- 31 0 1/100 seconds periodic from SK 1703 master (every
tion minute)
FtbK ...... Error message for adjacent components

In addition, all messages are only transmitted spontaneously or on request, except for “remote synchroniza-
tion”.
NOTE
i • If a substation supposed to be time set by the SK 1703 system, then this will only take place after
– going restart information (bit 0) for the FTbK
– going real-time information (bit 5) for the FTbK
• The time setting message is always transmitted from the SK 1703 system at the 10th second.
The protocol element expects “time setting” once the system has restarted if the SK 1703 automation unit is
provided with a time (parameter remote time sychronization).
If the comp-no. of time master is parameterized (uneven value of 255), then the protocol element also
expects the response message for the date. This is requested for data/time using an interrogation message,
which is transmitted to the master after the automation unit has restarted.
NOTE
i The daylight saving time/standard time identifier is automatically determined from the parameterized
Daylight saving time rule.
All expected messages must be received within 50 seconds after receipt of the first message. In addition,
remote synchronization must also occur 50 seconds after receipt of the time setting message at the latest.
The internal SICAM A8000 “time synchronization” systems is always forwarded when remote synchronization
is received.
If the protocol element detects an error in the time setting process, then a real-time fleeting contact (bit#5 in
the error message for adjacent components with status = 1 and status = 0) is generated for the time/date, as
well as an interrogation message for the radio clock’s parameterized component number.

DC8-037-2, Edition 11.2020
12.15 SAT SK 1703
Time setting process after restarting the entire automation unit

The protocol element monitors whether the internal clock was set after 3 minutes during the relevant parame-
terization. Time setting process:
[dw_PCBSA0_timesync, 1, en_US]
➊ Error message for adjacent components with a restart fleeting contact or a real-time fleeting contact
➋ Interrogation message for time/date (optional)
➌ Remote synchronization
➍ Time setting message
➎ Response message for date (optional)
1) Forwarding the time synchronization message on the BSE with the received time information.
2) Forwarding the time synchronization message to the BSE with second:millisecond is determined by
the remote synchronization message as well as the date + hour + minute from the clock inside the firm-
ware.
If the protocol element has not been set after 180 seconds then a new time setting process is requested (real-
time fleeting error contact, interrogation message for time/date) (see above for the process).
This product is carried out repeatedly until the automation unit time has been set.
Time setting process after a selective protocol element restart

As the basic system elements are back in operation after a selective restart, the time is also set for the automa-
tion unit. If the time for the protocol element is set within 120 seconds, then no other actions will be set by
the protocol element. If the protocol element time has not been set then a new time setting process is
requested (real-time fleeting error contact, interrogation message for time/date).
Time setting process after a going real-time error in the SK 1703
[dw_PCBSA0_timesync_error, 1, --_--]
➊ Time setting
➋ Remote synchronization

DC8-037-2, Edition 11.2020
12.15 SAT SK 1703
Monitoring
• If remote synchronization is not received within 60 seconds after the time setting message is received,
the time setting message is discarded and a new time setting process is requested.
• If the time of the protocol element has been set, then a max. discrepancy of ±2 seconds is tolerated every
time a remote synchronization message arrives.
If there is deemed to be a large time discrepancy, then another time setting process is triggered.
Remote Synchronization
Substation time synchronization can be carried out via the serial communication line, which is controlled by
the central station protocol element.
Remote synchronization is transmitted (provided that remote synchronization is used)
• spontaneously after the time setting process inside the AU
• cyclical, once a minute

In the case of remote synchronization, an interface check message is transmitted from the central station
protocol element with time information (= remaining time in the minute) as “system messages unacknowl-
edged for all” (or even “acknowledged for all” for redundant configurations) to the connected substations (see
also “data/systems unacknowledged for all”).
If the function is released, this message is transmitted to the substations depending on the baud rate that has
been set as soon as possible to the end of the ongoing minute (typically between the 50th and 55th second)
high-priority. The transmission period is selected in such a way that multiple transmissions can be sent out in
full prior to changing the minute.
The remaining time in the minute (in units of 10 ms) is transmitted as time information.
The substation doesn’t carry out a runtime correction, as the central station has already carried it out.
Example of RT remote synchronization message (= interface checking message), unbundled:
[dw_PCBSA0_remote_timesync, 1, en_US]

DC8-037-2, Edition 11.2020
12.15 SAT SK 1703
*) 16-bit time information for RT remote synchronization

0 = Remote clock synchronization is deactivated
5999 .. 1 time information for remote clock synchronization (= remaining time in the minute in n ⋅ 10 ms);
5999 = Start of the minute
1 = End of the minute
The remaining time in the minute is entered into the message with the value 0 (this remaining time
information is not forwarded from the substation protocol element) for as long as the time in the central
station has not been set.
12.15.6.8 Command Messages Selective to a Substation

sion in progress.
If the reaction of the substation to a transmitted message is to be acquired quickly by the central station, a
demand (parameterizable station-selective continuous interrogation) can be carried out from the central
station. This station-selective interrogation is retriggered by further messages to the same station (message
configured with interrogation) or canceled by messages to other stations.
12.15.6.9 Counter Interrogation Message

The SK 1703 counter interrogation message is converted to the SICAM A8000 “counter interrogation require-
ment” (FC:=153) system message.
The transmission from the SK 1703 master takes place in an alternative way:
• Station-selective (and therefore acknowledged)
• Acknowledged for all (only available for the SK 1703 multi-point traffic slave)
• Unacknowledged for all
The counter interrogation message from the SK 1703 to SICAM A8000 can be set via a parameter-settable
assignment. There are 5 possible assignments:
IEC SK 1703
IEC-FRZ IEC-RQT Restore identifier Group number Select
0 to 3 0 to 63 0 to 4 0 to 3 0, 1
IEC-FRZ = Freeze identifier

0 Query (no freeze or reset)
2 Counter freeze with reset
3 Reset counter
IEC-RQT = Interrogation qualifier
0 No counter interrogation
1 Request counter group 1
2 Counter interrogation for group 2
5 General request counter
6 to 31 Reserved - compatible section
32 to 63 Reserved - private section
Freeze identifier
0 Transmit
1 Freeze without transmitting

DC8-037-2, Edition 11.2020
12.15 SAT SK 1703
2 Freeze with transmitting

3 Freeze with transmitting or switching off spontaneous
transmission for MK 1703
4 Do not convert message
This assignment table only applies in the receive direction.
• The IEC counter interrogation command wis always distributed to all inside the AU
(CASDU = FFFF or Reg# = 255 and comp# = 255).
NOTE
i A counter interrogation cannot be carried out in the transmit direction!
12.15.6.10 Acquisition of Transmission Time

Transmission time acquisition for correcting time synchronization with the connected substations is not
supported by the protocol element (see also section Remote Synchronization, Page 1602.
12.15.6.11 Transmission Facilities “Modems”

The protocol element supports selected transmission facilities – for which the parameters are fixed. The trans-
mission facility is selected using the parameter Interface modem. Specific parameters can be customized
by selecting a freely definable transmission facility.
In most cases, transmission facilities only support specific transmission speeds or combinations of transmis-
sion speeds in transmit/receive direction, you can find these in the descriptions for the transmission facility.
The transmission speed must be set using the parameter Baud rate.
predefined or if modified parameters are to be used for predefined transmission facilities. To do this, you need
to set the parameter Interface modem to free definable. Only then are all supported parameters
displayed and can be parameterized with the required values (refer to table with default parameters for trans-
mission facilities).
The following parameters are also available for adapting the protocol to the transmission medium that is used
and to the time behavior of the connected partner:
• Character monitoring time
• Idle monitoring time
• Call monitoring time (see section 12.15.6.2 Acknowledgement Procedure and section
12.15.6.3 Acknowledgment Method – Wireless Relay Mode (IEC 60870-5-2))
The character monitoring time is used for message interruption monitoring and message resynchronization in
receive direction. A message interruption is identified if the time between 2 bytes of a message is greater than
the set character monitoring time. In the event of a message interruption the on-going receive handling is
canceled and the message is discarded. After a message interruption has been identified a new message is
only accepted on the line in receive direction after an idle time.
The protocol element – insofar as the transmission facility (VFT channel) provides this signal on the receive
side – can evaluate the DCD interface signal and for example, use it for monitoring functions.

DC8-037-2, Edition 11.2020
12.15 SAT SK 1703
Preset parameters for transmission facilities
Transmission facility elec- RTS tp tv tn tdis DCD Tbo tsta tcl tcldl A_I T
trical [ms] [ms] [bit] [ms] unce b [s] y
inter- [ms] [ms] [ms]
face
SAT modem “4-wire RS-232 ON 0 0 3 35 YES 5 5 10 200 A I
transmission line” 334
SAT modem “2-wire RS-232 ↑↓ 0 30 3 35 YES 5 5 10 200 A I
SAT-DMS 335 RS-232 ON 0 0 5 0 NO 0 0 0 0 A I
SAT-DMS 336 RS-232 ↑↓ 0 50 5 35 YES 5 5 10 200 A I
Optical RS-232 ↑↓ 0 1 0 0 NO 0 0 0 0 A I
Radio digital RS-232 ↑↓ 30 100 11 50 YES 10 5 0 200 A I
Radio analog RS-232 ↑↓ 50 300 50 100 YES 10 5 0 200 A I
ms
Direct connection RS-485 ↑↓ 0 1 0 0 NO 0 0 0 0 A I
SAT modem “4-wire RS-232 ON 0 0 3 0 YES 5 5 10 200 A I
SAT modem “2-wire RS-232 ↑↓ 0 1 0 0 NO 0 0 0 0 A I
SAT modem “2-wire RS-232 ↑↓ 0 1 0 0 NO 0 0 0 0 A I
Direct connection RS-232 ON 0 0 0 0 NO 0 0 0 0 A I
freely definable
Legend:
RTS .... ↑↓ = RTS is scanned for each message to control the modem's level scan (ON / OFF)
tp ......... Pause time (tp)
tv.......... Set_up_time (tv)
tn.......... Run-out time (tn)
tdis........ Disable time (tdis)
DCD....... DCD evaluation
tbounce.. Bounce suppression time (tbounce)
tstab ..... Stability monitoring time (tstab)
tcl.......... Continuous level monitoring time (tcl)
tcldly ..... Transmission delay if continous level (tcldly)
A_I......... Asynchronous_Isochronous
T............ Bit cycle (only for isochronous) (I=internal, E=external)
334 SAT-VFM, VFT, WTK, WTK-S, CE-0700

335 ring configuration
336 Ring configuration (AE remotely with SAT-VFT)
337 CE-0701
338 CE-0701 via modem
339 CE-0701 via Westermo TD-32
340 CE-0701 via Westermo GD-01

DC8-037-2, Edition 11.2020
12.15 SAT SK 1703
[dw_PCBST0_timing, 1, en_US]
Figure 12-30 PCBST0 Timing
Legend:
RTS ……. Request to Send (switch on transmit part)
DCD …… Data Carrier Detect
TXD …… Transmit Data
RXD …… Receive Data
tdlyRTS ..... Runtime of the transmission system (switch on the time delay/time difference between the transmit
part (RTS ↑) and receiver ready (DCD ↑))
tp ………. Pause time (delay before the transmit part is switched off with RTS)
tv ………. Set-up time (transmit delay, after the transmit part has been switched on with RTS)
tn ………. Run-out time (switch off transmit level with RTS after message transmission is delayed)
tsw …….. Internal processing time
tsignal ….. Signal-transit time (depending on the transmission facility/transmission route used)

DC8-037-2, Edition 11.2020
12.15 SAT SK 1703
tbounce …. Detection time after a positive/negative DCD edge (DCD debouncing)

tstab ….… Stability monitoring time - the new DCD status is only used once the stability monitoring time has
elapsed for message synchronization
tcl …....... Continuous level monitoring time
tcldly …… Transmit delay at level - another message transmission is carried out at continuous level once the
transmission delay has elapsed at the latest
tdis …….. Disable time of the receiver after receiving a message (for suppressing the erroneous characters
during level scanning)
➊ DCD valid
[dw_PCBST0_timing_2xRTS, 1, en_US]
Figure 12-31 PCBST0 Timing 2 x RTS
Legend:
RTS ……. Request to Send (switch on transmit part)
DCD …... Data Carrier Detect (receive signal level)
TXD …… Transmit Data
RXD …… Receive Data
tdlyRTS .... Transmission system lead time (switch on the time delay/time difference between the transmit part
(RTS ↑) and receiver ready (DCD ↑))
tp ……… Dead time (delay before the transmit part is switched off with RTS)
tv ……… Lead time (transmit delay after the transmit part has been switched on with RTS)
tn ……… Post-trigger time (switch off transmit level with RTS after message transmission is delayed)

DC8-037-2, Edition 11.2020
12.15 SAT SK 1703
tpz2RTS … Pause between 2 immediate RTS keyings

tsignal ….. Signal-transit time (depending on the transmission facility/transmission route used)
tbounce …. Detection time after a positive/negative DCD edge (DCD debouncing)
tdis ……. Receive a reclaimed time after receiving the message (for suppressing erroneous characters during
level scanning)
➊ The pause must be set between 2 RTS keyings that are carried out consecutively in the master station in
such a way that a level change ➋ is clearly detected in the substation.
The special timing affects multiple transmissions for “messages to all” or if a station change
is made (for example, acknowledgement for station n, next call-up to station n).
➌ If RTS is not used for carrier switching (transmission route is fixed and gated), then the pause must be 33-bit
between 2 messages.
12.15.6.12 General
Process Image
The protocol element carries out a processing image for the following SK 1703 information formats (in the
transmit and receive direction):
• 16 single-point information items
• 8 double-point information items
• 4 double-point information items with command return information

The process image is used for
• Spontaneity of individual information items in receive direction from the received group format
(Example: 16 single-point information items)
• For converting IEC single objects to SK 1703 group formats

(16 single-point information items, 8 double-point information items, 4 double-point information items +
command return information)
• For GI handling in transmit direction

(Example: 16 IEC single-point information items → 1 SK 1703 information message)
• Emulating the data if component X fails
Information Handling in the Transmit Direction

All information items that are used are marked as invalid (I = 1) and as not topical (NT = 1) after restarting the
protocol element. The information image is updated via the general interrogation inside the AU.
The update for the individual SK 1703 information message is is monitored using the timeout (selectively,
depending on the source value).
The information state (state + invalid identifier) is updated in the process image but not transmitted for each
information that is used that isn't current.
If the last information for the SK 1703 information message is updated, then the update timeout is stopped
and the information message is transmitted with GI = 1 and the current I bit. If the update timeout elapses,
then all information for the information message are set to current and transmitted with GI = 1 and I = 1.
If a state changes made to information and not all information has been updated for the SK 1703 information
message, then the information message is transmitted (S = 1, I = 1).
NOTE
i The update timeout must be adjusted for the entire general interrogation runtime.

DC8-037-2, Edition 11.2020
12.15 SAT SK 1703
If a GI request is received then all information items that have been defined in transmit direction are marked
with a GI trigger. A SK 1703 information message is only transmitted once all information has been updated
for the relevant source value number.
The update is monitored using the timeout (selectively depending on the source value number). If the timeout
elapses, then the missing information is marked as invalid (I = 1), but the information message is still trans-
mitted with GI = 1.
If an information state change is produced while general interrogation is running inside a value number, then
it is transmitted with S = 1 and the current value number I bit. If the GI trigger has been set for this informa-
tion, then the GI bit is also set.
12.15.6.13 Error messages

Only the error message for adjacent components (DA = 0, QB# 20, QW# 0), and the error
message for non-adjacent components (DA = 0, QB# 0, QW# 9) is supported.
The SK 1703 message error message for adjacent components, and error message for non-
adjacent components is converted by the protocol element to the SICAM A8000 error message (diagnos-
tics handling message: Function code 148 / information code = 4).
Implementing error assignment error message for adjacent components SK1703 → SICAM A8000
[dw_ftbk_SK-A8000, 1, en_US]

DC8-037-2, Edition 11.2020
12.15 SAT SK 1703
Implementing error assignment error message for non-adjacent components SK1703 → SICAM
A8000
[dw_ftnbk_SK-A8000, 1, en_US]
The SICAM A8000 error message (message for diagnostics treatment: Function code 148 / information code =
4) is converted from the protocol firmware to the message “message for adjacent components” or to the “error
message for non-adjacent components”.

DC8-037-2, Edition 11.2020
12.15 SAT SK 1703
Implementing error assignment error message for adjacent components SICAM A8000 → SK1703
[dw_ftbk_A8000-SK, 1, en_US]

DC8-037-2, Edition 11.2020
12.15 SAT SK 1703
Implementing error assignment error message for non-adjacent components SICAM A8000 →
SK1703
[dw_ftnbk_A8000-SK, 1, en_US]
12.15.6.14 Component X Failure

Component failure in multi-hierarchical configurations can be reported from the component that has detected
it using the system message component X failure.
The component failures are reported in the SK 1703 due to the topology.
When the component X failure message is received, all messages that have been entered in SIP message
address conversion (OPM II) and receive direction for the failed components by the central station protocol
element (except for commands, setpoints and 2 to 57 byte REKO messages) are emulated as failed.
The GI feature of a type identifier is determined in the AU configuration.
The messages are emulated with
• Cause of transmission: spontaneous or interrogated

If the impending failure is detected (SK 1703 message I bit in the process image = 0), then the NT bit is
always emulated with the cause of transmission = spontaneous (= 03); if the failure had already been
detected (SK 1703 message I bit in the process image = 1), than the NT bit is emulated with the cause of
transmission = interrogated (= 20).
• Quality code: NT-Bit = 1
• Value: last value received

(from the protocol firmware process image)

DC8-037-2, Edition 11.2020
12.15 SAT SK 1703
12.15.6.15 Measured Values, Setpoint Values

A distinction is drawn between the following formats in the SICAM A8000 system:
• Normalized (measured value, setpoint)
• Scaled (measured value, setpoint)
• Short floating point (measured value, setpoint)
• Integrated total (31-bit + sign)
A distinction is drawn between the following formats in the SK 1703 system:
• 10x binary value formats (8-bit + sign, 11-bit + sign)
• 8x BCD value formats
• 1x short floating point
In addition, specially coded values are used for representing specific statuses (overflow, faulty) which are now
shown as their own quality bits in the SICAM A8000 data format.
A linear adaptation can be parameterized in the transmit and receive direction for each data point. Linear
adaptation is determined using the following parameters:
• X_0%
Lower limit of the range of values used in the external (protocol-specific) format. The corresponding
internal value is configured at Y_0%.
• X_100%
Upper limit of the range of values used in the external (protocol-specific) format. The corresponding
internal value is configured at Y_100%.
• Y_0%
Lower limit of the range of values used in the selected internal format. The internal format is specified by
the TI (type identification). The corresponding external value is configured at X_0%.
• Y_100%
Upper limit of the range of values used in the selected internal format. The internal format is specified by
the TI (type identification). The corresponding external value is configured at X_100%.
The parameters X_0% and X_100% for linear adaptation are also used as replacement values for faulty float
values (TI:=36 or 50) in transmit direction. The parameters Y_0% and Y_100% for linear adaptation are also
used as replacement values for faulty values in receive direction.
Conversion in Transmit Direction
NT = 1 or IV = 1 → I (IE) = 1
IV = 1 → Binary values: 2n – 1
BCD values: All BCD value bits are set
Floating point:X0, if SIACM A8000 value is positive
X100, if SIACM A8000 value is positive
OV = 1 → Binary values: 2n – 2
BCD values: All BCD value bits
Floating point: X0, if SIACM A8000 value is positive
SICAM A8000 value > SK 1703 format (if no adaptation has been used)
→ Binary values: 2n – 2
BCD values: All BCD value bits
Floating point: X0, if SIACM A8000 value is positive

DC8-037-2, Edition 11.2020
12.15 SAT SK 1703
Limitation: Normalized values (TI:=34 or 48) cannot be converted to BCD values or floating- point values.
Linear adaptation
Linear adaptation can be selectively parameterized for each value (measured value, setpoint).
Adaptation is activated if Y_0% or Y_100% has been parameterized as not 0.
Value SK 1703 = k ⋅ value SICAM A8000 + d
whereby:
k = (X100 – X0) / (Y100 – Y0)
d = X0 – k ⋅ Y0
The following also applies:

Value SICAM A8000 < Y0 → value SK 1703 = X0, OV = 1
Value SICAM A8000 > Y100 → value SK 1703 = X100, OV = 1
[dw_mv_A8000-SK, 1, en_US]
Figure 12-32 PCBST0 Measured Value Conversion in Transmit Direction

DC8-037-2, Edition 11.2020
12.15 SAT SK 1703
X0, X100 .... SK 1703 value (example: X0 = -2000, X100 = 2000)

Y0, Y100 ... SICAM A8000 value (example: normalized, Y0 = -1, Y100 = 1)
X_0% and Y_0% must be parameterized to 0 for unipolar measured values.
Conversion in the Receive Direction
I (IE) = 1 → NT = 1
Pseudo tetrads for BCD values → IV = 1, SICAM A8000 value = f (sign)
Value = 2n – 1 for binary → IV = 1, SICAM A8000 value = f (sign)
values → OV = 1, SICAM A8000 value = f (sign)
Value = 2n – 2 for binary
values
SK 1703 value > SICAM A8000 format (if no adaptation has been used)
→ OV = 1, value = f (sign)
f (sign): Y0, if the sign has been set
Y100, if the sign has not been set
Limitation: BCD values and floating point values cannot be converted to normalized values.
Linear adaptation
Linear adaptation can be selectively parameterized for each value (measured value, setpoint).
Adaptation is activated if X_0% or X_100% has been parameterized as not 0.
Value SICAM A8000 = k ⋅ value SK 1703 + d
whereby:
k = (Y100 – Y0) / (X100 – X0)
d = Y0 – k ⋅ X0
The following also applies:

Value SK 1703 < X0 → value SICAM A8000 = Y0, OV = 1
Value SK 1703 > X100 → value SICAM A8000 = Y100, OV = 1

DC8-037-2, Edition 11.2020
12.15 SAT SK 1703
[dw_mv_SK-A8000, 1, en_US]
Figure 12-33 PCBST0 Measured Value Conversion in Receive Direction
X0, X100 .... SK 1703 value (example: X0 = -2000, X100 = 2000)

Y0, Y100 ... SICAM A8000 value (example: normalized, Y0 = -1, Y100 = 1)
X_0% and Y_0% must be parameterized to 0 for unipolar measured values.
12.15.7 Message Conversion In Transmit Direction (SICAM A8000 → SAT SK 1703)
In transmit direction a type identifier can be converted to various data types .

Example: <TI:=35> .. Measured value, scaled → Data type = 1 (8-bit + sign)
<TI:=35> .. Measured value, scaled → Data type = 2 (11-bit + sign)
For commands in transmit direction a command output time in SAT SK 1703 format must be provided.
The command output time can be set in the process technique of the OPM II between 0.1 and 310 s. However,
this time is only used for IEC commands with QOC = without additional definition; the command
output time for the whole AU is provided for IEC commands with QOC = short/long.

DC8-037-2, Edition 11.2020
12.15 SAT SK 1703
NOTE
i Converting the parameterized time may lead to rounding errors as they are illustrated in the SAT SK 1703
format with the factor (1 to 31) and the time base.
For double commands (TI:=46 or 47) only one entry in the SIP telegram address conversion is used. The para-
meterized SK 1703 command number applies to the ON or OFF command status (can be parameterized). The
command number for the complementary command output is automatically the next command number.
Example:
CASDU1 =1 SC# 10
CASDU2 =2 DT = 11
IOA1 =1 SB# 0
→
IOA2 =0 SV# 0
IOA3 =0 Bit# 2
TI = 46 Comm-Stat = ON
ON command → bit# 2 (= command#)

OFF command → bit# 3 (= command#)
NOTE
i If double commands are used, then the bit# 0, 2, 4 to 14 can be parameterized.
12.15.7.1 Commands
The address conversion is parameterized using SICAM TOOLBOX II, OPM II (object-orientated process data
manager). To do this, in the “SIP message address conversion”, the detailed routing type firmware /
Trans_command is provided with the following entries.
Parameter Meaning
IOA1
IOA2
IOA3

C Component number
0 to 254
DT Data type
1 to 30
BD Printed circuit board assembly number
0 to 255
V Value number
0 to 255

DC8-037-2, Edition 11.2020
12.15 SAT SK 1703
Parameter Meaning
bit Bit number (Command number in the SK 1703)
• 0 to 15 (for single commands <TI:=45>)

• 0, 2 to 14 (for double commands <TI:=46> and regulating step commands
<TI:=47>)
IEC-command_state Assignment between the IEC command status and the SK 1703 command bit (=
SK 1703 month number four double commands and regulating step commands
• NOT USED (for single commands <TI:=45>)

• OFF (for double commands <TI:=46> and adjusting step commands
<TI:=47>)
• ON (for double command <TI:=46> and adjusting step commands <TI:=47>)
command_output_time_S SK 1703 command output time for commands with a command qualifier = no
K 1703 additional definition
0.1 to 310 s
12.15.7.2 Binary Information, Values (Measured Values, Integrated Totals)

manager). To do this, in the “SIP message address conversion”, the detailed routing type firmware / Transmit
detailed routing is provided with the following entries.
Parameter Meaning
IOA1
IOA2
IOA3

• Transformer tap position value <TI:=32>
• Bit string 32 Bit <TI := 33>
• 31-bit integrated total + sign <TI:=37>
• Setpoint command, normalized <TI:=48>
• Setpoint command, scaled <TI:=49>
• Setpoint command, short floating-point number <TI:=50>
• 32-bit bitstring <TI:= 51>
• Payload container <TI:= 142>
C Component number
0 to 254
DT Data type
1 to 30
0 to 255

DC8-037-2, Edition 11.2020
12.15 SAT SK 1703
Parameter Meaning
V Value number
0 to 255
bit Bit number (indication number in SK 1703)
• 0 to 15 for 16 single-point information items (DFK = 03)

• 0 to 7 for 8 double-point information items (DFK = 43)
• 0 to 3 for 4 double-point information items + command return information
(DFK = 13)
• 0 for all other formats
RT-DT Real-time data type
• 1 to 30
• 31 = not used
Only to be parameterized if the transmission is supposed to take place with two
data flows (= NEZ + EZ)
12.15.7.3 Two Data Streams (NRT + RT) in Transmit Direction

The protocol element supports the option of transmitting data points according to the concept of the two data
streams – without time (= NRT) and with time (= RT) – to the central station. If this function is used, please
note the following points:
• Both pieces of information (NRT + RT) are transmitted in a message (= chained), irrespective of the
message length that has been set.
• Prioritization is not present in the conventional sense of NRT and RT data.
• Binary information:
The information items that have been used for a SK 1703 information message (value number) must also
always be parameterized in real time.
• The DT parameter must always be parameterized for a NRT data type.
12.15.8 Message Conversion In Receive Direction (SICAM A8000 ← SAT SK 1703)
The “QOC” (command output time) is parameterized for each IEC command.
If SAT SK 1703 commands are converted to double commands (TI:=46 or 47), then the SAT SK 1703 is
converted to SICAM A8000 (IEC), just like in the transmit direction.
In receive direction a data type can be converted only to one type identifier.

DC8-037-2, Edition 11.2020
12.15 SAT SK 1703
Example: Data type DT = 1 ( 8 Bit + sign) → <TI:=34>

Data type DT = 2 (11 Bit + sign) → <TI:=35>
12.15.8.1 Commands
manager). In “SIP telegram address conversion”, the detailed routing type firmware / Rec_command is
provided with the following inputs for this purpose.
Parameter Meaning
IOA1
IOA2
IOA3

C Component number
0 to 254
DT Data type
1 to 30
0 to 255
V Value number
0 to 255
bit Bit number (Command number in the SK 1703)
• 0 to 15 for single commands <TI:=45>

• 0, 2 to 14 for double commands <TI:=46> and regulating step commands
<TI:=47>
IEC-command_state Assignment between the IEC command status and the SK 1703 command bit (=
SK 1703 month number for double commands and regulating step commands
• NOT USED (for single commands <TI:=45>)

• OFF (for double commands <TI:=46> and regulating step commands
<TI:=47>)
• ON (for double command <TI:=46> and regulating step commands
<TI:=47>)
IEC_quali- Command output time
fier_of_command
• no definition
• short (= short command execution time)
• long (= long command execution time)
12.15.8.2 Binary Information, Measured Values

manager). In “SIP telegram address conversion”, the detailed routing type firmware / Rec_FR is provided with
the following inputs for this purpose.

DC8-037-2, Edition 11.2020
12.15 SAT SK 1703
Parameter Meaning
IOA1
IOA2
IOA3

• Transformer tap position value <TI:=32>
• Bit string 32 bit <TI:= 33>
• 31-bit integrated total + sign <TI:=37>
• Setpoint command, normalized <TI:=48>
• Setpoint command, scaled <TI:=49>
• Setpoint command, short floating-point number <TI:=50>
• 32-bit bitstring <TI:= 51>
• User data container <TI:= 142>
C Component number
0 to 254
DT Data type
1 to 30
0 to 255
V Value number
0 to 255
bit Bit number (indication number in SK 1703)
• 0 to 15 for 16 single-point information items (DFI = 03)

• 0 to 7 for 8 double-point information items (DFI = 43)
• 0 to 3 for 4 double-point information items + command return information
(DFI = 13)
• 0 for all other formats
ind_Attrib Information attribute (auxiliary information for indication conversion):
• Status: Information state

• SF: Breaker Tripping
• SL: Switching operation in progress
SL + SF is only permitted for 4 double-point information items with command
return information!

DC8-037-2, Edition 11.2020
12.15 SAT SK 1703
Parameter Meaning
12.15.9 Message Format Conversion SAT SK 1703 ⇔ IEC 60870-5-101/104
The following table describes how the SAT SK 1703 message formats (external data block format) are imple-
mented according to IEC 60870-5-101/104 and vice versa.
If a type identifier is not specified for a SAT SK 1703 data format (–), this format is not supported!
SAT SK 1703 standard message formats SICAM A8000 data block format
(IEC 60870-5-101/104)
Designation DFK TI (type identification)
[H]
Binary values that are not in real time
8-bit binary value and sign 00H 34, 35, 36, 37, 48, 49, 50
16-bit binary value 20H
BCD values that aren’t in real time
4 decades BCD 01H 35, 36, 37, 49, 50
3.5 decades, BCD + sign 01H
Decimal point control message for display output, 4 values –
01H
8 decades BCD 11H 35, 36, 37, 49, 50
Decimal point control message for display output –
11H
2 decades BCD 21H 35, 36, 37, 49, 50
Transformer tap position value 21H 32
6 decades BCD 31H 35, 36, 37, 49, 50
Bitstrings that aren’t in real time
Bit string 16 bit 02H 33, 51
Bit string 32 bit 12H

DC8-037-2, Edition 11.2020
12.15 SAT SK 1703
(IEC 60870-5-101/104)
Messages that aren’t in real time
16 single-point indications 03H 30
16 error messages 03H
4 double-point indications (MG/MA) with command feedback 13H 31
16 single-point fleeting indications 23H –
1 indication 33H –
8 double-point indications (MG/MA), status stored 43H 31
Commands that aren’t in real time
1 Single command (from a group of 16 commands) 04H 45, 46, 47
8 pieces of status information in control direction 14H –
Combination messages that aren’t in real time - Binary value + indications
8-bit binary value + sign and 06H –
4-bit limiting-value indication and
2-bit gradient indication
11-bit binary value + sign and 16H –
4-bit limiting-value indication and
Transparent data that isn’t in real-time
16-bit transparent data 07H 33, 51
Floating point data that isn’t in real time
32-bit floating point value 08H 35, 36, 37, 49, 50
Computer link formats that aren’t in real time
32-bit binary value + 2 status byte 0FH –
32 bit binary value + 3 status byte 1FH –
2-57 byte data 3FH –
Data acknowledgment 4FH –
Real time binary values
15-bit binary value and sign A0H 34, 35, 36, 37, 48, 49, 50
16-bit binary value A0H
31-bit binary value and sign B0H 34, 35, 36, 37, 48, 49, 50
32-bit binary value B0H
7-bit binary value and sign C0H 34, 35, 36, 37, 48, 49, 50
8-bit binary value C0H
23-bit binary value and sign D0H 34, 35, 36, 37, 48, 49, 50
24-bit binary value D0H
Real time BCD values
4 decades BCD 81H 34, 35, 36, 37, 48, 49, 50
8 decades BCD 91H 35, 36, 37, 49, 50

DC8-037-2, Edition 11.2020
12.15 SAT SK 1703
(IEC 60870-5-101/104)
2 decades BCD A1H 35, 36, 37, 49, 50
1.5 decades, BCD + sign A1H
Transformer tap position value A1H 32
6 decades BCD B1H 35, 36, 37, 49, 50
5.5 decades, BCD + sign B1H
Real-time bitstrings
Bit string 16 bit 82 33, 51
Bit string 32 bit 92
Real-time indications
16 single-point indications (GI-format) 83H –
8 double-point indications (Z/D) (GI format) 83H
4 double-point indications (Z/D) with command feedback (GI 83H –
format)
16 single-point indications 83H 30
16 error messages 83H 30
8 double-point indications (Z/D) 83H 31
8 double-point indications (MG/MA) 83H 31
4 indications (Z/D) with command return information 83H 31
4 indications (MG/MA) with command feedback 83H 31
1 single-point indication (spontaneous format) B3H –
1 double-point indication (Z/D) (spontaneous format) B3H
1 double-point indication (Z/D) with command feedback B3H –
(spontaneous format)
16 single-point indications (1 ms format) E3H 30
8 double-point indications (Z/D) (1 ms format) E3H 31
4 indications (Z/D) with command feedback (1 ms format) E3H 31
Real-time commands
1 single command 84H 45, 46, 47
1 single command (1 ms) A4H 45, 46, 47
Real-time combination messages - Binary value + indications
8-bit binary value + sign + 86H –
4-bit limiting-value indication +
11-bit binary value + sign + 96H –
4-bit limiting-value indication +
Real-time transparent data
16 bit transparent data (1 ms format) A7H 33, 51
Real-time floating point data
32-bit floating point value 88H 35, 36, 37, 49, 50
Real-time computer link formats
32-bit binary value + 2 status byte 8FH –
32 bit binary value + 4 status byte AFH –

DC8-037-2, Edition 11.2020
12.15 SAT SK 1703
(IEC 60870-5-101/104)
Real-time system messages
Time setting acknowledgement control message B3H –
Time setting acknowledgement data message B3H –
Time change message B3H –
Period messages B3H –
System messages
Interface testing message 05H –
Error message between 2 adjacent components 05H ✓
Error interrogation message 05H ✓
Response to error interrogation message 05H ✓
GI request message 05H ✓
Information refresh request 05H ✓
Time setting message 05H ✓ 341
Interrogation message for time and date 05H ✓ 342
Response message for time 05H ✓ 341
Response message for date 05H ✓ 341
Counter interrogation message 05H
✓ 341
Error interrogation table acknowledgment 05H
✓
Error message between non-adjacent 05H
Components
✓ 341
message Component X failure 05H
✓
Remote reset 05H
–
Read interrogation message memory 05H
–
Read response message memory 05H
–
Periphery control message 05H
Down line loading messages
Start 15H ✓
End 15H ✓
E 15H ✓
G 15H ✓
WPI 15H ✓
WPE 15H ✓
WP 15H ✓
DP 15H ✓
Y (re-triggering session time) 15H ✓
Response message DATA 15H ✓
Response message END 15H ✓
Legend:
DFK ... data format qualifier
TI ....... type identification
341 in receive direction only

342 only in transmit direction

DC8-037-2, Edition 11.2020
12.15 SAT SK 1703
Overview of Supported Type Identification
Process information in monitoring direction

(station-specific parameter; specifying all type identifiers that have been used, either with X (if used in
standard direction), or R (if used in opposite direction), or B (if used in both directions))
<13> := Measured value, floating-point number M_ME_NC_1
<14> := Measured value, floating-point number with time tag M_ME_TC_1
<20> := Blocked single-point information with status change display M_PS_NA_1
<30> := Single-point indication with time tag CP56Time2a M_SP_TB_1

DC8-037-2, Edition 11.2020
12.15 SAT SK 1703
<36> := Measured value, floating-point number with time tag CP56Time2a M_ME_TF_1
M_EP_TF_1
CP56Time2a
Either the ASDUs <2,4,6,8,10,12,14,16,17,18,19> or <30- 40> can be used.
NOTE
i Only type identifiers are used with time tags CP56Time2a inside the AU.
Process information in monitoring direction (private section)
<142> := User data container
<143> := real-time system indication
Process information in command direction

standard direction), or R (if used in opposite direction), or B (if used in both directions)
<50> := Set point command, floating-point number C_SE_NC_1
<51> := 32-bit bitstring C_BO_NA_1

(station-specific parameter; inputting X, if it's used)

DC8-037-2, Edition 11.2020
12.15 SAT SK 1703

<100> := (General) interrogation command C_IC_NA_1
<102> := Poll C_RD_NA_1

<112> := Parameter for measured values, short floating-points P_ME_NC_1
File transmission
<122> := File directory poll, file selection, file poll, section poll F_SC_NA_1

DC8-037-2, Edition 11.2020
12.15 SAT SK 1703
<126> := File directory F_DR_TA_1
Assignments for type identifiers und cause of transmission between BSE and PRE
NOTE
i Only type identifiers are used with time tags CP56Time2a inside the AU.
Gray box = Combination of the type identifier and cause of transmission is not provided in the standard that is
specific to the application.
Empty box = Combination of the type identifier and cause of transmission is not used.
Indication of the combination of type identifier and cause of transmission:
X if used in the standard direction
R if used in the opposite direction
B if used in both directions

DC8-037-2, Edition 11.2020
12.15 SAT SK 1703
[dw_type_identification, 1, 1, --_--]

DC8-037-2, Edition 11.2020
12.15 SAT SK 1703
[dw_type_identification1, 1, 1, --_--]
1) “20” in the event of general interrogation

*) “Activation” it is also set for the GI bit that has been set in the SK 1703 data format in transmit direction
(irrespective of the data direction).

DC8-037-2, Edition 11.2020
12.16 ABB RP570/571
12.16 ABB RP570/571
12.16.1 Short Description
The protocol element is used for interfacing of telecontrol centers, front-ends and control systems by using
the ABB RP570/RP571 protocol in the multi-point traffic. The protocol element emulates one RP570/RP571
Slave in the dedicated line operation.
Configuration
[RP5U01a, 1, en_US]
Figure 12-34 Configuration ABB RP570/RP571
12.16.2 Functions
Communication of a substation with a central station
• Unbalanced multi-point slave according to RP570/RP571 specification in Leased-Line mode

RP5UT1 is substation (ABB RP570/RP571 Slave)
• Data acquisition by polling
• General interrogation, interrogation of integrated totals (counter values)
• Spontaneous transmission of commands and set points in command direction
• Spontaneous transmission of indications, measured values and integrated totals (counter values) in
monitoring direction
• Multi-hierarchical configurations possible (RP571 mode)
• Time synchronization over communication line
ment.

DC8-037-2, Edition 11.2020
12.16 ABB RP570/571

optional DCE
Balanced interface (V.11) RS-485 (2-wire) / RS-422 X2 → CM-0829 RXD, TXD, CTS, RTS, DCD, DTR, DSR/
(4-wire) asynchronous (CM-0819344) VCC, GND (for CM-08x9)
Optical interface (multimode fiber optic ring) X2 → CM-0821 RXD, TXD, CTS, RTS, DCD, DTR, DSR/
VCC, GND (for CM-0821)
Unbalanced interchange circuit (V.24/V.28) X6345 RXD, TXD, CTS, RTS, DCD, DTR, DSR,
NOTE

SICAM A8000 CP-8000/CPC80 RP5UT1 –
CP-802x/CPC80

SICAM AK 3 CP-2016/CPCX26 SM-2551/RP5ZA1 –
CP-2019/PCCX26 SM-0551/RP5ZA1
Legacy systems CP-20xx SM-2551/RP5ZA1 –
(SICAM AK CP-50xx SM-0551/RP5ZA1
SICAM TM CP-60xx SM-2541/RP5ZA1
SICAM BC)
Third-party system – – –


DC8-037-2, Edition 11.2020
12.16 ABB RP570/571

The Firmware is designed for the communication of SICAM A8000 system components and third-party
systems with the RP570/RP571 protocol, whereby SICAM A8000 emulates the functionality of one RP570/571
substation.
Transmission rate 50, 110, 150, 200, 300, 600, 1200, 1800, 2000, 2400, 4800, 9600
bits/s
Modulation PCM Byte asynchronous
Transmission method Half-duplex
Character frame • 1 Start bit
• 8 Data bit
• 1 Parity bit (even)
• 1 Stop bit
Character representation see DIN 66022
Bit transmit sequence LSB (least significant bit) is transmitted first
Message protection HA = 4
Message structure DIN 19244 (issue January 1986) with modifications
Message formats in monitoring direction (= SICAM A8000 transmit direction):
• INDICATION MESSAGE (IDM)
• INDICATION MESSAGE WITH STATUS (IDS)
• ANALOG VALUE MESSAGE (AVM)
• ANALOG VALUE MESSAGE WITH STATUS (AVS)
• DIGITAL VALUE MESSAGE (DVM)
• EVENT RECORDING MESSAGE FOR INDICATION (ERMI)
• EVENT RECORDING MESSAGE FAULT DISTANCE (ERMFD)
• PULSE COUNTER MESSAGE (PCM)
• PULSE COUNTER TELEGRAM (PCT)
• TERMINAL STATUS (TSTA)
• TERMINAL EVENT (TEV)
• CYCLE COMPLETE RESPONSE PRIORITY LEVEL 1 (CCR 1)
• CYCLE COMPLETE RESPONSE PRIORITY LEVEL 2 (CCR 2)
• POLLING REQUEST INSTRUCTION (PRI)
• POSITIV ACKNOWLEDGE (ACK)
• EXECUTED RESPONSE (EXR)
• EXECUTED RESPONSE, RESTARTED (EXRR)
• NOT EXECUTED RESPONSE (NXR)
• CHECK BACK RESPONSE (CBR)

Message formats in command direction (= SICAM A8000 receive direction):
• REQUEST B (RB)
• REQUEST X (RX)
• STATUS CHECK INSTRUCTION (SCI)

DC8-037-2, Edition 11.2020
12.16 ABB RP570/571
• RESET SEQUENCE NUMMER (RSEQ)
• FUNCTION COMMAND #1, #2, #3, #13 (FCOM)
• FUNCTION TABLE #0, #10 (FTAB)
• IMMEDIATE EXECUTED COMMAND (IXC)
• CHECK BACK BEFORE EXECUTE COMMAND (CBXC)
• INHIBIT COMMAND (IHC)
• EXECUTE COMMAND (EXC)
• SET POINT MESSAGE (SPM)
• GENERAL OUTPUT MESSAGE (GOM)
QOC-PreSelectionCommand (project specific)
Limitations
• Spontaneous information is not chained
• CCRX identifier in the function field is not supported
• Ax redundancy not supported
• ADLP-180 is not supported
• Load share operation not possible
• RA is always responded with CCR1; information is never reported
• FTAB messages are not evaluated, but they are confirmed (EXR)
• Operation mode with main line and backup line is not supported
• Negative Acknowledge (NACK) is not supported
• Only a subset of function commands is supported
NOTE
i As adaptation to third-party system, this protocol element implements only a part of the functionality and
the data formats of the non-SICAM interface. For a concrete case of application it is therefore to be
checked, how far the real requirements correspond with the functionality implemented here and to what
extent additional expansions or adaptations are necessary.
12.16.5.2 Transmission protocol
Each message basically consists of two parts
• a protocol-dependent part (message frame)
• a protocol-independent part (message data)

The message structure is based on the DIN-standard 19244 (transmission protocol for the format class F 1.2),
issue January 1986.
The transmission protocol prescribes the rules for the message structure and the transmission procedure. The
telecontrol message is so structured, that on the one hand the assignment to the ISO-layers, see DIN ISO
7498, Connection, Network and Transport, can be recognized as well as the higher levels on the other.
Basic message format:

DC8-037-2, Edition 11.2020
12.16 ABB RP570/571
Header for communication unit (KE) (Connection-,

Network- and Transport layer)
Header for process unit (PE) (Higher levels)
Information part
End part for communication unit (KE)
Message formats
The message formats and rules are based on the standard: Telecontrol Equipment and Systems Part 5: Trans-
mission Protocols Format Class FT 1.2. There are formats defined for fixed and variable message lengths as
well as single characters. The formats are distinguished, amongst other things, by different start characters.
Message format fixed block length
• Block length ≠ 0
For RP570/571 the format has a fixed block length of 5 bytes and consists of a start character, 2 user
bytes, a check byte and a stop byte.
[rp5ut1_format_fixed, 1, en_US]
Figure 12-35 Message format fixed block length
Remark:
D1 basically represents the least significant bit (LSB).
Representation of a byte (LSB shown right-aligned):
D8 D1
27 26 25 24 23 22 21 20
Following RP570/571 messages use the message format with fixed block length:
RP570: RA, RB, SCI, RSEQ, CCR1, CCR2, EXR, EXRR, NXR, PRI
RP571: RA, RB, SCI, RSEQ, CCR1, CCR2, ACK, PRI
• Single character (block length = 0)

This message format is not used on RP570/571 protocol!
Transmission rules for formats with fixed block length
• Idle state on the line represents 1-Signal.
• Each UART-character consists of start bit (0), 8 info bits, parity bit (even) and stop bit (1).
• No idle states are allowed between the UART-characters of a format block (no idle bits). This is necessary
(according to DIN) due to the required hamming distance = 4.

DC8-037-2, Edition 11.2020
12.16 ABB RP570/571
• In case of a loss of synchronization, a minimum number of 33 bits idle becomes necessary between the
formats (blocks).
Note: If switching on the carrier (in the master station) causes faulty characters in the RTU, the setup time
must be set greater than 33 bits.
• The user data bytes are monitored by the checksum. The checksum is the arithmetical sum, without
consideration of the values carried over, over all user data bytes (without Start and Stop).
• The receiver checks:

– per UART character: Start bit, Stop bit and Parity bit (even)
– per Format: Start character, Checksum and Stop character
If one of these checks leads to a negative result, then the entire message is to be discarded. The further
procedure is as described for loss of synchronization under point 4, this means, the message is not
acknowledged (by the substation) and must be repeated. With a positive check result the information is
forwarded.
Message formats with variable block length

The format consists of an initial start character, two similar characters in which the number L of the user data
is transmitted, a second start character, the checksum and the stop character. The number L of user data bytes
lies within the range 0 ... 255.
[rp5ut1_format_variable, 1, en_US]
Figure 12-36 Message formats with variable block length
Transmission rules for formats with variable block length
• Idle state on the line represents 1-signal.
• Each UART character consists of start bit (0), 8 info bits, parity bit (even) and stop bit (1).
• No idle states are allowed between the UART-characters of a format block (no idle bits). This is necessary
(according to DIN) due to the required hamming distance = 4.
• In case of a loss of synchronization, a minimum number of 33 bits idle becomes necessary between the
formats (blocks).
Note: If switching on the carrier (in the master station) causes faulty characters in the substation, the
setup time must be set greater than 33 bits.
• The user data bytes are monitored by the checksum. The checksum is the arithmetical sum, without
consideration of the values carried over, over all user data bytes (without start and stop).

DC8-037-2, Edition 11.2020
12.16 ABB RP570/571
• The receiver checks:

– per UART character: start bit, stop bit and parity bit (even)
– per Format (TG):
– the defined start character at the beginning and after the two L-bytes
– the identity of the two length bytes L
– whether the number of characters received (Byte) is the same as L + 6
– the checksum
– the stop character
If one of these checks leads to a negative result, then the entire message is to be discarded. The further
procedure is as described for loss of synchronization under point 4, this means, the message is not
acknowledged (by the substation) and must be repeated. With a positive check result the information is
forwarded and the message is acknowledged to the transmitting station.
12.16.5.3 Length-, Address- and Function Field
Assignment of the Length-(L)-Field

The length field defines the number of user data bytes, see “Record Formats Used”.
Values between (0) and 255 are possible.
D8 D1
27 26 25 24 23 22 21 20 L-Field
Assignment of the Address- (A)-Field

The address field defines the RP570 station address. Values between 0 and 255 are possible. Address field
equals 0 means, that the message from the central station is transmitted to all remote terminal units. In this
case the message must not be acknowledged or responded by any substation (RTU).
D8 D1
27 26 25 24 23 22 21 20 A-Field
Identification of the participant:

On a line, each station must know which messages are directed to it and from where they originate. Because
messages cannot be exchanged between any two stations, but rather only between the central station and a
substation, it is sufficient to state in all messages the concerned substation (independent whether it is trans-
mitter or receiver).
NOTE
i In the RP571 Mode the own RP570-RTU-No is replaced by the “Router-RTU-No” and additionally the
“Process-RTU-No” (after the F-Field) is transmitted. In the following description, however, only the term
“Process-RTU-No” is used, which is in RP570 Mode the “RTU-No”.
Assignment of the F-Field in Command Direction
D8 D7 D6 D5 D4 D3 D2 D1
SFK MD Function RB
Meaning of the fields in the F-field in command direction:

RB = 1 Direction bit of the information (= 1 command direction)
Function Message type

DC8-037-2, Edition 11.2020
12.16 ABB RP570/571
M/D Message acknowledgement

0 = Monolog Mode (no acknowledgement)
1 = Dialog Mode (with acknowledgement)
SFK Record sequence identifier
A message in Monolog Mode (M/D = 0) must not be acknowledged by the remote terminal unit (for instance
commands to all). A message in Dialog Mode (M/D = 1) must be acknowledged by the remote terminal unit.
There are message formats that may be transmitted in Monolog Mode and Dialog Mode, as well as messages
that may only be transmitted in Dialog Mode.
Table 12-11 The following table lists the message formats implemented and their transmission mode in
command direction.
Funktionscode Message Format Mnemonic M D

0 REQUEST A RA ✓
Request for data of Priority 1
8 REQUEST B RB ✓
Request for data of Priority 1, 2 or 3
4 REQUEST X RX ✓
Request of a certain variable (test)
15 STATUS CHECK INSTRUCTION SCI X ✓
7 RESET SEQUENCE NUMBER RSEQ ✓ ✓
Resetting of the record sequence identifier
6 FUNCTION COMMAND FCOM ✓ ✓
System-internal commands
5 CHECK BACK BEFORE EXECUTE COMMAND CBXC ✓
Selection command pulse command Type-1
13 EXECUTE COMMAND EXC ✓
Execution pulse command Type-1
3 INHIBIT COMMAND IHC ✓ ✓
Inhibit pulse command Type-1
9 IMMEDIATE EXECUTED COMMAND IXC ✓ ✓
Pulse command Typ 1/Typ 2
1 SET POINT MESSAGE SPM ✓ ✓
Setpoint command, setpoint value
11 GENERAL OUTPUT MESSAGE GOM ✓ ✓
Setpoint value, binary information
12 TIME SYNC INSTRUCTION TSI ✓ ✓
Record Sequence Identifier (SFK)

The record sequence identifier (SFK) protects the communication against information loss and duplication.
With the SFK in the request control code of the F-field in command direction, a retransmission of the last
message can be achieved in case of information loss.
The record sequence identifier is handled by the central station for each substation.
Handling of SFK in the Central Station

If no valid answer is received with a specified timeout, the sent message is repeated with the same sequence
number again.
The central station repeats this message n times (n = retry number). If the retry number is reached, the substa-
tion is marked as faulty. A faulty substation is always called with SCI by the cetral station.

DC8-037-2, Edition 11.2020
12.16 ABB RP570/571
Handling of SFK in the Substation (RTU)

The substation interprets a record sequence identifier increased by 1 compared with the previous request as
positive acknowledgement for the information it has transmitted. Otherwise, with this mechanism a repeat of
the last three sequence numbers can be requested from the central station.
The substation always stores the function byte (F-field) of the last correct received message in Dialog Mode
with the sequence numbers 0, 1, 2 and 3 and the whole corresponding answer which the substation has sent.
Sequence number = 0 Received function byte Sent answer
If the substation receives a message in Dialog Mode with an unexpected sequence number (expected is: (last
received + 1) modulo 4), it checks the received function byte with the stored one. If they match, it retransmits
the stored answer again without performing the command again. If they do not match, the substation keeps
quiet; the received message is discarded.
Note:
The messages SCI and RSEQ initialize the sequence number (to “0”, next expected is “1”). Further the stored
“function byte” and “sent answer” are erased (as described before).
Assignment of the F-field in signaling direction – type 1
D8 D7 D6 D5 D4 D3 D2 D1
AZ Function Ü PRI RB
Meaning of the fields in the F-field in signaling direction Type 1:

RB = 0 Direction bit of the information (= 0 monitoring direction)
PRI Priority
0 = priority 1
1 = priority 2, 3
Ü Transmission
0 = without status
1 = with status
AZ Interrogation cycle
0 = cycle not completed
1 = cycle completed
Table 12-12 The following table lists the message formats implemented, that are transmitted with the F-
field type 1.
Message Format Mnemonic Priority with CCRx F-Field

ANALOG VALUE AVM P1 No 00101000
MESSAGE Yes 10000000
Measured values P2, P3 No 00101010
Yes 10000010
ANALOG VALUE AVS P1 No 00101100
MESSAGE WITH Yes 10000100
STATUS P2, P3 No 00101110
Measured values
Yes 10000110
(with status)

DC8-037-2, Edition 11.2020
12.16 ABB RP570/571
Message Format Mnemonic Priority with CCRx F-Field

INDICATION IDM P1 No 00110000
Binary information P2, P3 No 00110010
Yes 10001010
INDICATION IDS P1 No 00110100
MESSAGE WITH Yes 10001100
STATUS P2, P3 No 00110110
Binary information
Yes 10001110
(with status)
DIGITAL VALUE DVM P1 No 00111000
Digital value P2, P3 No 00111010
Yes 10010010
PULSE COUNTER PCM P1 No 00111100
Count message P2, P3 No 00111110
Yes 10010110
PULSE COUNTER PCT P1 No 01001110
TELEGRAMM Yes 10011100
Count message P2, P3 No 01010000
Yes 10011110
EVENT RECORDING ERMI P2, P3 No 01000000
MESSAGE FOR INDI-
CATION
Binary information
with time tag
EVENT RECORDING ERMFD P2, P3 No 01010110
MESSAGE FOR
FAULT DISTANCE
measured value
from protection
unit-fault distance
The message types listed above are only support without CCRx (CCRx-no). CCRx indicates that further informa-
tion is available for this priority level (P1 or P2/P3).
Assignment of the F-field in signaling direction - type 2
D8 D7 D6 D5 D4 D3 D2 D1
Free Function RB
Meaning of the fields in the F-field in signaling direction type 2:

RB = 0 Direction bit of the information (= 0 monitoring direction)

DC8-037-2, Edition 11.2020
12.16 ABB RP570/571
Table 12-13 The following table lists the message formats implemented, that are transmitted with the F-
field Type 2.
Message Format Mnemonic F-Field

CYCLE COMPLETE RESPONSE CCR1 00000000
PRIORITY LEVEL 1
Cycle Priority 1 complete
CYCLE COMPLETE RESPONSE CCR2 00000010
PRIORITY LEVEL 2
Cycle Priority 2 complete
EXECUTED RESPONSE, RESTARTED EXRR 00000100
Positive acknowledgement; first
acknowledgement after POWER/UP
EXECUTED RESPONSE EXR 00000110
Positive acknowledgement to
various messages
NOT EXECUTED RESPONSE NXR 00001000
Negative acknowledgement to
various messages
TERMINAL STATUS TSTA 00001010
Station status
TERMINAL EVENT MESSAGE TEV 00001110
Station information
POLLING REQUEST INSTRUCTION PRI 00011000
POSITIV ACKNOWLEDGE ACK 00011010
Positive acknowledgement
NEGATIV ACKNOWLEDGE NACK 00011110 346
Negative acknowledgement
RP571 Router Station Number

In order to handle multi-hierarchical configurations (substation with subordinate substations) the protocol
type “RP571” is used. The “RTU-No” is now replaced by a dual address scheme:
• Router-RTU-No.
• Process-RTU-No.
The Router-RTU communicates directly with the central station. The “Process-RTU-No” is used for addressing of
information (destination address in command direction, source address in monitoring direction).
If “Router-RTU-No” =“ Process-RTU-No”, information is directed to the Router-RTU or the information is from the
Router-RTU (originator).
346 currently not supported

DC8-037-2, Edition 11.2020
12.16 ABB RP570/571
[rp5u01e, 1, en_US]
If no further subordinate substations are connected to a substation, then Process-RTU-No = Router-RTU-No.

Sub-Substation Handling
[rp5u01f, 1, en_US]
Figure 12-37 Configuration with Sub-Substations

DC8-037-2, Edition 11.2020
12.16 ABB RP570/571
Table 12-14 Command to Router-RTU (Process-RTU-No = 10):
Central Station RB 10 IXC 10 RB 10

Router RTU CCR 2 EXR CCR 2
Table 12-15 Command to Process-RTU# 11:
Central Station RB 10 IXC 11 RB 10 RB 10

Router RTU CCR 2 ACK EXR CCR 2

CCITT USA Line designation Reg. direction
V.24
102 GND Signal ground Signal Ground
103 TD Transmit data Transmit Data → DCE
104 RD Receive data Receive Data ← DCE
105 RTS Switch on the transmit Request to send → DCE
part
106 CTS Clear to send Clear to send ← DCE
109 DCD Receive signal level Data carrier detect ← DCE
107 DSR Readiness for operation Data Set ready ← DCE

The data are pulse code modulated in groups of 8 Bit and transmitted asynchronous. A USART building block
in asynchronous mode provides each byte with a byte frame in the process.
1 Start bit
8 Data bits
1 Stop bit
byte.
[dw_RP5UT1_pcmba_modulation, 1, --_--]
Figure 12-38 ABB RP570/RP571 Byte Frame

DC8-037-2, Edition 11.2020
12.16 ABB RP570/571
A: Empty line status (binary information “1”), between two telegrams at least 33 bit (in the event of an error)
B: Start bit ("0")
C: 8-bit data (possibly frame data or telegram data), LSB (Least Significant Bit) is transmitted first
D: Parity bit (even parity)
E 1. Stop bit ("1")
T: Time to transmit a bit (1/transmission speed)
FB: Framing bits for the USART building block
12.16.5.6 Traffic Management
The remote terminal units are requested cyclically by the master station (polling-procedure). The polling-
procedure is based on transmitting information on event from the RTU, but each request must be responded
by the RTU, expected the request is directed to all RTU’s. (broadcast) Within the polling cycle user data
messages (commands, setpoint values,…) can be inserted in the command direction. In monitoring direction
the data are subdivided into 3 priority levels, Priority 1, 2 and 3, whereby Priority 1 is regarded as the highest
priority level.
The master station uses two different requests to collect information of different priority levels from the RTU:
• Request A (RA): information of priority 1, TSTA, TEV
• Request B (RB): information of priority 1, 2, 3, TSTA, TEV

Attention: Request A is always respond with CCR1 (no information available).
Typical message sequences
Table 12-16 Polling procedure:
Master RA RB RB
Slave CCR 1 IDM CCR 2
Table 12-17 Command to RTU:
Master RB IXC RB RB
Slave CCR 2 EXR CCR 2 IDM
Table 12-18 Restart of RTU:
Master RB RB SCI SCI RB RB

Slave CCR 2 ↑ EXRR TSTA TEV
RTU
Restart
If the master station detects the failure of a RTU, then this station is always requested with “SCI” (-status check
instruction).
NOTE
i The firmware accepts only SCI and RSEQ after restart or after establishing communication. All other
messages are discarded.
After the master station has received a certain “Terminal Event” message it can start a parameter download
procedure, which is performed with FTAB messages. During the parameter downloading the RTU must no
transmit any information (neither spontaneous nor because of the received SCI before).

DC8-037-2, Edition 11.2020
12.16 ABB RP570/571
The parameter download is concluded with the function command “Activate RTU” (= FCOM2). After the recep-
tion of FCOM2 the RTU enables transmission of process information.
Note:
messages in command direction (i.e. commands, setpoints) are converted correctly and executed during
parameter download, if the master station would send this messages.
12.16.6 Communication according to ABB RP570/571
12.16.6.1 Process Image

The firmware manages a process image (data base), in order to
• Monitor indications and measured values for change
• Transmit indications and measured values directly from the process image in case of “Status Check
Instruction” (general interrogation)
The process image is structured according to RP570/RP571 block numbers (1 block-no = 1 measured value or
16 binary information). The process image contains beside the state invalid identifier (IV).
SICAM A8000 information objects contain the following data point quality identifiers:
• NT-Bit (not topical)
• IV-Bit (invalid)
• BL-Bit (blocked – descriptor only for bouncing signal)
• OV-Bit (overflow – only for measured values)

In the RP570/571 protocol there is only one identifier: IV (RP570/571) = NT v IV v OV.
Counter values are not recorded in the process image. After a firmware restart, the process image is initialized
with the state "0" and IV, as well as the startup delay started (parameter-settable).
The startup delay serves to update the process image. During this time, no communication takes place to the
central station (receiver is disabled). Changes that occur in the process status are not stored.
12.16.6.2 Data Transmission Procedure and Preparation

The RP570/571 protocol uses two different requests (Request A, Request B) to collect information of different
priority levels (P1, P2, P3):
Request A (RA)
• Information of priority 1 (P1)
• One Terminal Status message
• One Terminal Event message

Request B (RB)
• All information
As the priority control of all information takes places on the basic system element (BSE) and the firmware has
no influence to the priority control, a received Request A is always confirmed with CCR1 (no information avail-
able).
The protocol element (PRE) may only send events to the central station if it has received a corresponding call
(request). If the PRE is allowed to transmit data to the central station, then it requests data from the BSE ("give
me data").
The BSE now decides based on the priority control, which data are sent to the PRE. If the PRE receives an
SICAM A8000 message, then
• a change comparison is performed
• the process image is updated

DC8-037-2, Edition 11.2020
12.16 ABB RP570/571
If a change is detected, a RP570/571 message is generated, the parameterized priority is added and sent to the
central station. Chaining of spontaneous events is not done (only one Block-No in one message).
If no change is detected, then a further chaining operation ("give me data") is initiated, unless the parameter-
ized number of chaining operations has also been reached. If the number of chaining operations has been
reached, a CCR2 message is sent to the central station.
RP570 Radio Spontaneous Mode
General
If leased line for RP570 ommunication (in Polling Mode) between central station and substation is not avail-
able, radio communication can be used for RP570 communication (radio spontaneous mode).
The radio spontaneous mode is a special mode of communication where radio is used for RP570 communica-
tion; but radio must be used only for a limited duration (like dial-up mode, duration is defined in the central
station).
The RP570 protocol procedure is identical in the polling mode and radio spontaneous mode, excepted the
connection setup of the substation. The connection setup can be established by any system (central or substa-
tion), but the communication structure is still hierarchically. That means, a link connection can only be estab-
lished between a central station and a substation, but never between substations.
A connection setup initiated by the central station will be done in case of general interrogation, check cycle or
information (example: commands) to be sent.
A connection setup by the secondary station may only be initiated if important information (events) is avail-
able to be transmitted. Spontaneous events (single point/double point information) in the secondary station
initiate always an automatic connection setup while spontaneous measured values initiate never a connection
setup without additional parameterization (CAEx plus, selective dataflow).
A cyclic connection setup can only be performed by the central station at a configurable interval (check cycle)
and is used for:
• Check if station is available
• Clock synchronization
The connection setup of the secondary station is performed by sending a Polling Request Instruction
(PRI) to the primary station. This RP570 message initiates starting the polling procedure in the central station
to the substation, identified by the PRI.
All information with internal priority level = data class 1 initiates an automatic connection setup (same
behavior like SICAM A8000 dial-up slave).
If a connection is established to the central station, all information – independent of the internal priority level
– is transmitted.
An automatic general interrogation (for indications and measured values) after establishing a connection is
not supported by the firmware.
The radio spontaneous mode of the protocol element must be enabled by setting the parameter Radio
spontaneous mode = enabled.
Radio Modem Radius PDR 121 v2

Radio spontaneous mode is e.g. supported by Radius PDR 121 v2 modem. This modem includes the radio
(high frequency channel) and also supports routing of RP570 messages in the radio network.
• The signal RTS (SICAM A8000) is not used, but PDR121 modem uses this for data flow control (RTS is
active permanent)
• DCD signal is not used
Connection Setup of Substation

A connection setup of the secondary station may only be initiated if the important information (events) are
available to be transmitted and no valid RP570 message frames (acc. FT1.2) are received for a configurable
duration (polling procedure of central station is stopped). This duration is defined by the parameter Commu-
nication - inactivity.

DC8-037-2, Edition 11.2020
12.16 ABB RP570/571
This condition avoids the interruption of active polling procedure of the central station or message collisions
of other substations, which also initiates a PRI.
After detection of communication inactivity, the PRI will be sent.
After transmission of the PRI message the configurable monitoring timeout Connection setup -
timeout is started for monitoring the polling procedure of the central station.
If the PRI message is received correct in the central station, the communication between central station and
substation is done with the standard RP570 polling sequence (unbalanced master/slave communication)
controlled by the central station.
The Connection setup - timeout is stopped, if requests are received from the central station and
enables transmission of all process information (not only data class1 information).
Disconnection (Clear Connection)
The central station will always clear the connection. After the connection to a substation has been established,
independent of initiator (central station or the substation) the central station clears the connection after a
predefined timeout or no process information is available in the substation to be transmitted. The central
station clears the connection by sending the function command Telephone hang up – start active
call up (FCOM#11 – INFO 1=2) in monolog mode. This command informs the substation that the polling
procedure is finished and instructs the substation to initiate a further PRI, if any important spontaneous infor-
mation (data class 1) occurs. All priority levels, except Data class 1 levels, are blocked AU-internally.
Repeat of Connection Setup
If the central station does not start a polling procedure after the substation has transmitted a PRI, the
Connection setup - timeout expires. The substation repeats the PRI n times (n is configurable). If all
repeats of connection setup fails, a warning Radio spontaneous mode: connection setup to
master station not successful is set.
Before the next repeat of connection setup will be initiated, the substation performs an additional delay (extra
long break). The additional delay is defined by the parameter Connection setup - break. This delay is
increased by own RP570 RTU-No ⋅0.2 s.
Communication Sequence
After the connection setup is established, the data exchange is done with polling; the central station transmits
requests (with or without information) to the substation, and the substation responds to these requests with
or without information.
NOTE
i RSEQ requests do not retrigger the Call timeout in radio spontaneous mode.

DC8-037-2, Edition 11.2020
12.16 ABB RP570/571
Connection Setup initiated by Central Station (example: check procedure)
[RP5UT1_check_cycle, 1, en_US]
Figure 12-39 Connection Setup initiated by Central Station

DC8-037-2, Edition 11.2020
12.16 ABB RP570/571
[RP5UT1_check_cyclkes, 1, en_US]
Figure 12-40 Connection Setup initiated by the Substation
NOTE
i The firmware initiates a connection setup at each event (data class 1) in the automation unit, independ-
ently the event is defined in the SIP address message conversion. If this effect is not acceptable, the "selec-
tive data flow" must be used.

DC8-037-2, Edition 11.2020
12.16 ABB RP570/571
12.16.6.3 General Interrogation

The central station causes with the message Status Check Instruction (SCI) the remote terminal unit
to transmit the current process state.
If the SCI is forwarded to the remote terminal, then the general interrogation is answered directly from the
process image of the firmware. The firmware, however, also sends a GI request (image GI) to the BSE, in order
to keep the process image guaranteed synchronous between BSE and firmware. The GI data sent by the BSE
are only forwarded to the master on change (status or state).
[RP5UT1GA, 1, en_US]
Figure 12-41 RP570/571 General Interrogation
CASDU of the Internal GI Request

During startup the firmware generates an assignment between CASDU and RP570-Process-RTU-No. If up to 2
CASDUs are assigned to one RP570-Process-RTU-No, then the internal GI-request (TI 100) is always executed
selectively, otherwise the GI request is always addressed broadcast. Every received GI request is always
converted to the SICAM A8000 system message General Interrogation Request.
Processing
The Status Check Instruction (SCI) is always directed to a Process-RTU-No. The firmware transmits the informa-
tion of the Process-RTU-No requested in the SCI message.

DC8-037-2, Edition 11.2020
12.16 ABB RP570/571
Exception:
• After restart or after receipt of FCOM2, the whole data base is transmitted.
• RP571
After receipt of SCI directed to the Router-RTU, the transmission of the whole data base can be enabled
(Parameter SCI to Router RTU).
Transmission of Data After Status Check Instruction

Information is transmitted after a Status Check Instruction to a certain substation as follows:
• Terminal Status (TSTA)
• Terminal Event (TEV)
• Information of priority 1
The order of TSTA and TEV messages is determined by the parameters Priority - TSTA message and
Priority - TEV message.
TSTA and TEV messages to be transmitted must be parameterized (Parameter System messages (TSTA,
TEV) after SCI).
Information is transmitted in increasing order of Process-RTU-No and Block-No. Indications and analog meas-
ured values are always transmitted in the message format with status (IDS and AVS).
Order of data types:
• Indications (IDS)
• Analog measured values (AVS)
• Digital measured values (DVM)

The message length at general interrogation is configurable (blocked transmission of indications and analog
measured values).
SCI to Router-RTU
Transmission of all information:
• Terminal-Status (Router-RTU)
• Terminal-Event (Router-RTU)
• Terminal-Status (Process-RTU-No = x)
• Terminal-Event (Process-RTU-No = x)
• Terminal-Status (Process-RTU-No = y)
• Terminal-Event (Process-RTU-No = y)
12.16.6.4 QOC Preadjustment Commands

The Quality of Command (QOC = Quality of command = Command output duration) to be added on received
commands can be preadjusted by preadjustment commands. This function is implemented project-specific.
Two different QOC preadjustment commands exist:
• QOC preadjustment command interlocking
• QOC preadjustment command PSG

DC8-037-2, Edition 11.2020
12.16 ABB RP570/571
The QOC preadjustment commands are identified by the parameterized RP570-QOC:
• preadjustment interlocking commands (RWE)
• preadjustment PSG commands (RWE)

All commands which should to be added on with the preadjusted QOC must be defined in the SIP address
message conversion with RP570-QOC = QOC acc. preadjustment (RWE).
Add-on of QOC:
Circuit breaker: CTYPE = 0 Disconnector: CTYPE = 4
Interlocking PSG QOC Interlocking QOC
ON ON 0 ON 10
OFF ON 9 OFF 11
ON OFF 10
OFF OFF 11
Attention: The QOC preadjustment commands (PSG and interlocking) must be defined only once.
The state of both QOC preadjustment commands can be confirmed with double-point information to the
central station. For this purpose, two double-point information items must be defined in the SIP address
message conversion as follows:
• ERMI_(time_tag) = no
• RP570-indication-type =
(possible:)
– QOC RI PSG
– QOC RI inter-
locking
12.16.6.5 Terminal Status Message (TSTA)

Terminal Status messages are system indications of the substation itself which are transmitted spontaneous
(on event) or at “Status Check Instruction” (general interrogation).
The substation handles 8 TSTA messages for each RP570-Process-RTU-No. These messages are initialized
after restart as follows:
RP570-message reference Ident-No. Bit 15 to 12 Bit 11 to 8 Bit 7 to 4 Bit 3 to 0
Message 0 1 1000 0001 0000 0000
Message 1 2 0000 0000 0000 0000
Message 2 3 0000 0000 0000 0010
Message 3 1 1000 0011 0000 0010

DC8-037-2, Edition 11.2020
12.16 ABB RP570/571
RP570-message reference Ident-No. Bit 15 to 12 Bit 11 to 8 Bit 7 to 4 Bit 3 to 0

Message 4 2 0000 0000 0000 0000
Message 5 3 0000 0000 0000 0000
Message 6 4 0000 0000 0000 0000
Message 7 5 0000 0000 0000 0000
Ident = 1, Bit-No = 8 … “RTU is active”

Ident = 1, Bit-No = 9 … “RTU is synchronized”
These indications are generated automatically by the substation (only for the own RP570 RTU-No).
These 8 predefined TSTA messages can be changed or updated with single point information (TI 30) of the SIP
address message conversion (also the RP570-Ident-No, refer to Terminal Status Message (TSTA),
Page 1684).
The RP570 message reference is used for access between data base and SIP address message conversion.
The transmission of TSTA messages must be enabled in the system technical parameterization.
Parameters:
• advanced parameters | RP570/571 specific settings | System messages (TSTA,

TEV) after SCI

TEV) after FCOM13
12.16.6.6 Terminal Event Message (TEV)

Terminal Event messages are system internal events of the RTU itself (example: RTU restarted), which are only
transmitted on event. Several master stations need TEV messages of the substation for correct operation,
other master stations do not need any TEV messages.
The substation handles 8 TEV messages for each RP570-Process-RTU-No. These messages are initialized
after restart as follows:
RP570-message reference Event-Nr. INFO 1 INFO 2 INFO 3 INFO 4 INFO 5 INFO 6
Message 0 23 0 0 0 0 0 0
Message 1 24 0 0 0 0 0 0
Message 2 25 0 0 0 0 0 0
Message 3 1 0 0 0 0 0 0
Message 4 1 0 0 0 0 0 0
Message 5 1 0 0 0 0 0 0
Message 6 1 0 0 0 0 0 0
Message 7 1 0 0 0 0 0 0
These 8 predefined TEV messages can be changed or updated with bit string 32 bit (TI 33) of the SIP address
message conversion (also the RP570-Event-No, refer to Terminal Event Message (TEV), Page 1685).
The RP570 message reference is used for access between data base and SIP address message conversion.
The transmission of TEV messages must be enabled in the system technical parameterization:
Parameters:

TEV) after SCI

TEV) after FCOM13
12.16.6.7 Activation of the Substation

Several central stations do not expect process information after restart of the substation. The central station
only accepts process information after it has activated the substation.

DC8-037-2, Edition 11.2020
12.16 ABB RP570/571
The activation is performed with the system command FCOM-No = 2. This behavior must be configured with
the parameter Common settings | protocol enabling | Enable of user data:
• immediately after startup
• wait for FCOM no. 2
Waiting for FCOM-No = 2

After restart of the substation and startup delay has been expired, all parameterized TSTA and TEV messages
are transmitted (system messages after SCI). Then the firmware is waiting for FCOM-No = 2.
After the substation has received FCOM-No = 2, the transmission of information is enabled (terminal status
“RTU is active”). Further, after reception of an FCOM-No = 2 to the own RP570-RTU-No, the transmission of the
whole data is initiated (general interrogation to all substations).
12.16.6.8 Conversion of Measured Values
General
The RP570/571 protocol uses two different message formats for measured values:
• Analog measured values (AVM/AVS)

range: -2048 to 0 to +2047
full scale (100 %): 2000
• Digital measured values (DVM)

The coding of digital measured values is determined in the SIP address message conversion:
– 16 bit bipolar
range: -32768 to 0 to 32767
full scale (100 %): 32000
– 16 bit BCD
This coding is only valid for step position information <TI:=32>
range: 0 to 9999
– 16 bit transparent
This coding is only valid for bit string 32 bit <TI:=33>
range: 0 to 65535
The following type identifications can be converted to RP570/571 measured values:
• Bit string 32 bit <TI:=33>
• Measured value– normalized <TI:=34>

The data point quality identifier NT (not topical), IV (invalid) and OV (Overflow) are converted to status =
invalid/faulty.
A linear adaptation can be parameterized for each measured value (only TI 34, 35, 36). The linear adaptation
is defined through the following parameters:
Lower limit of the used measuring range in the external format (protocol-specific). The corre-
sponding internal value is defined at Y_0%.
Upper limit of the used measuring range in the external format (protocol-specific). The corre-
sponding internal value is defined at Y_100%.

DC8-037-2, Edition 11.2020
12.16 ABB RP570/571

Lower limit of the used measuring range in the selected internal format. The internal format is
defined at TI (type identification). The corresponding external value is defined at X_0%.
Upper limit of the used measuring range in the selected internal format. The internal format is
defined at TI (type identification). The corresponding external value is defined at X_100%.
As only two measured value formats are defined in the RP570/571 protocol, the parameters X_0% and
X_100% are defined in the range:
Analog measured value (AVS/AVM): -2048 to +2047
Digital measured value (DVM): -32768 to +32767
Also valid: Y_100% > Y_0%

The parameters Y_0% and Y_100% are defined by the internal type identification.
Measured value - normalized: -1 to + 1
Measured value - scaled: -32768 to +32767
Measured value - short floating: No check
The linear adaptation is activated, if Y_0% or Y_100% is parameterized unequal to “0”.
Value Conversion without Linear Adaptation

– Value range: -64 to +63
Value RP570 = vlue SICAM A8000
• Measured value normalized <TI:= 34>

– Value range: -1 to +1
Value RP570 = value SICAM A8000 ⋅ full scale
• Measured value scaled <TI:=35>

– Value range : -32768 to +32767
Value RP570 = value SICAM A8000
• Measured value short float <TI:=36>

– Value range: -3.4 ⋅ 1038 to +3.4 ⋅ 1038
Value RP570 = value SICAM A8000
If the measured value to be converted (value SICAM A8000) is not in the valid range of the RP570/571 format or
the measured value is already marked as OV = 1, the RP570/571 measured value is set to its positive maximum
value (+2047, +32767) or negative maximum value (-2047, -32767) and status = invalid (0x07).
Value Conversion with Linear Adaptation

The adaptation is activated, if Y_0% or Y_100% are parameterized to unequal “0”.
Value RP570 = k ⋅ value SICAM A8000 + d
whereby
k = (X100 – X0) / (Y100 – Y0)
d = X0 – k ⋅ Y0
Attention:
Value SICAM A8000 <Y0 → Value RP570 = X0 and status = invalid
Value SICAM A8000 >Y100 → Value RP570 = X100 and status = invalid

DC8-037-2, Edition 11.2020
12.16 ABB RP570/571
[rp5ut01o, 1, en_US]
Figure 12-42 RP570/571 - Value Conversion of Bipolar Measured Values
12.16.7 Message Conversion In Transmit Direction (SICAM A8000 → RP570/571)
Supported message formats:

SICAM A8000 ABB RP570/571
Designation Func- Message Designation
tion
Code
Responses (link layer)
0 CCR1 CYCLE COMPLETE RESPONSE PRIORITY
LEVEL 1
1 CCR2 CYCLE COMPLETE RESPONSE PRIORITY
LEVEL 2
13 ACK POSITIVE ACKNOWLEDGE
15 NACK NEGATIVE ACKNOWLEDGE
3 EXR EXECUTED RESPONSE
2 EXRR EXECUTED RESPONSE RESTARTED
4 NXR NOT EXECUTED RESPONSE

DC8-037-2, Edition 11.2020
12.16 ABB RP570/571
SICAM A8000 ABB RP570/571

Designation Func- Message Designation
tion
Code
10 CBR CHECK BACK RESPONSE
12 PRI POLLING REQUEST INSTRUCTION
13 ACK POSITIVE ACKNOWLEDGE
15 NACK NEGATIVE ACKNOWLEDGE
3 EXR EXECUTED RESPONSE
2 EXRR EXECUTED RESPONSE RESTARTED
4 NXR NOT EXECUTED RESPONSE
10 CBR CHECK BACK RESPONSE
Process information
Single point information <TI:=30> 24,25 IDM INDICATION MESSAGE/
26,27 IDS INDICATION MESSAGE with STATUS
32 ERMI EVENT RECORDING Message for Indication
Double point information <TI:=31> 24,25 IDM INDICATION MESSAGE/
26,27 IDS INDICATION MESSAGE with STATUS
32 ERMI EVENT RECORDING Message for Indication
Measured value 15 bit + sign normalized 20,21 AVM ANALOG VALUE MESSAGE/
<TI:=34> 22,23 AVS ANALOG VALUE MESSAGE with STATUS
28, 29 DVM DIGITAL VALUE MESSAGE
Measured value 15 bit + sign scaled 20,21 AVM ANALOG VALUE MESSAGE/
Measured value short floating point 20,21 AVM ANALOG VALUEMESSAGE/
Set position information <TI:=32> 28, 29 DVM DIGITAL VALUE MESSAGE
Integrated total 31 bit + sign <TI:=37> 30, 31 PCM PULSE COUNTER MESSAGE
39, 40 PCT PULSE COUNTER TELELGRAM
Measured value short floating point 43 ERMFD EVENT RECORDING MESSAGE
<TI:=36> FAULT DISTANCE
System information
Single point information <TI:=30> 5 TSTA TERMINAL STATUS
Bit string 32 bit <TI:=33> 7 TEV TERMINAL EVENT MESSAGE

DC8-037-2, Edition 11.2020
12.16 ABB RP570/571
12.16.7.1 Response
Cycle Complete Response, Priority Level 1 (CCR1)
RP570/571 message format
[rp5u16, 1, --_--]
This message is always sent to the master station when a “request A” is received (see 12.16.6.2 Data Trans-
mission Procedure and Preparation).
Cycle Complete Response, Priority Level 2 (CCR2)
[rp5u17, 1, --_--]
This message is sent to the master station when a “request B” is received and no information (measured value,
indication, etc.) is available to be transmitted.

DC8-037-2, Edition 11.2020
12.16 ABB RP570/571
Positive Acknowledge (ACK)
[rp5u18, 1, --_--]
This message serves as a positive response to a message sent by the central station (command, setpoint
command, etc.), if it is not directed to the Router-RTU but to a subordinate substation in the RP571 mode.

DC8-037-2, Edition 11.2020
12.16 ABB RP570/571
Negative Acknowledge (NACK)
[rp5u19, 1, --_--]
Note: This message is not supported currently by the firmware.

DC8-037-2, Edition 11.2020
12.16 ABB RP570/571
Executed Response (EXR)
[rp5u20, 1, --_--]
This message serves as a positive response to a message sent by the master station. (command, setpoint
command, etc.) to the substation.
Executed Response, RTU Restarted (EXRR)
[rp5u21, 1, --_--]

DC8-037-2, Edition 11.2020
12.16 ABB RP570/571
This message serves as a positive response to the “status check instruction” (SCI) in RP570 format on start up
of the substation.
Not Executed Response (NXR)
[rp5u22, 1, --_--]
This message serves as a negative response to a message sent by the master station (command, setpoint, etc.)
to the substation.
Check Back Response (CBR)
[rp5u23, 1, --_--]
OBJECT NUMBER object number of the received command

CTYPE 0 =object command

DC8-037-2, Edition 11.2020
12.16 ABB RP570/571
This message serves as the positive response to the “Check Back Before Execute Command” (CBXC).
Polling Request Instruction (PRI)
[rp5u24, 1, --_--]
This message is sent by the substation to the master station in radio spontaneous mode when important data
is ready to be sent.

DC8-037-2, Edition 11.2020
12.16 ABB RP570/571
12.16.7.2 Process Information
Indications (IDS/IDM, ERMI)
Indication Message without Status (IDM)

[rp5u25, 1, --_--]
FCODE D7 D6 D5 D4 D3 D2 D1 Priority with

CCR
0 0 1 1 0 0 0 1 no
0 0 1 1 0 0 1 2, 3 no
1 0 0 0 1 0 0 1 yes347
1 0 0 0 1 0 1 2, 3 yes347
BLOCK NO Block number

VALUE 16 bit information
347 not supported

DC8-037-2, Edition 11.2020
12.16 ABB RP570/571
Indication Message with Status (IDS)

[rp5u26, 1, --_--]

CCR
0 0 1 1 0 1 0 1 no
0 0 1 1 0 1 1 2, 3 no
1 0 0 0 1 1 0 1 yes347
1 0 0 0 1 1 1 2, 3 yes347

STATUS Status flags of information
1 (11 for double point information) = invalid
VALUE 16 bit information
Conversion IDS/ID
• The maximum message length is configurable; therefore the number of blocks of indications is limited.
Attention: This parameter is only active for transmission caused by "status check instruction“, if sponta-
neous transmission (event) happens, the message contains only one block of indications.

DC8-037-2, Edition 11.2020
12.16 ABB RP570/571
• Double point information

the bit position of a double point information within a block number is always an even number (0, 2, 4,
… 14).
The even bit number (0, 2, 4, … 14) epresents the ON status (in normal case).
The representation can be inverted by a parameter (selective for each double point information).
• Message format with status (IDS)

The use of the format “indication message with status” (IDS) can be determined by a parameter:
– at status check instruction (SCI), status change
– at status check instruction (SCI), status <> 0 (= block number is invalid)
• Invalid-Bit
IV (RP570) = NT (SICAM A8000) v IV (SICAM A8000)
Event Recording Message for Indications (ERMI)
[rp5u27, 1, --_--]

SEQUENCE NO Sequence number
The sequence number (0 to 255) is incremented for each event recording
message ERMxx. The first value is transmitted with 0; then, the sequence
number is incremented from 255 to 1.

DC8-037-2, Edition 11.2020
12.16 ABB RP570/571
VAL Single point information:

01 = ON
10 = OFF
Double point information:
01 = ON
10 = OFF
00 = intermediate position
11 = faulty position
TYP 0 = single point information
1 = double point information
BIT NO Bbit number within the binary information block
OF 1 = FIFO overflow
not supported by the firmware ; always 0
NS 1 = clock of RTU is not synchronized
If time of the indication (TI 30, 31) is marked as invalid
T QUALITY Time quality
000 time is valid
001 ms and lower is not valid
010 ms x 10 and lower is not valid
011 ms x 100 and lower is not valid
100 second and lower is not valid
101 second x 10 and lower is not valid
Iis set if an error occurs on conversion to RP570-time format
DAY OF MONTH Day of current month
TIME Time since midnight in intervals of 0.1 ms
NOTE
i Indication with time tag (ERMI) is always transmitted additionally to indication without time tag (IDS/IDM),
if transmission of ERMI is enabled (Parameter ERMI_(time_tag)).
A transmission occurs only on event (state has been changed) and the indication itself is valid (NT = 0 und IV =
0).
Address conversion SICAM A8000 → RP570/571

The parameterization of the address and message conversion for indications in transmit direction is to be done
with the SICAM TOOLBOX II, OPM II, or with the parameters for transmit detailed routing when using SICAM
WEB.

DC8-037-2, Edition 11.2020
12.16 ABB RP570/571
Parameter category:
Parameter Meaning
CASDU2 0 to 255
IOA1
IOA2
IOA3

RP570-Process-RTU-No 1 to 255
RP570-Format • IDS
• IDM
RP570-Block-No 0 to 255
RP570-Bit-No Bit position within the block number
• Single-point information: 0 to 15
• Double-point information: 0, 2, 4, to 14
RP570-Priority • Priority 1
• Priority 2
• Priority 3
All indications of a block number must have the same priority!
ERMI_(time tag) Enabling of transmission with time tag (additional to IDS/IDM)
• No
• Yes

DC8-037-2, Edition 11.2020
12.16 ABB RP570/571
Parameter Meaning
DM-Inverting Possibility to invert the state of double point information; but only ON and OFF is
inverted
• no
ON: Bit-No. = 0, 2, 4, to 14
OFF: Bit-No. = 1, 3, 5, to 15
• yes
ON: Bit-No. = 1, 3, 5, to 15
OFF: Bit-No. = 0, 2, 4, to 14
RP570-Indication type Definition of type of indication is used for special function QOC-predjustment –
return indication
• Process indication
• QOC - RI PSG
• QOC - RI interlocking
Measured Value Analog (AVS/AVM)
Analog Value Message without Status (AVM)

[rp5u28, 1, --_--]

DC8-037-2, Edition 11.2020
12.16 ABB RP570/571

CCR
0 0 1 0 1 0 0 1 no
0 0 1 0 1 0 1 2, 3 no
1 0 0 0 0 0 0 1 yes347
1 0 0 0 0 0 1 2, 3 yes347
BLOCK NO Block number of the first measured value

VALUE Measured value in 12 bit two's-complement
NCB Number of consecutive block numbers
Analog Value Message with Status (AVS)

[rp5u29, 1, --_--]

CCR
0 0 1 0 1 1 0 1 no
0 0 1 0 1 1 1 2, 3 no
1 0 0 0 0 1 0 1 yes347
1 0 0 0 0 1 1 2, 3 yes347

DC8-037-2, Edition 11.2020
12.16 ABB RP570/571
BLOCK NO Measured value block number

STATUS 000 normal
001 lower alarm zone (not supported)
010 upper alarm zone (not supported)
011 lower warning zone (not supported)
100 upper warning zone (not supported)
101 not used
110 not used
111 invalid or blocked
LIM CHK 1 = measured value subject to limit monitoring (not supported)
0 = no limit monitoringkeine
VALUE Measured value in 12 bit two's-complement format, the sign is extended to 16
bits
Conversion AVS/AVM
• The maximum message length is configurable; therefore the number of blocks of measured values is
limited.
Attention: This parameter is only active for transmission caused by „status check instruction“, if sponta-
neous transmission (event) happens, the message contains only one measured value.
• Message format with status (AVS)

The use of the format measured value with status (AVS) can be determined by a parameter:
– at status check instruction (SCI), status change
– at status check instruction (SCI), status <> 0 (=measured value is invalid)
• Status
Only normal (= 0) and invalid/blocked is supported
Status (RP570) = NT (not topical) v IV (invalid) v OV (Overflow)

The parameterization of the address and message conversion for measured values in transmit direction is to
be done with the SICAM TOOLBOX II, OPM II, or with the parameters for transmit detailed routing when using
SICAM WEB.
Parameter category:

DC8-037-2, Edition 11.2020
12.16 ABB RP570/571
Parameter Meaning
CASDU2 0 to 255
IOA1
IOA2
IOA3

• Measured value 15 bit + sign scaled <TI:=35>
• Measured value short floating-point <TI:=36>
RP570-Format • AVS
• AVM
• Priority 2
• Priority 3
RP570-DVM-coding Coding of digital measured values, irrelevant for analog measured values
Lower limit of the used measuring range in the external format (protocol-
specific). The corresponding internal value is defined at Y_0%.
possible: -2048 to +2047 (12 bit bipolar)
Upper limit of the used measuring range in the external format (protocol-
• <TI:=34>: -1 to +1
• <TI:=35>: -32768 to +32767
• <TI:=34>: -1 to +1
• <TI:=35>: -32768 to +32767
Conversion of measured values: refer to 12.16.6.8 Conversion of Measured Values.

DC8-037-2, Edition 11.2020
12.16 ABB RP570/571
Measured Values Digital (DVM)
DIGITAL VALUE MESSAGE DVM

[rp5u30, 1, --_--]

CCR
0 0 1 1 1 0 0 1 no
0 0 1 1 1 0 1 2, 3 no
1 0 0 1 0 0 0 1 yes347
1 0 0 1 0 0 1 2, 3 yes347
BLOCK NO Measured value block number

STATUS 000 normal
001 lower alarm zone (not supported)
010 upper alarm zone (not supported)
011 lower warning zone (not supported)
100 upper warning zone (not supported)
101 not used
110 not used
111 invalid or blocked
LIM CHK 1 = measured value subject to limit monitoring (not supported)
0 = no limit monitoring
VALUE Measured value according RP570-DVM-coding
• 16 bit bipolar (digital): 16 bit two's-complement

• 16 bit BCD
• 16 bit transparent

DC8-037-2, Edition 11.2020
12.16 ABB RP570/571

SICAM WEB.
Parameter category:
Parameter Meaning
CASDU2 0 to 255
IOA1
IOA2
IOA3

• Bit string of 32 bit <TI:=33>
RP570-Format DVM
• Priority 2
• Priority 3
RP570-DVM-coding Coding of digital measured values
• 16 bit bipolar (digital)

• 16 bit BCD
• 16 bit transparent

DC8-037-2, Edition 11.2020
12.16 ABB RP570/571
Parameter Meaning
• <TI:=34>: -1 to +1
• <TI:=35>: -32768 to +32767
• <TI:=34>: -1 to +1
• <TI:=35>: -32768 to +32767
Note:
• Status
Only normal (= 0) and invalid/blocked (= 7) is supported.
Status (RP570) = NT (not topical) v IV (invalid) v OV (Overflow)
• No value adaption of step position information (TI 32) and

Bit string 32 bit (TI 33): X_0% = X_100% = Y_0% = Y_100% = 0
• At bit string 32 bit (TI 33) only the least significant two bytes are converted into the DVM message.
• Conversion of measured value: refer to12.16.6.8 Conversion of Measured Values.

DC8-037-2, Edition 11.2020
12.16 ABB RP570/571
Integrated Totals (Pulse Counter)
PULS COUNTER MESSAGE (PCM)

[rp5u31, 1, --_--]

CCR
0 0 1 1 1 1 0 1 no
0 0 1 1 1 1 1 2, 3 no
1 0 0 1 0 1 0 1 yes347
1 0 0 1 0 1 1 2, 3 yes347

DC8-037-2, Edition 11.2020
12.16 ABB RP570/571
PULSE COUNTER TELEGRAM (PCT)

[rp5u32, 1, --_--]

CCR
0 1 0 0 1 1 1 1 no
0 1 0 1 0 0 0 2, 3 no
1 0 0 1 1 1 0 1 yes347
1 0 0 1 1 1 1 2, 3 yes347

RC Restart counter
Not supported by firmware; always "0"
IV Invalid value
IV = 1, if NT = 1 (not topical) or IV = 1 (invalid)
CT Changed time
Not supported by firmware; always "0"
IT Invalid time
IT = 1,if time tag of the integrated total (= count value) is invalid
LS Local storage
IR 1 = transmission caused by an “intermediate reading”
The quality bits LS, IR and EPR are set because of the parameter PCM_PCT-
quality bits

DC8-037-2, Edition 11.2020
12.16 ABB RP570/571
EPR 1 = transmission caused by an “end of period reading”

The quality bits LS, IR and EPR are set because of the parameter PCM_PCT-
quality bits
VALUE Count in 32 bit binary value two's-complement
DAY, HOUR, MINUTE, Current time
SECOND

The parameterization of the address and message conversion for integrated totals in transmit direction is to be
done with the SICAM TOOLBOX II, OPM II, or with the parameters for transmit detailed routing when using
SICAM WEB.
Parameter category:
firmware /Trans_counter_value
Parameter Meaning
CASDU2 0 to 255
IOA1
IOA2
IOA3
• Counter value 31 bit with sign with sequence number <TI:=37>

RP570-Format • PCM
• PCT

DC8-037-2, Edition 11.2020
12.16 ABB RP570/571
Parameter Meaning
• Priority 2
• Priority 3
PCM_PCT-Quality-bits Quality bits to be set in the PCM/PCT message
• Form bits on the most recent count interrogation348

• EPR = 1; IR = 0, LS = 0
• EPR = 0; IR = 1; LS = 0
• EPR = 1; IR = 1, LS = 0
• EPR = 1; IR = 0; LS = 1
• EPR = 0; IR = 1, LS = 1
• EPR = 1; IR = 1; LS = 1
348 "intermediate reading" (FCOM # 3): IR = 1, "end of period reading" (FCOM # 3): EPR = 1

DC8-037-2, Edition 11.2020
12.16 ABB RP570/571
Fault Distance – Measured Value
EVENT RECORDING MESSAGE FAULT DISTANCE (ERMFD)
[rp5u33, 1, --_--]

SEQUENCE NO Sequence number
The sequence number (0 to 255) is incremented for each event recording
message ERMxx. The first value is transmitted with 0; then, the sequence
number is incremented from 255 to 1

DC8-037-2, Edition 11.2020
12.16 ABB RP570/571
FORMAT Coding of "VALUE":

000: 32 bit unsigned integer; not supported
001: 32 bit signed integer; not supported
010: short real number (IEEE STD 754)
VALUE 32 bit value coding according FORMAT
OF 1 = buffer overflow
Not supported by the firmware; always "0"
NS 1 = clock of RTU is not synchronized if time tag of the information is marked as
“invalid”
T QUALITY Time quality
000 time is valid
001 ms and lower is not valid, not supported by the firmware
010 ms x 10 and lower is not valid, not supported by the firmware
011 ms x 100 and lower is not valid, not supported by the firmware
100 second and lower is not valid, not supported by the firmware
101 second x 10 and lower is not valid, not supported by the firmware
Is set if an error occurs on conversion to RP570 time format.
DAY OF MONTH Day of current month
TIME Time since midnight in intervals of 0.1 ms
NUMBER Fault number, always "1"
RELATIVE TIME Relative time since general start of operation (n ⋅ 1 ms); always "0"
CAUSE OF TRANSMISSION Spontaneous = "1"
Conversion
• Each event is transmitted (value has been changed or not) but the value must be valid (NT = 0, IV = 0, OV
= 0)
• No transmission of the event if cause of transmission is background scan (= 02) or interrogated by station
interrogation in the normal case
• Value adaptation also possible

SICAM WEB.

DC8-037-2, Edition 11.2020
12.16 ABB RP570/571
Parameter category:
Parameter Meaning
CASDU2 0 to 255
IOA1
IOA2
IOA3
• Measured value 15 bit + sign-normalized <TI:=34>

• Measured value 15 bit + sign-scaled <TI:=35>
RP570-Format ERMFD
RP570-Priority Irrelevant for fault distance
RP570-DVM-coding Coding of digital measured values
Irrelevant for fault distance

DC8-037-2, Edition 11.2020
12.16 ABB RP570/571
Parameter Meaning
• <TI:=34>: -1 to +1
• <TI:=35>: -32768 to +32767
• <TI:=34>: -1 to +1
• <TI:=35>: -32768 to +32767
Conversion of measured value: refer to 12.16.6.8 Conversion of Measured Values.
12.16.7.3 System messages
Terminal Status Message (TSTA)

TSTA messages are system information of the RTU itself. 8 different TSTA messages are handled for each
process-RTU-No, which are initialized after restart with predefined values (refer to 12.16.6.5 Terminal Status
Message (TSTA)). If these predefined messages are not acceptable, the TSTA messages can be updated with
single point information (TI 30). The access to the internal process image happens with the RP570 message
reference (refer to Address Conversion). The transmission of the TSTA message happens only upon change of
status.
Terminal Status Message (TSTA)
[rp5u34, 1, --_--]

DC8-037-2, Edition 11.2020
12.16 ABB RP570/571
IDENT Identification of status information

RTU STATE Status flags of RTU (= Inf. 0 to 15)

The parameterization of the address and message conversion for system information in transmit direction is to
SICAM WEB.
Parameter category:
firmware /Trans_TSTA
Parameter Meaning
CASDU2 0 to 255
IOA1
IOA2
IOA3
• Single point information <TI:=30>

RP570-Process-RTU-No. 1 to 254
RP570-Ident-No. 0 to 15
RP570-Object-No. 0 to 2047
RP570-Bit-No. Bit number within the Ident-No.
0 to 15
RP570-Message refer- The message reference is used for access to the data base of the different TSTA
ence: messages
0 to 7
Terminal Event Message (TEV)

TEV messages are system information of the RTU itself. 8 different TEV messages are handled for each
process-RTU-No, which are initialized after restart with predefined values (refer to 12.16.6.6 Terminal Event
Message (TEV)). If these predefined messages are not acceptable, the TSTA messages can be updated with bit
string 32 bit (TI 33). The access to the internal process image happens with the RP570 message reference
(refer to Address Conversion). The transmission of the TEV message happens only upon change of status.

DC8-037-2, Edition 11.2020
12.16 ABB RP570/571
[rp5u35, 1, --_--]
EVENT NO Terminal Event Number

The parameterization of the address and message conversion for system information in transmit direction is to
SICAM WEB.
Parameter category:
firmware /Trans_TEV

DC8-037-2, Edition 11.2020
12.16 ABB RP570/571
Parameter Meaning
CASDU2 0 to 255
IOA1
IOA2
IOA3
• Bit string 32 bit <TI:=33>

RP570-Process-RTU-No. 1 to 254
RP570-Event-No. 0 to 31
RP570-Message reference The message reference is used for access to the data base of the different TEV
messages
0 to 7
TEV-INFO-Offset Byte offset in the TEV message from which the data bytes of the information
object (= bit string of 32 bit) are inserted
0 to 5
TEV-INFO-byte-count Number of bytes of the information object (= bit string of 32 bit) which are
inserted in the TEV message
1 to 4
Table 12-19 Example:
RP570-Prozess-RTU-No: =x
RP570-Event-No: = 23
RP570-Message reference: =3
TEV-INFO-Offset: =1
TEV-INFO-byte count: =4
Table 12-20 Terminal Event Message (after restart)
EVENT-NO = 1
INFO 1 = 0
INFO 2 = 0
INFO 3 = 0
INFO 4 = 0
INFO 5 = 0
INFO 6 = 0

DC8-037-2, Edition 11.2020
12.16 ABB RP570/571
Terminal Event Message (updating)
[rp5u36, 1, en_US]
12.16.8 Message Conversion In Receive Direction (SICAM A8000 ← RP570/571)
Table 12-21 Supported message formats:
ABB RP570/571 SICAM A8000

Func. Message Message Designation Message Designation
code
Data Request Messages
0 RA REQUEST A -
8 RB REQUEST B -
4 RX REQUEST X Request of a certain block number AVS,
IDS, DVM supported
System commands:
15 SCI STATUS CHECK INSTRUCTION General interrogation (from data base)
7 RSEQ RESET SEQUENCE NUMBER -
6 FCOM FUNCTION COMMAND Restart RTU
#1 Activate RTU
#2 Counter interrogation message
#3 Telephone “hang up” (start active call up)
#11 Set RTU in/out of Service
#13
12 TSI TIME SYNC INSTRUCTION Time synchronization
2 FTAB FUNCTION TABLE
Indications
#0
Analog measured values
#10
Process information:
9 IXC IMMEDIATE EXECUTED COMMAND Single command <TI:=45> (execute)
Double command <TI:=46> (execute)
Regulating step command <TI:=47>
(execute)

DC8-037-2, Edition 11.2020
12.16 ABB RP570/571
ABB RP570/571 SICAM A8000

5 CBXC CHECK BACK BEFORE EXECUTE COMMAND Single command <TI:=45> (select)
Double command <TI:=46> (select)
(select)
3 IHC INHIBIT COMMAND Single command <TI:=45> (cancel)
Double command <TI:=46> (cancel)
(cancel)
13 EXC EXECUTE COMMAND Single command <TI:=45> (execute)
Double command <TI:=46> (execute)
(execute)
1 SPM SET POINT MESSAGE Measured value 15 Bit + sign normalized
<TI:=34>
Measured value 15 Bit + sign scaled
<TI:=35>
Measured value short floating point
<TI:=36>
Setpoint command normalized <TI:=48>
Setpoint command scaled <TI:=49>
Setpoint command short floating point
<TI:=50>
11 GOM GENERAL OUTPUT MESSAGE Measured value 15 Bit + sign normalized
<TI:=34>
Measured value 15 Bit + sign scaled
<TI:=35>
Measured value short floating point
<TI:=36>
Setpoint command normalized <TI:=48>
Setpoint command scaled <TI:=49>
Setpoint command short floating point
<TI:=50>
Single command <TI:=30>
Double command <TI:=31>

DC8-037-2, Edition 11.2020
12.16 ABB RP570/571
12.16.8.1 Data Request Messages
Request A (RA)
[dw_rp5u01, 1, --_--]
Figure 12-43 Request A message
The master station uses the service “Request A” for requesting of information of priority level 1 from the RTU.
If no information is available the RTU responds with CCR1.
Attention: The firmware responses “Request A” always with CCR1.
Request B (RB)
[dw_rp5u02, 1, --_--]
Figure 12-44 Request B message
The master station uses the service “Request B” for requesting of information of priority levels (= 1, 2, 3) and
all events from the RTU. If no information is available the RTU responds with CCR2.
Request X (RX)
The service “Request A” allows the master station to request a certain information object from the RTU – speci-
fied by data type and block number.

DC8-037-2, Edition 11.2020
12.16 ABB RP570/571
[dw_rp5u03, 1, --_--]
Figure 12-45 Request X message
DTYPE 0 0 0 = Indications
0 0 1 = Pulse counter values, not supported
0 1 0 = Analog values
0 1 1 = Digital values
1 0 0 = SUB-RTU polling status, not supported
1 0 1 = SUB-RTU polling acknowledgement, not supported
BLOCK NUMBER Block number of the request point
If the requested information object does not exist in the data base or DTYPE is not supported, the firmware
responds with NXR (not execute response). If the requested information object exists in the data base, the
firmware responds with the corresponding message format (with parameterized priority level; indications and
analog measured values always with status).
12.16.8.2 System commands
Status Check Instruction (SCI)

The service “Status Check Instruction” (general interrogation) always uses the central station to update its data
base.
If the SCI is directed to the own RP570-RTU-No it can be defined, if only information of the request RTU-No or
of all RTU-No (only RP571 mode) should be transmitted.

DC8-037-2, Edition 11.2020
12.16 ABB RP570/571
[rp5u04, 1, --_--]
Figure 12-46 Status Check Instruction-message
Response:
• EXR resp. EXRR
• NXR: SCI to an unknown process-RTU-No. (only RP571 mode)
NOTE
i EXRR is only responded if the SCI was received in the message format with fixed block length.
Function Command (FCOM)

“Function Commands” are RP570/571-specific system commands; only a subset of the defined FCOM
messages is supported. Not supported FCOM messages are responded with NXR.

DC8-037-2, Edition 11.2020
12.16 ABB RP570/571
[rp5u05, 1, --_--]
Figure 12-47 Function Command Message
FCOM NO Function Command Number

SATELLITE LINE Satellite Line number: not evaluated
SATELLITE RTU NO Satellite RTU number: not evaluated
INFO1 to INFO6 additional information of FCOM
Supported FCOM messages:
Designation FCOM Additional information

No.
Cold Start 1
Activate RTU 2
Reading of pulse counters 3 INFO1 = 1: intermediate (= transmit)
INFO1 = 2: end of period (= freeze + transmit)
Telephone hang up 11 INFO1 = 2: start active call up349
Subordinate RTU in/out of Service 13 INFO1 = 1: In service
INFO1 = 2: Out of service
349 only supported if radio spontaneous mode is enabled

DC8-037-2, Edition 11.2020
12.16 ABB RP570/571
Cold Start (FCOM-No = 1)
• Perform a restart of the automation unit

Restart is only performed if the FCOM message is addressed to the own RP570-RTU-No or “broadcast”
• If the FCOM message is not addressed to the own RP570-RTU-No (only in RP571 mode) the firmware
responds with NXR
Activate RTU (FCOM-No = 2)
• “Activate RTU” is used to activate the substation after concluding parameter download of original ABB
substations. The firmware does not evaluate the parameter messages (FTAB), but in some cases this
behavior must be evaluated (see 12.16.6.7 Activation of the Substation).
• Response: always EXR

Reading of pulse counters (FCOM-No = 3)
• INFO1 = 1: intermediate reading = read, transmit (FRZ = 0)
• INFO1 = 2: end of period reading = freeze (FRZ = 1) + read, transmit (FRZ = 0)
• Conversion: counter request message (FC = 153), broadcast address (CASDU=FF, FF), request counter
group parameterizeable (group 1 to 4, all groups)
• Process-RTU-No is not evaluated in RP571 mode.
• Response: always EXR

Telephone hang up (FCOM-No = 11)
• “Start active call up” (INFO1 = 2) is supported only when radio spontaneous mode is enabled.
This command instructs the secondary station to transmit a “polling request instruction”, if important
information (data class 1, example: indications, system messages) is ready for sending.
Response:
EXR … if radio spontaneous mode is enabled
NXR … if radio spontaneous mode is disabled
• All other commands of FCOM-No = 11 are not supported

Response: NXR
Subordinate RTU in/out of Service (FCOM-No = 13)
• FCOM 13 commands are only responded by the firmware; however no further actions are performed. The
transmission of “Terminal Status” indications (TSTA) and “Terminal Event” indications (TEV) can be
performed.
System technical parameterization: system indications (TSTA, TEV) after FCOM 13
• Response:
– EXR
– NXR (unknown Process-RTU-No with RP571 mode)

DC8-037-2, Edition 11.2020
12.16 ABB RP570/571
Reset Sequence Number (RSEQ)
[rp5u06, 1, --_--]
Figure 12-48 Reset Sequence Number message
The substation initializes the sequence number (to “0”) and confirms the last sent message negatively (only
AU-internal).
NOTE
i RSEQ request does not retrigger communication monitoring (call monitoring time), if radio spontaneous
mode is enabled.

DC8-037-2, Edition 11.2020
12.16 ABB RP570/571
Time Synchronisation Instruction (TSI)
[rp5u07, 1, --_--]
Figure 12-49 Time Synchronisation Instruction-message
DATE day since 1.1.1980 (= 1. day)

TIME time since 0 intervals of 0,1 ms
The firmware corrects the received time by the transmission delay of the message.
Response: always EXR
Function Table (FTAB)

“Function Table” messages are used for parameter download of the RTU. The firmware does not evaluate this
message but responds it with EXR.
For blocking of indications and analog measured values it is necessary to evaluate certain FTAB messages.

DC8-037-2, Edition 11.2020
12.16 ABB RP570/571
Parameter – Messages (FTAB-Type = 0; 24 Byte Parameter)
[rp5u08, 1, --_--]
Figure 12-50 Function Table messages
1)„Blocked” information; 1 (2) bits for each indication within the block number
0 = normal, 1 (11) = blocked
Only BLOCK NO and BLOCKED is evaluated.

DC8-037-2, Edition 11.2020
12.16 ABB RP570/571
Parameter – analog measured value (FTAB-Type = 10; 13 Byte Parameter)
[rp5u09, 1, --_--]
Figure 12-51 Function Table message
Only BLOCK NO and the bit BLK is evaluated.

BLK = 0 … normal
BLK = 1 … blocked
Response of FTAB-Type = 0 and 10
• EXR: Block-No exists in data base
• NXR: Block-No and/or Process-RTU-No does not exist in data base

Response of all other FTAB-Types
• EXR: Process-RTU-No exists in data base
• NXR: Process-RTU-No does not exist in data base

DC8-037-2, Edition 11.2020
12.16 ABB RP570/571
12.16.8.3 Process information
Direct Commands (Immediate Execute Command)

[rp5u10, 1, --_--]
OBJECT NUMBER object number of command

CTYPE 0 = object command with short time
1 = regulating command with long time
2 = not used
3 = not used
4 = object command with long time
5 = not used
6 = not used
7 = not used
STO 1 = stop running regulating command (valid only for CTYPE = 1)
not evaluated
ON/OFF 0 = OFF
1 = ON
Response:
• EXR:
– Command address (process-RTU-No and object-No) is defined in SIP address message conversion
and command address is not selected on a Check Back before Execute command"
• NXR:
– Command address is not defined in SIP address message conversion
– RP570-Process-RTU-No unknown
– CTYPE not supported
Spontaneous forwarding:
• Cause of transmission = Activation (= 6)
• Command state (SCS, DCS) = ON/OFF from received message

DC8-037-2, Edition 11.2020
12.16 ABB RP570/571
• Quality of command (QOC) = parameterizeable
• Select/Execute (S/E) = always "0" (= execute)
Address conversion RP570/571 → SICAM A8000

The parameterization of the address and message conversion for commands in receive direction is to be done
with the SICAM TOOLBOX II, OPM II, or with the parameters for receive detailed routing when using SICAM
WEB.
Parameter category:
Parameter Meaning
CASDU2 0 to 255
IOA1
IOA2
IOA3

RP570-Format Commands
RP570-Object-No 0 to 2047

DC8-037-2, Edition 11.2020
12.16 ABB RP570/571
Parameter Meaning
RP570-QOC Command output duration to be added on (QOC)
• Command output time from messages (CTYPE)

– Long command output time = CTYPE = 4 or CTYPE = 1
– Short command output time = CTYPE = 0
• Pulse command with short output time
• Pulse command with long output time
• Pulse command without output time
• QOC acc to preadjustment (RWE)
• Preadjustment interlocking command (RWE)
• Preadjustment PSG command (RWE)
DM_DB-Inverting Inverting of double point information, double command or regulating step
command
• yes
• no
Select Before Execute Commands

For Select Before Execute commands 3 message formats are used:
• Check Back before Execute Command (CBXC; FCode = 5)
• Execute Command (EXC; FCode = 13)
• Inhibit Command (IHC; FCode = 3)

The message formats “check back before execute command” and “inhibit command” do not include the
command state (ON/OFF), therefore these messages must be handled by the firmware specially.
[rp5u11, 1, --_--]

DC8-037-2, Edition 11.2020
12.16 ABB RP570/571
OBJECT NUMBER object number of command

CTYPE 0 = object number with short time
4 = object number with long time
ON/OFF only at “Execute Command”
0 = OFF
1 = ON
The Select command (CBXC) can not be forwarded immediately to the automation unit (SICAM A8000)
because CBXC does not contain the command state. Therefore the firmware stores the command address
(RP570-Process-RTU-No and block number) and is waiting for the Execute command (timeout = 10 s).
If the Execute command is received within timeout and the command address (of execute) is equal to the
Select command, then the Select command is forwarded with the command state of the Execute command to
the automation unit; after a parameter-settable delay the Execute command is forwarded.
NOTE
i Up to 5 Select before Execute commands can be handled simultaneously.
• Cause of transmission = Activation (=6)
• Command state (SCS, DCS) = ON/OFF from received message
• Quality of command (QOC) = parameterizeable
• Select/execute (S/E)
– "1" … select command
– "0" … execute command
Block diagram (OK-case)
[rp5u12, 1, en_US]

DC8-037-2, Edition 11.2020
12.16 ABB RP570/571
Response of CBXC
• CBR:
– Command address (RP570-Process-RTU-No und block number) is defined in SIP-address message
conversion and command is not selected till now.
• NXR:
– Command address unknown
– Process-RTU-No unknown (protocol type = RP571)
– Command is already selected
Response of EXC and IHC
• EXR:
– Command address is equal to the address of CBXC
• NXR:
– Command address unknown
– Command address is not selected (timeout already expired)
– Process-RTU-No unknown (protocol type = RP571)
– CTYPE not supported

The parameterization of the address and message conversion for commands in receive direction is to be done
WEB.
Parameter category:

DC8-037-2, Edition 11.2020
12.16 ABB RP570/571
Parameter Meaning
CASDU2 0 to 255
IOA1
IOA2
IOA3

RP570-Format Commands
• Command output time from messages (CTYPE)

– Long command output time = CTYPE = 4 or CTYPE = 1
– Short command output time = CTYPE = 0
• Pulse command with short output time
• Pulse command with long output time
• Pulse command without output time
• QOC acc. to preadjustment (RWE)
• Preadjustment interlocking command (RWE)
• Preadjustment PSG command (RWE)
command
• yes
• no

DC8-037-2, Edition 11.2020
12.16 ABB RP570/571
Indications in Command Direction
GENERAL OUTPUT MESSAGE (GOM)

[rp5u13, 1, --_--]
OBJECT NO object number
[rp5u13a, 1, en_US]
IND State of Indication
• Cause of transmission = spontaneous (=3)
• State of single point information = “LSB” of RP570-State of Indication (IND)
• State of double point information = RP570-State of Indication (IND)

The parameterization of the address and message conversion for indications in receive direction is to be done
WEB.

DC8-037-2, Edition 11.2020
12.16 ABB RP570/571
Parameter category:
Parameter Meaning
CASDU2 0 to 255
IOA1
IOA2
IOA3
• Single point information <TI:=30>

• Double point information <TI:=31>
RP570-Format GOM
• NOT USED
command
• yes
• no
Measured Values, Setpoints in Command Direction

For transmission of setpoints or measured values (in command direction) two different RP570- message
formats are used:
• Set Point Message SPM (FCode = 1)
• General Output Message GOM (FCode = 11)

Both message formats allows the transmission of analog values (12 bit bipolar) or digital values (16 bit
bipolar).

DC8-037-2, Edition 11.2020
12.16 ABB RP570/571
[rp5u14, 1, --_--]
OBJECT NO Object number
Setpoint coding: analog (12 Bit bipolar)
[rp5u15, 1, en_US]
Coding happens in 12 bit two's complement, extended to 16 bit.
Setpoint coding: digital (16 Bit bipolar)
[rp5u15a, 1, en_US]
Coding happens in 16 bit two's complement.

Response
• EXR:
– RP570-Address (process-RTU-No and block number) in SIP-address message conversion defined and
conversion of value ok

DC8-037-2, Edition 11.2020
12.16 ABB RP570/571
• NXR:
– RP570-Process-RTU-No unknown (protocol type = RP571)
– RP570-Address unknown
– Conversion of value not possible (i.e. setpoint to large)

The parameterization of the address and message conversion for measured values or setpoints in receive
direction is to be done with the SICAM TOOLBOX II, OPM II, or with the parameters for receive detailed routing
when using SICAM WEB.
Parameter category:
firmware /Rec_value
Parameter Meaning
CASDU2 0 to 255
IOA1
IOA2
IOA3

• Setpoint value 15 bit + sign normalized <TI:=48>
• Setpoint value 15 bit + sign scaled <TI:=49>
• Setpoint value short floating point <TI:=50>
RP570-Format • SPG
• GOM
RP570-Setpoint-coding • 12 bit bipolar (analog)
• 16 bit bipolar (digital)

DC8-037-2, Edition 11.2020
12.16 ABB RP570/571
Parameter Meaning
• -32768 to +32767 (16 bit bipolar)

• -2048 to +2047 (12 bit bipolar)
• -32768 to +32767 (16 bit bipolar)

• -2048 to +2047 (12 bit bipolar)
• <TI:=34, 48>: -1 to + 1
• <TI:=35, 49>: -32768 to +32767
• <TI:=36, 50>: no check
• <TI:=34, 48>: -1 to + 1
• <TI:=35, 49>: -32768 to +32767
• <TI:=36, 50>: no check
Value Conversion
The conversion of the received setpoint commands or measured values can be done with or without linear
adaption.
Conversion without linear adaption:
• X_0% = 0 and X_100% = 0
• <TI:=34, 48>
Setpoint value coding = 12 bit bipolar (analog) → 2000 = 100 %
Setpoint value coding = 16 bit bipolar (digital) → 32000 = 100 %
Conversion with linear adaption:
• X_0% <> 0 or X_100% <> 0
• X_0% < X_100%
• X_0% ≤ received value ≤X_100%

DC8-037-2, Edition 11.2020
12.17 Benning MCU
12.17 Benning MCU
The BMCUT0 protocol element (Benning MCU ASCII protocol) is used to connect Benning MCU systems in
series.
The Benning MCU ASCII protocol is a proprietary protocol from Benning. The protocol that has been provided
by the Benning MCU 2000 meets the requirements of the SvSig guideline (TLS/94) put in place by Deutsche
TELEKOM to its fullest extent. However, it was expanded in many respects for flexible use.
In the SICAM A8000, the protocol elements takes over the master station functionality for connecting max. 1
Benning MCU substation during communication.
The Benning MCU ASCII protocol is an end-to-end traffic protocol with query mode for log (transmitting indica-
tions and measured values). Only command telegrams (query/control commands) are transmitted by the
master station. Data is only transmitted from the substation to the master station after an interrogation
command.
The tasks of the protocol element are as follows:
• Converting the IEC 60870-5-101/104 data to Benning MCU ASCII protocol
• Adapting the system and addressing concepts for the SICAM A8000 and the Benning MCU
NOTE
i Only the functions that have been implemented for the Benning MCU ASCII protocol in the SICAM A8000
system are described in this document.
Configuration
Example: SICAM A8000 CP-8000 configuration with Benning MCU 2500
[Benning_Configuration_CP_8000, 1, --_--]

DC8-037-2, Edition 11.2020
12.17 Benning MCU
Overview of Systems with Benning MCU ASCII Protocol
Designation
Benning MPR2600 with alarm and
system monitoring module: MCU
100
Benning MPR5400 with alarm and

system monitoring module: MCU
1000
Benning MCU 1000/2000+
Benning modular rectifier slot with

MCU 2500

DC8-037-2, Edition 11.2020
12.17 Benning MCU
12.17.2 Functions
Function BMCUT0
■ Serial communication protocol according to Benning MCU ASCII protocol ✓
– Central station function ✓
– Substation function
■ Network configuration
– Point-to-point configuration ✓
– Multiple point-to-point configuration (each point-to-point configuration requires a separate ✓
interface)
– Multipoint-partyline configuration
– Multipoint-star configuration ✓
– max. connections (for each interface) 1
■ Physical layer/data flow control
– RS-232 (unbalanced interface according to V.24/V.28) ✓
– RS-485 (unbalanced interface according to V.11)
– RS-422 (unbalanced interface according to V.11) ✓
– Balanced interface according to X.24/X.27
– Data transmission route (full duplex)
– Data transmission route (half duplex) ✓
– Byte frame (7E1, 7º1, 7N1, 8E1, 8º1, 8N1) ✓
– Byte frame (7E1.5, 7º1.5, 7N1.5, 8E1.5, 8º1.5, 8N1.5) ✓
– Byte frame (7E2, 7º2, 7N2, 8E2, 8º2, 8N2) ✓
– Modulated pulse code, asynchronous byte (pulse-code modulation) ✓
– LSB (least significant bit) is transmitted first ✓
■ Supported baud rates
– 50, 75, 100, 110, 134.5, 150, 200, 300, 600, 1050, 1200, 1800, 2000, 2400, ✓
4800, 9600, 19200
■ Telegram protection
– Protecting telegrams for commands, acknowledgement -
– CRC-16 telegram protection according to DIN 66219 Part 4 (for indication/measured value ✓
protocol)
■ Interoperability
– Benning MCU ASCII protocol (partial functions) ✓
– ASCII character according to MS-DOS code page 437 ✓
■ Benning MCU ASCII protocol – Data communication control
– Request response ✓
– Half duplex ✓
■ Benning MCU ASCII protocol – supported message formats in the monitoring direction (receive
direction)
– Protocol (measured value/indication message) ✓
– Acknowledgment ✓
■ Benning MCU ASCII protocol – supported message formats in the command direction (transmit
direction)
– AA ..... Interrogate the last 10 indication protocols
– AB ….. Interrogate current protocol ✓
– AL ….. Switching over to equalization charging ✓
– DL ….. Switching over to TRICKLE CHARGING ✓

DC8-037-2, Edition 11.2020
12.17 Benning MCU
Function BMCUT0
– DR ….. Switching over to direct power supply ✓
– EN ….. Resetting overvoltage shutdown ✓
– LA ….. Switching over to CHARGE ✓
– RD ….. Resetting redundancy ✓
– SA … SL ….. Signal check for relay 1 .. 12 ✓
– TB ….. Start battery test ✓
– TE ….. End battery test ✓
– WI .... Repeat protocol that was transmitted most recently
– SERVICE .… Service release via the modem
– ZT ..… Change date and time
■ Data acquisition by querying ✓
■ Acquisition of events (transmitting data ready for sending) ✓
■ General interrogation, substation interrogation ✓
■ Time synchronization
■ Command transmission ✓
– Setting the control location
– ACTCON, ACTTERM emulation (inside the SICAM A8000)
■ Metered value transmission
■ File transfer
■ Optimized parameters for selected transfer directions
– Predefined parameters for selected transmission facilities
– Providing connected 5 V transmission facilities
(via DSR state line)
ATTENTION: Check current consumption of transmission facility!
■ Message conversion in transmit direction: SICAM A8000 → Benning MCU (command or
control direction)
– <TI:=45> ..… Single command ✓
– <TI:=100> … General interrogation command ✓
■ Message conversion in receive direction: SICAM A8000 ← Benning MCU (indication or monitoring
direction)
– <TI:=30> ... Single-point indication with time marker CP56Time2a ✓
– <TI:=36> … Measured value, short floating-point number with time marker ✓
■ Redundancy (functions to support redundant ways of communication)
– PRE redundancy
– Listening mode when passive
– Tristate of the RS-232 interface when passive
■ Control and feedback of protocol elements
● Protocol element control messages
– Send (general) interrogation command to all ✓
– Transmit (general) interrogation command to GI group ✓
– Send (general) interrogation command to selective CASDU ✓
– Send reset command
– Setting the control location
● Protocol element return messages

DC8-037-2, Edition 11.2020
12.17 Benning MCU
Function BMCUT0
– Station failure
– Station status
– DTR status (1= status line active)
– DSR status (1= status line active)
■ Remote maintenance with SICAM TOOLBOX II via serial connection with Benning MCU ASCII
protocol
■ Special functions
■ Parameterization
– SICAM TOOLBOX II + OPM ✓
– SICAM WEB Engineering ✓
NOTE
i The protocol element doesn’t transmit any commands when protocol transmission is running. A half duplex
transmission medium can be used as a result.
This means that commands can be transmitted with a delay! Spontaneous transmit mode for protocols may
not be used in the Benning MCU!
Constraints
• Only a subset of the functionality and telegram formats that have been defined as per the Benning MCU
ASCII protocol is supported.
• Only a subset of the message formats that have been defined according to IEC60870-5-101-/104 is
supported for message conversion.
• RS-485 is not supported.
• Max. 100 indications possible.

(Benning MCU supports max. 100 indications)
• Max. 120 measured values possible.

(Benning MCU supports max. 120 indications)
• Max. 10000 characters can be used for the indication/measured value telegram (Protocol)
.
• A pause of min. 10 seconds must be adhered to between the protocols when protocols are being queried
in a cyclical fashion (continuous protocol query: typically 20 s; min. 10 s)
• Half duplex mode (if the Benning MCU transmits, receive is blocked, and the MCU doesn’t process inqui-
ries that have been made in the intervening period).
• Redundancy is not supported!
• Time synchronization is not supported.
NOTE
i This protocol element is mainly used to connect third-party devices, so it has only implemented a part of
the functionality and data formats that the protocol defines. Therefore, you always need to check whether
the supported functionality corresponds to the functionality required for the project or whether additional
functions are or adaptations are required for a clear use case.

DC8-037-2, Edition 11.2020
12.17 Benning MCU
ment.
optional DCE
Unbalanced interchange circuit (V.24/V.28) X2 RXD, TXD, CTS 350, RTS, DCD, DTR,
Balanced interface (V.11) RS-422 (4-wire) asyn- X3 TXD+, TXD-, RXD+, RXD- (4-wire)
chronous
Balanced interface (V.11) RS-422 (4-wire) asyn- X2 → CM-0829 RXD, TXD, CTS, RTS, DCD, DTR, DSR/
chronous VCC, GND (for CM-08x9)
Optical interface (multi mode fiber optic) ring X2 → CM-0821 RXD, TXD, CTS, RTS, DCD, DTR, DSR,
GND (for CM-0821)
Unbalanced interchange circuit (V.24/V.28) X6 351 RXD, TXD, CTS, RTS, DCD, DTR, DSR,
NOTE

SICAM A8000 Series CP-8000/CPC80 BMCUT0 max. 1 remote station
CP-802x/CPC80
Remote Station (Substation)

Third-party system – – Benning MCU-100
Benning MCU-1000
Benning MCU-2000
Benning MCU-2500
(or another third-party
system according to the
Benning MCU ASCII
protocol functions that
have been implemented
in the SICAM A8000
series)


DC8-037-2, Edition 11.2020
12.17 Benning MCU
12.17.5.1 Address Field (Substation or Device Address)

The Benning MCU ASCII protocol does not define an address field for a station address. Command telegrams
and acknowledgment messages are transmitted without an address.
The operation location identifier (12-digit alphanumeric code for identifying the plant to be called) must be
entered in data messages (indication/measured value protocol) as an address.
This address is checked by the protocol element in the master station. If the operating position identifier that
has been received does not match the one that has been parameterized, then the received data is not
accepted.

The following V.24 interface lines are used for the RS-232 interface:
Interface line number Designation Use
TxD <103> TRANSMIT DATA Transmit data
RxD <104> RECEIVE DATA Receive data
GND <102> SIGNAL GROUND
The following V.24 interface lines can be used as an option for the RS-232 interface:
Interface line number Designation Use
RTS <105> REQUEST TO SEND Switching on the transmit signal level of
the transmission facility
RTS = always ON
Additional external converters must be used for the RS-422 in conjunction with the RS-232 interface.
Wiring for CP-8000/X2 connection ↔ Benning MCU (D-Sub – D-Sub) with a 3-wire null modem cable
NOTE
i With a serial connection via X2, a jumper is required between CTS and GND, providing the interface shall
also be used for the connection with the project engineering PC.
Define with a dedicated parameter (Serial Communication Settings | Serial Engineering
Interface = Disabled) that interface X2 is not used for parameter configuration. Thus no connection

DC8-037-2, Edition 11.2020
12.17 Benning MCU
Wiring for CP-8000 connection ↔ Benning MCU (D-Sub – D-Sub) with null modem cable 2xDB9F 1.8 m
TF5-204--
NOTE
i If a null modem cable is used for the connection between the SICAM A8000 and the Benning MCU, then
the X2 interface must be blocked using the parameterSerial Communication settings |
Serial Engineering Interfaceon the CP-8000/CPC80.
ATTENTION
The Benning system (for example: MCU 1000/2000+) <as an option> can release a fixed voltage (approx. 10
V) to selected status line inputs for the RS-232 interface (for example: DCD, DSR)!
When using a null modem cable for the SICAM A8000, these status lines must be alternatively
• deactivated in the Benning system using jumpers or
• disconnected in the null modem cable (in the plug or with a suitable adapter)
Wiring for CP-8022/X6 connection ↔ Benning MCU
Recommended D-sub/RJ45 adapter:

RS Pro MHDA9-SMJ8-M-K. This adapter provides a wired RJ45 socket and an unwired D-sub plug (female).
RJ45 socket wiring: Wiring at 9-pole D-sub plug:

DC8-037-2, Edition 11.2020
12.17 Benning MCU
Pin Wire color

1 Black Pins at the D-sub plug can be assigned according to wiring
2 yellow diagram.
3 orange
4 red
5 green
6 Brown
7 Gray
8 Blue
Unused cores must be insulated!
Shield Black
When using the shield, it must be soldered to the metal plate of
the D-sub plug.

The data is pulse-code modulated in groups of 7 to 8 bit and transmitted asynchronously. A USART building
block in asynchronous mode provides each byte with a byte frame in the process.
1 Start bit
8 Data bits
1 Parity bit (no parity)
1 Stop bit
The byte frame can be parameterized (system parameter).

byte.
[7-8-bit-information, 2, en_US]
Figure 12-52 Benning MCU Byte Frame

DC8-037-2, Edition 11.2020
12.17 Benning MCU
12.17.6 Communication according to Benning MCU
12.17.6.1 Data Acquisition by querying

The data (measured values, indications) is transmitted from the Benning substations to the SICAM A8000
central station via interrogation commands, which are controlled by the central station, this means that data
that has changed is stored in the substation and transmitted to the central station if this substation is queried.
Measured values and indications are transmitted by the Benning substation as a protocol. The data message
must always include all parameterized measured values and all parameterized indications.
The interrogation procedure can be carried out either continuously (continuous cycle) or only on request.
The interrogation cycle must be parameterized for the current protocol in the central station using the param-
eter Advanced parameters | cycle time for "require last protocol".
The current protocol is typically queried every 20 seconds.
NOTE
i The current protocol may not be queried for < 10 seconds!
The commands that have been transmitted must be acknowledged by the substation. Transmission of a data
message is triggered by the substation as a result, depending on the function of the command to be trans-
mitted.
Example:
Central station → Substation: Command “Interrogate current protocol”
Central station ← Substation: Acknowledgment
Central station ← Substation: “Current protocol”
No additional commands must be transmitted from the substation → to the central station when transmitting
data messages from the substation → to the central station.
If the Benning MCU transmits, receive is blocked, and the MCU doesn’t process inquiries that have been made
in the intervening period!
NOTE
i The IEC60870-5-101/-104 parameter setting on the base system element is not relevant for the BMCUT0
protocol element!
Acknowledgment procedure
All messages (commands) transmitted to a substation must be acknowledged by it. If, with non-faulty trans-
mission line, the acknowledgment is missing for longer than the expected acknowledgment 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 acknowledgement expectation time is set using the parameter Advanced parameters | Moni-
toring times | Expected acknowledge time.
NOTE
i The internal Benning preparation time and complete protocol transmission must be taken into account in
the acknowledgment expectation time.
The number of retries must be set in the central station using the parameter Message retries |
Retries for data message SEND/CONFIRM (station-selective)

DC8-037-2, Edition 11.2020
12.17 Benning MCU
A data message that is transmitted by the substation to the central station is not acknowledged by the central
station.
If the current protocol is transmitted with errors, the current protocol is queried again in the next interrogation
grid.
NOTE
i If the “interrogate current protocol” command is acknowledged from the substation, but the current
protocol is not transmitted n times by the substation (n = number of retries), then the data from the
current protocol is emulated as failed by the central station protocol element (NT = 1).
Failure Monitoring System in the Central Station

The interface in the central station is monitored by checking cyclical message reception, which is controlled by
cyclical querying of the current protocol, and by monitoring acknowledgement of transmitted commands.
If the interface fails, the parameterized data points in receive direction are emulated by the basic system
element as if they are faulty (NT = 1).
Interrogation commands in transmit direction are transmitted without any retries if the interface fails (number
of retries = 0) and then discarded.
Recording Events (Transferring Data Ready for Sending)

Substation data that is ready to be transmitted is stored in the substation until transmission takes place. This
function is carried out by the Benning MCU and cannot be influenced by the central station.
The current values are always transmitted for all parameterized measured values and indications with the
current protocol. If fault occurred when transmitting the current protocol, MTLs may be lost if the indication
status has changed by the next transmission.
Message from the Substation and the Central Station

Messages from the substation to the central station are only transmitted after a command (interrogation
command/control command).

The Benning MCU ASCII protocol does not define a general interrogation.
The current values for the parameterized indications and measured values are always transmitted with the
current data message “protocol”.
The current data message “protocol” is interrogated by the central station for a general interrogation. All indi-
cations and measured values from the current “protocol” are forwarded once inside the SICAM A8000 central
station with the status “interrogated via a general interrogation”.
12.17.6.3 Time synchronization

Setting the date and time (time synchronization) for the Benning partner is not supported!
The Benning MCU time synchronization with the Benning MCU ASCII protocol can be released or blocked in
the Benning MCU via the serial interface.
The Benning MCU ASCII protocol defines the following command for setting the date and time:
Ztdd.mm.yy-hh:mm:ss<CR><LF>
dd …… Day (1 to 31)
mm … Month (1 to 12)
yy …… Year (00 to 99 = 2000 to 2099)
hh …. Hour (00 to 24)
mm … Minute (0 to 59)
ss ….. Second (0 to 59)

DC8-037-2, Edition 11.2020
12.17 Benning MCU

The protocol element for the Benning MCU ASCII protocol in the SICAM A8000 central station carries out a
query of the current data message “protocol” on a continuous basis with the command that has been deter-
mined for this purpose.
The current protocol can either be queried continuously (continuous cycle) or only on request.
The interrogation cycle must be parameterized for the current protocol in the central station using the param-
eter Advanced parameters | cycle time for "require last protocol".
The current protocol is typically queried every 20 seconds.
NOTE
i If the “interrogate current protocol” command is acknowledged from the substation, but the current
protocol is not transmitted n times by the substation (n = number of retries), then the data from the
current protocol is emulated as failed by the central station protocol element (NT = 1).
Additional commands to the Benning substation can be triggered in the SICAM A8000 central station by a user
program (CAEx) or by a connected control system (SCADA) for transmission with a IEC60870-5-101 single
command <TI:=45>.
NOTE
i The protocol element does not transmit any commands while protocol transmission is in progress. A half
duplex transmission medium can be used as a result.
This means that commands can be transmitted with a delay!
Spontaneous transmit mode for protocols may not be used in the Benning MCU!
Possible commands: (central station → substation)

Identifier Use
AA Interrogate the last 10 indication protocols
AB Interrogate current protocol
AL Switching over to equalization charging
DL Switching over to TRICKLE CHARGING
DR Switching over to direct power supply
EN Resetting overvoltage shutdown
LA Switching over to CHARGE
RD Resetting redundancy
SA Signal check for relay 1
SB Signal check for relay 2
SC Signal check for relay 3
SD Signal check for relay 4
SE Signal check for relay 5
SF Signal check for relay 6
SG Signal check for relay 7
SH Signal check for relay 8
SI Signal check for relay 9
SJ Signal check for relay 10
SK Signal check for relay 11
SL Signal check for relay 12

DC8-037-2, Edition 11.2020
12.17 Benning MCU
Identifier Use
SERVICE Service release via modem
TB Start battery test
TE End battery test
WI Repeat protocol that was transmitted most recently
ZT Change date and time
Commands with a line through them are not supported!
NOTE
i The commands must be enabled in the Benning MCU!
12.17.6.5 Count Value Transmission

The Benning MCU ASCII protocol does not define any special count value transmission. Count values can be
transmitted as measured values, if this is available in the Benning system.
The protocol element for the Benning MCU ASCII protocol (master station) in SICAM A8000 does not support
any functions in relation to redundancy.
12.17.8 Message Formats
The telegram structure corresponds to the definitions according to the Benning MCU ASCII protocol.
3 different telegram types are supported:
• Command message
• Data message protocol (indication/measured value message)
• Acknowledgment message
12.17.8.1 Command Message

Structure of a command message: (master station → substation)
• Identifier
• End of message: <CR> <LF>
Commands (master station → substation)

Identifier Use Response from substation
AA Interrogate the last 10 indication protocols Acknowledgment, indication/measured value
message
AB Interrogate current protocol Acknowledgment, indication/measured value
message
AL Switching over to equalization charging Acknowledgment
DL Switching over to TRICKLE CHARGING Acknowledgment
DR Switching over to direct power supply Acknowledgment
EN Resetting overvoltage shutdown Acknowledgment
LA Switching over to CHARGE Acknowledgment

DC8-037-2, Edition 11.2020
12.17 Benning MCU
Identifier Use Response from substation

RD Resetting redundancy Acknowledgment
SA Signal check for relay 1 Acknowledgment
SB Signal check for relay 2 Acknowledgment
SC Signal check for relay 3 Acknowledgment
SD Signal check for relay 4 Acknowledgment
SE Signal check for relay 5 Acknowledgment
SF Signal check for relay 6 Acknowledgment
SG Signal check for relay 7 Acknowledgment
SH Signal check for relay 8 Acknowledgment
SI Signal check for relay 9 Acknowledgment
SJ Signal check for relay 10 Acknowledgment
SK Signal check for relay 11 Acknowledgment
SL Signal check for relay 12 Acknowledgment
SERVICE Service release via modem Acknowledgment
TB Start battery test Acknowledgment
TE End battery test Acknowledgment
WI Repeat protocol that was transmitted most Acknowledgment, indication/measured value
recently message
ZT Change date and time Acknowledgment
Commands with a line through them are not supported!
NOTE
i The commands must be released in the Benning MCU!
Examples:
Example: Switching over to charge
Direction <ASCII> message <HEX> message Note
Z→V LA <CR> <LF> 4C 41 0D 0A Command “Switch over to charge”
Z←V Q <CR> <LF> 51 0D 0A Acknowledgment

Z→V TB <CR> <LF> 54 42 0D 0A Command “Start battery test”
Setting the Date and Time (Time Synchronization)

Setting the time + date (time synchronization) for the Benning partner is not supported!
The system time (internal time) of the Benning MCU can be set remotely using the ZT command.
Message format: ZTdd.mm.yy-hh:mm:ss<CR><LF>
dd …… Day (1-31)
mm … Month (1-12)
yy …… Year (00-99 = 2000-2099)
hh …. Hour (00-24)
mm …Minute (0-59)
ss …. Second (0-59)

DC8-037-2, Edition 11.2020
12.17 Benning MCU
NOTE
i The Benning MCU time synchronization with the Benning MCU ASCII protocol can be released or blocked in
the Benning MCU via the serial interface.
Setting the date and time should be carried out once the master station has started up and when the time
is changed (for example, during the daylight saving time/standard time switchover). A cyclical time
synchronization such as once a minute or once a day is not required!
Example: Change date and time

Z→V ZT19.02.14-17:23:45 <CR> 5A 54 31 39 2E 30 32 2E Format: ZTdd.mm.yy-
<LF> 31 34 2D 31 37 3A 32 33 hh:mm:ss<CR><LF>
3A 34 35 20 0D 0A
12.17.8.2 Acknowledgment Message

An acknowledgement message is only transmitted as a confirmation for safe receipt of a command.
Structure of an acknowledgment message: (master station ← substation)
• Q identifier
• End of message: <CR> <LF>
Example: Switching over to charge

Z→V LA <CR> <LF> 4C 41 0D 0A Command “Switch over to charge”
12.17.8.3 Data Message “Protocol”

All measured values and all indications are always transmitted in one data message “protocol”. The max length
of the data message depends on the hardware equipment and the number of indications and measured values
that have been parameterized by the Benning MCU.
NOTE
i A MCU 1000/2000+ transmits max. 2000 characters, a MCU 2500 can transmit up to 4000 characters. New
variants can transmit longer data message.
Structure of a data message: Substation → Master station
• The indication header

is transmitted once at the start of the message
<XON> ........ Introducing character [17 dec] or [11 hex]
...
<;> .............. Separator [59 dec] or [3B hex]
...
<202> ......... Software module identifier currently <202>
...

DC8-037-2, Edition 11.2020
12.17 Benning MCU

...
<x...xx> ...... Operating position identifier
.... 12-digit alphanumeric code for identifying the plant to be called
<CR><LF> ... Final character [10,13 dec] or [0A, 0D hex]
..
• Measured values
This block repeats for each measured value, the final character is
transmitted after the last measured value
<x...xx> ...... Measured value ID (up to 15 ASCII characters)
....
<x...xx> ...... Unit of measurement (up to 2 ASCII characters)
....
..
• Indications
This block repeats for each indication, the final character is trans-
mitted after the last indication:
<x> ............. Indication status (1 ASCII char-
[95 dec] or [5F hex]
... acter)
[32 dec] or [20 hex]
<-> = inactive indication
< > = active indication
<x...xx> ...... Indication identifier (up to 14 ASCII characters)
....
...
..
• Check digit
<xxxxx> ...... Check digit (CRC16 message protection)
..... The check digit is a decimal number (5 ASCII characters) that is
determined in the CRC16 method (DIN66219, section 4) (the
following end character is not included)
• End character
<CR><LF> ... [13,10 dec] or [0D, 0A hex]
..
<XOFF> ...... [19 dec] or [13 hex]
...
The ASCII characters in the description are represented with <xxxx>.

The D characters <> are not transmitted as ASCII characters in the process.

DC8-037-2, Edition 11.2020
12.17 Benning MCU
Notes:
• Software module identifier:

The software module identifier is not checked by the SICAM A8000 master station.
The software module identifier can be displayed in SICAM A8000 using SICAM TOOLBOX II / ST emulation
with IDH.
200 … is a MCU 2000 as per the original protocol specification (is no longer used for plants)
201 … is a MCU 2000 or MCU 1000 or MCU 2000+ with an up-to-date protocol specification (since
approx. 1999)
202 … is a MCU 2500 with an up-to-date protocol specification.
• Value format for measured values

There’s no limitation here as to how the protocol description is specified. However, the MCU transmits 1
decimal place and as many pre-decimal places as required for the number value.
Note: Only supported measured value formats are converted in the receive direction!
Supported measured value formats:
- xxxxxx.x ….. n-predecimal places; 1,n) decimal place(s)
Measured value limitation due to the delimiter that has been determined.
- hh:mm:ss … Time (for example, for ZVOD)
• Measured value DZ: (= Date + Time)

Format: DZ dd.mm.yy-hh:mm:ss
The DZ measured value is always the period when the protocol was created.
The DZ always corresponds to the current system time when querying the protocol using the AB
command.
DZ would would match the protocol generation time in every single protocol when the last 10 indication
protocols are queried.
The DZ measured value is not always available in the protocol (but it is most of the time).
The SICAM A8000 master station does not evaluate the DZ measured value in the protocol.
Data that has been changed from the protocol is forwarded with the SICAM A8000 system time when the
protocol is received.
Note: The DZ measured value is not converted in receive direction!
• ZVOD measured value: (= Duration of the battery test)

Format: ZVOD hh:mm:ss
typ. 30 minutes to max. 4 hours. Max. possible value = 18 hours.
The ZVOD measured value is not always available in the protocol - depending on the parameterization in
the Benning MCU.
Note: The ZVOD measured value can be converted to a measured value in receive direction (0 to 64800
seconds)!
• Units for measured values

The measured value units in the protocol are not evaluated by the SICAM A8000 master station.
• Pauses between protocols

When the last 10 protocols are queried, the protocols are transmitted one after the other by the Benning
MCU without a deliberate pause, but framed by <XON> and <XOFF> in each case. In practice, there is a
brief pause, as the archived protocols first need to be unpacked and copied.
• There may be < 1 ms in between as there are also higher priority interrupts.
Character timeout should be set to approx. 5 ms.
Example: Interrogate current “protocol”

DC8-037-2, Edition 11.2020
12.17 Benning MCU

Z→V AB <CR> <LF> 41 42 0D 0A Command “Interrogate current
protocol”
Z←V <XON>; 11 3B “Protocol” data message
202; 32 30 32 3B
TBGERXXXXXXX<CR><LF> …………................…………
UBBR 26.9 V<CR><LF> …
ILOATOT 0.4 A<CR><LF> …………................…………
IRECTOT 0.4 A<CR><LF> …
TBAT01 25.4 °<CR><LF> …………................…………
…
PLOAMAX 0.0 kW<CR><LF>
…………................…………
CBAT 0.0 Ah<CR><LF>
…
DZ 01.01.05-07:24:00 h
…………................…………
ZVOD 00:00:00 h<CR><LF> …
UVOD01 0.0 V<CR><LF> …………................…………
IREC13 0.4 A<CR><LF> …
_EFA;_UBBR<24.5; …………................…………
_URGERR;_NURERR; …
_DFD;_RECCHG; …………................…………
_MCUBUS;_MOD; …
_RECOFF; …………................…………
…
_UBBR>29.7;
…………................…………
_TSEFAU;
…
_REC13;
…………................…………
_MAIREC13;
…
_FANREC13<CR><LF>
…………................…………
51788<CR><LF> …
<XOFF> …………................…………
…
…………................…………
…
…………................…………
…
…………................…………
…
…………................…………
…
…………................…………
…
…………................…………
…
…………................…………
…
…………................…………
…
35 31 37 38 38 0D 0A
13

DC8-037-2, Edition 11.2020
12.17 Benning MCU
NOTE
i If the “interrogate current protocol” command is acknowledged from the substation, but the current data
message is not transmitted n times by the substation (n = number of retries), then the data from the
current data message is emulated as failed by the master station protocol element (NT = 1).
Failed Indications/Measured Values

Failed values are not transmitted in the data message or with a specific status in the Benning system,
depending on the Benning system used.
Benning How are failed values transmitted?
MCU-100
MCU-1000
MCU-2000
MCU-2500 The values are not transmitted in the data message (“protocol”) if there any communication
errors for I/O printed circuit board assemblies or for faulty printed circuit board assemblies
that have been removed
Values that have not been transmitted but have been parameterized are emulated with NT = 1 (not topical) for
the BSE!
Example 1 “OK“:
TxD: AB <CR><LF> interrogation command
RxD: Q <CR><LF> Acknowledgment
RxD: 11;202;287100100000 <CR><LF>
RxD: UBBR 47.6 V <CR><LF> ← Still available here → Process image is applicable
RxD: IRECTOT 0.4 A <CR><LF> ← Still available here → Process image is applicable
RxD: PGRA01 0.0 kW <CR><LF>
RxD: CBAT 0.0 Ah <CR><LF>
RxD: DZ 10.11.16-14:32:50 h <CR><LF>
RxD: ZVOD 00:00:00 h <CR><LF>
RxD: UVOD 0.0 V <CR><LF>
RxD: IREC02 0.1 A <CR><LF> ← Still available here → Process image is applicable
RxD: _ENCON; GRS;_URGERR;
NURERR;_CHG;_MCUBUS;_MOD;_VOD;_RECOFF;_VODERR;_BATDI-
SACT;_ERRLAD;_UBBR1<2.10;_UBBR1>2.50;_REC02; IREC02;_FANREC02 <CR><LF>
RxD: 56852 <CR><LF>
RxD: 13
Example 2 “NOK“:
TxD: AB <CR><LF> Interrogation command
RxD: Q <CR><LF>
UBBR 47.6 V <CR><LF> ← Value failed (no longer included in the Benning ASCII
message)
Values that have not been transmitted but have been para-
meterized are emulated with NT = 1 (not topical) for the
BSE!
IRECTOT 0.4 A <CR><LF> ← Value failed (no longer included in the Benning ASCII
message)
BSE!
RxD: 11;202;287100100000 <CR><LF>

DC8-037-2, Edition 11.2020
12.17 Benning MCU

RxD: DZ 10.11.16-14:36:31 h <CR><LF>
RxD: IREC02 0.1 A <CR><LF> ← Still available here → Process image is applicable
SACT;_ERRLAD;_UBBR1<2.10;_UBBR1>2.50;_REC02; MAIREC02;_FANREC02 <CR><LF>
RxD: 24227 <CR><LF>
RxD: 13
Example 3 “NOK“:
TxD: AB <CR><LF>
RxD: Q <CR><LF>
UBBR 47.6 V <CR><LF> ← Value failed (no longer included in the Benning ASCII
message)
BSE!
IRECTOT 0.4 A <CR><LF> ← Value failed (no longer included in the Benning ASCII
message)
BSE!
RxD: 11;202;287100100000 <CR><LF>
RxD: DZ 10.11.16-14:36:31 h <CR><LF>
IREC02 0.1 A <CR><LF> ← Value failed (no longer included in the Benning ASCII
message)
BSE!
SACT;_ERRLAD;_UBBR1<2.10;_UBBR1>2.50;_REC02; MAIREC02;_FANREC02 <CR><LF>
RxD: 14536 <CR><LF>
RxD: 13
12.17.8.4 Address Field (Substation or Device Address)

The Benning MCU ASCII protocol does not define an address field for a station address. Command telegrams
and acknowledgment messages are transmitted without an address.
The operation location identifier (12-digit alphanumeric code for identifying the plant to be called) must be
entered in data messages (indication/measured value protocol) as an address.
This address is checked by the protocol element in the master station. If the operating position identifier that
has been received does not match the one that has been parameterized, then the received data is not
accepted.
12.17.8.5 Message Protection

Data messages are protected by a CRC16 checksum according to checksum handling as per DIN 66219 Part 4.

DC8-037-2, Edition 11.2020
12.17 Benning MCU
Generator polynomial CRC-16

according to DIN 66219 Part 4
Generator polynomial g(x) = x16 + x12 + x5 + 1
Initial values 0000
Range The checksum is created from all characters prior to the checksum itself. 2
characters with the value “0x00” (=‘\0‘) must also be taken into account
during calculation.
Command messages, acknowledgment messages are transmitted without message protection.
12.17.9.1 Overview
Data in transmit direction is transferred by the basic system element to the protocol element in SICAM A8000-
internal IEC 60870-5-101/104 format. Data formats IEC60870-5-101/-104 ↔ Benning MCU ASCII protocol are
converted on the protocol element. The data is transmitted as per the transmission procedure of the Benning
MCU ASCII protocol.
The data in transmit direction is spontaneously transmitted and not temporarily stored in an internal process
image.
Data in receive direction is converted by the protocol element from the Benning MCU ASCII format on the
transmission line to a SICAM A8000 internal IEC 60870-5-101/104 format and transferred to the base system
element.
Converting SICAM A8000 message formats ↔ Benning MCU ASCII protocol and converting the address infor-
mation is designated as message conversion.
The address conversion for the SICAM A8000 internal IEC 60870-5-101/104 ↔ to the Benning MCU ASCII
(address and message format) is carried out using the SICAM TOOLBOX II, OPM II with the “SIP message
address conversion”, or with SICAM WEB.
Categories for SIP message address conversion
Data Direction Category

Command Transmit direction firmware /Trans_command
Binary information Receive direction firmware /Rec_indication
Measured value Receive direction firmware /Rec_measured value
The following parameters apply to all parameter categories:

Parameter
Lk_Reg Link region number
The data point is assigned to the automation unit with the selected region number.
Lk_Comp Link component number
The data point is assigned to the automation unit with the selected component
number.
Lk_BSE Link basic system element
The data point is assigned to the selected basic system element in the selected auto-
mation unit.
Lk_SSE Link supplementary system element
The data point is assigned to the selected supplementary system element in the
selected automation unit.

DC8-037-2, Edition 11.2020
12.17 Benning MCU
Parameter
Lk_DS Link destination station
The data point is assigned to the selected destination station in the selected automa-
tion unit.
Lk_Cat Link category
Lk_Prep Link prepared
• Data point prepared: signal will not be loaded into destination system
• Data point activated: signal is activated and will be loaded upon conversion into
destination system
12.17.9.2 Message Conversion in Transmit Direction (Central Station → Substation)

message conversion in transmit direction: IEC60870-5-101/104 → Benning MCU
SICAM A8000: IEC 60870-5-101/104 → Benning MCU ASCII protocol
Type ID Designation Identifier Designation
– – AB Query current protocol 352
<TI:=45> Single command AA Interrogate the last 10 indication
AB protocols
AL Query current protocol 352
DL Switching over to equalization
DR charging
EN Switching over to TRICKLE CHARGING
LA Switching over to direct power
supply
RD
Resetting overvoltage shutdown
SA
Switching over to CHARGE
SB
Resetting redundancy
SC
Signal check for relay 1
SD
SE
SF
SG
SH
SI
SJ
SK
SL
SERVICE
TB
TE
Service release via modem
WI
Start battery test
End battery test
Repeat protocol that was transmitted
most recently
352 the protocol element carries out a query of the “current protocol” in a cyclical fashion (time grid can be parameterized); the query can
also be controlled by the process command as an option in this case

DC8-037-2, Edition 11.2020
12.17 Benning MCU
SICAM A8000: IEC 60870-5-101/104 → Benning MCU ASCII protocol

– – ZT Change date and time
<TI:=100> General interrogation command AB Interrogate current protocol 353
Commands
The address and message conversion for commands in transmit direction can be parameterized using the
Parameter category:
353 the current data message “protocol” is interrogated during general interrogation; all binary information and measured values for the
received data message are forwarded to the basic system element once with the cause of transmission “interrogated due to station
interrogation”

DC8-037-2, Edition 11.2020
12.17 Benning MCU
Parameter

CASDU, IOA SICAM A8000 internal IEC608705-101/-104 message address
MCU_Command Benning MCU command qualifier (identifier)
• AB ….. Interrogate current protocol

• AL ….. Switching over to equalization charging
• DL ….. Switching over to TRICKLE CHARGING
• DR ….. Switching over to direct power supply
• EN ….. Resetting overvoltage shutdown
• LA ….. Switching over to CHARGE
• RD ….. Resetting redundancy
• SA ….. Signal check for relay 1
• SB ….. Signal check for relay 2
• SC ….. Signal check for relay 3
• SD ….. Signal check for relay 4
• SE ….. Signal check for relay 5
• SF ….. Signal check for relay 6
• SG ….. Signal check for relay 7
• SH ….. Signal check for relay 8
• SI .….. Signal check for relay 9
• SJ ….. Signal check for relay 10
• SK ….. Signal check for relay 11
• SL ….. Signal check for relay 12
• TB ….. Start battery test
• TE ….. End battery test
TI SICAM A8000 101/-104 data format

45 Single command ⇒⇓
MCU Benning MCU command

command
“Identifier”
AB Interrogate current protocol ✓
AL Switching over to equalization charging ✓
DL Switching over to TRICKLE CHARGING ✓
DR Switching over to direct power supply ✓
EN Resetting overvoltage shutdown ✓
LA Switching over to CHARGE ✓
RD Resetting redundancy ✓
SA Signal check for relay 1 ✓
SB Signal check for relay 2 ✓
SC Signal check for relay 3 ✓
SD Signal check for relay 4 ✓

DC8-037-2, Edition 11.2020
12.17 Benning MCU

command
“Identifier”
SE Signal check for relay 5 ✓
SF Signal check for relay 6 ✓
SG Signal check for relay 7 ✓
SH Signal check for relay 8 ✓
SI Signal check for relay 9 ✓
SJ Signal check for relay 10 ✓
SK Signal check for relay 11 ✓
SL Signal check for relay 12 ✓
TB Start battery test ✓
TE End battery test ✓
Message conversion
The table describes the elements of the IEC 60870-5-101/104 message during message conversion.
Message elements
TI .. Type Identification • TI 45 .. Single command
06 .. Activation Not evaluated
07 .. Confirmation of activation Not supported!
08 .. Abortion of activation Not evaluated
09 .. Confirmation of the abortion of acti- Not supported!
vation
10 .. Termination of the activation Not supported!
xx .. Other COTs Not evaluated
T .. Test Not supported!
Information
SCO
0 .. OFF [Only <TI:=45>]
1 .. ON Not evaluated
QOC S/E
0 = execute Not evaluated
1 = select Not evaluated
0 .. No additional defini- Not evaluated
tions
1 .. Short pulse duration Not evaluated
2 .. Long pulse duration Not evaluated
3 .. Persistent command Not evaluated
• Elements of the IEC60870-5-101/-104 message that are not listed are not evaluated/not supported!
• The Benning MCU ASCII message that has been received in SICAM A8000 in ST emulation can be
displayed using IDA (displaying the ASCII characters that were transmitted/received most recently).

DC8-037-2, Edition 11.2020
12.17 Benning MCU
General Interrogation Command

The message address is assigned to the spontaneous information object “general interrogation command”
automatically in transmit direction (no parameterization required for message conversion).
Parameter category:
---

100 General Interrogation Command ⇒⇓

command
“Identifier”
AB Interrogate current protocol ✓
Message conversion
Message elements
CASDU, IOA .. Message address Not evaluated; IOA=0
06 .. Activation Not evaluated
07 .. Confirmation of activation Not supported!
08 .. Abortion of activation Not evaluated
09 .. Confirmation of the abortion of acti- Not supported!
vation
10 .. Termination of the activation Not supported!
xx .. Other COTs Not supported!
T .. Test Not supported!
Information
Interrogation qualifier [Qualifier of query]
QOI <0> = not used
<1 to 19> ... reserved Not evaluated
<20> ... Station interroga- Not evaluated
tion (overall) During a general interrogation, the current protocol is interro-
gated with AB and all binary information/measured values that
have the cause of transmission “interrogated via station interrog-
ation” are forwarded to the BSE.
<21 to 36> ... Interrog- Not evaluated
ating groups 1 to 16
<37 63> ... Reserved Not evaluated
<64 to 255> ... Reserved Not evaluated
(private section)

DC8-037-2, Edition 11.2020
12.17 Benning MCU
12.17.9.3 Message Conversion in Receive Direction (Central Station ← Substation)

Message conversion in receive direction: IEC60870-5-101/104 ← Benning MCU
SICAM A8000: IEC 60870-5-101/104 Benning MCU ASCII protocol
Type ID Designation Identifier Designation
<TI:=30> Single-point information with - Indication (from “Protocol”data
CP56Time2a time tag message)
<TI:=36> Measured value, short floating point - Measured value (from “Protocol”data
number with time tag message)
Binary Information
The address and message conversion for binary information items in receive direction can be parameterized
using the SICAM TOOLBOX II, OPM II, or for engineering via SICAM WEB with the transmit detailed routing
parameters.
Parameter category:
Parameter
CASDU1 SICAM A8000 internal IEC608705-101/-104 message address
CASDU2
IOA1
IOA2
IOA3
• <TI:=30> .. single-point information with CP56Time2a time tag

operation_location_identifier Benning MCU operation location identifier:
Operation location identifier (up to 12 ASCII characters)
MCU_Adr(binary_identifier) Benning indication qualifier:
Report qualifier (up to 14 ASCII characters)
Software module identifier is not evaluated in the Benning MCU ASCII message!

30 Single-point information with CP56Time2a time tag ⇒⇓

DC8-037-2, Edition 11.2020
12.17 Benning MCU
Benning data format

Indications ✓
Message conversion
Message elements
TI .. Type identification • <TI:=30> .. single-point information with CP56Time2a time
tag
CASDU, IOA .. Message address Can be set by parameter
(Benning operation location identifier, indication identifier)
BL .. Blocked Not supported (BL = 0)
SB .. Substituted Not supported (SB = 0)
NT .. Not topical NT = 0:
Valid indication qualifier received by Benning.
NT = 1:
Emulated by the PRE if the parameterized Benning indication
identifier is not transmitted, or the partner does not transmit the
current protocol after n commands (n= number of retries).
NT = 1:
Emulated by the basic system element on failure of the protocol
element or the remote terminal unit.
IV .. Invalid Not supported (IV = 0)
03 .. Spontaneous When the information status or the quality code changes
20 .. Interrogated by station interrogation Upon receipt of a GI request
xx .. Other COTs Not supported
Information
SPI 0 .. OFF Benning indication status = "_" … inactive indication OFF
1 .. ON Benning indication status = "_" … active indication ON
Time_tag
CP56Time2a .. Date + time PRE internal time (receive time) when the indication/measured
value protocol is received.
Measured Values
The address and message conversion for measured values in receive direction can be parameterized using the
SICAM TOOLBOX II, OPM II, or for engineering via SICAM WEB with the transmit detailed routing parameters.

DC8-037-2, Edition 11.2020
12.17 Benning MCU
Parameter category:
firmware /Rec_measured value
Parameter
CASDU1 SICAM A8000 internal IEC608705-101/-104 message address
CASDU2
IOA1
IOA2
IOA3
• <TI:=36> .. Measured value, short floating-point number with time tag

CP56Time2a
operation_location_identifier Benning MCU operation location identifier:
Operation location identifier (up to 12 ASCII characters)
MCU_Addr (indication identi- Benning measured value ID:
fier) Measured value ID (up to 15 ASCII characters)
Lower limit of the range of values used in the external format (protocol-
specific). The corresponding internal value is configured at Y_0%.
Possible options: -2048 to + 2047
Upper limit of the range of values used in the external format (protocol-
specific). The corresponding internal value is configured at Y_100%.
Possible options:
<TI:=34>: -1 to +1
<TI:=35>: -32768 to +32767
<TI:=36>: no test

DC8-037-2, Edition 11.2020
12.17 Benning MCU
Parameter
Possible options:
<TI:=34>: -1 to +1
<TI:=35>: -32768 to +32767
<TI:=36>: no test
Thresh_uncond When changing the value > thres_ uncond, the received value is immedi-
ately forwarded to the BSE.
Thresh_additive When changing the value ⇐ thres_ uncond, the received value is not imme-
diately forwarded to the BSE and additive change monitoring is carried out.
Additive change monitoring:
If the summed changes (addition of changes since the last transfer, taking
signs into account as well) > Thresh_additive, the received value is passed
to the BSE.
Thresh_unit • Absolute value [value received from Benning MCU]
• %
Note: Software module identifier is not evaluated in the Benning MCU ASCII message!

36 Measured value, short floating-point number with time tag CP56Time2a ⇒⇓
Benning Data format

Measurand ✓
Value adaptation
Value adaptation is defined by the parameters X_0%, X_100%, Y_0%, Y_100%.

DC8-037-2, Edition 11.2020
12.17 Benning MCU
[BMCUT0_mv_conditioning, 1, en_US]
The adaptation is only carried out if X0 or X100 <> 0 has been parameterized.
NOTE
i • If the value adaptation (direct forwarding) that is outside the range of values for the selected
IEC60870-5-101/-104 type identifier is not activated, then OV = 1 is set.
Change monitoring
In order to avoid unnecessarily burdening the SICAM A8000 internal and further communication, the meas-
ured value is monitored for changes according to the following rules:
• The first value determined after startup is transmitted immediately
• Each change of quality descriptors IV triggers an immediate transfer, the quality descriptors OV does not
initiate a transfer

DC8-037-2, Edition 11.2020
12.17 Benning MCU

The measured value is monitored for a change in the parameterizable processing grid. 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_uncond, the new measured value
is transmitted immediately.
Otherwise, in the parameterized processing grid the deviations from the last spontaneously transmitted meas-
ured value are totalled according to the polarity sign. First when the amount of this total exceeds the parame-
terized Thresh_additive is the current measured value spontaneously transmitted.
Thresh Thresh addi- Processing
uncond tive
0 0 → Value is transmitted to the BSE in the next processing grid if there is a
0 <> 0 change
<> 0 0 → Value is not transmitted to the BSE (only if there is a status change)
<> 0 <> 0 • Change of value greater or equal than Thresh_uncond
→ Transmit the value to the BSA in the next processing grid
• Change less than Thresh_uncond
procedure.
The thresholds are to be parameterized for every measured value with the parameter Thresh_additive
and the parameter Thresh_uncond .
Message conversion
Message elements
TI .. Type Identification • TI 36 .. Measured value, short floating-point number with
time tag CP56Time2a
(Benning operation location identifier, measured value ID)
BL .. Blocked Not supported (BL = 0)
SB .. Substituted Not supported (SB = 0)
NT .. Not topical NT = 0:
Valid measured value ID received from Benning.
NT = 1:
Emulated by the PRE if the parameterized Benning measured
value ID is not transmitted, or the partner does not transmit the
current protocol after n commands (n= number of retries).
NT = 1:
Emulated by the basic system element on failure of the protocol
element or the remote terminal unit
IV .. Invalid IV = 0
OV .. Overflow OV = 1:
• Benning MCU value outside the range of the selected type

identifier
• Benning MCU value less than X_0% or greater than X_100%

DC8-037-2, Edition 11.2020
12.17 Benning MCU
Message elements
03 .. Spontaneous Alteration of the measured value depending on the thresholds or
20 .. Interrogated by station interrogation Upon receipt of a GI request
xx .. Other COTs Not supported
Information
Value.. Value = IEEE STD 754 = short floating-point number
S ..Sign = Converted Benning measured value in the following format: n
pre-decimal places,1 decimal place
The unit of the Benning measured value is not evaluated.
Time_tag
CP56Time2a .. Date + time PRE internal time (receive time)
12.17.10Protocol Element Control and Return Information
This function is used for the user-specific influencing of the functions of the protocol elements. It contains two
parts that are independent of one another:

• Applicational control of station interrogation

• Using statuses of certain status lines as process information
• The obtaining of station interrogation information

DC8-037-2, Edition 11.2020
12.17 Benning MCU
Block diagram
[dw_protocol_control, 1, en_US]

The protocol element for the Benning MCU ASCII protocol (master station) in SICAM A8000 does not support
any functions in relation to controlling the protocol element with the protocol element control messages.

information in monitoring direction and thereby enables protocol element statuses to be
• Status of the status lines
• Protocol-specific feedback (dependent on the protocol element used)

The messages with process information are assigned to the feedback on the base system element
using the system parameters for the SICAM A8000 system data protocol element return informa-
tion.
The source from which the parameterized return information should be generated can be set using the param-
eters Supplementary system element and Station number.
Messages for the protocol element return information are transmitted to the basic system element from the
protocol element spontaneously if there is a change, or as a response to a general interrogation command.
Possible return information from the substation:

DC8-037-2, Edition 11.2020
12.17 Benning MCU

Station
Status DTR 255 1 = status line active
always transmitted!
Status DSR 255 1 = status line active
always transmitted!
Station failure 0 1 = Station failed
Is not currently supported by the basic system
element!
Legend:
0 to 99 ..... of the selected protocol element
255 .......... Station number not used!
12.17.11ASCII Table (MS-DOS Code Page 437)
The Benning MCU ASCII protocol uses the ASCII table according to MS-DOS code page 437 for representing the
ASCII characters, and includes the following characters (the number underneath symbol is the Unicode value
written as a hexadecimal):

DC8-037-2, Edition 11.2020
12.17 Benning MCU

DC8-037-2, Edition 11.2020
12.18 AGP (Power Distributor Branch Specific Test Equipment)
The AGP protocol is a serial transmission protocol for coupling the AGP (Power distributor branch specific test
equipment). The AGP is only connected via fiber optic cables. A media converter RS-232 ↔ is also required for
this.
The following protocol firmware is available in SICAM A8000 for connecting the AGP:
AGPMT0 CP-8000 AGP protocol master (end-end protocol for coupling the
CP-802x “Power distributor branch specific test equipment”)
Power distributor branch specific test equipment

The trend towards compact, factory-ready, type-tested indoor switchgear places new demands on the line test
to be integrated. If the test continues to be carried out conventionally, the advantages of compact concepts
are quickly exhausted. The traditional primary devices (switching element, test rail and in particular the test
resistor with its heat development) do not fit into the desired types of switchboards.
The AGP uses a resource-saving, low-loss method, which can be used in branch-connected compact switch
cells. Discriminating faulty networks provides safe results even on large networks with high cable counts.
According to the state of the art, the device is maintenance-free.
The AGP requires no external power supply. By means of AGP, an energy pulse is controlled synchronously
from the covered operating rail to the mains voltage to the trolley branch to be tested. The resulting current
profile is evaluated by the integrated control unit.
The test request, the test result and the status of the test device are serially exchanged via a fiber optic
connection between the control unit (under high voltage) and an associated field device.
12.18.2 Functions
• Serial communication protocol based on IEC 60870-5-2 for coupling the AGP
(Power distributor branch specific test equipment)
• Unbalanced transmission:
– CP-8000/CP-802x = Master
– AGP = Slave
– Point-to-point configuration (Master+ 1 Slave)
– max. number of AGP devices per interface = 1
• Physical interface on the CP-8000/CP-802x

– RS-232 (external media converter “RS-232 ↔ optically” required)
• Physical interface at the AGP

– optical interface (plastic fiber optic with ST plug)
• Baud rates
– 38400 Bit/s

DC8-037-2, Edition 11.2020
• Bit transmission layer

– IEC 60870-5-2 Message frame according to IEC 60870-5-1/FT1.2
– Byte Frame: 8E1
– Message protection: d=4
– Checksum (8 Bit) + Parity bits + transmission rules
• Data acquisition by polling (state messages, measured values)

– upon request, if the test conditions are met
• Indications
– Suppression of intermediate and faulty position for double-point information
– Answering of the general interrogation from the process image of the protocol firmware
– spontaneous, if the test conditions are met
– Emulation of ACTCON for commands/setpoint values according IEC 60870-5-101/104
• IEC60870-5-101/-104 data formats in transmit direction (command/control direction)

– <TI=34> ... measured value, normalized value with time tag CP56Time2a
– <TI=35> ... Measured value, scaled value with time tag CP56Time2a
– <TI=36> ... Measured value, floating point number with time tag CP56Time2a
– <TI=45> ... Single command
– <TI=48> ... Setpoint command, normalized value
– <TI=49> ... Setpoint command, scaled value
– <TI=50> ... Setpoint command, short floating point number
• IEC60870-5-101/-104 data formats in receive direction (signaling/monitoring direction)

– <TI=30> ... Single-point information with CP56Time2a time tag
– <TI=31> ... Double-point information with time tag CP56Time2a
– <TI=34> ... measured value, normalized value with time tag CP56Time2a
– <TI=35> ... Measured value, scaled value with time tag CP56Time2a
– <TI=36> ... Measured value, floating point number with time tag CP56Time2a
• Web Server
– Log internal diagnostic information / state information can be viewed via PRE-specific web pages.
Restrictions
• Emulations of ACTTERM for setpoint values according to IEC 60870-5-101/104 are not supported.
• Emulations of ACTCON/ACTTERM for general interrogation according to IEC 60870-5-101/104 are not
supported.
• “Select-Before-Operate” for commands/setpoint values is not supported.
• Control location, Check control location for commands and setpoint values are not supported

DC8-037-2, Edition 11.2020
ment.

optional DTE
Unbalanced interchange circuit (V.24/V.28) X2 → Media RXD, TXD, CTS 354, GND
RS-232 asynchronous converter
(RS-232/optical)
UN1373BiS
Unbalanced interchange circuit (V.24/V.28) X6 → Media RXD, TXD, CTS, GND
RS-232 asynchronous 355 converter
(RS-232/optical)
UN1373BiS
Own Station AGP Master" (central station)

SICAM A8000 Series CP-8000/CPC80 AGPMT0 max. 1 AGP device as
CP-802x/CPC80 remote station
Remote Station AGP (Substation)

Siemens AGP – –
12.18.5 Communication according to AGP
For the data transmission from/to AGP a serial transmission protocol is used.
Data transfer between the CP-8000/CP-802x and the AGP is controlled exclusively by the protocol firmware
AGPMI0 (= AGP master). The AGP replies only to queries by the master. Data from AGP → master can only be
transmitted as a reply to a request.
The data transmission takes place exclusively with the baud rate 38400 Bit/s.
To connect the AGP, an optical connection with plastic FO is required (idle state = light ON).
The CP-8000/CP-802x requires a media converter (RS-2 ↔ optical) and an adapter.
On the AGP side, the media converter with ST connection is required (included).

355 only CP-8022 (operation mode switchable via parameter)

DC8-037-2, Edition 11.2020
Schematic configuration - Example: AGP to CP-8021 (X2)
[AGPMT0_Configuration_CP-8021, 1, en_US]
Wiring for connection CP-802x (X2) ↔ UN1373Bis
[AGP_Adapter_RJ45_DSUB9_CP-802x, 1, en_US]
NOTE
i With a serial connection via CP-8000/CP-802x Interface X2 a bridge between CTS and GND is required, as
far as the interface shall also be used for the connection with the engineering PC. By means of a special
parameter you can define that the interface is not used for engineering ( [BSE] System settings |
Serial interface | Serial engineering interface = disabled ) . Thus no connection

DC8-037-2, Edition 11.2020
Recommended D-Sub/RJ45 Adapter RS Pro Series HDA D-Sub-Adapter for Sub-D terminal block, 9-pole (Order
information see A.8 Cables and Plugs). The adapter RS Pro HDA9-SMJ8-M-K provides a wired RJ45 socket and
an unwired D-sub plug (male).
Wiring of the RJ45 socket
Pin Wire color

1 black
2 yellow
3 orange
4 red
5 green
6 browne
7 grey
8 blue
Shield black
NOTE
i There are other similar converters on the market - the color of the wires can be different! (Check wire color
and pin assignment!).
Pin assignment RS-232 interface on D-Sub/RJ45 Adapter
Pin RS-232 Signal Meaning D-Sub9 plug (female)

1 DCD (I) Receive level
2 RXD (I) Receive data
3 TXD (O) Transmit data
4 DTR (O) DEE ready
5 GND Signal ground
6 n.c.
7 RTS (O) Request to send
8 CTS (I) Clear to send
9 n.c.

DC8-037-2, Edition 11.2020
Pin assignment RS-232 interface on media converter UN1373Bis
Pin RS-232 Signal Meaning D-Sub9 socket (female) UN1373Bis

(DÜE-assignment) 356
1 DCD (O)
2 RXD (O) Receive data
3 TXD (I) Transmit data
4 DTR (I)
5 GND Signal ground
6 DSR (O)
7 RTS (I)
8 CTS (O)
9 n.c.
Wiring at the 9-pole D-sub plug:

The assignment of the pins at the D-sub plug (backside view of plug) can be made according to wiring
diagram.
[dw_9-pole_DSUB_soldering, 1, en_US]
356 Front view of plug

DC8-037-2, Edition 11.2020
Necessary accessories
Meaning Order number

UN1373Bis (Media converter optical/RS-232) To order at:
AGP coupling plug for connection to AGP Gateway Siemens Walter-
including license key for operating the firmware with shausen
the AGP.
Fiber optic connector for V.24 data transmission over
Order designation:
shorter distances with a 1000μ PMMA fiber for IBM
UN1373Bis
PC.
Power supply from the data circuit.
Current consumption: approx. 5 mA
Data rate: approx. 40 kBaud
Electric connection: D-sub connector, 9-pin, socket
ON)
Wavelength: 600 nm
Launched power: 15μW (-18dBm) (UTx0 = 10 V)
Sensitivity 0,2 μW (-37 dBm)
Optic budget: 16 dB(+ 3 dB system reserve)
Typical range: 60m
optical connection: ST-plug
optical signal layer: inversion (idle state: light ON)
Housing: plastic, metalized
operating temperature 0 to +65 °C
D-Sub/RJ45 Adapter (male) http://at.rson-
HDA9-PMJ8-M-K line.com/web/p/
Order nr. 382-2689 products/3822689/
Plastic FO with ST-connector

Type: I-V2Y(ZN)11Y2P980/1000 6.1 mm
AGP “Power distributor branch specific test equip- To order at:

ment” Siemens Walter-
shausen
Order designation:
AGP test cylinder
AGP License
The AGP license is included with the UN1373Bis
(Media converter optical/RS-232) from Siemens
Waltershausen.

DC8-037-2, Edition 11.2020
12.18.5.1 Data transmission from/to AGP
Test sequence (without measured value query current integral)

If the test conditions are met (circuit breaker is switched off and voltage from the busbar is present), the test
(without MW query) can be started by means of a command message. After checking the AGP, the detected
AGP status messages are transmitted.
AGP state messages:
• Result check OK
• Result check NOK
• Fault: Temperature too high
• Fault: Voltage difference too low
• Fault: Timeout negative half wave
• Fault: no zero crossing of the voltage
• Fault: Voltage integral too small
• Fault: Effective value of the voltage too high
• Fault: Primary voltage not within the permitted range
• Failure: Feedback signal not active
• Failure: Feedback signal during test
• Failure: no feedback signal when switched on
• Failure: Feedback signal not ready
• Failure: Fault current sensor
• Failure: Fault temperature sensor
• Aggregated fault: Fault
• Aggregated fault: Failure
• Check running
Test sequence (with measured value query current integral)

This corresponds to the previous test procedure. Additionally only the calculated current integral as a meas-
ured value is queried and transmitted after the transmission of the test result.
Status request
In this case, no check is carried out, but only the current AGP status messages are queried and transmitted.
General Rules
After a test has been started, it must wait at least 3 seconds until a new test can be carried out.
12.18.5.2 Function for the Support of Redundant Communication Routes
This function is currently not supported!

DC8-037-2, Edition 11.2020
12.18.6 Parameter and Setting

[PRE] Common settings
Interface Selection of the communication X1
interface X2
X3
X6 357
Default setting = not used
Baud Rate The AGP device supports only baud Permitted range = 38400
rate 38400 Bit/s Standard setting = 38400
Transmission facility Most of the time settings are fixed freely definable
and cannot be changed for the Modem for "4-wire transmission
predefined transmission facilities. line" (SAT-VFM,-WT,-WTK,-WTK-
Connection of the transmission S,CE-0700)
facilities as described (additional Modem for "2-wire transmission
adapters / cables are sometimes line" (SAT-VFM,-WT,-WTK,-WTK-
required) S,CE-0700)
optical
Direct connection (RS-485)
[PRE] Common settings | Byte frame
Data bits Number of data bits 5 Bit
6 Bit
7 Bit
8 Bit
Parity Selection of the Parity Bit no Parity
even Parity
odd Parity
Stop bits Number of Stop Bits 1 Bit [1] 1.5 Bit [2] 2 Bi
Common settings | Transmission facility
Asynchronous / Isochronous Asynchronous (V.24/V.28, 16 time Asynchronous “V.24/V.28“ (16
bit clock) or Isochronous (X.24/ times bit clock)
X.27 1 time bit clock) Isochronous “X.24/X.27“ (1 times
bit clock)
Bit timing (only with Bit timing: (only with isochronous) external (bit clock from RXC input)
isochronous) either externally (from the RXC internal (bit clock at TXC output)
input) or internally (at the TXC
output)
DCD-evaluation Evaluation of the DCD input. DCD disabled
can be used for telegram synchro- enabled
nization in the receive direction.
Continuous level moni- Continuous level monitoring time Float [####.#] 0.1 to 6553.5 [s] 0
toring time (tcl) (tcl) [s]
Electrical Interface RS232 (V.24/V.28)
RS422 (V.11)
RS485 (V.11)
Run out time "time base" Parameterized times in bit depend bit
(tn) on the set baud rate! ms
357 only CP-8022

DC8-037-2, Edition 11.2020

Run out time (tn) After the message transmission has Integer [#####]
ended the transmit signal level 0 to 32767 [ms/Bit]
(RTS) is first switched off after
expiry of the run-out time.
Pause time "time base" Parameterized times in bit depend bit
(tp) on the set baud rate! ms
Pause time (tp) Before sending a message, the set Integer [#####]
pause time is observed before 0 to 32767 [ms/Bit]
switching on the transmission level
(RTS).
Bounce suppression time The state of the DCD status line is Integer [#####]
(tbounce) evaluated after the bounce 0 to 65535 [ms]
suppression time (tprell).
Transmission delay at Another message transmission is Float [####.#]
level (tcldly) carried out at a permanent level at 0.1 to 6553.5 [s]
the latest after the transmission 0 [s]
delay has expired.
Blocking time "Time base" Parameterized times in bit depend bit
(tdis) on the set baud rate! ms
Disable time (tdis) Blocking time (Disable time) after Integer [#####]
reception of a message Note: To 0 to 32767 [ms/Bit]
suppress incorrect characters
during carrier switching.
Stability monitoring time Stability monitoring time (tstab) Integer [#####] 0 to 65535 [ms]
(tstab) The new DCD state is only used for
message synchronization after the
stability monitoring time has
expired.
Set-up time "time base" Parameterized times in bit depend bit
(tv) on the set baud rate! ms
Set-up time (tv) After switching on the transmission Integer [#####]
level (RTS), the message transmis- 0 to 32767 [ms/Bit]
sion is started after the set-up time.
At tv = 0 there is no carrier
switching (RTS = OFF)!
[PRE] Redundancy
Listening mode (failure Failure monitoring time in moni- Float [####.]
monitoring time) toring mode (0 = no monitoring) 0 to 60000 [s]
Operation if passive Behavior in redundancy state Transmitter "tristate", listening
PASSIVE Normal operation: mode
Behavior as for status = ACTIVE Transmitter "active", listening mode
standby: No answer from the PRE Transmitter "active", normal mode
Delay passive => active Delay time when switching from Integer [####]
PASSIVE => ACTIVE (0 = no delay) 0 to 2000 [s]
[PRE] message repetitions
Retries for data message The number of maximum message Integer [###]
SEND/CONFIRM (station repetitions to be performed. 0 to 255
selective)
Retries for data messages The number of maximum message Integer [###]
SEND/NO REPLY (broadcast) repetitions to be performed. 0 to 255

DC8-037-2, Edition 11.2020

Retries for INIT-messages The number of maximum message Integer [###]
SEND/CONFIRM (station repetitions to be performed. 0 to 255
selective)
[PRE] Advanced parameters
Number of dummy bytes Used to enable the controller of the Integer [##]
before telegram AGP from standby. 1 to 12
Default value voltage This value is used as the default Integer [###]
range value and can be changed with a 0 to 255
setpoint value (voltage range).
Enable 1-out-of-n command If 1-out-of-n monitoring is acti- no
handling vated, new commands or setpoint yes
values are blocked as long as a
command or setpoint value is still
active. This applies globally to all
connected stations.
Enable ACTCON no
yes
License key 16 characters with the value 0 to 9 String 16 characters
and A to F are allowed
Station number Integer [###]
0 to 99
255
Advanced parameters | binary informations
Intermediate state Double-point informations received Integer [##]
suppression time by the AGP device with inter- 0 to 60 [s]
mediate position will only be
forwarded after the suppression
time for intermediate position has
expired. If a valid status of the
double-point information is
received within the suppression
time for intermediate position,
then the suppression time for inter-
mediate position is aborted and
only the valid state of the double-
point information is forwarded.
faulty state suppression Double-point informations received Integer [##]
time by the AGP device with faulty posi- 0 to 60 [s]
tion will only be forwarded after
the suppression time for faulty
state has expired. If a valid status of
the double-point information is
received within the suppression
time for faulty state, then the
suppression time for faulty state is
aborted and only the valid state of
the double-point information is
forwarded.

DC8-037-2, Edition 11.2020

[PRE] Advanced parameters | Software test points
... The software test points may only no
be used under the guidance of yes
be turned off.
[PRE] Advanced parameters | Web server
HTTP Webserver A wide range of diagnostic infor- disabled
mation can be conveniently read enabled
out using a web browser using the
HTTP web server.
Advanced parameters | monitoring time
Idle monitoring time After transmission disturbances or Integer [#####]
message interruption the idle state 0 to 32767 [ms/Bit]
is monitored. After expiry of the
monitoring time the receiver is
resynchronized. Faster resynchroni-
zation can be achieved by using the
DCD input.
Idle monitoring time "time Parameterized times in bit depend bit
base" on the set baud rate! ms
Expected_ack_time_corr_fac The expected acknowledgment Float [###.##]
tor time is determined automatically. 0 to 655.35 s
Signal propagation delays and
further delay times must be taken
into account in the correction
factor for the expected acknowl-
edgment time.
Timeout Confirmation If an "activation / deactivation" Integer [###]
(command, setpoint value) is sent 0 to 255 [s]
to the remote station, a "confirma-
tion" is expected within this time. If
the timeout expires, the "activa-
tion / deactivation" is confirmed
negatively.
Timeout Termination - This timeout is started when a Integer [###]
short command (activation) with feed- 0 to 255 [s]
back is sent to the remote station.
If the timeout expires (= no return
information), a negative "termina-
tion" is forwarded.
Timeout Termination - long This timeout is started when a Integer [###]
command (activation) with return 0 to 255 [s]
information is sent to the remote
station. If the timeout expires (= no
return information), a negative
"termination" is forwarded.

DC8-037-2, Edition 11.2020

Character Monitoring Time Message gap monitoring Maximum Integer [#####]
pause between successive bytes of 0 to 32767 [ms/Bit]
a message Idle monitoring time is
started after detection of message
interruption.
Charactger monitoring time Parameterized times in bit depend bit
"time base" on the set baud rate! ms
NOTE
i On the basic system element in the topology for AGPMT0 you have to enter "multi-point traffic master with
station# 1".
IEC 60870-5-101/104 ↔ AGP is performed by the protocol element. The transmission of the data to the AGP is
controlled by the protocol element.
Data in receive direction will be read by the protocol element from the external AGP device after check or
status request, then converted by the protocol element from the AGP data format → SICAM A8000 internal
IEC 60870-5-101/104 format and transferred to the basic system element (no 101/104 blocking).
The conversion of the SICAM A8000 internal IEC 60870-5-101/104 message format ↔ AGP data format and
the conversion of the address information are called message conversion.
The parameterization of the conversion from IEC 60870-5-101/104 ↔ AGP (address and message format) is to
be done with SICAM Device Manager with function Signals or SICAM TOOLBOX II / OPM using "SIP Message
Address Conversion".
Supported processing types for message conversion
Data Direction Processing type AGPMI0

Binary information Receive direction firmware /Rec_binary_information ✓
Measured values Receive direction firmware/Rec_measured_value ✓
Measured values Transmit direction firmware /Trans_value ✓
Setpoint values
12.18.7.1 Message Conversion in Transmit Direction (Master → Slave)

Message Conversion in Transmit Direction IEC 60870-5-101/104 → AGP
SICAM A8000: IEC 60870-5-101/104 → AGP
TI Designation Data format
<TI:=34> measured value, normalized value Setpoint value voltage range
<TI:=35> Measured value, scaled value with Setpoint value voltage range
time tag CP56Time2a
<TI:=36> Measured value, short floating point Setpoint value voltage range
<TI:=45> Single command Start check with/without measured value query,
status request
<TI:=48> Setpoint command, normalized value Setpoint value voltage range

DC8-037-2, Edition 11.2020
SICAM A8000: IEC 60870-5-101/104 → AGP

<TI:=49> Setpoint command, scaled value Setpoint value voltage range
<TI:=50> Setpoint command, short floating Setpoint value voltage range
point number
<TI:=100> (General) Interrogation command 358
Commands
Parameter Category:
Parameters

AGP_Data type AGP Function:
• Start check (without MW query)

• Start check (with MW query)
• AGP status request
ACTCON/ACTTERM
If the simulation ACTCON/ACTTERM with the parameter [PRE] AGP | Communication functions |
Command transmission | Command concept to third party connection | Simulation
ACTCON/ACTTERM is released, the transfer of ACTCON takes place depending on the 1 out of n check. If the
AGP message Check is running appears, the status ACTTERM is formed based on this message (positive
for the message status = 1, negative after 5 seconds). If this message does not exist, the ACTTERM is gener-
ated positively immediately after ACTCON.
Message Conversion
358 The GA data - in response to a general interrogation command - are transmitted by protocol element from the PRE internal process
image to the BSE and redistributed by the BSE.

DC8-037-2, Edition 11.2020

TI .. Type Identification TI 45 .. Single command
06 .. activation is evaluated (only “Activation” allowed)
xx .. other COTs not accepted (only “Activation” allowed)
Information
SCO/DCO/RCO
1 .. ON evaluated
QOC S/E
0 .. no additional defini- evaluated
tions
1 .. short pulse duration evaluated
2 .. long pulse duration evaluated

transmit direction is to be done with SICAM TOOLBOX II, OPM II or with the parameters for transmit detail
routing when using SICAM WEB for engineering.
Parameter Category:

DC8-037-2, Edition 11.2020
Parameters

CP56Time2a
• <TI:=48> .. Setpoint command, normalized value
AGP_Data format AGP Function:
• Setpoint value voltage range

Y_0%, Y_100%
• <TI:=34.48> .. X_0% and X_100% must not be greater or less than ± 1.
• <TI:=35.49> .. X_0% and X_100% must not be less than -32768 or greater
than +32767.
• Value adjustment inactive at Y_0% and Y_100% = 0
• Y_0% = 0, Y_100% = 250
ACTCON/ACTTERM
If the simulation ACTCON/ACTTERM with the parameter [PRE] AGP | Communication functions |
Command transmission | Command concept to third party connection | Simulation
ACTCON/ACTTERM is released, the transfer of ACTCON takes place for setpoint values depending on the 1 out
of n check. ACTTERM is not generated for setpoint values.
Value Adaption:

DC8-037-2, Edition 11.2020
• X100 = AGP value value range 0 to 255 (X100% = 255)
• Y100 = SICAM A8000 value

The adaption is only performed if Y_0% or Y_100% <> "0" is parameterized.
NOTE
i • If the raw value of the SICAM A8000 raw value is less than Y_0% or greater than Y_100% when the
value adjustment is on, no conversion is carried out and the error message Format conversion
error in send direction is set. The last valid value is retained.
• If adaption is not activated (= direct transfer) and the SICAM A8000 raw value is outside the value
range of the selected AGP data format, then no message conversion is done and the error message
Error of format conversion in transmit direction is set. The last valid value is
retained.
• The value adjustment for the voltage range must be for Y_0% = 0 and Y_100% = 250.
Message Conversion

DC8-037-2, Edition 11.2020

CP56Time2a
CP56Time2a
• < TI:=48> .. Set point command, normalized value
NT .. not topical not evaluated
IV .. invalid not evaluated
06 .. activation is evaluated (only "activation" allowed)
[only <TI:=48, 49, 50>]
Information
• scaled value
QOS S/E [only <TI:=48, 49, 50>]
0 = execute Is checked for "execute"
Time tag
12.18.7.2 Message Conversion in Receive Direction (Master ← Slave)
Message Conversion in Receive Direction IEC 60870-5-101/104 ← AGP
SICAM A8000: IEC 60870-5-101/104 ← AGP

TI Designation Data format
<TI:=30> Single-point information State messages (result check, failure)
<TI:=31> Double-point information State messages (result check, failure)
<TI:=34> Measured value, normalized value Calculated current integral value

DC8-037-2, Edition 11.2020
SICAM A8000: IEC 60870-5-101/104 ← AGP

<TI:=35> Measured value, scaled value Calculated current integral value
<TI:=36> Measured value, short floating point Calculated current integral value
number
Binary information
be done with SICAM TOOLBOX II, OPM II or with the parameters for transmit detail routing when using SICAM
Parameter Category:
Parameters


DC8-037-2, Edition 11.2020
Parameters
AGP_Data type AGP-State message:
• Result check OK
• Fault: Temperature too high
• Fault: Primary voltage not within the permitted range
• Check running
When the status is queried, the status messages result check OK and
result check NOK are not transmitted.
Data type Informa- Message conversion:
tion
• Single point information inverted <TI:=30>
• Double-point information state OFF <TI:=31>
• Double-point information state ON <TI:=31>
Conver- Message conversion to IEC 60870-5-101/104:
sion_binary_infor-
mation • Single-point information
• Transient information transfer only ON
• Transient information emulate OFF
• Double-point information with DIFF/STÖR suppression
• Double-point information without DIFF/STÖR suppression

DC8-037-2, Edition 11.2020
Supported data formats (AGP state messages)
AGP Function AGP State message IEC 60870-5-101/104

code Data format (TI)
• Result check OK 30, 31
• Fault: Temperature too high 30
• Fault: Primary voltage not within the permitted
range
• Check running
If desired, selected status information from the AGP device (e.g., "result check") may be forwarded by the
protocol element as a double message. For this, two images with the same CASDU and IOA address must be
created in the message conversion in the receive direction for each double-point information.
The 1st image of the double-point information is assigned in the field Data type Information to the
value double-point information state OFF (TI 31). The 2nd image of the double-point information is assigned
in the field Data type Information to the value double-point information state ON (TI 31).

The forwarding of a double-point information from PRE → BSE with intermediate state (information is not
“ON” and not “OFF”) or faulty state (information is “ON” and “OFF”) will be suppressed for a parameterizable
time.
For the suppression of the intermediate position, a intermediate position suppression time can be set for all
double-point information with parameter ([PRE] AGP | Communication functions | Binary
informations | Intermediate position suppression time).

DC8-037-2, Edition 11.2020
For the suppression of the faulty position, a suppression time for faulty state can be set for all double-point
information with parameter ([PRE] AGP | Communication functions | Binary informations |
suppression time for faulty state).
Message Conversion
tag
CP56Time2a
03 .. spontaneous • upon change of information state
• Transient informations (if these are set by the AGP) are
always transmitted with cause of transmission = 3 (= spon-
taneous).

DC8-037-2, Edition 11.2020

• A GI request (station interrogation/general interrogation) is

always answered by the protocol element itself from the
PRE internal process image.
Information
1 .. ON supported
intermediate state
1 .. OFF supported
2 .. ON supported
Time tag
CP56Time2a .. Date + Time PRE internal time (receive time) or, in the case of general inter-
rogation, the internal time at which the GA data is emulated
from the protocol element from the PRE internal process image.
Measured values
The parameterization of the address and message conversion for measured values in receive direction is to be
Parameter Category:
firmware/Rec_measured_value

DC8-037-2, Edition 11.2020
Parameters

CP56Time2a
AGP_Data type AGP measured value:
• Current integral value

Y_0%, Y_100%
• <TI:=34> .. Y_0% and Y_100% must not be greater or less than ± 1.
• <TI:=35> .. Y_0% and Y_100% must not be less than -32768 or greater than
+32767.
• Value adoption inactive at X_0% and X_100% = 0
Supported data formats (AGP measured values)
AGP Function AGP value IEC 60870-5-101/104

code Data format (TI)
Current integral value 34, 35, 36
Value Adaption:

DC8-037-2, Edition 11.2020
The value adaption is only performed if X_0% or X_100% <> "0" is parameterized.
AGP value value range: 0 to 255 (X_100% = 255)
NOTE
i If the AGP value is outside the value range of the selected IEC 60870-5-101/104 type identifier when the
value adoption (= direct transfer) is not activated, then OV = 1 is set.
Message Conversion
CP56Time2a
CP56Time2a

DC8-037-2, Edition 11.2020

• AGP value outside the range of the selected type identifica-

tion
• AGP value less than X_0% or greater X_100%

03 .. spontaneous The AGP value is always passed after every check with measured
value query.
• A GI request (station interrogation/general interrogation) is

always answered by the protocol element itself from the
PRE internal process image.
Information
• scaled value
Time tag
CP56Time2a .. Date + Time PRE internal time (receive time) or, in the case of general inter-
rogation, the internal time at which the GA data is emulated
from the protocol element from the PRE internal process image.
12.18.8 Web Server
Protocol-internal statistics and diagnostic information can be read out with a web browser. The web server is
part of basic system element – the PRE specific web pages will be provided by protocol element.
System Firmware Protocol function PRE specific Web
Pages
CP-8000 AGPMT0 AGP protocol master for coupling the Power ✓
CP-802x distributor branch specific test equipment

With the SICAM Device Manager, the PRE-specific web pages can be called up directly from the Device
Manager with the links under "Protocol Details".

DC8-037-2, Edition 11.2020
With SICAM TOOLBOX II or a web browser, the PRE-specific web pages can be selected via the IP address of the
target system.
CPU PRE Example
M-CPU 0 to 7 https://172.16.0.3/pre0
https://172.16.0.3/pre7
or
https://172.16.0.3/mpre0
https://172.16.0.3/mpre7
C-CPU0 0 to 3 https://172.16.0.3/c0pre0
NOTE
access by the user with the parameter [PRE] HTTP web server | HTTP web server.

PRE specific web page for AGPMT0
• Overview X
– Connections X
– Routing Transmit X
– Routing Receive X
• Developer Information
– Freespace X
– Dataflow Test X
– Diagnosis (IDR) X
– Diagnosis (IDH) X
– Diagnosis (IDE) X
– Diagnosis (IDZ) X

DC8-037-2, Edition 11.2020
NOTE
12.18.8.2 Overview

Field Note
Protocol Protocol function
Physical Interface Used COM interface
• Firmware active
• Ready
With web page Connections detailed information about the status of the connection to each connected AGP-
device will be displayed.

DC8-037-2, Edition 11.2020
Field Note
Station number 1 (SICAM A8000 internal station number of connection to
AGP)
Status State of the connection to AGP:
• OK
• NOK
Additional info extra information
Start status request

Start status request sends a status query to the AGP device. The result of the last check procedure or status
request is displayed under Last result of check procedure or status request.
Last Result of Check Procedure or Status Request

Time and data of the last check procedure or status request is displayed under Last result of check procedure
or status request.
Field Note
Start time Start time of the last test or status query
End time End time of the last check or status query
Type Type of last communication sequence with AGP
AGP data type AGP Data type of the last check or status request
Status AGP Data state of the last check or status request

DC8-037-2, Edition 11.2020
With web page Routing Transmit the information of the parameterized data points in the send direction for
the connected AGP device are displayed.
Field Note
Count Number of parameterized data points in transmit direction
Count transmit commands Number of incorrectly parameterized data points for
"commands" in the transmit direction
Count transmit values Number of incorrectly parameterized data points for "setpoint
values" in the transmit direction
Count error Number of faulty parameterized data points in transmit direc-
tion
Error Error number
• ERR = 0 ....... no error

• ERR = 1 ....... SICAM type identification (TI) invalid
• ERR = 2 ....... SICAM sub adress invalid
• ERR = 3 ....... detailed routing type invalid
• ERR = 5 ....... SICAM type identification (TI) not supported
• ERR = 6 ....... not supported type ID for this object type
• ERR = 7 ....... AGP function code invalid
• ERR = 15 ...... SICAM address is used twice
• ERR = 16 ...... AGP address is used twice
• ERR = 17 ...... parameters of adaptation invalid
• ERR = 18 ...... threshold used but no linear adaption
• ERR = 23....... link address invalid or not used
• ERR = 100 ..... capsule no. for measured value wrong or
too large
• ERR = 101 ..... X0 and X100 are equal of linear adaption
• ERR = 102 ..... X100 is less than X0 of linear adaption
• ERR = 103 ..... Y0 and Y100 are equal of linear adaption

DC8-037-2, Edition 11.2020
Field Note
TI IEC 60870-5-101/104 Type identification (A8000 internal)
CASDU1, CASDU2 A8000 internal IEC 60870-5-101/104 Address of the data
IOA1, IOA2, IOA3 point
Routing type Detailed routing type for this data point:
• command
• setpoint value
Station no. Station number of the AGP device
Data type Used AGP data type for this data point
Last time sent Time of the last transmission for this data point BSE → PRE
Last COT sent Last transmitted cause of transmission (COT) for this data point
from BSE → PRE
Last dp qual sent Last sent quality descriptor for this data point from the BSE →
PRE
Last value sent Last sent value for this data point from the BSE → PRE
Routing Transmit (Filter not used)

All parameterized data points in transmission direction are displayed.
Incorrect parameterized data points are marked "red".
Routing Transmit - with text filter


DC8-037-2, Edition 11.2020

All faulty parameterized data points in transmit direction are displayed.
With web page Routing Receive the information of the parameterized data points in the receive direction for
the connected AGP device are displayed.
Field Note
Count Number of parameterized data points in receive direction
Count receive binary idications Number of incorrectly parameterized data points for "binary
informations" in the receive direction
Count receive measuered values Number of incorrectly parameterized data points for "measured
values" in the receive direction
Count errors Number of faulty parameterized data points in receive direction

DC8-037-2, Edition 11.2020
Field Note
Error Error number
• ERR = 0 ....... no error

• ERR = 1 ....... SICAM type identification (TI) invalid
• ERR = 2 ....... SICAM sub adress invalid
• ERR = 4 ....... detailed routing type invalid
• ERR = 5 ....... SICAM type identification (TI) not supported
• ERR = 6 ....... not supported type ID for this object type
• ERR = 7 ....... AGP function code invalid
• ERR = 8 ....... wrong setting conversion of binary inputs
• ERR = 15 ...... SICAM address is used twice
• ERR = 16 ...... AGP address is used twice
• ERR = 17 ...... wrong setting analog value adaption
• ERR = 18 ...... threshold used but no analog value adaption
• ERR = 23....... link address is invalid or not used
• ERR = 100 ..... capsule no. for measured value wrong or
too large
• ERR = 101 ..... X0 and X100 are equal of linear adaption
• ERR = 102 ..... X100 is less than X0 of linear adaption
• ERR = 103 ..... Y0 and Y100 are equal iof linear adaption
• ERR = 104 ..... absolute threshold larger than 103%
• ERR = 105 ..... additive threshold larger than 1000%
• ERR = 106 ..... IEC group for counters too large
• ERR = 107 ..... transmission for counters too large
• ERR = 108 ..... adaption too large for counters
• ERR = 109 ..... capsule no. for counters wrong or too large
• ERR = 115 ..... suppression time faulty state invalid
• ERR = 116 ..... suppression time intermadiate pos. Invalid
• ERR = 120 ..... capsule no. for bin.information wrong or
too large
• ERR = 121 ..... wrong assignment type ID and bin. informa-
tion type
• ERR = 122 ..... bin. information conversion invalid
Routing type Detailed routing type for this data point:
• binary indication
• analog value
Station no. Station number of the AGP device

DC8-037-2, Edition 11.2020
Field Note
Data type AGP data type:
• current integral value
• inspection result not OK
• inspection result OK
• malfunction: temperature too high
Last time sent Time of the last transfer of the data point PRE → BSE
Last COT sent Last transmitted cause of transmission (COT) for this data point
from PRE → BSE
Last dp qual sent Last sent quality descriptor for this data point from the PRE →
BSE
Last value sent Last sent value for this data point from the PRE → BSE
Routing Receive (Filter not used)

All faulty parameterized data points in receive direction are displayed. Faulty data points are marked "red".
Routing Receive - with text filter


DC8-037-2, Edition 11.2020

All faulty parameterized data points in receive direction are displayed.

DC8-037-2, Edition 11.2020
12.18.8.6 Developer Information – Freespace
On the web page Developer Information – Freespace internal information (free memory) of the firmware is
displayed.
Field Note
Count malloc Internal information
Count free Internal information
Heap complete (Bytes) Internal information
Heap internal (Bytes) Internal information

DC8-037-2, Edition 11.2020
With web page Developer Information – Dataflow Test messages transmitted via internal interface from PRE
↔ BSE will be displayed.
Field Note
No. Message number

Station A8000 internal station number of connection
COT IEC 60870-5-101/104 cause of transmission (A8000 internal)
Origin IEC 60870-5-101/104 originator address (A8000 internal)
Data IEC 60870-5-101/104 state of the data point
(A8000 internal)
(A8000 internal)
Time Receive time (AGP)
Message filter for simultaneous logging ("Monitoring Filter")


DC8-037-2, Edition 11.2020
The value "255" sets this field to "Wildcard". i.e. all messages are logged with this field (0-255).
Message filter for logging - Suppress Filter

If a filter is selected, the messages selected by the filter are not logged (i.e., "suppressed"). If no filter is
selected all messages will be logged.
The value "255" sets this field to "Wildcard". i.e. all messages with this field (0-255) are suppressed.

DC8-037-2, Edition 11.2020

General information of PRE firmware ("PRE general Information")
Field Note
IDR diagnostic information of the PRE firmware ("PRE diagnosis information (IDR)")
Field Note
Name Diagnosis text

12.18.8.9 Developer Information – Diagnosis (IDH)
The Developer Information – Diagnosis (IDH) web-page will display the last 2000-4000 data sent / received
in HEX and ASCII without timestamps.
Deleting the IDH diagnostic information on the PRE ("Clear serial test")
The IDH diagnostic information (serial test) on the PRE, can be deleted under "Clear serial test" with Clear.

DC8-037-2, Edition 11.2020
IDH-Diagnostic information "serial test"
Field Note
Direction TXD = Transmit Data (of PRE)
RXD = Receive Data (of PRE)
00, 01, 02, .. 15 Byte no. (0-15) per row
The transmitted/received bytes are entered in chronological
order into the byte number TXD xxxx-yyyy, RXD xxxx-yyyy.
TXD xxxx-yyyy Byte number for transmit data
RXD xxxx-yyyy Byte number for receive data
HEX The left range of the table (byte number 00..15) shows the
sent/received data are in HEX.
ASCII The right range of the table (byte number 00..15) shows the
sent/received data are in ASCII.
12.18.8.10 Developer Information – Diagnosis
On the web page Developer Information – Diagnosis (IDZ) detailed information of the last 10,000 trans-
mitted/received data or "transmission events" with time tags are shown.
Deleting the IDZ diagnostic information on the PRE ("Clear serial test")
The IDZ diagnostic information on the PRE can be cleared under "Clear serial test" with Clear.

DC8-037-2, Edition 11.2020
IDZ-diagnostic information "Serial test"
Field Note
Serial test xxxxx bytes in Number of stored transmission events in the buffer (max. 10000).
buffer. If more than 10,000 transmission events are recorded, the value xxxxx
remains at 10000 and the oldest transmission events are deleted.
Field Note
Date and time Current date + time of the entry
Time difference Difference time to previous event

DC8-037-2, Edition 11.2020
Field Note
Type Tansmission event:
• TXD … Data byte sent

• RXD … Data byte received
• TPD … Data bit sent "ON/OFF" (pulse duration modulation) 359
• RPD … Data bit received "ON/OFF" (pulse duration modulation) 359
• RTS ON ... RTS status line "ON" <OUT> (“manually“ controlled by PRE)
• RTS OFF ... RTS status line "OFF" <OUT> (“manually“ controlled by PRE)
• RTS_T0 ON ... RTS status line "ON" <OUT> (controlled by UART)
• RTS_T0 OFF ... RTS status line "OFF" <OUT> (controlled by UART)
• DTR ON … DTR status line "ON" <OUT>
• DTR OFF … DTR status line "OFF" <OUT>
• DCD ON … DCD status line "ON" <IN>
• DCD OFF … DCD status line "OFF" <IN>
• CTS ON … CTS status line "ON" <IN>
• CTS OFF … CTS status line "OFF" <IN>
• DCD_T1 ON … DCD bounce suppression "ON"
• DCD_T1 OFF … DCD bounce suppression "OFF"
• TI0 … Timer 0 expiration
• TI2 … Timer 2 expiration (typisch verwendet für Quittungserwartungs-
zeit)
• TI3 … Timer 3 expiration (typisch verwendet für Neusync)
• USER … User transmission event (including user identifier <0-255>)
– triggered by the PRE firmware
– Entry chronological to IDZ (only for diagnosis)
– User identification is entered in the column "User".
TXD Data-Byte/-Bit sent
• xx,‘x‘ … Displayed in HEX, ‘ASCII‘

• ON, OFF … TXD Bit statu "ON/OFF" (only with pulse duration modula-
tion) 359
RXD Data-Byte/-Bit received
• xx,‘x‘ … Displayed in HEX, ‘ASCII‘

• ON, OFF … RXD Bit status "ON/OFF" (only with pulse duration modula-
tion) 359
359 only possible with CI-8551

DC8-037-2, Edition 11.2020
Field Note
User Additional information about the transmission event "Type=User":
• 0-255 … If Type = USER, then the value transmitted by the PRE firm-
ware is entered in the "USER" field.
Status Status for transmission event "Type=RXD":
• GAP … Pause detected on reception ("message gap")

• PARITY … Parity fault
• FRAMING … Framing fault
• OVERRUN … Overrun fault
• OVERRUN_BUFFER … Overrun RX (Intermediate buffer error)
IDZ-diagnostic information "Serial test" - with text filter

12.18.8.11 Developer Information – Diagnosis (IDE)
The Developer Information – Diagnosis (IDE) web-page displays PRE-internal diagnostic information or
statistics information.

DC8-037-2, Edition 11.2020
Deletion of the IDE diagnostic information on PRE (“Clear diagnosis“)

The IDE diagnostic information on the PRE can be cleared under "Clear diagnosis" with Clear.
General information of the IDE diagnosis ("General information")
Field Note
Cleared at Time of IDE diagnosis information cleared
Query at Last query time of IDE diagnosis information
Redundancy state Actual redundancy state of PRE firmware

DC8-037-2, Edition 11.2020
General information of the IDE diagnosis ("polling")
Field Note
Min. cycle time (all stations OK) Minimum cycle time for all “OK” stations
Max. cycle time (all stations OK) Maximum cycle time for all “OK” stations
Min. cycle time Minimum cycle time
Avg. cycle time (last 10 cycles) Average cycle time (last 10 cycles)
Informations about the control location of the PRE‘s (“Control location“)
Field Note
The activated control locations will be displayed when control
location function is enabled. Note: this function is currently not
supported!
Receive error statistics ("Receive Errors")
Field Note
Parity error Number of detected “parity errors”
Framing error Number of detected “byte framing errors”
Overrun error Number of detected “overflow errors”
Comment:
In case of overflow error the firmware load is too high - the
received bytes can no longer be processed correctly.
Sync character invalid Number of detected “sync character invalid” errors
End character invalid Number of detected “end character invalid” errors
Receive buffer full Number of detected “receive buffer full” errors
Length invalid Number of detected “length invalid” errors
Checksum error Number of detected “checksum errors”
Invalid gap Number of detected “invalid gap” errors between 2 bytes of
within same message.
State of Communication Link ("Station State")

For each station, the current status and statistics about the number of failures and retries are displayed.
Field Note
State OK ….… Communication link OK
NOK ..… Communication link NOK (failed)
Retry count Number of retries since last Clear diagnosis
NOK count Number of communication link NOK (failed) since last Clear
diagnosis
Retry rate Number of retries in % since last Clear diagnosis

DC8-037-2, Edition 11.2020
Chronological list of retries and station failures ("Station History")
Field Note
Time Date + Time of communication error (OK, NOK, Retry)
State State:
• Retry no x … Retry number x

• Station OK
• Station NOK

DC8-037-2, Edition 11.2020
12.19 IOT
12.19 IOT
The IOT protocol (“Internet Of Things”) is an Ethernet protocol for transmitting messages (process information)
to the cloud for processing/data analysis by higher-level systems.
The connection to the Internet is made via an external GPRS router or via Internet access via Ethernet.
The following protocol firmware is available:
OPUPT0 CP-8000 IOT-Publisher (MQTT) for AWS Cloud (Amazon Web
CP-802x Services) and Microsoft Cloud (Azure)
OPUPT1 CP-8000 IOT-Publisher for Mindsphere (Siemens)
CP-802x
IOT Data Transfer/Data Processing - Overview
• CP-8000/CP-802xsends messages with process informations as a “Publisher” to a “Broker” of a cloud

provider (Microsoft Azure, Amazon Web Services, Siemens Mindsphere).
• The messages are stored in the broker.
• Subscribers can register at the broker for data from selected devices.
• The stored messages are distributed by the broker to the subscribers.
• The subscribers can then carry out extensive data analyzes and evaluations as required with the associ-
ated data from the cloud.
Schematic configuration for IOT Publisher (MQTT):
[OPUPTx_Configuration, 1, --_--]

DC8-037-2, Edition 11.2020
12.19 IOT
12.19.2 Functions
Function OPUPT0 OPUPT1

■ "IOT-Publisher" for CP-8000/CP-802x X X
■ Supported IOT protocols

– OPC UA PubSub 1.04 (MQTT) (IEC 62541) X
– MindConnect (HTTPS, native MindSphere IoT Protocol) X
■ Network configuration
– IOT Publisher to Cloud-Destination 1 1
– Port number MQTT 1883
– Port number MQTT + TLS 8883
– Port number HTTPS 443
■ Broker Mode
– MQTT X
■ Supported Cloud Services

– AWS (Amazon Web Services) X
– Azure (Microsoft) X
– local Broker X
– Mindsphere (Siemens) X X
■ Connection mode for cloud services

– AWS (Amazon Web Services) TLS
– Azure (Microsoft) TLS
– local Broker - without TLS
- with TLS
- with TLS +
JWT 360
– Mindsphere (Siemens) - with TLS + HTTPS
JWT 360
■ Security
– Preshared Key X
– Username, Password X
– Certificates X
■ License
– License required to use the firmware in CP-8000/CP-802x .
■ Physical interface "Ethernet"

– X1, X2 X X
360 Json WEB Token

DC8-037-2, Edition 11.2020
12.19 IOT
Function OPUPT0 OPUPT1
■ LAN/WAN communication over Ethernet TCP/IP

– Ethernet interface X X
– TCP/IP optimization parameter X X
– TCP/IP Keep Alive X X
■ Supported IEC60870-5-101/-104 data formats in transmit direction (SICAM A8000 → IOT)

– <TI=30> ... Single-point information with CP56Time2a time tag X X
– <TI=31> ... Double-point information with time tag CP56Time2a X X
– <TI=32> ... Transformer tap position value CP56Time2a time tag X X
– <TI=34> ... measured value, normalized value with time tag CP56Time2a X X
– <TI=35> ... Measured value, scaled value with time tag CP56Time2a X X
– <TI=36> ... Measured value, floating point number with time tag X X
CP56Time2a
– <TI=37> ... Integrated totals with time tag CP56Time2a X X
■ Supported IEC60870-5-101/-104 data formats in receive direction (SICAM A8000 ← IOT)

–
■ Webserver (PRE specific WEB-Pages) X X
■ Engineering
– SICAM Device Manager X X
– SICAM TOOLBOX II X X
Restrictions
• In receive direction “SICAM A8000 ← IOT” no data formats are supported!
ment.
optional DTE
(twisted pair) X4
GPRS X7361 (Antenna)
361 only CP-8022

DC8-037-2, Edition 11.2020
12.19 IOT
Own station "IOT-Publisher" (Client)

SICAM A8000 Series CP-8000 OPUPT0 IOT Publisher MQTT for:
CP-802x
• Microsoft Azure
Cloud
• Amazon Web Serv-
ices (AWS)
• Mindsphere
(Siemens)
OPUPT1 IOT Publisher (Mind-
sphere) for:
Siemens Mindsphere
Remote station "Broker" (Server for WEB Services)

Broker for Microsoft Azure - -
Cloud
Broker for Amazon AWS - -
Cloud
Broker for Siemens Mind- - -
sphere Cloud
local Broker - -
12.19.5 Parameters and Properties
12.19.5.1 Parameter and Properties (OPUPT0)

[PRE] Interface parameter
[PRE] Broker Mode
Broker Mode Selection with which protocol data Permitted range =
should be sent to the broker
• AMQP
• MQTT
Default setting = MQTT
[PRE] AMQP Broker
Station number (internal) SICAM A8000 internal station Permitted range =
number for diagnostic, data
routing
• 0 to 99 ... internal station
number
• 255 ... not used
Station failure If the TCP/IP connection fails, the Permitted range =
transmission of the error message
can be suppressed with station
• yes (=notification)
failure = no • no (=no notification)

DC8-037-2, Edition 11.2020
12.19 IOT

Station name Dynamic part in the Publisher ID Permitted range =
• Max. 64 characters
• valid signs: A to Z, a to z,
0 to 9, “_“
Default setting =
AMQP IP address IP Address of the broker (AMQP) as Permitted range =
remote station (in format: IPV4). 0.0.0.0 to 255.255.255.254
Note: Standard setting = 0.0 0.0
AMQP IP address is only
required if the broker has a static IP
address (0.0.0.0 = AMQP Host-
name is used). The IP address of the
own station is set on the BSE.
Connection Mode Mode whether AMQP should be Permitted range =
used encrypted or unencrypted.
• without TLS, without SASL
(Port 5672)
• with TLS, without SASL (Port
5671)
• without TLS, with SASL (Auth.
Plain) (Port 5672)
• with TLS, with SASL (Auth.
Plain) (Port 5671)
• with TLS, with SASL (Auth.
Plain) Azure (Port 5671)
Default setting = with TLS, with
jSON web token (JWT)
AMQP Hostname Host name of the AMQP broker Permitted range =
Example for Siemens Mindsphere:
AMQP Hostname =
mqtt.eu1.mindsphere.io • valid signs: A to Z, a to z,

0 bis 9, _, .
Default setting =
AMQP source Permitted range =

• valid signs: A to Z, a to z, 0 to
9, “_“
AMQP target Permitted range =

9, “_“
AMQP/SASL username User name for MQTT authentica- Permitted range =
tion (not used with JWT).
9, “_“
Default setting =

DC8-037-2, Edition 11.2020
12.19 IOT

AMQP/SASL password Password for MQTT authentication Permitted range =
(not used with JWT).
9, “_“
Default setting =
Encoding Permitted range =
• SIEMENS
• OPC_UA
default setting = SIEMENS
File transfer Permitted range = 0 to 65535 s
Default setting =
KeepAlive Permitted range = 0 to 65535 s
Default setting =
Keyframe Permitted range = 0 to 65535 s
Default setting =
Metaframe Permitted range = 0 to 65535 s
Default setting =
SAS Token validity Permitted range = 0 to 65535 days
Default setting =
SAS connection string Permitted range =

9, “_“
Measuring value cycle Time for the state compression for Permitted range = 0 to 65535 s
measured values Default setting = 30 s
MSS (maximum segment size) Maximale TCP/IP segment size. Permitted range = 0 to 1460 byte
Default setting = 1460 byte
DNS Server IP Address of the DNS Server (in Permitted range =
format IVP4). 0.0.0.0 to 255.255.255.254
IP-Address 8.8.8.8 = Google DNS
Server (public DNS-Server)
Learn data points Dynamic learning of the data Permitted range =
points. No detailed routing of the
data points required.
• always
The name of the data point is algo- • with first general interroga-
rithmically generated from the IEC tion
60870-5-101/104 address. • only via message address
conversion
Default setting = always
Certificate Own certificate/private key for the Permitted range =
TLS encryption.
• not used
• Certifivate 1 to 10
Certificate authority Broker certificate for authentica- Permitted range =
tion.
• Certificate authority 1 to 10

DC8-037-2, Edition 11.2020
12.19 IOT

[PRE] MQTT Broker
routing
number
• 255 ... not used
failure = nein. • no (=no notification)
Station name Dynamic part in the Publisher ID Permitted range =
• valid signs: A to Z, a to z,
0 to 9, “_“
Default setting =
MQTT IP address IP Address of the broker (MQTT) as Permitted range =
remote station (in format: IPV4). 0.0.0.0 to 255.255.255.254
MQTT IP address is only
required if the broker has a static IP
address (0.0.0.0 = MQTT host
name is used). The IP address of the
own station is set on the BSE.
Connection Mode Mode whether MQTT should be Permitted range =
encrypted or unencrypted.
• without TLS (Port 1883)
• with TLS (Port 8883)
• with TLS, with jSON web
token (JWT, Port 8883)
Default setting = with TLS, with
jSON web token (JWT)
MQTT host name Host name of the MQTT broker Permitted range =
Example for Siemens Mindsphere:
MQTT host name =
mqtt.eu1.mindsphere.io • valid signs: A to Z, a to z,

0 bis 9, _, .
Default setting =
MQTT Client ID Name of publisher at MQTT level. Permitted range =
Default equal to the publisher ID.
• permitted characters: all (incl.
special characters)
Default setting =
MQTT topic Topic for the MQTT message. Permitted range =
Note:
Topic name for Siemens Mind-
sphere: c/{ClientID}/o/opcua/
• permitted characters: all (incl.
special characters)
{VersionMS}/u/{Meas:d}{File:d}
{Meta:m} Default setting =

DC8-037-2, Edition 11.2020
12.19 IOT

MQTT user name User name for MQTT authentica- Permitted range =
tion (not used with JWT).
9, “_“
Default setting =
MQTT password Password for MQTT authentication Permitted range =
(not used with JWT).
9, “_“
Default setting =
File transfer Permitted range = 0 to 65535 s
Default setting =
KeepAlive Permitted range = 0 to 65535 s
Default setting =
Keyframe Permitted range = 0 to 65535 s
Default setting =
Metaframe Permitted range = 0 to 65535 s
Default setting =
Measuring value cycle Time for the state compression for Permitted range = 0 to 65535 s
measured values Default setting = 30 s
MSS (maximum segment size) Maximum TCP/IP Segment Size. Permitted range = 0 to 1460 byte
DNS Server IP Address of the DNS Servers (in Permitted range =
format: IPV4). 0.0.0.0 to 255.255.255.254
Server (public DNS-Server)
• always
conversion
Certificate Own certificate/private key for the Permitted range =
TLS encryption.
• not used
• Certifivate 1 to 10
Certificate authority Broker certificate for authentica- Permitted range =
tion.
• Certificate authority 1 to 10

DC8-037-2, Edition 11.2020
12.19 IOT

[PRE] HTTP-Webserver
HTTP web server With a web browser protocol- Permitted range =
internal information can be
displayed.
• disabled
Note: • enabled
For safety reasons, the web server Default setting = disabled
operation.
12.19.5.2 Parameter and Properties (OPUPT1)

[PRE] Interface parameter
[PRE] Mindsphere
routing.
number
• 255 ... not used
failure = no . • no (=no notification)
Mindsphere IP address IP Address of the tenant as remote Permitted range =
station (in format: IPV4). 0.0.0.0 to 255.255.255.254
Mindsphere IP address is only
required if the tenant has a static IP
address (0.0.0.0 = Mindsphere
Hostname is used). The IP address
of the own station is set on the
BSE.
Tenant Tenant of the Mindsphere Permitted range =
customer
9, “_“
Default setting =
Init Token Initial Access Token from the Mind- Permitted range =
sphere
Default setting =
User Agent Agent ID from the Mindsphere Permitted range =

9, “_“
Default setting =

DC8-037-2, Edition 11.2020
12.19 IOT

Mindsphere Hostname Hostname of the Mindsphere Permitted range =
Tenants
9, “_“, "."
Default setting =
Initial Registration URI Registration address from the Permitted range =
Mindsphere
9, “_“, "."
Default setting =
Security Policy Permitted range =
• Preshared Key
Default setting = PreShared Key
KeepAlive Key Rotation Interval Permitted range = 0 to 65535 s
Keyframe Time between 2 general interroga- Permitted range = 0 to 65535 s
tions Default setting = 7200 s
MSS (maximum segment size) Maximum TCP/IP Segment Size Permitted range = 0 to 1460 byte
DNS Server IP Address of the DNS Servers (in Permitted range =
format: IPV4). 0.0.0.0 to 255.255.255.254
Server (Öpublic DNS-Server)
• always
conversion
Buffer time Time interval in which data is Permitted range = 0 to 65535 ms
"collected" and then uploaded Default setting = 10000 ms
together.
[PRE] HTTP-Webserver
HTTP web server With an Internet Explorer (WEB Permitted range =
browser), protocol-internal infor-
mation can be displayed.
• disabled
Note: • enabled
For safety reasons, the web server Default setting = disabled
should be "disabled" in a system in
operation.

DC8-037-2, Edition 11.2020
12.19 IOT
IEC 60870-5-101/104 ↔ IOT is performed by the protocol element. The transmission of the data to the IOT
cloud is controlled by the protocol element.
Data in the receive direction are not supported by the protocol element!
The conversion of the SICAM A8000 internal IEC 60870-5-101/104 message format → IOT data format and the
The parameterization of the conversion from IEC 60870-5-101/104 ↔ IOT (address and message format) is to
be done with SICAM Device Manager with function “Signals” or SICAM TOOLBOX II / OPM using “SIP Message
Address Conversion”.
Categories for SIP Message Address Conversion
Data Direction Processing type OPUPT0 OPUPT1

Binary informa- Transmit direction firmware/Send ✓ ✓
tion
Measured Transmit direction firmware/Send ✓ ✓
values
Integrated Transmit direction firmware/Send ✓ ✓
totals
12.19.6.1 Message Conversion in Transmit Direction (SICAM A8000 → IOT)

Message Conversion in Transmit Direction IEC 60870-5-101/104 → IOT
SICAM A8000: IEC 60870-5-101/104 → IOT
TI Designation Designation
<TI:=30> Single-point information with CP56Time2a time tag SPSValue
<TI:=31> Double-point information with time tag CP56Time2a DPSValue
<TI:=32> Transformer tap position value CP56Time2a time tag StepPosValue
<TI:=34> Measured value, normalized value with time tag CP56Time2a MeasuredValue
<TI:=35> Measured value, scaled value with time tag CP56Time2a MeasuredValue
<TI:=36> Measured value, short floating point number with time tag MeasuredValue
CP56Time2a
<TI:=37> Integrated totals with time tag CP56Time2a CounterValue
Binary information
be done with the SICAM Device Manager with the function “Signale” or the SICAM TOOLBOX II / OPM.
Processing: firmware/Send
[OPUPI0_DM_Send_Meldung, 1, en_US]
Parameters

• <TI:=32> .. Step position information with CP56Time2a time tag
Name Name of the signal

DC8-037-2, Edition 11.2020
12.19 IOT
Parameters
104 address SICAM A8000 internal IEC 60870-5-101/104 message address
VTA Process-technical address of the data point:

• permitted characters: all incl. special characters
Example: /Alarm/battery_alert.Batterie
Long text Description of the data point:

Example: /Alarm/battery_alert.Batterie
Unit_ not used for binary information
Examples for alarms (SPS = SinglePointState) in Mindsphere: (possible representation in subscriber):

TI: 30
CASDU1: 1
CASDU2: 2
IOA1: 30
IOA2: 4
IOA3: 5
VTA: /Alarm/battery_alert.Battery
Long text: /Alarm/battery_alert.Battery
Message Conversion
tag
CP56Time2a
• <TI:=32> .. Step position information with CP56Time2a
time tag
BL .. blocked is evaluated and implemented on quality information from
PubSub

DC8-037-2, Edition 11.2020
12.19 IOT

SB .. substituted is evaluated and implemented on quality information from
PubSub
NT .. not topical is evaluated and implemented on quality information from
PubSub
IV .. invalid is evaluated and implemented on quality information from
PubSub
xx .. evaluated
Information
Single point information only <TI:=30> Single-point information with time tag
CP56Time2a
1 .. ON evaluated
Double point information only <TI:=31> Double-point information with time tag
CP56Time2a
DPI 0 .. indeterminate or evaluated
intermediate state
1 .. OFF evaluated
2 .. ON evaluated
Step position information only <TI:=32> Step position information with time tag
CP56Time2a
VTI Values of the intermediate evaluated
state information
–64 to +63
Intermediate state evaluated
<0> Operational equip-
ment not
in intermediate state
<1> Operational equip-
ment in
Intermediate state
Time tag
CP56Time2a .. Date + Time evaluated
measured values, counters

be done with the SICAM Device Manager with the function “Signale” or the SICAM TOOLBOX II / OPM.
Processing: firmware/Send
[OPUPI0_DM_Send_Wert, 1, en_US]

DC8-037-2, Edition 11.2020
12.19 IOT
Parameters

CP56Time2a
Name Name of the signal
104 address SICAM A8000 internal IEC 60870-5-101/104 message address
VTA Process-technical address of the data point:

Example: P_GEN_1
Long text Description of the data point:

Example: Performance Generator 1
Unit_ Description of the data point:
Examples: MW, mA, MegaWatt,…
Example for MeasuredValue in Mindsphere: (possible representation in subscriber):

TI: 36
CASDU1: 1
CASDU2: 2
IOA1: 3
IOA2: 4
IOA3: 5
VTA: LV/Bay4_1kxz5.150A/Current_N.ILN
Long text: LV/Bay4_1kxz5.150A/Current_N.ILN
Unit:

DC8-037-2, Edition 11.2020
12.19 IOT
Message Conversion
CP56Time2a
CP56Time2a
BL .. blocked is evaluated and implemented on quality information from
PubSub
SB .. substituted is evaluated and implemented on quality information from
PubSub
NT .. not topical is evaluated and implemented on quality information from
PubSub
PubSub
OV .. overflow is evaluated and implemented on quality information from
PubSub
xx .. other COTs evaluated
Information
• scaled value
Time tag

TI .. Type Identification • <TI:=37> .. Integrated totals with time tag CP56Time2a
Sequence number will not be rated
CY .. Carry will not be rated
CA .. Presets will not be rated
PubSub
xx .. other COTs evaluated
Information

DC8-037-2, Edition 11.2020
12.19 IOT

S .. sign
Time tag
12.19.7 Web Server
A web server is integrated into the protocol firmware for internal diagnostic information. The web server is
part of basic system element – the PRE specific web pages will be provided by protocol element.
System Firmware DNP3 PRE specific Web Pages
CP-8000 OPUPT0 IOT-Publisher (MQTT) for ✓
CP-8021 AWS Cloud (Amazon Web
CP-8022 Services), Mindsphere
(Siemens) and Microsoft
Cloud (Azure)
OPUPT1 IOT-Publisher for Mind- ✓
sphere (Siemens)

With the SICAM TOOLBOX II or a web browser, the integrated web server is addressed by specifying the IP
address of the automation unit.
With the CP-8000/CP-802x, the web server for the protocol elements on PRE0 to PRE3 can be reached as
follows (example):
NOTE
access by the user with the parameter [PRE] HTTP web server | HTTP web server.

PRE specific web page for
OPUPT0 OPUPT1
• Overview
– List(s) ✓ ✓
– Asset Information ✓ ✓
• Developer Information

DC8-037-2, Edition 11.2020
12.19 IOT
PRE specific web page for

OPUPT0 OPUPT1
– Freespace ✓ ✓
– Duration ✓ ✓
– Connection Log ✓ ✓
NOTE
An updating of the web page displayed in the web browser can be performed e.g. by means of a refresh of
the web browser.
12.19.7.2 Overview

Field Note
IP address Own IP address of the assigned interface
Default gateway Default gateway of the assigned interface
Subnet mask Subnet mask of the assigned interface
MAC address MAC address of the assigned interface
• Ready
•
Manufacture# of hardware MLFB-number + Serial number of the hardware group
Manufacture# used (from MLFB-number + Serial number of the hardware group from the SD Card
Backup) (Spare part concept)

DC8-037-2, Edition 11.2020
12.19 IOT
With web page Connections detailed information about the status of the connection to the broker will be
displayed.
Field Note
Broker IP address IP address of the broker
Broker hostname Host name of the broker
Broker mode Broker mode:
• MQTT
Connection mode parameter MQTT Connection Mode (encrypted / unencrypted, authentication)
Connection mode MQTT MQTT Connection Mode (encrypted / unencrypted, authentication)
MQTT client id Client-ID on MQTT level (default: Publisher-ID)
MQTT topic 0 Topic von dem MQTT-Subscriber die Daten abholen können
MQTT topic 1 362 Not used
Username Username for authentication on protocol level
Password Password for authentication on protocol level
MQTT ping Monitoring time on MQTT level
Message ACK Acknowledgment time for last sent message to the broker (Publish ACK)
362 only OPUPI0

DC8-037-2, Edition 11.2020
12.19 IOT

With web page Routing Transmit information about the parameterized data points to the broker in transmit
direction are shown.
Field Note
Routing from Toolbox file Automatically converted data points from the applied signals
Count Number of parameterized data points in transmit direction from the Toolbox
file
Error Error number
• ERR = 0 …. no error
Routing from PRE message Message conversion based on SIP message conversion (detailed routing)
conversion
Error Error number
Routing learned Number of learned data points in transmit direction
Error Error number
TI IEC 60870-5-101/104 Type identification (CP-8050 internal)
IOA1, IOA2, IOA3
Name Data point name
Description Long text
Unit Address of the data point
All parameterized data points in transmission direction are displayed. Incorrect parameterized data points are
marked "red".

DC8-037-2, Edition 11.2020
12.19 IOT
12.19.7.5 List(s)
On the web page List(s) the current data model sent to Mindsphere will be displayed.

DC8-037-2, Edition 11.2020
12.19 IOT
12.19.7.6 File List(s)
On the web page File List(s) information about the last sent file (for example, Asset Information) is displayed.

DC8-037-2, Edition 11.2020
12.19 IOT
12.19.7.7 Asset Information

The Asset Information web page displays information from substations of other protocol elements (e.g.,
61850). The information is exchanged between the protocol firmwares.
NOTE
i This function is currently only supported between the protocols ET85 and OPUPT0.
Field Note
Asset information source Asset information source
• Function disabled
• Information about the protocol element from which the asset informa-
tion is read (Example: Revision, IP address, ...)
Asset Information Asset information - provided by another protocol

DC8-037-2, Edition 11.2020
12.19 IOT
12.19.7.8 Developer Information - Freespace
With web page Developer Information – Freespace internal information (free memory) of the firmware is
displayed.
This information is helpful in the case of error detection and should be sent to support as needed.
Field Note
Heap (Byte) Internal information
Used (Byte) Internal information
Max Used (Byte) Internal information
Free (Byte) Internal information
Count alloc Internal information
Count calloc Internal information
Count realloc Internal information
Count free Internal information

DC8-037-2, Edition 11.2020
12.19 IOT
12.19.7.9 Developer Information - Duration
On the web page Developer Information – Duration internal task run times are shown.
These informations are helpful for the developer in case of problems.
Field Note
Type Internal information
Count Internal information
Act (us) Internal information
Min (us) Internal information
Max (us) Internal information
12.19.7.10 Developer Information - Connection Log
On the web page Developer Information – Connection log displays a chronological list of connection infor-
mation (connection state) to the broker.
The connection log list will be deleted on restart or reset. A maximum of 100 entries are saved in the list.
Field Note
No. Consecutive number
Time Time of logging in the log
Error Type of error
Status Error state

DC8-037-2, Edition 11.2020
12.19 IOT

With web page Developer Information – Dataflow Test messages transmitted via internal interface from PRE
↔ BSE will be displayed.
Field Note
No. Message number

TI IEC 60870-5-101/104 Type identification (CP-8050 internal)
IOA1, IOA2, IOA3
COT IEC 60870-5-101/104 Cause of transmission (SICAM A8000 internal)
Origin IEC 60870-5-101/104 Originator address (SICAM A8000 internal)
Data IEC 60870-5-101/104 State of data point (SICAM A8000 internal)
Time Time in logged message

DC8-037-2, Edition 11.2020
12.19 IOT
Message filter for simultaneous logging (“Monitoring Filter”)

With the value 255 "Wildcard" is set for this field. This means that all messages with this field (0 to 255) are
logged.
Message filter for logging - “Suppress Filter”

With filter enabled, messages selected by filter will be suppressed from logging. If no filter is selected all
With the value 255 “Wildcard” is set for this field. This means that all messages with this field (0 to 255) are
suppressed.

DC8-037-2, Edition 11.2020
12.19 IOT

General information of PRE firmware ("PRE general Information")
Field Note
FWName Name of PRE firmware
Build State of generation of the PRE firmware
IDR diagnostic information of the PRE firmware ("PRE diagnosis information (IDR)")
Field Note
Name Diagnosis text

DC8-037-2, Edition 11.2020
12.19 IOT
Field Note


DC8-037-2, Edition 11.2020
12.20 VLAN
12.20 VLAN
Virtual Local Area Networks (VLANs) are logical networks that are implemented on a physical LAN.
In this way, several logically separated networks can be operated for different areas on one physical network.
The technical basis for VLANs is described in the IEEE 802.1Q standard.
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 essen-
tial 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”.
12.20.2 Sample Applications
One application is that several logical VLANs are 'transmitted' to a CP-8050 over a single physical connection.
In the switch, the individual VLANs are then "switched through" to different physical switch ports.
[dw_use_case_vlan_1, 1, --_--]
The switch is a "VLAN aware switch" which processes the VLAN information (VLAN tag) in the Ethernet header.
Another application example is the integration of the CP-8050 in a physical ring, where different "logical rings"
are implemented via VLANs.

DC8-037-2, Edition 11.2020
12.20 VLAN
[dw_use_case_vlan_2, 1, --_--]
12.20.3 Configuration
On the CP8050, VLANs can be added to any simple Ethernet interface and to Ethernet switching groups. The
HSR and PRP switching groups are not supported in the first version.
The configuration is done in the Device Manager under System | Communication | LAN interfaces
| VLAN interfaces
The following parameters can be set for a VLAN:
• Port group
This parameter can be used to select the Ethernet interface or the switching group to which a VLAN is to
be added
• VLAN ID
This parameter can be used to specify the ID that is to be assigned to the VLAN. The valid range of values
is [1 ... 4094]
• VLAN Priority
This parameter can be used to specify the 3-bit priority value for VLAN packets that are sent via this VLAN.
The valid range of values is [0 ... 7]

DC8-037-2, Edition 11.2020
12.20 VLAN
Example
[sc_VLAN_config_1, 1, en_US]
The configured VLANs can then be used just like the physical interfaces for configuration of the LAN inter-
faces:
[sc_VLAN_config_2, 1, en_US]

DC8-037-2, Edition 11.2020
12.21 SNMP
12.21 SNMP
SNMP (Simple Network Management Protocol) is a network protocol used to monitor or control network
components (e.g. Router, Switches, Server or Automation units (SPS, 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 an SNMPv3 Agent in SICAM A8000 CP-8050 it is possible to read out SNMP Variables
(stored in the MIB = Management Information Base) via network with a standard network management soft-
ware (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.
[dw_A8000_snmp_config_8000_802x, 1, --_--]
The SNMP protocol (Agent) is integrated in the firmware of the master module.
SNMP variables retrievable via:
• Standard SNMP network management software
• SCADA system with integrated SNMP manager.
• SICAM SCC
12.21.2 Functions
• SNMP
– SNMPv2
– SNMPv3
– SNMP Agent
– Support of max. 4 Users
• Supported ports
– Port 161: SNMP, Incoming, UDP
– Port 162: SNMP Trap, Outgoing, UDP

DC8-037-2, Edition 11.2020
12.21 SNMP
• 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) 363
– SET (write of SNMP variables) 364
– RESPONSE (answer to GET, GETNEXT, GETBULK)
– TRAP (spontaneous data from SNMP Agent to SNMP Manager) 365
• Supported MIBs
– sicamRTUs
– MIB-2 (RFC1213)
– Ethernet-MIB (RFC3635) 366
– Host-Resources-MIB (RFC2790) 367
– USM-MIB (RFC2574)
– VACM-MIB (RFC2575)
– DGPI-MIB (Siemens Energy Management Digital Grid Product Inventory MIB)
• Supported SNMP variables MCPU (rough overview)

– Plant name
– Firmware Revision
– Uptime
– Port Status
– central error table
– TRAP “History” (Reading back of the last sent TRAPs)
– max. Number of saved traps: 50
• SNMPv3 “Security Level”

– 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)
• SNMPv3 “Privacy Protocol” (Protocol for encryption)

– DES (Data Encryption Standard)
• Security: Encrypted storage of passwords
363 available from SNMPv2

364 is only supported for the following SNMP Variables of MIB-2: sysName, sysLocation, sysContact
365 Traps are transmitted with Security Level = "authPriv" with username = "Trap" and the configured passwords for authentication and
encryption
366 is only partially supported; the supported OIDs are listed in the MIBs provided for SICAM A8000
367 is only partially supported; the supported OIDs are listed in the MIBs provided for SICAM A8000

DC8-037-2, Edition 11.2020
12.21 SNMP
12.21.3 Configuration
Enable SNMP
The SNMP function in SICAM A8000 (SNMP Agent) is released on the basic system element (BSE) with the
parameter Network Settings | SNMP | SNMP agent.
The desired SNMP version, SNMPv2 (without security) or SNMPv3 (with security) is selected on the basic
system element (BSE) with parameter Network settings | SNMP | SNMP Version.
Supported SNMP Versions:
• SNMPv3
– SNMP queries from SNMP Manager are only supported according to SNMPv3
– Traps are transmitted to only one SNMP manager in accordance with SNMPv3
Required security settings according to SNMPv3:
– Security Level (= authPriv)
– Authentication Protocol (= MD5)
– User Name / Password
– Privacy Protocol (= DES)
• SNMPv2 + SNMPv3
– SNMP queries from SNMP Manager are supported according to SNMPv2 or SNMPv3
– Traps are only transmitted to one SMNP manager according to SNMPv3
– Password “Community String” (for Read/Write)
– Security Level (= authPriv)
– Authentication Protocol (= MD5)
– Privacy Protocol (= DES)
– User Name / Password
SNMPv2
SNMPv2 supports a “Community String” (= password) as a backup for the access by the SNMP manager. The
community string is transmitted unencrypted and therefore offers only very limited security for SNMP queries.
The password for Read Community is set on the basic system element (BSE) with the parameter Network
Settings | SNMP | SNMPv2 | Password Read Community eingestellt.
The password for Write Community is set on the basic system element (BSE) with the parameter Network
Settings | SNMP | SNMPv2 | Password Write Community eingestellt.
Traps are not supported with SNMPv2!
SNMPv3
The SNMPv3 agent in SICAM A8000 supports a selection of the authentication and encryption protocols
defined in SNMPv3 as a backup for access by the SNMP manager.
The security level for SNMPv3 is set on the basic system element (BSE) with parameter Network settings
| SNMP | SNMPv3 | Security Level.
NOTE
i Currently only the security level “authPriv” is supported.

DC8-037-2, Edition 11.2020
12.21 SNMP
SNMPv3 defines the following security levels:
• authPriv = Authentication with encryption
• noAuthnoPriv = no authentication / no encryption 368
• authnoPriv = Authentication / no encryption 369
Protocol for authentication

The protocol for authentication is set on the basic system element (BSE) with parameter Network settings
| SNMP | SNMPv3 | Authentication protocol.
SNMPv3 defines the following protocols for authentication (Authentication Protocol):
• MD5 (Message Digest Algorithm)
• SHA (Secure Hash Algorithm) 370
Protocol for encryption

The protocol for encryption is set on the basic system element (BSE) with parameter Network settings |
SNMP | SNMPv3 | Privacy protocol.
SNMPv3 defines the following protocols for encryption (Privacy Protocol):
• DES (Data Encryption Standard)
• AES (Advanced Encryption Standard) 371
• 3-DES 372
User
SNMPv3 Agent in SICAM A8000 supports following user:
• User 1
• User 2
• User 3
• User 4
• User “Trap”
Every single user can be enabled or disabled.
The parameters for User 1-4 are set on the basic system element (BSE) with the parameters under Network
settings | SNMP | SNMPv3 | User #.
Parameter for User 1:
• User enabled
• User Name
• Password for authentication or Password for authentication PSK 373
368 currently no supported!

369 is currently not supported!
373 PSK (Pre Shared Keys) only possible with Secure Password Storage (settings for security)

DC8-037-2, Edition 11.2020
12.21 SNMP
• Password for encryption or Password for encryption PSK 374
• Enable write access for users

The change of the SNMP variables sysName, sysLocation, sysContact (defined in MIB-2) with SNMP SET can be
released with the parameter.
Parameter for User 2-4:
• User enabled
• User Name
• Password for authentication PSK 375
• Password for encryption PSK 376
• Enable write access for users

The change of the SNMP variables sysName, sysLocation, sysContact (defined in MIB-2) with SNMP SET can be
released with the parameter.
SNMPv3 Traps
Selected SNMP variables are spontaneously transferred from SICAM RTUs as “SNMP Trap” according to SNMPv3
to an SNMP manager (see SNMP Variables).
The transmission of the traps can be enabled on the basic system element (BSE) with the parameter Network
Settings | SNMP | SNMPv3 | Traps | Enable traps.
The parameters for traps are set on the basic system element (BSE) with the parameters under Network
settings | SNMP | SNMPv3 | Traps.
Parameter for traps:
• Enable traps
• User Name
The user name for the Trap function is set with “Trap” and can not be changed.
• IP-address for SNMP Manager (Traps)

Traps are only transferred to the SNMP manager with this IP address.
• Diagnostic Traps
The transmission of selected diagnostic information as traps can be enabled or disabled .
• Password for authentication PSK 377 Password for authentication for the transmission of traps.
• Password for encryption PSK 378 Password for encryption for the transmission of traps.
SNMPv3 “TRAP-History”
For selected SNMP traps, a limited number of changes can be read out via the SNMP variable "TRAP history".
The 50 most recently sent traps are entered in an SNMP table and can be read out with GET/GETBULK
GETNEXT (see SNMP Variables).
374 PSK (Pre Shared Keys) only possible with Secure Password Storage (settings for security)
375 PSK (Pre Shared Keys) only possible with Secure Password Storage (settings for security possible)

DC8-037-2, Edition 11.2020
12.21 SNMP
NOTE
i The TRAP history is deleted on reset or restart!
12.21.4 SNMP MIBs – Management Information Base
A MIB (management information base) describes the information, which can be retrieved or modified via a
network management protocol (e.g. SNMP). These informations are named "Managed Objects". These are
description files, in which the single values are listed in table form. A MIB is specific for each component.
12.21.4.1 Download of the MIB-Files

The MIB files can be downloaded from the SIOS Portal (Siemens Industry Online Support) https://
support.industry.siemens.com :
• Search for SICAM RTUS MIB in the SIOS Portal
• Click in the list of results on SICAM RTUs SNMP MIB File (Download)
After the download you get the file SICAMRTUs_SNMP_MIB_V06.00.00.zip.
• Save this file to the computer where the MIB Browser is installed (for example, C:/Siemens) and unpack
the MIB files.
12.21.4.2 Import the MIB files in the MIB Browser

The import of the MIB files into your MIB browser must be done in the following sequence:
• Import of SIEMENS-SMI.mib
• Import of sicamRTUs.mib
• Import of digitalGridProductInventory.mib
• Import ofemergencyUser.mib
• Import ofRFC1213-MIB.mib (optional)
• Import ofRFC3635_mib.mib (Ethernet-MIB, optional)
• Import of RFC2790_mib.mib (Host-Resources-MIB, optional)

Beside a standard MIB browsers you can load the MIB files also with the control center system SICAM SCC and
250 SCALA.
12.21.4.3 MIB: MIB-2 (RFC1213)

By means of this standard MIB, basic data of a CP-8050 system can be read out. The corresponding object ID is
called:
Path: iso.org.dod.internet.management.MIB-2.system.sysDescr (1.3.6.1.2.1.1.1)

DC8-037-2, Edition 11.2020
12.21 SNMP
Following objects are in this Object ID:

Objects Description / Example
Vendor Siemens AG
ProductFamily SICAM A8000
ProductName CP-8050
OrderNumber 6MF28..... (MLFB number)
HwVersion HW version of the device
FwVersion FW version of the device (e.g.: FW: 01.PB)
SwVersion SW version of the device
ProductSerialNumber (e.g.: SN: GC8-050--_88_BF1702....)
12.21.4.4 sicamRTUs
Path: iso.org.dod.internet.private.enterprises.siemens.sicamRTUs (1.3.6.1.4.1.22638.7)

DC8-037-2, Edition 11.2020
12.21 SNMP
12.21.4.5 MIB: dgpiMIB

(Digital Grid Product Inventory)

DC8-037-2, Edition 11.2020
12.21 SNMP
This private MIB implements the "Enterprise Asset Management (EAM)" domain model for all products of EM
DG PRO.
Path: iso.org.dod.internet.private.enterprises.siemens.siemensCommon.dgpiMIB (1.3.6.1.4.1.22638.11.1)
Object group 1: dgpiProdIdentity

This collection contains the supplier name ("Siemens AG") and some customer-related information at product
level, such as asset UUID (inventory number), customer name, product location, and geo-location. These
customer-related objects can only be read via SNMP. That is, they must be configured by the customer in other
ways (e.g., product-specific engineering tool, Web UI, etc.)
With the SICAM TOOLBOX II, this data can be entered with the following parameter: [BSE] System
settings | Device settings
Sub-Object group Objects Description
- dgpiVendorName Siemens AG
dgpiAssetUuid
dgpiCustomerName
dgpiLocationName
dgpiGeoPositionLatitude
dgpiGeoPositionLongi-
tude
dgpiGeoPositionAltitude
Object group 2: dgpiProdComp

This collection contains the product & component table (dgpiProductComponentsTable), which is the
most important object of the MIB. The product and its components are represented by lines in this table. The
first line is always occupied by the product, the following lines by the components. The order of the compo-
nents in the rows of this table is not mandatory.

DC8-037-2, Edition 11.2020
12.21 SNMP

dgpiProductComponent- dgpiProdCompIndex Index of the table line
sTable dgpiProdCompContai- Identifies the containment hierarchy of the product and
nedIn its components. It's zero in the product line because the
product is at the top of the hierarchy.
In the component rows, it corresponds to the value of
the object dgpiProdCompIndex of the product line (if
the component is directly from the product) or its
"parent" component row (if the component is contained
in a "parent" component).
dgpiProdCompClass identifies the class of the product or component of this
line
e.g.: hwProduct
dgpiProdCompName contains the name of the product or component
e.g.: SICAM A8000 CP-8050
dgpiProdCompDescrip- contains a brief description of the product or component
tion
dgpiProdCompOrder- contains the MLFB number of the product or component
Number e.g.: 6MF28050AA00
dgpiProdCompSerial- contains the serial number of the product or component
Number e.g.: BF1612034390
dgpiProdCompVersion contains the version number of the FW, HW, SW or the
configuration
dgpiProdCompHwSlot contains the number or name of the slot where the hard-
ware component is located
dgpiProdCompManu- contains the date of manufacture of the HW product or
factDate component
dgpiProdCompConfi- contains the last modification date and the last modifica-
gLastChange tion time of the updatable component
- dgpiProductCompTable- contains the date and time of the last change of each
LastChange dgpiProductComponentsTable object.
The change includes creation, removal and modification
of table rows.
This is in contrast to the dgpiProdCompLastChange
Change object, which refers to changing of rows, that
represent certain component classes.
Object group 3: dgpiNotifications

This group defines a notification (SNMPv2 trap, SNMPv3 indication). Sending this notification can be enabled /
disabled using the dgpiNotificationsEnabled object.
- dgpiNotificationsEna- enables/disables the sending of this notification
bled
dgpiNotificationProd-
CompChanged
Object group 4: dgpiConformance

This group contains compliance instructions. It defines that the implementation of the product identity and
product & component group objects is mandatory. The implementation of the objects of the notification
group is optional. The latter takes into account that not all SNMP agent implementations are prepared for
sending SNMP traps or indications.

DC8-037-2, Edition 11.2020
12.21 SNMP

dgpiCompliances dgpiCompliances
dgpiGroups dgpiProductIdenti-
tyGroup
dgpiProdCompGroup
dgpiNotifObjectsGroup
dgpiNotifNotifica-
tionsGroup
12.21.5 SNMP Variables
12.21.5.1 Introduction
The current state of the supported SNMP variables can be read out by the SNMP manager with the SNMP serv-
ices GET / GETNEXT / GETBULK. CP-8000/CP-802x supports the query of SNMP variables from different SNMP
managers with different IP addresses. The SNMP response is sent back to the SNMP manager from which the
SNMP request (GET / GETNEXT / GETBULK) was received.
SNMP variables of the following MIB files are supported:
• MIB-2 (RFC1213)
• sicamRTUs
• Ethernet-MIB (RFC3635)
• Host-Resources-MIB (RFC2790)
• USM-MIB (RFC2574)
• VACM-MIB (RFC2575)
• DGPI-MIB (Siemens Energy Management Digital Grid Product Inventory MIB)
12.21.5.2 SNMP Variables for MIB: sicamRTUs
General Information
GET NEXT / Response
TRAP
GETBULK / Response
<sicamRTUs.MIB>
GET / Response
SNMP address object identi- Data

fier (OID) Object description type
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.3.6.1.4.1.22638.7.1.1.1 Plant name 379 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 ✓ ✓
379 The shown value equals the parameter on M: AU common settings | Plant.

DC8-037-2, Edition 11.2020
12.21 SNMP
GET NEXT / Response
TRAP
GETBULK / Response
<sicamRTUs.MIB>
GET / Response
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 information – central ✓ ✓
error table
1.3.6.1.4.1.22638.7.10.1.1 Sum diagnosis table | Fault 1 “Class internal” Text ✓ ✓
1.3.6.1.4.1.22638.7.10.1.2 Sum diagnosis table | Fault 2 “Class external” Text ✓ ✓
1.3.6.1.4.1.22638.7.10.1.3 Sum diagnosis table | Fault 3 “Class communication” Text ✓ ✓
1.3.6.1.4.1.22638.7.10.1.4 Sum diagnosis table | Fault 4 “Class test” Text ✓ ✓
1.3.6.1.4.1.22638.7.10.1.5 Sum diagnosis table | Fault 5 “Class warning” Text ✓ ✓
1.3.6.1.4.1.22638.7.10.1.6 Sum diagnosis table | Fault 6 “Class module failure” Text ✓ ✓
1.3.6.1.4.1.22638.7.10.1.7 Sum diagnosis table | Fault 7 “Class failure” Text ✓ ✓
1.3.6.1.4.1.22638.7.10.1.8 Sum diagnosis table | Fault 8 “Class startup” Text ✓ ✓
1.3.6.1.4.1.22638.7.10.1.9 Sum diagnosis table | Fault 9 “Class parameter” Text ✓ ✓
1.3.6.1.4.1.22638.7.10.1.10 Sum diagnosis table | Fault 10 “Class configuration” Text ✓ ✓
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 ✓
NOTE
i All SNMP variables of the sicamRTUs.MIB can only be read via SNMP but not changed. SNMP variables can
not be read or changed with the SICAM TOOLBOX II. The central error table in SICAM RTUs is referred to as
the sum diagnostic table.
Example: SNMP GET for OID: 1.3.6.1.4.1.22638.7.10.1.1 Sum diagnosis table | Fault 1 „Class internal“

DC8-037-2, Edition 11.2020
12.21 SNMP
Example for firmware revision interrogation table (retrieved with ManageEngine MIB browser):
Traps
The following diagnostic information are sent spontaneously as SNMP Traps to the SNMP Manager:

DC8-037-2, Edition 11.2020
12.21 SNMP
GET NEXT / Response
TRAP
GETBULK / Response
<sicamRTUs.MIB>
GET / Response
1.3.6.1.4.1.22638.7.10.10 SICAM RTUs Traps
(formerly 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 - 10 Integer ✓
(These correspond to the error classes in the central
error table, see 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: Time when the trap occurred Date + ✓
Time
NOTE
i All SNMP variables of the sicamRTUs.MIB can only be read via SNMP but not changed.
SNMP variables can not be read or changed with the SICAM TOOLBOX II.
The following state information are sent spontaneously as SNMP Traps to the SNMP Manager:
GET NEXT / Response
TRAP
GETBULK / Response
<sicamRTUs.MIB>
GET / Response
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
Example: SNMP „TRAPs“

DC8-037-2, Edition 11.2020
12.21 SNMP
Example: SNMP „TRAP Details“
Traps History
The following status information "TRAP History" can be requested by the SNMP Manager:
GET NEXT / Response
TRAP
GETBULK / Response
<sicamRTUs.MIB>
GET / Response

1.3.6.1.4.1.22638.7.11.1 SNMP table with the last 50 traps sent ✓
NOTE
The following traps are entered in the TRAP history:

DC8-037-2, Edition 11.2020
12.21 SNMP
GET NEXT / Response
TRAP
GETBULK / Response
<sicamRTUs.MIB>
GET / Response
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” ✓
1.3.6.1.4.1.22638.7.10.1.2 Sum diagnosis table | Fault 2 “Class external” ✓
1.3.6.1.4.1.22638.7.10.1.3 Sum diagnosis table | Fault 3 “Class communication” ✓
1.3.6.1.4.1.22638.7.10.1.4 Sum diagnosis table | Fault 4 “Class test” ✓
1.3.6.1.4.1.22638.7.10.1.5 Sum diagnosis table | Fault 5 “Class warning” ✓
1.3.6.1.4.1.22638.7.10.1.6 Sum diagnosis table | Fault 6 “Class module failure” ✓
1.3.6.1.4.1.22638.7.10.1.7 Sum diagnosis table | Fault 7 “Class failure” ✓
1.3.6.1.4.1.22638.7.10.1.8 Sum diagnosis table | Fault 8 “Class startup” ✓
1.3.6.1.4.1.22638.7.10.1.9 Sum diagnosis table | Fault 8 “Class parameter” ✓
1.3.6.1.4.1.22638.7.10.1.10 Sum diagnosis table | Fault 8 “Class configuration” ✓
NOTE
Example: Interrogation of the SNMP "TRAP History"
Example: SNMP “TRAP History“ table

DC8-037-2, Edition 11.2020
12.21 SNMP
12.21.5.3 SNMP variables for MIB: dgpiMIB
Object group 1: dgpiProdIdentity

This collection contains the supplier name ("Siemens AG") and some customer-related information at the
product level, such as asset UUID (inventory number), customer name, product location, and geo-location.
These customer-related objects can only be read via SNMP. That is, they must be configured by the customer
in other ways (e.g., product-specific engineering tool, Web UI, etc.)
With the SICAM TOOLBOX II, this data can be entered with the following parameter:
Sub-Object group Objects Description / SICAM TOOLBOX II Parameter
- dgpiVendorName fix: "Siemens AG"
dgpiAssetUuid is generated by the device itself
dgpiCustomerName [BSE] System settings | Device settings |
Customer
dgpiLocationName [BSE] System settings | Device settings |
Device name
dgpiGeoPositionLatitude [BSE] System settings | Device settings |
Geographical position | Latidude
dgpiGeoPositionLongi- [BSE] System settings | Device settings |
tude Geographical position | Longitude
dgpiGeoPositionAltitude [BSE] System settings | Device settings |
Geographical position | Altitude
Object group 2: dgpiProdComp

This collection contains the product & component table (dgpiProductComponentsTable), which is the
most important object of the MIB. The product and its components are represented by lines in this table. The
first line is always occupied by the product, the following lines by the components. The order of the compo-
nents in the rows of this table is not mandatory.

DC8-037-2, Edition 11.2020
12.21 SNMP

dgpiProductComponent- dgpiProdCompIndex Index of the table line
sTable dgpiProdCompContai- Identifies the containment hierarchy of the product and
nedIn its components. It's zero in the product line because the
product is at the top of the hierarchy.
In the component rows, it corresponds to the value of
the object dgpiProdCompIndex of the product line (if
the component is directly from the product) or its
"parent" component row (if the component is contained
in a "parent" component).
dgpiProdCompClass identifies the class of the product or component of this
line
e.g.: hwProduct
dgpiProdCompName contains the name of the product or component
e.g.: SICAM A8000 CP-8050
dgpiProdCompDescrip- contains a brief description of the product or component
tion
dgpiProdCompOrder- contains the MLFB number of the product or component
Number e.g.: 6MF28050AA00
dgpiProdCompSerial- contains the serial number of the product or component
Number e.g.: BF1612034390
dgpiProdCompVersion contains the version number of the FW, HW, SW or the
configuration
dgpiProdCompHwSlot contains the number or name of the slot where the hard-
ware component is located
dgpiProdCompManu- contains the date of manufacture of the HW product or
factDate component
dgpiProdCompConfi- contains the last modification date and the last modifica-
gLastChange tion time of the updatable component
- dgpiProductCompTable- contains the date and time of the last change of each
LastChange dgpiProductComponentsTable object.
The change includes creation, removal and modification
of table rows.
This is in contrast to the dgpiProdCompLastChange
Change object, which refers to changing of rows, that
represent certain component classes.
Object group 3: dgpiNotifications

This group defines a notification (SNMPv2 trap) that will be sent when the dgprProductComponentsTable
has changed.
- dgpiNotificationsEna- enables/disables the sending of this notification
bled

DC8-037-2, Edition 11.2020
A Ordering Information
A.1 Basic Units 1842

A.2 Power Supply Modules 1843
A.3 SICAM I/O Modules 1844
A.4 SICAM TM I/O Modules 1847
A.5 Interface Modules 1851
A.6 Transmission Facilities 1852
A.7 Recommended Upstream Power Supply Devices 1855
A.8 Cables and Plugs 1856
A.9 Memory Cards 1859
A.10 IE RJ45 Port Lock 1860
A.11 Engineering Tools 1861

DC8-037-2, Edition 11.2020
Ordering Information
A.1 Basic Units
A.1 Basic Units

Designation MLFB
CP 8000 Master Module with I/O 6MF2101-0AB100AA0
Temperature range -25 bis +70°C
(equipped with an SD card)
CP 8000 Master Module with I/O 6MF2101-1AB100AA0

CP-8021 Master Module 6MF2802-1AA00

Note:
External power supply module required
CP-8022 Master Module with GPRS 6MF2802-2AA00

Note:
External power supply module required
Spare Part
Designation MLFB
CM-8812 Bus Connector SICAM I/O C53207-A5812-D481-3
Set with 10 pcs.
(the bus connector is included with CP 802x
modules)
Locking Hook SICAM A8000 3cm Module C53207-A5014-D481-1
Set with 10 pcs.
Locking Hook CP-8000 C53207-A520-D4-1

Set with 10 pcs.

DC8-037-2, Edition 11.2020
A.2 Power Supply Modules
A.2 Power Supply Modules

Designation MLFB NUMBER
PS-8620 power supply 6MF2862-0AA00
DC 24 to 60 V
Note:
Only for CP-8021 and CP-8022

DC 110 to 220 V
Note:

DC 24 to 60 V
Note:

DC 100 to 240 V/AC 100 to 240 V
Note:
Spare Part

CM-8812 Bus connector SICAM I/O C53207-A5812-D481-3
10x set
(this bus connector is part of PS-862x and PS-864x
modules)
10x set

DC8-037-2, Edition 11.2020
A.3 SICAM I/O Modules

DI-8110 Digital input 6MF2811-0AA00
2x8, DC 24 V

2x8, DC 48/60 V

2x8, DC 110 V

2x8, DC 220 V
DO-8212 Digital output 6MF2821-2AA00

8x DC 24 to 220 V/AC 230 V
AI-8310 Analog input 6MF2831-0AA00

2x2 Pt100/Pt1000

DC8-037-2, Edition 11.2020

4x ±20 mA/±10 V
AI-8510 analog input 6MF2851-0AA00

3x V (240 V), 3x I (LoPo)
Note:
CM-8820 is required for current measurement!

3x V (LoPo), 3x I (LoPo)
AO-8380 Analogue output 6MF2838-0AA00

4x ±20 mA/±10 V
Spare Part

CM-8812 Bus connector SICAM I/O C53207-A5812-D481-3
10x set
(a bus connector is part of all SICAM I/O modules)

10x set

DC8-037-2, Edition 11.2020
Accessories

CM-8811 coupling for SICAM I/O modules 6MF2881-1AA00
Note: Only for SICAM I/O modules on CP-8000
CM-8820 CT adapter for AI-8510 6MF2882-0AA00

3xI 1 A_5 A/225 mV
Note: for AI-8510 only
CM-8830 SICAM I/O modules for LED display 6MF2883-0AA00

DC8-037-2, Edition 11.2020
A.4 SICAM TM I/O Modules

DI-6100 Digital input 6MF1113-0GB00-0AA0
2x8, DC 24 to 60 V

2x8, DC 110/220 V

2x8, DC 24 to 60 V 1 ms

2x8, DC 110/220 V 1 ms

2x8, DC 220 V
DO-6200 Digital output for transistor 6MF1113-0GC00-0AA0

2x8, DC 24 to 60 V

DC8-037-2, Edition 11.2020

DO-6212 Digital output for relay 6MF1113-0GC12-0AA0
8x DC 24 to 220 V/AC 230 V
DO-6220 command output for base module 6MF1113-0GC20-0AA0
DO-6221 command output for base module meas- 6MF1113-0GC21-0AA0

urement
DO-6230 command output for relay module 6MF1113-0GC30-0AA0
AI-6300 Analog input 6MF1113-0GD00-0AA0

2x2 ±20 mA/±10 V

2x2 ±2.5 mA/±5 mA/±10 V

DC8-037-2, Edition 11.2020

2x2 ±1 mA/±2 mA/±10 V

2x2 Pt100/Ni100
AO-6380 Analog output 6MF1113-0GD80-0AA0

4x ±20 mA/±10 mA/±10 V
TE-6430 counter input 6MF1113-0GE30-0AA0

2x DC 24 to 60 V

DC8-037-2, Edition 11.2020
Accessories

CM-6811 coupling for SICAM TM I/O modules 6MF1113-0GJ11-0AA0
Note: only for SICAM TM I/O modules on CP-8000
CM-6812 coupling for SICAM TM I/O modules 6MF1113-0GJ12-0AA0

Note: only for SICAM TM I/O modules on CP-802x
Bus termination for TM housing 6MF1313-0GA50-0AA0

DC8-037-2, Edition 11.2020
A.5 Interface Modules
A.5 Interface Modules

Designation MLFB
CM-0819 Converter RS-232/RS-485, insulated 6MF1111-2AJ10-0AA0
CM-0821 Fieldbus Interface Ring (3x FO, 1x el.) 6MF1111-0AJ21-0AA0
CM-0822 Fieldbus Interface Star (4x FO) 6MF1111-0AJ22-0AA0
CM-0823 Fieldbus Interface Ring (3x FO,1x RS 485) 6MF1111-0AJ23-0AA0
CM-0829 Converter RS-232/RS-422; RS485 6MF1111-2AJ20-0AA0
CM-0847 Fiberoptic Interface (el.-FO) 6MF1113-0AJ47-0AA0

DC8-037-2, Edition 11.2020
A.6 Transmission Facilities

Designation MLFB
CE-0700 V.23 Leased Line Modem for DIN rail 6MF1102-0BC00-0AA0
installation, 400 mW
CE-0701 WT Channel Modem for DIN rail installa- 6MF1102-0CA81-0AA0

tion, 2,0 W
SCALANCE M874-2 GPRS Router 6GK5874-2AA00

for the wireless IP communication of Ethernet-
based automation devices via 2.5G mobile radio
VPN, firewall, NAT; 2-port switch
MD741-1 GPRS Router 6NH9741-1AA00
RUGGEDCOM RX1400 6ZB5531-0AL01

Ethernet switch and TCP/IP router
Siemens Converter LWE - RS232 7XV5652

DC8-037-2, Edition 11.2020
Designation MLFB
Siemens Mini Starcoupler 7XV5450
ANT 794-4MR Antenna LTE (4G), UMTS (3G), GSM 6NH9860-1AA00

(2G)
Incl. 5 m connection cable
(Antenna for integrated GPRS modem of CP-8022)
Recommended Third-Party Products
Designation
TP Radio WDM 8000
Multi-point traffic
SATELLINE 2ASxE
Multi-point traffic
Westermo TD-36AV
(AC 22 to 264 V/DC 18 to 300 V)
Westermo TD-36LV
(AC 10 to 30 V/DC 10 to 60 V)
Dial-up traffic analog
Westermo IDW-90
Dial-up traffic ISDN

DC8-037-2, Edition 11.2020
Designation
Cinterion MC52iT dualband modem
GSM 900/1800 MHz
incl. mounting set for DIN rail and connection
cable (1.5 m)
MC Technologies MC55iw quadband modem

GSM 850/900/1800/1900 MHz
Dr. Neuhaus Tainy EMOD-V2-IO

or
Dr. Neuhaus Tainy EMOD-L1-IO
REEL K70ZCR
GSM 850/900/1800/1900 MHz + UMTS + WLAN
2400 MHz
PHOENIX CONTACT PSM-ME-RS232/RS485-P Inter-

face converter
for converting RS-232 (V.24) to RS-422 (V.11) and
RS-485, with electrical isolation, 2 channels, rail-
mountable

DC8-037-2, Edition 11.2020
A.7 Recommended Upstream Power Supply Devices
A.7 Recommended Upstream Power Supply Devices

Designation
MTM Power HSA50 S24
AC 90 to 264 V or DC 120 to 340 V
Output DC 24 V, 2,1 A
SYKO EWS 01 U.06.05.20

AC 82 to 264 V
Output 5 V, 2 A
SYKO EWS 01 U.06.24.05

DC 36 to 350 V
Output 24 V, 0,5 A

DC8-037-2, Edition 11.2020
A.8 Cables and Plugs

Terminals for CP-8000
Designation Order number

SICAM A8000 CP-8000 terminal set C53207-A5838-D481-1
Terminals for CP-8021, CP-8022

Push-in terminal 8-pole (phoenixcontact.com)
DFMC 1,5/ 4-ST-3,5 1714514
Minimum order quantity:
50 pcs.
SICAM A8000 COM labels (4x48 pcs.) C53207-A5835-D481-1

Set with 48 pcs. each (X1, X2, X3, X6)

DC8-037-2, Edition 11.2020
Terminals for I/O Modules

Removable screw terminal 4-pole (phoenixcontact.com)
FRONT-MSTB-2,5/4-ST-5,08 1709836
50 pcs.
Removable screw terminal 10-pole (phoenixcontact.com)

FRONT-MSTB-2,5/10-ST-5,08 1709767
50 pcs.
SICAM A8000 I/O labels (4x48 pcs.) C53207-A5816-D481-1

Set with 48 pcs. each (X1, X2, X3, X4)
Ethernet Cables
Designation MLFB
Industrial Ethernet TP Cord RJ45/RJ45, 1m 6XV1870-3QH10
CAT 6A, TP cable 4x 2 (–25 to 80 °C 380), 2m 6XV1870-3QH20
length 1 to 10 m 3m 6XV1870-3QH30
4m 6XV1870-3QH40
6m 6XV1870-3QH60
10 m 6XV1870-3QN10
Industrial Ethernet TP XP Cord RJ45/RJ45, CAT 6A, 6XV1870-3RH10
crossed TP cable 4x 2 (–25 to 80 °C 381), length
1m
Industrial Ethernet TP Cord RJ45/RJ45, CAT 6A, 6XV1870-3QE50

crossed TP cable 4x 2 (–25 to 80 °C 382), length
0.5 m
380 -40 to 80 °C in fixed installation

381 -40 to 80 °C in fixed installation
382 –40 to 80 °C in fixed installation

DC8-037-2, Edition 11.2020
2-Line Arrangement for SICAM TM I/O Modules
Designation MLFB
CM-6810 TM I/O Modules extension cable 6MF1113-0GJ10-0AA0
Recommended Third-Party Products

Connection CM 8820 → AI 8510 (meinhart.at)
HSLCH FRNC (7x 0,75 mm²)
Connection CM 8820 → AI 8510 (lappkabel.de)

ÖLFLEX FD 855 CP (7 G 0,5 mm²)
D-Sub/RJ45 Adapter (female) (rs-online.com)

MHDA9-SMJ8-M-K 382-2695
D-Sub/RJ45 Adapter (male) (rs-online.com)

MHDA9-PMJ8-M-K 382-2689
FTDI Chip US232R-10 (rs-online.com)

with 10 cm cable 429-274
FTDI Chip US232R-100-BLK (rs-online.com)

with 1 m cable 687-7806

DC8-037-2, Edition 11.2020
A.9 Memory Cards
A.9 Memory Cards

Designation MLFB
SD Card 512 MB 6MF1213-2GA05-0AA0
Temperature range -40°C to 70°C (spare part)
SD Card 2 GB 6MF1213-1GA05-0AA0
Temperature range -25°C to70°C (spare part)

DC8-037-2, Edition 11.2020
A.10 IE RJ45 Port Lock
A.10 IE RJ45 Port Lock

Designation MLFB
RJ45 Port Lock 6GK1901-1BB50-0AA0
Port lock with key for mechanical closing of RJ45
ports
1 pack = 1 piece

DC8-037-2, Edition 11.2020
A.11 Engineering Tools
A.11 Engineering Tools

SICAM TOOLBOX II
NOTE
i Please note that CP-8000/CP-802x is supported by the SICAM TOOLBOX II as of version 6.01.
Designation Item number

SICAM TOOLBOX II V6 License Catalog, License D30-013-6
Ordering
SICAM TOOLBOX II S38-100
The SICAM TOOLBOX II is supplied on an USB stick. For the usage of the single tools software licenses are
required.
You find the exact order information in the document SICAM TOOLBOX II V6 License Catalog, License
Ordering.
SICAM WEB

SWEB00 SCD-001-1
Sicam_first_startup SC8-900-1
SICAM Device Manager

SICAM Device Manager S51-000

DC8-037-2, Edition 11.2020
DC8-037-2, Edition 11.2020
B Examples of Instruction Lists (IL)
B.1 Transfer an Input to a Signalling Output and to a Command Output 1864

B.2 Combine 2 Inputs with AND 1865
B.3 Linear Adaptation with Value Selection 1866
B.4 Operating Hours Counter 1867
B.5 Bounce Suppression 1869
B.6 Setpoint Command 1871
B.7 Speed Comparison 1872

DC8-037-2, Edition 11.2020
Examples of Instruction Lists (IL)
B.1 Transfer an Input to a Signalling Output and to a Command Output
B.1 Transfer an Input to a Signalling Output and to a Command Output

The first digital input of the Master Module (with default address and type identification is loaded into the
accumulator. In the next lines the loaded value is transferred to a single-point information output and to a
command output.
Changing the input type from “single command” to “single-point information” with the engineering tool, the
relay at the output D00 picks up when the input is logical “1”. Otherwise, this output address will be sent to
the communication because it is not existing within the periphery. The address of the command is preset so
that the command is output on output D01.
PLC_RESET:
PLC_INIT:
PLC_START:
LD I_030_002_000_000.VALUE (*IN00 TI:30 IOA1:002 IOA2:000 IOA3:000*)

ST O_030_008_000_000.VALUE (*store at output as binary information*)
ST O_045_009_000_000.VALUE (*store at output as command*)

DC8-037-2, Edition 11.2020
B.2 Combine 2 Inputs with AND
B.2 Combine 2 Inputs with AND

The cycle time is set to 50 ms. The first 2 inputs of the Master module are linked with a logical AND. The result
is transferred to a flag and additional to a digital output. The type identification of the output is single
message.
PLC_RESET:
LD 50 (*load value 50*)
ST PLC_CYCLETIME (*store at system variable in ms*)
PLC_INIT:
PLC_START:
LD I_030_002_000_000.VALUE (*read input IN00*)
ST AND.IN0 (*store on input 0 for AND function*)
LD I_030_003_000_000.VALUE (*read input IN01*)
ST AND.IN1 (*store on input 1 for AND function*)
CAL AND (*call AND function*)
ST M_BOOL_TESTFLAG (*store on a flag*)
ST O_030_008_000_000.VALUE (*store as single command output*)

DC8-037-2, Edition 11.2020
B.3 Linear Adaptation with Value Selection
B.3 Linear Adaptation with Value Selection

Two analog values are compared and the higher one is selected (MAX). With this one an adaptation kx+d is
performed. The processed value receives a new address (O_036_032_001_001.VALUE). The constants for k
(M_REAL_CONSTANTforK) and d (M_REAL_CONSTANTforD) are defined with initial values in the programm
sequence PLC_INIT.
PLC_RESET:
PLC_INIT:
LD 10
ST M_REAL_CONSTANTforK (*constant for k*)
LD -5
ST M_REAL_CONSTANTforD (*constant for d*)
PLC_START:
LD I_036_032_000_000.VALUE (*input 1*)
ST MAX.IN0
LD I_036_033_000_000.VALUE (*input 2*)
ST MAX.IN1
CAL MAX (*the greater value of both is used*)
ST M_REAL_MAXVALUE (*serves for reading which value will*)
ST MUL.IN0 (*be used*)
LD M_REAL_CONSTANTforK
ST MUL.IN1
CAL MUL (*the selected value is multiplicated*)
ST ADD.IN0 (*with the constant and results as "kx"*)
LD M_REAL_CONSTANTforD
ST ADD.IN1
CAL ADD (*after the multiplication add "d"*)
ST O_036_032_001_001.VALUE (*selected adapted value*)

DC8-037-2, Edition 11.2020
B.4 Operating Hours Counter

The current seconds value of the system time of CP-8000/CP-802x is loaded. A positive edge is generated at
the zero second and switched to the CU input of an up counter. Thereby, the counter score is incremented by
1 per minute.
The sum of the operating hours results of two values:
• Current counter score (CTU_COUNTER.CV)
• Counter score before the last power down (MR_DINT_MINUTES)

The score will be saved in a retaining flag (M_DINT_MINUTESOLD). This means, after a power down
(startup) the counter will continue with incrementing based on the last value.
The hours result by minutes devided by 60. The hours always will be recalculated based on the minutes, the
same after a power down.
PLC_RESET:
LD 10 (*load Value 10*)
PLC_INIT:
LD MR_DINT_MINUTES (*load power-fail safe value*)
ST M_DINT_MINUTESOLD (*freeze in a flag as old value*)
PLC_START: (*Operating hours counter*)

LD PLC_SYSTIME.SEC (*fetch second value of the system time*)
ST M_DINT_SEC (*and store in variable*)
LD M_DINT_SEC (*current second*)
EQ 0 (*compare with second 0*)
ST CTU_COUNTER.CU (*HIGH always at the second 0, required*)
(*edge detection is implemented within the counter*)
CAL CTU_COUNTER (*increments the counter*)
LD CTU_COUNTER.CV (*load current counter score*)
LD M_DINT_MINUTESOLD (*load old value*)
CAL ADD (*call ADD function*)
ST MR_DINT_MINUTES (*store sum of operating minutes in a retaining flag,*)
(*after startup the old value will be added to the*)
(*current counter score*)
LD 60 (*load constant for 60 minutes*)
CAL DIV (*call DIV function*)
ST M_DINT_HOURS (*sum of operating hours*)
(*= minutes divided by 60*)
To reset the counter score it is necessary to reset the counter (CTU_COUNTER.R) as well asthe flag with the
retained value (M_DINT_MINUTESOLD).
This could be executed by a subroutine (before PLC_RESET). With RET the subroutine will be left.
(*SUBROUTINE*)
ResetCounter:
LD 0
ST M_DINT_MINUTESOLD (*the old value for operating minutes is set to "0"*)
ST M_BOOL_RESET (*reset the flag for running this subroutine*)
LD 1

DC8-037-2, Edition 11.2020
ST CTU_COUNTER.R (*reset counter by input R*)

RET
(*END SUBROUTINE*)
The call of the subroutine could be executed at the end (after ST M_DINT_HOURS). Therefore the flag
(M_BOOL_RESET) must be set to 1. Instead of the flag an input address could be used, for instance a
command.
Reaching the command CALC the call of the subroutine will be executed. In the subroutine the flag
(M_BOOL_RESET) will be reset to 0, otherwise the counter would last at 0 as long as the flag will be reset to 0.
LD 0 (*besides reset of the time*)

ST CTU_COUNTER.R (*the counter input R is set to "0"*)
LD M_BOOL_RESET (*if the flag is set to "1"*)

CALC ResetCounter (*call the subroutine ResetCounter*)

DC8-037-2, Edition 11.2020
B.5 Bounce Suppression

If an input signal is bouncing, the blocked bit (BL) is set. The number of state changes until the BL bit is set, as
well as the monitoring time during which the information must be static until the BL bit is reset, are adjustable
via constants. An output is set to 0 during the BL bit is set.
With an edge detection for the rising edge (R_TRIG_INEDRISE0) and the falling edge (F_TRIG_INEDFALL0) the
counter (CTU_EDC0) will be incremented by 1. At the same time the R input of the counter is reset via an ON
delay for the rising edge (TON_EDTIMERISE0) as well as for the falling edge (TON_EDTIMEFALL0). With this
function all state changes of the input will be integrated by the counter (started with the first edge and trig-
gered by each following one).
As soon as a state change of the input happens the flag (M_BOOL_COUNTER00) is reset and the input of an
AND (module 8) is set (inverted). If the sum of state changes is greater as or equal to a defined number
(CV>=PV) the counter output is set as well, and the BL bit is set. With the set BL bit the output is reset by
another AND (module 9).
After termination of the monitoring time the R input of the counter is set again, and the counter is reset. If the
BL bit is set, it will be reset as well (output of module 8 is 0).
In the procession sequence the R input of the counter must be reset first, because only afterwards the positive
edge at the CU input of the counter causes an increment. Therefore the application program handles the R
input before the CU input of the counter.
Example:
Number of state changes ≥5
Monitoring time of the stability of the input = 10 s
PLC_RESET:
LD 20 (*load Value 20*)
PLC_INIT:
LD 5 (*number of transients until*)
ST CTU_EDC0.PV (*information is set bouncing*)
(*once detected as bouncing, the input signal must last statical "1" for a

DC8-037-2, Edition 11.2020
preset time until the blocked bit will be reset again*)

LD 10000 (*load constant for 10s*)
ST TON_EDTIMERISE0.PT (*ON delay rising edge*)
ST TON_EDTIMEFALL0.PT (*ON delay falling edge*)
PLC_START:
(*Modules 4,5,6,7 – if there are no more state changes of the input, the
counter will be reset when the preset monitoring time has expired*)
LD I_030_002_000_000.VALUE (*input*)
ST M_BOOL_INPUT00
ST TON_EDTIMERISE0.IN (*rising edge - module 4*)
STN TON_EDTIMEFALL0.IN (*falling edge - module 5*)
CAL TON_EDTIMERISE0 (*call module 4*)
ST OR.IN0
CAL TON_EDTIMEFALL0 (*call module 5*)
ST OR.IN1
CAL OR (*call module 6*)
ST M_BOOL_COUNTER00 (*also in graphic*)
ST CTU_EDC0.R (*reset input of counter - module 7*)
(*Modules 1,2,3,7 – rising and falling edge of the input are combined with an
OR and put to the CU input of the counter – each change will be added*)
LD M_BOOL_INPUT00
ST R_TRIG_INEDRISE0.CLK (*rising edge - module 1*)
ST F_TRIG_INEDFALL0.CLK (*falling edge - module 2*)
CAL R_TRIG_INEDRISE0 (*call module 1*)
ST OR.IN0
CAL F_TRIG_INEDFALL0 (*call module 2*)
ST OR.IN1
CAL OR (*call module 3*)
ST CTU_EDC0.CU (*count up input of counter - module 7)
ST M_BOOL_MODULE3 (*only for graphic*)
(*Modules 7,8 – with the first edge change the monitoring time will be started.
If the number of edges is greater then the number of transients within this
time, the output of the AND (module 8) is set = blocked*)
CAL CTU_EDC0 (*call module 7*)
ST M_BOOL_MODULE7 (*only for graphic*)
ST AND.IN0
LDN M_BOOL_COUNTER00
ST AND.IN1
CAL AND (*call module 8*)
ST M_BOOL_BOUNCING00 (*is "1" if the input is bouncing*)
ST O_030_002_000_000.BL (*set blocked bit of the input*)
(*Module 9 - the output is reset during the input is detected as bouncing*)

LD M_BOOL_INPUT00
ST AND.IN0
LD M_BOOL_BOUNCING00
STN AND.IN1
CAL AND (*call module 9 – if bouncing, then "0"*)
ST O_030_002_000_000.VALUE (*output of input information*)

DC8-037-2, Edition 11.2020
B.6 Setpoint Command
B.6 Setpoint Command

PLC_RESET:
PLC_INIT:
PLC_START:
(*Mapping inputs to flags*)
LD I_050_171_105_000.S_E (*setpoint command select/execute*)

ST M_BOOL_NBVCmL45
LD I_030_008_004_000.VALUE (*single-point information input*)
ST M_BOOL_OmkHandL45
LD I_036_018_039_000.VALUE (*measured value float input*)
ST M_REAL_CmL45
LD I_050_171_105_000.VALUE (*setpoint command float input*)
ST M_REAL_BvCmL45DC
(*Temporary test variables*)
LD I_050_171_105_000.S (*check for a rising edge, otherwise*)

ST R_TRIG_EDRISE1.CLK (*create a confirmation each cycle*)
CAL R_TRIG_EDRISE1 (*if no setpoint is present, the logic*)
JMPN HOPP90 (*will jump over the COT procedure*)
LD I_050_171_105_000.S_E (*setpoint command select/execute*)

ST O_050_171_105_000.S_E (*here you have to add the select*)
(*before execute procedure*)
ST M_BOOL_NBVCmL45
LD I_050_171_105_000.VALUE
ST O_050_171_105_000.VALUE (*setpoint command float output*)
ST M_REAL_BvCmL45DC
(*Example for select before execute*)
LD 7 (*7 = confirmation, 10 = termination*)

ST O_050_171_105_000.COT (*set to 0 would create the confirmation here,*)
(*and the termination in the following cycle*)
LD 1
ST O_050_171_105_000.S (*setpoint command spontaneous*)
HOPP90:

DC8-037-2, Edition 11.2020
B.7 Speed Comparison

PLC_RESET:
PLC_INIT:
LD 1000 (*drop off delay in ms*)
ST TOF_EDCHNGRISE0.PT
ST TOF_EDCHNGFALL0.PT
PLC_START:
(*Check speed value on change*)
LD I_034_016_000_000.S (*load spontaneous bit speed value*)
JMPN NO_CHANGE (*jump if no change of value*)
(*Change of speed value present*)

LD I_034_016_000_000.VALUE (*load speed value*)
ST M_REAL_VALUENEW (*current speed value to flag*)
ST SUB.IN0
LD M_REAL_VALUEOLD (*load old speed value*)
ST SUB.IN1
CAL SUB (*form difference value*)
ST M_REAL_VALUEDIF (*difference value to flag*)
(*Take over change of value*)

LD M_REAL_VALUENEW (*load current value*)
ST M_REAL_VALUEOLD (*save current value for next change of value*)
(*Value comparison speed ascending*)

LD M_REAL_VALUEDIF (*load diff. value*)
ST GT.IN0
LD 0
ST GT.IN1
CAL GT (*diff. value > 0: speed ascending*)
ST M_BOOL_SPAS (*set flag speed ascending*)
(*Value comparison speed descending*)

LD M_REAL_VALUEDIF (*load diff. value*)
ST LT.IN0
LD 0
ST LT.IN1
CAL LT (*diff. value < 0: speed descending*)
ST M_BOOL_SPDE (*set flag speed descending*)
NO_CHANGE: (*jump mark if no change of value*)
(*Drop-off delay speed ascending*)

LD M_BOOL_SPAS (*load flag speed ascending*)
ST TOF_EDCHNGRISE0.IN
CAL TOF_EDCHNGRISE0 (*drop-off delay*)
LD TOF_EDCHNGRISE0.Q
ST O_030_048_000_000.VALUE (*reset output*)
(*Drop-off delay speed descending*)

LD M_BOOL_SPDE (*load flag speed descending*)
ST TOF_EDCHNGFALL0.IN
CAL TOF_EDCHNGFALL0 (*drop-off delay*)

DC8-037-2, Edition 11.2020
LD TOF_EDCHNGFALL0.Q
ST O_030_049_000_000.VALUE (*set binary output*)
(*Reset flags for speed ascending, descending*)

LD 0
ST M_BOOL_SPAS (*reset flag speed ascending*)
ST M_BOOL_SPDE (*reset flag speed descending*)

DC8-037-2, Edition 11.2020
DC8-037-2, Edition 11.2020
C Error Handling
C.1 Errors with the Engineering via SICAM WEB 1876

DC8-037-2, Edition 11.2020
Error Handling
C.1 Errors with the Engineering via SICAM WEB

The following table shows a variety of possible operating errors which can occur with engineering via SICAM
WEB. It does not lay claim to completeness, since depending on the used connection, system configuration
and web browser different conditions can occur.
There is also no warranty that the described remedies really always lead to the desired goal.
Characteristic Possible cause Remedy
After entry of the IP address of a • There is no connection to the • Anew call of the IP address in
target device in the web browser selected target device the web browser resp.
the indication "web page not avail- “Refresh”
able"
• Target device is switched off
• IP address is wrong • Check whether target device
is switched on and connected
with the PC
• With operation via Ethernet
and without router the
network addresses of the
target device and PC must fit
(dependent on the subnet
mask)
After an update in the web browser • The session was already termi- • Avoid extended pauses (> 15
(by selection of a menu or by nated by means of the min) during the operation or
transfer of a parameter) the logon internal watchdog parameterization procedure
page appears
• The session was terminated by • Store changed parameters by
means of logon by another clicking on the apply button
user
After loading of an IL the web • The IL to be loaded is too large • Cancel loading process (stop
browser tries to refresh over long function in the web browser)
time (> 1 min) or no return infor-
• Generally a loading process
mation from the loading process

takes longer the larger the IL • Check whether errors are
is recorded in the Diagnosis
occurs at all
• Load a smaller IL
• When the target device
responds after the loading
process, check whether the IL
is applied
After loading of an IL web pages • An invalid IL has been loaded • Read error display in the diag-
are faulty or empty; possibly the nosis
red ER LED is lighting
• During the transmission a
connection fault may have • Check whether the correct
been occurred source file is loaded
• Check whether the file which
contains the IL is a text file
(ASCII format)
• Check whether the correct
control code is in the text file
After startup of the system the There is a syntax error • Check whether errors are
application program remains recorded in the Diagnosis
stopped
• Correct the IL in the indicated
line number

DC8-037-2, Edition 11.2020
Error Handling
Characteristic Possible cause Remedy

After loading of an IL no automatic • An invalid program code • Follow error indication
restart is requested (wrong file or file format) has
been loaded
• Evaluate diagnosis
• A connection fault may be

occurred during the transmis-
sion
After loading of the parameters the • In the loaded parameteriza- • Set again a valid IP address
target device can be selected no tion an invalid or unknown IP with Sicam_first_startup on
longer from the web browser; address is set the target device; enter this
possibly the red ER LED is lighting address after successful trans-
• An invalid parameter file has
mission in the web browser to
been loaded
get access to the target device
• During the transmission a
• Otherwise detach the SD card
connection fault may have
from the target device and
been occurred
overwrite it again with valid
parameters offline
After loading of a firmware the Firmware code not loaded/config- • Start a new loading process
loaded firmware revision does not ured completely due to communi-
appear in the configuration page cation fault or operating error (e.g.
• Observe progress display
menu was quitted prematurely) • Loading process is completed

correctly when the indication
UPLOAD SUCCESSFUL
appears, with hyperlink to the
target device

DC8-037-2, Edition 11.2020
DC8-037-2, Edition 11.2020
D Setting Up a Dial-Up Connection
D.1 Settings in Microsoft Windows 8 1880

D.2 Settings in Microsoft Windows 7 1890
D.3 Settings in Microsoft Windows Vista 1899
D.4 Restore the Settings for Using the Internet 1908

DC8-037-2, Edition 11.2020
Setting Up a Dial-Up Connection
D.1 Settings in Microsoft Windows 8

Modem installation
Select the control panel item from the start menu
Open the modem-group by double-clicking the “Phone and Modem Options” symbol. If you need to input loca-
tion information, enter any number combination and click OK.
[sc_control_panel_modem_add, 1, en_US]
Figure D-1 Adjusting Phone and Modem Options
Click the Modems index tab and click Add... to install the modem.
[sc_modem_add, 1, en_US]
Figure D-2 Adding a Modem
The Hardware Wizard starts, which guides you comfortably through the installation. Tick the Select modem
(no automatic detection) check box and click Next >.

DC8-037-2, Edition 11.2020
Under Manufacturers, select (Standard Modem Types), and under Models, select Standard 33600bps
Modem, then click Next >.
[sc_hardware_assistent_a, 1, en_US]
Figure D-3 Selecting a Modem
Mark the required interface in this window and confirm the input by pressing NEXT >. Complete the modem
installation in the next window by clicking the Finish button.
[sc_hardware_assistent_b, 1, en_US]
Figure D-4 Readying the Modem

DC8-037-2, Edition 11.2020
Now, in the Modems tab, select the Properties button and check how the Max. Transmission rate of
115200 is shown in the bottom window. If this setting shows another value, please correct it and confirm by
pressing OK.
[sc_phone_modem_properties, 1, en_US]
Figure D-5 Setting the Modem Properties
The modem installation is now complete!
Network Configuration
Select the control panel item via the start menu to establish a new remote data transmission connection.
Double-click on the symbol “Network and release center”.
[sc_control_panel_network_link, 1, en_US]
Figure D-6 Network and Release Center

DC8-037-2, Edition 11.2020
Click Set up new connection or network.
[sc_network_sharing_center_setup, 1, en_US]
Figure D-7 Setting up a New Connection
Select the Connect to the Internet item as a network connection type in the following window. Continue by
pressing Next >.
[sc_connection_with_internet, 1, en_US]
Figure D-8 Connecting to the Internet (1)

DC8-037-2, Edition 11.2020
If there is already an Internet connection available, this window appears:
[sc_connection_with_internet_anyway, 1, en_US]
Figure D-9 Connecting to the Internet (2)
Select Still set up a new connection, and continue.

Now you need to select the connection type. Please click on dialing connection and continue.
[sc_dial_up_connection, 1, en_US]
Figure D-10 Selecting the Dialing Connection

DC8-037-2, Edition 11.2020
Next, input any designation for the Connection name and any numerical value in the Dialing phone
number field. You also need to input your user name and Password here When you have carried out the
steps, confirm by pressing Next > in each case.
[sc_isp_parameters, 1, en_US]
Figure D-11 Entering the Connection Parameters
Pay attention to the ticks in the check boxes. Finally, click on Connect.
A window then appears with the connection test, you can cancel it.
Finally, click Close.
[sc_connection_with_internet_dial, 1, en_US]
Figure D-12 Closing the Connection Test
Now click the networks button in the taskbar notification area.
[sc_connections_icon_taskbar, 1, en_US]
Figure D-13 Displaying the Networks via the Taskbar

DC8-037-2, Edition 11.2020
Now an overviews of all available networks opens. To do this, choose the new dialing connection and click
Connect.
[sc_program_manager, 1, en_US]
Figure D-14 Displaying the Available Networks
In the “Connect with ...” window, click the Properties button.
[sc_connection_properties, 1, en_US]
Figure D-15 Selecting the Connection Properties

DC8-037-2, Edition 11.2020
Check the settings and correct them, if required. Confirm with OK.
[sc_connection_properties_modem_config, 1, en_US]
Figure D-16 Connection Properties - Modem Configuration
Now select the Network tab.

Mark the Internet protocol version 4 (TCP/IPv4) line, and then click Properties.
The Get IP address automatically and Get DNS server address automatically items must be selected in this
window. Continue by pressing Advanced.....
[sc_tcp_ip_settings, 1, en_US]
Figure D-17 Connection Properties - TCP/IP Settings

DC8-037-2, Edition 11.2020
In the last settings window under the“ IP settings” tab, the Use default gateway for remote network check
box may not be ticked. Confirm your inputs by pressing OK in each case.
[sc_ip_settings, 1, en_US]
Figure D-18 Connection Properties - IP Settings
Now click on the networks button in the taskbar notification area.
[sc_connections_icon_taskbar, 1, en_US]
Now an overviews of all available networks opens. To do this, click on the new connection and click Connect.
[sc_program_manager, 1, en_US]

DC8-037-2, Edition 11.2020
In the “Connect with ...” window, click the Choose button.
[sc_connection_dial, 1, en_US]
Figure D-21 Selecting the Connection Created
The installation and configuration is thereby complete!

DC8-037-2, Edition 11.2020

Modem installation
Open the modem group by double-clicking on the “Phone and Modem” symbol. Click the Modems index tab
and click Add... to install the modem.
[sc_control_panel_modem_add, 1, en_US]
The Hardware Wizard starts, which guides you comfortably through the installation. Tick the “Select modem
(no automatic detection”) check box and click Next >.
Under Manufacturers, select (Standard Modem Types), and under Models, select Standard 33600bps
Modem, then click Next >.
[sc_hardware_assistent_a, 1, en_US]
Figure D-23 Selecting a Modem

DC8-037-2, Edition 11.2020
Mark the required interface in this window and confirm the input by pressing NEXT >. Complete the modem
installation in the next window by clicking the Finish button.
[sc_hardware_assistent_b, 1, en_US]
Figure D-24 Readying the Modem
Now, in the Modems tab, select the Properties button and check how the Max. Transmission rate of
115200 is shown in the bottom window. If this setting shows another value, please correct it and confirm by
pressing OK.
[sc_phone_modem_properties, 1, en_US]
Figure D-25 Setting the Modem Properties
The modem installation is now complete!

DC8-037-2, Edition 11.2020
Network Configuration
Select the control panel item via the start menu to establish a new remote data transmission connection.
Double-click on the “Network and release center” symbol.
[sc_control_panel_network_link, 1, en_US]
Figure D-26 Network and Release Center
Click Set up new connection or network.
[sc_network_sharing_center_setup, 1, en_US]
Figure D-27 Setting up a New Connection

DC8-037-2, Edition 11.2020
Select the Connect to the Internet item as a network connection type in the following window. Continue by
pressing Next >.
[sc_connection_with_internet, 1, en_US]
Figure D-28 Connecting to the Internet
Now you need to select the connection type. Please click on dialing connection and continue.
[sc_dial_up_connection, 1, en_US]
Figure D-29 Selecting the Dialing Connection

DC8-037-2, Edition 11.2020
Next, input any Connection name and any numerical value in the Dialing phone number field. You also
need to input your user name and Password here When you have carried out the steps, confirm by pressing
Next > in each case.
[sc_isp_parameters, 1, en_US]
Figure D-30 Entering the Connection Parameters
Pay attention to the ticks in the check boxes. Finally, click on Connect.
A window then appears with the connection test, you can cancel it.
Then please select Still use a connection.
[sc_connection_test_cancel, 1, en_US]
Figure D-31 Closing the Connection Test

DC8-037-2, Edition 11.2020
Finally, click Close.
[sc_connection_ready, 1, en_US]
Figure D-32 Connection Ready
Now click the networks button in the taskbar notification area.
[sc_connections_icon_taskbar, 1, --_--]
Now an overviews of all available networks opens. To do this, choose the new dialing connection and right-
click Properties.
[sc_connections_display, 1, en_US]

DC8-037-2, Edition 11.2020
Check the settings and correct them, if required. Confirm with OK.
[sc_connection_properties_modem_config, 1, en_US]
Figure D-35 Connection Properties - Modem Configuration
Mark the Internet protocol version 4 (TCP/IPv4) line, and then click Properties. In this window the items
Obtain an IP address automatically and Obtain DNS server address automatically must be selected.
Continue by pressing Advanced.....
[sc_tcp_ip_settings, 1, en_US]
Figure D-36 Connection Properties - TCP/IP Settings

DC8-037-2, Edition 11.2020
In the last settings window under the IP settings tab, the Use default gateway for remote network check
box may not be ticked. Confirm your inputs by pressing OK in each case.
[sc_ip_settings, 1, en_US]
Figure D-37 Connection Properties - IP Settings
To establish a connection, click the networks button again in the taskbar notification area.
[sc_connections_icon_taskbar, 1, --_--]
Now an overviews of all available networks opens. To do this, choose the new dialing connection and click
Connect.
[sc_connections_display, 1, en_US]

DC8-037-2, Edition 11.2020
In the “Connect with ...” window, click the Choose button.
[sc_connection_dial, 1, en_US]
Figure D-40 Selecting the Connection Created
The installation and configuration is now complete.

DC8-037-2, Edition 11.2020
D.3 Settings in Microsoft Windows Vista
D.3 Settings in Microsoft Windows Vista

Modem installation
Open the modem-group with a double-click on the symbol “Phone and Modem Options”. Click the Modems
index tab and click Add... to install the modem.
[sc_phone_modem_options, 1, en_US]
The Hardware Wizard starts, which guides you comfortably through the installation. Tick the Select modem
(no automatic detection) check box and click Next >.
Under Manufacturers, select (Standard Modem Types), and under Models, s

Manual CP-8000 CP-802x ENG DC8-037-2.06

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

Manual CP-8000 CP-802x ENG DC8-037-2.06

Uploaded by

Copyright:

Available Formats

Preface

Open Source Software

SICAM A8000 Series General Information 1

Disclaimer of Liability Copyright

Purpose of the Manual

This manual describes the features and functions of following products:

SICAM A8000 Series, CP-8000, CP-8021, CP-8022, Manual 3

• EN 60870-2-1:1996 for 2014/30/EU

FCC Conformity Information

4 SICAM A8000 Series, CP-8000, CP-8021, CP-8022, Manual

• Reorient or relocate the receiving antenna.

• Increase the separation between the equipment and receiver.

• Consult the dealer or an experienced radio/TV technician for help.

• Reorient or relocate the receiving antenna.

• Increase the separation between the equipment and receiver.

• Consult the dealer or an experienced radio/TV technician for help.

This product is UL-certified based on the Technical data:

For further information see UL database in the internet: http://ul.com.

SICAM A8000 Series, CP-8000, CP-8021, CP-8022, Manual 5

i The UL approval does not apply to CP-8000.

Customer Support Center

6 SICAM A8000 Series, CP-8000, CP-8021, CP-8022, Manual

Qualified Electrical Engineering Personnel

• Proper storage, setup and installation

• Proper operation and maintenance

Selection of Used Symbols on the Device

Nr. Symbol Description

1 Direct current, IEC 60417, 5031

2 Alternating current, IEC 60417, 5032

3 Direct and alternating current, IEC 60417, 5033

4 Earth (ground) terminal, IEC 60417, 5017

SICAM A8000 Series, CP-8000, CP-8021, CP-8022, Manual 7

Nr. Symbol Description

5 Protective conductor terminal, IEC 60417, 5019

6 Caution, risk of electric shock

7 Caution, risk of danger, ISO 7000, 0434

8 Protective Insulation, IEC 60417, 5172, Safety Class II devices

9 Guideline 2002/96/EC for electrical and electronic devices

10 Guideline for the Eurasian Market

8 SICAM A8000 Series, CP-8000, CP-8021, CP-8022, Manual

SICAM A8000 Series, CP-8000, CP-8021, CP-8022, Manual 9

Open Source Software..................................................................................................................................9

SICAM A8000 Series, CP-8000, CP-8021, CP-8022, Manual 11

12 SICAM A8000 Series, CP-8000, CP-8021, CP-8022, Manual

4.4 Electromagnetic Compatibility...........................................................................................85

5 System Components and Technical Data................................................................................................... 93

SICAM A8000 Series, CP-8000, CP-8021, CP-8022, Manual 13

5.4.3.3 Technical Data..................................................................................................... 130

14 SICAM A8000 Series, CP-8000, CP-8021, CP-8022, Manual

5.4.12.3 Technical Data..................................................................................................... 195

6 Installation and Circuitry.......................................................................................................................... 219

SICAM A8000 Series, CP-8000, CP-8021, CP-8022, Manual 15

6.2.3 CP-802x Front and Side View..................................................................................... 228

16 SICAM A8000 Series, CP-8000, CP-8021, CP-8022, Manual

6.9 Setup of External Communication Connections............................................................... 261

SICAM A8000 Series, CP-8000, CP-8021, CP-8022, Manual 17

8 Engineering via SICAM TOOLBOX II..........................................................................................................337

9 Engineering via SICAM WEB..................................................................................................................... 363

18 SICAM A8000 Series, CP-8000, CP-8021, CP-8022, Manual

9.1.2.5 Security Settings for Internet Security (IPSec)........................................................379

SICAM A8000 Series, CP-8000, CP-8021, CP-8022, Manual 19

9.3.2 Download Device Settings......................................................................................... 510

10 Engineering via SICAM Device Manager.................................................................................................. 529