______________________________________________________________________________
Preface, Table of Contents
______________________________________________________________________________
Application and General Description
1
2
3
4
5
A
______________________________________________________________________________
SICAM 1703
Architecture and Data Flow
______________________________________________________________________________
System Services
Common Functions
______________________________________________________________________________
Telecontrol
System- and Basic System Elements
______________________________________________________________________________
Automation
______________________________________________________________________________
Message Formats
______________________________________________________________________________
DC0-015-2.02
Hint
Please observe Notes and Warnings for your own safety in the Preface.
Disclaimer of Liability
Although we have carefully checked the contents of this publication
for conformity with the hardware and software described, we cannot
guarantee complete conformity since errors cannot be excluded.
The information provided in this manual is checked at regular
intervals and any corrections that might become necessary are
included in the next releases. Any suggestions for improvement are
welcome.
Copyright
Copyright © Siemens AG 2011
The reproduction, transmission or use of this document or its
contents is not permitted without express written authority.
Offenders will be liable for damages. All rights, including rights
created by patent grant or registration of a utility model or design,
are reserved.
Subject to change without prior notice.
Document label:
SIC1703-HBGFSYSBSEACP-ENG_V2.02
Release date:
04.02.2011
Siemens Aktiengesellschaft
Order Nr.: DC0-015-2.02
Preface
This document is applicable to the following product(s):
•
ACP 1703
Purpose of this manual
This manual describes the function and mode of operation of system element-overlapping
services and basic system elements, that are supported on the platform ACP 1703.
It is intended for users of the target group stated below.
Target Group and Safety Instructions
The document you are reading right now is addressed to users, who are in charge of the
following engineering tasks:
•
Conceptual activities, as for example design and configuration
•
System parameterization and system diagnostic, using the designated engineering tools
•
Technical system maintenance
Above applies, as far as these tasks do not involve manipulations of the hardware.
Manipulating the hardware itself, as for example "unplugging" and "plugging" printed circuit
boards and modules, or working on terminals and/or connectors – for instance when applying
changes to the wiring – are – also if they are an issue in the context of configuration,
parameterization and diagnostic – not subject of this document.
For activities, which comprise hardware manipulations, it is essential to pay attention to the appropriate
safety instructions and to strictly adhere to the appropriate safety regulations.
Instructions and regulations are also stated in installation manuals or manuals which deal with hardware
installation and other hardware manipulations
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
3
Preface
Conventions Used
In this document, reference is often made to important information, notifications and
limitations. For clarification, the following conventions are thereby adhered to.
Note
Is an important note concerning characteristic or application of the described function
Attention
Provides information and explanations, the non-observance of which can lead to faulty behavior of the
system.
technical term, phrase, or function
designation
This syntax, for the purpose of easier
readability, identifies a term (also consisting
of several words), a phrase, or a function
designation
The following syntax identifies a parameter or a parameter group. The context in which the
syntax is used shows whether it refers to a parameter or to a parameter group.
<parameter group> | <parameter
group> | <parameter>
Parameter (qualified reference, includes
"path")
Time management | Daylight saving
time | Daylight saving time
enabling
<parameter group> | <parameter
group | *>
Parameter group (qualified reference,
includes "path")
Time management | Daylight saving
time
Parameter
<parameter>
Daylight saving time enabling
IEC_Enable
Parameter group
<parameter group | *>
Daylight saving time
A parameter name that ends with "_*", as
for example Inversion_*, can mean one
or all of the following (uniqueness results
from context):
<parameter_*>
Inversion
Inversion_0
Inversion_1
etc
#
in a <parameter group | *> or
in a <parameter>
"#" in a parameter group or in a parameter
corespond a number between 0 to 9, as for
example
PRE# … PRE0, PRE1
S#_U4_min … S0_U4_min, S1_U4_min
etc
4
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
Preface
Several Fundamental Terms
periodical Information
A periodical information is an information
with a deterministic transmission behavior
and is used for the exchange of a process
signal or a derived information between the
peripheral element and the higher-level
open-/closed-loop control function.
Periodical information are always
transmitted in groups and consequently with
the transmission already have a
chronologically consistent interrelationship.
Spontaneous Information Object
A spontaneous information object is an
object, which with change is transmitted
spontaneously in a message, and is used
for the exchange of a process signal or a
derived information (including Status)
between the system elements of the
particular automation unit, another
automation unit or a control system.
A spontaneous information object is always
transmitted individually and normally has a
time stamp, in order to be able to establish a
chronologically consistent interrelationship
later.
Message
A message is used for the spontaneous
transmission of process- and system
information. A message contains a
spontaneous information object, the address
for the unambiguous identification of the
information, type identification and
additional information necessary for the
transmission (e.g. length of the message)
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
5
Preface
6
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
Table of Contents
1
Application and General Description.............................................................................15
1.1
2
Architecture and Data Flow ............................................................................................17
2.1
3
Introduction.........................................................................................................16
Data Flow of Process Information ......................................................................18
System Services ..............................................................................................................19
3.1
3.1.1
3.1.1.1
3.1.2
3.1.2.1
Data Flow Control...............................................................................................20
Messages with Process Information .............................................................20
5-stage Message Address .......................................................................20
Messages with System Information ..............................................................21
System Address .......................................................................................21
3.1.2.1.1
Address of the Automation Unit ..........................................................21
3.1.2.1.2
Address of the System Element..........................................................21
3.1.3
Data Flow Test ..............................................................................................22
3.1.4
Message Simulation ......................................................................................23
3.2
Time Management..............................................................................................24
3.2.1
Clock..............................................................................................................24
3.2.2
Time Synchronization....................................................................................24
3.2.2.1
Time Synchronization with Serial Time Signal and Remote
Synchronization........................................................................................25
3.2.2.2
Time Synchronization in a Multi-Hierarchical Network.............................26
3.2.3
Time Tag .......................................................................................................26
3.2.4
Daylight-Saving and Normal Time ................................................................27
3.2.5
Time Zones ...................................................................................................27
3.2.6
Monitoring the Synchronization Event...........................................................27
3.2.6.1
Stand-alone of the Time-Signal Receiver ................................................28
3.2.6.2
Failure of the Serial Time Signal ..............................................................28
3.2.6.3
Failure of the Minute Pulse ......................................................................28
3.2.6.4
Failure of the Remote Synchronization....................................................28
3.2.6.5
Failure Behavior in Case of Combination of Time Signal and Remote
Synchronization........................................................................................29
3.2.7
3.3
Startup ...........................................................................................................30
Diagnostic and Signaling ....................................................................................31
3.3.1
Diagnostic Classes and their Meaning..........................................................31
3.3.2
Detailed Diagnostic .......................................................................................32
3.3.3
History Diagnostic .........................................................................................32
3.3.4
Sum Diagnostic .............................................................................................32
3.3.5
Network Survey .............................................................................................33
3.3.6
Display of the System States on the Automation Unit ..................................33
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
7
Table of Contents
3.3.7
Display of the System States on PSR II ....................................................... 33
3.3.8
Creation of Error Messages.......................................................................... 33
3.3.8.1
Error Messages Detailed Diagnostic Table ............................................. 34
3.3.8.2
Error Messages Sum Diagnostic Table................................................... 35
3.4
General Interrogation......................................................................................... 36
3.5
Failure ................................................................................................................ 38
3.5.1
3.5.1.1
Mark Data Points Affected by the Failure..................................................... 39
3.5.3
Diagnostic Information.................................................................................. 40
Data Storage on Flash Card .............................................................................. 41
3.6.1
Module Exchange ......................................................................................... 41
3.6.2
Commissioning an Automation Unit ............................................................. 41
3.6.3
Startup of an Automation Unit with Missing or Defective Flash Card........... 42
3.7
Autonomy........................................................................................................... 43
3.8
Communication with the Engineering System (TOOLBOX II) ........................... 44
3.9
Self-Test............................................................................................................. 45
3.9.1
Monitoring of Hardware and Firmware ......................................................... 45
3.9.2
Monitoring the Data Integrity ........................................................................ 48
3.10
Operating States................................................................................................ 50
3.10.1
Normal Operation ......................................................................................... 50
3.10.2
Limited Operation ......................................................................................... 50
3.10.3
Loading Operation ........................................................................................ 51
3.10.4
Firmware Shut Down .................................................................................... 52
3.10.5
Module Shut Down ....................................................................................... 52
Telecontrol ....................................................................................................................... 53
4.1
Introduction ........................................................................................................ 54
4.2
Communication with other automation units ..................................................... 55
4.2.1
Block Diagram .............................................................................................. 56
4.2.2
Automatic Data Flow Routing ....................................................................... 57
4.2.2.1
Messages in Control Direction ................................................................ 57
4.2.2.2
Messages in Monitor Direction ................................................................ 58
4.2.2.3
Messages in the Private Range .............................................................. 59
4.2.3
8
Measures in the Event of an Error........................................................... 38
3.5.2
3.6
4
Monitoring of the Interfaces .......................................................................... 38
Data Storage................................................................................................. 60
4.2.3.1
Message Characteristics ......................................................................... 61
4.2.3.2
Data Storage of Process Information ...................................................... 62
4.2.3.2.1
State Compression............................................................................. 62
4.2.3.2.2
Behavior with a Priority Channel Overload ........................................ 62
4.2.3.2.3
Behavior During a Communication Failure ........................................ 63
4.2.3.2.4
Dwell Time for Messages with Process Information .......................... 63
4.2.3.2.5
Station Interrogation ........................................................................... 64
4.2.3.2.6
Failure Management .......................................................................... 64
4.2.3.2.7
Blocking .............................................................................................. 65
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02
Table of Contents
4.2.3.3
4.2.4
Priority Control...............................................................................................65
4.2.4.1
Prioritization Algorithm .............................................................................66
4.2.4.2
Influencing of the Prioritization Algorithm by the Protocol Element .........67
4.2.5
Redundant Communication Routes ..............................................................68
4.2.5.1
Communication with Redundant Remote Stations ..................................68
4.2.5.2
Redundant Communication with a Remote Station (LSO) ......................68
4.2.5.2.1
Data Split Mode...................................................................................69
4.2.5.2.2
Load Share Mode................................................................................69
4.2.6
4.3
Startup ...........................................................................................................70
Protocol Element Control and Return Information .............................................71
4.3.1
Block Diagram ...............................................................................................71
4.3.2
Protocol Element Control ..............................................................................72
4.3.3
Protocol Element Return Information ............................................................73
4.4
Decentralized Archiving......................................................................................74
4.4.1
Block Diagram ...............................................................................................75
4.4.2
Recording of data into the archive ................................................................75
4.4.2.1
Spontaneous Archiving ............................................................................76
4.4.2.2
Periodical Archiving..................................................................................76
4.4.2.3
Power fail safe Storing .............................................................................77
4.4.2.4
Archiving before Time Setting ..................................................................77
4.4.2.5
Configuration of the archive .....................................................................77
4.4.3
5
Data Storage for Transparent Information ...............................................65
Transmission of the archive ..........................................................................78
Automation .......................................................................................................................79
5.1
Introduction.........................................................................................................80
5.2
Open-/Closed-Loop Control Function.................................................................81
5.2.1
Block Diagram ...............................................................................................83
5.2.2
Task Management.........................................................................................84
5.2.2.1
Coordination of the Sequences of a Task................................................84
5.2.2.2
Task timing ...............................................................................................85
5.2.2.3
Cycle Time ...............................................................................................85
5.2.2.4
Run Time Supervision..............................................................................86
5.2.2.5
Time Management for Function Blocks ...................................................87
5.2.3
5.2.3.1
Initialization....................................................................................................87
Startup of the Basic System Element ......................................................88
5.2.3.1.1
Initialization of the Variables ...............................................................88
5.2.3.1.2
Initialization of the Resource-Global Parameters ...............................88
5.2.3.1.3
Initialization of the Signals ..................................................................89
5.2.3.2
Startup of the Open-/Closed-Loop Control Function................................89
5.2.3.2.1
Initialization of the Variables ...............................................................90
5.2.3.2.2
Initialization of the Signals ..................................................................90
5.2.3.3
5.2.4
Stationary Cycles .....................................................................................91
Input Handling ...............................................................................................91
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
9
Table of Contents
5.2.4.1
5.2.4.1.1
Storage Method "State Stored" .......................................................... 92
5.2.4.1.2
Storage Method "Chronological Message" ........................................ 92
5.2.4.1.3
Storage Method "Chronological Global"............................................. 92
5.2.4.1.4
Failure Management .......................................................................... 93
5.2.4.1.5
Message Characteristics .................................................................... 93
5.2.4.1.6
Input Process Image for Spontaneous Information Objects .............. 94
5.2.4.2
Conversion of Spontaneous Information Objects to Periodical Information104
5.2.4.3
Synchronization of the Input Process Images....................................... 104
5.2.4.3.1
Periodical Information....................................................................... 105
5.2.4.3.2
System Information .......................................................................... 106
5.2.4.3.3
Spontaneous Information Objects.................................................... 107
5.2.5
Output Handling.......................................................................................... 108
5.2.5.1
Updating of Local Peripheral Elements for Periodical Information........ 108
5.2.5.2
Generation of Messages with System Information................................ 108
5.2.5.3
Generation of Diagnostic Information.................................................... 109
5.2.5.4
Change Monitoring for Spontaneous Information Objects .................... 109
5.2.5.4.1
5.2.5.5
Additive Threshold Value Procedure................................................ 110
Generation of Messages with Process Information............................... 111
5.2.5.5.1
Test Switches ................................................................................... 111
5.2.5.5.2
Behavior with General Interrogation................................................. 112
5.2.5.5.3
Message Characteristics .................................................................. 112
5.2.5.5.4
Output Process Image for Spontaneous Information Objects.......... 114
5.2.6
Loading of Application Program (Reload) .................................................. 125
5.2.7
Online-Test ................................................................................................. 126
5.2.7.1
Display/Forcing of Values...................................................................... 126
5.2.7.2
Test Switches ........................................................................................ 127
5.2.7.3
Changing the Processing Status of the Controller ................................ 128
5.2.7.4
Breakpoints............................................................................................ 129
5.2.7.5
Real Time Archive ................................................................................. 129
5.2.7.6
Display Status Information .................................................................... 131
5.2.7.7
Terminating the Online Test .................................................................. 131
5.3
Treatment for Commands to the Open-/Closed-Loop Control Function
according to IEC 60870-5-101/104.................................................................. 132
5.3.1
Pulse Commands ....................................................................................... 134
5.3.2
Setpoint Values .......................................................................................... 136
5.3.3
Bit String ..................................................................................................... 137
5.3.4
Functions in Detail ...................................................................................... 138
5.3.4.1
10
Message Processing for Spontaneous Information Objects ................... 91
Prepare Command Output Procedure .................................................. 138
5.3.4.1.1
Formal Check ................................................................................... 138
5.3.4.1.2
Retry Suppression............................................................................ 139
5.3.4.1.3
Direct Command .............................................................................. 139
5.3.4.1.4
Select and Execute Command......................................................... 139
5.3.4.1.5
Control Location Check .................................................................... 141
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02
Table of Contents
5.3.4.1.6
Command Locking ............................................................................142
5.3.4.1.7
1-out-of-n Check ...............................................................................143
5.3.4.1.8
System-Element Overlapping 1-out-of-n Check ...............................144
5.3.4.2
Initiate Command Output Procedure .....................................................145
5.3.4.3
Monitor Pulse Duration...........................................................................145
5.3.4.3.1
BefehlsCommand Output Time (without Return Information
Monitoring) ........................................................................................145
5.3.4.3.2
Application program (with Return Information Monitoring) ...............146
5.3.4.4
Error Handling ........................................................................................148
5.3.4.4.1
Cancel ...............................................................................................149
5.3.4.4.2
Cancel with Diagnostic......................................................................149
5.3.5
5.3.5.1
Data Interface..............................................................................................149
Spontaneous Information Objects to the Treatment for Commands .....149
5.3.5.1.1
Pulse Commands..............................................................................149
5.3.5.1.2
Setpoint Value...................................................................................150
5.3.5.1.3
Bitstring .............................................................................................151
5.3.5.1.4
Command x Interlocked ....................................................................151
5.3.5.1.5
Return Information x..........................................................................153
5.3.5.2
Spontaneous Information Objects from the Treatment for Commands .154
5.3.5.2.1
Confirmation of the Pulse Command ................................................154
5.3.5.2.2
Confirmation of the Setpoint Value ...................................................155
5.3.5.2.3
Confirmation of the Bitstring..............................................................156
5.3.5.2.4
Sum Command Interlocked ..............................................................156
5.3.5.3
System Information ................................................................................157
5.3.5.3.1
To the Application Program ..............................................................157
5.3.5.3.2
From the Application Program ..........................................................157
5.4
5.4.1
Restricted open/closed loop function ...............................................................158
Instruction List .............................................................................................159
5.4.1.1
Data Types .............................................................................................159
5.4.1.2
Variables ................................................................................................160
5.4.1.2.1
I/O Variablen .....................................................................................160
5.4.1.2.2
Internal variables...............................................................................162
5.4.1.2.3
System Variables ..............................................................................164
5.4.1.3
Constants ...............................................................................................165
5.4.1.4
Jump Marks............................................................................................165
5.4.1.5
Command Record ..................................................................................166
5.4.1.6
Functions................................................................................................167
5.4.1.6.1
Numerical Functions .........................................................................167
5.4.1.6.2
Arithmetical Functions.......................................................................167
5.4.1.6.3
Binary Logic Operation .....................................................................168
5.4.1.6.4
Selection Functions...........................................................................168
5.4.1.6.5
Comparison Functions ......................................................................169
5.4.1.7
5.4.1.7.1
Function Blocks......................................................................................169
Bistable Elements .............................................................................170
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
11
Table of Contents
5.4.1.7.2
Edge Detection................................................................................. 170
5.4.1.7.3
Counters ........................................................................................... 170
5.4.1.7.4
Timers............................................................................................... 171
5.4.2
5.4.2.1
Automatic Type Transformation ....................................................... 172
5.4.2.1.2
Structure data types ......................................................................... 173
5.4.2.1.3
Proprietary data types ...................................................................... 173
Variables................................................................................................ 174
5.4.2.2.1
I/O Variables..................................................................................... 174
5.4.2.2.2
System Variables ............................................................................. 174
5.4.2.3
Functions ............................................................................................... 175
5.4.2.3.1
Numerical Functions......................................................................... 175
5.4.2.3.2
Arithmetical Functions ...................................................................... 175
5.4.2.3.3
Binary Logic Operation..................................................................... 176
5.4.2.3.4
Selection Functions .......................................................................... 176
5.4.2.3.5
Comparison Functions ..................................................................... 177
5.4.2.3.6
Transformation Functions................................................................. 177
5.4.2.4
Function Blocks ..................................................................................... 178
5.4.2.4.1
Bistable Elements............................................................................. 178
5.4.2.4.2
Edge Detection................................................................................. 178
5.4.2.4.3
Counters ........................................................................................... 179
5.4.2.4.4
Timers............................................................................................... 179
5.4.2.4.5
Pulse Generator ............................................................................... 180
5.4.2.4.6
System Time Functions.................................................................... 180
5.4.2.4.7
Force Variable .................................................................................. 180
5.4.3
5.4.3.1
Internal Signal Processing.......................................................................... 181
Input Signals.......................................................................................... 181
5.4.3.1.1
Process image (state stored). .......................................................... 182
5.4.3.1.2
Ring chronological in message. ....................................................... 182
5.4.3.1.3
Ring chronological global. ................................................................ 183
5.4.3.1.4
Ring Overflow ................................................................................... 183
5.4.3.2
Output Signals ....................................................................................... 183
5.4.3.3
Automatic Routing of Data Points ......................................................... 183
5.4.3.4
Non-Volatile Memory ............................................................................. 183
5.4.3.5
Loading of Program (Cold Start) ........................................................... 184
5.4.3.6
Treatment of communication failure ...................................................... 184
5.4.3.6.1
5.4.4
12
Data Types ............................................................................................ 172
5.4.2.1.1
5.4.2.2
A
Function Diagram ....................................................................................... 172
Startup(Warm start).......................................................................... 184
Online Test ................................................................................................. 185
Message Formats.......................................................................................................... 187
A.1
Introduction ...................................................................................................... 188
A.2
Overview .......................................................................................................... 188
A.3
Messages with Process Information................................................................ 190
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02
Table of Contents
A.3.1
General Message Structure ........................................................................191
A.3.1.1
Length, Function Code and Checksum..................................................191
A.3.1.2
Function Code-Dependent Extra Information ........................................192
A.3.1.3
Address ..................................................................................................194
A.3.1.4
State .......................................................................................................195
A.3.1.5
Type Identification ..................................................................................197
A.3.1.6
Time Stamp ............................................................................................198
A.3.2
Information Objects .....................................................................................199
A.3.2.1
Single-Point Information (TI = 30) ..........................................................199
A.3.2.2
Double-Point Information (TI = 31).........................................................199
A.3.2.3
Transformer Tap Position Value (digital) (TI = 32).................................199
A.3.2.4
Bitstring of 32 bit (TI = 33)......................................................................200
A.3.2.5
Measured Value, Normalized Value (TI = 34)........................................200
A.3.2.6
Measured Value, Scaled Value (TI = 35) ...............................................200
A.3.2.7
Measured Value, Short Floating Point Number (TI = 36).......................201
A.3.2.8
Integrated Totals (TI = 37) .....................................................................201
A.3.2.9
Event of Protection Equipment (TI = 38)................................................202
A.3.2.10
Blocked Activation of the Protection (TI = 39)........................................202
A.3.2.11
Blocked Triggering of the Protection (TI = 40) .......................................203
A.3.2.12
Single Command (TI = 45) .....................................................................203
A.3.2.13
Double Command (TI = 46) ...................................................................204
A.3.2.14
Regulating Step Command (TI = 47) .....................................................204
A.3.2.15
Setpoint Command, Normalized Value (TI = 48) ...................................205
A.3.2.16
Sollwert-Stellbefehl, skalierter Wert (TI = 49) ........................................205
A.3.2.17
Setpoint Command, Short Floating Point Number (TI = 50) ..................206
A.3.2.18
Container for Process Information (TI = 142) ........................................206
A.3.2.19
File Transfer (TI = 144) ..........................................................................207
A.3.2.20
Packed Information Objects ...................................................................207
A.3.2.21
Addressing of an Individual Element (SQ=0) .........................................208
A.3.2.22
Addressing of a Sequence of Information Elements (SQ=1) .................208
A.4
Messages with System Information..................................................................208
A.4.1
Counter Interrogation Command.................................................................209
A.4.2
(General) Interrogation Command ..............................................................210
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
13
Table of Contents
14
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02
1
Application and General Description
Content
1.1
Introduction.........................................................................................................16
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
15
Application and General Description
1.1
Introduction
This document describes the standardized, parameter-settable function packages of the basic
system elements:
•
System Services
─ Data Flow Control
─ Time Management
─ Diagnostic and Signaling
─ General Interrogation
─ Failure
─ Data Storage on Flash Card
─ Autonomy
─ Communication with the Engineering System (TOOLBOX II)
─ Self-Test
─ Operating States
•
Telecontrol
─ Communication with other automation units
─ Protocol Element Control and Return Information
─ Decentralized Archiving
•
Automation
─ Open-/Closed-Loop Control Function
─ Treatment for Commands to the Open-/Closed-Loop Control Function according to IEC
60870-5-101/104
In the corresponding system element data sheets and system element manuals of those
system elements that contain and carry out one or more of these functions,
16
•
reference is made to this description
•
supplementary information and features that may possibly deviate are specified
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02
2
Architecture and Data Flow
Content
2.1
Data Flow of Process Information ......................................................................18
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
17
Architecture and Data Flow
2.1
Data Flow of Process Information
Process signals
Process
input/output
I/O
module
TM bus
Process periphery
IEC60870-5-101/104
Process periphery
IEC60870-5-101/104
Peripheral element
Process
input/output
Peripheral element
I/O
module
Ax 1703 PE bus
Treatment for
commands
IEC60870-5-101/104
Diagnostic
Error messages
Communication
function
Basic system element
Internal distribution of messages with process information (data flow control)
Protocol
element
control
Node bus
Open-/Closed
loop control
function
SBD bus
Protocol
element
Protocol
element
Link
18
Telecontrol
Messages with process information
Automation
Periodical information
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02
3
System Services
Content
3.1
Data Flow Control...............................................................................................20
3.2
Time Management..............................................................................................24
3.3
Diagnostic and Signaling ....................................................................................31
3.4
General Interrogation .........................................................................................36
3.5
Failure.................................................................................................................38
3.6
Data Storage on Flash Card...............................................................................41
3.7
Autonomy ...........................................................................................................43
3.8
Communication with the Engineering System (TOOLBOX II)............................44
3.9
Self-Test .............................................................................................................45
3.10
Operating States.................................................................................................50
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
19
System Services
3.1
Data Flow Control
The data flow control is that system function which co-ordinates the communication of
messages within the automation unit.
This function supports:
•
Messages with Process Information
•
Messages with System Information
•
Messages for Filetransfer
For the tracking of messages within an automation unit the following test functions are
available:
3.1.1
•
Data Flow Test
•
Message Simulation
Messages with Process Information
The distribution of messages with process information takes place by way of routing
(telecontrol) or assignment (open- / closed-loop control function) based on message address
and type identification in the message.
Messages with process information to be transmitted through protocol elements to other
automation units are distributed with the help of the Automatic Data Flow Routing.
For messages with process information for sinks within the automation unit, such as e.g.
periphery elements and the open-/closed-loop control function, the routing information or
assignments are automatically derived from parameters from OPM-inputs (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.
These messages have a 5-stage message address, that must be parameterized at the
sources. For a third-party system coupling via a serial interface, the corresponding protocol
element is the source.
3.1.1.1
5-stage Message Address
The 5-stage message address is defined according to IEC 60870-5-101/104:
•
•
CASDU ...
Common address of ASDU
The CASDU is determined for each data point with the help of the OPM II. Valid thereby:
─ CASDU1
...
least significant octet
─ CASDU2
...
most significant octet
IOA
...
Address of the information object
The IOA is determined for each data point with the help of the OPM II. Valid thereby:
─ IOA1 ...
least significant octet
─ IOA2 ...
─ IOA3 ...
20
most significant octet
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02
System Services
3.1.2
Messages with System Information
The distribution of messages with system information takes place with the help of the systemtechnical destination address in the message by way of automatic routing within the
automation unit.
The routing takes place with the help of the parameterized configuration- and topology
information.
3.1.2.1
System Address
3.1.2.1.1 Address of the Automation Unit
An automation unit is addressed by means of:
region number (0 .. 249) and
•
component number (0 .. 255).
Within a system-technical plant each automation unit must be unambiguously addressed.
Therefore a system-technical plant may consist of up to 64.000 automation units.
3.1.2.1.2 Address of the System Element
Within an automation unit the system elements are addressed with:
•
Basic System Element and
•
Supplementary System Element.
System Element
Basic System Element
Supplementary System
Element
Master control unit
20
254
C-CPU 0 – 16
0 – 16
254
Peripheral element 0 – 15 of a basic
system element
0 – 16, 20
0 –15
Protocol element 0 –3 of a basic
system element
0 – 16, 20
128 – 131
all system elements of an automation
unit
255
255
all basic system elements of an
automation unit
255
254
all supplementary system elements of
a basic system element
0 – 16, 20
255
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
21
System Services
3.1.3
Data Flow Test
For the data flow test there are test points available within the automation unit at defined
places, for the purpose of monitoring the message traffic. Thereby both messages with
process information as well as messages with system information can be tracked.
The following test points are basically available:
•
from and to communication
•
from and to peripheral element
•
internal data flow
─ from and to basic system element
─ from and to supplementary system element
─ from and to special functions
The availabilty of test points depends on the system element used.
The messages acquired at the test points are stored on the master control unit in a FIFO
(service ring). These can be displayed with the help of the TOOLBOX II.
Attention
Messages with larger data length (e.g. blocked messages) are not represented completely with the
display.
The service ring has a capacity of approx. 250 messages and can be operated in two modes:
•
Stop, when ring is full
If the capacity is exceeded no further messages are entered. This state is displayed after
the last message read by the TOOLBOX II, with the binary information "Service ring full!
Data loss".
•
Wrap around
If the capacity is exceeded, the oldest message is overwritten with each new message.
Once the TOOLBOX II begins reading the service ring, the further entry of messages is
blocked.
Through variable filters (pass through- and blocking filters) the possibility exists of only having
messages displayed, which are relevant for the test. There are filters that act in the
automation unit before the entry in the service ring and filters in the TOOLBOX II.
The test points and filters must be deleted again by means of operator input. I.e. the test
points and filters are not deleted only by terminating the tool.
Attention
An activated data flow test means, that the message flow through the automation unit can be reduced to
50%. I.e. for automation units with a high data throughput, FIFO overflows can thereby occur on the node
bus. In further succession this can lead to system elements being shut down. A possible remedy is, to set
the previously mentioned filters in the automation unit.
22
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02
System Services
Special case startup
For the case, that the message traffic is to be tracked during startup of the automation unit,
the following behavior can be set via the menu item "Simultaneous logging startup":
3.1.4
•
Setting possibility of all necessary test points and filters
•
Menu item Simultaneous logging/Startup
•
Confirmation of the inquiry "Trip reset of the automation unit"
•
Reset the automation unit
•
The startup of the system element is halted, before the message traffic with other system
elements begins -> LED "CAE" lights up.
•
Test points and filters are loaded
•
With the confirmation of the inquiry "Startup simultaneous logging prepared, will be started
with OK", the startup can be continued by the operator.
Message Simulation
This function enables messages to be passed into the data flow with the help of the
TOOLBOX II. Both messages with process information as well as messages with system
information can be simulated.
The simulated message is passed in and distributed at the master control unit of the selected
automation unit.
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
23
System Services
3.2
Time Management
The overall concept assumes, that each automation unit and each system element, that has a
time-dependent function to fulfill, can manage a clock with corresponding accuracy and
resolution. Each automation unit has a central clock, the so-called time server.
The format of the clocks is structured in Year (2 digit) - Month - Day - Hour - Minute - Second 1/1000 Second.
3.2.1
Clock
In normal operation (error-free operation) the clocks are set once after startup oft the
automation unit and then run completely autonomous without any further time setting
mechanisms.
Only a Time Synchronization ensures, that all time servers in all automation units run
synchronously.
All clocks within an automation unit are operated and synchronized by a central 10 ms-clock
pulse, that is generated by the time server of the automation unit with an accuracy of < 1 ms.
With a restart, all clocks start to run unsynchronized with the value 0 hours, i.e. until the first
time setting they have only a relative time, whereby this time is identified with "invalid".
3.2.2
Time Synchronization
The time server of an automation unit can
•
be synchronized by a serial time signal over the direct serial connection of a DCF77 or a
GPS time signal receiver.
•
be synchhronized by remote synchronization with the clock synchronization command
over a serial communication or over the LAN (Ethernet TCP/IP – NTP). In case of serial
communication failure the time can be set by TOOLBOX II.
•
be synchronized by a minute pulse of a DCF77 or a GPS time signal receiver. The time
can be set via the communication (serial, LAN) by means of the synchronization
command, or by TOOLBOX II.
•
be operated free running (not synchronized).
The method of time synchronization is determined with the parameter Time
management | Common settings | Synchronizing of the automation unit for
each automation unit.
24
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02
System Services
The accuracy of the clocks of an automation unit is dependent on the choice of method for the
time synchronization. With the remote synchronization this is also dependent on the protocol
element and the transmission medium.
Time Synchronization Method
Remarks
Accuracy
Serial time signal
GPS time signal receiver
± 1ms
DCF77 time signal receiver with
correlation process
± 1ms
GPS time signal receiver
± 10ms
DCF77 time signal receiver with
correlation process
± 10ms
LAN or WAN with NTP with point-topoint connections via switches
± 3ms
Connections with incalculable
message delays (e.g. ISDN, ADSL,
SAT120/DMS etc.)
< ± 1s
after connection setup with a point-topoint connection (e.g. dial-up traffic)
1)
Point-to-point connections with a time
synchronization 1x every minute
± 10ms
Point-to-point connections with a time
synchronization every 5th second 2)
± 1ms
Combination from serial time signal
and remote synchronization or NTP
3)
Minute pulse
Remote synchronization or NTP
Serial time signal and Remote
synchronization
None (stand alone)
10-4 equals
±360ms/h
1)
The accuracy is dependent on the periodicity of the clock synchronization command and the quartz
accuracy (10-4 equals ±360ms/h) of the remote terminal unit. The periodicity of the clock synchronization
command can be set with parameters on the corresponding protocol element with the master function.
2)
Dependent on the protocol element used (e.g. UMPM01 and UMPS01)
3)
The accuracy is dependent on the current operating state. The accuracy is 1 ms in the fault-free
operation (serial time signals). At failure of the serial time signal the accuracy is dependent on the
communication connection (see remark to remote synchronization or NTP).
3.2.2.1
Time Synchronization with Serial Time Signal and Remote
Synchronization
This method of synchronization is a combination of synchronization with the serial time signal
and remote synchronization. Thereby the serial time signal is the primary synchronization
event, and remote synchronization is the secondary synchronization event.
Switchover from primary to secondary synchronization event
In case of failure of the serial time signal a switchover to remote synchronization occurs after
a delay of 65 seconds.
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
25
System Services
If the time signal receiver is free running a switchover to remote synchronization occurs after a
settable time (parameter Time management | Common settings | Free running time
of time sig. receiver).
Switchover from secondary to primary synchronization event
As soon as the serial time signal, without free running indicator, is received a switchover
occurs after a delay of 65 seconds.
3.2.2.2
Time Synchronization in a Multi-Hierarchical Network
In the entire network at least one automation unit must be synchronized with serial time signal
or NTP, i.e. one time master must exist.
The transmission of the clock synchronization command to other automation units takes place
automatically from the time master in the parameterized control direction (topology parameter
Clock-Sync = automatic).
The clock synchronization command is only accepted from a communication line, that is
defined in the topology parameters as monitor direction.
Automation units with time master do not accept any clock synchronization command.
For special applications, the previously described time synchronization automatic can be
adapted in the topology parameters (Clock-Sync):
3.2.3
Parameter Clock-Sync
Function
transmit only
The clock synchronization command is transmitted over this
interface regardless of the parameterized data flow direction
receive only
The clock synchronization command is accepted over this
interface for time synchronization
inhibited
Over this interface neither the clock synchronization command is
transmitted nor is a received clock synchronization command
accepted
Time Tag
The time tagging takes place automatically at all places in the system, where messages with
process information are generated. The transfer of the messages with process information
with standard protocols always takes place with 7 octet time. The resolution and the accuracy
of the time tag is dependent on the function and on the system element.
26
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02
System Services
3.2.4
Daylight-Saving and Normal Time
With remote synchronization over point-to-point transmission media the switchover from/to
daylight-saving time takes place automatically.
If the time synchronization takes place by means of a serial time signal (GPS or DCF77 time
signal receiver) the switchover is performed according to the European standard (+ or – 1
hour) depending on the parameter Time management | Time zone | GPS time zone
identification std. time or Time management | Time zone | GPS time zone
identification DST (default setting is Central Europe CET). In these parameters an ASCII
text is to be entered according to the time signal receiver used. The parameter Time
management | Daylight saving time | Daylight saving time enabling is not
relevant.
With time synchronization without daylight-saving / normal time support
•
remote synchronization over LAN/WAN with NTP (Network Time Protocol)
•
remote synchronization over transmission medium with unknown delays (e.g. dial-up
traffic) and a periodicity of the clock synchronization command > 1h
the switchover times of the daylight-saving- and normal time are to be determined by means
of the parameter group Time management | Daylight saving time | Daylight
saving time rule | *. This parameter group first becomes active, when the parameter
Time management | Daylight saving time | Daylight saving time enabling is
set.
3.2.5
Time Zones
For a time synchronization with GMT (Greenwich Mean Time), for the adjustment of the clock
time to the local time the time zone is to be defined with the parameter Time
management | Time zone | Time zone. This is necessary for a remote synchronization
over LAN/WAN with NTP (Network Time Protocol).
For time synchronization with a serial time signal it is necessary to parameterize the
identification text for normal time with the parameter Time management | Time zone |
GPS time zone identification std. time and the daylight-saving time with the
parameter Time management | Time zone | GPS time zone identification DST. By
default the identification text for Central Europe ("CET" and "CEST") is set.
3.2.6
Monitoring the Synchronization Event
After startup, on failure of the synchronization event, or after the stand-alone monitoring has
triggered a failure event, the clock time in all clocks of the automation unit is provided with an
"invalid" identifier. All clocks of the connected automation units, that are synchronized from
this automation unit, are likewise provided with the "invalid" identifier (except after startup).
This mark distributes the clock synchronization commands of the protocol element in the
parameterized or fixed defined grid.
The "invalid" identifier is reset with the next error-free synchronization operation and is always
output from an automation unit with time master.
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
27
System Services
3.2.6.1
Stand-alone of the Time-Signal Receiver
If the connection between time-signal receiver and –transmitter is interrupted for longer than a
parameter-settable time (Parameter Time management | Common settings | Unit of
time for free running and monitoring time), the diagnostic information ''Stand-alone
of the time signal receiver" of the class "Warning" is set.
In addition all clocks of the automation unit are set to "invalid". All clocks of the connected
automation units, that are synchronized from this automation unit, are likewise provided with
the "invalid" identifier.
3.2.6.2
Failure of the Serial Time Signal
A check is performed of whether the serial time signal arrives within 2.5 seconds. If this is not
the case, a diagnostic information "Failure of time signal" of the class "Warning" is set.
If the serial time signal fails for longer than the time defined with the parameter
Time management | Common settings | Monitoring time for synchroniz. event,
a diagnostic information "Failure of time signal" of the class "External" is set. In addition all
clocks of the automation unit are set to "invalid". All clocks of the connected automation units,
that are synchronized from this automation unit, are likewise provided with the "invalid"
identifier.
3.2.6.3
Failure of the Minute Pulse
A check is performed of whether the minute pulse arrives within 65 seconds. If this is not the
case, a diagnostic information "Failure of minute pulse" of the class "Warning" is set.
If the minute pulse fails for longer than the time defined with the parameter
Time management | Common settings | Monitoring time for synchroniz. event,
a diagnostic information "Failure of minute pulse" of the class "External" is set. In addition all
clocks of the automation unit are set to "invalid". All clocks of the connected automation units,
that are synchronized from this automation unit, are likewise provided with the "invalid"
identifier.
3.2.6.4
Failure of the Remote Synchronization
If the clock synchronization command fails for longer than the time defined with the parameter
Time management | Common settings | Monitoring time for synchroniz. event,
a diagnostic information "Failure of synchronization over communication line" of the class
"Warning" is set.
Monitoring does not start before the clocks of the automation unit have been set.
In addition all clocks of the automation unit are set to "invalid". All clocks of the connected
automation units, that are synchronized from this automation unit, are likewise provided with
the "invalid" identifier.
28
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02
System Services
3.2.6.5
Failure Behavior in Case of Combination of Time Signal and
Remote Synchronization
Both synchronization events are supervised independent of the currently effective
synchronization event.
Failure of the primary synchronization event (serial time signal)
A check is performed of whether the serial time signal arrives within 2.5 seconds. If this is not
the case, a diagnostic information "Failure of time signal" of the class "Warning" is set.
After a delay of 65 seconds a switchover to the secondary synchronization event (remote
synchronization) occurs.
If the time signal receiver is free running a switchover to the secondary synchronization event
(remote synchronization) occurs after a settable time (parameter Time
management | Common settings | Free running time of time sig. receiver).
Case A: secondary synchronization event failed
If the serial time signal fails for longer than the time defined with the parameter Time
management | Common settings | Monitoring time for synchroniz. event, a
diagnostic information "Failure of time signal" of the class "External" is set.
In addition all clocks of the automation unit are set to "invalid".
All clocks of the connected automation units, that are synchronized from this automation unit,
are likewise provided with the "invalid" identifier.
Case B: secondary synchronization event OK
If the serial time signal fails for longer than the time defined with the parameter Time
management | Common settings | Monitoring time for synchroniz. event, a
diagnostic information "Failure of time signal" of the class "External" is set.
The clocks of the automation unit are not set to "invalid".
Failure of the secondary synchronization event (remote synchronization)
If the clock synchronization command fails for longer than the time defined with the parameter
Time management | Common settings | Monitoring time for synchroniz. event,
a diagnostic information "Failure of synchronization over communication line" of the class
"Warning" is set.
Monitoring does not start before the clocks of the automation unit have been set.
Case A: primary synchronization event failed
All clocks of the automation unit are set to "invalid".
All clocks of the connected automation units, that are synchronized from this automation unit,
are likewise provided with the "invalid" identifier.
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
29
System Services
Case B: primary synchronization event OK
The clocks of the automation unit are not set to "invalid".
3.2.7
Startup
After startup the clocks of the automation unit are set with the first occurrence of a valid
synchronization event.
Note
A valid synchronization event may as well contain a time marked as invalid.
If within 2 minutes a valid synchronization event does not arrive a diagnostic information
"Time of automation unit not set" of the class "Warning" is set.
Note
Connected automation units are synchronized not before the automation unit has a valid time.
30
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02
System Services
3.3
Diagnostic and Signaling
The diagnostic treatment of an automation unit recognizes and manages diagnostic
information. Diagnostic information are errors, faults and also operating states. These
diagnostic informations are categorized for each system element in the automation unit,
sorted according to diagnostic class, stored with detailed description and summed up.
3.3.1
Diagnostic Classes and their Meaning
Failure (Class A)
Signals, that an automation unit can no longer be reached and will be created by the
monitoring automation unit.
Module Failure (Class B)
Signals, that the internal communication with a system element is no longer possible and will
be created by the monitoring basic system element.
External Errors (Class E)
Are errors, that are detected through monitoring the information from sensors and actuators.
They can concern the peripheral element, the wiring and sensors or actuators, insofar as the
source of error can not be unequivocally localized to the peripheral element; then it would be
an internal error.
Startup (Class H)
Signals, that the automation unit or the system element has started up following Power-Up or
Reset.
Internal Errors (Class I)
Are errors, that can be unequivocally traced back to system elements in the automation unit
(Firmware or Hardware).
Communication Errors (Class K)
Are errors, that are detected by protocol elements and result from the monitoring of the
communication line, insofar as the source of error can not be unequivocally localized to the
protocol element; then it would be an internal error.
Test (Class T)
Test means, that a clearly assigned function is in test; e.g. Online-Test of the Open-/ClosedLoop Control Function.
Warning (Class W)
Warning indicates, that the system is still functioning, but has limited functionality or
availability, e.g. parameter error, poor line quality, external minute synchronization failed, but
internal quartz accuracy is still sufficient.
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
31
System Services
3.3.2
Detailed Diagnostic
Administration and storage of detailed diagnostic information for each system element in the
detailed diagnostic table. Storage means, that all diagnostic information occurring either since
the last read out by the PSR II or since startup of the automation unit are flagged.
Provision of additional identifiers for the detailed diagnostic information, in the event that
further information is necessary for an error detection (e.g. in which routing record the error
has occurred). Additional identifiers can only be read out with the PSRII.
3.3.3
History Diagnostic
Administration of a diagnostic ring for each basic system element for the chronological logging
of changes to the diagnostic information of the basic system element and its supplementary
system elements. The last 20 changes that have occurred are stored with time and date.
3.3.4
Sum Diagnostic
The sum diagnostic creates sums about detailed diagnostic information according to
established rules and presents these in a sum diagnostic table:
32
Diagnostic Information
Meaning
Sum diagnostic record of the
automation unit
Summing of the sum diagnostic records of the basic system
elements
Sum diagnostic record of a basic
system element
Summing of the diagnostic information of a basic system element
and all its supplementary system elements according to
diagnostic classes
Failure of a basic system element
Failure of a peripheral element
Failure of a protocol element
Information of the diagnostic class B (module failure) of the
corresponding system element
Fault of a basic system element
Fault of a peripheral element
Fault of a protocol element
Sum of the diagnostic classes I(nternal), E(xternal), K
(communication) of the corresponding system element
Failure of a communication line
Failure of the remote station for a protocol element with Single
Point data communication mode or failure of all stations for a
protocol element with Multi Point data communication mode
Fault of a communication line
This diagnostic information is only significant for protocol
elements with Multi Point data communication mode and
indicates, that one or several stations have failed.
Sum diagnostic record of the rest
of the system
The sum diagnostic record of the rest of the system is created
from all sum diagnostic records of the other automation units
(power network survey).
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02
System Services
3.3.5
Network Survey
The sum diagnostic record of an automation unit is automatically distributed to all other
automation units by means of messages with system information in monitoring direction.
Each automation unit stores these sum diagnostic records in a power network survey table.
For special applications, in the topology parameters a distribution to other automation units
can be inhibited or also enabled in the control direction.
On failure of one automation unit, the class "Failure" is created by the automation unit
detecting the failure, entered in the corresponding part of the network diagnostic table and
distributed.
This emulation can be delayed with the parameter AU common settings | Delay time
failure reproduction.
3.3.6
Display of the System States on the Automation Unit
Display of the AU sum diagnostic record and of operating states via LED´s on the front panel
of the master control element. Which information is displayed, can be taken from the
corresponding system element manual.
Summing of the classes I, E, K, B and output at the relay contact "Error" of the master control
element. The output takes place in the open-circuit principle.
The watchdog is output at the relay contact "WD" of the master control element. The output
takes place in the closed-circuit principle.
3.3.7
Display of the System States on PSR II
The PSR II is a toolset of the TOOLBOX II. With the help of the tool "Diagnostic" in the toolset
PSR II, detailed system states (single diagnostic) are summed (overview diagnostic) and the
content of the diagnostic ring (History diagnostic) is read out and displayed with plain text.
With the help of the power network survey diagnostic, all sum diagnostic records of the
automation units defined in the topology can be displayed.
3.3.8
Creation of Error Messages
This function enables messages with process information to be created from freely selectable
diagnostic information. The messages can be distributed within the automation unit, to other
automation units or to control systems and e.g. evaluated for the following tasks:
•
Signaling of selected system states
•
Information for redundancy switchovers
•
Logging of faults
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
33
System Services
The messages are generated with a freely selectable 5-stage address and the type
identification 30 (single-point information). The acquisition of the changed diagnostic
information takes place periodically every 100ms. Diagnostic information items that are
present for a shorter period are stored transiently.
The diagnostic information can be taken both from the detailed diagnostic table as well as
from the sum diagnostic table.
The assignment of the address for the messages with process information to the diagnostic
information is carried out with the help of the process-technical parameter setting in the OPM.
•
Error messages detailed diagnostic table
•
Error messages sum diagnostic table
The possibility exists of assigning individual diagnostic information items, or with the help of
wildcards, a group of diagnostic information items (all diagnostic classes, -records, -bits) to a
message. If a group of diagnostic information items is assigned to a message, a logical OR for
all diagnostic information concerned is created automatically.
3.3.8.1
Error Messages Detailed Diagnostic Table
The assignment of the diagnostic information or a group of diagnostic information items to the
message with process information is performed with the help of process-technical parameters
of the ACP 1703 system data by means of selection texts in Drop-Down List boxes or by the
input of values:
•
Message address
•
Lk_Bse (basic system element)
•
SSE (supplementary system element)
─ (PE0 - PE15, PRE0 - PRE3) or
─ BSE itself.
•
Diagnostic class
─ Internal, External, Communication, Test, Module Failure, Warning, Startup or
─ Wildcard (all Bits, all Records, all Classes). The content of both parameters
Diagnostic record and Diagnostic bit are meaningless.
•
Diagnostic record
─ Record number within the selected class or
─ Wildcard (all Bits, all Records). The content of the parameter Diagnostic bit is
meaningless.
•
Diagnostic bit
─ Bit 0 .. Bit 15 or
─ Wildcard (all Bits)
Note
The significance of the diagnostic records and the diagnostic bits is dependent on the configured system
element and is to be taken from the relevant system element manual.
Attention
These parameters are not mirror parameters, i.e., these parameters are not copied with the TOOLBOX II
- function "Copy BSE". This is necessary, since otherwise the diagnostic information would be distributed
with the same message address but of different quality.
34
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02
System Services
3.3.8.2
Error Messages Sum Diagnostic Table
The assignment of the diagnostic information to the message with process information is
performed with the help of process-technical parameters of the ACP 1703 system data by
means of selection texts in Drop-Down List boxes:
•
Message address
•
Error location/basic system element
•
Error location/supplementary system element
•
Error type
Parameter
Error
Location/BSE
Error
Location/SSE
from the sum diagnostic
record of the automation
unit
AU sum
BSE itself / AU sum /
Rest system
Class internal, external,
communication, test,
warning, module failure,
startup
from the sum diagnostic
record of a basic system
element
C0-CPU ... C16-CPU, BSE itself / AU sum /
M-CPU
Rest system
Class internal, external,
communication, test,
warning, module failure,
startup
Failure of a basic system
element
C0-CPU ... C16-CPU
System element failure
Fault of a basic system
element
C0-CPU ... C16-CPU, BSE itself / AU sum /
M-CPU
Rest system
System element fault
Failure of a peripheral
element
C0-CPU ... C16-CPU, PE 0 .. PE15
M-CPU
System element failure
Fault of a peripheral
element
C0-CPU ... C16-CPU, PE 0 .. PE15
M-CPU
System element fault
Failure of a protocol
element
C0-CPU ... C16-CPU, PRE 0 .. PRE3
M-CPU
System element failure
Fault of a protocol
element
C0-CPU ... C16-CPU, PRE 0 .. PRE3
M-CPU
System element fault
Failure of a
communication line
C0-CPU ... C16-CPU, PRE 0 .. PRE3
M-CPU
Communication failure
Fault of a communication
line
C0-CPU ... C16-CPU, PRE 0 .. PRE3
M-CPU
Communication fault
from the sum diagnostic
record of the rest system
Rest system
Class internal, external,
communication, test,
warning, module failure,
startup
Diagnostic Information
BSE itself / AU sum /
Rest system
BSE itself / AU sum /
Rest system
Error Type
Attention
These parameters are not mirror parameters, i.e., these parameters are not copied with the TOOLBOX II
- function "Copy BSE". This is necessary, since otherwise the diagnostic information are distributed with
the same message address but of different quality.
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
35
System Services
3.4
General Interrogation
On startup of an automation unit or individual system elements or after faults in the system
(communication faults, FIFO overflows) the participating automation units or system elements
ensure, that the operation is resumed automatically in a coordinated manner.
This means, that the external and internal communication connections are set up and all data
points concerned, and relevant system information for the system-wide updating of the
process images are transmitted from their source right to their sink. This takes place with the
initiation of a station interrogation to the corresponding part of the automation network, where
the error occurred.
In which kind the station interrogations are triggered and how messages with interrogated
process information are processed can bees seen in the various sections describing the
functions (e.g. communication).
In the following cases a station interrogation is tripped automatically:
•
Station interrogation "all CASDU´s"
─ after POWER UP or RESET of a system element
─ after POWER UP or RESET of an automation unit
─ after communication failure
─ after redundancy switchover to active
•
Station interrogation "selective CASDU"
─ after receipt of the message "End of initialization" for the corresponding CASDU
•
Station interrogation to sources within the automation unit
─ after internal data loss (e.g. FIFO overflow)
─ after the loading of newly added routings or assignments
The transmission of "all data concerned" means, that
•
with the station interrogation, all GI-capable messages with process information are
transmitted, i.e. all those data, that can be interrogated with their state in the periphery and
from processing functions (binary information, analog values, digital values, calculated
values etc.) or system information (system error information),
•
in a multi-hierarchical network, with a station interrogation not only the local data of an
interrogated automation unit are transmitted, but also those of automation units
hierarchically subjacent and reachable over external communication,
•
invalid or blocked data (value disturbances, information affected with the failure of a
system element or failure of an automation unit) are also to be transmitted with a station
interrogation.
Special system-wide applicable mechanisms ensure, that
36
•
with a GI-request, only those data are transmitted, which the requesting station requires.
•
dependent on the process data to be transmitted, the station interrogation is possible both
in monitoring- as well as in control direction.
•
due to consequential reactions with the occurrence of a station interrogation initiation,
above all in multi-hierarchical networks, no more than one station interrogation is
performed (although e.g. with the restart of an automation unit, due to the communication
failure associated with it, several other automation units would have a station interrogation
initiation)
•
with the simultaneous occurrence of several station interrogations, an unnecessary load of
the communication is prevented.
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02
System Services
•
in the event of a station interrogation, the data according to IEC 60870-5-101/104 are
transmitted in blocks, in order to achieve a considerably more efficient transmission. the
condition for this is, that the message addresses (IOA) are defined successively without
gaps.
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
37
System Services
3.5
Failure
In single and in multi-hierarchical configurations, the failure management ensures, through the
monitoring of the internal and external interfaces, the marking of the data points affected by a
failure and the generation of diagnostic information.
3.5.1
Monitoring of the Interfaces
The monitoring of the internal and external interfaces takes place with periodical monitoring
messages. These monitoring messages are generated and monitored by the system elements
or automation units at both sides of the interface. The periodicity is dependent on the
interface.
Interface
Time Period
Maximum Detection Time of the
Failure
Peripheral modules
TM Bus
10 ms
20 ms
Peripheral elements (HWDefect)
Ax 1703-PE Bus
10 ms
40 ms
Peripheral elements (FWError)
Ax 1703-PE Bus
5s
10 sec
Protocol elements
SBD-Bus
500 ms
1.5 sec
Basic system elements
N-Bus
500 ms
1.5 sec
Basic system elements
Redundancy
synchronization
link
can be set by
parameter
in 100ms
steps
starting at
100ms
Normal operation:
set monitoring time 1) + 10ms
Communication
line
can be set by
parameter
Dependent on the parameterized
baud rate, the time for monitoring
messages and the message
repetitions
Automation unit
During synchronization of the
application program
set monitoring time 1) * 5
1)
Parameter Redundancy | Synchronisation parameter | Red_sync monitoring
timeout
3.5.1.1
Measures in the Event of an Error
If the failure of a higher-level system element is detected, the particular system element and
all lower-level system elements are brought to the state "Firmware Shut Down".
Exception: Autonomous basic system elements (see Autonomy)
38
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02
System Services
3.5.2
Mark Data Points Affected by the Failure
After the detection of the failure of system elements or automation units, all data points
affected by this failure at the system-internal sinks (e.g. open-/closed-loop control function,
peripheral elements) or at the communication interfaces to other automation units
(communication function in transmit direction) are flagged with "not topical".
The data points are only then flagged with "not topical", if the failure is present for longer than
a parameterized time. This parameter AU common settings | Delay time NT
reproduction can be set one time for the automation unit.
Possibly available redundancy configurations are thereby taken into account.
Redundancy Configuration
With a redundancy configuration, the data point is first flagged as failed, when all redundant
sources which this data point affects, have been detected as "failed".
Redundant sources are:
•
Communication interfaces which receive this data point from other automation units
(communication function in receive direction)
•
Sources within the automation unit which generate this data point (e.g. open-/closed-loop
control function, peripheral elements)
In addition, all redundant sources at each system-internal sink and at all communication
interfaces to other automation units are learned for all data points to be handled at these
places.
A maximum of 8 redundant sources can be learned. With the help of the parameter BSE
common settings | Maximum number of redundant sources an optimization of the
memory requirements can be performed.
Special Cases
If the data point is not to be transferred from all redundant sources or more than 8 redundant
sources are required, the automatic learning can be switched off. For this, all redundant
sources that are relevant for this data point, are compiled to form a so-called RedundancySource-Identification.
This is carried out by assigning all relevant redundant sources to a Redundancy-SourceIdentification with the help of the topology parameter RQID (Redundancy-SourceIdentification).
A maximum of 254 Redundancy Source Identifications can be defined.
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
39
System Services
3.5.3
Diagnostic Information
After the detection of the failure of system elements or automation units, the corresponding
diagnostic information are set.
For a system element failure, the corresponding diagnostic information "Module failure" is set.
If the communication connection to a remote station fails, the corresponding diagnostic information "Failure of the automation unit" is set. The diagnostic information "Failure of the
automation unit" is also set, if a system element fails, which lies on the path to this automation
unit. These system elements are normally basic system elements with communication
function or protocol elements. With the diagnostic information "Failure of the automation unit",
possibly existing redundancy configurations are taken into account.
These diagnostic informations are however only set, if the failure is present for longer than the
parameterized AU common settings | Delay time failure reproduction. This
parameter can be set one time for the automation unit.
Redundancy Configuration
With a redundancy configuration, the corresponding diagnostic information "Failure of the
automation unit" is first set, if all communication connections over which this automation unit
can be reached, have failed.
The parameter AU common settings | Delay time failure reproduction is also
effective in this case.
The failure of the communication connection or a system element is signaled immediately
with a diagnostic information regardless of the redundant sources.
40
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02
System Services
3.6
Data Storage on Flash Card
All firmware and parameters of an automation unit are stored non-volatile on a Flash Card.
This Flash Card is a permanent component of the master control element.
On startup of the automation unit or individual system elements, the firmware and the
necessary parameters are transmitted from the Flash Card to the system elements.
The Flash Card enables the exchange of a module without using the TOOLBOX II.
3.6.1
Module Exchange
With all system elements – except master control element – after the exchange of the module,
no further operator inputs are required. All firmware and parameters are transmitted
automatically to the exchanged module.
If the master control element is exchanged, in addition the Flash Card from the defective
module is to be slotted into the exchanged module.
After an exchange of modules, during startup of the automation unit or a system element,
calibration processes take place between the Flash Card and the system elements. These
calibration processes cause longer startup times and are indicated on the front panel by the
LED "CPY" (see chapter Operating States "Loading Operation").
further cases for a calibration process:
3.6.2
•
Revision of the firmware different between Flash-Card and system element
•
Type of the firmware different between Flash-Card and system element
•
No firmware loaded on the system element
•
Revision of the parameters different between Flash-Card and system element
•
No parameters loaded on the system element
Commissioning an Automation Unit
For the initial commissioning of an automation unit, at least one blank, formatted Flash Card
with a FAT 16 file system is required.
If a formatted, blank Flash Card is detected by the master control element, the master control
element goes to the state "Firmware Shut Down". This state can however not be diagnosed
with the TOOLBOX II, but rather is only indicated by the flashing of the possibly available
"HLT" LED on the front panel. With system elements without the "HLT" LED, this state can not
be clearly detected.
To make the automation unit operational, the automation unit must be initialized and all
firmware and parameters loaded with the TOOLBOX II Toolset PSR II.
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
41
System Services
3.6.3
Startup of an Automation Unit with Missing or Defective Flash
Card
If the Flash Card is missing or defect, the startup of an automation unit takes place with the
firmware and parameters possibly available on the system elements. After startup a diagnostic
information is set, in order to indicate this inadmissible state.
Attention
If this inadmissible state is ignored, it can lead to faulty behavior of the automation unit. This state can be
compared to when parameters are loaded, that do not correspond to the process connected to the
automation unit.
42
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02
System Services
3.7
Autonomy
Autonomy means, that an autonomous basic system element and its supplementary system
elements (protocol- and peripheral elements) continue to function during the failure of the
master control unit.
This behavior can be set for each basic system element by means of a parameter BSE
common settings | Autonomy.
On failure of the master control unit, data points are flagged with "not topical", which:
•
are acquired by other system elements in the automation unit and are not acquired over
the particular peripheral- or protocol elements.
•
are acquired by other automation units and not connected over the particular protocol
elements.
After startup of the master control unit, the autonomous basic system element is synchronized
without interruption to operation. Due to a general interrogation, the data points flagged with
“not topical” on failure of the master control unit are updated.
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
43
System Services
3.8
Communication with the Engineering System
(TOOLBOX II)
For the communication between the TOOLBOX II and the destination system there are
different variants:
•
direct local over the serial Toolbox interface (TB) on the master control element
•
over a network connection LAN/WAN (TCP/IP)
•
over serial remote communication connection from and to other automation units.
With the exception of the very first initialization operation, this is only possible with a direct
local connected TOOLBOX II, all tasks are possible in each of the above stated variants:
44
•
Upload parameters
•
Diagnostic
•
Test (e.g. Online-Test of the function diagram) and
•
Load firmware
•
etc.
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02
System Services
3.9
Self-Test
The self-test is used for the protection against inadmissible operating states. Through a series
of monitoring operations, defects of the hardware used or faulty behavior of the firmware are
detected.
3.9.1
Monitoring of Hardware and Firmware
Timeout monitoring (watchdog)
Protection against
defect of the CPU used and
faulty behavior of the firmware
Monitored by
Hardware and firmware
Function
The processor and the firmware running on it is monitored by a
watchdog. This watchdog is an independent hardware monoflop,
which must be retriggered in a defined time window by the
firmware.
The status of the CPU watchdog is signaled optically on the front
of the module via a yellow LED with the designation "RY". In
addition, the watchdog status is conducted on a relay. If the
watchdog is started up, the relay is activated (closed-circuit
principle). On the connector strip, the relay contacts (open- and
closed contact) can be unclipped.
Measure in case of error
The relay "Watchdog" is deactivated with the expiry of the
hardware monoflop.
The firmware initiates a reset of the system element. After
startup, the system element is switched to the "Firmware Shut
Down" state.
Dynamic behavior
up to 20ms
IDLE monitoring
Protection against
Faulty behavior of firmware or application programs with endless
loops, firmware execution times too long etc.
Monitored by
Firmware
Function
In the IDLE-Task (low priority task of the operating system) a
firmware monoflop is retriggered with a time base of 5 seconds.
As long as this firmware monoflop is started up, the retriggering
of the watchdog is enabled.
Measure in case of error
The watchdog is no longer retriggered. Further procedure see
Monitoring of Hardware and Firmware.
Dynamic behavior
up to 5 sec
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
45
System Services
Code memory monitoring
Protection against
defect of the storage medium used (Flash-PROM or Flash-Card)
and
undetected transmission errors when loading the program code
Monitored by
Firmware
Function
With the creation of all bytes of the code area through addition,
including the free bytes up to the end of the physical storage
medium, a 16-bit checksum MODULUS 65536 is formed. This is
stored on a free storage space in the code area of the firmware.
During startup and in operation in the IDLE Task, all bytes in the
storage medium are added and compared with the stored
checksum.
Measure in case of error
With inequality, the system element is switched to the "Module
Shut Down" state.
Dynamic behavior
During startup, the error is detected immediately.
During normal operation, it may take a few seconds until the error
is detected.
In operation, typically another measure of protection is effective
(e.g.
Illegal Opcode, Monitoring of Hardware and Firmware )
Parameter memory monitoring
Protection against
defect of the storage medium used (Flash-PROM or Flash-Card)
and
undetected transmission errors when loading the parameters
Monitored by
Firmware
Function
For each available parameter block a 16-bit checksum
MODULUS 65536 is created by the TOOLBOX II and entered in
the parameter block.
During startup, in operation in the IDLE-Task and always when
this parameter block has been loaded from the TOOLBOX, all
bytes of every parameter block are added (algorithm as offline)
and compared with the stored checksum.
Measure in case of error
With inequality of one of the checksums, the system element is
switched to the "Firmware Shut Down" state.
Dynamic behavior
During startup and after being loaded by the TOOLBOX II, the
error is detected immediately.
During normal operation, it may take a few seconds until the error
is detected.
In operation, with an error in the application program of the open/closed loop control function, typically another measure of
protection is effective (e.g.
Illegal Opcode, Monitoring of Hardware and Firmware.
Firmware self-monitoring
46
Protection against
incorrect call parameters with system functions and programming
errors
Monitored by
Firmware
Measure in case of error
The system element is switched to the "Firmware Shut Down"
state.
Dynamic behavior
The error is detected immediately.
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02
System Services
Shadow RAM
Protection against
defect of the storage medium used (DRAM) and
defect of the DRAM refresh logic implemented
Monitored by
Hardware
Measure in case of error
With inequality, the system element is switched to the "Module
Shut Down" state.
Dynamic behavior
The error is detected immediately.
RAM test with addressing errors check
Protection against
Defect of the storage medium used (DRAM),
Defect of the READ/WRITE equipment,
Defect of the RAM´s in a defined area,
Defect of the DRAM refresh logic implemented and
Short or interruptions on the data and address bus
Monitored by
Firmware
Measure in case of error
The system element is switched to the "Module Shut Down"
state.
Dynamic behavior
During startup, the error is detected immediately.
During normal operation, it may take a few seconds until the error
is detected.
Monitoring forbidden memory access
Protection against
Firmware errors
Monitored by
CPU exception handling
Measure in case of error
The firmware initiates a reset of the system element. After
startup, the system element is switched to the "Firmware Shut
Down" state.
Dynamic behavior
The error is detected immediately.
Monitoring forbidden I/O access
Protection against
Firmware errors when accessing the I/O address range, and
Hardware errors
Monitored by
CPU exception handling
Measure in case of error
The system element is switched to the "Firmware Shut Down"
state.
Dynamic behavior
The error is detected after 1µs
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
47
System Services
Illegal Opcode
Protection against
Firmware errors with e.g. jump operations,
Defect of the storage medium used (Flash-PROM),
Defect of the READ equipment and
Short or interruptions on the data- and address bus
Monitored by
CPU exception handling
Measure in case of error
The firmware initiates a reset of the system element. After
startup, the system element is switched to the "Firmware Shut
Down" state.
Dynamic behavior
The error is detected immediately.
Stack Overflow
Protection against
Firmware errors
Monitored by
Mode 1: CPU exception handling
Mode 2: Firmware
Measure in case of error
Mode 1: The system element is switched to the
"Module Shut Down" state.
Mode 2: The system element is switched to the
"Firmware Shut Down" state.
Dynamic behavior
Mode 1: The error is detected immediately.
Mode 2: It takes a few seconds until the error is detected.
3.9.2
Monitoring the Data Integrity
Messages with spontaneous information objects on internal interfaces
48
Protection against
Defect of the storage medium used (FIFO) and
internal communication errors
Monitored by
Firmware
Function
Every message that is sent over the internal buses is secured
with a checksum. This is carried out by adding all bytes of the
message with an 8-bit (Ax 1703 PE Bus) checksum MODULUS
256 or words of the message with a 16-bit (node- and SBD-Bus)
checksum MODULUS 65536.
Measure in case of error
With inequality between the received and calculated checksum,
the transmission to the remote station is discontinued.
Dynamic behavior
The error is detected immediately.
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02
System Services
Messages with periodical information on the Ax 1703 PE Bus
Protection against
Ax 1703 PE bus communication errors
Monitored by
Hardware
Hamming distance
4
Function
Every message that is sent over the Ax 1703 PE Bus is secured
through a longitudinal- and vertical parity.
Measure in case of error
With inequality between the received and calculated parity, the
transmission to the remote station is discontinued.
Dynamic behavior
The error is detected immediately.
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
49
System Services
3.10
3.10.1
Operating States
Operating State
LED "RY"
LED "ER"
LED "HLT"
LED "CPY"
Normal Operation
lights up
dark
dark
dark
Limited Operation
lights up
lights up
dark
dark
Loading Operation
Loading parameters
Saving parameters
not relevant
not relevant
not relevant
not relevant
not relevant
not relevant
dark
flashes
Load firmware and save
(indication on the master control unit
only)
not relevant
not relevant
not relevant
lights up
Firmware Shut Down
dark
lights up
flashes
dark
Module Shut Down
dark
lights up
lights up
dark
Normal Operation
Normal operation means, that all parameterized functions run correctly.
This state is indicated for each system element as follows:
LED "RY"
LED "ER"
LED "HLT"
LED "CPY"
lights up
dark
dark
dark
In addition, further LED’s can light up (dependent on the system element), e.g. for the display
of process signals, status lines of the communication interface.
3.10.2
Limited Operation
Limited operation means, that not all parameterized functions run correctly.
This state is indicated for each system element as follows:
LED "RY"
LED "ER"
LED "HLT"
LED "CPY"
lights up
lights up
dark
dark
In addition, for the error detection further LED’s can also light up (dependent on the system
element).
The faulty parts of the automation unit are identified and if necessary deactivated. The nonfaulty functions continue to work normally (error tolerance) as long as they are not affected by
the faulty functions.
50
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02
System Services
Examples:
•
Communication to the higher-level automation unit or control system failed; the automation
unit continues to run autonomously.
•
Peripheral element failed; data points of the failed peripheral element are flagged with "not
topical" and transmitted, all other peripheral elements continue to work normally.
With the TOOLBOX II a detailed diagnostic of the error is possible.
3.10.3
Loading Operation
During the loading operation, parameters and firmware programs in the automation unit are
brought up to date. The loading operation can either be started by means of the TOOLBOX II
or takes place automatically on startup of the automation unit or a system element (see
chapter "Startup").
If the loading operation is controlled by the TOOLBOX II, there are two separate states:
•
the loading operation
•
the saving of the parameters and the firmware program
Loading operation
The loading operation is initiated by the TOOLBOX II, if a difference between the parameters
or firmware saved on the Flash-Card and those currently in the TOOLBOX II has been
detected.
This state is indicated for each system element as follows:
LED "RY"
LED "ER"
LED "HLT"
LED "CPY"
Parameter
not relevant
not relevant
not relevant
dark
Firmware (indication on the master
control unit only)
not relevant
not relevant
not relevant
lights up
Saving the parameters and the firmware program
The parameters and firmware updated through the loading operation are programmed in the
Flash-PROM on the corresponding basic system element and saved on the Flash-Card.
This state is indicated for each system element as follows:
LED "RY"
LED "ER"
LED "HLT"
LED "CPY"
Parameter
not relevant
not relevant
not relevant
flashes
Firmware (indication on the master
control unit only)
not relevant
not relevant
not relevant
lights up
Attention
A switching off or reset of the automation unit during the saving of the parameters and firmware program
on the Flash-Card is to be absolutely avoided. In the most unfavorable case an exchange of the master
control element is necessary.
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
51
System Services
3.10.4
Firmware Shut Down
Firmware shut down means, that all functions with the exception of those that are necessary
for the communication with the TOOLBOX II in the local operating mode, are halted.
In this state the watchdog of the module elapses and all outputs are terminated.
This state is indicated for each system element as follows:
LED "RY"
LED "ER"
LED "HLT"
LED "CPY"
dark
lights up
flashes
dark
With system elements without the "HLT" LED, this state can not be clearly detected.
Attention
If the shut down of the firmware takes place due to "Illegal opcode", "General protection" and "Watchdog
elapsed", this is indicated by the possibly available "CAE" LED on the front panel.
On occurrence of this state, a diagnostic information is set with an error code. If a remedy is
possible by the user, an additional diagnostic information is set.
This state can now only be ended with a Power up or Reset. The reset can be tripped both by
the TOOLBOX II as well as with the reset button on the master control unit.
Depending on the parameter BSE common settings | Failure behavior with
Firmware shut down: this state is retained until a Power up or Reset. The reset can be
tripped both by the TOOLBOX II as well as with the reset button on the master control unit.
Firmware restart:
a system startup is initiated due to an automatic reset tripped by the
firmware. If such a procedure occurs 3 times inside 30 minutes, the system element remains
in the "Firmware shut down" state.
3.10.5
Module Shut Down
Module shut down means, that all activities of the hardware and firmware are halted.
This state is indicated for each system element as follows:
LED "RY"
LED "ER"
LED "HLT"
LED "CPY"
dark
lights up
lights up
dark
In this state the watchdog of the module elapses and all outputs are terminated.
This state can now only be ended with a Power up or Reset. The reset can be tripped by the
TOOLBOX II (if this state does not affect master control unit) or with the reset button on the
master control unit.
52
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02
4
Telecontrol
Content
4.1
Introduction.........................................................................................................54
4.2
Communication with other automation units ......................................................55
4.3
Protocol Element Control and Return Information .............................................71
4.4
Decentralized Archiving......................................................................................74
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
53
Telecontrol
4.1
Introduction
The function package Telecontrol includes the following functions:
•
Process input and output on peripheral elements
•
Communication with other automation units
─ Automatic data flow routing
─ Data storage
─ Priority control
•
Protocol elements
•
Redundant communication routes
•
Communication within the automation unit
•
Protocol element control and return information
•
Decentral archive
The functions for process input and output on peripheral elements are described in detail in
the document 1703 Common Functions Peripheral Elements according to
IEC 60870-5-101/104
The functions for protocoll elements are described in detail in the document
1703 Common Functions Protocoll Elements
54
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02
Telecontrol
4.2
Communication with other automation units
The communication function controls the transmission of messages via protocol elements to
other automation units or control systems.
A protocol element is based on hardware integrated in a basic system element or on a serial
interface module (SIM) that can be installed on a basic system element for serial, LAN/WAN
and field bus communication and supports standard protocols according to
IEC 60870-5-101/103/104 and a large number of protocols for the communication with thirdparty systems.
The communication function differentiates between transmission and receive direction.
Communication function 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 controller in order to optimally utilize the transmission route.
•
Automatic data flow routing
•
Data storage
•
Priority control
Communication function in receive direction
•
Messages with process information are distributed to all functions within the automation
unit.
•
Messages with system information are either processed directly (e.g. station interrogation)
or distributed further based on their destination address (CASDU) (e.g. messages for
remote maintenance).
Thereby maximum 4 protocol elements are supported per basic system element. The
equipment of the protocol elements depends on the basic system element.
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
55
Telecontrol
4.2.1
Block Diagram
Internal distribution of messages with process information
Internal distribution of messages with system information
Transmit direction
Automatic data flow
routing
Data storage
e.g. GI
Priority controller
Protocl element
Link
Message reception
Receive direction
Messages with process information
Messages with system information
56
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02
Telecontrol
4.2.2
Automatic Data Flow Routing
For the automatic 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, is to be parameterized.
The type identification of each message provides information about the class (refer to
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
─ In simple applications, the messages are distributed via an entry in the topology.
─ For more complex applications, the messages can be distributed selectively with the
help of the data flow filter. 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.
Messages with system information in the private range are distributed based on their systemtechnical destination address. Which automation unit is reached over which interface is to be
defined in the topology parameters.
For the correct function of the automatic data flow routing, the following points are to be
adhered to
•
Messages with process information in monitor direction according to IEC 60870-5-101 or
104 are to be defined with a CASDU, which represents the source address. The address
element IOA can be freely selected.
•
Messages with process information and messages with system information in control
direction according to IEC 60870-5-101 or 104 are to be defined with a CASDU, which
represents the source address. The address element IOA can be freely selected.
•
A process-technical unit can occur in one or several system-technical unit(s). I.e. one or
several automation units can represent one CASDU.
•
Several process-technical units can occur in one system-technical unit. I.e. one
automation unit can represent several CASDU´s.
Note
Messages with process information, which are received via an interface with a LAN, are not send to
this interface (prevention of circulating messages). If nevertheless received messages with process
information must be transferred over this LAN, this must be applicably resolved by the generation of new
messages with process information with the help of the open-/closed-loop control function.
4.2.2.1
Messages in Control Direction
Messages with process information in control direction and messages with system information
are distributed based on their CASDU.
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
57
Telecontrol
For this, information is necessary which specifies, over which communication interface and
which station or connection the automation unit(s) can be reached, which this CASDU
contains.
This information is learned from messages with process information in monitor direction, by
storing the CASDU and the system-technical entry point (source identification) of these
messages. To make this procedure possible, GI-capable messages with process information
in monitor direction must be received with the corresponding CASDU from this systemtechnical entry point.
For messages with process information in control direction which are defined with cause of
transmission set to "activation", the origin address is used for directing the replies
("confirmation"). If the origin address is used, it must be unambiguous for each source. The
origin address can be parameterized for each connection or station. This parameterized origin
address is then always added if the origin address is not defined in the received message
(origin address = 0). If the origin address is neither validly parameterized nor defined in the
message, the replies to this message are distributed to all communication interfaces which are
defined as monitor direction in the topology.
If the data flow direction for a communication interface is defined with “both directions” in the
topology, all messages with process information in control direction and messages with
system information in control direction are distributed on principal to this communication
interface regardless of the CASDU contained in the message.
4.2.2.2
Messages in Monitor Direction
The simplest possibility of directing is the entry in the topology, which defines the data flow
direction. This represents a pass-through filter over which communication interface messages
with process information in monitor direction are required.
If this simple form of directing is inadequate, the possibility of a data flow filter exists. This is
defined in the system-technical parameter Data flow filter. In the data flow filter, pass
through- and blocking filters are possible for address elements such as CASDU, IOA and/or
type identification with wildcard specifications. The specification can take place for each octet
of the address elements. With this method, selective groups of messages with process
information in monitor direction can be routed or blocked to the communication interfaces.
Topology parameters
"data flow direction"
Monitor direction
not
Monitor direction
Blocking filter
Data management of the communication function
Internal distribution of messages with process information
The data flow filter affects exclusively messages with process information in monitor direction,
in addition to the defined data flow direction. I.e. a data flow filter affects the data flow direction
defined for these messages. First pass through filters are evaluated in parallel and
subsequently blocking filters in series.
Pass through filter
Reasonable filters are dependent on the data flow direction:
58
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02
Telecontrol
•
Blocking filters in monitor direction
•
Pass through filters in control direction
If individual messages with process information in monitor direction are also required for
cross-couplings in the control direction, in principle these must be defined with data flow
filters.
To modify a data flow filter, a reset of the automation unit is necessary. The routings are relearned with each startup.
4.2.2.3
Messages in the Private Range
In principle, these can only be distributed by way of the data flow routing. The definition of the
data flow direction in the topology parameters is not effective for these messages.
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
59
Telecontrol
4.2.3
Data Storage
Messages that are intended for transmission over communication interfaces, are in principle
stored chronologically 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)
Specifically reduces 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 direction
Messages that are stored too long in the priority channel are discarded
60
•
Answering of station interrogations
•
Behavior during failure of peripheral elements, communication interfaces etc.
•
Blocking (series of information elements)
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02
Telecontrol
4.2.3.1
Message Characteristics
This table provides an overview about the characteristics of the messages.
Message with process information
in monitor direction
TI
GI
VWZ
ZV
PRI
Single-point information
1,2,30
YES
NO
NO
UEW
Double-point information
3,4,31
YES
NO
NO
UEW
Step position information
5,6,32
YES
NO
PAR
UEW
Bitstring of 32 bit
7,8,33
YES
NO
NO
UEW
Measured value, normalized value
9,10,34
YES
NO
PAR
UEW
Measured value, scaled value
11,12,35
YES
NO
PAR
UEW
Measured value, short floating point
number
13,14,36
YES
NO
PAR
UEW
Integrated totals
15,16,37
NO
NO
NO
UEW
Event of protection equipment
17,38
NO
NO
NO
UEW
Blocked activation of the protection
18,39
NO
NO
NO
UEW
Blocked triggering of the protection
19,40
NO
NO
NO
UEW
Packed single-point information with status
change detection
20
-
-
-
-
The message "Packed single-point information with status change detection" not supported !
Message with process information
in control direction
TI
GI
VWZ
ZV
PRI
Single command
45,58
NO
YES
NO
BEF
Double command
46,59
NO
YES
NO
BEF
Regulating step command
47,60
NO
YES
NO
BEF
Set point command, normalized value
48,61
NO
YES
NO
BEF
Set point command, scaled value
49,62
NO
YES
NO
BEF
Set point command, short floating point
number
50,63
NO
YES
NO
BEF
Bitstring of 32 bit
51,64
NO
YES
NO
BEF
Message with system information
in control direction
TI
GI
VWZ
ZV
PRI
Interrogation command
100
NO
NO
NO
SYS
Counter interrogation command
101
NO
NO
NO
SYS
Clock synchronization command
103
NO
NO
NO
ZS
Messages with transparent information
TI
GI
VWZ
ZV
PRI
Container for system information
135
NO
NO
NO
SYS
Container for process information
142
NO
NO
NO
TR
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
61
Telecontrol
Legend:
TI
…
GI
…
VWZ …
ZV …
PRI …
heading of column
Type identification
GI-capable
dwell-time-monitored
state-compressed
Priority channel
content of column
ZS …
Priority channel for clock-time synchronization
SYS …
Priority channel for system information
BEF …
Priority channel for process information in control direction
UEW …
Priority channel for process information in monitor direction
TR …
Priority channel for transparent information
PAR ...
adjustable with parameters (default YES)
4.2.3.2
Data Storage of Process Information
If a message with process information is determined for transmission, the process image
before the ring is updated and entered in the ring in the correct time sequence. An updating of
the process image only takes place for GI-capable messages with process information.
4.2.3.2.1 State Compression
So as not to load the transmission path unnecessarily with e.g. floating measured values, with
certain messages no chronological storage takes place, rather a state compression. I.e. if a
data point is already in the ring, then it is overwritten with that currently received. This only
occurs if the message status, the cause of transmission and the origin address are identical.
State compression can be disabled for each type identification of the following messages
using the parameter
•
TI 32 Step position information
AU common settings | Settings for type identification |
TI 32 Step position information | State compression
•
TI 34 Measured value, normalized value
AU common settings | Settings for type identification |
TI 34 Measured value, normalized value | State compression
•
TI 35 Measured value, scaled value
AU common settings | Settings for type identification |
TI 35 Measured value, scaled value | State compression
•
TI 36 Measured value, short floating point number
AU common settings | Settings for type identification |
TI 36 Measured value, short floating pt. number | State compression
4.2.3.2.2 Behavior with a Priority Channel Overload
If a GI-capable message with process information can no longer be entered in the priority
channel, the process image before the ring is updated with the process information and
flagged with data loss. A non-GI-capable message with process information or a message
with system information is discarded. This situation is reported issuing the diagnostic
information "ring x overflow".
62
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02
Telecontrol
If the priority channel is free again, then depend on the parameter
Communication | PRE# | Advanced settings | Behaviour for messages from a
source GI all process information flagged with data loss are transferred with cause of
transmission set to "spontaneous" or with cause of transmission set to "background scan".
4.2.3.2.3 Behavior During a Communication Failure
With a failure of the remote station, it can be specified for each protocol element, how long the
messages currently queued for transmission remain stored in the priority channels during a
communication failure.
The behavior can be set via the parameter Communication | PRE# | Advanced
settings | Failure behavior for process inform. with:
•
Delete priority channels immediately
•
Delete priority channels after a parameterized time (range 1 sec. to approx. 18 hours)
•
Do not delete priority channels
and via the parameter Communication | PRE# | Advanced settings | Failure
behavior for transparent info. with:
•
Delete priority channels immediately
•
Do not delete priority channels
As long as the communication failure exists, no further data is entered in deleted priority
channels. The process image before the ring is updated with the process information.
After a going communication failure, messages not yet entered into the ring or deleted from
the ring, are sent with their current status from the process images before the ring and in
depend of the parameter Communication | PRE# | Advanced settings | Behaviour
for messages from a source GI with cause of transmission set to “spontaneous” or with
cause of transmission set to "background scan".
4.2.3.2.4 Dwell Time for Messages with Process Information
The dwell time for messages with process information in control direction defines how long a
message with process information in control direction may be stored in the priority channel.
A maximum dwell time for messages with process information in control direction can be
determined via the parameter AU common settings | Dwell time for msg. in
command direction for each automation unit.
If the message has been stored longer than the parameterized time in the priority channel
before it could be transmitted, it is discarded without error information.
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
63
Telecontrol
4.2.3.2.5 Station Interrogation
After reception of an interrogation command from a remote station, all GI-capable messages
with process information that match the interrogated CASDU (selective or all) and which are
determined for this remote station are activated for transmission.
Only the station interrogation (global) is supported as interrogation identification.
These messages are provided with their last transmitted status and cause of transmission set
to "interrogated by station interrogation".
These messages are generally transmitted without time stamp and, if possible, packed.
For each running station interrogation of an interrogating station, a maximum of one further
(general-) interrogation command is stored for the currently processed CASDU.
If a message is transferred to the communication function in transmit direction with the cause
of transmission "background scan" or "interrogated with station interrogation", in depend of
the parameter Communication | PRE# | Advanced settings | Behaviour for
messages from a source GI a comparison with the last transmitted state takes place or
not.
Parameter is change monitoring
The change comparison is carried out over all elements of the spontaneous information
object, except for the cause of transmission and the time information. Only with change is the
message activated for transmission with the cause of transmission "spontaneous".
Parameter is data transfer
The message will be send with the cause of transmission "background scan"
4.2.3.2.6 Failure Management
With a failure of a message source (e.g. periphery elements, communication interfaces), all
affected GI-capable messages with process information are flagged "not topical". The affected
messages are provided with the current time and activated for transmission with cause of
transmission set to "spontaneous". The transmission takes place with the last stored process
status.
64
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02
Telecontrol
4.2.3.2.7 Blocking
The blocking is carried out according to the procedure described in the standard IEC 60870-55 as a result of information elements.
The prerequisite for blocking is, that
•
the type identification,
•
the common address of the ASDU,
•
the cause of transmission and
•
the origin address
match.
The number of spontaneous information objects to be blocked is determined in bytes by the
parameter Communication | PRE# | IEC60870-5-101/104 | Variable elements of
the message | Maximum message length.
4.2.3.3
Data Storage for Transparent Information
Messages with transparent information (such as e.g. containers with process information etc.)
are stored in an own priority channel without process images.
With a priority channel overload, the messages are discarded and the overload is signaled
with a diagnostic information. The error is first reset when the priority channel is empty.
Whether this priority channel is to be deleted during a communication failure can be set by a
parameter (see "Behavior During a Communication Failure").
4.2.4
Priority Control
The priority controller has the task of selecting messages recorded in the data memories
independently 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 several informations queued at the same time, 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, the lower priority data can also be transmitted.
The classification according to data class 1 and data class 2 only has an effect on the dial-up
traffic.
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
65
Telecontrol
The priority channels are subdivided into the following priority levels:
Priority
Priority level
high
Time synchronization
System information and process information in monitor direction
interrogated by general interrogation
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
low
transparent Information
For messages with process information in monitor direction priority categories (see following
table) are defined. Each of these priority categories can be assigned one priority level
(process information in monitor direction Priority HIGH with class 1 data, MEDIUM or LOW
with class 2 data) via parameter (parameter group Communication | PRE# | Advanced
settings | *).
It is possible to assign the same priority level to several priority categories.
For the messages with process information in monitor direction, the following priority
categories are defined:
Priority category
TI
Message with process information in monitor
direction
Binary Information
1,2,30
Single-point information
Priority binary
information
3,4,31
Double-point information
5,6,32
Step position information
17,38
Event of protection equipment
18,39
Blocked activation of the protection
19,40
Blocked triggering of the protection
Measured values
7,8,33
Bitstring of 32 bit
Priority measured value
9,10,34
Measured value, normalized value
11,12,35
Measured value, scaled value
13,14,36
Measured value, short floating point number
15,16,37
Integrated totals
Integrated totals
Priority counters
4.2.4.1
Prioritization Algorithm
With each search for transmitting a message, starting from the priority level clock-time
synchronization, a check takes place whether a message is queued for transmission. When
transmitting messages of one priority level, the maximum number of messages of the
respective priority level is taken into account. If this is reached, the corresponding priority level
is suspended until further notice.
66
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02
Telecontrol
If no message is found during a search (no data to be transmitted, or all priority levels
suspended), then all priority levels are enabled again with their maximum number of
messages. The priority level clock-time synchronization is enabled again immediately each
time, after a message has been transmitted in another priority level. It is thereby stepped
down 1:1 to all other levels. In the priority level system information, the same stepping down to
the lower priority levels is applicable. Since the process information in the monitor direction
interrogated by the GI is also stored in this priority level, one achieves a compromise between
the fast transfer of current data and a limited duration of the station interrogation.
4.2.4.2
Number of messages
Priority level
1:1 to all levels
Time synchronization
1:1 to all lower priority levels
System information and process information in monitor direction
interrogated by station interrogation
9
Process information in control direction
8
Process information in monitor direction Priority HIGH with
class 1 data
3
Process information in monitor direction Priority MEDIUM with
class 2 data
2
Process information in monitor direction Priority LOW with class 2
data
1
Transparent information
Influencing of the Prioritization Algorithm by the Protocol
Element
For special applications (e.g. dial-up traffic) the protocol element can influence these priority
algorithms by being able to block or release priority levels for the transmission.
Application Dial-up Traffic
The dial-up traffic utilizes the blocking of priority levels, so that certain messages (e.g.
measured values) do not cause any spontaneous transmission and consequently a
connection setup. The connection setup is derived from the information "Access request"
(according to IEC 60870-5-2, where data class 1 and data class 2 are defined).
Valid thereby:
•
Data class 1 ... Connection setup is activated
•
Data class 2 ... No connection setup takes place
The table below shows, which priority level is assigned to which data class and consequently
causes a connection setup or not:
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
67
Telecontrol
4.2.5
Priority level
Data class
Time synchronization
1
System information and process information in monitor direction interrogated by
station interrogation
1
Process information in control direction
1
Process information in monitor direction Priority HIGH with class 1 data
1
Process information in monitor direction Priority MEDIUM with class 2 data
2
Process information in monitor direction Priority LOW with class 2 data
2
Transparent information
2
Redundant Communication Routes
In accordance with the requirements with regard to reaction time, availability, data throughput
and transmission media, the following redundancy operating modes are possible:
4.2.5.1
•
communication with redundant remote stations
•
redundant communication with a remote station (load share operation)
Communication with Redundant Remote Stations
The communication with redundant remote stations is possible with every data communication
mode (single point, multi point). Thereby both transmission paths are operated independent of
each other.
4.2.5.2
Redundant Communication with a Remote Station (LSO)
The redundant communication to a remote station allows two operating modes:
•
Data Split Mode
─ Improvement in the availability
─ different baud rates possible on both transmission paths
─ if one interface fails a switch-over to the other interface occurrs; in case of same baud
rates, data throughput remains the same
•
Load Share Mode
─ Improvement of the data throughput and the availability through optimum utilization of
the interfaces at every load and operating state
─ same baud rates recommended on both transmission paths
─ if one interface fails the entire traffic is handled over the available interface; data
throughput goes down to the value which is achieved in data split mode under
otherwise same conditions
68
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02
Telecontrol
The redundant communication to a remote station
•
is supported
─ exclusively with the data communication mode "single point"
─ only with the two interfaces (PRE0 and PRE1 or PRE2 and PRE3) of one serial
interface module. Both protocol elements of an interface pair must be assigned to one
basic system element.
4.2.5.2.1 Data Split Mode
Normally all messages are transmitted over the protocol element with the lower number
(PRE0 or PRE2).
The other protocol element of the interface pair (PRE1 or PRE3) checks the functioning
capability of the interface by means of monitoring messages.
Fault:
Communication faulty over protocol element PRE 0 or PRE2
On failure of this interface, all messages are transmitted over the other protocol element of the
interface pair. The protocol element with the faulty interface (PRE0 or PRE2) checks the
functioning capability through monitoring messages. If the full functioning capability of the
interface at protocol element PRE0 or PRE2 is detected, a switchover of the interfaces to
normal operation takes place.
Communication faulty over both protocol elements of an interface pair
On failure of both interfaces of an interface pair, the last unacknowledged message continues
to be transmitted to the last failed interface. The other protocol element of the interface pair
transmits monitoring messages.
4.2.5.2.2 Load Share Mode
Normally the messages are transmitted over the protocol element currently not busy.
Preferred is always the protocol element with the lower number (PRE0 or PRE2).
To avoid overtaking effects of messages with the same address, the next transmission of this
message is blocked until the previously transmitted message has been acknowledged.
Protocol elements not currently required check the functioning capability of the interface
through monitoring messages.
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
69
Telecontrol
Fault:
Communication faulty over one protocol element of an interface pair
On failure of this interface, all messages are transmitted over the other protocol element of the
interface pair. The protocol element with the faulty interface checks the functioning capability
through monitoring messages. If the full functioning capability of the interface is detected, a
switchover of the interfaces to normal operation takes place.
Communication faulty over both protocol elements of an interface pair
On failure of both interfaces of an interface pair, the last unacknowledged message continues
to be transmitted to the last failed interface. The other protocol element of the interface pair
transmits monitoring messages.
4.2.6
Startup
End of initialization in transmit direction
The startup for a link takes place in accordance with the sequence for the initialization end
according to IEC 60870. This only takes place during the startup of a basic system element or
the automation unit.
The message "Initialization end" is transmitted for each learned CASDU to those remote
stations to which messages with process information in monitor direction are distributed.
During startup, this takes place for all learned CASDU´s, if all messages to be transmitted
have been learned ( = 15 sec after the last message of the CASDU to be sent). Until the
message “Initialization end” is transmitted, a station interrogation from the remote station is
not answered.
On reception of the (general-) interrogation command, all learned messages of the
interrogated CASDU are transmitted with the cause of transmission "interrogated with station
interrogation". Subsequently the message traffic takes place according to the priority
controller.
Initialization end in receive direction
After reception of a "Initialization end" message a (general-) interrogation command is
transmitted for the corresponding CASDU.
70
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02
Telecontrol
4.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
•
Protocol Element Return Information
The Protocol Element Control enables:
•
the reachability of stations to be tested
•
the suppression of errors with intentionally switched-off stations (Station Service)
The Protocol Element Return Information enables:
the cost control of telephone charges
•
the cost-efficient utilization of the telephone line (e.g. command initiation only then, when a
connection has already been established).
Block Diagram
Internal distribution of messages with process information
4.3.1
•
Protocol controller
Internal
function
Protocol element
return information
Link
Protocol element
Messages with process information
Messages with system information
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
71
Telecontrol
4.3.2
Protocol Element Control
With the help of messages with process information, the protocol element control enables
specific functions of the protocol elements to be controlled.
The following messages with process information are supported:
•
Single-point information (type identification 30)
•
Single command (type identification 45)
The assignment of the messages with process information to the functions is carried out with
the help of process-technical parameters of the ACP 1703 system data protocol element
control message.
Possible functions:
Parameter
ControlFunction_
(PRE)
AdditionalParameter_
(PRE)
Meaning
0 - 239
0 - 65535
Depends on the protocol element used
240
not used
Send (General) Interrogation Command
241
not used
Send (General) Interrogation Command to a group
242
not used
Select control location "global"
243
0 – 2 (QRP)
Reset process command
243 - 255
not used
Reserve
On which destination the parameterized control function should act, is set with the following
parameter:
Parameter
Meaning
PRE
128 – 131
254
...
by
...
Protocol element 0 – 3
Protocol element is selected automatically
the
Multimaster function
Station
0 – 99
...
Station 0 – 99 of the selected protocol
element
125
...
all stations of the selected protocol element
255
...
Protocol element with Single Point data
communication mode
If the single-point information is used, it can be set with the parameter edge_(PRE), whether:
•
the parameterized function is activated by the positive or negative edge or
•
the parameterized function is activated by the state = 1 in the message or the successive
function (function + 1) is activated by the state = 0 in the message
If the single command is used, the parameterized function is activated with each message.
72
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02
Telecontrol
4.3.3
Protocol Element Return Information
The protocol element return information generates messages with process information in
monitor direction and thereby enables states of the protocol elements to be displayed and
processed.
There are three different categories of return information:
•
Status of the status line
•
specific, depending on the protocol element used (see System Element Manual of the
protocol element)
•
Status of the stations
Depending on the return information the following messages with process information can be
selected:
•
Single-point information (type identification 30)
•
Measured value, short floating point number (type identification 36)
The assignment of the messages with process information to the return information is carried
out with the help of process-technical parameters of the ACP 1703 system data (protocol
element return information message).
From which source the parameterized return information are to be generated, is set with
parameters:
Parameter
Meaning
PRE_(RM)
128 – 131
...
Station
0 – 99
...
element
255
...
or
Station 0 – 99 of the selected protocol
Protocol element 0 – 3
all stations of the protocol element selected
protocol element with single point traffic
mode or
the protocol element itself
Possible return information:
Parameter
Return information function_(PRE)
id
TI
Station number
Status RTS (1 = status line active)
0
30
255
Status CTS (1 = status line active)
1
30
255
Status DCD (1 = status line active)
2
30
255
Status DTR (1 = status line active)
3
30
255
Status DSR (1 = status line active)
4
30
255
Status RI (1 = status line active)
5
30
255
protocol-specific return information 0 – 15
6 - 21 30
0 – 99, 255
protocol-specific return information value
22
36
0 – 99, 255
Station status
(1 = Station enabled for call cycle)
23
30
0 – 99
Station failure
(1 = Station failed)
24
30
0 – 99
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
73
Telecontrol
4.4
Decentralized Archiving
By means of the function "decentralized archive" (DEAR) it is possible to store events of a
substation locally and – whenever it is required – to transmit to the corresponding control
system. On the other hand it is possible to restore the archive of a control system after a
communication failure.
ACP 1703 supports one archive. This archive can consist of several files.
Depending on which data should be archived following types of archivation are distinguished:
•
spontaneous archiving and
•
periodical archiving
DEAR is separated in two partial functions:
74
•
recording of data into the archive
•
transmission of the archive
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02
Telecontrol
4.4.1
Block Diagram
TI 122
Recording of data into the
archive
Internal distribution of messages with process information and for the filetransfer
(assignment of the messages to the archive )
spontaneous archiving
for e.g. binary
information, counter
periodical Archivig for
e.g. measured values
Process image
Periodical
recording
temporary
file
file 1
file n
Archive (flashcard)
TI 120, TI 121
TI 123, TI 124
TI 126
Transmission of the file
TI 122
(interrogation from the control system or
TOOLBOX)
Messages with process information
Messages for the filetransfer
4.4.2
Recording of data into the archive
Every data point used in a automation unit can be assigned for the record in the decentralized
archive by parameter setting in the detail routing. The assignment of data points for the
decentralized archive takes place data point by data point.
ACP 1703 records an assigned data point dependent on the type spontaneous or periodical in
the archive. Each record contains a time tag with a resolution of 1 ms.
The assignment of the messages with process information in monitoring direction and
messages for data transmission to the archive is carried out with the help of process-technical
parameters for the decentral archiving | * in OPM II. The message address is
adjustable by means of the parameter CASDU1, CASDU2, IOA1, IAO2 and IOA3.
The function is determined with the additional parameter Function_(DEAR).
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
75
Telecontrol
Possible functions:
Parameter Function_(DEAR)
Description
archive data
This messages with supported type identifications are used for
storing according to the type of storing (spontaneous or
periodical) into the archive
adress maindirectory
This message with type identification 122 is used for the
interrogation of the maindirectory
adress subdirectory
This message with type identification 122 is used for the
interrogation of the subdirectory
adress file
This message with type identification 122 is used for the
interrogation of the files
Supported type identifications
Since for the data transmission to the control system the file transfer according to IEC 608705-101/104 is used, only type identifications which are named in the standard are supported:
TI
4.4.2.1
Data point type
Type of storing
30
single-point information with time tag CP56Time2a
spontaneous
31
double-point information with time tag CP56Time2a
spontaneous
32
Step position information with time tag CP56Time2a
spontaneous
33
Bitstring of 32 bits with time tag CP56Time2a
spontaneous
34
measured value, normalized with time tag CP56Time2a
periodical
35
measured value, scaled with time tag CP56Time2a
periodical
36
measured value, short floating point with time tag
CP56Time2a
periodical
37
integrated total with time tag CP56Time2a
spontaneous
38
Event of protection equipment with time tag CP56Time2a spontaneous
39
Packed start events of protection equipment with time tag
CP56Time2a
spontaneous
40
Packed output circuit information of protection equipment
with time tag CP56Time2a
spontaneous
Spontaneous Archiving
Each received and in the detailed routing assigned message, with the corresponding type
identification for spontaneous archiving (see table "Supported type identifications"), is
immediately entered to the temporary file without without change comparison.
4.4.2.2
Periodical Archiving
Each received and in the detailed routing assigned message, with the corresponding type
identification for periodical archiving (see table "Supported type identifications"), is entered to
the process image. This process image is entered to the temporary file with the grid defined in
parameter Decentral archiving | Recording grid for measured values.
76
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02
Telecontrol
4.4.2.3
Power fail safe Storing
The temporary file is stored non-volatile on the SD-card if:
•
the temporary file is full or
•
after 5 seconds have expired
Hint
In the case of a loss of voltage maximum the data of the last 5 seconds before the loss of voltage until the
time setting of the automation unit can be lost.
4.4.2.4
Archiving before Time Setting
Data points are saved only if the time of the aoutomation unit is set. Archive records with
relative time are not possible.
4.4.2.5
Configuration of the archive
Depending on the structure of the automation system and the required usage, the archive can
be structured into more or less files with the parameter Decentral archiving | Memory
configuration archive.
Dependent from Automation System
If the archive is inquired rarely per day within a large period (e.g. in case of dial-up
connection), a small amount of large files is useful.
If the archive is usually inquired within a short period, a large amount of small files is useful.
Dependent from Usage
If the archive is mainly required for short communication failures, a large amount of small files
is useful.
If the archive is mainly required for long communication failures (e.g. bridging a failure over
the weekend), a small amount of large files is useful.
Note
The files of the archive are deleted, if parameter Decentral archiving | Memory configuration
archive changes, or if there are implausible files or file information for the archive on the SD-card.
Hint
The file overview shows one file more than set per parameter, because one file is always in processing
(likewise the total number of data point entries can be maximum larger for the amount of entries of a file);
if this parameter is changed or the archive is configured the first time, the configuration can last up to 10
minutes after "Ready" is displayed on the master control element.
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
77
Telecontrol
4.4.3
Transmission of the archive
The transmission of the archive takes place in principle after the request of an higher-level
place. However there is a possibility to transmit the subdirectory list spontaneous in case of a
change in the archive. This function is enabled with parameter Decentral archiving |
spontaneous transmission of directory list. Thereby the subdirectory list with all
files is sent, independent which file has changed.
Calling the archive has to be initiated by a control system. The file transfer is performed
according to IEC 60870-5. Every control system which works according to that standard can
initiate a transfer of archive files from the automation unit.
The sequence of messages for the interrogation of archive files is defined according to
IEC 60870-5-101/-104. The transmission sequence is monitored for abortion for a predefinde
time which is set in parameter Decentral archiving | Timeout for filetransfer. If
this monitoring responds, the transmission sequence cannot be continued, but must be
started again with an inquiry of the maindirectory.
For the inquiry of the directories and files, the CASDU and IOA must be defined in detailed
routing. The value for CASDU is arbitrary (it must not correspond with the CASDU of the
automation unit) but it must be unique for all inquiries.
For the transmission (TI 125) of the individual data points in the files it is possible to determine
the format of the adress with the parameters Decentral archiving | number of bytes
CASDU in the archive, number of bytes IOA in the archive and number of
bytes COT in the archive.
Additional the Decentral archiving | Maximum message length for one segment
can be set with a parameter.
Definitions for the Request of Files
•
The files are transmitted as sorted in the file overview. The oldest file is displayed first, the
youngest file last.
•
The data points within a file are not sorted chronological, however, a single data point
within a file is recorded chronologisch.
•
For each file the "time of the last record" into the file is transmitted in the file overview,
since the acquisition time of the data point may not be within the storing time period.
•
Via the "time of the last record" (creation time) the control system is able to request for the
file(s) which contain the records of the desired recording period.
•
Interrogation criteria:
─ A communication failure directly at the interface to the control system is detected by
itself, and it is able to request for the files over the period of the failure automatically
─ With communication failure in further hierarchy (at interfaces which do not lead directly
to the control system) a notification of the period to be requested is performed by a
coming/going single-point information. This single point information must be generated
by the user.
•
The file directory can be accessed by severel remote stations at the same time. A
transmission, however, can be performed only to one remote station. If there are several
interrogating remote stations, the transmission takes place first to the remote station
belonging to the first received interrogation. The other interrogations are acknowledged
negative as long as the current transmission is completed.
Note
If TM 1703 mic recognizes errors in the directory or upon the file handling (for instance a negative
acknowledgement, the transmission will be cancelled.
78
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02
5
Automation
Content
5.1
Introduction.........................................................................................................80
5.2
Open-/Closed-Loop Control Function.................................................................81
5.3
Treatment for Commands to the Open-/Closed-Loop Control Function
according to IEC 60870-5-101/104 ..................................................................132
5.4
Restricted open/closed loop function ...............................................................158
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
79
Automation
5.1
Introduction
The function package Automation includes the following functions:
80
•
Acquisition of the process data on the peripheral elements and transfer of the periodical
information over the Ax 1703 peripheral bus to the open-/closed-loop control function.
•
Open-/Closed-Loop Control Function
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02
Automation
5.2
Open-/Closed-Loop Control Function
The open-/closed-loop control function is used for the management of automation tasks with
the help of an application program.
The creation of the application program is carried out by the TOOLBOX II with the tool
CAEx plus predominantly in function diagram technology according to IEC 61131-3.
The application program processes process information (so-called signals) from the peripheral
elements connected to the basic system element 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. One
differentiates between input- and output process images.
The exchange of the process information can take place in 2 variants:
•
periodical information from and to the peripheral elements connected to the basic system
element (local periphery) over the Ax 1703 peripheral bus
•
spontaneous information objects from and to functions or peripheral elements within the
automation unit, other open-/closed-loop control functions and other automation units or
control systems with the help of the telecontrol function.
The open-/closed-loop control function supports 32 programs (type instances), whereby each
program can be assigned one of three periodical tasks. As a result, fast controls can be
optimally combined with slower background processings.
The management of these three periodical tasks (Task Management) corresponds with the
standard IEC 61131. Spontaneous tasks are not supported.
The open-/closed-loop control function consists of the following part functions:
•
Task Management
─ Coordination of the sequences of a task
─ Coordination of the three tasks with each other
─ Run time supervision
─ Time management for function blocks
•
Initialization
─ Startup of the basic system element (resource)
─ Startup of the open-/closed-loop control function (all tasks or single task)
•
Input handling
─ Message processing for spontaneous information objects
─ Conversion of spontaneous information objects to periodical information
─ Synchronization of the input process images for
•
•
−
periodical Information
−
spontaneous information objects
−
System information
Program processing
Output handling
─ Updating of local peripheral elements for periodical information
─ Generation of messages with system information
─ Generation of diagnostic information
─ Change monitoring for spontaneous information objects
─ Generation of messages with process information
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
81
Automation
•
Loading of the Application Program (Reload)
•
Online test
─ Display/Forcing of values
─ Test switches
─ Changing the execution status of the open-/closed-loop control function
─ Setting breakpoints
─ Real time archive
─ Display status information
─ Read and write variables
General characteristics
•
Retain
Variables, signals (input process image 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 available again with the value before the power failure.(see
"Initialization")
•
Reload
Loading of changes, that make a startup of the basic system element unnecessary.
─ without interruption to operation
The continuity of the function of the application program can, due to the type of
changes, be maintained, with the exception of the program switch after the reload
─ with interruption to operation
The continuity of the function can not be maintained
82
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02
Automation
5.2.1
Block Diagram
Process input and output
Ax 1703 peripheral bus
Input process
image
periodical
information
System
information
Input process
image
spontaneous
information
objects
Message
processing
Synchronization
Task management
Synchronization
Input process
image
Programs
Output
process image
"fast" task
"fast" task
"fast" task
task
task
"slow" task
task
"slow" task
"slow" task
Program
variables
Resourceglobal
variables and
parameters
Output process
image
periodical
information
System
information
Change
monitoring
Generation of
messages
Program 1
Program 32
Internal distribution of messages with process information
Message with process information
Communication function
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
Periodical information
83
Automation
5.2.2
Task Management
5.2.2.1
Coordination of the Sequences of a Task
Initialization
Start periodical
(cycle time)
Execution indicator (LED "run")
Time-out monitoring
Input handling
Program processing
Program A
Program B
:
Program n
Output handling
Online test
Real time archive
Stop
84
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02
Automation
5.2.2.2
Task timing
PRIORITY HIGH
10ms
System clock
10ms
10ms
10ms
10ms
10ms
10ms
10ms
10ms
10ms
10ms
Time handling and Ax-PE bus
Transmission of period. information
Open-/Closed loop control function
Fast task
processing
Cycle time 10ms
curr. run time
Run time 5ms
5ms
5ms
5ms
5ms
5ms
5ms
5ms
5ms
5ms
5ms
5ms
Message generation from result
data of the fast task
(specific Task)
Communication
receive direction
Open-/Closed loop control function
Processing
Task
Msg gen.
Cycle time 40ms
curr. run time
Run time 8 ms
18,5ms
25,5ms
19ms
Communication
transmit direction
Open-/Closed loop control function
Slow task
Cycle time 80ms
Run time 12 ms
Processing
Msg gen.
curr. run time
??ms
69,5ms
System IDLE task
PRIORITY LOW
Legend
Spontaneous messages
Interrupt
Periodical information
Task running
Task able to run but interrupted
Msg gen.
Message generation from result data
As can be seen from the diagram, a constant run time is only guaranteed for the "fast Task".
For the "Task" and "slow Task", no constant predictable run times are produced due to
interruptions from higher-priority functions. That means, that with the output of signals (e.g.
with a pulse) a jitter can occur depending on the loading of the resource.
5.2.2.3
Cycle Time
The cycle time is that time scale, in which all programs assigned to a task (type instances),
must have processed the input- and output handling for this task.
The cycle time can be set for each task from 10 ms to 65 sec in 10ms steps.
The cycle times of the three tasks must be different and ascending from the "fast Task" to the
"slow Task".
The cycle times of the tasks can be set in the tool CAEx plus. Modification with the help of the
online test is not possible.
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
85
Automation
5.2.2.4
Run Time Supervision
This function monitors the proper sequence of each task within its set cycle time. If a 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 timeout is signaled.
The signaling and its effect takes place dependent on operating state:
Normal operation
•
Every timeout increments a counter for the corresponding task. These three counters (one
for each task) can be read out with the TOOLBOX II tool "CAEX plus Online-Test" menu
item "Display Status Information". These three counters can be reset by means of an
operator input in the Online-Test. The reset also takes place with a warm- and cold start.
•
If more than 4 timeouts are detected within 10 consecutive cycles, a diagnostic information
is set for the corresponding task. This diagnostic information is reset, when the previously
stated condition is no longer fulfilled.
Exception: With the "fast Task" the output handling for the message generation is not
monitored as previously described, rather this message generation must run once within 16
cycles of the "fast Task". A diagnostic information is set, when this condition is not fulfilled.
This diagnostic information is reset, when the previously stated condition is no longer fulfilled.
•
If the processing time of the task takes longer than a time that can be set for each task
(= n * cycle time of the task, 0 = monitoring inactive) with the parameter max. number at
reload (CAEX plus – properties Task – 1703), this task is deleted and a diagnostic
information is set for the corresponding task. In addition, all peripheral elements connected
to this basic system element are switched to the "Module shut down" state (substitute
value input on the peripheral element). This state can only be canceled with a startup
(power up or reset) of the basic system element.
Loading of Application Program (Reload)
•
While loading the application program (reload), the before described run time supervision
(4 timeouts within 10 consecutive cycles) is deactivated.
•
If the processing time of the task takes longer than a time that can be set for each task
(= n * cycle time of the task, 0 = monitoring inactive) with the parameter max. number at
reload (CAEX plus – properties Task – 1703), this task is deleted and a diagnostic
information is set for the corresponding task. In addition, all peripheral elements connected
to this basic system element are switched to the "Module shut down" state (substitute
value input on the peripheral element). This state can only be canceled with a startup
(power up or reset) of the basic system element.
Synchronization of Application Program (Reload)
86
•
While synchronizing the application program via the redundancy synchronization link, the
run time supervision is deactivated.
•
Only the redundancy synchronization link is supervised (see "Monitoring of the
Interfaces").
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02
Automation
5.2.2.5
Time Management for Function Blocks
The time management ensures the most possible precise termination of time-controlled
function blocks (e.g. Monoflop). The time management exists with each task. The accuracy of
the time set in the function block is dependent on the cycle time of the task in which the
function block is processed. This time only makes sense in multiples of the cycle time of the
task.
Example for a time that is not set in multiples of the cycle time:
Cycle time of the task: 30ms
Time of the function block:
40ms
Produces a true time of:
60ms
Special cases
•
Timeout in the last cycle before the time expires
The time is extended by the cycle time of the task
•
Task stopped
The time is extended by the duration of this state. The time management of other tasks is
not affected by this.
•
Startup of time-controlled function blocks stored non-volatile (retain)
With a warm start the time expired remains effective, i.e. the function block ends its timedependent function after the time still remaining. The time from the tripping of the warm
start, power down and reset until the completion of the initialization is not compensated.
With a cold start, the time blocks begin again with their initial value.
•
Stationary cycles
Time-controlled function blocks work normally during the stationary cycles. However, if the
time expires within the stationary cycles, signals derived from this are first effective after
completion of the stationary cycles.
5.2.3
Initialization
Before a task manages to be executed for the first time with its programs, the signals and the
variables must be switched to a defined state.
For this purpose, various methods are used depending on the trip:
•
Startup of the basic system element
•
Startup of the open-/closed-loop control function
Depending on the tripping point, distinction is made between a cold - or warm start. The
distinction only affects variables and signals etc. flagged RETAIN.
Warm start: the variables and signals etc. flagged RETAIN are not initialized
Cold start: the variables and signals etc. flagged RETAIN with the initial value
defined by the system or by the user are initialized.
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
87
Automation
After the initialization of the signals at the input and the variables, the programs are initialized
by means of stationary cycles.
On expiry of the stationary cycles, the output process images are updated.
5.2.3.1
Startup of the Basic System Element
The startup of a basic system element (resource) can be tripped by means of:
Tripping point
Startup type
Power-Up
Warm start
Reset the automation unit
Warm start
Reset of the basic system element
Warm start
Initialization of the automation unit
Cold start
Exchange of the Flash Card
Cold start
Initialization of the basic system element
Cold start
Note
corresponds with an initialization of the
automation unit
All signals of the input and output process images, the resource-global variables and
parameters and the local variables of the programs of all tasks are initialized.
5.2.3.1.1 Initialization of the Variables
A distinction is made between three possible initial values for each variable:
•
Initial value defined by the system = 0
•
Initial value defined by the user with CAEx plus.
•
RETAIN
with warm start the resource-global variables and local variables of the programs are
initialized with those values, that were current before the power failure.
with cold start these variables are initialized with the initial value defined by the system or
by the user.
5.2.3.1.2 Initialization of the Resource-Global Parameters
A distinction is made between three possible initial values for each variable:
•
88
Initial value defined by the system = 0
•
Initial value defined by the user with CAEx plus.
•
RETAIN
with warm start the resource-global parameters are not initialized.
with cold start the resource-global parameters are initialized with the initial value defined
by the system or by the user.
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02
Automation
5.2.3.1.3 Initialization of the Signals
The input process images for periodical information are set to 0. Before the tasks start,
the input process image is written with the current process information. For failed peripheral
elements the corresponding periodical information "Module failed" is set.
The input process images for spontaneous information objects are initialized with their
initial value according to the type identification by means of messages. A distinction is thereby
made between three possible initial values for each spontaneous information object:
•
Initial value defined by the system; see "Input Process Image for Spontaneous Information
Objects"
•
Initial value defined by the user; basic data of certain spontaneous information objects
(see "Message Characteristics ") an initial value can be specified by the OPM II
•
RETAIN
with warm start all elements of a spontaneous information object are initialized with those
values, that were current before the power failure (see "Message processing for
spontaneous information objects").
with cold start all elements of a spontaneous information object are initialized with the
initial value defined by the system or by the user.
With which initial value the input process image is initialized is dependent on the spontaneous
information object and on parameters (see "Input Process Image for Spontaneous Information
Objects").
Before the tasks are started, a general interrogation is tripped and the arrival of all assigned
GI-capable messages with process information is waited with time out (t = number of assigned
messages x 10ms). On expiry of the time, the spontaneous information objects for nonreceived messages are processed with their initial value and "not topical" (NT).
The output process images for periodical information are updated on expiry of the
stationary cycles and transmitted over the Ax 1703 peripheral bus to the local peripheral
elements.
The output process images for spontaneous information objects are updated on expiry of
the stationary cycles. Subsequently, messages are generated for all spontaneous information
objects and transferred with the cause of transmission "interrogated by general interrogation".
With the next cycle, the change monitoring for spontaneous information objects takes place.
5.2.3.2
Startup of the Open-/Closed-Loop Control Function
The startup of the open-/closed-loop control function (the resource or a task) can be tripped by
means of:
•
online test
Thereby a so-called warm- or cold start of the open-/closed-loop control function is performed
dependent on the operator input.
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
89
Automation
5.2.3.2.1 Initialization of the Variables
A distinction is made between three possible initial values for each variable:
•
Initial value defined by the system = 0
•
Initial value defined by the user with CAEx plus.
•
RETAIN
with warm start the resource-global variables and the local variables of the programs are
not initialized.
with cold start the resource-global and the local variables of the programs are initialized
with the initial value defined by the system or by the user.
Attention
Resource-global variables are only handled with a warm- or cold start, which acts on the resource.
5.2.3.2.2 Initialization of the Signals
The input process images for periodical information are not initialized.
Input process images for spontaneous information objects
GI-capable messages with process information are not initialized.
Non-GI-capable messages with process information are initialized with their initial value
according to type identification by means of messages. A distinction is thereby made between
three possible initial values for each spontaneous information object:
•
Initial value defined by the system; see Input Process Image for Spontaneous Information
Objects"
•
Initial value defined by the user; basic data of certain spontaneous information objects
(see "Message Characteristics ") an initial value can be specified by the OPM II
•
RETAIN
with warm start no initialization.
with cold start all elements of a spontaneous information object are initialized with the
initial value defined by the system or by the user.
With which initial value the input process image is initialized is dependent on the spontaneous
information object and on parameters (see "Input Process Image for Spontaneous Information
Objects").
Exception:
•
Spontaneous information objects that have been stored "chronological message" or
"chronological global", are initialized with the most current information. I.e. stored
messages are discarded.
•
RETAIN
with cold start all elements of non-GI-capable messages with process information are
initialized with the initial value defined by the system or by the user.
The output process images for periodical information are updated on expiry of the
stationary cycles and transmitted over the Ax 1703 peripheral bus to the local peripheral
elements.
90
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02
Automation
The output process images for spontaneous information objects are updated on expiry of
the stationary cycles. Subsequently, the change monitoring for spontaneous information
objects takes place.
5.2.3.3
Stationary Cycles
Stationary cycles are used for the processing of intentional feedback, in order to obtain stable
initial states after the initialization phase. For the processing of the stationary cycles, the
number of passes for each task can be parameterized. The number is to be so chosen, that all
feedback pass through in such a way, that the output signals show a stable state.
Attention
If insufficient stationary cycles are run through, on startup, undesirable generation of messages for
spontaneous information objects or outputs to the local peripheral elements can occur.
5.2.4
Input Handling
The input handling is used for the provision of consistent process images for each task for the
duration of the program processing.
The input handling exists for each task and consists of:
•
Message processing for spontaneous information objects
•
Conversion of spontaneous information objects to periodical information
•
Synchronization of the input process images for:
─ periodical Information
─ system information
─ spontaneous information objects
Spontaneous information objects can be stored non-volatile (Retain). The maximum number is
256. Which spontaneous information objects are stored non-volatile (Retain), can be set by
means of parameters in the OPM II.
5.2.4.1
Message Processing for Spontaneous Information Objects
After reception of a message with process information the entry is carried out in the input
process image for spontaneous information objects according to the selected storage method.
The message processing for spontaneous information objects is available for each task.
The following storage methods are possible:
•
state stored
•
chronological message
•
chronological global
The storage method can be set for each message.
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
91
Automation
5.2.4.1.1 Storage Method "State Stored"
With the storage method "State Stored" the spontaneous information objects from received
messages are entered directly in the input process image for spontaneous information
objects.
5.2.4.1.2 Storage Method "Chronological Message"
With the storage method "Chronological Message" for each cycle all spontaneous information
objects of the received messages are entered in the input process image for spontaneous
information objects, until a message with the same address would be entered.
Example:
n
Cycle
n+1
n+2
Received message
A B
A C
Message processing
A B
A C
If more messages arrive than can be processed, a ring overload can occur. This state can
also occur, if the associated task has been halted through the online test.
Error handling
With an overload of the ring, a diagnostic information is set for the corresponding task and a
further entry is prevented. If more messages arrive, before the ring is half free again,
•
non-GI-capable messages with process information are discarded
•
the state is flagged for GI-capable messages with process information
Once the ring is half free again, the spontaneous information objects flagged during the ring
overload are entered in the ring with the last valid state and processed as described
previously.
5.2.4.1.3 Storage Method "Chronological Global"
With the storage method "Chronological Global" for each cycle precisely one spontaneous
information object is entered in the input process image for spontaneous information objects.
If more messages with spontaneous information objects arrive than can be processed, a ring
overload can occur. This state can also occur, if the associated task has been halted through
the online test.
92
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02
Automation
Error handling
With an overload of the ring, a diagnostic information is set for the corresponding task and a
further entry is prevented. If more messages arrive before the ring is half free again,
•
non-GI-capable messages with process information are discarded
•
the state is flagged for GI-capable messages with process information
Once the ring is half free again, the spontaneous information objects flagged during the ring
overload are entered in the ring with the last valid state and processed as described
previously.
5.2.4.1.4 Failure Management
On failure of the source (communication interface, peripheral element etc.), for all GI-capable
messages with process information affected by this the quality descriptor "not topical" and the
cause of transmission "spontaneous" (BOOL) is set.
Once the source is available again, with the next messages all elements of the associated
spontaneous information objects are updated.
5.2.4.1.5 Message Characteristics
Explanation of the symbols, designations and values used in the following tables.
Column Name
contains
TI
PLC
Meaning
Type identification of the spontaneous information object
YES / NO
GI
Message can be processed by the open-/closed-loop control
function
GI-capable
YES
Spontaneous information object is also transmitted with a
general interrogation
NO
Spontaneous information object is transmitted exclusively
due to an event (change, operator input)
Sto Default
Storage method
Type of storage of the spontaneous information object by
default
ZU
State stored
ZFR_TEL
Chronological message
ZFR_GL
Chronological global
PER
YES / NO
Direct transfer of the basic data of a message to the
peripheral elements as periodical information
INIT
YES / NO
The basic data of the spontaneous information object can be
specified an initial value by the OPM II. Which basic data can
be specified an initial value, can be seen in chapter "Input
process images for spontaneous information objects"
ReqMem
<value>
[in bytes]
Specifies, how much memory is required in the process
images at least (without additional status) for a message.
each assigned additional status is to be added. Values see
"Input process images for spontaneous information objects"
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
93
Automation
Message with process
information in monitor
direction
TI
PLC
GI
Sto
Default
PER
INIT
ReqMem
Single-point information
30
YES
YES
ZFR_TEL YES
YES
5
Double-point information
31
YES
YES
ZU
NO
NO
6
Step position information
32
YES
YES
ZFR_TEL NO
NO
7
Bitstring of 32 bit
33
YES
YES
ZFR_TEL NO
NO
9
Measured value, normalized
value
34
YES
YES
ZU
YES
YES
9
Measured value, scaled value
35
YES
YES
ZU
YES
YES
7
Measured value, short floating
point number
36
YES
YES
ZU
YES
YES
9
Integrated totals
37
YES
NO
ZFR_TEL NO
NO
9
Event of protection equipment
38
YES
NO
ZFR_TEL NO
NO
8
Blocked activation of the
protection
39
YES
NO
ZFR_TEL NO
NO
12
Blocked triggering of the
protection
40
YES
NO
ZFR_TEL NO
NO
10
Packed single-point information
with status change detection
20
NO
-
-
-
-
-
Single command
45
YES
NO
ZFR_GL
NO
NO
4
Double command
46
YES
NO
ZFR_GL
NO
NO
5
Regulating step command
47
YES
NO
ZFR_GL
NO
NO
5
Set point command, normalized
value
48
YES
NO
ZFR_GL
NO
YES
7
Set point command, scaled value
49
YES
NO
ZFR_GL
NO
YES
5
Set point command, short floating
point number
50
YES
NO
ZFR_GL
NO
YES
7
Bitstring of 32 bit
51
YES
NO
ZFR_GL
NO
NO
5
(General) interrogation command
100
NO
-
-
-
-
-
Counter interrogation command
101
NO
-
-
-
-
-
Clock synchronization command
103
NO
-
-
-
-
-
Container for system information
135
NO
-
-
-
-
-
Container for process information
142
NO
-
-
-
-
-
Message with process
information in control direction
Message with system
information in control direction
Message with transparent
information
5.2.4.1.6 Input Process Image for Spontaneous Information Objects
A spontaneous information object consists of several elements.
These elements are subdivided into:
94
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02
Automation
•
Basic data e.g. the single-point information, the measured value
•
Standard status
object e.g.:
dependent on the type identification of the spontaneous information
─ Quality descriptor invalid (IV)
─ Quality descriptor not topical (NT)
─ Quality descriptor overflow (OV)
─ Cause of transmission spontaneous
─ Cause of transmission GI
•
Additional status
object e.g.:
dependent on the type identification of the spontaneous information
─ Quality descriptor substituted (SB)
─ Confirmation (P/N)
─ Quality descriptor blocked (BL)
─ Test (T)
─ Redundancy
─ Cause of transmission (COT)
─ Originator address
─ Time and date
The definition of basic data, standard status and additional status is described for each type
identification of the spontaneous information object in the following tables.
Explanation of the symbols, designations and values used in the following tables.
Column
Name
contains
Meaning
Element in
message
Element
(bold)
Basic data of a spontaneous information object
element
element *
Format
Standard- or additional status
These elements are not defined in the standard 60870-5-101/104, but rather are
made available internally
Specifies the value range and the required memory in the process image
BOOL
binary
value range 0/1
required memory 1 byte
USINT
analog
value range 0 … 255
INT
analog
value range -32,768 … 32,767
UINT
analog
value range 0 … 65,535
DINT
analog
value range
-2,147,483,648 … 2,147,483,647
byte
required memory 1 byte
required memory 2 byte
UDINT
analog
value range 0 … 4,294,967,294
byte
REAL
analog
value range short real
8.43 x 10 –37 ... 3.37 x 1038
byte
TIME
STO
Table
value range 8 x 0 … 255
byte
required memory 2 byte
required memory 4
required memory 4
required memory 4
required memory 8
Storage method
Type of storage in the process images on
ZU
The process image contains the state of the last received message
WI
The process image is set on reception of a message and reset after once
processing the application program of the corresponding task
MEM
specifies, when memory is assigned in the process images
fix
These elements always occupy memory in the process images, even if only one
element is assigned
These elements only occupy memory in the process images, if they are also
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
95
Automation
assigned.
opt
INIT
Specifies the initial value in the process image
<value>
No input in the OPM II possible
<value> / A
Input in the OPM II possible with parameter Initial value binary or
Initial value analog
Signal_Ext
Specifies, with which extension the signal name (the element in the message) can
be assigned. The extensions are defined in structure definitions (see column
"Name of Structure")
no entry
The signal name without extension indicates basic data in the message if these
only consist of one element
. <ext>
Indicates individual elements of basic data in the message, if they consist of
several elements
_STATE.<ext>
Indicates standard states in the message
_<ext>
Indicates additional states in the message
Name of
structure
Specifies the name of the structure, in which the extension of the signal name is
defined
Single-point information TI 30
Element in Message
Format STO
MEM
INIT
Single-point information
SPI
BOOL
ZU
fix
0/A
Signal_Ext
Name of Structure
Quality descriptor invalid
IV
BOOL
ZU
fix
0
_STATE. IV
TB_SD_SPO_STATE_BIN_INF
Quality descriptor not topical NT
BOOL
ZU
fix
1
_STATE. NT
TB_SD_SPO_STATE_BIN_INF
Cause of transmission GI
BOOL
WI
fix
0
_STATE. GI
TB_SD_SPO_STATE_BIN_INF
Cause of transmission "spontaneous"
*
BOOL
WI
fix
0
_STATE. S
TB_SD_SPO_STATE_BIN_INF
Quality descriptor "substituted"
SB
BOOL
ZU
opt
0
_SB
Quality descriptor "blocked"
BOOL
ZU
opt
0
_BL
BOOL
ZU
opt
0
_PN
BOOL
ZU
opt
0
_T
BOOL
ZU
opt
0
_R
USINT
ZU
opt
4
_COT
Originator address
USINT
ZU
opt
0
_ORIGINATO
R
Time and date
TIME
ZU
opt
0
_TIMETAG
TB_SD_SYSTEM_TIME
Confirmation
Test
*
BL
P/N
T
Redundancy
*
Cause of transmission
COT
Double-point information TI 31
Element in Message
Format STO
MEM
INIT
Signal_Ext
Name of Structure
Double-point information
DPI / OFF
BOOL
ZU
fix
0
. Off
TB_SD_SPO_TI31_DPI
Double-point information
DPI / ON
BOOL
ZU
fix
0
. On
TB_SD_SPO_TI31_DPI
BOOL
ZU
fix
0
_STATE. IV
TB_SD_SPO_STATE_BIN_INF
Quality descriptor not topical NT
BOOL
ZU
fix
1
_STATE. NT
TB_SD_SPO_STATE_BIN_INF
Cause of trans-mission GI
BOOL
WI
fix
0
_STATE. GI
TB_SD_SPO_STATE_BIN_INF
Cause of transmission
"spontaneous"
*
BOOL
WI
fix
0
_STATE. S
TB_SD_SPO_STATE_BIN_INF
Quality descriptor
"substituted"
BOOL
ZU
opt
0
_SB
Quality descriptor invalid
96
IV
*
SB
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02
Automation
Quality descriptor "blocked"
BOOL
ZU
opt
0
_BL
BOOL
ZU
opt
0
_PN
BOOL
ZU
opt
0
_T
BOOL
ZU
opt
0
_R
USINT
ZU
opt
4
_COT
Originator address
USINT
ZU
opt
0
_ORIGINATO
R
Time and date
TIME
ZU
opt
0
_TIMETAG
TB_SD_SYSTEM_TIME
Confirmation
Test
BL
P/N
T
Redundancy
*
Cause of transmission
COT
Step position information TI 32
Element in Message
Format STO
MEM
INIT
Signal_Ext
Name of Structure
Value
USINT
ZU
fix
0
. VALUE
TB_SD_SPO_TI32_VTI
Intermediate state
BOOL
ZU
fix
0
. TSI
TB_SD_SPO_TI32_VTI
BOOL
ZU
fix
0
_STATE. IV
TB_SD_SPO_STATE_VALUE
Quality descriptor "not topical"
NT
BOOL
ZU
fix
1
_STATE. NT
TB_SD_SPO_STATE_VALUE
Quality descriptor "overflow" OV
BOOL
ZU
fix
0
_STATE. OV
TB_SD_SPO_STATE_VALUE
Cause of transmission "GI"
BOOL
WI
fix
0
_STATE. GI
TB_SD_SPO_STATE_VALUE
Cause of transmission "spontaneous"
*
BOOL
WI
fix
0
_STATE. S
TB_SD_SPO_STATE_VALUE
Quality descriptor "substituted"
SB
BOOL
ZU
opt
0
_SB
Quality descriptor "blocked"
BOOL
ZU
opt
0
_BL
BOOL
ZU
opt
0
_PN
BOOL
ZU
opt
0
_T
BOOL
ZU
opt
0
_R
Quality descriptor "invalid"
Confirmation
Test
IV
*
BL
P/N
T
Redundancy
*
Cause of transmission
USINT
ZU
opt
4
_COT
Originator address
COT
USINT
ZU
opt
0
_ORIGINATO
R
Time and date
TIME
ZU
opt
0
_TIMETAG
TB_SD_SYSTEM_TIME
Signal_Ext
Name of Structure
Bitstring of 32 bit TI 33
Element in Message
Format STO
MEM
INIT
Binary status information
BSI
UDINT
ZU
fix
0
Quality descriptor "invalid"
IV
BOOL
ZU
fix
0
_STATE. IV
TB_SD_SPO_STATE_VALUE
Quality descriptor "not topical"
NT
BOOL
ZU
fix
1
_STATE. NT
TB_SD_SPO_STATE_VALUE
Quality descriptor "overflow" OV
BOOL
ZU
fix
0
_STATE. OV
TB_SD_SPO_STATE_VALUE
Cause of transmission "GI"
BOOL
WI
fix
0
_STATE. GI
TB_SD_SPO_STATE_VALUE
Cause of transmission "spontaneous"
*
BOOL
WI
fix
0
_STATE. S
TB_SD_SPO_STATE_VALUE
Quality descriptor "substituted"
SB
BOOL
ZU
opt
0
_SB
Quality descriptor "blocked"
BOOL
ZU
opt
0
_BL
BOOL
ZU
opt
0
_PN
Confirmation
P/N
*
BL
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
97
Automation
Test
T
BOOL
ZU
opt
0
_T
BOOL
ZU
opt
0
_R
USINT
ZU
opt
4
_COT
Originator address
USINT
ZU
opt
0
_ORIGINATO
R
Time and date
TIME
ZU
opt
0
_TIMETAG
TB_SD_SYSTEM_TIME
Signal_Ext
Name of Structure
Redundancy
*
Cause of transmission
COT
Measured value, normalized value TI 34
Element in Message
Format STO
MEM
INIT
Normalized value NVA
REAL
ZU
fix
0/A
BOOL
ZU
fix
0
_STATE. IV
TB_SD_SPO_STATE_VALUE
Quality descriptor "not topical"
NT
BOOL
ZU
fix
1
_STATE. NT
TB_SD_SPO_STATE_VALUE
Quality descriptor "overflow" OV
BOOL
ZU
fix
0
_STATE. OV
TB_SD_SPO_STATE_VALUE
Cause of transmission "GI"
BOOL
WI
fix
0
_STATE. GI
TB_SD_SPO_STATE_VALUE
Cause of transmission
spontaneous"
*
BOOL
WI
fix
0
_STATE. S
TB_SD_SPO_STATE_VALUE
Quality descriptor
"substituted"
BOOL
ZU
opt
0
_SB
BOOL
ZU
opt
0
_BL
BOOL
ZU
opt
0
_PN
BOOL
ZU
opt
0
_T
BOOL
ZU
opt
0
_R
USINT
ZU
opt
4
_COT
Originator address
USINT
ZU
opt
0
_ORIGINATO
R
Time and date
TIME
ZU
opt
0
_TIMETAG
TB_SD_SYSTEM_TIME
Signal_Ext
Name of Structure
Quality descriptor "invalid"
Test
*
SB
Quality descriptor "blocked"
Confirmation
IV
BL
P/N
T
Redundancy
*
Cause of transmission
COT
Measured value, scaled value TI 35
Element in Message
Format STO
MEM
INIT
Scaled value
INT
ZU
fix
0/A
BOOL
ZU
fix
0
_STATE. IV
TB_SD_SPO_STATE_VALUE
Quality descriptor "not topical"
NT
BOOL
ZU
fix
1
_STATE. NT
TB_SD_SPO_STATE_VALUE
Quality descriptor "overflow" OV
BOOL
ZU
fix
0
_STATE. OV
TB_SD_SPO_STATE_VALUE
Cause of transmission "GI"
BOOL
WI
fix
0
_STATE. GI
TB_SD_SPO_STATE_VALUE
Cause of transmission "spontaneous"
*
BOOL
WI
fix
0
_STATE. S
TB_SD_SPO_STATE_VALUE
Quality descriptor "substituted"
SB
BOOL
ZU
opt
0
_SB
Quality descriptor "blocked"
BOOL
ZU
opt
0
_BL
BOOL
ZU
opt
0
_PN
BOOL
ZU
opt
0
_T
BOOL
ZU
opt
0
_R
USINT
ZU
opt
4
_COT
SVA
Quality descriptor "invalid"
Confirmation
Test
*
BL
P/N
T
Redundancy
*
Cause of transmission
98
IV
COT
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02
Automation
Originator address
USINT
ZU
opt
0
_ORIGINATO
R
Time and date
TIME
ZU
opt
0
_TIMETAG
TB_SD_SYSTEM_TIME
Measured value, short floating point number TI 36
Element in Message
Format STO
MEM
INIT
Signal_Ext
Name of Structure
Short floating point number
REAL
ZU
fix
0/A
BOOL
ZU
fix
Quality descriptor "not topical"
NT
BOOL
ZU
fix
0
_STATE. IV
TB_SD_SPO_STATE_VALUE
1
_STATE. NT
TB_SD_SPO_STATE_VALUE
Quality descriptor "overflow" OV
BOOL
ZU
fix
0
_STATE. OV
TB_SD_SPO_STATE_VALUE
Cause of transmission "GI"
BOOL
WI
fix
0
_STATE. GI
TB_SD_SPO_STATE_VALUE
Cause of transmission "spontaneous"
*
BOOL
WI
fix
0
_STATE. S
TB_SD_SPO_STATE_VALUE
Quality descriptor "substituted"
SB
BOOL
ZU
opt
0
_SB
Quality descriptor "blocked"
BOOL
ZU
opt
0
_BL
BOOL
ZU
opt
0
_PN
BOOL
ZU
opt
0
_T
BOOL
ZU
opt
0
_R
USINT
ZU
opt
0
_COT
Originator address
USINT
ZU
opt
0
_ORIGINATO
R
Time and date
TIME
ZU
opt
0
_TIMETAG
TB_SD_SYSTEM_TIME
Format STO
MEM
INIT
Signal_Ext
Name of Structure
DINT
ZU
fix
0
. CR
TB_SD_SPO_TI37_BCR
Sequence number SQ
USINT
ZU
fix
0
. SQ
TB_SD_SPO_TI37_BCR
Carry
CY
BOOL
ZU
fix
0
. CY
TB_SD_SPO_TI37_BCR
Preset
CA
BOOL
ZU
fix
0
. CA
TB_SD_SPO_TI37_BCR
Invalid
IV
BOOL
WI
fix
0
_STATE. IV
TB_SD_SPO_STATE_COUNT
Cause of transmission "spontaneous"
*
BOOL
WI
fix
0
_STATE. S
TB_SD_SPO_STATE_COUNT
Confirmation
BOOL
ZU
opt
0
_PN
BOOL
ZU
opt
0
_T
BOOL
ZU
opt
0
_R
Quality descriptor "invalid"
Confirmation
Test
IV
*
BL
P/N
T
Redundancy
*
Cause of transmission
COT
Integrated totals TI 37
Element in Message
Binary counter reading
Test
BCR
P/N
T
Redundancy
*
Cause of transmission
USINT
ZU
opt
0
_COT
Originator address
COT
USINT
ZU
opt
0
_ORIGINATO
R
Time and date
TIME
ZU
opt
0
_TIMETAG
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
TB_SD_SYSTEM_TIME
99
Automation
Event of protection equipment TI 38
Element in Message
Format STO
MEM
INIT
Signal_Ext
Name of Structure
Single event of protection
equipment
OFF
BOOL
ZU
fix
0
. Off
TB_SD_SPO_TI38_SEP
Single event of protection
equipment
ON
BOOL
ZU
fix
0
. On
TB_SD_SPO_TI38_SEP
Elapsed time
UINT
ZU
fix
0
. ET
TB_SD_SPO_TI38_SEP
BOOL
ZU
fix
0
_STATE. IV
TB_SD_SPO_STATE_PROT
BOOL
ZU
fix
1
_STATE. NT
TB_SD_SPO_STATE_PROT
BOOL
ZU
fix
0
_STATE. EI
TB_SD_SPO_STATE_PROT
Cause of transmission
"spontaneous"
*
BOOL
WI
fix
0
_STATE. S
TB_SD_SPO_STATE_PROT
Quality descriptor "substituted"
SB
BOOL
ZU
opt
0
_SB
Quality descriptor "blocked"
BOOL
ZU
opt
0
_BL
BOOL
ZU
opt
0
_PN
BOOL
ZU
opt
0
_T
BOOL
ZU
opt
0
_R
USINT
ZU
opt
0
_COT
Originator address
USINT
ZU
opt
0
_ORIGINATO
R
Time and date
TIME
ZU
opt
0
_TIMETAG
TB_SD_SYSTEM_TIME
Quality descriptor "invalid"
Quality descriptor
"not topical"
NT
Elapsed time invalid
Confirmation
Test
IV
EI
BL
P/N
T
Redundancy
*
Cause of transmission
COT
Blocked activation of the protection TI 39
Element in Message
Format STO
MEM
INIT
Signal_Ext
Name of Structure
General start of operation
BOOL
ZU
fix
0
. GS
TB_SD_SPO_TI39_SPE
Start of operation phase L1
BOOL
ZU
fix
0
. SL1
TB_SD_SPO_TI39_SPE
Start of operation phase L2
BOOL
ZU
fix
0
. SL2
TB_SD_SPO_TI39_SPE
Start of operation phase L3
BOOL
ZU
fix
0
. SL3
TB_SD_SPO_TI39_SPE
Start of operation IE (earth
current)
BOOL
ZU
fix
0
. SIE
TB_SD_SPO_TI39_SPE
Start of operation in reverse
direction
BOOL
ZU
fix
0
. SRD
TB_SD_SPO_TI39_SPE
Relay duration time
UINT
ZU
fix
0
. RDT
TB_SD_SPO_TI39_SPE
Quality descriptor "invalid"
BOOL
ZU
fix
0
_STATE. IV
TB_SD_SPO_STATE_PROT
Quality descriptor "not topical"
NT
BOOL
ZU
fix
1
_STATE. NT
TB_SD_SPO_STATE_PROT
Elapsed time invalid
BOOL
ZU
fix
0
_STATE. EI
TB_SD_SPO_STATE_PROT
Cause of transmission
"spontaneous"
*
BOOL
WI
fix
0
_STATE. S
TB_SD_SPO_STATE_PROT
Quality descriptor
"substituted"
BOOL
ZU
opt
0
_SB
BOOL
ZU
opt
0
_BL
BOOL
ZU
opt
0
_PN
BOOL
ZU
opt
0
_T
BOOL
ZU
opt
0
_R
Test
100
P/N
T
Redundancy
EI
SB
Quality descriptor "blocked"
Confirmation
IV
*
BL
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02
Automation
Cause of transmission
COT
USINT
ZU
opt
0
_COT
Originator address
USINT
ZU
opt
0
_ORIGINATO
R
Time and date
TIME
ZU
opt
0
_TIMETAG
TB_SD_SYSTEM_TIME
Blocked triggering of the protection TI 40
Element in Message
Format STO
MEM
INIT
Signal_Ext
Name of Structure
General command to output
circuit
BOOL
ZU
fix
0
. GC
TB_SD_SPO_TI40_OCI
Command to output circuit phase
L1
BOOL
ZU
fix
0
. CL1
TB_SD_SPO_TI40_OCI
Command to output circuit phase
L2
BOOL
ZU
fix
0
. CL2
TB_SD_SPO_TI40_OCI
Command to output circuit phase
L3
BOOL
ZU
fix
0
. CL3
TB_SD_SPO_TI40_OCI
Relay operation time
UINT
ZU
fix
0
. ROT
TB_SD_SPO_TI40_OCI
BOOL
ZU
fix
0
_STATE. IV
TB_SD_SPO_STATE_PROT
Quality descriptor "not topical"
NT
BOOL
ZU
fix
1
_STATE. NT
TB_SD_SPO_STATE_PROT
Elapsed time invalid
BOOL
ZU
fix
0
_STATE. EI
TB_SD_SPO_STATE_PROT
Cause of transmission
"spontaneous"
*
BOOL
WI
fix
0
_STATE. S
TB_SD_SPO_STATE_PROT
Quality descriptor
"substituted"
BOOL
ZU
opt
0
_SB
BOOL
ZU
opt
0
_BL
BOOL
ZU
opt
0
_PN
BOOL
ZU
opt
0
_T
BOOL
ZU
opt
0
_R
USINT
ZU
opt
0
_COT
Originator address
USINT
ZU
opt
0
_ORIGINATO
R
Time and date
TIME
ZU
opt
0
_TIMETAG
TB_SD_SYSTEM_TIME
Format STO
MEM
INIT
Signal_Ext
Name of Structure
Quality descriptor "invalid"
Test
EI
SB
Quality descriptor "blocked"
Confirmation
IV
BL
P/N
T
Redundancy
*
Cause of transmission
COT
Single command TI 45
Element in Message
single command state
SCS
BOOL
WI
fix
0
. STATE
TB_SD_SPO_TI45_SCO
qualifier of command
QU
USINT
WI
fix
0
. QOC
TB_SD_SPO_TI45_SCO
BOOL
WI
fix
0
. S_E
TB_SD_SPO_TI45_SCO
Cause of transmission
activation, deactivation
BOOL
WI
fix
0
_STATE. S
TB_SD_SPO_STATE_
COMMAND
Confirmation
BOOL
ZU
opt
0
_PN
BOOL
ZU
opt
0
_T
BOOL
ZU
opt
0
_R
USINT
WI
opt
0
_COT
Originator address
USINT
ZU
opt
0
_ORIGINATO
R
Time and date
TIME
ZU
opt
0
_TIMETAG
Select / execute
Test
S/E
P/N
T
Redundancy
*
Cause of transmission
COT
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
TB_SD_SYSTEM_TIME
101
Automation
Double command TI 46
Element in Message
Format STO
MEM
INIT
Signal_Ext
Name of Structure
double command state
DCS / OFF
BOOL
WI
fix
0
. Off
TB_SD_SPO_TI46_DCO
double command state
DCS / ON
BOOL
WI
fix
0
. On
TB_SD_SPO_TI46_DCO
USINT
WI
fix
0
. QOC
TB_SD_SPO_TI46_DCO
S/E
BOOL
WI
fix
0
. S_E
TB_SD_SPO_TI46_DCO
Cause of trans-mission
activation,
deactivation
BOOL
WI
fix
0
_STATE. S
TB_SD_SPO_STATE_
COMMAND
Confirmation
BOOL
ZU
opt
0
_PN
BOOL
ZU
opt
0
_T
BOOL
ZU
opt
0
_R
USINT
WI
opt
0
_COT
Originator address
USINT
ZU
opt
0
_ORIGINATO
R
Time and date
TIME
ZU
opt
0
_TIMETAG
TB_SD_SYSTEM_TIME
qualifier of command
Select / execute
Test
QU
P/N
T
Redundancy
*
Cause of transmission
COT
Regulating step command TI 47
Element in Message
Format STO
MEM
INIT
Signal_Ext
Name of Structure
Regulating step command
RCO / LOWER
BOOL
WI
fix
0
. LOWER
TB_SD_SPO_TI47_RCO
Regulating step command
RCO / HIGHER
BOOL
WI
fix
0
. HIGHER
TB_SD_SPO_TI47_RCO
USINT
WI
fix
0
. QOC
TB_SD_SPO_TI47_RCO
BOOL
WI
fix
0
. S_E
TB_SD_SPO_TI47_RCO
Cause of transmission
activation, deactivation
BOOL
WI
fix
0
_STATE. S
TB_SD_SPO_STATE_
COMMAND
Confirmation
BOOL
ZU
opt
0
_PN
BOOL
ZU
opt
0
_T
BOOL
ZU
opt
0
_R
USINT
WI
opt
0
_COT
Originator address
USINT
ZU
opt
0
_ORIGINATO
R
Time and date
TIME
ZU
opt
0
_TIMETAG
TB_SD_SYSTEM_TIME
Qualifier of command
Select / execute
Test
QU
S/E
P/N
T
Redundancy
*
Cause of transmission
COT
Setpoint command, normalized value TI 48
Element in Message
Format STO
MEM
INIT
Signal_Ext
Name of Structure
Normalized value NVA
REAL
ZU
fix
0/A
. VALUE
TB_SD_SPO_TI48_SP_NVA
USINT
ZU
fix
0
. QL
TB_SD_SPO_TI48_SP_NVA
BOOL
ZU
fix
0
. S_E
TB_SD_SPO_TI48_SP_NVA
Cause of transmission
activation, deactivation
BOOL
WI
fix
0
_STATE. S
TB_SD_SPO_STATE_
COMMAND
Confirmation
BOOL
ZU
opt
0
_PN
BOOL
ZU
opt
0
_T
BOOL
ZU
opt
0
_R
Qualifier of command
Select / execute
Test
102
S/E
P/N
T
Redundancy
QL
*
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02
Automation
Cause of transmission
COT
USINT
ZU
opt
0
_COT
Originator address
USINT
ZU
opt
0
_ORIGINATO
R
Time and date
TIME
ZU
opt
0
_TIMETAG
TB_SD_SYSTEM_TIME
Setpoint command, normalized value TI 49
Element in Message
Format STO
MEM
INIT
Signal_Ext
Name of Structure
Scaled value
INT
ZU
fix
0/A
. VALUE
TB_SD_SPO_TI49_SP_SVA
USINT
ZU
fix
0
. QL
TB_SD_SPO_TI49_SP_SVA
BOOL
ZU
fix
0
. S_E
TB_SD_SPO_TI49_SP_SVA
Cause of transmission
activation, deactivation
BOOL
WI
fix
0
_STATE. S
TB_SD_SPO_STATE_
COMMAND
Confirmation
BOOL
ZU
opt
0
_PN
BOOL
ZU
opt
0
_T
BOOL
ZU
opt
0
_R
USINT
ZU
opt
0
_COT
Originator address
USINT
ZU
opt
0
_ORIGINATO
R
Time and date
TIME
ZU
opt
0
_TIMETAG
SVA
Qualifier of command
Select / execute
Test
QL
S/E
P/N
T
Redundancy
*
Cause of transmission
COT
TB_SD_SYSTEM_TIME
Setpoint command, short floating point number TI 50
Element in Message
Format STO
MEM
INIT
Signal_Ext
Name of Structure
Short floating point number
REAL
ZU
fix
0/A
. VALUE
TB_SD_SPO_TI50_SP_SFP
USINT
ZU
fix
0
. QL
TB_SD_SPO_TI50_SP_SFP
BOOL
ZU
fix
0
. S_E
TB_SD_SPO_TI50_SP_SFP
Cause of transmission
activation, deactivation
BOOL
WI
fix
0
_STATE. S
TB_SD_SPO_STATE_
COMMAND
Confirmation
BOOL
ZU
opt
0
_PN
BOOL
ZU
opt
0
_T
BOOL
ZU
opt
0
_R
USINT
ZU
opt
0
_COT
Originator address
USINT
ZU
opt
0
_ORIGINATO
R
Time and date
TIME
ZU
opt
0
_TIMETAG
TB_SD_SYSTEM_TIME
Format STO
MEM
INIT
Signal_Ext
Name of Structure
UDINT
ZU
fix
0
Cause of transmission
activation,
deactivation
BOOL
WI
fix
0
_STATE. S
TB_SD_SPO_STATE_
COMMAND
Confirmation
BOOL
ZU
opt
0
_PN
BOOL
ZU
opt
0
_T
BOOL
ZU
opt
0
_R
USINT
ZU
opt
0
_COT
Qualifier of command
Select / execute
Test
QL
S/E
P/N
T
Redundancy
*
Cause of transmission
COT
Bitstring of 32 bit TI 51
Element in Message
Binary status information
Test
BSI
P/N
T
Redundancy
*
Cause of transmission
COT
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
103
Automation
Originator address
USINT
ZU
opt
0
_ORIGINATO
R
Time and date
TIME
ZU
opt
0
_TIMETAG
5.2.4.2
TB_SD_SYSTEM_TIME
Conversion of Spontaneous Information Objects to Periodical
Information
This function enables signals assigned in CAEX plus of basic data of the spontaneous
information objects to be converted to periodical information. This periodical information is
transmitted directly to the peripheral elements over the Ax 1703 peripheral bus.
For which spontaneous information objects this function is available, can be seen in chapter
"Characteristics of the Messages".
5.2.4.3
Synchronization of the Input Process Images
At the beginning of every cycle of a task, the synchronization of the input process image of the
corresponding task takes place by copying over the signals from the input process images for
periodical information, system information and spontaneous information objects. Only signals
are copied over that are assigned to the task.
Due to the synchronization a consistent process image is ensured for the duration of the
program execution of the task.
Dependent on the source of the signal (periodical information, system information or
spontaneous information object) different signal processing operations are performed.
During the synchronization test switches are taken into account. These test switches can be
switched on and –off by means of the Online Test and prevent an updating of the selected
signals for all tasks.
Test switches are possible for:
104
•
one periodical information
•
all periodical information
•
all elements of one spontaneous information object
•
all elements of all spontaneous information objects
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02
Automation
5.2.4.3.1 Periodical Information
The synchronization of the input process images takes place by copying over the states of all
periodical information of a peripheral element, if at least one periodical information of the
peripheral element in the corresponding task is assigned as a signal.
A copying over of the periodical information of a peripheral element does not occur:
•
on failure of the peripheral element
─ peripheral element not available
─ wrong peripheral element configured
─ transmission error on the Ax 1703 peripheral bus
─ peripheral element defect
•
if the test switch for the periodical information is activated
On failure of the peripheral element, the states before the failure are retained and the
periodical information "Module failed" is set for the corresponding peripheral element.
Note
Which periodical information is available for a peripheral element can be referred to in the corresponding
system element manual.
The following diagram shows the times, at which the input process images are updated for
each task.
System clock
10ms
10ms
10ms
10ms
10ms
10ms
10ms
10ms
10ms
10ms
10ms
Time handling and Ax-PE bus
Transmission of period. information
Fast task
Cycle time 20ms
Task
Cycle time 30ms
Slow task
Cycle time 50ms
Legende
Task running
Copying periodical information
Task able to run but interrupted
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
105
Automation
5.2.4.3.2 System Information
The synchronization of the input process images takes place by copying over all system
information, if at least one system information is assigned as a signal in the corresponding
task.
Explanation of the designations and values used in the following tables.
Spaltenname
enthält
Format
Bedeutung
gibt den Wertebereich und den Speicherbedarf im
Prozessabbild an
BOOL
binär
Wertebereich 0/1
USINT
analog
Wertebereich 0 ... 255
UINT
analog
Wertebereich 0 ... 65.535
TIME
Tabelle
Wertebereich 8 x 0 ... 255
The following table shows the possible system information and their features:
106
Signal Name
Format
Features
SvSystemInput.CycleTime
TIME
current time at the moment of the cycle start of the
task
SvSystemInput.Init
BOOL
is set for the duration of the stationary cycles of the
corresponding task.
SvSystemInput.Onlinetest
BOOL
is set for the duration of the active online test
SvSystemInput.Systemstart
BOOL
is set for the duration of the stationary cycles after a
startup of the basic system element.
SvSystemInput.Warmstart
BOOL
is set during the first cycle after a warm start of the
corresponding task for one cycle, regardless of
whether stationary cycles or not
SvSystemInput.Coldstart
BOOL
is set during the first cycle after a cold start of the
corresponding task for one cycle, regardless of
whether stationary cycles or not
SvSystemInput.RuntimeError
BOOL
is set during the next cycle after a timeout of the
corresponding task for one cycle
SvSystemInput.RegNr
USINT
Region number of the automation unit on which the
application program is running
SvSystemInput.CmpNr
USINT
Component number of the automation unit on which
the application program is running
SvSystemInput.BSENr
USINT
Number of the basic system element on which the
application program is running
SvSystemInput.
RuntimeErrorCount
UINT
is set for one cycle of the corresponding task, after
the initialization has been terminated
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02
Automation
Signal Name
Format
Features
SvSystemInput.
BOOL
Command output busy
CommandBusy
set:
if the command input is initiated for a command with
parameterized 1-out-of-n check. (receipt of the
spontaneous information object "Command" (ACT)
regardless of whether select or execute)
reset:
if the command output procedure is ended
• pulse commands:
After transmission of the spontaneous information
object "Command" with ACTTERM or negative
ACTCON
• setpoint command or Bitstring of 32 bit:
After transmission of the spontaneous information
object "Command" positive or negative ACTCON
SvSystemInput.
BOOL
CommandLocked
SvSystemInput.
Sum command interlocked
is set with interlocking violation for one cycle of the
corresponding task
TIME
ShortPulseDuration
short command output time
Parameter AU common settings | Short pulse
duration
Updating on startup and with parameter change
SvSystemInput.
LongPulseDuration
TIME
long command output time
Parameter AU common settings | Long pulse
duration
Updating on startup and with parameter change
5.2.4.3.3 Spontaneous Information Objects
The synchronization of the input process images takes place by copying over the basic data
and standard states of the spontaneous information object, if at least one element of the
spontaneous information object is assigned as a signal in the corresponding task. The copying
over of an additional status only takes place, if it is also assigned to a signal.
A copying over of the spontaneous information object does not occur, if the test switch for the
spontaneous information object is activated.
Normally the state of the spontaneous information object in the input process image of the
corresponding task is copied.
Transient handling for elements without change of state
With certain elements of spontaneous information objects (e.g. command) no change of the
information occurs through the transmission. For this information, a negative edge is
automatically generated in the following cycle. Which elements of the spontaneous
information object are affected by this, is described for each type identification in chapter
"Input Process Image for Spontaneous Information Objects" column "STO".
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
107
Automation
5.2.5
Output Handling
The output handling is used for updating the local peripheral elements (periodical information)
and the message generation for system information and spontaneous information objects after
the program execution of a task.
The output handling is available for each task and consists of:
•
Updating of Local Peripheral Elements for Periodical Information
•
Generation of Messages with System Information
•
Generation of Diagnostic Information
•
Change Monitoring for Spontaneous Information Objects
•
Generation of Messages with Process Information
Before the data transfer, test switches are taken into account. These test switches can be
switched on and off by means of the Online Test and prevent an updating of the selected
signals for all tasks.
Test switches are possible for:
5.2.5.1
•
one periodical information item
•
all periodical information
•
all elements of one spontaneous information object
•
all elements of all spontaneous information objects
Updating of Local Peripheral Elements for Periodical Information
The updating of the peripheral elements takes place by copying over the output process
images for periodical information in the process images of the peripheral elements with the
help of the Ax 1703 peripheral bus.
An updating of a periodical information of a peripheral element does not occur:
•
if an incorrect peripheral element is configured
•
if the test switch for the periodical information is activated
The updating of a peripheral element takes place with the cycle of the highest-priority task,
which has an assignment to a periodical information of this peripheral element.
Note
Which periodical information a peripheral element processes, can be referred to in the corresponding
system element manual.
5.2.5.2
Generation of Messages with System Information
With the application program messages with system information can be generated with the
help of special function blocks.
The following table shows which messages with system information are generated with which
function block.
108
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02
Automation
5.2.5.3
Message with system
information in control direction
Function Block
(General) interrogation command
TB_GENERAL_INTERROGATION
Counter interrogation command
TB_COUNTER_INTERROGATION
Generation of Diagnostic Information
By means of the application program, with the help of special function blocks diagnostic
information of the class "E(xternal)" and "W(arning)" can be set or reset.
The following table shows which diagnostic information are generated with which function
block.
5.2.5.4
Diagnostic Information
Function Block
Class "E(xternal)"
TB_SET_DIAG_ERROR
Class "W(arning)"
TB_SET_DIAG_WARNING
Change Monitoring for Spontaneous Information Objects
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 a grid of the cycle time of each task, in which the signal
is assigned to a spontaneous information object.
The change monitoring acts on basic data and selected elements of the spontaneous
information objects (see column "GEN" in the table in chapter "Output Process Image of
Spontaneous Information Objects")
On a change of the state in a corresponding element of the spontaneous information object,
the generation of the message is initiated.
Thereby several methods are used for the decision "valid change":
•
every change of the information state of the signal regardless in which new state
•
change of the information state of the signal with a positive edge
•
change according to the rules of the additive threshold value procedure
Which method of change monitoring is used for an element in the spontaneous information
object can be referred to in the column "GEN" in the table in chapter "Output Process Image
of Spontaneous Information Objects".
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
109
Automation
5.2.5.4.1 Additive Threshold Value Procedure
The additive threshold value procedure prevents an unnecessary loading of the links with
insignificant changes of the corresponding signal and acts only on the basic data of the
spontaneous information objects with measured values.
In the grid of the cycle time of the corresponding task, the measured value is monitored for
change. If the deviation from the last spontaneously transmitted measured value is greater
than the set unconditional threshold (absolute_threshold), the new measured value is
transmitted immediately. Otherwise, in the grid of the cycle time of the corresponding task the
deviations from the last spontaneously transmitted measured value are added according to
polarity sign. First when the amount of this total exceeds the set additive threshold
(add._threshold) is the current measured value spontaneously transmitted.
A transmission of the measured value due to a general interrogation does not influence the
threshold value procedure.
Each measured value is determined by means of parameterization:
─ absolute_threshold 0.0
-
3.37x10
─ add._threshold
-
3.37x10
0.0
38
38
Examples
Cycle Time
0.1s
Thresh_uncond
80
Thresh_additive
6000
Example 1: After transmission due to the exceeding of the large threshold, the value
has changed once by 79 (< the large threshold) and subsequently
remains constant. The measured value is transmitted after 7,5 seconds.
0,0s
0,1s
0,2s
0,3s
0,4s
0,5s
0,6s
0,7s
0,8s
... 7,4s
7,5s
Measured value
300
379
379
379
379
379
379
379
379
... 379
379
Difference
>80
79
79
79
79
79
79
79
79
... 79
79
Additive total
0
79
158
237
316
395
474
553
632
... 5925 6004
Transmission
x
x
Example 2: After transmission due to the exceeding of the large threshold, the value
has changed once by 1 (< the large 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
... 599s 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.
110
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02
Automation
5.2.5.5
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
1
0
0
1
1
2
1
... 0
1
Transmission
x
Generation of Messages with Process Information
If a spontaneous information object has been activated for transmission due to a change, a
message with process information is generated.
The generation of the message is carried out in every task, in which a signal has been
assigned to the corresponding spontaneous information object.
Special case:if different elements of a spontaneous information object are assigned from
several tasks, the message generation takes place in the highest-priority task with an
assignment to this spontaneous information object
Generation of the message means:
•
•
Entry of the parameterized message address (CASDU and IOA)
Entry of the time tag either
─ the current time at the start of the cycle of the corresponding task
(i.e. resolution of the time tag = cycle time of the task) or
─ the time information from a signal, if <Signal name>_TIMETAG has been assigned to this
spontaneous information object.
•
Data transfer of the message to the internal distribution of messages with process
information.
5.2.5.5.1 Test Switches
With the generation of messages with process information test switches are taken into
account. These test switches can be switched on and –off by means of the online test and
prevent a transfer of the message for the selected spontaneous information object.
Test switches are possible for:
•
all elements of one spontaneous information object
•
all elements of all spontaneous information objects
Attention
If a spontaneous information object is switched to test, it is not transferred with the quality descriptor
"blocked".
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
111
Automation
5.2.5.5.2 Behavior with General Interrogation
With a GI-request, all GI-capable messages with process information of all tasks are
transferred.
To keep the system load as little as possible, the messages are transferred staggered.
In a grid of 30ms, beginning with the highest-priority task, n messages of a task are
transmitted. If there are no more GI-capable messages to transmit in a task, it is skipped.
The following table specifies the number of messages to be transmitted for each task:
Task
Number of Messages
Fast task
10
Task
5
Slow task
5
Special case: Stationary cycles
After completion of the stationary cycles, all GI-capable messages with process information of
the initialized task are transferred staggered.
Special case: Spontaneous information object in test
The state is transferred, that existed before the "switch to test".
5.2.5.5.3 Message Characteristics
Explanation of the symbols, designations and values used in the following tables.
Column Name
contains
TI
PLC
Type identification of the spontaneous information object
YES / NO
GI
Message can be processed by the open-/closed-loop control
function
GI-capable
YES
Spontaneous information object is also transmitted with a
general interrogation
NO
Spontaneous information object is only transmitted with a
change
ADD
YES / NO
Message generation with additive change monitoring
PER
YES / NO
Direct transfer of the basic data of a message to the
peripheral elements as periodical information
GEN
ReqMem
112
Meaning
Message generation
SYS
Message is automatically generated by the system with
change
FBS
Message must be generated by a function block in the
application program.
<value>
[in bytes]
Specifies, how much memory is required in the process
images at least (without additional status) for a message.
Each assigned additional status is to be added. Values see
Output process images for spontaneous information objects
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02
Automation
Message with process information
in monitor direction
TI
PLC
GI
ADD
PER
GEN
ReqMem
Single-point information
30
YES
YES
NO
YES
SYS
1
Double-point information
31
YES
YES
NO
NO
SYS
2
Step position information
32
YES
YES
NO
NO
SYS
2
Bitstring of 32 bit
33
YES
YES
NO
NO
SYS
4
Measured value, normalized value
34
YES
YES
YES
YES
SYS
4
Measured value, scaled value
35
YES
YES
YES
NO
SYS
2
Measured value, short floating point
number
36
YES
YES
YES
YES
SYS
4
Integrated totals
37
YES
NO
NO
NO
SYS
7
Event of protection equipment
38
YES
NO
NO
NO
SYS
4
Blocked activation of the protection
39
YES
NO
NO
NO
SYS
8
Blocked triggering of the protection
40
YES
NO
NO
NO
SYS
6
Packed single-point information with
status change detection
20
NO
-
-
-
-
-
Single command
45
YES
NO
NO
NO
SYS
3
Double command
46
YES
NO
NO
NO
SYS
4
Regulating step command
47
YES
NO
NO
NO
SYS
4
Set point command, normalized value
48
YES
NO
NO
NO
SYS
6
Set point command, scaled value
49
YES
NO
NO
NO
SYS
4
Set point command, short floating point
number
50
YES
NO
NO
NO
SYS
6
Bitstring of 32 bit
51
YES
NO
NO
NO
SYS
4
(General) interrogation command
100
YES
NO
-
-
FBS
10
Counter interrogation command
101
YES
NO
-
-
FBS
10
Clock synchronization command
103
NO
-
-
-
-
-
Container for system information
135
NO
-
-
-
-
-
Container for process information
142
NO
-
-
-
-
-
Message with process information
in control direction
Message with system information
in control direction
Message with transparent information
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
113
Automation
5.2.5.5.4 Output Process Image for Spontaneous Information Objects
Explanation of the symbols, designations and values used in the following tables.
Column
Name
Element in
Message
contains
Meaning
Element (bold)
Basic data of a spontaneous information object
element
Standard- or additional status
element *
These elements are not defined in the standard 60870-5-101/104, but rather are
made available internally
specifies the value range and the required memory in the process image
Format
BOOL
binary
value range 0/1
USINT
analog
value range 0 … 255
INT
analog
value range -32,768 … 32,767
UINT
analog
value range 0 … 65,535
DINT
analog
value range
-2,147,483,648 … 2,147,483,647
required memory 4 byte
UDINT
analog
value range 0 … 4,294,967,294
required memory 4 byte
REAL
analog
value range short real
8.43 x 10 –37 ... 3.37 x 1038
required memory 4 byte
value range 8 x 0 … 255
required memory 8 byte
TIME
GEN
114
required memory 2 byte
required memory 2 byte
specifies with which event a message is generated
with change of the information state of the signal
POS
with a positive edge of the signal
ADD
according to the rules of the additive change monitoring
NO
no generation
specifies, when memory is assigned in the process images
fix
These elements always occupy memory in the process images, even if only one
element is assigned
opt
These elements only occupy memory in the process images, if they are also
assigned.
YES / NO
specifies whether an initial value can be input by the OPM II
Signal_Ext
Name of
structure
required memory 1 byte
YES
MEM
INIT
Table
required memory 1 byte
specifies, with which extension the signal name (the element in the message) can
be assigned. The extensions are defined in structure definitions (see column
"Name of Structure")
no entry
the signal name without extension indicates basic data in the message if these
only consist of one element
.<ext>
indicates individual elements of basic data in the message, if they consist of
several elements
_STATE <ext>
indicates standard states in the message
_<ext>
indicates additional states in the message
specifies the name of the structure, in which the extension of the signal name is
defined
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02
Automation
Single-point information TI 30
Element in Message
Format GEN
MEM
INIT
Signal_Ext
Name of Structure
Single-point information
SPI
BOOL
YES
fix
NO
Quality descriptor "invalid"
IV
BOOL
YES
opt
NO
_STATE. IV
TB_SD_SPO_STATE_BIN_INF
Quality descriptor "not topical"
NT
BOOL
YES
opt
NO
_STATE. NT
TB_SD_SPO_STATE_BIN_INF
Cause of transmission "GI"
BOOL
POS
opt
NO
_STATE. GI
TB_SD_SPO_STATE_BIN_INF
Cause of transmission
"spontaneous"
*
BOOL
POS
opt
NO
_STATE. S
TB_SD_SPO_STATE_BIN_INF
Quality descriptor
"substituted"
BOOL
YES
opt
NO
_SB
BOOL
YES
opt
NO
_BL
BOOL
YES
opt
NO
_PN
BOOL
YES
opt
NO
_T
BOOL
YES
opt
NO
_R
USINT
YES
opt
NO
_COT
Originator address
USINT
NO
opt
NO
_ORIGINATO
R
Time and date
TIME
YES
opt
NO
_TIMETAG
TB_SD_SYSTEM_TIME
SB
Quality descriptor "blocked"
Confirmation
Test
*
BL
P/N
T
Redundancy
*
Cause of transmission
COT
Double-point information TI 31
Element in Message
Format GEN
MEM
INIT
Signal_Ext
Name of Structure
Double-point information
DPI / OFF
BOOL
YES
fix
NO
. Off
TB_SD_SPO_TI31_DPI
Double-point information
DPI / ON
BOOL
YES
fix
NO
. On
TB_SD_SPO_TI31_DPI
BOOL
YES
opt
NO
_STATE. IV
TB_SD_SPO_STATE_BIN_INF
Quality descriptor "not topical"
NT
BOOL
YES
opt
NO
_STATE. NT
TB_SD_SPO_STATE_BIN_INF
Cause of trans-mission "GI"
BOOL
POS
opt
NO
_STATE. GI
TB_SD_SPO_STATE_BIN_INF
Cause of transmission
"spontaneous"
*
BOOL
POS
opt
NO
_STATE. S
TB_SD_SPO_STATE_BIN_INF
Quality descriptor
"substituted"
BOOL
YES
opt
NO
_SB
BOOL
YES
opt
NO
_BL
BOOL
YES
opt
NO
_PN
BOOL
YES
opt
NO
_T
BOOL
YES
opt
NO
_R
USINT
YES
opt
NO
_COT
Originator address
USINT
NO
opt
NO
_ORIGINATO
R
Time and date
TIME
YES
opt
NO
_TIMETAG
Quality descriptor "invalid"
Test
*
SB
Quality descriptor "blocked"
Confirmation
IV
BL
P/N
T
Redundancy
*
Cause of transmission
COT
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
TB_SD_SYSTEM_TIME
115
Automation
Step position information TI 32
Element in Message
Format GEN
MEM
INIT
Signal_Ext
Name of Structure
Value
USINT
YES
fix
NO
. VALUE
TB_SD_SPO_TI32_VTI
Intermediate state
BOOL
YES
fix
NO
. TSI
TB_SD_SPO_TI32_VTI
BOOL
YES
opt
NO
_STATE. IV
TB_SD_SPO_STATE_VALUE
Quality descriptor "not topical"
NT
BOOL
YES
opt
NO
_STATE. NT
TB_SD_SPO_STATE_VALUE
Quality descriptor "overflow" OV
BOOL
YES
opt
NO
_STATE. OV
TB_SD_SPO_STATE_VALUE
Cause of transmission "GI"
BOOL
POS
opt
NO
_STATE. GI
TB_SD_SPO_STATE_VALUE
Cause of transmission
"spontaneous"
*
BOOL
POS
opt
NO
_STATE. S
TB_SD_SPO_STATE_VALUE
Quality descriptor
"substituted"
BOOL
YES
opt
NO
_SB
BOOL
YES
opt
NO
_BL
BOOL
YES
opt
NO
_PN
BOOL
YES
opt
NO
_T
BOOL
YES
opt
NO
_R
USINT
YES
opt
NO
_COT
Originator address
USINT
NO
opt
NO
_ORIGINATO
R
Time and date
TIME
YES
opt
NO
_TIMETAG
TB_SD_SYSTEM_TIME
Signal_Ext
Name of Structure
Quality descriptor "invalid"
Test
*
SB
Quality descriptor "blocked"
Confirmation
IV
BL
P/N
T
Redundancy
*
Cause of transmission
COT
Bitstring of 32 bit TI 33
Element in Message
Format GEN
MEM
INIT
Binary status information
BSI
UDINT
YES
fix
NO
Quality descriptor "invalid"
IV
BOOL
YES
opt
NO
_STATE. IV
TB_SD_SPO_STATE_VALUE
Quality descriptor "not topical"
NT
BOOL
YES
opt
NO
_STATE. NT
TB_SD_SPO_STATE_VALUE
Quality descriptor "overflow" OV
BOOL
YES
opt
NO
_STATE. OV
TB_SD_SPO_STATE_VALUE
Cause of transmission "GI"
BOOL
POS
opt
NO
_STATE. GI
TB_SD_SPO_STATE_VALUE
Cause of transmission
"spontaneous"
*
BOOL
POS
opt
NO
_STATE. S
TB_SD_SPO_STATE_VALUE
Quality descriptor
"substituted"
BOOL
YES
opt
NO
_SB
BOOL
YES
opt
NO
_BL
BOOL
YES
opt
NO
_PN
BOOL
YES
opt
NO
_T
BOOL
YES
opt
NO
_R
SB
Quality descriptor "blocked"
Confirmation
Test
*
BL
P/N
T
Redundancy
*
Cause of transmission
USINT
YES
opt
NO
_COT
Originator address
USINT
NO
opt
NO
_ORIGINATO
R
Time and date
TIME
YES
opt
NO
_TIMETAG
116
COT
TB_SD_SYSTEM_TIME
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02
Automation
Measured value, normalized value TI 34
Element in Message
Format GEN
MEM
INIT
Signal_Ext
Name of Structure
Normalized value NVA
REAL
ADD
fix
NO
BOOL
YES
opt
NO
_STATE. IV
TB_SD_SPO_STATE_VALUE
Quality descriptor "not topical"
NT
BOOL
YES
opt
NO
_STATE. NT
TB_SD_SPO_STATE_VALUE
Quality descriptor "overflow" OV
BOOL
YES
opt
NO
_STATE. OV
TB_SD_SPO_STATE_VALUE
Cause of transmission "GI"
BOOL
POS
opt
NO
_STATE. GI
TB_SD_SPO_STATE_VALUE
Cause of transmission
"spontaneous"
*
BOOL
POS
opt
NO
_STATE. S
TB_SD_SPO_STATE_VALUE
Quality descriptor
"substituted"
BOOL
YES
opt
NO
_SB
BOOL
YES
opt
NO
_BL
BOOL
YES
opt
NO
_PN
BOOL
YES
opt
NO
_T
BOOL
YES
opt
NO
_R
USINT
YES
opt
NO
_COT
Originator address
USINT
NO
opt
NO
_ORIGINATO
R
Time and date
TIME
YES
opt
NO
_TIMETAG
TB_SD_SYSTEM_TIME
Signal_Ext
Name of Structure
Quality descriptor "invalid"
Test
*
SB
Quality descriptor "blocked"
Confirmation
IV
BL
P/N
T
Redundancy
*
Cause of transmission
COT
Measured value, scaled value TI 35
Element in Message
Format GEN
MEM
INIT
Scaled value
INT
ADD
fix
NO
BOOL
YES
opt
NO
_STATE. IV
TB_SD_SPO_STATE_VALUE
Quality descriptor "not topical"
NT
BOOL
YES
opt
NO
_STATE. NT
TB_SD_SPO_STATE_VALUE
Quality descriptor "overflow" OV
BOOL
YES
opt
NO
_STATE. OV
TB_SD_SPO_STATE_VALUE
Cause of transmission "GI"
BOOL
POS
opt
NO
_STATE. GI
TB_SD_SPO_STATE_VALUE
Cause of transmission
"spontaneous"
*
BOOL
POS
opt
NO
_STATE. S
TB_SD_SPO_STATE_VALUE
Quality descriptor "substituted"
SB
BOOL
YES
opt
NO
_SB
Quality descriptor "blocked"
BOOL
YES
opt
NO
_BL
BOOL
YES
opt
NO
_PN
BOOL
YES
opt
NO
_T
BOOL
YES
opt
NO
_R
USINT
YES
opt
NO
_COT
Originator address
USINT
NO
opt
NO
_ORIGINATO
R
Time and date
TIME
YES
opt
NO
_TIMETAG
SVA
Quality descriptor "invalid"
Confirmation
Test
IV
*
BL
P/N
T
Redundancy
*
Cause of transmission
COT
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
TB_SD_SYSTEM_TIME
117
Automation
Measured value, short floating point number TI 36
Element in Message
Format GEN
MEM
INIT
Signal_Ext
Name of Structure
Short floating point number
REAL
ADD
fix
NO
BOOL
YES
opt
NO
_STATE. IV
TB_SD_SPO_STATE_VALUE
Quality descriptor "not topical"
NT
BOOL
YES
opt
NO
_STATE. NT
TB_SD_SPO_STATE_VALUE
Quality descriptor "overflow" OV
BOOL
YES
opt
NO
_STATE. OV
TB_SD_SPO_STATE_VALUE
Cause of transmission "GI"
BOOL
POS
opt
NO
_STATE. GI
TB_SD_SPO_STATE_VALUE
Cause of transmission
"spontaneous"
*
BOOL
POS
opt
NO
_STATE. S
TB_SD_SPO_STATE_VALUE
Quality descriptor "substituted"
SB
BOOL
YES
opt
NO
_SB
Quality descriptor "blocked"
BOOL
YES
opt
NO
_BL
BOOL
YES
opt
NO
_PN
BOOL
YES
opt
NO
_T
BOOL
YES
opt
NO
_R
USINT
YES
opt
NO
_COT
Originator address
USINT
NO
opt
NO
_ORIGINATO
R
Time and date
TIME
YES
opt
NO
_TIMETAG
TB_SD_SYSTEM_TIME
Format GEN
MEM
INIT
Signal_Ext
Name of Structure
Quality descriptor "invalid"
Confirmation
Test
IV
*
BL
P/N
T
Redundancy
*
Cause of transmission
COT
Integrated totals TI 37
Element in Message
Binary counter reading
DINT
YES
fix
NO
. CR
TB_SD_SPO_TI37_BCR
Sequence number SQ
USINT
YES
fix
NO
. SQ
TB_SD_SPO_TI37_BCR
Carry
CY
BOOL
YES
fix
NO
. CY
TB_SD_SPO_TI37_BCR
Preset
CA
BOOL
YES
fix
NO
. CA
TB_SD_SPO_TI37_BCR
Invalid
IV
BOOL
YES
opt
NO
_STATE. IV
TB_SD_SPO_STATE_COUNT
Cause of transmission "spontaneous"
*
BOOL
POS
opt
NO
_STATE. S
TB_SD_SPO_STATE_COUNT
Confirmation
BOOL
YES
opt
NO
_PN
BOOL
YES
opt
NO
_T
BOOL
YES
opt
NO
_R
USINT
YES
opt
NO
_COT
Originator address
USINT
NO
opt
NO
_ORIGINATO
R
Time and date
TIME
YES
opt
NO
_TIMETAG
Test
P/N
T
Redundancy
*
Cause of transmission
118
BCR
COT
TB_SD_SYSTEM_TIME
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02
Automation
Event of protection equipment TI 38
Element in Message
Format GEN
MEM
INIT
Signal_Ext
Name of Structure
Single event of protection
equipment
OFF
BOOL
YES
fix
NO
. Off
TB_SD_SPO_TI38_SEP
Single event of protection
equipment
ON
BOOL
YES
fix
NO
. On
TB_SD_SPO_TI38_SEP
Elapsed time
UINT
YES
fix
NO
. ET
TB_SD_SPO_TI38_SEP
BOOL
YES
opt
NO
_STATE. IV
TB_SD_SPO_STATE_PROT
Quality descriptor "not topical"
NT
BOOL
YES
opt
NO
_STATE. NT
TB_SD_SPO_STATE_PROT
Elapsed time invalid
BOOL
YES
opt
NO
_STATE. EI
TB_SD_SPO_STATE_PROT
Cause of transmission
"spontaneous"
*
BOOL
POS
opt
NO
_STATE. S
TB_SD_SPO_STATE_PROT
Quality descriptor
"substituted"
BOOL
YES
opt
NO
_SB
BOOL
YES
opt
NO
_BL
BOOL
YES
opt
NO
_PN
BOOL
YES
opt
NO
_T
BOOL
YES
opt
NO
_R
USINT
YES
opt
NO
_COT
Originator address
USINT
NO
opt
NO
_ORIGINATO
R
Time and date
TIME
YES
opt
NO
_TIMETAG
Quality descriptor "invalid"
Test
EI
SB
Quality descriptor "blocked"
Confirmation
IV
BL
P/N
T
Redundancy
*
Cause of transmission
COT
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
TB_SD_SYSTEM_TIME
119
Automation
Blocked activation of the protection TI 39
Element in Message
Format GEN
MEM
INIT
Signal_Ext
Name of Structure
General start of operation
BOOL
YES
fix
NO
. GS
TB_SD_SPO_TI39_SPE
Start of operation phase L1
BOOL
YES
fix
NO
. SL1
TB_SD_SPO_TI39_SPE
Start of operation phase L2
BOOL
YES
fix
NO
. SL2
TB_SD_SPO_TI39_SPE
Start of operation phase L3
BOOL
YES
fix
NO
. SL3
TB_SD_SPO_TI39_SPE
Start of operation IE (earth
current)
BOOL
YES
fix
NO
. SIE
TB_SD_SPO_TI39_SPE
Start of operation in reverse
direction
BOOL
YES
fix
NO
. SRD
TB_SD_SPO_TI39_SPE
Relay duration time
UINT
YES
fix
NO
. RDT
TB_SD_SPO_TI39_SPE
BOOL
YES
opt
NO
_STATE. IV
TB_SD_SPO_STATE_PROT
Quality descriptor "not topical"
NT
BOOL
YES
opt
NO
_STATE. NT
TB_SD_SPO_STATE_PROT
Elapsed time invalid
BOOL
YES
opt
NO
_STATE. EI
TB_SD_SPO_STATE_PROT
Cause of transmission
"spontaneous"
*
BOOL
POS
opt
NO
_STATE. S
TB_SD_SPO_STATE_PROT
Quality descriptor
"substituted"
BOOL
YES
opt
NO
_SB
BOOL
YES
opt
NO
_BL
BOOL
YES
opt
NO
_PN
BOOL
YES
opt
NO
_T
BOOL
YES
opt
NO
_R
Quality descriptor "invalid"
Test
EI
SB
Quality descriptor "blocked"
Confirmation
IV
BL
P/N
T
Redundancy
*
Cause of tran-mission
USINT
YES
opt
NO
_COT
Originator address
USINT
NO
opt
NO
_ORIGINATO
R
Time and date
TIME
YES
opt
NO
_TIMETAG
120
COT
TB_SD_SYSTEM_TIME
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02
Automation
Blocked triggering of the protection TI 40
Element in Message
Format GEN
MEM
INIT
Signal_Ext
Name of Structure
General command to output
circuit
BOOL
YES
fix
NO
. GC
TB_SD_SPO_TI40_OCI
Command to output circuit
phase L1
BOOL
YES
fix
NO
. CL1
TB_SD_SPO_TI40_OCI
Command to output circuit
phase L2
BOOL
YES
fix
NO
. CL2
TB_SD_SPO_TI40_OCI
Command to output circuit
phase L3
BOOL
YES
fix
NO
. CL3
TB_SD_SPO_TI40_OCI
UINT
YES
fix
NO
. ROT
TB_SD_SPO_TI40_OCI
BOOL
YES
opt
NO
_STATE. IV
TB_SD_SPO_STATE_PROT
Quality descriptor "not topical"
NT
BOOL
YES
opt
NO
_STATE. NT
TB_SD_SPO_STATE_PROT
Elapsed time invalid
BOOL
YES
opt
NO
_STATE. EI
TB_SD_SPO_STATE_PROT
Cause of transmission
"spontaneous"
*
BOOL
POS
opt
NO
_STATE. S
TB_SD_SPO_STATE_PROT
Quality descriptor "substituted"
SB
BOOL
YES
opt
NO
_SB
Quality descriptor "blocked"
BOOL
YES
opt
NO
_BL
BOOL
YES
opt
NO
_PN
BOOL
YES
opt
NO
_T
BOOL
YES
opt
NO
_R
USINT
YES
opt
NO
_COT
Originator address
USINT
NO
opt
NO
_ORIGINATO
R
Time and date
TIME
YES
opt
NO
_TIMETAG
TB_SD_SYSTEM_TIME
Relay operation time
Quality descriptor "invalid"
Confirmation
Test
IV
EI
BL
P/N
T
Redundancy
*
Cause of transmission
COT
Single command TI 45
Element in Message
Format GEN
MEM
INIT
Signal_Ext
Name of Structure
single command state
SCS
BOOL
POS
fix
NO
. STATE
TB_SD_SPO_TI45_SCO
Qualifier of command
QU
USINT
NO
fix
YES
. QOC
TB_SD_SPO_TI45_SCO
BOOL
POS
fix
NO
. S_E
TB_SD_SPO_TI45_SCO
Cause of transmission
activation, deactivation
BOOL
POS
opt
NO
_STATE. S
TB_SD_SPO_STATE_
COMMAND
Confirmation
BOOL
YES
opt
NO
_PN
BOOL
YES
opt
NO
_T
BOOL
YES
opt
NO
_R
USINT
YES
opt
NO
_COT
Originator address
USINT
NO
opt
NO
_ORIGINATO
R
Time and date
TIME
YES
opt
NO
_TIMETAG
Select / execute
Test
S/E
P/N
T
Redundancy
*
Cause of transmission
COT
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
TB_SD_SYSTEM_TIME
121
Automation
Double command TI 46
Element in Message
Format GEN
MEM
INIT
Signal_Ext
Name of Structure
double command state
DCS / OFF
BOOL
POS
fix
NO
. Off
TB_SD_SPO_TI46_DCO
double command state
DCS / ON
BOOL
POS
fix
NO
. On
TB_SD_SPO_TI46_DCO
USINT
NO
fix
YES
. QOC
TB_SD_SPO_TI46_DCO
BOOL
POS
fix
NO
. S_E
TB_SD_SPO_TI46_DCO
Cause of transmission
activation, deactivation
BOOL
POS
opt
NO
_STATE. S
TB_SD_SPO_STATE_
COMMAND
Confirmation
BOOL
YES
opt
NO
_PN
BOOL
YES
opt
NO
_T
BOOL
YES
opt
NO
_R
Qualifier of command
Select / execute
Test
QU
S/E
P/N
T
Redundancy
*
Cause of transmission
USINT
YES
opt
NO
_COT
Originator address
COT
USINT
NO
opt
NO
_ORIGINATO
R
Time and date
TIME
YES
opt
NO
_TIMETAG
TB_SD_SYSTEM_TIME
Regulating step command TI 47
Element in Message
Format GEN
MEM
INIT
Signal_Ext
Name of Structure
Regulating step command
RCO / LOWER
BOOL
POS
fix
NO
. LOWER
TB_SD_SPO_TI47_RCO
Regulating step command
RCO / HIGHER
BOOL
POS
fix
NO
. HIGHER
TB_SD_SPO_TI47_RCO
USINT
NO
fix
YES
. QOC
TB_SD_SPO_TI47_RCO
Qualifier of command
Select / execute
QU
BOOL
POS
fix
NO
. S_E
TB_SD_SPO_TI47_RCO
Cause of transmission
activation, deactivation
BOOL
POS
opt
NO
_STATE. S
TB_SD_SPO_STATE_
COMMAND
Confirmation
BOOL
YES
opt
NO
_PN
BOOL
YES
opt
NO
_T
BOOL
YES
opt
NO
_R
USINT
YES
opt
NO
_COT
Originator address
USINT
NO
opt
NO
_ORIGINATO
R
Time and date
TIME
YES
opt
NO
_TIMETAG
Test
S/E
P/N
T
Redundancy
*
Cause of transmission
122
COT
TB_SD_SYSTEM_TIME
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02
Automation
Setpoint command, normalized value TI 48
Element in Message
Format GEN
MEM
INIT
Signal_Ext
Name of Structure
Normalized value NVA
REAL
YES
fix
NO
. VALUE
TB_SD_SPO_TI48_SP_NVA
Qualifier of setpoint
command
QL
USINT
YES
fix
YES
. QL
TB_SD_SPO_TI48_SP_NVA
Select / execute
BOOL
YES
fix
NO
. S_E
TB_SD_SPO_TI48_SP_NVA
Cause of transmission
activation, deactivation
BOOL
POS
opt
NO
_STATE. S
TB_SD_SPO_STATE_
COMMAND
Confirmation
BOOL
YES
opt
NO
_PN
BOOL
YES
opt
NO
_T
BOOL
YES
opt
NO
_R
USINT
YES
opt
NO
_COT
Originator address
USINT
NO
opt
NO
_ORIGINATO
R
Time and date
TIME
YES
opt
NO
_TIMETAG
TB_SD_SYSTEM_TIME
Test
S/E
P/N
T
Redundancy
*
Cause of transmission
COT
Setpoint command, normalized value TI 49
Element in Message
Format GEN
MEM
INIT
Signal_Ext
Name of Structure
Scaled value
SVA
INT
YES
fix
NO
. VALUE
TB_SD_SPO_TI49_SP_SVA
Qualifier of setpoint command
QL
USINT
YES
fix
YES
. QL
TB_SD_SPO_TI49_SP_SVA
Select / execute
BOOL
YES
fix
NO
. S_E
TB_SD_SPO_TI49_SP_SVA
Cause of transmission
activation,
deactivation
BOOL
POS
opt
NO
_STATE. S
TB_SD_SPO_STATE_
COMMAND
Confirmation
BOOL
YES
opt
NO
_PN
BOOL
YES
opt
NO
_T
BOOL
YES
opt
NO
_R
USINT
YES
opt
NO
_COT
Originator address
USINT
NO
opt
NO
_ORIGINATO
R
Time and date
TIME
YES
opt
NO
_TIMETAG
Test
S/E
P/N
T
Redundancy
*
Cause of transmission
COT
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
TB_SD_SYSTEM_TIME
123
Automation
Setpoint command, short floating point number TI 50
Element in Message
Format GEN
MEM
INIT
Signal_Ext
Name of Structure
Short floating point number
REAL
YES
fix
NO
. VALUE
TB_SD_SPO_TI50_SP_SFP
Qualifier of setpoint
command
QL
USINT
YES
fix
YES
. QL
TB_SD_SPO_TI50_SP_SFP
Select / execute
BOOL
YES
fix
NO
. S_E
TB_SD_SPO_TI50_SP_SFP
Cause of transmission
activation,
deactivation
BOOL
POS
opt
NO
_STATE. S
TB_SD_SPO_STATE_
COMMAND
Confirmation
BOOL
YES
opt
NO
_PN
BOOL
YES
opt
NO
_T
BOOL
YES
opt
NO
_R
USINT
YES
opt
NO
_COT
Originator address
USINT
NO
opt
NO
_ORIGINATO
R
Time and date
TIME
YES
opt
NO
_TIMETAG
TB_SD_SYSTEM_TIME
Format GEN
MEM
INIT
Signal_Ext
Name of Structure
UDINT
YES
fix
NO
Cause of transmission
activation,
deactivation
BOOL
POS
opt
NO
_STATE. S
TB_SD_SPO_STATE_
COMMAND
Confirmation
BOOL
YES
opt
NO
_PN
BOOL
YES
opt
NO
_T
BOOL
YES
opt
NO
_R
USINT
YES
opt
NO
_COT
Originator address
USINT
NO
opt
NO
_ORIGINATO
R
Time and date
TIME
YES
opt
NO
_TIMETAG
Test
S/E
P/N
T
Redundancy
*
Cause of transmission
COT
Bitstring of 32 bit TI 51
Element in Message
Binary status information
Test
P/N
T
Redundancy
*
Cause of transmission
124
BSI
COT
TB_SD_SYSTEM_TIME
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02
Automation
5.2.6
Loading of Application Program (Reload)
The following situations are to be distinguished with the loading of an application program:
•
Loading with operational interruption
Changes have been made to the application program, that
(a)
necessitate a startup of the basic system element (see following table)
(b)
do not maintain the functional continuity of the application program
•
Loading without operational interruption
Changes have been made to the application program, that
(c)
(d)
do not necessitate a startup (see following table) and
maintain the functional continuity of the application program.
Whether or not the functional continuity of the application program is maintained, depends of
the type and extent of the change. It is maintained for example, if
─ after change, the function corresponds completely with that before change (change not
noticeable from "outside")
─ only new functional parts were added, that do not affect those that already existed
─ parameters of a controller are adapted, that do not cause any jump reply
Note
The TOOLBOX II keeps track of changes applied to an application program by maintaining a revision
counter, and remembers the most recently loaded revision of each application program. If the revision of
the currently running application program is not identical with that of the most recently loaded, after the
loading of the new revision of the application program, a startup of the open-/closed-loop control function
is carried out with a cold start.
Functions in detail
After the loading of the application program for:
•
Variables or signals
only an initialization of newly added variables and signals takes place (see "Startup of the
Open-/Closed-Loop Control Function"). For newly added "Retain" variables and signals a
cold start is performed.
Attention
With a change of the initial value for an existing variable or signal, this is not accepted immediately. The
new initial value is first effective with a startup of the basic system element or the open-/closed-loop
control function (cold- or warm start tripped by the Online-Test)..
•
Programs or tasks
only an initialization of new tasks or programs takes place with a startup of the open/closed-loop control function with a cold start.
•
Global parameters, curves and sets of curves
an initialization takes place for all global parameters, curves and sets of curves with a cold
start.
The following table shows which changes in the application program (a) necessitate a startup
of the basic system element, and (c) which are accepted without.
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
125
Automation
Change
(a)
Element of a spontaneous information object is assigned to a signal (input and
output)
x
Assignments of all elements of a spontaneous information object are removed (input
and output)
x
Storage method for a spontaneous information object is changed (message
processing chronological <=> state stored)
x
Source identification for a message (expert parameter)
x
Initial values for the qualifier of command (short/long command output time)
x
Thresholds of the additive change monitoring
x
Configuration of the peripheral elements (installing, deleting, preparing)
Periodical information of a configured peripheral element is assigned to a signal
(input and output)
5.2.7
(c)
x
x
Online-Test
The following test functionalities are available:
•
5.2.7.1
Display/Forcing of values
•
Test switches input-/output messages or PE input/output-PIM´s
•
Changing the execution status of the open-/closed-loop control function
•
Setting breakpoints
•
Real time archive
•
Display status information
•
Read and write variables
Display/Forcing of Values
In the online test, values
•
in online-test-fields and
•
in value-fields
can be displayed and / or forced.
For that specific modules are needed, that must be included with the creation of the function
diagram.
Display
•
126
Display of boolean variables (line values)
The status of boolean variables is represented by a corresponding coloring of the variable
(TRUE = red or FALSE = blue).
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02
Automation
•
Display of other variables
The status of these variables can be displayed via OLT-fields or by selecting (cursor) the
variable and pressing the ALT-key.
The switchover of all variables between text display and value display is only possible with
several OLT-fields.
•
Display of structures
Structures are also displayed via OLT-fields, whereby however always only 1 structure
element can be assigned to an OLT-field. I.e. the display of complete structures is
presently not possible.
Forcing
Forcing means an intervention by the user in the logic of the program by changing the value of
the variable.
One-time forcing
With CAEx plus one can change the value of variables in the online test. This type of change
however only has validity, as long as this variable is not overwritten again through functionality
(e.g.: through a connection). Consequently the one-time forcing remains limited to the
following types of variables of a POE:
•
VAR, that are not given any assignment in the functionality
•
VAR_EXT, that have not been connected
Permanent forcing
Through the permanent forcing, a connection is changed in such a way, that a constant value
specified by the user is used instead of the actual source of the connection.
Permanent forcing is possible:
•
for arbitrary connections
By interconnecting a force-marker one determines, which arbitrary connections can be
permanently forced at later time and which not.
the force-marker must already be taken into account with the creation of the function
diagram (in the FBS-Editor), i.e. if a new force-marker is inserted during the test phase,
then the program must be regenerated and reloaded.
5.2.7.2
Test Switches
By means of test switches, that can be controlled with the online test, the copy operation (for
synchronization or updating of process images) for
•
messages (spontaneous information objects)
─ for each message or
─ all messages
•
periodical information
─ for each information or
─ each peripheral element
is enabled or blocked both input- as well as output-side.
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
127
Automation
5.2.7.3
Changing the Processing Status of the Controller
Stop controller
The resource is halted. The input- and output images are no longer updated, the last values
are retained. Messages for the input process image, that are to be handled in chronological
order, are piled up.
Start controller
The halted resource is started. No initialization steps such as e.g. stationary cycles are
performed. Piled-up messages are processed.
Perform cold start of the resource
Cold start of the controller as described in chapter „Initialization“.
Perform warm start of the resource
Warm start of the controller as described in chapter „Initialization“.
Halt task
The input- and output images assigned to the task are no longer updated, the last values are
retained. Messages for the input process image of the task, that are to be handled in
chronological order, are piled up.
Continue task
The halted task is started. No initialization steps such as e.g. stationary cycles are performed.
Piled-up messages are processed.
Perform cold start of a task
Cold start of the task as described in chapter „Initialization“. A cold start can also take place
with a current task. The initialization takes place between two cycles task cycles can
thereby be omitted.
Perform warm start of a task
Warm start of the task as described in chapter „Initialization“. A warm start can also take place
with a current task. The initialization takes place between two cycles task cycles can
thereby be omitted.
Halt program
The program is halted. The input- and output images continue to be updated. Chronological
(message or global) messages can possibly be discarded during the stoppage of the
application program.
128
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02
Automation
Continue program
The program continues to be executed again without any initialization.
5.2.7.4
Breakpoints
Through the breakpoint function the following operating steps are possible:
•
Breakpoint
•
Cycle step
Breakpoint
Up to 4 breakpoints can be defined for a trigger condition. The logic operation of these
breakpoints can be set to logical "AND" or "OR".
The condition can be set for each of these breakpoints:
•
Variable of the BOOL type
Value equal to or not equal to 0 or 1
•
Variable of the INT or REAL type
the set value
Value smaller, equal to, not equal to or greater than
The check of trigger condition takes place at the end of the selected task. If the trigger
condition is fulfilled, depending on the setting
•
the selected task or
•
the resource
is stopped and a diagnostic information of the class „Test“ is set.
Cycle step
In the operating mode "Cycle step" the selected task is executed one time and then halted.
5.2.7.5
Real Time Archive
The real time archive of the open-/closed-loop control function is a function, that records
variables or signals after every cycle. Which variables and signals are to be recorded, can be
defined with the TOOLBOX II tool "CAEx plus Online-Test". As a result it is possible to display
changes of variables and signals chronologically with the help of the oscilloscope function.
A chronological display of value changes is also possible without the real time archive.
However the display of the value changes takes place, in the best case, with a resolution of
200ms (dependent on the number of values to be displayed and the baud rate). It can thereby
happen, that value changes smaller than the resolution are not signaled on the monitor
screen.
The real time archive has a memory with a capacity of 100 KBytes for one resource.
The real time archive records the defined variables and signals in this memory. There are 2
possibilities of terminating the recording:
•
by means of operator input in "CAEX plus Online Test" or
•
by means of a definable Trigger Condition
If the recording is terminated by an operator input, the entire memory is utilized as pre-history.
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
129
Automation
If the recording is terminated by the trigger condition, the memory is split up into a pre- and
post-history. On reaching the trigger condition, recording continues until the memory for the
post-history has been filled.
How much memory is utilized for the pre- and post-history, is determined by a percentage
setting in the online test. The moment between pre- and post-history is determined by a
trigger condition. The check of trigger condition takes place at the end of the selected task.
Which variables and signals and in which periodicity these variables and signals are to
recorded in the real time archive, is determined in the online test. The periodicity is
determined by assigning the recording to a task. From its cycle time and the setting of how
many cycles are to be omitted between the recordings, the resolution of the display in the
oscilloscope function is produced.
Resolution [ms] = cycle time [ms] of the selected task * (number of cycles to be omitted +1)
Note
If this resolution is greater than the cycle time of that/those task(s) that handle(s) the selected variables
and signals, value changes can be lost for the display!
Note
The consistency of the recorded variables and signals with each other is only guaranteed for the selected
recording task and for higher-priority tasks!
The time period for the pre- and post-history is dependent on the number of variables and
signals that are to be recorded and the aforementioned resolution. For the calculation of the
time period, for a BOOL type variable 1 byte is to be taken into account, for the INT type 2
bytes and for the REAL type 4 bytes.
Time period [ms] =
102400 / (number of variables of type BOOL +
(number of variables of type INT or REAL * 4)) *
resolution [ms]
Trigger Condition
The trigger condition can consist of up to 4 so-called "Watchpoints". The logic operation of
these watchpoints can be set to logical "AND" or "OR".
The condition can be set for each of these watchpoints:
•
Variable of the BOOL type
Value equal to or not equal to 0 or 1
•
Variable of the INT or REAL type
the set value
Value smaller, equal to, not equal to or greater than
An activated trigger condition sets a diagnostic information of the class „Test“. A tripping of the
trigger condition sets a further diagnostic information of the class „Test“.
A termination of the online test does not automatically delete the trigger condition. I.e. The
recording in the archive does not need any active connected TOOLBOX II. A read out of the
real time archive is possible at any time.
130
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02
Automation
5.2.7.6
Display Status Information
With the function "Display status information“, for each task
•
the parameterized cycle time
•
the current run time (in 10µs)
•
the maximum run time (in 10µs)
•
the number of timeouts
can be interrogated.
With the interrogation of the status information, a reset of the current run time or the number
of timeouts is possible as an option.
5.2.7.7
Terminating the Online Test
If the online test is terminated, the following set test functions are automatically cancelled
again:
•
Halt resource, task, program
•
Breakpoints
The following functions are only deactivated after positive confirmation of the inquiry on
terminating the online test:
•
Test Switches
•
Force-Markers
•
Real Time Archive
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
131
Automation
5.3
Treatment for Commands to the Open-/Closed-Loop
Control Function according to IEC 60870-5-101/104
The treatment for commands serves for the check of 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 command (TI = 45, 58)
─ double command (TI = 46, 59)
─ regulating step command (TI = 47, 60)
•
Setpoint values
─ set point command, normalized value (TI = 48, 61)
─ set point command, scaled value (TI = 49, 62)
─ set point command, short floating point number (TI = 50, 63)
•
Bitstring
─ Bitstring of 32 bit (TI = 51, 64)
The data transfer of the spontaneous information objects to the application program of the
open-/closed-loop control function for further processing is dependent on the result of these
checks.
The activation of the element or function to be controlled is the task of the application program
of the open-/closed-loop control function.
For the proper operation of this function, information is required by the application program of
the open-/closed-loop control function (e.g. from an interlocking logic) for the choice of a
positive or negative confirmation.
The treatment for command is only performed, if the parameter IEC_Enable has been set.
This parameter can be set individually for each command.
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
─ control location check
─ command locking
─ system-element overlapping 1-out-of-n check
•
Initiate command output procedure
─ command to application program
•
Monitor pulse duration (only pulse commands)
─ command output time
─ return information monitoring
•
Terminate command output procedure (only pulse commands)
General Functions
•
Error handling
The following information are transported over the data interface:
132
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02
Automation
Information
System information
• Information to the application program
− Cmd_Busy (command output busy)
− Cmd_Locked (sum command interlocked)
• Information from the application program
− Sys_1_out_of_n_ena
(system-element overlapping 1-out-of-n
enable)
− Ctrl_Location (control location)
− Set (control location takeover)
− State (control location state)
Category
GetCmdBusy
GetCmdLocked
SetCmd_1_out_of_n_
ena
SetControlLocation
SetControlLocation
SetControlLocation
spontaneous information
objects
• Information to the treatment for commands and
in a broader consequence to the application
program
−
−
−
−
−
−
single command
double command
regulating step command
set point command, normalized value
set point command, scaled value
set point command, short floating point
number
− Bitstring of 32 bit
• Information from the application program
− command x interlocked
− return information x
• Information to the application program
− sum command interlocked
data type
data type
data type
data type
data type
data type
data type
interlocking image
RI image
The column "Category" specifies, with which function block the system information is
processed or with which parameter of the category "process-technical message" the message
address of the spontaneous information object is to be parameterized.
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
133
Automation
5.3.1
Pulse Commands
Principle
Application program of the
open-/closed loop control function
Treatment for pulse commands
spontaneous information object Command
x
(ACT, S/E = select or execute)
Prepare command initiation
Formal check
Retry suppression
Direct or select- and
execute command
Control location check
Command interlocking
spontaneous information object
„Command x interlocked“
1-out-of-n check
System-overlapping
1-out-of-n check
system information „Command
system information „Sum
spontanes Informationsobjekt
output busy“
system information „1-out-of-n
enable“
command interlocked“
Command x (ACT/CON)
if S/E = execute
Command x to application program
Initiate command
output procedure
Monitor pulse duration
Return information
monitoring or
Command output
time
Spontaneous information object
„Return information x“
Terminate command
output procedure
Spontaneous information object
Command x (ACT/TERM)
Procedure
Function
Actions and Checks
Prepare command
output procedure
Receipt of the spontaneous information object
command (ACT)
• Formal check
Error Handling
Cancel
• Retry suppression
• Direct or
select and execute
command
134
Cancel
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02
Automation
• Control location check
Cancel with
diagnostic
• Command locking
Cancel with
diagnostic
• 1-out-of-n check
Set internal state "Command output busy", if the
parameter 1_of_n for this command is set
Cancel with
diagnostic
• System-element
overlapping 1-out-of-n
check
Set system data point "Command output busy"
and wait for "1-out-of-n enable", if the parameter
1_of_n_t > 0 for this command is set
Cancel with
diagnostic
Initiate command
output procedure
Send the spontaneous information object
command (ACTCON)
• Command to
application program
Only at execute command (S/E = execute)
Monitor pulse duration
• Command output time
Only at execute command (S/E = execute)
• Return information
monitoring
Only at execute command (S/E = execute)
Terminate command
output procedure
Only at execute command (S/E = execute)
Send the spontaneous information object
command (ACTTERM) and
reset system data point and the internal
information "Command output busy", if the
parameter 1_of_n for this command is set
If a faulty state is detected during this procedure an immediate abortion of the treatment takes
place. Depending on the error, various measures are initiated (see Error Handling).
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
135
Automation
5.3.2
Setpoint Values
Principle
Application program of the
open-/closed loop control function
Treatment for setpoint command
spontaneous information object Command
x
(ACT, S/E = select or execute)
Prepare command initiation
Formal check
Retry suppression
Direct or select- and
execute command
Control location check
Command interlocking
spontaneous information object
„Command x interlocked“
1-out-of-n check
System-overlapping
1-out-of-n check
system information „Command
system information „1-out-of-n
system information „Sum
spontanes Informationsobjekt
output busy“
enable“
command interlocked“
Command x (ACT/CON)
if S/E = execute
Command x to application program
Initiate command
output procedure
Terminate command
output procedure
Procedure
Function
Actions and Checks
Prepare command
output procedure
Receipt of the spontaneous information object
command (ACT)
• Formal check
Error Handling
Cancel
• Retry suppression
136
• Direct or
select and execute
command
Cancel
• Control location check
Cancel with
diagnostic
• Command locking
Cancel with
diagnostic
• 1-out-of-n check
Set internal state "Command output busy", if the
parameter 1_of_n for this command is set
Cancel with
diagnostic
• System-element
overlapping 1-out-of-n
check
Set system data point "Command output busy" and
wait for "1-out-of-n enable" , if the parameter 1_of_n
> 0 for this command is set
Cancel with
diagnostic
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02
Automation
Initiate command
output procedure
Send the spontaneous information object command
(ACTCON)
• Command to
application program
Only at execute command (S/E = execute)
Terminate command
output procedure
Only at execute command (S/E = execute)
Reset system data point and the internal information
"Command output busy", if the parameter 1_of_n for
this command is set
If a faulty state is detected during this procedure an immediate abortion of the treatment takes
place. Depending on the error, various measures are initiated (see Error Handling).
5.3.3
Bit String
Principle
Treatment for bitstring of 32 bits
spontaneous information object Command
Application program of the
open-/closed loop control function
x
(ACT, S/E = execute)
Prepare command initiation
Formal check
Retry suppression
Control location
check
Command
interlocking
1-out-of-n check
system-overlapping
1-out-of-n check
spontaneous information object
spontaneous information object
„Command x interlocked“
system information „Command
output busy“
system information „1-out-of-n
system information „Sum
enable“
command interlocked“
Command x (ACT/CON)
Initiate command
output procedure
Command x to application program
Terminate command
output procedure
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
137
Automation
Procedure
Function
Actions and Checks
Prepare command
output procedure
Receipt of the spontaneous information object
command (ACT)
• Formal check
Error Handling
Cancel
• Retry suppression
• Control location check
Cancel with
diagnostic
• Command locking
Cancel with
diagnostic
• 1-out-of-n check
Set internal state "Command output busy", if the
parameter 1_of_n for this command is set
Cancel with
diagnostic
• System-element
overlapping 1-out-of-n
check
Set system data point "Command output busy" and
wait for "1-out-of-n enable" , if the parameter 1_of_n
> 0 for this command is set
Cancel with
diagnostic
Initiate command
output procedure
Send the spontaneous information object command
(ACTCON)
• Command to
application program
Terminate command
output procedure
Reset system data point and the internal information
"Command output busy", if the parameter 1_of_n for
this command is set
If a faulty state is detected during this procedure an immediate abortion of the treatment takes
place. Depending on the error, various measures are initiated (see Error Handling).
5.3.4
Functions in Detail
5.3.4.1
Prepare Command Output Procedure
5.3.4.1.1 Formal Check
Before a command can be executed, a formal check is performed on the spontaneous
information object "command".
The following checks are performed:
•
Cause of transmission is
─ "Activation" or
─ "Cancellation of activation"
•
Qualifier of command is
─ no determination or
─ short command execution time or
138
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02
Automation
─ long command execution time
•
Command state of a single command is
─ ON (OFF is not allowed)
•
Command state of a double command is
─ OFF or
─ ON
•
Command state of a regulating step command is
─ HIGHER or
─ LOWER
If the formal check is not passed,
•
the command is rejected
•
the activation is negatively confirmed
5.3.4.1.2 Retry Suppression
As a result of message repetition (Retries) on the link several spontaneous information objects
"Command" can be received with identical content. This can lead to errors of the command
output such as e.g. 1-out_of-n errors.
With the function Retry Suppression these spontaneous information objects are ignored.
Thereby the last corresponding message received is checked for equivalence (including the
time information).
5.3.4.1.3 Direct Command
The procedure for the command transmission according to IEC 60870-5-101/104 for "direct
command" is set by means of the parameter select_execute_t = 0.
On receipt of the spontaneous information object "Command" with cause of transmission set
to "activation" and the data point identifier "execute" the command output procedure with
following checks is initiated:
•
1-out-of-n check
•
Control location check
•
Command locking
•
System-element overlapping 1-out-of-n check
Depending on these checks a positive or negative confirmation of the activation takes place.
5.3.4.1.4 Select and Execute Command
The procedure for the command transmission according to IEC 60870-5-101/104 for "selectand execute command" is set by means of the parameter select_execute_t > 0. The
parameterized value specifies, within which time the execute command must be received
following the selection command.
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
139
Automation
Selection command (select)
On receipt of the spontaneous information object "Command" with cause of transmission set
to "activation" and the data point identifier "select", a check is performed whether the selection
command is permitted.
The following checks are performed:
•
Parameter select_execute_t > 0
•
Command not selected or not executing
If these conditions are not satisfied:
•
the command is rejected
•
the activation is negatively confirmed
If these conditions are satisfied, following checks are performed:
•
1-out-of-n check
•
Control location check
•
Command locking
•
System-element overlapping 1-out-of-n check
Depending on these checks a positive or negative confirmation of the activation takes place.
Upon positive confirmation of the activation the execute command is waited for.
Expiration of timeout
If the timeout (parameter select_execute_t) expired:
•
the command is rejected
Cancel the selection
This waiting state can be terminated by means of a spontaneous information object
"Command" with cause of transmission set to "deactivation", the qualifier of command "S/E" is
not relevant.
The following checks are performed:
•
Parameter select_execute_t > 0
•
The command to be canceled is selected, i.e. the elements of the spontaneous information
object of Select- and Execute command are identical except for the element “cause of
transmission”, "S/E" (irrelevant) and the elements for the timetag.
If these conditions are not satisfied:
•
a negative confirmation of the deactivation is transmitted
•
the selected command is NOT canceled.
If these conditions are satisfied:
•
the selected command is canceled and
•
a positive confirmation of the deactivation is transmitted
Note
If the selection command has not been confirmed (e.g. the enabling of the system-element overlapping
1-out-of-n check is still expected), a negative confirmation of the deactivation is transmitted and the
selected command is canceled.
140
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02
Automation
Execute command (execute)
On receipt of the spontaneous information object "Command" with cause of transmission set
to "activation" and the data point identifier "execute" within the parameterized time
select_execute_t following a selection command, a check is performed whether the
execute command is permitted.
•
Parameter select_execute_t > 0
•
Command not executing
•
The command to be executed is selected, i.e. the elements of the spontaneous
information object of Select- and Execute command are identical except for the element
"S/E" and for the elements of timetag
If these conditions are not satisfied:
•
the command is rejected
•
the activation is negatively confirmed
If these conditions are fulfilled, the command output procedure is initiated with the following
further checks:
•
1-out-of-n check
•
Control location check
•
Command locking
•
System-element overlapping 1-out-of-n check
Depending on these checks a positive or negative confirmation of the activation takes place.
5.3.4.1.5 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 locations previously set or if no control location has been preset:
•
the command is rejected
•
the activation is negatively confirmed
•
the system information "Sum command interlocked" is set for one cycle of the
corresponding task
•
a spontaneous information object "Sum command interlocked" (positive transient) is
transmitted with the originator address of the command..
Set control location
The control location is set with system information with the help of the function block
"TB_SET_CONTROL_LOCATION" and is valid for all commands of a system element. Up to
256 control locations can be set simultaneously.
Note
If a control location is never set, i.e. function block not used or no positive edge of the system information
"Control location takeover", the control location check is deactivated.
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
141
Automation
The selection and takeover of the control location must be carried out in the application
program of the open-/closed-loop control function on the particular system element.
The setting or adding of a control location or the deletion of all control locations is controlled
by the following system information:
•
control location
•
control location takeover
•
control location state
The following table shows the states of the system data points for the possible actions:
System Information
Action
Control
Location
Takeover
State
Setting or adding a control location
Originator
address
positive edge
ON
Delete all control locations
irrelevant
positive edge
OFF
Note
The control location(s) of the system element is (are) to be set after every startup.
For the definition of the control location, the following values indicate the originator address.
Originator address
Control Location
0
default
1 ... 127
remote command
128 ... 255
local command
5.3.4.1.6 Command Locking
With the help of the command locking, commands can be rejected or allowed processdependent. For this a process-dependent interlocking logic for each command or groups of
commands is to be created in the higher-level open-/closed-loop control function.
The information formed from this is to be signaled to the treatment for commands with a
spontaneous information object "Command x interlocked".
The corresponding information "Command x interlocked" must be assigned to a command
with the parameter Interlocking_Image of the category "Process-technical message" of the
product family CAEx plus.
If no assignment of the spontaneous information object "Command x interlocked" is carried
out for the corresponding command, the command locking is inactive for this command.
The following table shows the assignment of the information in the spontaneous information
object "Command x interlocked" to the command.
142
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02
Automation
Command
Command x Interlocked
Information Object
TI
Element
Information Object
TI
Element
Single command
45
SCS
single-point information
30
SPI
Double command
46
DCS / OFF
double-point information
31
DPI / OFF
DCS / ON
Step position command
47
RCS LOWER
DPI / ON
double-point information
31
DPI / OFF
DPI / ON
RCS
HIGHER
set point command,
normalized value
48
value
single-point information
30
SPI
set point command,
scaled value
49
value
single-point information
30
SPI
set point command, short
floating point number
50
value
single-point information
30
SPI
Bitstring of 32 bit
51
value
single-point information
30
SPI
Note
The elements of the double-point information are handled as two single-point information items (see Data
Interface)
If the corresponding information (sea previous table) is set in the spontaneous information
object "Command x locked":
•
the command is rejected
•
the activation is negatively confirmed
•
the system information "Command 1-out-of-n interlocked" is set for one cycle of the
corresponding task
•
a spontaneous information object "Sum command interlocked" (positive transient) is
transmitted with the originator address of the command..
5.3.4.1.7 1-out-of-n Check
With the 1-out_of-n check switched on, only one command is allowed at the same time. The
1-out-of-n check can be enabled per command using the parameter 1_of_n.
The 1-out_of-n check only acts on commands, that also have the 1-out-of-n check switched
on.
Commands that have the 1-out-of-n check switched on interlock all other commands that also
have the 1-out-of-n check switched on.
Commands that do not have the 1-out-of-n check switched on do not interlock any other
commands, even if they have the 1-out-of-n check switched on.
For this, when receiving a spontaneous information object "Command", the command output
becomes busy and stays busy until the command output is terminated.
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
143
Automation
The receipt of a spontaneous information object "Command" with activated 1-out-of-n check
during a busy command output has the effect, that:
•
the command will be rejected
•
the activation will be negatively confirmed
•
the system information "Sum command interlocked" is set for one cycle of the
corresponding task
•
a spontaneous information object "Sum command interlocked" (positive transient) will be
transmitted with the originator address of the command.
If a 1-out-of-n check is required over several system elements (e.g. all commands of an
automation unit), the "system-element overlapping 1-out-of-n check" is necessary.
5.3.4.1.8 System-Element Overlapping 1-out-of-n Check
The system-element-overlapping 1-out-of-n check is to be resolved with the help of a logic in
the open-/closed-loop control function and can be activated with the parameter 1_of_n_t > 0.
The parameter 1_of_n_t > 0 is only effective, if the 1-out-of-n check described before is
switched on.
Sequence:
The system information "Command output busy" is set and the higher-level open-/closed-loop
control function is made available.
The logic in the open-/closed-loop control function checks, amongst other things, the
information "Command output busy" of all other system elements which are to be taken into
account for the 1-out-of-n check.
The result of this check must be made available to the command output with a positive edge
of the system data point "1-out-of-n enable" within the settable monitoring time (Parameter
1_of_n_t ).
If the "enable" is given, the further checks are carried out.
Note
With the function "Select- and Execute command" the system data point "1-out-of-n enable" must be
present, until the execute command has also been completed.
If "1-out-of-n enable" does not arrive within the variable monitoring time (direct command,
selection command), or "1-out-of-n enable" is not present (execute command),
144
•
the command is rejected
•
the activation is negatively confirmed
•
the system information "Sum command interlocked" is set for one cycle of the
corresponding task
•
a spontaneous information object "Sum command interlocked" (positive transient) is
transmitted with the originator address of the command..
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02
Automation
5.3.4.2
Initiate Command Output Procedure
If the command message is an execute command (S/E = execute) and all relevant checks
have been passed, the command is signaled to the application program.
Thereby, the assigned elements of the spontaneous information object are entered in the
input process image of the corresponding task and set for one cycle.
Attention
With pulse commands, a possibly parameterized storage method with "chronological global and message"
is ignored. I.e. pulse commands that have a treatment according to IEC 60870-5-101/104, are
automatically "state stored" !
5.3.4.3
Monitor Pulse Duration
The monitoring of the pulse duration is used for terminating the command output procedure
and for generating the spontaneous information object "Command" with the cause of
transmission "Termination of activation".
This function is only effective for pulse commands and is split into two types:
•
Termination after the command output time (without return information monitoring)
•
Termination by the application program (with return information monitoring)
5.3.4.3.1 BefehlsCommand Output Time (without Return Information
Monitoring)
The end of the command output procedure is determined by the command output time in the
code of qualifier of command of the spontaneous information object.
Thereby, only the code of qualifier of command of short or long command output time is
allowed. The values for the short or long command output time can be set for each automation
unit with the parameter AU common settings | Short pulse duration and AU common
settings | Long pulse duration.
The termination of the command output procedure through the command output time is set by
means of the parameter RS_Mon_t with the value 0.
The following checks are performed.
If the parameterized value for the corresponding (short or long) pulse duration is 0 or the code
of qualifier of command is "not determined":
•
the command is rejected
•
the activation is negatively confirmed
Note
If the code of qualifier of command is "not determined", the termination of the command output procedure
must take place by mean of the application program (with return information monitoring).
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
145
Automation
5.3.4.3.2 Application program (with Return Information Monitoring)
The end of the command output procedure is determined by a return information from the
application program.
The termination of the command output procedure by the application program is set by means
of the parameter RS_Mon_t with the value > 0. This parameter determines, after which time
the return information by the application program must occur at the latest.
For the following spontaneous information objects, a return information monitoring is possible
•
single command (TI = 45, 58)
•
double command (TI = 46, 59)
•
regulating step command (TI = 47, 60)
The return information is to be generated by the application program and signaled to the
treatment for commands with a spontaneous information object "return information x".
The corresponding return information must be assigned to a command with the parameter
RS_Image of the category "Process-technical message" of the product family CAEx plus.
The following table shows the assignment of the information in the spontaneous information
object "Return Information x" to the command.
Command
Return Information
Information Object
TI
Element
Information Object
TI
Element
Single command
45
SCS
Single-point information
30
SPI
Double command
46
DCS / OFF
Double-point information
31
DPI / OFF
DCS / ON
Regulating step
command
47
RCS LOWER
RCS
HIGHER
DPI / ON
Double-point information
31
DPI / OFF
DPI / ON
For a proper functioning of the return information monitoring a positive edge of the return
information is necessary.
Note
In order to avoid errors in the signaling of an unsuccessful command initiation, the return information
monitoring time (Parameter RS_Mon_t) should be longer than the command output time.
146
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02
Automation
Spontaneous information object „Command“
Spontaneous information object „Command“
(ACT)
(ACTCON)
positive
Command to application program
Application program
Return information from application program
Return information monitoring time
Spontaneous information object „Command“
(ACTTERM)
positive
Special cases
Actuator does not reach the desired end position
If the actuator does not reach the end position or only reaches it after expiry of the return
information monitoring time,
•
a negative confirmation of the activation is transmitted
Spontaneous information object „Command“
Spontaneous information object „Command“
(ACT)
(ACTCON)
positive
Command to application program
Application program
Return information from application program
Return information monitoring time
Spontaneous information object „Command“
(ACTTERM)
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
negative
147
Automation
Actuator already in the desired end position
If the actuator is already in the desired end position, the behavior can be set with the
parameter RS_outp_same_state for all commands of a system element:
Behavior
Action
2
3
4
5
Confirmation of the command
(ACTCON)
positive
positive
positive
negative
Command to application program
Yes
Yes
No
No
Delay until transmission of
termination of the command
(ACTTERM)
√
√
-
-
Termination of the command
(ACTCON)
negative
positive
negative
-
Behavior
Parameter RS_outp_same_state
2
CON+/output/TERM-
3
CON+/output/TERM+
4
CON+/do not output/TERM-
5
CON-/do not output
Delay until transmission of termination of the command (ACTTERM)
5.3.4.4
•
If the qualifier of command is "short or long pulse duration", the termination of the
command (ACTTERM) is transmitted after the parameterized short or long command
output time.
•
If the qualifier of command is "not determined" the termination of the command
(ACTTERM) is transmitted after the parameterized return information monitoring time.
Error Handling
The error handling of the command output distinguishes between:
Meaning
Cancel
Parameter setting errors
Cancel with diagnostic
Operating errors
For each negative confirmation (ACTCON, DEACTCON and ACTTERM) the origin of the
cancellation is also displayed with a warning class diagnostic information and an originator
description.
148
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02
Automation
5.3.4.4.1 Cancel
The command output procedure is canceled.
•
System data point and internal state "Command output busy" is reset, if the parameter
1_of_n is set for this command
•
A spontaneous information object with negative "Confirmation of the activation" or negative
"Termination of the activation" is transmitted.
Following this the system element is again ready for a command.
5.3.4.4.2 Cancel with Diagnostic
The command output procedure is canceled.
•
A diagnostic information is set according to the origin
•
System data point and the internal information "Command output busy" is reset, if the
parameter 1_of_n for this command is set
•
A spontaneous information object with negative "Confirmation of the activation" or negative
"Termination of the activation" is transmitted
Additionally:
•
the system information "Sum command interlocked" is set for one cycle of the
corresponding task
•
a spontaneous information object ("Sum command interlocked") is transmitted.
Following this the system element is again ready for a command.
5.3.5
Data Interface
5.3.5.1
Spontaneous Information Objects to the Treatment for
Commands
5.3.5.1.1 Pulse Commands
Elements of the Message
TI
..
identification
type
TI 45
TI 46
TI 47
single command
double command
regulating step command
CASDU, IOA .. message address
Can be set by parameter
SCS
..
command state
0
..
not permitted
1
..
ON
single
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
149
Automation
DCS
..
command state
double
RCS
..
Regulating
step command state
QOC
..
command
0
..
not permitted
1
2
3
..
..
..
OFF
ON
not permitted
0
..
not permitted
1
2
3
..
..
..
LOWER
HIGHER
not permitted
Qualifier of
QU
..
code of
qualifier of command
0
…
command output time corresponding to the
parameter of each command
1
…
Command output time corresponding to the
parameter AU common settings | Short pulse duration
2
…
Command output time corresponding to the
parameter AU common settings | Long pulse duration
>2
S/E
..
select/execute
...
not supported
See cause of transmission "Activation"
Cause of transmission
06
..
activation
Command with "select" leads to a preparation of the command
initiation
Command with "execute" leads to an execution of the command
08
..
deactivation
A prepared command (select) is removed
..
positive/negative
confirmation
Not evaluated
T
Not evaluated
P/N
..
test
Originator address
Must correspond with the set control location(s) if the control
location detection is activated
5.3.5.1.2 Setpoint Value
Elements of the Message
TI
..
identification
type
TI 48
TI 49
TI 50
setpoint Command, normalized value
setpoint Command, scaled
setpoint Command, short floating point
CASDU, IOA .. message address
Can be set by parameter
Value
Setpoint value
QOS
..
qualifier of
setpoint command
QL
..
code of
qualifier of setpoint command
Not evaluated
S/E
See transmission cause "Activation"
..
select/execute
Cause of transmission
150
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02
Automation
06
..
activation
Setpoint command with "Select" leads to preparation of the
command initiation
Setpoint command with "Execute" leads to an execution of the
command
08
..
Deactivation
A prepared command (select) is removed
..
positive/negative
confirmation
Not evaluated
T
Not evaluated
P/N
..
Test
Originator address
Must correspond with the set control location(s) if the control
location detection is activated
5.3.5.1.3 Bitstring
Elements of the Message
TI
..
identification
type
TI 51
Bitstring of 32 bit
CASDU, IOA .. Message address
Can be set by parameter
Value
Bitstring
Cause of transmission
06
..
activation
Leads to an execution of the command
08
..
deactivation
Not supported
..
positive/negative
confirmation
Not evaluated
T
Not evaluated
P/N
..
test
Originator address
Must correspond with the set control location(s) if the control
location detection is activated
5.3.5.1.4 Command x Interlocked
Elements of the Message
TI
..
identification
type
TI 30
TI 31
single-point information with timetag CP56Time2a
double-point information with time tag CP56Time2a
CASDU, IOA .. Message address
Can be set with parameter, source must be the particular open/closed-loop control function
SPI
..
information
0
..
command not interlocked
1
..
command interlocked
single point
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
151
Automation
DPI
..
information
double point
Bit 0:
command OFF or LOWER
0
..
not interlocked
1
..
interlocked
Bit 1:
command ON or HIGHER
0
..
not interlocked
1
..
interlocked
QDS
..
descriptor
quality
BL
..
blocked
Not evaluated
SB
..
substituted
Not evaluated
NT
..
not topical
Not evaluated
IV
..
invalid
Not evaluated
Cause of transmission
02
scan
..
background
SPI or DPI is evaluated depending on quality descriptor
03
..
spontaneous
SPI or DPI is evaluated depending on quality descriptor
05
..
requested
SPI or DPI is evaluated depending on quality descriptor
11
..
return
information, caused by a remote
command
SPI or DPI is evaluated depending on quality descriptor
12
..
return
information, caused by a local
command
SPI or DPI is evaluated depending on quality descriptor
20
..
interrogated
by general interrogation
SPI or DPI is evaluated depending on quality descriptor
21-36
interrogated by group
1-16 interrogation
SPI or DPI is evaluated depending on quality descriptor
P/N
..
positive/negative
confirmation
Not evaluated
T
Not evaluated
..
Originator address
152
test
Not evaluated
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02
Automation
5.3.5.1.5 Return Information x
Elements of the Message
TI
..
identification
type
TI 30
TI 31
single-point information with timetag CP56Time2a
double-point information with time tag CP56Time2a
CASDU, IOA .. Message address
Can be set with parameter, source must be the particular open/closed-loop control function
SPI
..
information
single point
0
..
return information not available
1
..
return information available
DPI
..
information
double point
Bit 0:
LOWER
return information for command OFF or
0
..
not available
1
..
available
Bit 1:
HIGHER
return information for command ON or
0
..
not available
1
..
available
QDS
..
descriptor
quality
BL
..
blocked
Not evaluated
SB
..
substituted
Not evaluated
NT
..
not topical
Not evaluated
IV
..
invalid
Not evaluated
Cause of transmission
02
scan
..
background
SPI or DPI is evaluated depending on quality descriptor
03
..
spontaneous
SPI or DPI is evaluated depending on quality descriptor
05
..
requested
SPI or DPI is evaluated depending on quality descriptor
11
..
return
information, caused by a remote
command
SPI or DPI is evaluated depending on quality descriptor
12
..
return
information, caused by a local
command
SPI or DPI is evaluated depending on quality descriptor
20
..
interrogated
by general interrogation
SPI or DPI is evaluated depending on quality descriptor
21-36
interrogated by group
1-16 interrogation
SPI or DPI is evaluated depending on quality descriptor
P/N
..
positive/negative
confirmation
Not evaluated
T
not evaluated
..
Originator address
test
Not evaluated
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
153
Automation
5.3.5.2
Spontaneous Information Objects from the Treatment for
Commands
5.3.5.2.1 Confirmation of the Pulse Command
Elements of the Message
TI
..
identification
type
TI 45
TI 46
TI 47
single command
double command
regulating step command
Same as in the received command message
CASDU, IOA .. Message address
Same as in the received command message
SCS
..
command state
single
Same as in the received command message
DCS
..
command state
double
RCS
..
Regulating
step command state
QOC
..
command
qualifier of
QU
..
code of
qualifier of command
0
…
command output time corresponding to the
parameter of each command
1
…
Command output time corresponding to the
parameter AU common settings | Short pulse duration
2
…
Command output time corresponding to the
parameter AU common settings | Long pulse duration
>2
S/E
..
select/execute
...
not supported
Same as in the received command message
Cause of transmission
07
..
of the activation
confirmation
Positive confirmation with "select", if all conditions are fulfilled for
the select command.
Positive confirmation with "execute", if all conditions are fulfilled
for the execute or direct command.
Otherwise there is a negative confirmation
09
..
confirmation
deactivation
Positive confirmation:
- command output is prepared ("select")
Otherwise there is a negative confirmation
10
..
the activation
termination of
Only if the command initiation has been answered by a positive
"confirmation of the activation".
Positive confirmation:
- command output ended properly and
- status information in the correct state
Otherwise there is a negative confirmation
154
44
..
identification
unknown type
Not supported
45
COT
..
unknown
Not supported
46
..
CASDU
unknown
Not supported
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02
Automation
47
..
unknown IOA
Not supported
..
positive/negative
confirmation
See cause of transmission 07, 09 and 10
T
Same as in the received command message
P/N
..
test
Originator address
Same as in the received command message
5.3.5.2.2 Confirmation of the Setpoint Value
Elements of the Message
TI
..
identification
type
TI 48
TI 49
TI 50
Setpoint Command, normalized value
Setpoint Command, scaled
Setpoint command, short floating point
Same as in the received setpoint command
CASDU, IOA .. Message address
Same as in the received setpoint command
Value
Same as in the received setpoint command
QOS
..
qualifier of
setpoint command
QL
..
code of
qualifier of setpoint command
Same as in the received setpoint command
S/E
Same as in the received setpoint command
..
select/execute
Cause of transmission
07
..
of the activation
confirmation
Positive confirmation with "select", if all conditions are fulfilled for
the select command.
Positive confirmation with "execute", if all conditions are fulfilled
for the execute or direct command.
Otherwise there is a negative confirmation
09
..
confirmation
deactivation
Positive confirmation:
- setpoint value is prepared ("select")
Otherwise there is a negative confirmation
10
..
the activation
termination of
Not supported
44
..
identification
unknown type
Not supported
45
COT
..
unknown
not supported
46
..
CASDU
unknown
not supported
47
unknown IOA
Not supported
..
..
positive/negative
confirmation
See cause of transmission 07 and 09
T
Same as in the received setpoint command
P/N
..
Originator address
test
Same as in the received setpoint command
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
155
Automation
5.3.5.2.3 Confirmation of the Bitstring
Elements of the Message
TI
..
identification
type
TI 51
Bitstring of 32 bit
Same as in the received command message
CASDU, IOA .. Message address
Same as in the received Bitstring of 32 bit
Value
Same as in the received Bitstring of 32 bit
Cause of transmission
Positive confirmation, if all conditions are fulfilled.
07
..
of the activation
confirmation
09
..
confirmation
deactivation
Not supported
10
..
the activation
termination of
Not supported
44
..
identification
unknown type
Not supported
45
COT
..
unknown
Not supported
46
..
CASDU
unknown
Not supported
47
unknown IOA
Not supported
..
Otherwise there is a negative confirmation
..
positive/negative
confirmation
See cause of transmission 0
T
Same as in the received Bitstring of 32 bit
P/N
..
test
Originator address
Same as in the received Bitstring of 32 bit
5.3.5.2.4 Sum Command Interlocked
Elements of the Message
TI
..
identification
type
TI 30
single-point information with time tag CP56Time2a
CASDU, IOA .. Message address
Can be set by parameter
SPI
..
information
single point
Positive transient
QDS
..
descriptor
quality
BL
..
blocked
Not blocked
SB
..
substituted
Not substituted
NT
..
not topical
Created by the basic system element due to peripheral element
failure
IV
..
invalid
Current
Cause of transmission
156
02
scan
..
background
Not supported
03
..
spontaneous
Upon change of information state or quality descriptor
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02
Automation
05
..
requested
11
..
return
information, caused by a remote
command
Not supported
12
..
return
information, caused by a local
command
Not supported
20
..
interrogated
by general interrogation
Upon receipt of a GI request or
automatically after startup, parameter change, etc.
21-36
interrogated by group
1-16 interrogation
Not supported
P/N
..
positive/negative
confirmation
Positive
T
No test
..
test
Originator address
5.3.5.3
Not supported
Not determined
System Information
5.3.5.3.1 To the Application Program
System Information
Value Range
Meaning
BOOL
Command output busy
BOOL
Sum command interlocked
5.3.5.3.2 From the Application Program
System Information
Value Range
Meaning
1-out-of-n enable
BOOL
Enabling information for system-elementoverlapping 1-out-of-n check
Positive edge:
enabled and must remain set
until initiation of the command output (command
x to application program)
Reset:
inhibited
control location
USINT
Permitted origin address
control location takeover
BOOL
Positive edge:
takeover of control location
and control location state
control location state
BOOL
ON:
defined control location is set or added
OFF:
all control locations are deleted
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
157
Automation
5.4
Restricted open/closed loop function
For the processing and forwarding of process data from and to TM modules as well as
communication (serial or LAN) serves a programmable logical controller (PLC).
The implementation of the control is performed by an application program (linking, open-loop
and closed-loop controlling). The application program can be edited either as Instruction List
(IL) or as Function Diagram (FUD).
The features of IL and FUD follow the standard IEC 61131-3 (Programmable Logic Controllers
Part 3: Programming Languages). The languages Structured Text (ST) and Sequential
Function Chart (SFC) as defined in the standard are not supported.
Technical data
Property
Value
Remarks
Nesting levels max.
20
Nesting results from jumping to jump marks
Number of tasks
1
The system provides a task, on the basis of which the
application program is executed
Number of type instances
1
Program scanning
cyclical
Cycle time adjustable in the IL (10…2000 ms, grid
10 ms)
spontaneous
For fast reaction times, the option "single-pass" can be
set in the IL; as a result, with each change of a signal
• from the periphery or
• from the communication
the controller passes the application program once
spontaneously (it does not wait until the next program
run is due based on the parameterized cycle time)
cyclical +
spontaneous
Combination is possible
Common Restrictions
•
The number of standard blocks is restricted.
•
The number of standard data types is restricted.
•
Not all the type identifications (TI) are supported.
•
Automatic data type conversions are performed.
•
A non-volatile storing is only possible for local variables, not for messages and block
inputs and outputs.
•
Only one task is utilizable.
•
Only one type instance is utilizable.
•
The redundancy bit (R bit) is not supported.
•
Additional attributes (as for instance "additive threshold", "command identification") are not
supported.
•
Bumpless reload of the application program is not supported.
Restrictions with Programming in IL
158
•
I/O variables and internal variables are pre-defined (no variable declaration possible).
•
No definitions for TASK, RESOURCE, PROGRAM, FUNCTION, FUNCTION_BLOCK.
•
The derivation of function blocks is produced automatically.
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02
Automation
•
Subroutines can be jumped to via the instruction CAL.
Restrictions with Programming in FUD
•
Only one own CASDU is utilizable.
•
The message "TI 101" (counter interrogation) is not supported.
5.4.1
Instruction List
5.4.1.1
Data Types
Following data types are supported :
Data type
Description
Bits
Range
Init.
BOOL
Binary value
1
0-1
0
DINT
Integer value
32
-2147483648…2147483647
0
REAL
Floating point value
32
±1.175494E–38…±3.402823E+38
0
Automatic Type Transformation
The data type is automatically transformed to the correct data type if necessary for a specific
calculation. Example: if a SINE is calculated from a BOOL variable, then the BOOL value is
automatically converted to a REAL value.
Rules for the type transformation
Direction
Rule
Example
BOOL → DINT
value is taken over
1→1
BOOL → REAL
value is taken over
1→1
DINT → BOOL
if <> 0, then 1
if = 0, then 0
- 123 → 1
0→0
DINT → REAL
format conversion
123 → 123
REAL → BOOL
if <> 0, then 1
if = 0, then 0
1.23 → 1
0→0
REAL → DINT
format conversion
(round off)
1.23 → 1
– 500.99 → - 500
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
159
Automation
5.4.1.2
Variables
5.4.1.2.1 I/O Variablen
I/O variables relate to the inputs/outputs of the hardware (periphery) of an automation unit or
messages with process information.
An I/O variable has a fixed defined addressing structure. There are two different types of
syntax defined:
Simple Syntax (I/O)
X_XXX_XXX_XXX_XXX_XXXX.XX
attribute
name (freely definable, optional)
IOA 3 (HIGH) (3 characters)
IOA 2 (MIDDLE) (3 characters)
IOA 1 (LOW) (3 characters)
type identification (3 characters)
I ... input
O ... output
Example:
I_030_001_000_000_TEST.VALUE
O_031_005_001_000.OFF
Expanded Syntax (I)
E_XXX_XXX_XXX_XXX_XXX_XXX_XXXX.XX
attribute
name (freely definable, optional)
IOA 3 (3 characters)
IOA 2 (3 characters)
IOA 1 (3 characters)
CASDU 2 (3 characters)
CASDU 1 (3 characters)
Type identification (3 characters)
The expanded syntax can only be used for controller input variables.
Using the same IOA, input- and output-side the "freely definable name" must be different.
160
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02
Automation
The Instruction List supports the following type identifications and attributes:
Type identification
Signal type
Attribute
Data type
Description
Initial
value
30
1 1)
2 1)
Single-point information
NT
IV
BL
SB
VALUE
GI
BOOL
BOOL
BOOL
BOOL
BOOL
BOOL
Not topical
Invalid
BL bit
SB bit
Value
General interrogation
0
0
0
0
0
0 2)
31
Double-point information
NT
IV
BL
SB
OFF
ON
GI
BOOL
BOOL
BOOL
BOOL
BOOL
BOOL
BOOL
NT bit
IV bit
BL bit
SB bit
OFF bit
ON bit
General interrogation bit
0
0
0
0
0
0
0 2)
34
36
Measured value,
normalized
Measured value, floating
point
NT
IV
BL
SB
OV
VALUE
GI
BOOL
BOOL
BOOL
BOOL
BOOL
REAL
BOOL
NT bit
IV bit
BL bit
SB bit
OV bit
Value
General interrogation bit
0
0
0
0
0
0
0 2)
35
Measured value, scaled
NT
IV
BL
SB
OV
VALUE
GI
BOOL
BOOL
BOOL
BOOL
BOOL
DINT
BOOL
NT bit
IV bit
BL bit
SB bit
OV bit
Value
General interrogation bit
0
0
0
0
0
0
0 2)
37
Integrated total
IV
VALUE
SQ
CY
CA
BOOL
DINT
DINT
BOOL
BOOL
IV bit
Value
Sequence number
Carry
Preset
0
0
0
0
0
45
58 1)
Single command
QU
S_E
VALUE
DINT
BOOL
BOOL
Output time
Select/execute
Value
0
0
0
46
59 1)
Double command
QU
S_E
OFF
ON
DINT
BOOL
BOOL
BOOL
Output time
Select/execute
OFF bit
ON bit
0
0
0
0
48
61 1)
Setpoint command,
normalized
VALUE
QL
S_E
REAL
DINT
BOOL
Value
Output identifier
Select/execute
0
0
0
50
63 1)
Setpoint command,
floating point
VALUE
QL
S_E
REAL
DINT
BOOL
Value
Output identifier
Select/execute
0
0
0
49
62 1)
Setpoint command,
scaled
VALUE
QL
S_E
DINT
DINT
BOOL
Value
Output identifier
Select/execute
0
0
0
101
Counter interrogation
command
RQT
FRZ
DINT
DINT
Request code
Freeze code
0
0
1)
optional
2)
serves only for compatibility, a writing or reading of this bit has no effect
The following attributes apply for all the type identifications:
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
161
Automation
Attribute
Data type
Description
Initial value
S
BOOL
Spontaneous bit
0
COT
DINT
Cause of transmission
3/6
PN
BOOL
P/N bit of cause of transmission
0
T
BOOL
T bit of cause of transmission (test)
0
ORIGINATOR
DINT
Originator address
0
MS
DINT
Milliseconds (0…999)
Current time
SEC
DINT
Seconds (0…59)
Current time
MIN
DINT
Minutes (0…59)
Current time
IVT
BOOL
IV bit of time (1 = invalid)
Current time
H
DINT
Hours (0…23)
Current time
DST
BOOL
Daylight-saving time bit (1 = daylight-saving)
Current time
DAY
DINT
Day (1…31)
Current time
WEEKDAY
DINT
Week day (1…6, 1 = Sunday)
Current time
MONTH
DINT
Month (1…12)
Current time
YEAR
DINT
Year (0…99)
Current time
TIME_DATE
7 Byte
Time + date
1) 2)
Current time
1)
type identifiers that have no time (e.g. single command TI 45) are time-tagged in the
process image
3)
serves only for passing the time tag, it can not be used for calculation
Note
The name of a variable must not exceed 39 characters.
Umlauts and special characters are not to be used, since these may possibly not be displayed correctly in
the webbrowser.
Input variables cannot be written and output variables cannot be read.
For output variables not all attributes need to be used. In the presets the attributes at the
output side are set to the values defined in the table. One exception is the cause of
transmission COT, this is set to SPONTANEOUS (3), apart from commands, setpoint values and
counter interrogation, for which this is set to ACTIVATION (6).
5.4.1.2.2 Internal variables
Internal variables are flags that serve for the temporary storage of states or results.
A flag has a fixed defined addressing structure:
162
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02
Automation
X_XXX_XXXX
name (freely definable)
format
BOOL
DINT
REAL
flag type
M ... flag
MR ... non-volatile flag (retain)
Note
The name of a flag may not exceed 39 characters.
All the flags are initialized with the value 0.
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
163
Automation
5.4.1.2.3 System Variables
The following system variables are defined:
Key word
Attribute
Data type
Description
PLC_CYCLETIME
DINT
Scanning rate for cyclic program
execution in ms 1)
PLC_SINGLE
BOOL
Spontaneous program execution
PLC_SYSTIME
Access
Write
2)
System time
MS
S
MIN
IVT
H
DST
DAY
WEEKDAY
MONTH
YEAR
TIME_DATE
Write
Read
DINT
DINT
DINT
BOOL
DINT
BOOL
DINT
DINT
DINT
DINT
7 Byte
Milliseconds (0…999)
Seconds (0…59)
Minutes (0…59)
IV bit of time (1 = invalid)
Hours (0…23)
Daylight-saving time (0 = none)
Day (1…31)
Week day (1…7, 1 = Sunday)
Month (1…12)
Year (0…99)
Time + date 3)
PLC_PROCESSINGTIME
DINT
Current PLC processing time in ms
Read
PLC_CYCLETIME_OVERFLOW
BOOL
Processing time exceeded
Read
PLC_PROCESSINGCOUNTER
DINT
Program cycle counter
Read
PLC_SYSERROR_000
:
PLC_SYSERROR_255
BOOL
System error
Read
PLC_ENO
BOOL
Global flag "function block processed
faulty" 5)
Read
1)
range 10 ms…2000 ms, grid 10 ms (default 100 ms), 0=no cyclic program execution
2)
"1" = application program runs through once with each change (input signal from I/O module or from
communication), "0" = no spontaneous run of the application program (default)
5)
"1" = parameter change online, "0" = parameter change offline (WEBmic)
5)
"1" = no error, "0" = error
The following functions and function blocks can set the variable PLC_ENO to "0" (recognize
error), the other functions and function blocks set the variable always to "1".
Function/Function block
164
Error
DIV, DIV (key word)
IN1 = 0
MOD
IN1 = 0
TP
PT > 29826161 ms
TON
PT > 29826161 ms
TOFF
PT > 29826161 ms
TCLK
T1 > 29826161 ms
T2 > 29826161 ms
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02
Automation
5.4.1.3
Constants
Constants are fixed numerical values. Examples:
Data type
Value
BOOL
0
BOOL
1
DINT
-1234
DINT
532
DINT
+3
REAL
1.23E-03
REAL
-1.25E05
An automatic detection of the data type is performed. The order of priority for the detection is
BOOL before DINT before REAL.
Note
With inverted loading (LDN) of a DINT constant ("0", "1") a polarity sign must be used ("+0", "+1"),
otherwise the constant is detected as BOOL.
5.4.1.4
Jump Marks
Jump marks serve for the absolute or for the conditional
•
jump to program parts (branch)
•
call of subroutines (back with RET)
The name of a jump mark can be freely assigned, it must not exceed 39 characters and is
concluded with a ":".
Example: TEST:
Predefined jump marks exist for structuring the application program:
Key word
Execution
PLC_RESET
Before current process image
PLC_INIT
After current process image 1)
PLC_START
Cyclical after READY
from … to
1)
2)
PLC_RESET…PLC_INIT or
PLC_START
PLC_ INIT…PLC_START
PLC_START…end AWL
1)
optional
2)
since the execution continues to the end of the IL, jump marks that are jumped to with CAL
(subroutines) must be at the beginning of the IL (before PLC_RESET, PLC_INIT)
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
165
Automation
5.4.1.5
Command Record
Operators of the Instruction List
Key word
166
Operand Type
Description
LD
LDN
Constant, variable, flag
Load result
Load result negated
ST
STN
Variable, flag
Store result
Store result negated
S
R
Variable, flag
If result <> 0, then set
If result = 0, then reset
AND
ANDN
OR
ORN
XOR
XORN
Constant, variable, flag
Result = result AND …
Result = result AND NOT …
Result = result OR …
Result = result OR NOT …
Result = result XOR …
Result = result XOR NOT …
ADD
SUB
MUL
DIV
Constant, variable, flag
Result = result + …
Result = result - …
Result = result * …
Result = result/…
GT
GE
EQ
NE
LE
LT
Constant, variable, flag 1)
Result = result > …
Result = result >= …
Result = result = …
Result = result <> …
Result = result <= …
Result = result < …
JMP
JMPC
JMPN
Jump mark
Jump
If result <> 0, then jump
If result = 0, then jump
CAL
CALC
CALN
RET
Jump mark, function, function block 2)
Call
If result <> 0, then call
Iif result = 0, then call
Return from call
1)
the result in this case is of type BOOL (0 or 1)
2)
if a jump mark has been called by a CAL, CALC, CALN, then there is a return to the next command
after the call, if a RET command takes place. A jump mark that is called with CAL must have a
RET-instruction at the end
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02
Automation
5.4.1.6
Functions
A function provides upon execution exactly one data element. The call can be used as an
operand in an expression. A function does not contain any internal state informations, this
means, the call of a function with the same input parameters provides the same value at the
output.
5.4.1.6.1 Numerical Functions
Function
Input
operator
Input type
Description
Result
name
Result type
ABS
IN0
BOOL, DINT,
REAL
Absolute value
Q
BOOL
DINT
REAL
SQRT
IN0
REAL
Square root
Q
REAL
LN
IN0
REAL
Natural logarithm
Q
REAL
LOG
IN0
REAL
Logarithm base 10
Q
REAL
EXP
IN0
REAL
Exponential function
Q
REAL
Q
DINT
REAL
Q
REAL
Q
REAL
Q
REAL
Q
REAL
Q
REAL
Q
REAL
EXPT
IN0, IN1
BOOL, DINT,
REAL
Result =
SIN
IN0
REAL
Sine *)
COS
IN0
TAN
IN0
ASIN
ACOS
ATAN
*)
IN0
IN0
IN0
REAL
Cosine
*)
REAL
Tangent
REAL
*)
REAL
REAL
Arc sin
Arc cos
IN0IN1
*)
*)
Arc tangent
*)
the unit is radian
5.4.1.6.2 Arithmetical Functions
Function
Input
operator
Input type
Description
Result
name
Result type
ADD
IN0…IN9
BOOL, DINT,
REAL
Result = IN0 + IN1
+ … IN9
Q
DINT
REAL
SUB
IN0, IN1
BOOL, DINT,
REAL
Result = IN0 - IN1
Q
DINT
REAL
MUL
IN0…IN9
BOOL, DINT,
REAL
Result = IN0 + IN1
+ … IN9
Q
DINT
REAL
DIV
IN0, IN1
BOOL, DINT,
REAL
Result = IN0/IN1
Q
DINT
REAL
MOD
IN0, IN1
BOOL, DINT,
REAL
Result = IN0 modulus
IN1
Q
DINT
REAL
*)
*)
the result type is automatically determined based on the input parameter types; it is converted to
the largest input parameter type
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
167
Automation
5.4.1.6.3 Binary Logic Operation
Function
Input
operator
Input type
Description
Result
name
Result type
AND
IN0…IN9
BOOL
Result = IN0 and IN1
and … IN9
Q
BOOL
OR
IN0…IN9
BOOL
Result = IN0 or IN1
or … IN9
Q
BOOL
XOR
IN0…IN9
BOOL
Result = not IN0 and
not IN1 and … not
IN9
Q
BOOL
NOT
IN0
BOOL
Result = not IN0
Q
BOOL
5.4.1.6.4 Selection Functions
168
Function
Input
operator
Input type
Description
Result
name
Result type
SEL
G
IN0
IN1
BOOL
BOOL, DINT,
REAL
BOOL, DINT,
REAL
Result = IN0 if G = 0
Result = IN1 if G = 1
Q
BOOL
DINT
REAL
MAX
IN0…IN9
BOOL, DINT,
REAL
Result = MAX (IN0,
IN1, … IN9)
Q
BOOL
DINT
REAL
MIN
IN0…IN9
BOOL, DINT,
REAL
Result = MIN (IN0,
IN1, … IN9)
Q
BOOL
DINT
REAL
LIMIT
MN
IN
MX
BOOL, DINT,
REAL
BOOL, DINT,
REAL
BOOL, DINT,
REAL
Result = limited value
or IN
Q
BOOL
DINT
REAL
MUX
K
IN0…IN9
DINT
BOOL, DINT,
REAL
Result = multiplexed
value 2)
Q
BOOL
DINT
REAL
1)
the result type is automatically determined based on the input parameter types; it is
converted to the largest input parameter type
2)
the value K (0…9) determines the input that shall be interconnected
1)
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02
Automation
5.4.1.6.5 Comparison Functions
5.4.1.7
Function
Input
operator
Input type
Description
Result
name
Result type
EQ
IN0…IN9
BOOL, DINT,
REAL
Result = (IN0 = IN1)
& (IN1 = IN2)…
Q
BOOL
GE
IN0…IN9
BOOL, DINT,
REAL
Result = (IN0 >= IN1)
& (IN1 >= IN2)…
Q
BOOL
GT
IN0…IN9
BOOL, DINT,
REAL
Result = (IN0 > IN1)
& (IN1 > IN2)…
Q
BOOL
LE
IN0…IN9
BOOL, DINT,
REAL
Result = (IN0 <= IN1)
& (IN1 <= IN2)…
Q
BOOL
LT
IN0…IN9
BOOL, DINT,
REAL
Result = (IN0 < IN1)
& (IN1 < IN2)…
Q
BOOL
NE
IN0, IN1
BOOL, DINT,
REAL
Result = (IN0 <>IN1)
Q
BOOL
Function Blocks
A function block (FB) provides upon execution one or several values. Several designated
instances of a function block can be generated. Each instance has a corresponding name and
a data structure, which contain its internal and external output variables. All the values of the
output variables and the required internal variables of this data structure are kept safe from
one processing to the next, therefore the call of the same function block may not always
provide the same output values.
The derivation of the function block is produced automatically by the name. The name of the
function block must be unambiguous. It also must not be used for flags.
The call parameters must be interchanged per LD/ST combinations.
The name of the call parameter is produced from the name of the function and the name of
the parameter separated by a ".".
A function block has a fixed defined addressing structure:
X XXX_XXX X
name (freely definable)
(thereby results the derivation)
function block
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
169
Automation
5.4.1.7.1 Bistable Elements
Function
block
Input
operator
Input type
Description
Result
name
Result type
SR 1)
S1
R
BOOL
BOOL
Priority set
Q 1)
BOOL
RS 2)
S
R1
BOOL
BOOL
Priority reset
Q 2)
BOOL
1)
if S1 = 0 and R = 0, then Q1 = Q1; if S1 = 0 and R = 1, then Q1 = 0
if S1 = 1 and R = 0, then Q1 = 1; if S1 = 1 and R = 1, then Q1 = 1
2)
if S = 0 and R1 = 0, then Q1 = Q1; if S = 0 and R1 = 1, then Q1 = 0
if S = 1 and R1 = 0, then Q1 = 1; if S1 = 1 and R = 1, then Q1 = 0
5.4.1.7.2 Edge Detection
Function
block
Input
operator
Input type
Description
Result
name
Result type
R_TRIG1)
CLK
BOOL
Rising edge
Q 1)
BOOL
F_TRIG 2)
CLK
BOOL
Falling edge
Q 2)
BOOL
1)
if CLK 0 → 1, then Q = 1; if CLK = 1 → 0, then Q = 0
2)
if CLK 0 → 1, then Q = 0; if CLK = 1 → 0, then Q = 1
5.4.1.7.3 Counters
Function
block
Input
operator
Input type
Description
Result
name
Result type
CTD
CD
LD
PV
BOOL
BOOL
DINT
Counter downward
Q
CV 1)
BOOL
DINT
CTU
CU
R
PV
BOOL
BOOL
DINT
Counter upward
Q
CV *) 2)
BOOL
DINT
CTUD
CD
CU
R
LD
PV
BOOL
BOOL
BOOL
BOOL
DINT
Counter downward
Counter upward
QD 4)
QU 4)
CV 3)
BOOL
BOOL
DINT
CV = count value
170
1)
if R = 1, then CV = 0
if CU = 1 and CV < PVmax, then CV = CV + 1, Q = (CV >= PV)
2)
if R = 1, then CV = 0
if CU = 1 and CV < PVmax, then CV = CV + 1, Q = (CV >= PV)
3)
if R = 1, then CV = 0
if LD = 1, then CV = PV
if CU = 1 and CV < PVmax, then CV = CV + 1
if CD = 1 and CV > PVmin, then CV = CV - 1
4)
QU = (CV > = PV); QD = (CV < = 0)
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02
Automation
If the input CU or CD is at "1" for more than one cycle, the counter counts only the rising edge
(in the first detected cycle) by 1 upward/downward. The rest of the cycles at which the input is
at "1" are no longer counted by the counter.
5.4.1.7.4 Timers
Function
block
Input
operator
Input type
Description
Result
name
Result type
TP
IN
PT
BOOL
DINT
Pulse
Q 1)
ET
BOOL
DINT
TON
IN
PT
BOOL
DINT
ON delay
Q 2)
ET
BOOL
DINT
TOFF
IN
PT
BOOL
DINT
OFF delay
Q 3)
ET
BOOL
DINT
TCLK
T1
T2
DINT
DINT
Clock pulse
Q 4)
BOOL
ET = time value [ms]
1)
IN
Q
PT
PT
PT
ET
2)
IN
Q
PT
PT
PT
ET
3)
IN
Q
PT
PT
PT
ET
4)
T1
T2
T1
T2
The unit of PT, ET and T1, T2 is ms (range: 0 ms … 29826161 ms corresponds with 8.3 h).
If during a running time PT <> ET the parameter PT is changed, then this parameter is applied
immediately.
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
171
Automation
5.4.2
Function Diagram
Note
This section shows the scope for the programming with the Function Diagram editor of the TOOLBOX II
(CAEx plus). You will find the detailed description in the CAEx plus User Manual or in the Online Help of
the tool CAEx plus.
5.4.2.1
Data Types
TM 1703 mic supports the following data types:
Data type
Description
Bits
Range
Init.
BOOL
Binary value
1
0-1
0
DINT
Integer value
32
-2147483648…2147483647
0
REAL
Floating point value
32
±1.175494E–38…±3.402823E+38
0
5.4.2.1.1 Automatic Type Transformation
With CAEx plus all the IEC 61131-3 standard data types can be used which can be converted
to the supported data types. The data type conversion is performed automatically during the
code generation:
IEC 61131-3
172
TM 1703 mic
BOOL
BOOL
BYTE
DINT
WORD
DINT
DWORD
DINT
SINT
DINT
INT
DINT
DINT
DINT
USINT
DINT
UINT
DINT
UDINT
DINT
REAL
REAL
LREAL
REAL
TIME
DINT
Remark
Time value [milliseconds]
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02
Automation
5.4.2.1.2 Structure data types
From the supported data types own structure data types can be defined and used.
Note
Only scalar data types does supported . The structure variables are expanded automatically to single
variables during the code generation.
5.4.2.1.3 Proprietary data types
Message data
Signal type
Attribute
TB_SD_SPO_TI31_DPI
Double-point information
Off
On
TB_SD_SPO_TI37_BCR
Count value
CR
SQ
CY
CA
TB_SD_SPO_TI45_SCO
Single-point information
STATE
QOC
S_E
TB_SD_SPO_TI46_DCO
Double command
Off
On
QOC
S_E
TB_SD_SPO_TI48_SP_NVA
Setpoint command, normalized
VALUE
QL
S_E
TB_SD_SPO_TI49_SP_SVA
Setpoint command, scaled
VALUE
QL
S_E
TB_SD_SPO_STATE_BIN_INF
General state binary information
S
GI
NT
IV
TB_SD_SPO_STATE_COMMAND
General state command
S
TB_SD_SPO_STATE_COUNT
General state count value
S
IV
TB_SD_SPO_STATE_VALUE
General state measured value
S
GI
NT
IV
OV
TB_SD_SYSTEM_TIME *)
System time and message time
*)
serves only for passing the time tag from the input to the output, it can not be used for calculation
(only for the IL operations LD and ST utilizable);
this data type is used as block input or block output by the system time functions; corresponding
checks are performed during the code generation
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
173
Automation
5.4.2.2
Variables
5.4.2.2.1 I/O Variables
Only the type identifications mentioned in section Error! Reference source not found.,
Error! Reference source not found. are supported.
From the parameterization in the OPM II (list of the used input/output signals) upon code
generation for each signal the message address is coded in the variable name.
Syntax (I/O)
X_XXX_XXX_XXX_XXX_XXXX.XX
attribute
name (freely definable, optional)
IOA 3 (HIGH) (3 characters)
IOA 2 (MIDDLE) (3 characters)
IOA 1 (LOW) (3 characters)
type identification (3 characters)
I ... input
O ... output
Example:
O_031_000_001_002_CaexTel0000.OFF
O_031_000_001_002_CaexTel0000.ON
This example describes an output signal with the process-technical address "CAEx Tel0000"
and the message address
CASDU 1,1
IOA
0,1,2
TI
31
Note
If the CASDU in the message concurs with the projected CASDU of the automation unit, the CASDU is not
entered into the name of the variable.
For input messages with different CASDU, the CASDU is put into the variable name before the IOA.
5.4.2.2.2 System Variables
The system data points are available as global variables in the global variable object "System
info" in the resource.
The system data points are marked by the prefix "PLC_" ( see "system variables" chapter
"instruction list").
174
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02
Automation
5.4.2.3
Functions
5.4.2.3.1 Numerical Functions
Function
Input
operator
Input type
Description
Result
name
Result type
ABS
IN1
ANY_NUM
Absolute value
OUT1
ANY_NUM
SQRT
IN1
ANY_REAL
Square root
OUT1
ANY_REAL
LN
IN1
ANY_REAL
Natural logarithm
OUT1
ANY_REAL
LOG
IN1
ANY_REAL
Logarithm base 10
OUT1
ANY_REAL
EXP
IN1
ANY_REAL
Exponential function
OUT1
ANY_REAL
OUT1
ANY_NUM
IN0IN1
EXPT
IN1
IN2
ANY_NUM
ANY_NUM
Ergebnis =
SIN
IN1
ANY_REAL
Sine
OUT1
ANY_REAL
COS
IN1
ANY_REAL
Cosine
OUT1
ANY_REAL
TAN
IN1
ANY_REAL
Tangent
OUT1
ANY_REAL
ASIN
IN1
ANY_REAL
Arc sin
OUT1
ANY_REAL
ACOS
IN1
ANY_REAL
Arc cos
OUT1
ANY_REAL
ATAN
IN1
ANY_REAL
Arc tangent
OUT1
ANY_REAL
MOVE
IN1
ANY_NUM
Interconnect value
OUT1
ANY_NUM
CHS
IN1
ANY_NUM
Sign changer
OUT1
ANY_NUM
5.4.2.3.2 Arithmetical Functions
Function
Input
operator
Input type
Description
Result
name
Result type
ADD
IN1
IN2…IN16
ANY_NUM
ANY_NUM
Result = IN0 + IN1
+ … IN16
OUT1
ANY_NUM
ADD_T_T
IN1
IN2
TIME
TIME
Result = IN0 + IN1
OUT1
TIME
SUB
IN1
IN2
ANY_NUM
ANY_NUM
Result = IN0 - IN1
OUT1
ANY_NUM
SUB_T_T
IN1
IN2
TIME
TIME
Result = IN0 - IN1
OUT1
TIME
MUL
IN1
IN2…IN16
ANY_NUM
ANY_NUM
Result = IN0 * IN1
* … IN16
OUT1
ANY_NUM
MUL_T
IN1
IN2
TIME
ANY_NUM
Result = IN0 * IN1
OUT1
TIME
DIV
IN1
IN2
ANY_NUM
ANY_NUM
Result = IN0/IN1
OUT1
ANY_NUM
DIV_T
IN1
IN2
TIME
ANY_NUM
Result = IN0/IN1
OUT1
TIME
MOD
IN1
IN2
ANY_INT
ANY_INT
Result = IN0 Modulo
IN1
OUT1
ANY_INT
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
175
Automation
5.4.2.3.3 Binary Logic Operation
Function
Input
operator
Input type
Description
Result
name
Result type
AND
IN1
IN2…IN16
ANY_BIT
ANY_BIT
Result = IN0 and IN1
and … IN16
OUT1
ANY_BIT
OR
IN1
IN2…IN16
ANY_BIT
ANY_BIT
Result = IN0 or IN1
or … IN16
OUT1
ANY_BIT
XOR
IN1
IN2…IN16
ANY_BIT
ANY_BIT
Result = not IN0 and
not IN1 and … not
IN16
OUT1
ANY_BIT
NOT
IN1
ANY_BIT
Result = not IN0
OUT1
ANY_BIT
5.4.2.3.4 Selection Functions
Function
Input
operator
Input type
Description
Result
name
Result type
SEL
G
IN0
IN1
BOOL
ANY_NUM
ANY_NUM
Result = IN0 if G = 0
Result = IN1 if G = 1
OUT1
ANY
MAX
IN1
IN2…IN16
ANY_NUM
ANY_NUM
Result = MAX (IN0,
IN1, … IN16)
OUT1
ANY
MIN
IN1
IN2…IN16
ANY_NUM
ANY_NUM
Result = MIN (IN0,
IN1, … IN16)
OUT1
ANY
LIMIT
MN
IN
MX
ANY_NUM
ANY_NUM
ANY_NUM
Result = limited value
or IN
OUT1
ANY
MUX_DI
K *)
IN1…IN16
DINT
ANY
Result = multiplexed
value
OUT1
ANY
MUX_I
K *)
IN1…IN16
INT
ANY
ANY
Result = multiplexed
value
OUT1
ANY
MUX_SI
K *)
IN1…IN16
SINT
ANY
ANY
Result = multiplexed
value
OUT1
ANY
MUX_UD
K *)
IN1…IN16
UDINT
ANY
ANY
Result = multiplexed
value
OUT1
ANY
MUX_UI
K *)
IN1…IN16
UINT
ANY
ANY
Result = multiplexed
value
OUT1
ANY
MUX_US
K *)
IN1…IN16
USINT
ANY
ANY
Result = multiplexed
value
OUT1
ANY
*)
176
the value (0…9) determines the input that shall be interconnected
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02
Automation
5.4.2.3.5 Comparison Functions
Function
Input
operator
Input type
Description
Result
name
Result type
EQ
IN1
IN2…IN16
ANY_BIT
ANY_NUM
TIME
Result = (IN0 = IN1)
& (IN1 = IN2)…
OUT1
BOOL
GE
IN1
IN2…IN16
ANY_BIT
ANY_NUM
TIME
Result = (IN0 >= IN1)
& (IN1 >= IN2)…
OUT1
BOOL
GT
IN1
IN2…IN16
ANY_BIT
ANY_NUM
TIME
Result = (IN0 > IN1)
& (IN1 > IN2)…
OUT1
BOOL
LE
IN1
IN2…IN16
ANY_BIT
ANY_NUM
TIME
Result = (IN0 <= IN1)
& (IN1 <= IN2)…
OUT1
BOOL
LT
IN1
IN2…IN16
ANY_BIT
ANY_NUM
TIME
Result = (IN0 < IN1)
& (IN1 < IN2)…
OUT1
BOOL
NE
IN1
IN2
ANY_BIT
ANY_NUM
TIME
Result = (IN0 <> IN1)
OUT1
BOOL
5.4.2.3.6 Transformation Functions
Function
Input
operator
Input type
Description
Result
name
Result type
AtoBOOL
IN1
ANY_BIT
ANY_NUM
TIME
Value conversion
OUT1
BOOL
AtoBYTE
IN1
ANY
Value conversion
OUT1
BYTE
AtoDINT
IN1
ANY_BIT
ANY_NUM
TIME
Value conversion
OUT1
DINT
AtoDWORD
IN1
ANY
Value conversion
OUT1
DWORD
AtoINT
IN1
ANY
Value conversion
OUT1
INT
AtoREAL
IN1
ANY_BIT
ANY_NUM
TIME
Value conversion
OUT1
REAL
AtoSINT
IN1
ANY
Value conversion
OUT1
SINT
AtoTIME
IN1
ANY_BIT
ANY_NUM
TIME
Value conversion
OUT1
TIME
AtoUDINT
IN1
ANY
Value conversion
OUT1
UDINT
AtoUINT
IN1
ANY
Value conversion
OUT1
UINT
AtoUSINT
IN1
ANY
Value conversion
OUT1
USINT
AtoWORD
IN1
ANY
Value conversion
OUT1
WORD
TRUNC_DI
IN1
ANY_REAL
Integer formation
OUT1
DINT
TRUNC_I
IN1
ANY_REAL
Integer formation
OUT1
INT
TRUNC_LI
IN1
ANY_REAL
Integer formation
OUT1
LINT
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
177
Automation
5.4.2.4
Function
Input
operator
Input type
Description
Result
name
Result type
TRUNC_SI
IN1
ANY_REAL
Integer formation
OUT1
SINT
TRUNC_UD
IN1
ANY_REAL
Integer formation
OUT1
UDINT
TRUNC_UI
IN1
ANY_REAL
Integer formation
OUT1
UINT
TRUNC_UL
IN1
ANY_REAL
Integer formation
OUT1
ULINT
TRUNC_US
IN1
ANY_REAL
Integer formation
OUT1
USINT
Function Blocks
Note
Curve modules, set of curve modules and hydro does not supported .
5.4.2.4.1 Bistable Elements
Function
block
Input
operator
Input type
Description
Result
name
Result type
SR
S1
R
BOOL
BOOL
Set priority
Q1 1)
BOOL
RS
S
R1
BOOL
BOOL
Reset priority
Q1 2)
BOOL
1)
if S1 = 0 and R = 0, then Q1 = Q1; if S1 = 0 and R = 1, then Q1 = 0
if S1 = 1 and R = 0, then Q1 = 1; if S1 = 1 and R = 1, then Q1 = 1
2)
if S = 0 and R1 = 0, then Q1 = Q1; if S = 0 and R1 = 1, then Q1 = 0
if S = 1 and R1 = 0, then Q1 = 1; if S1 = 1 and R = 1, then Q1 = 0
5.4.2.4.2 Edge Detection
Function
block
Input
operator
Input type
Description
Result
name
Result type
R_TRIG
CLK
BOOL
Rising edge
Q 1)
BOOL
Falling edge
2)
BOOL
F_TRIG
178
CLK
BOOL
1)
if CLK 0 → 1, then Q = 1; if CLK = 1 → 0, then Q = 0
2)
if CLK 0 → 1, then Q = 0; if CLK = 1 → 0, then Q = 1
Q
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02
Automation
5.4.2.4.3 Counters
Function
block
Input
operator
Input type
Description
Result
name
Result type
CTD_ANY_
NUM
>CD
LD
PV
BOOL
BOOL
ANY_NUM
Counter downward
Q
CV 1)
BOOL
ANY_NUM
CTU_ANY_
NUM
>CU
R
PV
BOOL
BOOL
ANY_NUM
Counter upward
Q
CV 2)
BOOL
ANY_NUM
CTUD_ANY
_NUM
>CD
>CU
R
LD
PV
BOOL
BOOL
BOOL
BOOL
ANY_NUM
Counter downward
Counter upward
QD 4)
QU 4)
CV 3)
BOOL
BOOL
ANY_NUM
CV = count value
1)
if R = 1, then CV = 0
if CU = 1 and CV < PVmax, then CV = CV + 1, Q = (CV >= PV)
2)
if R = 1, then CV = 0
if CU = 1 and CV < PVmax, then CV = CV + 1, Q = (CV >= PV)
3)
if R = 1, then CV = 0
if LD = 1, then CV = PV
if CU = 1 and CV < PVmax, then CV = CV + 1
if CD = 1 and CV > PVmin, then CV = CV - 1
4)
QU = (CV > = PV); QD = (CV < = 0)
5.4.2.4.4 Timers
Function
block
Input
operator
Input type
Description
Result
name
Result type
TP
IN
PT
BOOL
TIME
Pulse
Q 1)
ET
BOOL
TIME
TON
IN
PT
BOOL
TIME
ON delay
Q 2)
ET
BOOL
TIME
TOFF
IN
PT
BOOL
TIME
OFF delay
Q 3)
ET
BOOL
TIME
ET = time value [ms]
1)
IN
Q
PT
PT
PT
ET
2)
IN
Q
PT
PT
PT
ET
3)
IN
Q
PT
PT
PT
ET
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
179
Automation
5.4.2.4.5 Pulse Generator
Function
block
Input
operator
Input type
Description
Result
name
Result type
fCLOCK_PU
LSE_sec
T1
T2
REAL
REAL
Clock pulse
O
BOOL
Description
Result
name
Result type
5.4.2.4.6 System Time Functions
Function
block
Input
operator
Input type
TB_SYSTE
M_TIME
Reading of the
system time is
already converted to
the system variable
PLC_SYSTIME by
means of the CAEx
plus transformer
TB_CONV_
SYSTIME_T
O_VALUES
SysTime
TB_SD_SYSTEM 7 byte IEC time to
_TIME
single values (is
transformed to the
attributes for time in
the target system)
ms
s
min
h
day
month
year
weekday
IV
dst
UINT
USINT
USINT
USINT
USINT
USINT
UINT
USINT
BOOL
BOOL
TB_CONV_
VALUES_T
O_SYSTIME
ms
s
min
h
day
month
year
weekday
IV
dst
UINT
USINT
USINT
USINT
USINT
USINT
UINT
USINT
BOOL
BOOL
Single values to
7 byte IEC time (is
transformed to the
attributes for time in
the target system)
SysTime
TB_SD_SY
STEM_TIM
E
5.4.2.4.7 Force Variable
Function
block
Input
operator
Input type
Description
Result
name
Result type
ForceMrk *)
IN
ANY
Set variable value
OUT
ANY
*)
180
only for the Offline Simulation
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02
Automation
5.4.3
Internal Signal Processing
5.4.3.1
Input Signals
At the input side of the controller the following memory types are available:
•
Process image (state stored).
•
Ring chronological in message.
•
Ring chronological global.
Assignments:
Type ID
Description
1
2
30
31
37
Single-point information
Single-point information with time tag
Single-point information with time tag CP56Time2a
Double-point information with time tag CP56Time2a
Integrated total with time tag CP56Time2a
Ring chronological in
message
34
Measured value, normalized value with time tag
CP56Time2a
Measured value, scaled value with time tag
CP56Time2a
Measured value, short floating point number with
time tag CP56Time2a
Process image
Single command
Single command with time tag CP56Time2a
Double command
Double command with time tag CP56Time2a
Setpoint command, normalized value
Setpoint command, normalized value with time tag
CP56Time2a
Setpoint command, scaled value
Setpoint command, scaled value with time tag
CP56Time2a
Setpoint command, short floating point number
Setpoint command, short floating point number with
time tag CP56Time2a
Counter interrogation command
Ring chronological global
35
36
45
58
46
59
48
61
49
62
50
63
101
Type of storing
Datenfluss
informations, integrated totals
commands, setpoint values, counter interrogation
ring chronological in message
ring chronological global
measured values
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
process image
control
181
Automation
5.4.3.1.1 Process image (state stored).
If data are entered in the process image (source: direct or decoupled via a ring), then the
individual fields are updated.
Exception: Spontaneous bit, single command (TI 45) and double command (TI 46). The state
is reset after one cycle.
For each information object type, the following information is stored:
Type
Information
Status bits in detail
Single-point information
Double-point information
COT
PN
T
ORIGINATOR
Status bits
User data
Time
S
NT
IV
CLASS1
BL
SB
Measured value, normalized value
Measured value, scaled value
Measured value, short floating point number
COT
PN
T
ORIGINATOR
Status bits
User data
Time
S
NT
IV
OV *)
CLASS1
OVW
BL
SB
Single command
Double command
Setpoint command, normalized value
Setpoint command, scaled value
Setpoint command, short floating point number
Counter interrogation command
COT
PN
T
ORIGINATOR
Status bits
User data
Time
S
CLASS1
CY
CA
Integrated total
COT
PN
T
ORIGINATOR
Status bits
User data
Time
sequence number
S
IV
CLASS1
CY
CA
*)
the bit OVW (overflow value) is set if a measured value to be written exceeds the upper or
lower limit of the data type; this bit is only applicable for normalized and scaled measured
values (TI34, TI35), the output side OV-bit is an OR logic operation of OV and OVW
5.4.3.1.2 Ring chronological in message.
The ring has a capacity of 140 entries.
With each cycle, reading continues to take place from this ring and the associated process
image is updated until one of the following conditions is fulfilled:
182
•
Ring is empty
•
Same IOA (index process image) is read a second time
•
50 messages have been read from the ring
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02
Automation
5.4.3.1.3 Ring chronological global.
The ring has a capacity of 20 entries.
With each cycle only one message is read from this ring and the associated process image
updated.
5.4.3.1.4 Ring Overflow
If a message not be entered due to the ring being full, then an error message is set and the
corresponding IOA is flagged as data loss.
Upon going ring overflow a general interrogation is tripped.
5.4.3.2
Output Signals
Controller output side, messages are then generated if one of the following conditions is
fulfilled:
•
Rising edge of the spontaneous bit (S).
•
Change of user data content.
•
Change of the quality bits (IV, NT, SB, BL, OV, CA, CY, SQ).
•
Change of the cause of transmission (COT, PN, T).
If the real-time of a controller output is not assigned by the application program, then it is
generated with the current time.
5.4.3.3
Automatic Routing of Data Points
Routing of spontaneus data points to the open closed loop function taking place by the
specification of the IOA in the IL implicit.
Routing of periodical data points from and to the open closed loop function taking place by the
definition of system variables.
5.4.3.4
Non-Volatile Memory
Variables that are defined as "retain" are stored in this sector. The storage takes place on the
module's own EEPROM synchronous to the controller pass every 500 ms. For this purpose
256 Byte of EEPROM are reserved and written according to an old-new comparison.
The sector in the EEPROM is checksum secured. If a checksum error occurs, then the entire
sector is re-written (this also applies with the first restart).
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
183
Automation
5.4.3.5
Loading of Program (Cold Start)
After loading the program the code is written into a separate area of the FLASHPROM
(checksum secured) and a startup is performed.
During this startup the sector of the NV-RAM for the controller is initialized , which means that
all variables (including the non-volatile flags) are set to their default values or their explicitly
specified initialization values.
After startup the program is processed from the Flash-PROM.
Further after loading the user program.
5.4.3.6
Treatment of communication failure
No data, that are received by the communication and sent to the controller (e.g. binary
informations for the control of functions in the controller), are created with the NT bit, if the
communication fails.
Reason: With usage of communication via Ethernet (IEC 60870-5-104) the data source
cannot be clearly established, since up to 4 sources are possible.
If necessary the error statistics of the communication are analyzed in the user program via the
system variable PLC_SYSERROR in order to derive further functions depending on these.
5.4.3.6.1 Startup(Warm start)
During a restart, all flags that are identified as non-volatile, are loaded from NV-RAM. The
entire input process image of the open-/closed-loop control function is initialized with the
current state of the periphery.
All data which cannot be initialized with current values, are initialized with the following values:
Variable
Value
T, PN, COT
0
ORIGINATOR
0
OV, S, GI, SB, BL, IV, CLASS1, CA, CY, SQ
0
NT
1
User data
0
Time
01:01:2000
00:00:00.000
Afterwards the open-/closed-loop control function starts operation.
Hint
The communication (serial or Ethernet) is first begun after one single, complete pass of the cycle part of
the user program (PLC_START).
184
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02
Automation
5.4.4
Online Test
The following test functionalities are available:
•
•
Display/Forcing of Values
Changing the Processing Status of the Controller
Informations about these functions are given in section 5.2.7.1, Display/Forcing of Values and
5.2.7.3, Changing the Processing Status of the Controller.
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
185
Automation
186
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02
A
Message Formats
Content
A.1
Introduction....................................................................................................... 188
A.2
Overview .......................................................................................................... 188
A.3
Messages with Process Information ................................................................ 190
A.4
Messages with System Information ................................................................. 208
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
187
Message Formats
A.1
Introduction
Only messages, both for process- as well as system information, with type
identification are supported in the public range of the IEC 60870-5-101/104.
Exceptions are system functions that are not defined in the public range of the IEC
60870-5-101/104:
•
Containers for process information (e.g. messages according to IEC 60870-5-103)
•
Containers for system information (e.g. remote maintenance).
In principle one differentiates between two types of communication:
•
Communication within an automation unit
•
Communication between automation units over their serial interfaces or LAN/WAN
connections
The message formats within the automation units are defined with regard to their
contents in such a way, that a conversion is possible at the interfaces to other
automation units into the following formats:
•
IEC 60870-5-101
•
IEC 60870-5-103
•
IEC 60870-5-104
IEC 60870-5-101 on serial or IEC 60870-5-104 on LAN/WAN connections are the
standard format for communication between the automation units of ACP 1703.
Over the transmission route, the message format between automation units is also
provided with a protocol-dependent message frame.
The following table shows the type identifications of the supported messages. For
messages over the communication routes, it can be set, whether they are transmitted
with 3 or 7 octet (Parameter Communication | PRE# | IEC60870-5101/104 | Variable elements of the message | Time stamp) or without time
stamp (parameter group Communication | PRE# | IEC60870-5101/104 | Transmission with/without timetag | *). The messages within
the automation unit always have a time stamp with 7 octets.
This chapter describes exclusively those message formats within the automation unit.
A.2
Overview
Legend:
TI external
…
Type identification over the communication route
TI internal
…
Type identification within the automation unit
The specification "monitor direction" or "control direction" is for classification
according to IEC 60870-5 only.
Message with process information
in monitor direction
TI
external
Time stamp
Single-point information
1
without
2
3 octet dual time
30
7 octet dual time
3
without
Double-point information
188
TI
internal
30
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02
Message Formats
4
3 octet dual time
31
7 octet dual time
5
without
6
3 octet dual time
32
7 octet dual time
7
without
8
3 octet dual time
33
7 octet dual time
9
without
10
3 octet dual time
34
7 octet dual time
11
without
12
3 octet dual time
35
7 octet dual time
13
without
14
3 octet dual time
36
7 octet dual time
15
without
16
3 octet dual time
37
7 octet dual time
17
3 octet dual time
38
7 octet dual time
18
3 octet dual time
39
7 octet dual time
39
Message with process information
in monitor direction (cont.)
TI
external
Time stamp
TI
internal
Blocked triggering of the protection
19
3 octet dual time
40
7 octet dual time
40
Blocked single point information with change
20
without
not supported
Message with process information
in control direction
TI
external
Time stamp
TI
internal
Single command
45
without
58
7 octet dual time
46
without
59
7 octet dual time
47
without
60
7 octet dual time
48
without
61
7 octet dual time
49
without
62
7 octet dual time
Step position information
Bitstring of 32 bit
Measured value, normalized value
Measured value, scaled value
Measured value, short floating point number
Integrated totals
Event of protection equipment
Blocked activation of the protection
Double command
Regulating step command
Set point command, normalized value
Set point command, scaled value
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
31
32
33
34
35
36
37
38
45
46
47
48
49
189
Message Formats
50
without
63
7 octet dual time
51
without
64
7 octet dual time
Message with system information
in control direction
TI
external
TI
internal
(General) Interrogation Command
100
internal message with system
information
Counter interrogation command
101
internal message with system
information
Clock synchronization command
103
internal message with system
information
Message in private range
TI
external
TI
internal
Container for system information
135
internal message with system
information
Container for process information
142
142
Set point command, short floating point
number
Bitstring of 32 bit
A.3
50
51
Messages with Process Information
The internal data format is formed from
•
the general message data such as length, function code and the checksum
•
the internal extra information dependent on the function code for process
information
•
the address
•
the status
•
the type identification
•
the time stamp
•
the information object
General legend for the data formats
All numbers listed are decimal numbers, unless they are specified explicitly as
hexadecimal numbers (indicated by "Hex").
"xxx" means, that this bit is defined, but in this case is insignificant.
190
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02
Message Formats
A.3.1
General Message Structure
A.3.1.1 Length, Function Code and Checksum
27
26
25
24
23
22
21
20
length
function code
function code dependent
extra information
address
state
type Identification
time stamp
information object
checksum
•
LENGTH:
[8 Bit]
Length over the entire internal data format in words without checksum
•
FUNCTION CODE:[8 Bit]
The function code specifies the format of the process information on the various
buses. In addition the possibility exists of transmitting process information over the fast
data channel,
•
CHECKSUM:
[8 Bit] on the Ax 1703 PE-Bus
[16 Bit] on the Node Bus and SBD-Bus
additive sum of all bytes modulus 256 on the Ax 1703PE-Bus or all words modulus
65536 on the Node- and SBD-Bus in the message excluding the checksum.
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
191
Message Formats
A.3.1.2 Function Code-Dependent Extra Information
27
26
25
24
23
22
21
20
0
length
2 or 4
1
function code
2
acknowledgement
info
3
4
5
Reserve
SQ
Number
variable structure qualifier
6
Time
7
IOA
format definition
Reserve
8
destination station
9
Basic System Element
source identification
10
Supplementary System Element
11
Station number
12
address
17
state
23
type identification
25
time stamp
32
nformation object
blocked
information objects
checksum
•
ACKNOWLEDGEMENT INFO:
0-65535
192
...
[16 Bit]
reserved
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02
Message Formats
Not used on the node bus
•
DESTINATION STATION:
0 - 99
125 ...
126 ...
255 ...
...
destination station number
reserved
reserved
no destination station (Single Point)
Not used on the node bus
•
SOURCE IDENTIFICATION:
[3x8 Bit]
The source identification specifies the entry point of the message in the automation
unit, or the source of the message within the automation unit.
Basic System Element 0-15
...
20
...
M-CPU
C-CPU 0 -15
Supplementary System Element
0-15
...
Peripheral element 0-15
128-131 ...
Protocol element 0 -3
254
...
the basic system element itself (source within the AU)
Station number
0-99
...
for protocol elements with Multi Point data
communication mode
254
...
the supplementary system element itself (source within the AU)
255
...
for protocol elements with Single Point data communication
mode
•
VARIABLE STRUCTURE QUALIFIER:
SQ ...
0
information object
1
...
Information object address available for every
...
Information object address available one time, all other
information objects have
ascending address order (LSB)
Number
•
...
>1
<2
...
...
an information object in the message
n information objects in a message
FORMAT DEFINITION:
defines the structure of the blocked information objects (valid only for SQ = 0)
IOA ...
0
1
2
3
...
...
...
...
inadmissible
LSB of the IOA
nd
LSB and 2 byte of the IOA (Octet 3 and 4)
nd
rd
LSB, 2 and 3 byte of the IOA (Octet 3, 4 and 5)
Time ...
0
1
2
3
...
...
...
...
no time
3 octet dual time (only possible in transmit direction)
7 octet dual time
inadmissible
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
193
Message Formats
A.3.1.3 Address
The address is used for the identification of an information object. It consists of two
parts
•
Common address of ASDU (CASDU)
•
Information object address (IOA)
This address has no predefined assignment, rather is freely assigned by the user
within the 5 octets of the address field.
The type identification is also drawn upon for the unambiguous identification of an
information object.
27
26
25
24
23
22
21
20
Länge
Funktionscode
funktionscodeabhängige
Zusatzinformation
12
CASDU1
13
CASDU2
14
IOA1
15
IOA2
16
IOA3
Gemeinsame
Adresse der ASDU
Adresse des
Informationsobjekts
Status
Typkennung
Zeitmarke
Informationsobjekt
Prüfsumme
194
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02
Message Formats
A.3.1.4 State
27
26
25
24
23
22
21
20
length
function code
function code dependent
extra information
address
17
XXX
XXX
18
T
P/N
19
IV
NT
GA
S
XXX
DV
XXX
R
Cause
SB
BL
EI
20
Reserve
21
Reserve
message state
cause of
transmission
0
0
22
OV
data point quaity descriptor
originator address
type identification
time stamp
information object
checksum
•
MESSAGE STATE:
[8 Bit]
DL Data Loss
indicates FIFO overflow.
The last correct message before the data loss bears the set state.
GI General Interrogation
the message of the interrogated data contains this state. This bit is always set, if the
cause of transmission is 2 or 20.
R
Redundancy Identifier
Used to distinguish the received data between the active or passive station.
0 ... active or no redundancy
1 ... passive
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
195
Message Formats
S
Spontaneous
The transmission has been initiated spontaneous due to a significant change or due to
an internal or external interrogation event (e.g. with station interrogation). With cyclic
data transmissions or data transmissions initiated through GI the state is not set,
however with state-change- and transient storage it is entirely possible that
simultaneous occurrences of the GI- and the S-state can happen.
This bit is always set, if the cause of transmission is 3 or 6.
•
CAUSE OF TRANSMISSION:
Cause
60870-5-101
01 - 47
00 ..
01 ..
02 ..
03 ..
04 ..
05 ..
06 ..
07 ..
08 ..
09 ..
10 ..
11 ..
12 ..
13 ..
14 - 19
20 ..
21 - 36
37 ..
38 - 41
42 - 47
48 - 63
01 - 63 ..
[8 Bit]
Identifier of the cause of transmission according to IEC
..
Definition in the compatible range
invalid
periodical
background scan
spontaneous
initialized
requested
Activation
Confirmation of the activation
Deactivation
Confirmation of the deactivation
Termination of the activation
Return information, caused by a remote command *1
Return information, caused by a local command *1
Transmission of a file
..
reserved
interrogated by station interrogation
..
interrogated by group 1 – 16 interrogation
interrogated by general counter interrogation
..
requested by group 1 – 4 counter request
..
reserved
..
Definition in the private range
*1
The remote command or local command is determined by the originator address:
1
...
127
Remote command
128 ...
255
Local command
•
P/N
1
0
..
..
Positive confirmation
Negative confirmation
•
T Test
•
DATA POINT QUALITY DESCRIPTOR:
[8 Bit]
The data point quality descriptor is dependent on the information object in the
message. I.e. with certain information objects several identifiers are irrelevant.
OV ...
value range
Overflow
BL
blocked the information is blocked for the transmission
...
the value of the information is outside a predefined
SB ...
substituted
the value of the information has been specified by an
operator or a sequence of automatic operations.
NT ...
disturbed).
not topical
The value is not current (e.g. the transmission is
IV ...
invalid The value is invalid. An acquisition function has determined an
abnormal function of the acquisition unit (e.g. the ADC no longer converts)
196
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02
Message Formats
EI ...
Elapsed time invalid (run-/ command time invalid)
The relative time in the message is invalid. This information is only provided for
protection events.
•
ORIGINATOR ADDRESS: [8 Bit]
0
1
not available
...
255
Number of the originator address
A.3.1.5 Type Identification
27
26
25
24
23
22
21
20
length
function code
function code dependent
extra information
address
state
23
type identification
24
reserved
time stamp
information object
checksum
•
TYPE IDENTIFICATION: [8 Bit]
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
197
Message Formats
A.3.1.6 Time Stamp
27
26
25
24
23
22
21
20
length
function code
function code dependent
extra information
address
state
type identification
25
MILLISECONDS
26
27
IV
28
SU
29
XXX
RES.
HOUR
WEEKDAY
30
31
MINUTE
7 octet dual time
DAY IN THE MONTH
RESERVE
MONTH
RES.
YEAR
Information object
checksum
198
•
MILLISECONDS: [16 Bit] <0 .. 59999>
•
MINUTE: [6 Bit]
•
IV:
[1 Bit]
0 .. Time valid, 1 .. Time invalid
•
HOUR:
[5 Bit]
<0 .. 23>
•
SU:
[1 Bit]
0 .. Standard time, 1 .. Daylight-saving time
•
DAY IN THE MONTH:
[5 Bit]
•
WEEKDAY:
[3 Bit]
<1 .. 7>
•
MONTH: [4 Bit]
<1 .. 12>
•
YEAR:
<0 .. 99>
[7 Bit]
<0 .. 59>
<1 .. 31>
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02
Message Formats
A.3.2
Information Objects
A.3.2.1 Single-Point Information (TI = 30)
27
26
25
24
23
22
21
20
19
IV
NT
SB
BL
xxx
0
0
xxx
Data point quality
descriptor
32
0
0
0
0
0
0
0
SPI
Information object
SPI ...
Single point information state (Single point information)
A.3.2.2 Double-Point Information (TI = 31)
27
26
25
24
23
22
21
20
19
IV
NT
SB
BL
xxx
0
0
xxx
32
0
0
0
0
0
0
DPI
data point quality
descriptor
information object
DPI ...
Double-point information state (Double point information)
0 = Intermediate position
1 = OFF
2 = OIN
3 = Faulty position
A.3.2.3 Transformer Tap Position Value (digital) (TI = 32)
27
26
25
24
23
22
21
20
19
IV
NT
SB
BL
xxx
0
0
OV
32
LK/T
data point quality
descriptor
value
LK/T ...
moving contact information
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
199
Message Formats
A.3.2.4 Bitstring of 32 bit (TI = 33)
27
26
25
24
23
22
21
20
19
IV
NT
SB
BL
xxx
0
0
xxx
data point quality
descriptor
32
BS7
BS0
bit 00 - 31
33
BS15
BS8
34
BS23
BS16
35
BS31
BS24
A.3.2.5 Measured Value, Normalized Value (TI = 34)
19
27
26
25
24
23
22
21
20
IV
NT
SB
BL
xxx
0
0
OV
data point quality
descriptor
2-1
measured value
32
33
Vz
2-15
Measured value ... 15 Bit + Vz ... < -1 .. 1-2-15>
The resolution is not determined; if the resolution is less than the LSB-unit, the least
significant bits are set to "ZERO".
A.3.2.6 Measured Value, Scaled Value (TI = 35)
19
27
26
25
24
23
22
21
20
IV
NT
SB
BL
xxx
0
0
OV
data point quality
descriptor
20
measured value
32
33
Vz
214
Measured value ... 15 Bit + Vz ... <-215 .. +215- 1>
200
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02
Message Formats
A.3.2.7 Measured Value, Short Floating Point Number (TI = 36)
27
26
25
24
23
22
21
20
19
IV
NT
SB
BL
xxx
0
0
OV
32
27
Mantissa
20
33
215
Mantissa
28
34
20
222
Mantissa
216
35
Vz
27
Exponent
21
data point quality
descriptor
measured value
The resolution is not determined; if the resolution is less than the LSB-unit, the least
significant bits are set to "ZERO".
A.3.2.8 Integrated Totals (TI = 37)
27
26
25
24
23
22
21
20
19
IV
XXX
XXX
XXX
XXX
0
0
XXX
32
27
20
33
215
28
34
223
216
35
VZ
230
36
0
CA
data point quality
descriptor
integrated total
224
CY
Sequenznummer
sequence number
...
0 - 31
CA ...
Counter set
CY ...
Counter overflow
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
201
Message Formats
A.3.2.9 Event of Protection Equipment (TI = 38)
27
26
25
24
23
22
21
20
19
IV
NT
SB
BL
EI
0
0
0
data point quality
descriptor
32
0
0
0
0
0
0
33
27
20
elapsed time
34
215
28
elapsed time ...
ES
Run/Command time
<0 .. 59999 ms>
ES
...
(Event state) binary information state
EI
...
(Elapsed time invalid) run-/ or command time invalid
A.3.2.10 Blocked Activation of the Protection (TI = 39)
27
26
25
24
23
22
21
20
19
IV
NT
SB
BL
EI
0
0
0
32
0
0
SRD
SIE
SL3
SL2
SL1
GS
33
27
20
34
215
28
Relay duration
...
Relay duration time
data point quality
descriptor
relay duration
<0 .. 59999 ms>
GS: General start of operation (General start)
SL1: Activation L1
(Start L1)
SL2: Activation L2
(Start L2)
SL3: Activation L3
(Start L3)
SIE: Start of operation IE (earth current) (Start IE)
SRD:
202
Start of operation in reverse direction
(Start reverse direction)
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02
Message Formats
A.3.2.11 Blocked Triggering of the Protection (TI = 40)
27
26
25
24
23
22
21
20
19
IV
NT
SB
BL
EI
0
0
0
32
0
0
0
0
CL3
CL2
CL1
GC
33
27
20
34
215
28
relay operating time
...
Relay operation time
data point quality
descriptor
relay operating time
<0 .. 59999 ms>
GC ...
(General command) General - OFF - information
CLX ...
(Command LX) Phase LX - OFF - information
A.3.2.12 Single Command (TI = 45)
27
26
25
24
23
22
21
20
19
xxx
xxx
xxx
xxx
0
0
0
xxx
data point quality
descriptor
32
S/E
0
SCS
information object
qualifier of command
S/E ...
Select / Execute
SCS ...
0
=
1
=
Single command (Single command state)
OFF
ON
qualifier of command ...
0
output time interval determined by
executing point)
=
no additional determination (i.e.
parameter at the
1
=
short command output time (determined by parameter)
2
=
long command output time (determined by parameter)
3
=
persistent command (no regulating command)
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
203
Message Formats
A.3.2.13 Double Command (TI = 46)
27
26
25
24
23
22
21
20
19
xxx
xxx
xxx
xxx
0
0
0
xxx
32
S/E
qualifier of command
DCS
information object
S/E ...
Select / Execute
DCS ...
Double command (double command state)
0
=
not permitted
1
=
OFF
2
=
ON
3
=
not permitted
qualifier of command ...
0
output time interval determined by
executing point)
=
data point quality
descriptor
no additional determination (i.e.
parameter at the
1
=
short command output time (determined by parameter)
2
=
long command output time (determined by parameter)
3
=
persistent command (no regulating command)
A.3.2.14 Regulating Step Command (TI = 47)
27
26
25
24
23
22
21
20
19
xxx
xxx
xxx
xxx
0
0
0
xxx
32
S/E
204
qualifier of command
RCS
data point quality
descriptor
information object
S/E ...
Select / Execute
RCS ...
Regulating Step Command (Regulating command state)
0
=
not permitted
1
=
next step lower
2
=
next step higher
3
=
not permitted
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02
Message Formats
qualifier of command ...
0
output time interval determined by
executing point)
=
no additional determination (i.e.
parameter at the
1
=
short command output time (determined by parameter)
2
=
long command output time (determined by parameter)
3
=
persistent command (no regulating command)
A.3.2.15 Setpoint Command, Normalized Value (TI = 48)
19
27
26
25
24
23
22
21
xxx
xxx
xxx
xxx
0
0
0
xxx
data point quality
descriptor
20
Vz
32
214
S/E
setpoint value identifier
setpoint value ...
S/E ...
information object
15 Bit + Vz ... <-1 ... +1 - 2-15>
Select / Execute
setpoint value identifier...
presently no definition
The resolution is not determined; if the resolution is less than the LSB-unit, the least
significant bits are set to "ZERO".
A.3.2.16 Sollwert-Stellbefehl, skalierter Wert (TI = 49)
19
27
26
25
24
23
22
21
20
xxx
xxx
xxx
xxx
0
0
0
xxx
data point quality
descriptor
20
32
33
Vz
34
S/E
214
information object
setpoint value identifier
setpoint value ...
S/E ...
15 Bit + Vz ... <-215 .. +215 - 1>
Select / Execute
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
205
Message Formats
setpoint value identifier...
presently no definition
The resolution is not determined; if the resolution is less than the LSB-unit, the least
significant bits are set to "ZERO".
A.3.2.17 Setpoint Command, Short Floating Point Number (TI = 50)
27
26
25
24
23
22
21
20
19
xxx
xxx
xxx
xxx
0
0
0
xxx
32
27
Mantissa
20
33
215
Mantissa
28
34
20
222
Mantissa
216
35
Vz
27
Exponent
21
36
S/E
data point quality
descriptor
setpoint value identifier
S/E ...
information object
Select / Execute
setpoint value identifier...
presently no definition
The resolution is not determined; if the resolution is less than the LSB-unit, the least
significant bits are set to "ZERO".
A.3.2.18 Container for Process Information (TI = 142)
The container for process information is used for the direct pass through of messages
that do not conform to the 60870-5-101/104 standard.
19
27
26
25
24
23
22
21
20
xxx
xxx
xxx
xxx
xxx
0
0
xxx
data point quality
descriptor
32
length of user data in
bytes
33
message type
34
user data (max. 104
bytes)
206
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02
Message Formats
The container for process information does not contain any time information.
Message type:
1 - 127 ...
3
...
128 - 255
128
...
129
...
130
...
131
...
250
...
253 - 255
0
...
non-specified message format
public range
Message format according to IEC870-5-103
...
private range
SAT Standard format
SSI-Format
STA-reply
File transfer SAT-DISTO
protocol-specific container
...
Parameter container for REY-DISP
A.3.2.19 File Transfer (TI = 144)
19
27
26
25
24
23
22
21
20
xxx
xxx
xxx
xxx
xxx
0
0
xxx
data point quality
descriptor
32
33
file transfer - data
A.3.2.20 Packed Information Objects
These parts only then exist in the message, if the number in the field "variable structure
qualifier" is >1.
The subsequently described block occurs n times –1 according to the number in the
field "Variable Structure Qualifier". The first information object is always located in the
"Standard part" of the internal data format.
The addressing of the individual information objects corresponds to the
IEC-60870-5-101 standard.
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
207
Message Formats
A.3.2.21 Addressing of an Individual Element (SQ=0)
27
26
25
24
23
22
21
20
information object address
1, 2, 3 octet (optionall)
depending on the
format definition "IOA"
DP quality descriptor
not present, 3 octet, 7 octet (optional)
time dependent on
format definition "Time"
information object
A.3.2.22 Addressing of a Sequence of Information Elements (SQ=1)
27
26
25
24
23
22
21
20
DP quality descriptor
information object
A.4
Messages with System Information
The internal data block format contains
208
•
the general message data such as length, function code and the checksum
•
the source address
•
the destination address
•
message identification
•
Source identification
•
Bus information
•
the information code dependent on the function code
•
the system information
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02
Message Formats
A.4.1
Counter Interrogation Command
27
26
25
24
23
22
21
0
20
length
1
153
function code
2
Source-Region = 0-249
source address
3
Source-Component = 0-254
4
Source-Basic System Element = 0-16, 20
5
Source-Supplementary System Element = 254
6
Destination-Region = 255
7
Destination-Component / Station = 255
8
Destination-Basic System Element = 31
9
Destination-Supplementary System Element = 255
destination address
message identification
source identification
bus information
reserve
20
0
21
6
information code
cause of transmission
22
LSB of the CASDU
23
MSB of the CASDU
24
FRZ
RQT
25
qualifier of interrogation
reserve
checksum
Qualifier of interrogation:
(QCC):
Identifier for the counter interrogation command
FRZ
RQT
Function
0
1 .. 4
5
Transmit selective group 1 .. 4
Transmit all groups (1 .. 4)
1
1 .. 4
5
Latching of selective group 1 .. 4
Latching of all groups (1 .. 4)
51 .. 54
55
Freeze and spontaneously transmit selective group 1 .. 4
Freeze and spontaneously transmit all groups (1 .. 4)
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
209
Message Formats
2
3
1 .. 4
5
Latching with reset of selective group 1 .. 4
Latching with reset of all groups (1 .. 4)
51 .. 44
55
Freeze with reset and spontaneously transmit selective group 1 .. 4
Freeze with reset and spontaneously transmit all groups (1 .. 4)
1 .. 4
5
Resetting of selective group 1 .. 4
Resetting of all groups (1 .. 4)
RQT: 0 .. 31
32 .. 63
A.4.2
public range
private range
(General) Interrogation Command
27
26
25
24
23
22
21
0
20
length
1
155
function code
2
Source-Region = 0-249
source address
3
Source-Component = 0-254
4
Source-Basic System Element = 0-16, 20
5
Source-Supplementary System Element = 254
6
Destination-Region = 255
7
Destination-Component / Station = 255
8
Destination-Basic System Element = 31
9
Destination-Supplementary System Element = 255
destination address
message identification
source identification
bus information
reserve
20
0
21
6
22
CASDU 1
LSB of the CASDU
23
CASDU 2
MSB of the CASDU
24
25
information code
cause of transmission
qualifier of interrogation
reserve
checksum
210
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02
Message Formats
Qualifier of interrogation:
acc. to IEC 60870-5-101 =
interrogation (global)
private range
=
64 ... Process information
65 ... Error messages
66 ... Failure messages
67 ... Application-GI
SICAM 1703 Common Functions System and Basic System Elements
DC0-015-2.02, Edition 02.2011
20 ... Station
211
Message Formats
212
SICAM 1703 Common Functions System and Basic System Elements
Edition 02.2011, DC0-015-2.02