02_General_009
02_General_009
0 SP2
Function Block Library
Function Description Edition 03/19
General
Safety Guidelines
This manual contains notices you have to observe in order to ensure your personal safety, as well as to prevent damage
to property. The notices referring to your personal safety are highlighted in the manual by a safety alert symbol, notices
referring to property damage only have no safety alert symbol. The notices shown below are graded according to the
degree of danger.
Danger
! indicates that death or severe personal injury will result if proper precautions are not taken.
Warning
! indicates that death or severe personal injury may result if proper precautions are not taken.
Caution
! with a safety alert symbol indicates that minor personal injury can result if proper precautions are not
taken.
Caution
without a safety alert symbol indicates that property damage can result if proper precautions are not
taken.
Attention
indicates that an unintended result or situation can occur if the corresponding notice is not taken into
account.
If more than one degree of danger is present, the warning notice representing the highest degree of danger will be used.
A notice warning of injury to persons with a safety alert symbol may also include a warning relating to property damage.
Qualified Personnel
The device/system may only be set up and used in conjunction with this documentation. Commissioning and operation
of a device/system may only be performed by qualified personnel. Within the context of the safety notices in this doc-
umentation qualified persons are defined as persons who are authorized to commission, ground and label devices, sys-
tems and circuits in accordance with established safety practices and standards.
Prescribed Usage
Note the following:
Warning
! This device and its components may only be used for the applications described in the catalog or the
technical description, and only in connection with devices or components from other manufacturers
which have been approved or recommended by Siemens.
Correct, reliable operation of the product requires proper transport, storage, positioning and assembly
as well as careful operation and maintenance.
Trademarks
All names identified by ® are registered trademarks of the Siemens AG.
The remaining trademarks in this publication may be trademarks whose use by third parties for their own purposes
could violate the rights of the owner.
Siemens AG
Automation and Drives Siemens AG 2005
Postfach 4848, 90327 Nuremberg, Germany Technical data subject to change.
Siemens Aktiengesellschaft
Reference Manual Objects General
Content
GENERAL 1
CEMAT Modules 4
Module data 5
CEMAT blocks 5
Interlock Modules from PCS 7 Advanced Process Library 6
Explanations to the Table Module Data 7
CEMAT Modules
The library "Minerals_Cemat" contains all blocks which are required for a running CEMAT AS.
The Reference Manual Objects describes the functions of the CEMAT Object modules. All fur-
ther Blocks you find in the general Documentation of PCS 7.
In this chapter you find the general, information about the CEMAT modules which is not specific
for a certain object. You will find information about performance, an introduction to the module
description (AS), general display rules (OS) and the representation forms of the objects.
In addition you will find operating instruction for the HMI.
Module data
CEMAT blocks
Runtime in ms
The time that the CPU needs to process the associated module program in the normal situation
(e.g. in the case of a driver, the processing time of the watch-dog timer organizational block
(OB), without producing an annunciation for a channel error).
The following table contains the runtimes in a S7 410-5HX08-0AB0. The runtimes for other
CPUs depend on their performance.
Work Memory
Memory requirement of the program code, once per module type.
Temporary memory
The local data storage required in a processing level for an invocation of the module. This is lim-
ited for a specific CPU, and causes a CPU stop should it be exceeded. You must check this in
the CPU configuration and, if necessary, redistribute to the processing levels (OBs) in accord-
ance with the actual requirement.
Multi-instance module
The technological module uses the specified modules and must be contained in the AP (appli-
cation program). They are stored in the same library.
Type/number
The listed blocks have to be called if you want to use the object. The Blocks are listed with
name and number.
Module name: Unique name of the S7 Block, e. g. C_DRV_1D.
For the CEMAT Objects this corresponds to the name of the object type.
Module no.: Unique number of the function block (FB) or function (FC).
Calling OBs
This provides details of the organizational blocks (OBs) in which the described block must be
installed.
In contrast to the general PCS 7 libraries the CEMAT library has some specialties. Most of the
CEMAT blocks must be called exclusively in the OB1 task. The detailed information you find in
the object descriptions.
When you install the modules in the CFC they are automatically called after the most recently
installed module. If necessary, you must change the processing sequence with the run-time edi-
tor. The CFC creates the necessary OBs during the compilation.
Function
This contains a summary of the function of the module. The section operating principle contains
further information for complex modules.
Operating principle
This contains more detailed information on the function of individual inputs, operating modes,
time processes, etc. You should understand the interrelationships described here in order to use
the module effectively.
Error handling
The error display is located in the CFC plan at the ENO Boolean module exit. The value corre-
sponds to the BIE (binary result in STEP 7-STL on completion of the module) or the OK bit (in
SCL notation) and means:
ENO=BIE=OK=1 (TRUE) -> the module result is correct.
ENO=BIE=OK=0 (FALSE) -> the result or the general conditions for this calculation (e.g. entry
values, operating mode, etc.) are invalid.
Start-up characteristics
A differentiation is made between:
First run
The module is called initially from the OB in which it has been inserted. This is usually the OB in
which the normal, process-related processing takes place (e.g. OB1). The module is preset with
the status corresponding to the input parameters. These can be default values (also refer to I/O
bar) or previously configured values, which, for example, you have parameterized in the CFC.
No special start-up behavior is described unless the module deviates from this rule.
Start-up
The module is processed once during a CPU start-up. To ensure this, the module has to be
called from a start-up OB (where it is included automatically by the ES). The start-up behavior is
described in this case.
The CEMAT object modules don’t have start-up characteristics. The blocks are called exclusive-
ly in the cyclical program.
Time characteristics
A module with time characteristics must be installed in an cyclic interrupt OB. It calculates its
time constants/parameters using its sampling time (the time interval between two successive,
cyclical processing steps). The sampling is determined by the step downs for the so-called run-
time group. This ensures that the module is not processed for every OB passage. This sampling
time is entered in the I/O bar, in the SAMPLE_T parameter.
The time behavior is mentioned only when the module exhibits such behavior.
The CEMAT object modules don’t have time characteristics. However for some of the objects
the run sequence is important. This is described under time characteristics.
Annunciation characteristics
The module with this behavior reports various events to the higher-level OS. When present, the
parameters needed to create the annunciation are documented. Modules without annunciation
behavior can be augmented with additional annunciation modules. The description for modules
with annunciation capability contains an indication of the annunciation behavior.
Module states
The status of the CEMAT Objects is shown in the symbol through change of the bitmap of
change of the color and in the faceplate through a short info text. The presentation of the visual-
ization status is shown under module status.
Commands
The possible commands for the object are listed in the object documentation.
Permitted
Name Description Format Default Type Attr. HMI
Values
The "I/O-bar" table shows all input and output parameters of the module type which the user
can access with his configuring means. Those elements that can be reached only from the
module algorithm are not listed (so-called internal variables). The columns have the following
meaning:
Name
Name of the parameter, derived from the designation, e.g. PV_IN = Process Variable Input
(process quantity, control quantity). Where appropriate, the same name convention as for
SIMATIC is used.
Description
Function (possibly short description)
Format
S7 data type of the parameter (BOOL, REAL, etc.).
Default
The value of the parameter before the module runs for the first time (provided it has not been
changed during the configuring).
Type
Type of the module algorithm access to the parameter; a differentiation is made between inputs,
non-isolated inputs and outputs (refer to table).
Parameter Types:
Abbreviation Type
I Input. Value supplied to the module (display in the CFC: left-hand parame-
ter list)
O Output. Output value (display in the CFC: right-hand parameter list)
IO Input/Output. Non-isolated input, which can be written from the OS and
rewritten from the module (display in the CFC: left-hand parameter list)
Attr. (Attribute)
Additional characteristics of the parameter when used in CFC. Non-connected input and input-
output parameters can be parameterized (only input-output parameters for online FCs). Output
parameters cannot be parameterized and can be transferred in the CFC by connecting to an in-
put of the same data type. Additional or deviating properties of the parameter are specified as
follows:
Attributes of the parameters:
Abbreviation Attribute
B Can be operated (only using the OS). An OS can make write access to the
element. It is implicitly not visible in the CFC.
E Transferred to the OS when changed
M MESSAGE ID not parameterizable for annunciation module (e.g. ALARM
8P). ID specified from the annunciation server.
Q Connectable. The element can be connected with another output of the
same type.
U Not visible in the CFC. Because the element is supplied by the CFC or the
OS, it is not displayed in the CFC (e.g. message ID). It is a default value
that can be changed in the CFC.
HMI
The parameters marked with "+" can be changed and monitored from the associated OS mod-
ule.
Permitted values
Additional limitation within the data type value range.
OS variables table
In the OS variables table all variables with Attribute S7_m_c = true are listed. During the OS
compile these variables are entered into the Tag Management of WinCC.
OS Variable
Name of the OS Variable
Description
Function (eventually short description)
PLC Data Type
S7 Data type of the parameter (BOOL, REAL, …)
OS Data Type
WinCC Data type of the parameter
Binary variable
Unsigned 8-bit value
Unsigned 16-bit value
Unsigned 32-bit value
Signed 16-bit value
32-bit floating-point number IEEE 754
Text variable 8-bit character set
Variable details
For the data exchange between AS and OS at many places the binary information is collected in
a word or double-word, in order to save resources. In this table you find the meaning of the sin-
gle bits.
Parameter
Parameter name used in the S7 program (internal information)
Function
Symbolic name of the parameter which describes the function.
OS Addr..
Variable number used WinCC and in the CFG-File (internal information)
Designation German
Description text of the parameter in German
Designation English
Description text of the parameter in English
Message Class
Message class, e. g. AL_H = Alarm - above
Fault Class
Classification according to the origin of the fault
E = Electrical
S = Safety
M = Mechanical
P = Process