Beruflich Dokumente
Kultur Dokumente
Basics 2
Logic blocks 6
Function Manual
Mathematical blocks 7
Panel blocks 9
Controller blocks 10
System blocks 11
Monitoring blocks 12
08/2017
A5E42064473-AA
Legal information
Warning notice system
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 only to property damage have no safety alert symbol. These 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
indicates that minor personal injury can result if proper precautions are not taken.
NOTICE
indicates that property damage can result if proper precautions are not taken.
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 product/system described in this documentation may be operated only by personnel qualified for the specific
task in accordance with the relevant documentation, in particular its warning notices and safety instructions. Qualified
personnel are those who, based on their training and experience, are capable of identifying risks and avoiding
potential hazards when working with these products/systems.
Proper use of Siemens products
Note the following:
WARNING
Siemens products may only be used for the applications described in the catalog and in the relevant technical
documentation. If products and components from other manufacturers are used, these must be recommended or
approved by Siemens. Proper transport, storage, installation, assembly, commissioning, operation and
maintenance are required to ensure that the products operate safely and without any problems. The permissible
ambient conditions must be complied with. The information in the relevant documentation must be observed.
Trademarks
All names identified by ® are registered trademarks of 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.
Disclaimer of Liability
We have reviewed the contents of this publication to ensure consistency with the hardware and software described.
Since variance cannot be precluded entirely, we cannot guarantee full consistency. However, the information in
this publication is reviewed regularly and any necessary corrections are included in subsequent editions.
1 Security information....................................................................................................................................19
2 Basics.........................................................................................................................................................21
2.1 About this document..............................................................................................................21
2.2 Overview of function blocks...................................................................................................22
2.3 Operator control and monitoring in WinCC............................................................................24
2.3.1 Block icon...............................................................................................................................24
2.3.2 Faceplate...............................................................................................................................25
2.3.3 Notes on configuration...........................................................................................................34
2.3.4 Setting of the standard server................................................................................................36
2.4 Hierarchical operating concept...............................................................................................37
2.4.1 Description of the concept......................................................................................................37
2.4.2 Configuration of the multiple control room operation.............................................................38
2.5 Panel integration....................................................................................................................39
2.5.1 Interface to the operator panel...............................................................................................39
2.5.2 Description of the concept......................................................................................................41
2.5.3 Overview of the IL S7 Comfort types.....................................................................................43
2.5.4 Operator control and monitoring in WinCC Comfort..............................................................45
2.5.4.1 General view of the panel blocks...........................................................................................45
2.5.4.2 Configuration of the panel interface.......................................................................................47
3 Operator control blocks..............................................................................................................................49
3.1 S7Aggr08 - Switchover for up to 8 units.................................................................................49
3.1.1 Function.................................................................................................................................49
3.1.2 Calling OBs............................................................................................................................49
3.1.3 Setting the operating mode....................................................................................................49
3.1.4 Number of units......................................................................................................................50
3.1.5 Master unit (OP_TIME_S parameter = 0)...............................................................................50
3.1.6 Maximum units to be switched...............................................................................................50
3.1.7 Activation/deactivation depending on operating hours / priorities (OP_TIME_S = 1
parameter)..............................................................................................................................51
3.1.8 Unit switch-on and switch-off delay........................................................................................51
3.1.9 Error handling.........................................................................................................................52
3.1.10 Cascading..............................................................................................................................52
3.1.11 Message behavior..................................................................................................................53
3.1.12 Startup characteristics............................................................................................................53
3.1.13 Time behavior........................................................................................................................53
3.1.14 Called blocks..........................................................................................................................53
3.1.15 Block parameters...................................................................................................................54
3.1.16 Operator control and monitoring............................................................................................58
3.1.16.1 S7Aggr08 views.....................................................................................................................58
3.1.16.2 S7Aggr08 standard view........................................................................................................58
3.1.16.3 S7Aggr08 parameter view......................................................................................................59
3.1.16.4 S7Aggr08 block icon..............................................................................................................60
9.14.1 Function...............................................................................................................................344
9.14.2 OBs to be called...................................................................................................................344
9.14.3 How it works.........................................................................................................................344
9.14.4 Startup characteristics..........................................................................................................345
9.14.5 Called blocks........................................................................................................................345
9.14.6 Block parameters.................................................................................................................345
9.14.7 Operator control and monitoring..........................................................................................347
9.14.7.1 S7PMV3P views...................................................................................................................347
9.14.7.2 S7PMV3P standard view.....................................................................................................347
9.14.7.3 S7PMV3P block icon............................................................................................................347
9.15 S7POpA - Operator panel interface for S7OpA...................................................................348
9.15.1 Function...............................................................................................................................348
9.15.2 OBs to be called...................................................................................................................348
9.15.3 Startup characteristics..........................................................................................................348
9.15.4 Called blocks........................................................................................................................349
9.15.5 Block parameters.................................................................................................................349
9.15.6 Operator control and monitoring..........................................................................................350
9.15.6.1 S7POpA views.....................................................................................................................350
9.15.6.2 S7POpA standard view........................................................................................................350
9.15.6.3 S7POpA block icons............................................................................................................350
9.16 S7POpD - Operator panel interface for S7OpD...................................................................351
9.16.1 Function...............................................................................................................................351
9.16.2 Calling OBs..........................................................................................................................351
9.16.3 Startup characteristics..........................................................................................................351
9.16.4 Called blocks........................................................................................................................352
9.16.5 Block parameters.................................................................................................................352
9.16.6 Operator control and monitoring..........................................................................................353
9.16.6.1 S7POpD views.....................................................................................................................353
9.16.6.2 S7POpD standard view........................................................................................................353
9.16.6.3 S7POpD block icons............................................................................................................354
9.17 S7PUsrM - operator panel interface for S7UsrM.................................................................355
9.17.1 Function...............................................................................................................................355
9.17.2 Calling OBs..........................................................................................................................355
9.17.3 Startup characteristics..........................................................................................................355
9.17.4 Called blocks........................................................................................................................356
9.17.5 Block parameter...................................................................................................................356
9.17.6 Operator control and monitoring..........................................................................................358
9.17.6.1 S7PUsrM views....................................................................................................................358
9.17.6.2 S7PUsrM standard view.......................................................................................................358
9.17.6.3 S7PUsrM block icons...........................................................................................................358
9.18 S7PVlv - Operator panel interface for S7Vlv........................................................................359
9.18.1 Function...............................................................................................................................359
9.18.2 Calling OBs..........................................................................................................................359
9.18.3 How it works.........................................................................................................................359
9.18.4 Startup characteristics..........................................................................................................360
9.18.5 Called blocks........................................................................................................................360
9.18.6 Block parameters.................................................................................................................360
9.18.7 Operator control and monitoring..........................................................................................362
9.18.7.1 S7PVlv views.......................................................................................................................362
9.18.7.2 S7PVlv standard view..........................................................................................................362
http://www.siemens.com/industrialsecurity.
Siemens’ products and solutions undergo continuous development to make them more secure.
Siemens strongly recommends to apply product updates as soon as available and to always
use the latest product versions. Use of product versions that are no longer supported, and
failure to apply latest updates may increase customer’s exposure to cyber threats.
To stay informed about product updates, subscribe to the Siemens Industrial Security RSS
Feed under
http://www.siemens.com/industrialsecurity.
Simulation active
Simulation inactive
Switching authority
Switching authority
The following switching authority are available:
● Operator panel: OP
● Control station OS (local control station): LCS
● Local OS: No icon
Tooltip text
The tooltip text contains text configured in the block comment of the associated AS block.
Referencing is in WinCC in the variable <instance>.#comment. The tooltip text is displayed
when the cursor is positioned on the icon.
2.3.2 Faceplate
Left-clicking on an icon in the WinCC graphic opens up an operator window (faceplate) for the
selected process tag.
Faceplate views
A faceplate usually offers a choice of several views.
The standard view provides a summary of the most important information. Additional views
contain detailed information and settings for the limits.
The button bar shows which view is currently active. The active button is colored green.
Maintenance view
Parameter view
Trend view
Message view
Batch view
3
4
1
2
Standard view
The standard view is different for each type of block, but the basic layout always remains the
same.
1
7
4 2
Limit view
The limit view is different for each block type depending on the number of limits, but the basic
layout is always the same.
1
2
Parameter view
The following control parameters can be set in the parameter view depending on block type:
● Monitoring,
● operating,
● and/or control parameters
(1) Setpoint
● High limit in %
● Low limit in %
(2) Slope in %
(3) Monitoring
● Run time in seconds
● Monitoring enabled
(4) Hysteresis
● Positioning in %
● Monitoring in %
Maintenance view
The maintenance view is different for each type of block, but the basic layout always remains
the same.
For motors, it contains counters for the operating hours and switching cycles; for monitoring
blocks it contains the simulation and substitute value.
Message view
The message view is the same for all block types. This section is therefore referenced in the
following document. The alarm screen displays the following information:
● Date
● Time
● Origin (plant designation of the process tag)
● User name, as configured
● Event (e.g., motor protection)
● Status (incoming/outgoing)
● Type (danger/malfunction/warning)
● Info text (if configured)
When the message view is selected for the process tag, only the relevant messages for this
process tag are displayed.
The alarm window corresponds to the S7 standard and can be operated as follows:
1
2
3
Trend view
The trend view is the same for all process tags. This section is therefore referenced in the
following document.
Only the number of trends may vary for different block types.
The trend view shows the analog values as a curve.
Example trend:
Batch view
The batch view is the same for all block types.
You can activate or deactivate the batch view by setting the internal WinCC variable
""@IL_BatchView". The variable is generated automatically in the OS project editor and located
in the Split Screen Manager group.
The "@S7_Trend.pdl" screen [screen size = 700 x 450] is the trend master for all faceplates.
The default setting of the process values for the faceplates (see descriptions of faceplates)
results in a time axis of 5 minutes being displayed.
Note
When archive values are used, all measured values must also be set up in the Process Value
Archive. Process values which do not exist in the archive are not shown.
S7Aggr08 - - -
S7Average ● Measured values Not used ● Suppression time
● Maximum value
● Mean value
● Minimum value
● Plausibility difference
S7CalcWatP ● Performance ● Energy ● Flow
● Performance limits ● Energy limits
S7HxFct ● Enthalpy ● Absolute humidity ● Relative humidity
● Saturated humidity
S7OpD - - -
● Deadband
● Control zone
● Control deviation
● Program value
S7UsrM - - -
S7Vlv - - -
S7VlvMot ● Manipulated variable (internal/ Not used ● Monitoring times
external/local)
● Readback value
● Manipulated variable
difference limits
● Readback value limits
● Manipulated variable
operating range
● Control deviation
● Tracking value
Attributes that do not exist on the block icon are marked with "-" in the table.
All relevant icons on the process control screen contain information that identifies the operator
station currently having switching authority. This information is also displayed in the faceplate.
See also
S7UsrM - Selection of operating level from 8 levels (Page 61)
Note
The enumeration linked to <Technological block>.PERMIS (default: OP_Conf1) is used
to display the current operator permission in the faceplate.
Note
You only need to use one DB for each controller that includes all IDB number entries of the
panel blocks used.
Core functionality
The S7 Industry Library of blocks contains matching interface blocks for some of your
technological blocks. The interface blocks are used to implement the data exchange between
the operator panel and operator station and to standardize the alarm logging. The interface
block also manages the operator authorization for the panel.
The interface blocks come with a library of preconfigured block icons and faceplates for
visualization on the operator panel.
Operating philosophy
All operator stations have two standard operating levels, 5 and 6.
An operator with operating level 5 "Process operations" can perform all switching operations,
which means all technological devices can be activated/deactivated or the operating mode
can be switched from manual to automatic and vice versa.
An operator with operating level 6 "Higher-level process operations" can change parameters
provided to the operator by a faceplate.
The operating philosophy implemented on the Operator Panel corresponds to operating level
5. Thus, it is not possible to change parameters on the OP or to set the equipment to "Out of
service".
Message behavior
The messages are generated by the technological block in the controller by calling the
Alarm_DQ and Alarm_SC functions. The operator station (OS) and operator panel (OP) receive
the messages and their states from the controller. The controller transmits the message
number and the corresponding message text to the HMI devices.
In addition, each panel block of the IL S7 has a WORD input as an alarm interface with which
bit messaging is implemented.
2SHUDWRU6WDWLRQ
$6
7HFKQRORJLFDO 3DQHOEORFN
EORFN
$ODUPB'46
2SHUDWRU3DQHO
In the message view of the operator panel, the message classes "S7 messages", "S7 controller
control system messages" and "S7 warning" are displayed. Note that messages of the
message class "S7 Process message" or "S7 Tolerance" are not displayed by the system
broken down by instances in the message view of the operator panel. Messages of these
message classes must be displayed by a separate message view in the operator panel project.
A filter is required to display messages broken down by instance in the message view of the
operator panel. The message is given a unique value to assign the messages on the panel to
an instance by means of filtering. This value consists of the instance DB number of the panel
function block and the value configured at the "AS_Nr" input of the panel block.
The filter value is written to the "Op_MsgFilter" I/O and transferred to the panel with the
message as message auxiliary value when the ALARM_DQ is generated. The message texts
are then filtered in the message view of the faceplate according to the value at the
"Op_MsgFilter" I/O of the associated panel block.
This means a value that is unique throughout the project must be configured at the input
"AS_Nr" for each AS in the project. Values between 1 and 999 are permitted at the "AS_Nr"
input.
Note
You can enable the associated value view using the EN_AUX input of the panel block. If
EN_AUX = 0, the view cannot be opened.
Message view
Note
Colors for message classes in the message window
The representation of the messages in the message window is made centrally in the TIA Portal
in the message settings of the message classes of the Panel.
So that the message texts can be configured in a readable color based on the message color,
each faceplate has the Message -> Alarm_TextColor attribute. Project-specific templates with
an appropriate message text color can thus be created.
The color is set to gray by default so that the text is readable for warnings, which are usually
yellow in PCS 7, as well as for black faults.
NOTICE
Associated values in the message texts of the panel blocks
The accompanying values at the end of the message texts (for example: (PUsrM: #@3X
%3u@)) must not be deleted or changed. These are required to correctly display the
messages in the message view on the panel. If these texts are adapted, this can cause
messages not to be displayed in the message view on the panel.
Access options
You can access the documentation as follows:
● On the Internet
– http://support.automation.siemens.com/WW/view/en/50708061 (http://
support.automation.siemens.com/WW/view/de/50708061)
3.1.1 Function
3.1.10 Cascading
QNOTACH info message:
Output bit when the required number of units could not be switched on. In addition, the missing
number is output at the QMISS output.
The messages can be locked centrally with MSG_LOCK (OS operation) or L_MSGLCK
(program).
SFC6 RD_SINFO
SFC20 BLKMOV
SFC107 ALARM_DQ
SFC19 ALARM_SC
Block I/Os
2
9
8 3
6
5
(1) Mode
Display and switchover of the operating mode This area provides information on the currently
valid operating mode. The following operating modes can be shown here:
● On
● Out of service
(2) Command
(3) Number of units
● Setpoint
● Quantity
(4) Master unit
● Setpoint
● Interval no.
(5) Message lock enabled
(6) Display area for block states
This area provides additional information on the operating state of the block:
● Master unit
(7) Display area for block states
This area provides additional information on the operating state of the block:
● LocalOS
(8)
● Units indicator:
– Green: Unit running + is available
– Dark green: Unit running + is not available
– White: Unit not running + is available
– Gray: Unit not running + is not available
● Time remaining until switchover of the master unit in the format dd hh:mm
– Gray characters: Time is running, but is not active (QTIME_S = 0)
– Black characters: Time is running + is active (QTIME_S = 1)
(9) Unit icon with number of active units:
● Green: Number of running units > 0
● Gray: Number of running units = 0
(1) Switchover
● Time remaining
(2)
● Req. units
● Missing units
● Max. units
● Master units
(3)
● Units 1 to 8
● available 1 to 8
● On 1 to 8
● Runtime 1 to 8
3.2.1 Function
3.2.5 Assignment of message text and message class to the block parameters
SFC6 RD_SINFO
SFC107 ALARM_DQ
SFC19 ALARM_SC
FC67 S7ASTIMEBCD
6 5
(1) LocalOS
(2) ControlCenterOS
(3) Operator panels
● Operator panels 1 to 2
(4) Operation level
● Operation levels 5 to 8
(5) Message lock enabled
(6) Display area for block states
This area provides additional information on the operating state of the block.
The currently selected operating level is defined for the entire project with an enumeration
type. The operating level determines which HMI devices can be used to control the unit. Levels
that are not available are grayed-out.
3.3.1 Function
SFC6 RD_SINFO
FB46 OP_A_LIM
UDT76 UDT_S7POpA
5 4
(2) LINK_ON
● On
● Off
(3) Output value
(4) Bumpless enabled
(5) Display area for block states
This area provides additional information on the operating state of the block.
● LocalOS
3.4.1 Function
SFC6 RD_SINFO
UDT75 UDT_S7POpD
4 1
(1) Command
● On
● Off
(2) Display area for block states
This area provides additional information on the operating state of the block.
● Off
(3) Display area for block states
This area provides additional information on the operating state of the block.
● LocalOS
(4) Status display
5 1
2
4
(1) On
(2) Pulse time in seconds
(3) Display area for block states
This area provides additional information on the operating state of the block:
● Off
(4) Display area for block states
This area provides additional information on the operating state of the block:
● LocalOS
(5) Status display
4.1.1 Function
A positive edge at the RESET or L_RESET input resets the value of QTH_ENGY to zero. On
restarting the CPU (in OB100), the value of STH_ENGY (Start Thermal Energy) is used as the
initial value to calculate the thermal energy QTH_ENGY.
Calculation of the thermal power
QTH_POW := ABS(V_FL_RT * KT * (T_FORERN – T_RETURN)).
Calculation of the emitted thermal energy (iteratively at the i-th block call after RESET or restart
of the CPU):
QTH_ENGY[i] := QTH_ENGY[i-1] + QTH_POW * (SAMPLE_T/3600.0).
The messages can be locked centrally with MSG_LOCK (OS operation) or L_MSGLCK
(program).
QMSG_SUP is set if the RUNUPCYC cycles have not finished running since the restart,
MSG_LOCK or L_MSGLCK = TRUE.
SFC107 ALARM_DQ
SFC19 ALARM_SC
UDTxx UDT_S7PCalcWatP
3
5
(1)
● Power
● Energy
(2) Start value energy
(3)
● Pre-run temp
● Return flow temp
● Flow
(4) Message lock enabled
(5) Display area for block states
This area provides additional information on the operating state of the block:
● Pre-run
● Heat
● LocalOS
4.2.1 Function
4.3.1 Function
4.4.1 Function
The messages can be locked centrally with MSG_LOCK (OS operation) or L_MSGLCK
(program).
QMSG_SUP is set if the RUNUPCYC cycles have not finished running since the restart or if
MSG_LOCK or L_MSGLCK = TRUE.
SFC6 RD_SINFO
SFC107 ALARM_DQ
SFC19 ALARM_SC
UDTxx UDT_S7PHxFct
4 3
(1)
● Enthalpy
● Absolute humidity
● Saturation humidity
● Wet bulb temperature
(2)
● Temperature
● Rel. humidity
(3) Message lock active
(4) Display area for block states
This area provides additional information on the operating state of the block:
● LocalOS
Note
The blocks for use in S7-300 and S7-1500 are identical in their function. The blocks are
supplied for CPU S7-300 for use in the SIMATIC Manager and for CPU S7-1500 for use in the
TIA Portal.
Note
Communication between redundant (S7-400H) and non-redundant (S7-300 / S7-1500 /
S7-400) stations
When communicating via the H blocks, the communication is only guaranteed for simple failure
(fault in Rack0 or Rack1) on the H system. If multiple failures occurs (fault in Rack0 and Rack1,
e.g. CPU in Rack0 is disturbed and CP in Rack1 is disrupted), communication is no longer
possible.
Used blocks
Single communication
H communication
1
Block is part of the APL
2
Block is part of the IL S7
3
Block is part of the IL PCS 7
S7-400 is configured in the SIMATIC Manager and CFC. S7-1500 is configured in the TIA
Portal. The blocks are optimized in the TIA Portal for the use of LAD, FBD or STL.
NOTICE
S7-400 is configured in the SIMATIC Manager and CFC. S7-1500 is configured in the TIA
Portal. The blocks are optimized in the TIA Portal for the use of LAD, FBD or STL.
The data limit for the data exchange is 64 KB per block pair. The transmission of the data via
a communication processor (CP) of the S7-300 is an exception with 32 KB. A maximum of
eight jobs can be executed in parallel for each S7 connection.
How it works
Sending is initiated by calling the block with the value 1 at the SendEn control input. During
the transmission of data, SendAct is set to 1.
If the job is completed without error, SendDone = 1 is set. SendErr is set to 1 is an error
occurs and new job is automatically triggered with the current data until all data have been
successfully sent.
If the input SendEn = 0, incomplete transmission is canceled. No further sending takes place
afterward (SendAct = 0).
The ID parameter is the connection number from the configuration of the S7 connection in
"NetPro" (PCS 7 / STEP 7) or "Devices and Networks" (TIA Portal).
The R_ID parameter is any number for each S7 connection (ID) that is unique and identical
at the corresponding send and receive blocks.
You can re-configure the addressing parameters ID and R_ID in runtime. The new
parameters take effect with each new job once the previous job is completed. You can find
additional information on these parameters in the system documentation for BSEND/BRCV.
Note
Error code or incorrect data at the data block
Only one Rcv block may be assigned to each Snd block. The combination of ID (connection
number) and R_ID (identification number) must be unique within the project for every block
pair.
Ensure that this assignment of the block pairs is correct, otherwise data will be sent to the
wrong blocks.
Configuration
Install the block in a cyclic interrupt OB (such as OB32) in the CFC Editor.
Startup characteristics
The block has no startup characteristics.
Time behavior
The block does not have any timing behavior.
Troubleshooting the block is restricted to the error information of the lower-level SFB 12
"BSEND".
The SendErr(ERROR) and SendStat(STATUS) outputs show the specific error information
for the lower-level SFB 12 "BSEND".
You can find the error information for the ERROR and STATUS outputs of the SFB 12 in the
manual "System Software for S7-300/400 - System and Standard Functions".
If an error occurs, a new job is automatically triggered with the current data until all data have
been successfully transferred.
Input parameters
Output parameters
How it works
Sending is initiated by calling the block with the value 1 at the SendEn control input. The data
are sent according to the settings of CycMin, CycMax or PV_In_HysXX. During the
transmission of data, SendAct is set to 1.
If the job is completed without error, SendDone = 1 is set. SendErr is set to 1 is an error
occurs and new job is automatically triggered with the current data until all data have been
successfully sent.
If the input SendEn = 0, incomplete transmission is canceled. No further sending takes place
afterward (SendAct = 0).
You can use CycMIN to set the number of cycles to wait before triggering the transfer of the
current input data, regardless of any changes to one or more values.
You can use CycMAX to specify how many cycles after the last valid data transfer to wait before
sending the current input data. Sending is executed even when no value has changed or when
the changes of a REAL value are within the hysteresis PV_In_HysXX.
The default value of the hysteresis is PV_In_HysXX = 0. If sending is not to be performed
after each value change, configure the PV_In_HysXX input accordingly. This involves an
absolute value.
When CycMax is reached, transfer is forced after the corresponding number of cycles.
The ID parameter is the connection number from the configuration of the S7 connection in
"NetPro" (PCS 7 / STEP 7) or "Devices and Networks" (TIA Portal).
The R_ID parameter is any number for each S7 connection (ID) that is unique and identical
at the corresponding send and receive blocks.
You can re-configure the addressing parameters ID and R_ID in runtime. The new
parameters take effect with each new job once the previous job is completed. You can find
additional information on these parameters in the system documentation for BSEND/BRCV.
Note
Error code or incorrect data at the data block
Only one Rcv block may be assigned to each Snd block. The combination of ID (connection
number) and R_ID (identification number) must be unique within the project for every block
pair.
Ensure that this assignment of the block pairs is correct, otherwise data will be sent to the
wrong blocks.
Configuration
Install the block in a cyclic interrupt OB (such as OB32) in the CFC Editor.
Startup characteristics
The block has no startup characteristics.
Time behavior
The block does not have any timing behavior.
Troubleshooting the block is restricted to the error information of the lower-level SFB 12
"BSEND".
The SendErr(ERROR) and SendStat(STATUS) outputs show the specific error information
for the lower-level SFB 12 "BSEND".
You can find the error information for the ERROR and STATUS outputs of the SFB 12 in the
manual "System Software for S7-300/400 - System and Standard Functions".
If an error occurs, a new job is automatically triggered with the current data until all data have
been successfully transferred.
Input parameters
Output parameters
How it works
Data are entered in the data block asynchronously to user-program execution. After
"S7RcvDig" has been called, instance DB data may not be processed as long as the job is in
progress (RcvNewData = 0). If the job is completed without errors, the RcvNewData output
is set to 1 for one cycle. In the next cycle, the receive enable is automatically sent by the FB
to the operating system of the CPU.
The receive enable can take effect prior to the arrival of the first receive job. In this case, the
receive enable is stored by the operating system.
The ID parameter is the connection number from the configuration of the S7 connection in
"NetPro" (PCS 7 / STEP 7) or "Devices and Networks" (TIA Portal).
The R_ID parameter is any number for each S7 connection (ID) that is unique and identical
at the corresponding send and receive blocks.
You can re-configure the addressing parameters ID and R_ID in runtime. The new
parameters take effect with each new job once the previous job is completed. You can find
additional information on these parameters in the system documentation for BSEND/BRCV.
Call the block pair consisting of the send (S7RcvDig) and receive block (Snd_DigVal) in each
program cycle (cyclically or also via timeout alarm).
Note
Error code or incorrect data at the data block
Only one Snd block may be assigned to each Rcv block. The combination of ID (connection
number) and R_ID (identification number) must be unique within the project for every block
pair.
Ensure that this assignment of the block pairs is correct, otherwise data will be sent to the
wrong blocks.
If you want to simulate the values, enable simulation via the SimOn input. In this case, the
values from the inputs SimPVX are written to the outputs PV_Outx. As long as simulation is
running, the data sent are not applied, since data reception is switched off.
Configuration
Install the block in a cyclic interrupt OB (such as OB32) in the CFC Editor.
Startup characteristics
The block has no startup characteristics.
Time behavior
The block does not have any timing behavior.
The following function is available at the Feature I/O for this block:
● Bit 29: Output substitute values if raw value is invalid
Troubleshooting the block is restricted to the error information of the lower-level SFB 13
"BRCV".
The SendErr (ERROR) and SendStat (STATUS) outputs show the specific error information
for the lower-level SFB 13 "BRCV".
You can find additional information in the manual System Software for S7-300/400 - System
and Standard Functions. There you can find a description for the RcvXErr (ERR) and
RcvXStat (STAT) outputs of SFB 13.
If Bit29 in the Feature structure is set, and no new data is received after the expiration of
RcvMonCyc (number of cycles), the substitute value is output and the RcvMonErr output is
set to 1. While RcvMonCyc cycles are running, the last received values are applied to the
output.
If Bit29 in the Feature structure is not set and an error occurs, the last valid values are always
applied to the output.
Input parameters
Output parameters
How it works
Data are entered in the data block asynchronously to user-program execution. After
"S7RcvAna" has been called, instance DB data may not be processed as long as the job is in
progress (RcvNewData = 0). If the job is completed without errors, the RcvNewData output
is set to 1 for one cycle. In the next cycle, the receive enable is automatically sent by the FB
to the operating system of the CPU.
The receive enable can take effect prior to the arrival of the first receive job. In this case, the
receive enable is stored by the operating system.
The ID parameter is the connection number from the configuration of the S7 connection in
"NetPro" (PCS 7 / STEP 7) or "Devices and Networks" (TIA Portal).
The R_ID parameter is any number for each S7 connection (ID) that is unique and identical
at the corresponding send and receive blocks.
You can re-configure the addressing parameters ID and R_ID in runtime. The new
parameters take effect with each new job once the previous job is completed. You can find
additional information on these parameters in the system documentation for BSEND/BRCV.
Call the block pair consisting of the send (S7RcvAna) and receive block (Snd_AnaVal) in each
program cycle (cyclically or also via timeout alarm).
Note
Error code or incorrect data at the data block
Only one Snd block may be assigned to each Rcv block. The combination of ID (connection
number) and R_ID (identification number) must be unique within the project for every block
pair.
Ensure that this assignment of the block pairs is correct, otherwise data will be sent to the
wrong blocks.
If you want to simulate the values, enable simulation via the SimOn input. In this case, the
values from the inputs SimPVX are written to the outputs PV_Outx. As long as simulation is
running, the data sent are not applied, since data reception is switched off.
Configuration
Install the block in a cyclic interrupt OB (such as OB32) in the CFC Editor.
Startup characteristics
The block has no startup characteristics.
Time behavior
The block does not have any timing behavior.
Troubleshooting the block is restricted to the error information of the lower-level SFB 13
"BRCV".
The SendErr (ERROR) and SendStat (STATUS) outputs show the specific error information
for the lower-level SFB 13 "BRCV".
You can find additional information in the manual System Software for S7-300/400 - System
and Standard Functions. There you can find a description for the RcvXErr (ERR) and
RcvXStat (STAT) outputs of SFB 13.
If Bit29 in the Feature structure is set, and no new data is received after the expiration of
RcvMonCyc (number of cycles), the substitute value is output and the RcvMonErr output is
set to 1. While RcvMonCyc cycles are running, the last received values are applied to the
output.
If Bit29 in the Feature structure is not set and an error occurs, the last valid values are always
applied to the output.
Input parameters
Output parameters
How it works
Sending is initiated by calling the block with the value 1 at the SendEn control input. During
the transmission of data, SendXAct is set to 1.
If the job is completed without error, SendXDone = 1 is set. SendXErr is set to 1 is an error
occurs and new job is automatically triggered with the current data until all data have been
successfully sent.
If the input SendEn = 0, incomplete transmission is canceled. No further sending takes place
afterward (SendXAct = 0).
The IDX parameter is the connection number from the configuration of the S7 connection in
"NetPro" (PCS 7 / STEP 7) or "Devices and Networks" (TIA Portal).
The R_IDX parameter is any number for each S7 connection (IDX) that is unique and identical
at the corresponding send and receive blocks.
You can re-configure the addressing parameters IDX and R_IDX in runtime. The new
parameters take effect with each new job once the previous job is completed. You can find
additional information on these parameters in the system documentation for BSEND/BRCV.
Note
Error code or incorrect data at the data block
Only one Rcv block may be assigned to each Snd block. The combination of ID (connection
number) and R_ID (identification number) must be unique within the project for every block
pair.
Ensure that this assignment of the block pairs is correct, otherwise data will be sent to the
wrong blocks.
Configuration
Install the block in a cyclic interrupt OB (such as OB32) in the CFC Editor.
Startup characteristics
The block has no startup characteristics.
Time behavior
The block does not have any timing behavior.
Troubleshooting the block is restricted to the error information of the lower-level SFB 12
"BSEND".
The SendErr(ERROR) and SendStat(STATUS) outputs show the specific error information
for the lower-level SFB 12 "BSEND".
You can find the error information for the ERROR and STATUS outputs of the SFB 12 in the
manual "System Software for S7-300/400 - System and Standard Functions".
If an error occurs, a new job is automatically triggered with the current data until all data have
been successfully transferred.
Input parameters
Output parameters
How it works
Sending is initiated by calling the block with the value 1 at the SendEn control input. The data
are sent according to the settings of CycMin, CycMax or PV_In_HysXX. During the
transmission of data, SendXAct is set to 1.
If the job is completed without error, SendXDone = 1 is set. SendXErr is set to 1 is an error
occurs and new job is automatically triggered with the current data until all data have been
successfully sent.
If the input SendEn = 0, incomplete transmission is canceled. No further sending takes place
afterward (SendXAct = 0).
You can use CycMIN to set the number of cycles to wait before triggering the transfer of the
current input data, regardless of any changes to one or more values.
You can use CycMAX to specify how many cycles after the last valid data transfer to wait before
sending the current input data. Sending is executed even when no value has changed or when
the changes of a REAL value are within the hysteresis PV_In_HysXX.
The default value of the hysteresis is PV_In_HysXX = 0. If sending is not to be performed
after each value change, configure the PV_In_HysXX input accordingly. This involves an
absolute value.
When CycMax is reached, transfer is forced after the corresponding number of cycles.
The IDX parameter is the connection number from the configuration of the S7 connection in
"NetPro" (PCS 7 / STEP 7) or "Devices and Networks" (TIA Portal).
The R_IDX parameter is any number for each S7 connection (IDX) that is unique and identical
at the corresponding send and receive blocks.
You can re-configure the addressing parameters IDX and R_IDX in runtime. The new
parameters take effect with each new job once the previous job is completed. You can find
additional information on these parameters in the system documentation for BSEND/BRCV.
Note
Error code or incorrect data at the data block
Only one Rcv block may be assigned to each Snd block. The combination of ID (connection
number) and R_ID (identification number) must be unique within the project for every block
pair.
Ensure that this assignment of the block pairs is correct, otherwise data will be sent to the
wrong blocks.
Configuration
Install the block in a cyclic interrupt OB (such as OB32) in the CFC Editor.
Startup characteristics
The block has no startup characteristics.
Time behavior
The block does not have any timing behavior.
Troubleshooting the block is restricted to the error information of the lower-level SFB 12
"BSEND".
The SendErr(ERROR) and SendStat(STATUS) outputs show the specific error information
for the lower-level SFB 12 "BSEND".
You can find the error information for the ERROR and STATUS outputs of the SFB 12 in the
manual "System Software for S7-300/400 - System and Standard Functions".
If an error occurs, a new job is automatically triggered with the current data until all data have
been successfully transferred.
Input parameters
Output parameters
How it works
Data are entered in the data block asynchronously to user-program execution. After
"S7RcvHDig" has been called, instance DB data may not be processed as long as the job is
in progress (RcvXNewData = 0). If the job is completed without errors, the RcvXNewData
output is set to 1 for one cycle. In the next cycle, the receive enable is automatically sent by
the FB to the operating system of the CPU.
The receive enable can take effect prior to the arrival of the first receive job. In this case, the
receive enable is stored by the operating system.
The IDX parameter is the connection number from the configuration of the S7 connection in
"NetPro" (PCS 7 / STEP 7) or "Devices and Networks" (TIA Portal).
The R_IDX parameter is any number for each S7 connection (IDX) that is unique and identical
at the corresponding send and receive blocks.
You can re-configure the addressing parameters IDX and R_IDX in runtime. The new
parameters take effect with each new job once the previous job is completed. You can find
additional information on these parameters in the system documentation for BSEND/BRCV.
Call the block pair consisting of the send (S7RcvHDig) and receive block (SndH_DigVal) in
each program cycle (cyclically or also via timeout alarm).
Note
Error code or incorrect data at the data block
Only one Snd block may be assigned to each Rcv block. The combination of ID (connection
number) and R_ID (identification number) must be unique within the project for every block
pair.
Ensure that this assignment of the block pairs is correct, otherwise data will be sent to the
wrong blocks.
If you want to simulate the values, enable simulation via the SimOn input. In this case, the
values from the inputs SimPVX are written to the outputs PV_OutX. As long as simulation is
running, the data sent are not applied, since data reception is switched off.
Configuration
Install the block in a cyclic interrupt OB (such as OB32) in the CFC Editor.
Startup characteristics
The block has no startup characteristics.
Time behavior
The block does not have any timing behavior.
The following function is available at the Feature I/O for this block:
● Bit 29: Output substitute values if raw value is invalid
Troubleshooting the block is restricted to the error information of the lower-level SFB 13
"BRCV".
The SendErr (ERROR) and SendStat (STATUS) outputs show the specific error information
for the lower-level SFB 13 "BRCV".
You can find additional information in the manual System Software for S7-300/400 - System
and Standard Functions. There you can find a description for the RcvXErr (ERR) and
RcvXStat (STAT) outputs of SFB 13.
If Bit29 in the Feature structure is set, and no new data is received after the expiration of
RcvMonCyc (number of cycles), the substitute value is output and the RcvMonErr output is
set to 1. While RcvMonCyc cycles are running, the last received values are applied to the
output.
If Bit29 in the Feature structure is not set and an error occurs, the last valid values are always
applied to the output.
Input parameters
Output parameters
How it works
Data are entered in the data block asynchronously to user-program execution. After
"S7RcvHAna" has been called, instance DB data may not be processed as long as the job is
in progress (RcvXNewData = 0). If the job is completed without errors, the RcvXNewData
output is set to 1 for one cycle. In the next cycle, the receive enable is automatically sent by
the FB to the operating system of the CPU.
The receive enable can take effect prior to the arrival of the first receive job. In this case, the
receive enable is stored by the operating system.
The IDX parameter is the connection number from the configuration of the S7 connection in
"NetPro" (PCS 7 / STEP 7) or "Devices and Networks" (TIA Portal).
The R_IDX parameter is any number for each S7 connection (IDX) that is unique and identical
at the corresponding send and receive blocks.
You can re-configure the addressing parameters IDX and R_IDX in runtime. The new
parameters take effect with each new job once the previous job is completed. You can find
additional information on these parameters in the system documentation for BSEND/BRCV.
Call the block pair consisting of the send (S7RcvHAna) and receive block (SndH_AnaVal) in
each program cycle (cyclically or also via timeout alarm).
Note
Error code or incorrect data at the data block
Only one Snd block may be assigned to each Rcv block. The combination of ID (connection
number) and R_ID (identification number) must be unique within the project for every block
pair.
Ensure that this assignment of the block pairs is correct, otherwise data will be sent to the
wrong blocks.
If you want to simulate the values, enable simulation via the SimOn input. In this case, the
values from the inputs SimPVX are written to the outputs PV_OutX. As long as simulation is
running, the data sent are not applied, since data reception is switched off.
Configuration
Install the block in a cyclic interrupt OB (such as OB32) in the CFC Editor.
Startup characteristics
The block has no startup characteristics.
Time behavior
The block does not have any timing behavior.
Troubleshooting the block is restricted to the error information of the lower-level SFB 13
"BRCV".
The SendErr (ERROR) and SendStat (STATUS) outputs show the specific error information
for the lower-level SFB 13 "BRCV".
You can find additional information in the manual System Software for S7-300/400 - System
and Standard Functions. There you can find a description for the RcvXErr (ERR) and
RcvXStat (STAT) outputs of SFB 13.
If Bit29 in the Feature structure is set, and no new data is received after the expiration of
RcvMonCyc (number of cycles), the substitute value is output and the RcvMonErr output is
set to 1. While RcvMonCyc cycles are running, the last received values are applied to the
output.
If Bit29 in the Feature structure is not set and an error occurs, the last valid values are always
applied to the output.
Input parameters
Output parameters
5.10.1 Function
The ASRcvH block coordinates the receipt of telegrams between a redundant and a non-
redundant automation station via S7 communication (BRECV). Up to 30 REAL values and 30
binary values are sent. Each value also has a binary quality code which specifies whether the
measured value is correct.
Messages
The associated values (ExtVa1x) of the message block can be assigned freely.
SFC6 RD_SINFO
SFB35 ALARM_8P
FB1152 IL_BR
UDT1190 UDT_BoolSt
UDT1191 UDT_RealSt
5.11.1 Function
Messages
The associated values (ExtVa1x) of the message block can be assigned freely.
SFC6 RD_SINFO
SFB35 ALARM_8P
FB1151 IL_BS
UDT1190 UDT_BoolSt
UDT1190 UDT_RealSt
5.12.1 Function
Note
The block is designed for use in S7-4xx CPUs.
During communication between S7-4xx and S7-3xx, up to 222 bytes can be read from a DB.
During communication between S7-4xx and S7-15xx, up to 222 bytes can be read from a DB.
Configuration
The S7Get block requires the following information at its I/Os in order to read data from an S7
controller:
I/O Information
KOM_ID Local ID of the S7 connection from NetPro. This
ID is shown as HEX in NetPro. Note the following
when entering at the block:
DBNO_SRC DB number of the data block containing the data
to be read in S7-3xx/S7-15xx.
ADDR_SRC Start address of the area of the data to be read
within the data block in the S7-3xx/S7-15xx .
DBNO_DST DB number of the data block where the read data
is to be stored.
ADDR_DST Start address at which the read data is to be stored
in the data block.
LENGTH Length of data to be read in BYTES
The block starts writing the data as soon as the input is START = true.
It reads the data from the address defined at the I/Os DBNO_SRC.ADDR_SRC, for the area that
was set with the I/O LENGTH and writes it to the position that was defined with the I/Os
DBNO_DST.ADDR_DST.
As long as the input START = true, the read operation is performed at each block call.
Sign-of-life monitoring
● EN_LIFE = true
Sign-of-life monitoring is active.
A Lifebit is configured in the target station (S7-300/ S7-1500), which is interconnected to the
connector LIFE_BIT. If there is no status change within the time configured at the connector
MONITOR, the output QERR switches to true. When the suppression time configured at the
connector SUPPTIME expires, a message is triggered if it is not otherwise suppressed by
L_MSGLCK.
● EN_LIFE = false
Sign-of-life monitoring is not active
The monitoring to determine if communication with the target station is possible is done via
the functions of the SFC GET and the connection monitoring of the S7-400. The configuration
of the communications interface determines when the message is triggered.
SFC6 RD_SINFO
SFB14 GET
SFC107 ALARM_DQ
SFC19 ALARM_SC
5.13.1 Function
Note
The block is designed for use in S7-4xx CPUs.
During communication between S7-4xx and S7-3xx, up to 212 bytes can be written to a DB.
During communication between S7-4xx and S7-15xx, up to 212 bytes can be written to a DB.
Configuration
The S7Put block requires the following information at its I/Os in order to write data to an S7
controller:
I/O Information
KOM_ID Local ID of the S7 connection from NetPro. This
ID is shown as HEX in NetPro. Note the following
when entering at the block:
DBNO_SRC DB number of the data block containing the data
to be sent.
ADDR_SRC Start address of the area of the data to be sent
within the data block.
DBNO_DST DB number of the data block in which the data to
be sent should be stored in the S7-3xx/S7-15xx.
ADDR_DST Start address at which data to be sent should be
stored in the data block in the S7-3xx/S7-15xx.
LENGTH Length of data to be transferred in BYTES
The block starts writing the data as soon as the input is START = true.
The block then reads the data from the address defined at the I/Os DBNO_SRC.ADDR_SRC, for
which the area was set with the I/O LENGTH and writes it to the position that was defined with
the I/Os DBNO_DST.ADDR_DST target system was defined.
As long as the input START = true, the write operation is performed at each block call.
Sign-of-life monitoring
● EN_LIFE = true
Sign-of-life monitoring is active.
A Lifebit is configured in the target station (S7-300/ S7-1500), which is interconnected to the
connector LIFE_BIT. If there is no status change within the time configured at the connector
MONITOR, the output QERR switches to true. When the suppression time configured at the
connector SUPPTIME expires, a message is triggered if it is not otherwise suppressed by
L_MSGLCK.
● EN_LIFE = false
Sign-of-life monitoring is not active
The monitoring to determine if communication with the target station is possible is done via
the functions of the SFC PUT and the connection monitoring of the S7-400. The configuration
of the communications interface determines when the message is triggered.
The QERR output and the message are output delayed by the time "SUPPTIME". If
communication is "OK" and the time "SUPPTIME" has expired, the output and the message
change to the OK state.
SFC6 RD_SINFO
SFB15 PUT
SFC107 ALARM_DQ
SFC19 ALARM_SC
6.1.1 Function
6.2.1 Function
6.3.1 Function
7.1.1 Function
7.1.6 Integrate
The measured value (MODE=0:=PV; MODE=1:=PULSE) is accumulated in two counter
registers:
● QACCU_1
● QACCU_2.
The following parameters must be configured for this:
MODE = 0
The measured value is transferred at the PV input. The ACCU_T parameter specifies the
integration sampling cycles in seconds.
The PV measured value is weighted at the BASE_PV parameter. It is essential to ensure that
the ACCU_T and BASE_PV parameters have the same unit (e.g., BASE_PV = 3600 must be
specified for a measured value with the unit m³/h and an ACCU_T of 1 second).
A deadband can be configured at the DEADB parameter. When PV < DEADB, the deadband
is not included in the integration. In this case, the BASE_PU parameter is not relevant. The
measured value is calculated with the following formula:
QACCU_1 := QACCU_1 + PV*SW*ACCU_T/BASE_PV
MODE = 1
The measured value is transferred to the PULSE input as a pulse.
The pulse is weighted at the BASE_PU parameter. In this case, the BASE_PV, ACCU_T
parameter is not relevant.
Reset counter
The counter states are reset via the faceplate and via the interconnectable inputs L_RESET1/
L_RESET2.
The DATE_AC1/DATE_AC2 parameters each specify the time stamp for the reset operations
in the format [yy/mm/dd_hh].
SFC6 RD_SINFO
SFC67 S7ASTIMEBCD
5 4
(1) Counter 1
● Total 1
(2) Reset
(3) Counter 2
● Total 2
(4) Reset
(5) LocalOS
7.2.1 Function
Only the values which are used, enabled, and not faulty are checked for plausibility. Values
that are not used or have not been enabled are always identified as plausible. All measured
values are also marked as plausible if the plausibility check has been deselected with
PL_CH_EN = FALSE.
If one or several measured values are not plausible following generation of the mean value,
the value which deviates the most is initially marked as implausible. A new mean value is
determined without the implausible values and the plausibility of the remaining measured
values is checked again. When only two measured values are left to generate the mean value,
they are only considered plausible if the difference between both measured values is less than
the plausibility difference (PL_DIFF). If both values are implausible, mean value, minimum
value, and maximum value are generated from the two (implausible) values and output until
the message has been sent to WinCC. The values which were valid last are then output.
The maximum (QMAX) and the minimum (QMIN) are determined from all valid (used, enabled,
not faulty, and plausible) values.
If no used, enabled, and intact measured values are available or the two remaining values are
implausible, the values which were valid last are output at outputs V, QMIN, and QMAX. The
QERR output is also set.
If only one measured value is used, enabled, and intact, the value is considered plausible and
generates the mean, maximum, and minimum values.
The messages can be locked centrally with MSG_LOCK (OS operation) or L_MSGLCK
(program).
QMSG_SUP is set if the RUNUPCYC cycles have not finished running since the restart,
MSG_LOCK or L_MSGLCK = TRUE.
Initialization Meaning
V=0 Mean value = 0
QERR = 0 At least one measured value is used, enabled, and not faulty.
QUx_STAT = 0 All values connected, enabled, correct, and plausible
A manual new start is triggered as long as the RESTART input is set to TRUE.
SFC6 RD_SINFO
SFC107 ALARM_DQ
SFC19 ALARM_SC
Block I/Os
(1) LocalOS
(2) Displays for activity, measured values, units, and temperatures
● You can enable or disable the activity of each line by selecting or deselecting the check
box.
● The colored lines indicate the following states:
– Green = OK
– Red = Faulty
– Gray = Disabled
(3) Message lock enabled
(1) Plausibility
● Plausibility difference
● Suppression time
● Plausibility check
The inputs for switching the motor on and off in manual operating mode are called manual
control inputs. These inputs are listed below.
The inputs for switching the motor on and off in local mode with LOCAL_S = 1 are called local
control inputs. These inputs are listed below.
The outputs for controlling the motor are called control outputs. These outputs are listed below:
The inputs which report the current motor state to the block are called response message
inputs. These inputs are listed below.
The motor blocks have the following inputs for parameterization of the monitoring times:
8.1.2 Function
The function of the blocks is similar to that of the S7 standard block MOTOR. The S7 standard
block has been expanded with the addition of a number of functions for water and wastewater
applications. Functions that are not required have been removed.
The motor is controlled by the block with the control outputs. One or more run feedback
messages (for ON, OFF, or the current speed) can be monitored if desired. The feedback
messages are provided by an auxiliary contactor.
Note
Most of the functions described above can be enabled and disabled using inputs.
The allocation of priorities to individual input variables and influence on the control signals is
shown in the following table. The sections following provide further details.
Priority: Influence:
High REMOTE = 0
Motor protection error, if MSS_OFF = 1
LOCK = 1 / REPAIR = 1
LOCK_ON = 1
Monitoring error, if FAULT_OFF = 1
Low Automatic/Manual mode
No effect Motor protection error, if MSS_OFF = 0
Monitoring error, if FAULT_OFF = 0
Control system fault, operator error
Local mode
You can enable local operation by setting the REMOTE input to "0". You can set the mode for
local operation with the LOCAL_S mode variable (BOOL type).
The current manual or automatic command is output on switching back from local operation
to remote operation.
LOCAL_S = 0 1
Enable local operation CFC/SFC CFC/SFC
Operation in the faceplate Not possible Not possible
Tracking via an external input No Yes
Reaction of the block Adjustment of the feed‐ Monitoring of the feed‐
back value back value
Interlock activated No Yes
Behavior at LOCAL_S = 0
● The control settings for the block are made based on internal adjustment of the feedback
value.
● The configured runtime monitoring of the block is deactivated.
● The configured interlock functions of the block are disabled.
In local operation and with MONITOR = 0, QRUN and QSTOP are set to 0.
Behavior at LOCAL_S = 1
● The control of the block is tracked by a connected input parameter (LOCAL_ON, for
example). The interconnected input parameter includes the control signal for the local
operator station on the system.
● The runtime monitoring of the block is effective in accordance with your configuration.
● The parameterized locking functionalities of the block are activated.
Manual mode
Operator control is performed with the manual control inputs MAN_ON (S7MotSpd: S1_ON,
S2_O) and MOT_OFF via the OS system if the applicable enables ON_OP_EN and
OFF_OP_EN (S7MotSpd: S1_OP_EN, S2_OP_EN and OFF_OP_EN) exist.
Automatic mode
An automatic unit outputs the control commands via the interconnected input AUTO_ON.
The following flowchart illustrates the various operating modes. The block inputs via which the
block receives its control commands in the particular operating mode are shown in
parentheses.
8.1.7 Interlock
The interlock function takes priority over all other control signals and errors - with the exception
of the motor circuit breaker when the corresponding enable signal is set (MSS_OFF = 1).
When LOCK or LOCK_ON is set, the motor is switched on and off directly (without considering
the time MIN_CMD). LOCK has the higher priority.
When the repair switch is off (REPAIR = 1), the motor is also switched off directly.
8.1.8 Control
The motor is activated with the applicable control outputs (S7MotSpdC and S7Mot: QON,
QOFF or S7MotSpd: QS1, QS2 and QOFF or S7MotRev: QREV, QFORW and QOFF). The
control output remains set until a new command is output.
During the switching time (setting of the control output until the required state of the response
message inputs is reported), the QRUN and QSTOP outputs are set to 0. When runtime
monitoring (MONITOR = 0) is deselected, the QRUN and QSTOP outputs are set together
with the control outputs. There are exceptions here for S7MotSpd and S7MotRev.
The input MIN_CMD contains the minimum time which must pass before the control outputs
output another command to the motor.
Example
When the motor is switched on with the control outputs, the time MIN_CMD must pass
measured starting from the feedback indicating that the motor is running (QRUN = 1) before
a command is output to switch off the motor. The same applies to the switching off or switching
over of the motor S7MotSpd from speed 1 to speed 2 and switching S7MotRev from motor on
in reverse to motor on in forward. The operator control enable is disabled for the manual inputs
until the MIN_CMD time has expired.
When MSUP_TMR <> 0, the output QM_SUP is set to 1 for motor off. When the motor is
switched on, QM_SUP is not reset to 0 until the time MSUP_TMR expires. When MSUP_TMR
= 0, QM_SUP always remains set to 0.
The output QM_SUP can be used to hide runtime monitoring. If, for example, a 'Flow-Switch’
reports flow while the pump is running, the output QM_SUP can be used to prevent this
message from being generated when the motor is at standstill.
The messages can be locked centrally with MSG_LOCK (OS operation) or L_MSGLCK
(program).
QMSG_SUP is set if the RUNUPCYC cycles have not finished running since the restart, or if
MSG_LOCK or L_MSGLCK = TRUE.
8.1.15 Availability
When motor control is possible in automatic mode, the output QAVAIL is set to TRUE. This is
the case under the following conditions.
● No local mode (QLOCAL = FALSE)
● No wait mode (QREPAIR = FALSE)
● Automatic mode (QMAN_AUT = TRUE)
● No interlock (LOCK = FALSE, LOCK_ON = FALSE)
● No external faults (QCSF = FALSE)
● Motor circuit breaker not tripped (QMST_ST = FALSE
● No runtime monitoring errors (QMON_ERR = FALSE)
Parameter Meaning
RUNTIME/QRUNTIME Number of operating hours since the last motor start
RUNTOTAL/QRUNTOTAL Number of operating days since the last total reset
STOPTIME/QSTOPTIME Number of hours in standstill since the last motor stop
STARTCYC/QSTARTCYC Number of start cycles since the last total reset
QPM_MSG = 1, if
RUNTOTAL/QRUNTOTAL > MAX_RUNTIME or
STARTCYC/QSTARTCYC > MAX_STARTCYC
The parameters can be reset with edge-triggered reset of the inputs to zero. The AS time is
written to the relevant input (DATE_TMR and DATE_TOT) as the time stamp for the reset.
Note
The AS time can differ from the OS- time.
SFC6 RD_SINFO
SFC107 ALARM_DQ
SFC19 ALARM_SC
FC67 S7ASTimeBCD
8.2.1 Function
Priority: Event:
High V_LOCK = 1
VL_CLOSE = 1
c VL_OPEN = 1
Monitoring error, if FAULT_SS = 1
Priority: Event:
Low Automatic/Manual mode
No effect Monitoring error, if FAULT_SS = 0
Control system fault, operator error
Local operation
You can enable local operation by setting the REMOTE input to "0". You can set the mode for
local operation with the LOCAL_S mode variable (BOOL type).
The current manual or automatic command is output on switching back from local operation
to remote operation.
LOCAL_S = 0 1
Enable local operation CFC/SFC CFC/SFC
Operation in the faceplate Not possible Not possible
Tracking via an external input No Yes
Reaction of the block Adjustment of the feedback Monitoring of the feedback
value value
Interlock activated No Yes
Behavior at LOCAL_S = 0
● The control settings for the block are made based on internal adjustment of the feedback
value.
● The configured runtime monitoring of the block is deactivated.
● The configured interlock functions of the block are disabled.
In local mode with LOCAL_S=0, the current status of the valve is displayed on the OS if
feedback is available (MONITOR = TRUE; NO_FB_xx, NOMON_xx = FALSE).
Behavior at LOCAL_S = 1
● The control of the block is tracked by a connected input parameter (LOCAL_OP, for
example). The interconnected input parameter includes the control signal for the local
operator station on the system.
● The runtime monitoring of the block is effective in accordance with your configuration.
● The parameterized locking functionalities of the block are activated.
Manual mode
Input MAN_OC is controlled via the OS. Enables (OP_OP_EN or CL_OP_EN) must be
available in order for operation to proceed.
Automatic mode
The control command is obtained via the input AUTO_OC (1: open, 0: close).
The connection must be made by means of interconnection to an automatic system.
8.2.7 Interlock
The interlock function takes priority over all other control signals and errors. When V_LOCK
is set, the valve is placed in its neutral position. If V_LOCK is not set, a locking state (open/
closed) can also be selected directly via the inputs VL_OPEN and VL_CLOSE. The VL_CLOSE
signal locks VL_OPEN.
8.2.8 Monitoring
Monitoring logic is used to check correspondence between the control command output
QOPEN or QCLOSE and the feedback of the actual state of the valve (FB_OPEN, FB_CLOSE).
If the end position has not been reached after the monitoring time TIME_MON has expired or
if the feedback changes without reason, the output QMON_ERR is set. Setting the FAULT_SS
input restores the valve to the zero energy neutral position. If the FAULT_SS command is not
set, the command predefined by AUTO_OC or MAN_OC remains pending at outputs QOPEN /
QCLOSE. If no limit feedback signal is connected, a MONITOR = 0 signal must be output to
the monitoring function, which then assumes that the limit of the valve has been reached within
the time TIME_MON. Until the time TIME_MON has expired, QOPENING or QCLOSING is
displayed. In error-free monitoring mode, the outputs QOPENING or QCLOSING show the
valve opening/closing. The outputs QCLOSED and QOPENED show whether or not the valve
has reached the end position.
The inputs NO_FB_xx and NOMON_xx are used to parameterize whether no feedback is
available for the states "open" or "closed" (NO_FB_xx=1) or the available feedback (e.g., due
to failure of the end position switch) is not to be evaluated (NOMON_xx=1).
The FAULT_SS parameter defines the relevance of the monitoring error. If FAULT_SS = 1,
the valve is set to its neutral position (defined by SS_POS) in the event of an error.
FAULT_SS = 0 has no effect on the control outputs.
This type must be assigned to the "S7UsrM" blocks of the units and all [PERMIS] inputs of the
technological blocks, as well as to the OP interface block "S7PVlv".
Example
Select the units within the "Process object view", filter by "I/O Name" "*PERMIS" and assign
the corresponding type to all "enumerations".
8.2.14 Availability
When valve control is possible in automatic mode, the output QAVAIL is set to TRUE. This is
the case under the following conditions:
● No local mode (QLOCAL = FALSE)
● No startup
● Automatic mode (QMAN_AUT = TRUE)
● No interlock (V_LOCK = FALSE, VL_OPEN = FALSE, VL_CLOSE=FALSE)
● No external faults (QCSF = FALSE)
● No runtime monitoring errors (QMON_ERR = FALSE)
SFC6 RD_SINFO
SFC107 ALARM_DQ
SFC19 ALARM_SC
UDT64 UDT_S7PVlv (UDT_OP_SVALVE)
Block I/Os
9 2
7 4
8.3.1 Function
8.3.3 Feedback
S7Mot has the feedback input FB_ON.
Parameter Effect
FB_ON = 1 Motor running
FB_ON = 0 Motor stopped
UDT62 UDT_S7PMot
6
2
5
This area provides additional information on the operating state of the block:
● Fault
(4) Display area for block states
This area provides additional information on the operating state of the block:
● Remote
● Local
(5) Display area for block states
This area provides additional information on the operating state of the block:
● Fault
● No connection
● Stop
● Start
● -> Start (Motor starting)
● -> Stop (Motor stopping)
● Forced start
● Forced stop
(6) Display area for block states
This area displays the active operating level of the block.
(7) Status display of motor
The current status of the motor is graphically displayed here:
● Green: Motor running
● Gray: Motor idle
● Red: A fault has occurred
8.4.1 Function
8.4.3 Feedback
S7MotRev has the feedback inputs FB_ON_REV and FB_ON_FORW. When the motor is
running in reverse, FB_ON_REV = 1 is set; when the motor is running in forward,
FB_ON_FORW = 1 is set. If no feedback inputs are set, the motor will be at standstill. If both
feedback inputs are set, there will be no valid feedback.
8.4.5 Control
The motor can be started in forward or reverse. When the motor is started in one direction,
changing direction is only possible once the time (MIN_CMD) has expired. Changing direction
is only possible via stop.
During the transition from forward to reverse, the QRUN output remains set to 1. The QRUN
output also remains set to 1 during the transition from reverse to forward (including when the
motor is switched off).
Manual mode
In manual mode, the block is started in reverse and forward with the REV_ON or FORW_SON
input; it is switched off with MOT_OFF. If one input is set, the other two are automatically reset
by the block.
Automatic mode
Starting and stopping the motor takes place in automatic mode with the AUTO_ON input. If
input AUTO_SPD = 0, the motor starts in forward. If AUTO_SPD = 1, the motor also starts in
forward and then switches to reverse once forward operation has been established.
Forced ON (LOCK_ON)
The direction is specified via the LOCK_SPD input.
UDT74 UDT_S7PMotRev
Block I/Os
6
2
5
8.5.1 Function
8.5.3 Feedback
S7MotSpd has the feedback inputs FB_ON_1 and FB_ON_2. When the motor is running at
speed 1, FB_ON_1 is set to 1. When the motor is running at speed 2, FB_ON_2 is set to 1. If
no feedback inputs are set, the motor will be at standstill. If both feedback inputs are set, there
will be no valid feedback.
8.5.5 Control
The motor can be started at the speeds 1 and 2. For starting at speed 2, the motor is first
started at speed 1. The motor is not started at speed 2 until speed 1 has been reached and
the time between two control commands (MIN_CMD) has elapsed. It is possible to switch a
motor running at speed 1 directly to speed 2. If a motor running at speed 2 is to be decelerated
to speed 1, the motor is first switched off and then started again at speed 1.
During the transition from speed 1 to speed 2, the output QRUN remains set to 1. During the
transition from speed 2 to speed 1, QRUN also remains set to 1 (including when the motor is
switched off).
Manual mode
In manual mode, the block is started and switched off at speeds 1 and 2 with the SP1_ON,
SP2_ON, and MOT_OFF inputs. When one input is set, the other two are automatically reset
by the block.
Automatic mode
Starting and stopping the motor takes place in automatic mode with the AUTO_ON input. If
input AUTO_SPD = 0, the motor starts at speed 1. If input AUTO_SPD = 1, the motor also
starts at speed 1 and increases to speed 2 once this has been reached.
Forced on (LOCK_ON):
The speed is specified via the LOCK_SPD input.
UDT63 UDT_S7PMotSpd
Block I/Os
6
2
5
8.6.1 Function
8.6.3 Feedback
S7MotSpdC has two separate inputs for the evaluation of feedback from the motor. When the
motor is running, FB_ON is set to 1. When the motor is at standstill, FB_ON is set to 0. If neither
of the two inputs or both inputs are set, valid feedback will not be recognized.
The feedback input for the actual speed of S7MotSpdC (SPEED_FB) is always evaluated
regardless of the MONITOR input. The speed is not monitored.
UDT66 UDT_S7PmotSpdC
Block I/Os
9
1
3
8
7
4
6
● Stop
● -> Start (Motor starting)
● -> Stop (Motor stopping)
● Forced start
● Forced stop
(8) Display area for block states
This area displays the active operating level of the block.
(9) Status display of motor
The current status of the motor is graphically displayed here:
● Green: Motor running
● Gray: Motor idle
● Red: A fault has occurred
Multi-instance user object for Basic block in CFC Operator panel block in CFC
S7MV3P LMN3P LMN3P_OP
S7MotSpdC VSD VSD_OP
8.7.1 Function
8.7.7 Setpoint
In manual operating mode, the operator setpoint SP_OP is active. If SP_OP_ON = 1, the
setpoint can be controlled. In automatic operating mode, the SPEXON_L input is used to select
whether the internal setpoint SP_INT (SPEXON_L = 0) or the external setpoint SP_EXT
(SPEXON_L = 1) is to be used. The operator setpoint is updated.
The setpoint is limited by an upper limit (QSP_HLM) and a lower limit (QSP_LLM). The limits
can be manipulated. QSP_HLM is specified with SP_HLM. If final controlling element is not
enabled, QSP_LLM (EN_LMN = FALSE) = 0. Otherwise, it is equal to the low limit SP_LLM.
In LOCK status, the operator setpoint is not updated unless the input TRK_LOCK is set.
Example
Select the units in the "process object view", filter by "I/O Name" "*PERMIS" and assign the
corresponding type to all "enumerations".
The messages can be locked centrally with MSG_LOCK (OS operation) or L_MSGLCK
(program).
QMSG_SUP is set if the RUNUPCYC cycles have not finished running since the restart,
MSG_LOCK or L_MSGLCK = TRUE.
8.7.12 Availability
When control of the control command is possible in automatic mode, the output QAVAIL is set
to TRUE. This is the case under the following conditions.
● No local mode (QLOCAL = FALSE)
● Automatic mode (QMAN_AUT = TRUE)
● No interlock (LOCK = FALSE)
● No external faults (QCSF = FALSE)
SFC6 RD_SINFO
SFC107 ALARM_DQ
SFC19 ALARM_SC
UDT52 UDT_S7SPLITRANGE
UDT65 UDT_S7PMV3P
Block I/Os
1
8
2
7
4 3
(1) Display and switch the operating mode and manipulated variable
● Display and switch the operating mode:
This area provides information on the currently valid operating mode. The following
operating modes can be shown here:
– Manual
– Automatic
● Display the manipulated variable:
This area shows how to specify the manipulated variable. The setpoint can be specified as
follows:
– Auto external
– Auto internal
– Internal
You can find additional information on the operating modes of the block in the section Operating
modes (Page 190)
FU (FU = 1) view
1
11
2
4
10
9
5
8
7 6
(1) Setpoint
● High limit in percent
● Low limit in percent
(2) Slope
● Slope in percent
(3) Monitoring
● Run time in seconds
● Monitoring enabled
(4) Hysteresis
● Positioning in percent
● Monitoring in percent
How it works
Various operating modes are available for controlling the motor-driven valve. This functionality
allows you to set specific valve states. All changes of modes or states and faults occurring in
this context are monitored, visualized in the faceplate and reported to the operator. Operators
with suitable permissions can use the block icon and the faceplate to view the current states
and operate the motorized valve.
Configuration
Install the block in a cyclic interrupt OB (such as OB32) in the CFC Editor. The block is also
installed automatically in the startup OB (OB100).
Startup characteristics
Use the Feature Bit startup characteristics to define the startup characteristics of this block.
Following startup, the messages are suppressed for the number of cycles configured in the
RunUpCyc parameter.
After a startup without control (Open, Close = 0)", no monitoring of the feedback signals
FbkOpen and FbkClose takes places during the V_MonTiStatic time. Changes to
FbkOpen and FbkClose are applied. This means that the feedback is monitored again even
in the stop state.
"Local mode"
You can find general information on "Local mode", switching modes and bumpless switchover
in the Local mode section. For more information see the APL Function Manual.
You can control the following motor valve actions in "Local mode"
● "Open" (OpenLocal = 1)
● "Close" (CloseLocal = 1)
● "Stop" (StopLocal = 1).
A block operated in "Local mode" is controlled either by "Local" signals or by feedback signals
(input parameters FbkOpen and FbkClose; if no position can be assigned, the last valid
position is applied). You can configure the LocalSetting input parameter accordingly.
"Automatic" mode
You can find general information on "Automatic mode", switching modes and bumpless
switchover in the section Manual and automatic mode for motors, valves and dosers. For more
information see the APL Function Manual.
You can control the following motor valve actions in "Automatic" mode:
● "Open" (OpenAut = 1)
● "Close" (CloseAut = 1)
● "Stop" (StopAut = 1)
"Manual" mode
You can find general information on "Manual mode", switching modes and bumpless
switchover in the section Manual and automatic mode for motors, valves and dosers. For more
information see the APL Function Manual.
You can control the following motor valve actions in "Manual" mode:
With Feature.Bit13 = 0:
● "Open" (OpenMan = 1)
● "Close" (CloseMan = 1)
● "Stop" (StopMan = 1)
With Feature.Bit13 = 1:
● Open / Close or Stop via the MV_Int input
"Out of service"
You can find general information about the "Out of service" mode in the Out of service section.
For more information see the APL Function Manual.
S7VlvMot functions
The functions for this block are listed below.
Operator authorizations
This block provides the standard function, operator authorizations. For more information, refer
to the APL Function Manual.
The block has the following permissions for the OS_Perm parameter:
Bit Function
0 1 = Operator can switch to "Automatic mode"
1 1 = Operator can switch to "Manual mode"
2 1 = Operator can switch to "Local mode"
3 1 = Operator can switch to "Out of service" mode
Bit Function
4 1 = Operator can stop the motor
5 1 = Operator can open the valve
6 1 = Operator can close the valve
7 1 = Operator can reset the valve
8 1 = Operator can define the monitoring time for the valve startup
9 1 = Operator can define the monitoring time for the valve run time
10 1 = Operator can activate the monitoring time of the valve (Bit 8 - 9)
11 1 = Operator can define the monitoring time for the motor startup
12 1 = Operator can define the monitoring time for the motor run time
13 1 = Operator can enable the monitoring time function for the motor (bits 11 - 12)
14 1 = Operator can define the monitoring time for startup
15 1 = Operator can define the monitoring time for the run time
16 1 = Operator can activate the monitoring time function (bits 14 - 15)
17 - 18 Not used
19 1 = Operator can change the limit for the hysteresis
20 - 23 Not used
24 1 = Operator can activate the message lock
25 1 = Operator can reset the current run time
26 1 = Operator can reset the total run time
27 - 30 Not used
31 Reserved
The block has the following permissions for the OS1Perm parameter:
Bit Function
0-6 Not used
7 1 = Operator can change the manual parameter Man
8-9 Not used
10 1 = Operator can change the high operating limit of the manipulated variable MV_HiLim
11 1 = Operator can change the low operating limit of the manipulated variable MV_LoLim
12 - 19 Not used
20 1 = Operator can enable manipulated variable tracking in "Manual mode" MV_TrkRbk
21 1 = Operator can enable the bumpless switchover from external to internal MV_TrkExt
22 - 25 Not used
26 1 = Operator can change the limit (control error) for the high alarm ER_AH_Lim
27 1 = Operator can change the hysteresis (control error) ER_Hyst
28 1 = Operator can change the limit (control error) for the low alarm ER_AL_Lim
29 1 = Operator can change the limit (position feedback) for the high warning RbkWH_Lim
30 1 = Operator can change the hysteresis (position feedback) RbkHyst
31 1 = Operator can change the limit (position feedback) for the low warning RbkWL_Lim
Note
If you interconnect a parameter that is also listed in OS_Perm or OS1Perm as a parameter,
you have to reset the corresponding OS_Perm or OS1Perm bit.
Restart lock after changing direction of rotation or switching off the motor
Use the input parameter IdleTime to enter a restart lock for changing the direction of rotation
or restarting the motor. When the "Stop" command is given, the motor goes immediately into
"Stop" mode and IdleTime starts after the feedback (FbkOpening and FbkClosing = 0).
The motor cannot be started again (open or close) until the IdleTime has expired.
Interlocks
This block provides the following interlocks:
● Activation enable
● Interlock without reset ("Interlock")
● Interlock with reset ("Protection")
Refer to the Interlocks section for more information. For more information, refer to the APL
Function Manual.
Torque monitoring
The block provides torque monitoring.
The signals of the torque monitoring switches are interconnected to input parameters
TorqOpen for opening and TorqClose for closing the motor valve.
The Good state is indicated with the value 1 for this parameter .
Using Feature.Bit23 (Vibrate), you can define how to proceed in automatic mode when
the torque has been reached.
the cause of the torque shutoff by means of vibration. This procedure is repeated a maximum
of VibrNo times.
In analog mode (Feature.Bit13 = 1), the motor runs VibrPerc % in the opposite
direction. In binary mode (Feature.Bit13 = 0) VibrWidth seconds.
If torque shutoff is enabled for opening the valve in analog mode, for example, the motor valve
returns to a value of
RbkOut - ((MV_HiLim - MV_LoLim) / 100.0 x VibrPerc)
. When this point is reached, the motor attempts to open to the previously set manipulated
variable once again.
During reversing, the display area of the standard view "Vibrate enabled" is displayed.
After attempting to overcome the cause of the torque VibrNo times, the motor is stopped. The
block must be reset before vibrating can be enabled again.
Seal valve
This function is enabled using Featurebit 8 Seal valve. The seal valve function combines
the query of the end position CLOSED via the input parameter FbkClose with the limit violation
of the configured torque via the input parameter TorqClose. This ensures that the valve is
sealed absolutely tight.
The valve is only considered completely sealed when the feedback of the end position
CLOSED (0->1) and the torque shutoff for closed are enabled. The torque shutoff should not
come before the feedback in this case. The FbkCloseOut output shows whether the valve is
sealed tight:
Maintenance information
The S7VlvMot block has the following inputs and outputs for the operating hour counter and
an output for preventive maintenance. The input and the corresponding output always have
the same value after startup.
Parameter Meaning
Runtime / RuntimeOut Number of operating hours since the last motor start
Runtotal / RuntotalOut Number of operating days since the last total reset
Stoptime / StoptimeOut Number of hours in standstill since the last motor stop
Startcyc / StartcycOut Number of start cycles since the last total reset
PM_Msg = 1, if
Runtotal / RuntotalOut > MaxRunt or
Startcyc / StartcycOut > MaxStart
The parameters can be reset with edge-triggered reset of the inputs to zero. The AS time at
the respective DateTmr and DateTot input is entered as the time stamp for the reset.
Note
The AS time can deviate from the OS time.
Disable interlocks
This block provides the standard function, Disable interlocks. For more information, refer to
the APL Function Manual.
Group error
This block includes the standard function, Group error. For more information, refer to the APL
Function Manual.
The following parameters are taken into consideration when forming the group error:
● CSF
● Trip
● V_MonDynErr
● V_MonStaErr
● M_MonDynErr
● M_MonStaErr
● MonDynErr
● MonStaErr
Note
After the motor valve stops in the intermediate position or end position or after a startup without
control (Open, Close = 0), no monitoring of the feedback signals FbkOpen and FbkClose
takes place during the time V_MonTiStatic. Changes to FbkOpen and FbkClose are
applied. This means that the feedback is monitored again even in stop state.
Note
When the "Seal valve" function is enabled by means of Feature bit 8, the torque shutoff for the
closing TorqClose is also evaluated (see section Seal valve).
Note
The warning is activated for each actuation that causes the motor to start, even if this means
that the valve is moved to the neutral position.
Neutral position
This block provides the standard function, Neutral position for motors, valves and controllers.
For more information, refer to the APL Function Manual.
Bit Function
0 Set startup characteristics
1 Characteristics for the out of service mode
2 Reset the commands for switching the operating mode
3 Enable reset of commands for control
4 Set switch or button mode
7 Anti-blocking system enabled (ABS)
8 Seal valve
9 Reset via input signals in the event of interlocking (protection) or errors
10 Exit local mode
11 Enable run time for feedback signals
12 Motor feedback is not available
13 Enable analog operating mode
14 Enable rapid stop via faceplate
15 - 16 Not assigned
17 Enable bumpless switchover to automatic mode for valves, motors and dosers
18 Enable error status for external process control error CSF
19 Reset even with locked state
20 Not assigned
21 Enable bumpless switchover to automatic mode for valves, motors and dosers
22 Update acknowledgment and error status of the message call
Bit Function
23 Enable vibrate function
24 Enable local operator authorization
25 Suppress all messages
26 Characteristics of the switching points in the "Out of service" operating mode
27 Interlock display with LocalSetting 2 or 4
28 Disabling switching points
29 Signal at limit violation
30 Set reset depending on the operating mode or the LiOp parameter
31 Enable reset of interlocks in manual mode
In switching mode (Bit 4 = 1), control is selected with the static signals OpenAut and
CloseAut. If the OpenAut and CloseAut inputs are not set, the motor is stopped. Control
via StopAut is not required. If the "Enable command reset for control" function is also enabled
(Bit 3 = 1), the OpenAut and CloseAut inputs are reset to 0 after evaluation in the block.
Disable feedback
This block provides the standard function, Disable feedback for valves. For more information,
refer to the APL Function Manual. Feedback monitoring can be disabled separately for each
feedback with NoFbkOpen or NoFbkClose as required.
Repair switch
This block has the repair switch function. When the repair switch is enabled (Repair = 1), the
valve is forced into the neutral position.
Message characteristics
The following messages can be generated for this block:
● Control system fault
● Instance-specific messages
Explanation:
You can interconnect an external fault (signal) to the input parameter CSF. If this signal changes
to CSF = 1, a control system fault is triggered ((MsgEvId4)).
Process messages
Input parameters
* Values can be written back to these inputs during processing of the block by the block
algorithm.
Output parameters
2
14
6
7
13
12
11 8
10
● "Stop"
● "Rapid stop"
activation sequence must perform a reset to once again enable activation of the control
according to the input parameters.
4
2
(1) Settings
You can enable the following functions for the controller in this area:
● "MV := Rbk in manual mode": Bumpless switchover from manual mode to automatic mode
● "MV := MV external": Bumpless switchover of the manipulated variable for manipulated
variable switchover from "external" to "internal". The internal manipulated variable is tracked
to the external one.
Enable monitoring
You enable monitoring by clicking the check box (☑).
Enable monitoring
You enable monitoring by clicking the check box (☑).
(4) Monitoring
In this area, you change parameters and thereby influence the control valve.
You can influence the following parameters:
● "Control": Monitoring time during opening and closing of the control valve (dynamic)
● "Runtime": Monitoring time of the end position of the control valve (static)
Enable monitoring
You enable monitoring by clicking the check box (☑).
S7VlvMot preview
The preview shows you the parameters that you, as an OS operator, can control. You cannot
control anything in this view, however.
(2) External MV
This field displays the external manipulated variable (MV_Ext).
(3) Internal MV
This field displays the internal manipulated variable (MV_Int).
(4) Local MV
This field displays the local manipulated variable (MV_Local).
(6) Track MV
This field displays the MV tracking (MV_TrkOn).
(7) Track MV
This field displays the tracking value (MV_Trk).
Icon Meaning
Valve open
Valve closed
Error at valve
Valve is opening
Valve is closing
Valve stops
9.1.1 Function
SFC6 RD_SINFO
UDTxx UDT_S7PCalcWatP
9.2.1 Function
SFC6 RD_SINFO
UDTxx UDT_S7PHxFct
9.3.1 Function
SFC6 RD_SINFO
UDT69 UDT_S7PMonAn
Block I/Os
9.4.1 Function
SFC6 RD_SINFO
UDT70 UDT_S7PMonAn08
Block I/Os
9.5.1 Function
SFC6 RD_SINFO
UDT71 UDT_S7PMonAnDi
Block I/Os
9.6.1 Function
SFC6 RD_SINFO
UDT73 UDT_S7PMonAnGrad
Block I/Os
9.7.1 Function
SFC6 RD_SINFO
UDT67 UDT_S7PMonDi
Block I/Os
9.8.1 Function
SFC6 RD_SINFO
UDT68 UDT_S7PMonDi08
Block I/Os
9.9.1 Function
Switching commands cannot be sent from the operator panel in the following operating states:
● "Forced on"
● "Forced off"
● "Local operation"
If the operator panel does not have switch permission, all switching states are forwarded from
the motor block S7Mot to the operator panel.
If a relevant system error or state affecting the motor occurs, this is reported to the operator
system by S7PMot.
SFC6 RD_SINFO
UDT62 UDT_S7PMot
Block I/Os
9.10.1 Function
SFC6 RD_SINFO
UDT74 UDT_S7PMotRev
Block I/Os
9.11.1 Function
The commands are sent at the motor control block S7MotSpd via the command outputs that
are interconnected to the motor block S7MotSpd. The motor control block checks for error
states. If no errors are found, the commands are sent to the motor.
Switching commands cannot be sent from the operator panel in the following operating states:
● "Forced on"
● "Forced off"
● "Local operation"
If the operator panel does not have switch permission, all switching states are forwarded from
the motor block S7MotSpd to the operator panel.
If a relevant system error or state affecting the motor occurs, this is reported to the operator
system by S7PMotSpd.
SFC6 RD_SINFO
UDT63 UDT_S7PMotSpd
Block I/Os
Block icon
Views
The block provides the following views:
● Standard view
● Message view
● Associated value view
Standard view
9.12.1 Function
SFC6 RD_SINFO
UDT66 UDT_S7PMotSpdC
Block I/Os
9.13.1 Function
SFC6 RD_SINFO
SFC24 TEST_DB
Block I/Os
9.14.1 Function
Switching commands cannot be sent from the operator panel in the following operating states:
● "Forced open"
● "Forced close"
● "Local operation"
If the operator panel does not have switch permission, all switching states are forwarded from
the valve block S7MV3P to the operator panel.
If a relevant system error or state affecting the valve occurs, this is reported to the operator
system by S7PMV3P.
SFC6 RD_SINFO
UDT65 UDT_S7PMV3P
Block I/Os
9.15.1 Function
SFC6 RD_SINFO
UDT76 UDT_S7POpA
Block I/Os
9.16.1 Function
SFC6 RD_SINFO
UDT75 UDT_S7POpD
Block I/Os
9.17.1 Function
SFC6 RD_SINFO
SFC24 TEST_DB
Block I/Os
9.18.1 Function
Switching commands cannot be sent from the operator panel in the following operating states:
● "Forced open"
● "Forced close"
● "Local operation"
If the operator panel does not have switch permission, all switching states are forwarded from
the valve block S7Vlv to the operator panel.
If a relevant system error or state affecting the valve occurs, this is reported to the operator
system by S7PVlv.
SFC6 RD_SINFO
UDT64 UDT_S7PVlv (UDT_OP_SVALVE)
Block I/Os
9.19.1 Function
SFC6 RD_SINFO
SFC24 TEST_DB
Block I/Os
How it works
The block is a PID controller with continuous output signal (manipulated variable). It is used
to activate a final controlling element with continuous action input.
The block functions following the PID algorithm with a delayed D action and an integrator with
double precision.
The block is suitable for controlling sluggish control loops, for example, for temperatures and
filling levels, and high-speed control loops, for example, for flow rates and speed. For a given
CPU, a compromise has to be made between the number of controllers and the frequency
with which the individual controllers have to be processed. The faster the modulated control
loops are (i.e., the more frequently the manipulated variables have to be calculated per time
unit), the lower the number of controllers that can be installed.
Configuration
Install the block in a cyclic interrupt OB (such as OB32) in the CFC Editor. The block is also
installed automatically in the startup OB (OB100).
For the control loop monitoring to work as planned in the trend view of the controller faceplates,
the S7_archive:='shortterm' attribute must be set for the following tags in the process tag types
for control loops at the controller function blocks:
● Output parameters
– MV
– RbkOut
– SP
– PV_Out
Startup characteristics
Use the startup characteristics Feature bit to define the startup characteristics for this block.
Following startup, the messages are suppressed for the number of cycles configured in the
RunUpCyc parameter.
10.1.3 Functions
The functions for this block are listed below.
If the controller is in "Out of service" mode, the output parameter MV is set to the last valid
value in manual mode or the neutral position manipulated variable depending on the Feature
bit (neutral position manipulated variable takes effect at startup).
Neutral position
The block provides the standard function Neutral position for motors, valves, and controllers.
For more information see the APL Function Manual.
Group error
This block includes the standard function, Group error. For more information see the APL
Function Manual.
The following parameters are taken into consideration when generating the group error:
● CSF
Change the standardized variables to the actual range of the process values and manipulated
variables.
● Internal and external setpoints; the process value and corresponding parameters are
entered according to the physical measuring range of the process value.
● The manual value, the tracking value of the manipulated variable, feedforward control, and
the corresponding parameters are set according to the physical measuring range of the
manipulated variable.
The effective gain is:
● GainEff = (NormMVH - NormMVL) / (NormPVH - NormPVL) • Gain
PID algorithm
The manipulated variable is generated in automatic mode according to the following algorithm:
● MV = Gain • (1 + 1 / (TI • s) + (TD • s) / (1 + TD / DiffGain • s)) • ER
Where:
● s = Complex number
The following step response occurs:
Note
This formula describes a standard application where the P, I, and D component is activated
and the P and D components are not in the feedback circuit (PropSel = 1,TI <> 0,DiffToFbk =
0andPropFacSP = 1).
Control zone
The block provides the standard function Using control zones. For more information see the
APL Function Manual.
The following characteristics are available for this block at the relevant bits:
Bit Function
0 Set startup characteristics
1 Characteristics for the out of service mode
2 Reset the commands for switching the operating mode
4 Set switch or button mode
12 Control zone with specified I component
13 Control zone with frozen I component
14 External control error
15 Neutral position manipulated variable takes effect with "Out of service" operating
mode
16 Neutral position manipulated variable takes effect at startup
18 Disabling bumpless switchover to automatic mode for controllers
22 Update acknowledgment and error status of the message call
Bit Function
24 Enable local operator authorization
25 Suppress all messages
26 Characteristics of the switching points in the "Out of service" operating mode
28 Disabling switching points
29 Signal at limit violation
Operator authorizations
The block provides the standard function Operator authorizations. For more information see
the APL Function Manual.
The block has the following permissions for the OS_Perm parameter:
Bit Function
0 1 = Operator can switch to "Automatic mode" AutModOp
1 1 = Operator can switch to "Manual mode" ManModOp
2 1 = Operator can switch to "Out of service" mode OosOp
3 1 = Operator can switch to "program mode" AdvCoEn
4 1 = Operator can switch the setpoint to "external" SP_ExtOp
5 1 = Operator can switch the setpoint to "internal" SP_IntOp
6 1 = Operator can change the internal setpoint SP_Int
7 1 = Operator can change the manual parameter Man
8 1 = Operator can change maximum usage limit of the setpoint SP_InHiLim
9 1 = Operator can change minimum usage limit of the setpoint SP_InLoLim
10 1 = Operator can change maximum operating limit of the manipulated variable Man‐
HiLim
11 1 = Operator can change minimum operating limit of the manipulated variable Man‐
LiLim
12 1 = Operator can use the setpoint's gradient limitation function SP_RateOn
13 1 = Operator can change the setpoint's high limit for the ramp SP_UpRaLim
14 1 = Operator can change the setpoint's low limit for the ramp SP_DnRaLim
15 1 = Operator can change between the time value or the value for the ramp
SP_RmpModTime
16 1 = Operator can change the ramp time SP_RmpTime
17 1 = Operator can change the target setpoint SP_RmpTarget for the setpoint ramp
18 1 = Operator can activate the setpoint ramp function SP_RmpOn
19 1 = Operator can permit the PID optimization function OptimEn
20 1 = Operator can activate the track setpoint in "Manual mode" function SP_TrkPV
21 1 = Operator can enable the bumpless switchover from external to internal SP_TrkExt
22 1 = Operator can change the gain parameter Gain
23 1 = Operator can change the integral action time parameter TI
24 1 = Operator can change the derivative action time parameter TD
25 1 = Operator can change the derivative gain parameter DiffGain
Bit Function
26 1 = Operator can change the dead band parameter DeadBand
27 1 = Operator can change the control zone parameter ConZone
28 - 31 Not used
The block has the following permissions for the OS1Perm parameter:
Bit Function
0 1 = Operator can change the limit (process value) for the high alarm PV_AH_Lim
1 1 = Operator can change the limit (process value) for the high warning PV_WH_Lim
2 Not used
3 1 = Operator can change the hysteresis (process value) PV_Hyst
4 Not used
5 1 = Operator can change the limit (process value) for the low warning PV_WL_Lim
6 1 = Operator can change the limit (process value) for the low alarm PV_AL_Lim
7 1 = Operator can change the limit (control error) for the high alarm ER_AH_Lim
8 1 = Operator can change the hysteresis (control error) ER_Hyst
9 1 = Operator can change the limit (control error) for the low alarm ER_AL_Lim
10 1 = Operator can change the limit (position feedback) RbkWH_Lim for the high
warning
11 1 = Operator can change the hysteresis (position feedback) RbkHyst
12 1 = Operator can change the limit (position feedback) for the low warning RbkWL_Lim
13 - 15 Not used
16 1 = Operator can change MsgLock
17 - 31 Not used
Note
If you interconnect a parameter that is also listed as a parameter in OS_Perm, you have to
reset the corresponding OS_Perm.Bit.
Specifying the display area for process and setpoint values as well as operations
Specifying the display area for process and setpoint values as well as operations
10.1.5 Messaging
Message characteristics
The following messages can be generated for this block:
● Control system fault
● Process messages
You can interconnect an external fault (signal) to input parameter CSF. If this signal changes
to CSF = 1, a process control error is triggered (MsgEvId09).
Process messages
10.1.6 I/Os
Input parameters
* Values can be written back to these inputs during processing of the block by the block
algorithm.
Output parameters
19
1
18 5
2
3
17 4
16 5
15 3
6
14
7
6
13 9
12
10
11
(1) "Settings"
You can enable the following functions for the controller in this area:
● "PID optimization": ☑ activate controller optimization
● "SP := PV in manual mode": ☑ Bumpless switchover from "manual mode" to "automatic
mode"
● "SP := SP external": ☑ Bumpless switchover of the setpoint for setpoint switchover from
"external" to "internal". The internal setpoint is tracked to the external one.
(2) "Parameters"
In this area, you change parameters and, therefore, influence the controller.
You can influence the following parameters:
● "Gain": Proportional gain
● "Integral time" Integral action time in [s]
● "Derivative time TD": Derivative action time in [s]
● "Derivative gain": Gain of the derivative action
● "Dead band": Width of dead band
● "Control zone": Width of control zone
(3) "Delay factor"
In this area, you set the following delay factors for the controller:
● "ER H Alarm": Factor for high alarm in [s/PV_Unit]
● "ER L Alarm": Factor for high alarm in [s/PV_Unit]
The preview shows you the parameters that you, as an OS operator, can control. You cannot
control anything in this view, however.
(1) Process value
This area shows the real process value (PV).
(2) Preview area
This area shows you a preview for the following values:
● "SP external": currently applicable external setpoint
● "SP internal": currently applicable internal setpoint
● "Control deviation": Current control deviation
● "Program value": specified value for program mode
● "Disturbance variable": additive value for feedforward control
Area of application
The S7TiSwitch block is a software implementation of a clock timer. Eight switch channels
(pairs of "On" and "Off" switch points) can be preset. Each channel can be switched On or Off
for every day of the week separately.
Configuration
Compilation settings
The S7TiSwitch block requires different FCs in the number range 1-8. Therefore, the
compilation settings for the CFC must be configured under Options\Settings\Compile
\Download in such a way that the FC numbers 1-8 are in the reserved area.
Startup characteristics
All pulse timers are reset during startup. According to APL (Feature Bit0 ‘Startup’), messages
and operator authorizations either retain their last value or they are reset.
Called blocks
FC1 AD_DT_TM
FC7 DT_DAY
FC8 DT_TOD
FC14 GT_DT
FC34 SB_DT_DT
FC69 LOC_TIME
SFC1 READ_CLK
SFC6 RD_SINFO
SFC19 ALARM_SC
SFC20 BLKMOV
SFC107 ALARM_DQ
Configuration
Install the block in a cyclic interrupt OB (such as OB32) in the CFC Editor. The block is also
installed automatically in the startup OB (OB100).
Function
Every switch point can be set to a time between 00:00:00 and 23:59:59. The switch-on time
must always be earlier than the switch-off time.
The output signal of a switch channel is set to "On" if the current time is later than or the same
as the switch-on time and earlier or the same as the switch-off time. Timings are to the second.
Example:
Switch-on time for channel 1: 22:00:00 (day 1) ⇒ Output is set to "On" at 22:00:00 (day 1)
Switch-off time for channel 1: 23:59:59 (day 1) ⇒
Switch-on time for channel 2: 00:00:00 (day 2) ⇒ Output is set to "Off" at 03:00:01 (day 2)
Switch-off time for channel 2: 03:00:00 (day 2) ⇒
For every switching output there are two pulsed outputs–one for the "On" pulse (P_Onn) and
another one for the "Off" pulse (P_Offn). The pulse length can be set for all pulses at once in
the parameter view of the faceplate.
In addition to performing the switching function, the S7TiSwitch block indicates when each
channel is next due to be switched "On" or "Off" based on the current program. The periods
of time prior to the next switch-on points are indicated at the NxTiOn block outputs and the
periods of time prior to the next switch-off points at the NxTiOffn block outputs. The amount
of time is indicated in seconds (double integer).
Operator authorizations
This block provides the standard function, operator authorizations. Information is available in
the section Operator control permissions in the APL Function manual.
The block has the following permissions for the OS_Perm parameter:
Bit Function
0 Reserved
1 1 = Operator can change switching points
2 1 = Operator can activate "On" mode
3 1 = Operator can activate "Out of service" mode
4 1 = Operator can change pulse time
5 1 = Local internal AS time used (LOC_TIME block)
5 - 15 Not used
16 1 = Operator can activate MsgLock
17 - 31 Not used
LocTiSetting input must be adapted for each user to the user-specific parameter
assignment.
S7TiSwit use in CPU without time status (e.g. S7300) - "Local and standard/daylight saving
time in the CPU":
The function BT_LT (FC 61) of the standard library is used to determine the standard and the
daylight saving time.
The standard/daylight saving time parameters can be assigned using the rule DB of the
standard library. The structure of the rule DB must be connected to the LocTiSetting input
(see documentation for the standard library rule DB / UDT 60). For this function, the Feature
input parameter of S7TiSwitch must be set as follows:
● Feature.Bit4 = 0
● Feature.Bit5 = 0
Additional blocks and interconnections are needed:
S7TiSwit use in CPU without time status (e.g. S7300) - "Local time in the CPU":
The function AD_DT_TM (FC1) of the standard library is used to determine the local time.
The time offset can be configured at the D input of the AD_DT_TM function. (The
LocTiSetting.B2L.T input of S7TiSwitch must be set to 0 for this). For this function, the
Feature input parameter of S7TiSwitch must be set as follows:
● Feature.Bit4 = 0
● Feature.Bit5 = 0
Additional blocks and interconnections are needed:
Bit Function
0 0 = Start up with initialization defined in OB100, 1 = Retain last stored values
1 1 = OosLi can set "Out of service"
2 1 = External time signal is used for switching
3 1 = Automatically switch over to internal time if TiExtQc <> 16#80 or 16#60
4 0 = Local time, 1 = AS internal time used for switching
5 1 = Local internal AS time used (LOC_TIME block)
6 - 21 Not used
22 1 = Update acknowledgment and error status of the message call
23 Not used
24 1 = Local operator authorization enabled
25 1 = Suppress all messages if MsgLock = 1
26 - 31 Not used
The following modes of behavior are available for this block at the relevant bits:
Bit Function
0 - 31 Not used
Since the block does not handle process values, it only recognizes two errors:
● ErrorNum
Displays the current error number.
Message behavior
The following messages can be generated for this block:
● Control system fault
Input parameters
* Values can be written back to these inputs during processing of the block by the block
algorithm.
Output parameters
4
3
(1) Mode
Display and switchover of the operating mode This area provides information on the currently
valid operating mode. The following operating modes can be shown here:
● On
● Out of service
(2) Display of the activation and deactivation times
This display shows the activation and deactivation times and displays the active/inactive
weekdays. The 8 time windows can be activated or deactivated. If a time window is currently
active, this is visualized by a green square.
(3) Message lock active
(4) Display area for block states
This area provides additional information on the operating state of the block:
● "Maintenance"
Additional information is available in the 'Maintenance enable' section in the APL manual.
(5) Current time display
This area displays the current day and current time and whether daylight-saving time is
currently active.
(6) Status display
The current status of the timer block is graphically displayed here.
(1) Settings
You can change parameters in this area. Refer to the section "Changing values" in the APL
manual for more information on the following parameters you can set:
● "Pulse time": Length of the pulse time
1
4
S7TiSwitch/1:
S7TiSwitch/2:
S7TiSwitch/3:
S7TiSwitch/4:
10.3.1 Function
The final controlling elements are limited to their respective limits STATUS_x.SP_HLM and
STATUS_x.SP_LLM. This would mean that a deadband would be created for a controller
manipulated variable between x1 and x2 in which there would be no change in the final
controlling elements. To prevent this from happening, waiting for a configured deadband
(DEADB_W) is incorporated after violations of SP_HLM / SP_LLM and then a jump is made
to the limit of the next final controlling element.
Example
LMN_PID > x1 + DEADB_W and control deviation is positive
⇒ LMN_PID is tracked to x2 by setting for EXT_T seconds the output LMN_TRK = x2 and
LMN_SEL = TRUE.
UDT52 UDT_S7SPLITRANGE
SFC6 RD_SINFO
Block I/Os
Example
The following example contains 3 final controlling elements with the following data:
Final controlling elements 1 – 3 are available and enabled:
● EN_x = TRUE, STATUS_x.STATUS Bit 0 = TRUE
Final controlling element 4 is not used:
● EN_4 = FALSE.
General information
Variable Value
DEADB_W 5%
Scenarios
The following scenarios apply to the example:
x: Irrelevant
+: Positive control deviation
-: Negative control deviation
10.4.1 Function
SFC6 RD_SINFO
11.1.1 Function
SFC1 READ_CLK
12.1.1 Function
12.1.5 Output V
The measured analog value appears on output V. The analog value can be from the process
(U), simulated (MAN_EN, U_MAN) or specified for a pending CSF via a substitute value
(SUBST_EN, U_SUBST). If the simulation value has been activated, it is given the highest
priority.
The output V is generated as shown in the following table.
The messages for limit value violations can be suppressed individually via the appropriate
M_SUP_xx inputs. The messages can be locked centrally with MSG_LOCK (OS operation) or
L_MSGLCK (program).
QMSG_SUP is set if the RUNUPCYC cycles have not finished running since the restart, or if
MSG_LOCK or L_MSGLCK = TRUE.
SFC6 RD_SINFO
SFC107 ALARM_DQ
SFC19 ALARM_SC
UDT69 UDT_S7PMonAn (UDT_OP_SMEAS)
5 2
(1)
● AH
● WH
(2)
● WL
● AL
(3) Bar graph for the process value
This area shows the current process value in the form of a bar graph. The visible area in the
bar graph depends on the configuration in the engineering system (ES).
The procedure for configuring trends is described in the document titled "Block description –
General".
12.2.1 Function
12.2.5 Output V
The measured analog value appears on output V. The analog value can be from the process
(U), simulated (MAN_EN, U_MAN) or specified for a pending CSF via a substitute value
(SUBST_EN, U_SUBST). If the simulation value has been activated, it is given the highest
priority.
The messages for limit value violations can be suppressed individually via the appropriate
M_SUP_x inputs. The messages can be locked centrally with MSG_LOCK (OS operation) or
L_MSGLCK (program).
QMSG_SUP is set if the RUNUPCYC cycles have not finished running since the restart,
MSG_LOCK or L_MSGLCK = TRUE.
Block I/Os
SFC6 RD_SINFO
SF107 ALARM_DQ
SFC19 ALARM_SC
UDT70 UDT_S7PMonAn08
(1)
● High limit
● Low limit
(2)
● Limits 1 to 8
● Limits 1 to 8
● Message lock 1 to 8
12.3 S7MonAnDi - Measured value monitoring for 4 analog and binary limits
12.3.1 Function
12.3.5 Output V
The measured analog value appears on output V. The analog value can be from the process
(U), simulated (MAN_EN, U_MAN) or specified for a pending CSF via a substitute value
(SUBST_EN, U_SUBST). If the simulation value has been activated, it is given the highest
priority.
Message Block param‐ Default message text Message class Can be suppressed by
number eter MSG_LOCK or
L_MSGLCK or
1 Q_AL Alarm low Alarm low M_SUP_AL
2 Q_AH Alarm high Alarm high M_SUP_AH
3 Q_WL Warning low Warning low M_SUP_WL
Message Block param‐ Default message text Message class Can be suppressed by
number eter MSG_LOCK or
L_MSGLCK or
4 Q_WH Warning high Warning high M_SUP_WH
5 QCSF External error AS control system -
Fault
The messages for limit value violations can be suppressed individually via the appropriate
M_SUP_xx inputs. The messages can be locked centrally with MSG_LOCK (OS operation) or
L_MSGLCK (program).
QMSG_SUP is set if the RUNUPCYC cycles have not finished running since the restart, or if
MSG_LOCK or L_MSGLCK = TRUE.
SFC6 RD_SINFO
SFC107 ALARM_DQ
SFC19 ALARM_SC
UDT71 UDT_S7PMonAnDi (UDT_OP_SMEASB)
5 2
(1)
● AH
● WH
(2)
● WL
● AL
(3) Bar graph for the process value
This area shows the current process value in the form of a bar graph. The visible area in the
bar graph depends on the configuration in the engineering system (ES).
12.4.1 Function
12.4.7 Output V
The measured analog value appears on output V. The analog value can be from the process
(U), simulated (MAN_EN, U_MAN) or specified for a pending CSF via a substitute value
(SUBST_EN, U_SUBST). If the simulation value has been activated, it is given the highest
priority.
The output V is generated as shown in the following table.
Message Block param‐ Default message text Message class Can be suppressed by
number eter MSG_LOCK or
L_MSGLCK
1 QCSF External error AS control system -
Fault
2 Q_AL Alarm low Alarm low M_SUP_AL
3 Q_AH Alarm high Alarm high M_SUP_AH
4 Q_WL Warning low Warning low M_SUP_WL
5 Q_WH Warning high Warning high M_SUP_WH
Message Block param‐ Default message text Message class Can be suppressed by
number eter MSG_LOCK or
L_MSGLCK
6 Q_GN Violation, gradient low Warning low M_SUP_GN
7 Q_GP Violation, gradient high Warning high M_SUP_GP
The messages for limit value violations can be suppressed individually via the appropriate
M_SUP_xx inputs. The messages can be locked centrally with MSG_LOCK (OS operation) or
L_MSGLCK (program).
QMSG_SUP is set if the RUNUPCYC cycles have not finished running since the restart, or if
MSG_LOCK or L_MSGLCK = TRUE.
SFC6 RD_SINFO
SFC107 ALARM_DQ
SFC19 ALARM_SC
UDT73 UDT_S7PMonAnGrad (UDT_OP_SMEASGRAD)
(1)
● Time base in seconds
● Time base selection
(2)
● Gradients below in °C
● Gradients above selection
(3)
● Gradients above in C
● Gradient selection
12.5.1 Function
12.5.4 Output Q
A message is sent to WinCC on a positive edge at the output Q. When a negative edge occurs,
the message assumes the status "departed." The output Q is generated; it is dependent on
the input type configured at the N_OP_CL parameter (break contact/make contact).. The output
Q always indicates the state triggering the message, except when HOLD_EN = TRUE. In this
case, the output Q is set and stored when the state triggering the message is queued. The
output remains queued when the state triggering the message departs and is not reset until a
positive edge occurs on the acknowledgment input L_RESET.
If the MAN_EN input is set to TRUE, the output Q is set based on the I_MAN parameter, which
is controlled in the faceplate of WinCC. In this case, a queued message is marked as departed.
The message path is then suppressed.
If SUBST_EN = TRUE, the substitute value I_SUBST is forwarded to the output Q in the event
of an external error (CSF = TRUE). MANUAL mode (MAN_EN = TRUE) has higher priority. If
manual mode is not selected, the I_MAN input is adjusted to the output Q to permit bumpless
switchover to manual mode.
The output Q is output as not malfunctioning if LOCK = TRUE, regardless of input I.
The messages can be locked centrally with MSG_LOCK (OS operation) or L_MSGLCK
(program).
QMSG_SUP is set if the RUNUPCYC cycles have not finished running since the restart,
MSG_LOCK or L_MSGLCK = TRUE.
SFC6 RD_SINFO
SFC107 ALARM_DQ
SFC19 ALARM_SC
UDT67 UDT_S7PMonDi (UDT_OP_SDIGMO)
3
5
(1)
● Input
● Output
● Normalization
(2) Suppression time
(3) Message lock enabled
(4) Display area for block states
This area provides additional information on the operating state of the block:
● Enabled
(5) Display area for block states
This area provides additional information on the operating state of the block:
● LocalOS
12.6.1 Function
12.6.4 Outputs Qx
A message is generally sent to WinCC when a positive edge occurs on one of the outputs Qx.
When a negative edge occurs, the message assumes the status "departed." The outputs Qx
are generated at parameter N_OP_CLx (break contact/make contact) based on the configured
input type. However, the outputs Qx always indicate the status which triggered the message.
When the MAN_ENx inputs are set to TRUE, the outputs Qx are not supplied by the inputs Ix
but by the I_MANx parameter which is controlled in the WinCC faceplate. A queued message
is marked as departed and no more messages are generated.
If SUBSTENx = TRUE, the substitute value Ix_SUBST is forwarded to the output Qx in the
event of an external error (CSFx = TRUE). MANUAL mode (MAN_ENx = TRUE) has higher
priority. If MANUAL mode is not selected, the I_MANx input is adjusted to the corresponding
output Qx to permit bumpless switchover to manual mode.
If LOCK = TRUE or the corresponding enable EN_Ix = FALSE, the outputs Qx are output as
not malfunctioning, regardless of the input.
The messages can be locked centrally with MSG_LOCK (OS operation) or L_MSGLCK
(program).
QMSG_SUP is set if the RUNUPCYC cycles have not finished running since the restart, or if
MSG_LOCK or L_MSGLCK = TRUE.
SFC6 RD_SINFO
SFC107 ALARM_DQ
SFC19 ALARM_SC
UDT68 UDT_S7PMonDi08
3
6
4
5
(1)
● Inputs 1 to 8
● Input signal 1 to 8 Off
● Output signal 1 to 8 Off
(2) Suppression time
(3) Message lock enabled
(4)
(5) Display area for block states
This area provides additional information on the operating state of the block:
● Enabled
(6) Display area for block states
This area provides additional information on the operating state of the block:
● LocalOS
(1) Inputs 1 to 8
● Sim. 1 to 8
● Sub. 1 to 8
● Enabled 1 to 8
O
F Object name
Feature S7RcvAna, 111
S7TiSwitch, 402 S7RcvDig, 107
Function S7RcvHAna, 127
S7TiSwitch, 399 S7RcvHDig, 123
Functions S7SndAna, 104
S7RcvAna, 112 S7SndDig, 101
S7RcvDig, 108 S7SndHAna, 119
S7RcvHAna, 128 S7SndHDig, 115
S7RcvHDig, 124 S7TiSwitch, 397
S7SndAna, 105 Operating mode
S7SndDig, 102 S7RcvAna, 112