Siemens SIMATIC PCS 7 Parts list manual

SIMATIC Process Control System PCS 7 SIMATIC BATCH Interface Blocks V7.1
_
_____________
_
_____________
_
_____________
Overview of the Block
Description
1
BATCH interface blocks
2
Equipment Parameter
Module
3
SIMATIC
Process Control System PCS 7
SIMATIC BATCH Interface Blocks
V7.1
Function Manual
03/2009
A5E02171101-01

Safety Guidelines
Safety Guidelines
This manual contains notices you have to observe in order to ensure your personal safety, as well as to prevent
damage to property. The notices referring to your personal safety are highlighted in the manual by a safety alert
symbol, notices referring 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
with a safety alert symbol, indicates that minor personal injury can result if proper precautions are not taken.
CAUTION
without a safety alert symbol, indicates that property damage can result if proper precautions are not taken.
NOTICE
indicates that an unintended result or situation can occur if the corresponding information is not taken into
account.
If more than one degree of danger is present, the warning notice representing the highest degree of danger will
be used. A notice warning of injury to persons with a safety alert symbol may also include a warning relating to
property damage.
Qualified Personnel
The device/system may only be set up and used in conjunction with this documentation. Commissioning and
operation of a device/system may only be performed by qualified personnel. Within the context of the safety notes
in this documentation qualified persons are defined as persons who are authorized to commission, ground and
label devices, systems and circuits in accordance with established safety practices and standards.
Prescribed Usage
Note the following:
WARNING
This device may only be used for the applications described in the catalog or the technical description and only
in connection with devices or components from other manufacturers which have been approved or
recommended by Siemens. Correct, reliable operation of the product requires proper transport, storage,
positioning and assembly as well as careful operation and maintenance.
Trademarks
All names identified by ® are registered trademarks of the Siemens AG. The remaining trademarks in this
publication may be trademarks whose use by third parties for their own purposes could violate the rights of the
owner.
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.
Siemens AG
Automation and Drives
Postfach 48 48
90437 NÜRNBERG
GERMANY
A5E00495301-02
Ⓟ 09/2008
Copyright © Siemens AG 2009.
Technical data subject to change

SIMATIC BATCH Interface Blocks V7.1
Function Manual, 03/2009, A5E02171101-01 3
Table of contents
1 Overview of the Block Description ............................................................................................................. 5
2 BATCH interface blocks............................................................................................................................. 9
2.1 IEPH...............................................................................................................................................9
2.1.1 IEPH: Equipment Phase - BATCH Interface..................................................................................9
2.1.2 Operator Control and Monitoring of IEPH....................................................................................16
2.1.3 I/Os of IEPH .................................................................................................................................19
2.2 IEOP.............................................................................................................................................21
2.2.1 IEOP: Equipment Operation - BATCH Interface..........................................................................21
2.2.2 I/Os of IEOP.................................................................................................................................27
2.2.3 Operator Control and Monitoring of IEOP....................................................................................29
2.3 TAG_COLL...................................................................................................................................32
2.3.1 TAG_COLL: TAG_Collect - BATCH Interface..............................................................................32
2.3.2 I/Os of TAG_COLL.......................................................................................................................33
2.4 IUNIT_BLOCK..............................................................................................................................34
2.4.1 IUNIT_BLOCK: Unit Allocation - BATCH Interface......................................................................34
2.4.2 I/Os of IUNIT_BLOCK ..................................................................................................................38
2.4.3 Operator Control and Monitoring of IUNIT_BLOCK.....................................................................40
3 Equipment Parameter Module ................................................................................................................. 43
3.1 IEPAR_BOOL...............................................................................................................................43
3.1.1 IEPAR_BOOL: Equipment Parameter Module for the Boolean Data Type .................................43
3.1.2 I/Os of IEPAR_BOOL...................................................................................................................44
3.2 IEPAR_DEST...............................................................................................................................45
3.2.1 IEPAR_DEST: Equipment Parameter Module for the DEST Data Type .....................................45
3.2.2 I/Os of IEPAR_DEST ...................................................................................................................45
3.3 IEPAR_DINT ................................................................................................................................46
3.3.1 IEPAR_DINT: Equipment Parameter Module for the Double Integer Data Type ........................46
3.3.2 I/Os of IEPAR_DINT ....................................................................................................................47
3.4 IEPAR_ENUM..............................................................................................................................48
3.4.1 IEPAR_ENUM: Equipment Parameter Module for the ENUM Parameter Type..........................48
3.4.2 I/Os of IEPAR_ENUM ..................................................................................................................48
3.5 IEPAR_PI .....................................................................................................................................49
3.5.1 IEPAR_PI: Equipment Parameter Module for Process Inputs.....................................................49
3.5.2 I/Os of IEPAR_PI .........................................................................................................................50
3.6 IEPAR_PO ...................................................................................................................................51
3.6.1 IEPAR_PO: Equipment Parameter Module for Process Outputs ................................................51
3.6.2 I/Os of IEPAR_PO........................................................................................................................52
3.7 IEPAR_REAL ...............................................................................................................................53
3.7.1 IEPAR_REAL: Equipment Parameter Module for the Real Data Type........................................53
3.7.2 I/Os of IEPAR_REAL ...................................................................................................................54

Table of contents
SIMATIC BATCH Interface Blocks V7.1
4 Function Manual, 03/2009, A5E02171101-01
3.8 IEPAR_SOURCE ........................................................................................................................ 55
3.8.1 IEPAR_SOURCE: equipment parameter module for the SOURCE data type ........................... 55
3.8.2 I/Os of IEPAR_SOURCE............................................................................................................. 56
3.9 IEPAR_STR ................................................................................................................................ 57
3.9.1 IEPAR_STR: equipment parameter module for the STRING parameter type............................ 57
3.9.2 I/Os of IEPAR_STR..................................................................................................................... 58
3.10 IEPAR_TKEY .............................................................................................................................. 59
3.10.1 IEPAR_TKEY: equipment parameter module for the TKEY data type ....................................... 59
3.10.2 I/Os of IEPAR_TKEY................................................................................................................... 60
3.11 IEPAR_VIA.................................................................................................................................. 61
3.11.1 IEPAR_VIA: equipment parameter module for the VIA data type............................................... 61
3.11.2 I/Os of IEPAR_VIA ...................................................................................................................... 62
Index........................................................................................................................................................ 63

SIMATIC BATCH Interface Blocks V7.1
Function Manual, 03/2009, A5E02171101-01 5
Overview of the Block Description 1
Introduction
The block descriptions always organized in the following form:
● Overview of the block description
● Object name (type + number)
● Function
● How the block functions
● Calling OBs
● Error handling
● I/Os of ...
● Operating control and monitoring of ...
Overview of the block description
Example: IEPH: Equipment Phase - BATCH Interface
The title begins with the type name of the block (IEPH). This symbol name is entered in the
symbol table and must be unique in the project.
You will find the keyword for the task/function of the block (equipment phase BATCH
interface) in the type name.
Object name (type + number)
FBx
The object name of the block type is formed by the type of implementation
Function block = FB, function = FC and the block number = x.
Function
This section briefly explains the function of the block. You can find additional information
about complex blocks in the section "How the Block Functions".
How the block functions
Here you can find additional information about the functions of individual inputs, modes, time
sequences, etc. You can learn about the overall relationships in order to use the block
effectively, here.

Overview of the Block Description
SIMATIC BATCH Interface Blocks V7.1
6 Function Manual, 03/2009, A5E02171101-01
Calling OBs
This section contains information about the organization blocks (OBs) in which the block
being described must be installed. When using CFC, the block is installed in the cyclic OBs
(cyclic interrupt) and automatically in the OBs listed in the taskbar of the block (for example,
in OB100 for a hot restart).
During compilation, CFC generates the required OBs. When using the blocks without CFC,
you must program these OBs and call the block instance in them.
Error handling
You can find the error code in the CFC chart at the ENO Boolean block output. The value
corresponds to the BR (binary result in STEP 7 SCL on completion of the block) or the OK
bit (in SCL notation) has the following meaning:
● ENO=BR=OK=1 (TRUE) → The result of the block is correct.
● ENO=BR=OK=0 (FALSE) → The result or the conditions for calculating the result (for
example, input values, modes) are not valid.
With FBs, you will also find the inverted BR at the output QERR of the instance DB.
● QERR=NOT ENO
The error code is produced in two independent ways:
The operating system detects a processing error (for example, value overflow, called system
functions supply error ID with BR=0). This is a system function and is not described in detail
in the individual block descriptions.
The block algorithm checks whether values and modes are functionally permitted These
errors are documented in the description of the block.
You can evaluate the error code, for example, to create messages or to work with substitute
values instead of incorrect results.

Overview of the Block Description
SIMATIC BATCH Interface Blocks V7.1
Function Manual, 03/2009, A5E02171101-01 7
I/Os of ...
The I/Os represent the data interface of the block. Via these I/Os, you can transfer data to
the block and fetch results from it.
Table 1-1 I/Os of ...
I/O
(parameter)
Meaning Type Default Type Attr. OCM Permitted
values
SP_VAL Setpoint
(input)
DInt 0 I +
The "I/Os" table lists all the input and output parameters of the block type that the user can
access with configuration tools. They are sorted alphabetically. I/Os that can only be
accessed by the algorithm of the block, so-called internal variables, are not listed. The
columns have the following meaning:
● I/O
Name of the parameter derived from the English name.
Example: PV_IN = Process Variable INput (process variable, control variable). As far as
permitted by SIMATIC conventions, the same names were used.
● Meaning
Function (sometimes abbreviation)
● Type
S7 data type of the parameter (e.g. BOOL, REAL)
● Default
The value of the parameter before the block is run for the first time, unless this was
changed during configuration
● Type
Type of access of the block algorithm on the parameter; differentiates between inputs,
reacting inputs and outputs (refer to table below).
Table 1-2 Block algorithm
Abbreviati
on
Type
I Input
Value supply of the block (representation in the CFC: left side of block)
O Output
Output value. (representation in the CFC: right side of the block)
IO Input / output
Reacting input that can be written by the OS and written back by the block (representation in the CFC: left side
of block)

Overview of the Block Description
SIMATIC BATCH Interface Blocks V7.1
8 Function Manual, 03/2009, A5E02171101-01
● Attr. (Attribute)
Additional characteristics of the parameter when used in CFC. Input and output
parameters that are not interconnected can have parameters assigned (input/output
parameters only with online FCs).
Output parameters cannot have values assigned and can be transferred in CFC by
interconnecting them to an input of the same data type.
Additional or deviating parameter properties will be specified as follows:
Table 1-3 Parameter properties
Abbreviation Attribute
Q Interconnectable
The I/O can be interconnected with another output of the same type.
U Hidden in the CFC
The I/O is not displayed in CFC (for example, the message ID), since this in supplied by the block itself or by
the OS block. This default setting can be changed in the CFC.
OCM
Parameters identified by the "+" character can be monitored and controlled using the
corresponding OS block.
Valid values
Valid limit within the range of values of the data type
Operating control and monitoring of ...
If an OS block exists for the PLC block, the fields on the faceplate are described in the table.

SIMATIC BATCH Interface Blocks V7.1
Function Manual, 03/2009, A5E02171101-01 9
BATCH interface blocks 2
2.1 IEPH
2.1.1 IEPH: Equipment Phase - BATCH Interface
IEPH: Equipment Phase - BATCH Interface
Object name (type + number)
FB 254 (Page 19)
Calling OBs
The OB in which you install the block (for example, OB1).
Function
The IEPH block serves as the interface between a BATCH recipe step of the type RPH
(recipe phase) and the user programs on the automation system for control and status
information. The IEPH block is used to pass on the batch control commands to the user
program (basic function blocks) and the status messages of the user encoded in the status
word of the IEPH block for batch control.
The setpoints are set and the process values adopted via the parameter blocks (IEPAR_...)
underlying the IEPH block. To allow this, the IEPAR blocks are interconnected with the
EPE_CONN output of IEPH. Via this output, there is also check to establish whether the
configured IEPH block instance and the IEPAR block instances match the definition of the
phase type. The name of the phase type is located in the F_TYPE input parameter of the
IEPH block.

BATCH interface blocks
2.1 IEPH
SIMATIC BATCH Interface Blocks V7.1
10 Function Manual, 03/2009, A5E02171101-01
The IEPH block allows the following status changes:
67$57
+(/'
KHOG
5(680,1*
UHVXPLQJ
+2/',1*
KROGLQJ
+2/' +2/'
QRWDXWRPDWLFDOO\FRPSOHWHG
5($'<72
&203/(7(
UHDG\WR
FRPSOHWH
)
,'/(
LGOHVWDWH 67$57 67$57,1*
VWDUWLQJ
5811,1*
UXQQLQJ
6723 $%257 VHOIWHUPLQDWLQJ 7(50,1$7(
67233,1*
VWRSSLQJ
$%257,1*
DERUWLQJ
&203/(7,1*
FRPSOHWLQJ
67233('
VWRSSHG
$5%257('
DERUWHG
&203/(7('
FRPSOHWHG
5(6(7
5(680(
67233,1*
VWRSSLQJ
(UURUUHFHLYHG
(UURUFOHDUHG
Operating principle
● Allocate / Enable
A recipe step can occupy the block by setting the identifier OCCUPIED = 1. It also enters
an occupied information based on the batch name, batch number, the step number
(UBA_NAME, UBA_ID, USTEP_NO) and, if necessary, the step monitoring time
(STEP_T). The block is only occupied if enabled for BATCH (BA_EN = 1), if set to auto
mode (status word bit 17 = 1), and if there is no active group error (status word bit
31 = 0).
● Control commands
The block is controlled by way of the ISTART, IHOLD, IABORT, ISTOP, ITERM, IRESET
(for interconnection in CFC) control inputs, or by means of control word ICTRL (used only
in BATCH). The active control commands can be read from the corresponding outputs,
for example, QSTART and QHOLD. Control word ICTRL enables the consistent writing of
control commands in BATCH. Example: ICTRL = 1 ensures that ISTART = 1 and
IHOLD = 0 are written simultaneously. The control inputs are reset automatically after the
corresponding end status was reached (reset of ISTART at the positive of the RUNNING
bit in USTAT_L, for example).

BATCH interface blocks
2.1 IEPH
SIMATIC BATCH Interface Blocks V7.1
Function Manual, 03/2009, A5E02171101-01 11
● Status word
The reaction to user input is signaled at the USTAT_L status input of the user block which
is interconnected with the IEPH block. The status, including other block information, is
returned at output QUSTAT_L and is monitored by BATCH. The bit assignment is
synchronized with the assignment at the SFC_CTRL block.
● No automatic completion
The BATCH block sets the READY bit in the status word to report that it is not
automatically completing and that BATCH is to handle completion. If using the
SFC_CTRL block which does not provide a READY status you can set the READY bit
using input IREADY.
● Runtime monitoring
The step time is incremented at intervals of one second with a positive edge at the
RUNNING status. The COMPLETED status is used to stops the time count. The
"Runtime exceeded" identifier is set (bit 19) if the actual value (Q_STEP_T) exceeds the
setpoint (STEP_T). Runtime monitoring is taken into account as message in WinCC and
does not generate a group error.
Note
Identifier "SFC: Step runtime error" is used internally by the SFC and leads to a group
error.
● Trigger for reading setpoints/actual values
If the block is active the user program can set the trigger signal IREFRESH in QUSTAT_L
by generating a positive edge at input IREFRESH. This action instructs BATCH to
immediately read all setpoints and actual values and to archive these in the batch data for
reporting.
● Trigger for checking and activating new setpoints
BATCH sets input IPARAM when reading new setpoints. The basic function detects this
action by monitoring the corresponding QPARAM output and can then check and activate
the setpoints. If the check returns a negative result the basic function can either signal an
error or disable the start by setting input "ILOCK". BATCH resets input IPARAM during
startup of the technical function. This can be done, for example, in conjunction with a
change of the mode of operation.

BATCH interface blocks
2.1 IEPH
SIMATIC BATCH Interface Blocks V7.1
12 Function Manual, 03/2009, A5E02171101-01
● Start lock
The "Start lock" identifier in the status word or input "ILOCK" can be used to inform the
BATCH block that start or resume is not desired.
Note
The start lock must have been set in IDLE state if the BATCH is to comply with the start
lock. If start lock is set the BATCH executes the occupation it initially writes the setpoints
and then waits for the block to reset the start lock.
● Continuous mode or bumpless changeover. In continuous mode, two recipe steps (time-
based) successively use the same block without resetting this block between the steps.
The block only reports the READY state at the end of the first cycle. BATCH then sets the
status ID for continuous mode by setting input ICONT instead of terminating the block by
setting ITERM. You configure this functionality when creating the recipes. ICONT is reset
when the second recipe step is activated.
"Continuous mode or bumpless changeover" is only supported by recipe functions which
are not automatically completed.
Allocation of ICTRL
Bit Meaning
0 ISTART
1 IHOLD
2 IABORT
3 IRESET
4 ITERM
5 Reserved
6 ISTOP
7 Reserved
8 ICONT
9 IPARAM
ICTRL contains all control inputs which are written by BATCH.
IREADY, ILOCK and IREFRESH are used by the user program and are therefore not
available in ICTRL.

BATCH interface blocks
2.1 IEPH
SIMATIC BATCH Interface Blocks V7.1
Function Manual, 03/2009, A5E02171101-01 13
Allocation of the status words USTAT_L and QUSTAT_L
Bit Meaning Remark Set if
0 IDLE the static state is "inactive"
1 RUNNING the static state is "active"
2 COMPLETED the static state is "completed"
3 HELD the static state is "held"
4 ABORTED the static state is "aborted"
5 READY the static state is "read to complete" IREADY = 1
6 STOPPED the static state is "stopped"
7 Free -
8 Free -
9 STARTING Transient state "starting"
10 RESUMING Transient state "resuming"
11 COMPLETING Transient state "completing"
12 HOLDING Transient state "holding"
13 ABORTING Transient state "aborting"
14 STOPPING Transient state "stopping"
15 Free -
16 Reserved (for SFC: Manual/Automatic mode requested)
17 QCMOD Identifier: Manual/Automatic
(1 = automatic)
18 BA_EN Identifier: BATCH enable
(1 = enabled)
BA_EN = 1
19 STEP_RT Runtime exceeded identifier Q_STEP_T > STEP_T
20 Reserved (for SFC: Operator request transition)
21 REFRESH Trigger for reading setpoints / actual values IREFRESH = 1
22 LOCK Identifier: Start lock (1 = locked) ILOCK = 1
23 CONTINUOUS Identifier: Continuous mode ICONT = 1
24 OCCUPIED Identifier: BATCH allocation
(1 = occupied)
OCCUPIED = 1
25 PROC_ERR (for SFC: Process error)
26 Reserved (for SFC: Execution error)
27 Reserved (for SFC: Step runtime error)
28 Reserved (for SFC: Configuration error)
29 Reserved (for SFC: Operator input error)
30 Reserved (for SFC: External error)
31 ERROR Group error

BATCH interface blocks
2.1 IEPH
SIMATIC BATCH Interface Blocks V7.1
14 Function Manual, 03/2009, A5E02171101-01
Rules for setting the status bits
● The static states ´represent the most important data in BATCH. The transition states are
optional. The RUNNING state may be activated directly after the IDLE state, for example.
● Only one static state and one transition state may be active simultaneously.
Example:
allowed: HELD only
allowed: ABORTING on its own
allowed: HELD and ABORTING (useful in order to be able to detect the original state)
not allowed: HELD and ABORTED
not allowed: HOLDING and ABORTING
Note
Exception: The READY state may be generated at another static state if the IREADY input is
used.
● A group error (bit 31) may be set in addition to any other state.
● The corresponding USTAT_L bit does not have to be set for entries in the "set if" column.

BATCH interface blocks
2.1 IEPH
SIMATIC BATCH Interface Blocks V7.1
Function Manual, 03/2009, A5E02171101-01 15
Batch messages
The associated values are occupied by the block as follows:
Associated value 1 = batch name UBA_NAME
Associated value 2 = step number USTEP_N0
Associated value 3 = batch ID UBA_ID
Block parameters Value Event Message class
QUSTAT_L bit 1 1 Function is active Status message - AS
QUSTAT_L bit 2 1 Function terminated Status message - AS
QUSTAT_L bit 3 1 Function in hold Status message - AS
QUSTAT_L bit 4 1 Function aborted Status message - AS
QUSTAT_L bit 5 1 Phase ready to complete Status message - AS
QUSTAT_L bit 6 1 Function stopped Status message - AS
QUSTAT_L bit 17 0 Function in manual mode Status message - AS
QUSTAT_L bit 18 0 Function not enabled for BATCH Status message - AS
QUSTAT_L bit 18 1 Operation enabled for BATCH Status message - AS
QUSTAT_L bit 19 1 Function exceeded runtime Status message - AS
QUSTAT_L bit 31 1 Function error AS process control system message

BATCH interface blocks
2.1 IEPH
SIMATIC BATCH Interface Blocks V7.1
16 Function Manual, 03/2009, A5E02171101-01
2.1.2 Operator Control and Monitoring of IEPH
Controlling and Monitoring of IEPH
The following table shows the assignment of the parameters of the IEPH block to the
input / output fields of the corresponding faceplate for the following views:
● Function
● Charge
● Setpoints
● Materials
Representation Input/output field User authorization Block parameters
"Status" display - QUSTAT_L
LED "Runtime error" - QUSTAT_L bit 19
"Error" LED - QUSTAT_L bit 31
LED "Manual" - QUSTAT_L bit 17
(if = 0)
Buttons "T", "H", B": Status in string,
hexadecimal, and binary format
- -
Operation and display "Function"
Enable for BATCH BA_EN bit 18
Occupy OCCUPIED bit 24
"Start" Button ISTART or ICTRL bit 0
"Cancel" button IABORT or ICTRL bit 2
"Stop" button ISTOP or ICTRL bit 6
"Hold" button IHOLD or ICTRL bit 1
"Terminate" button ITERM or ICTRL bit 4
"Reset" button IRESET or ICTRL bit 3
Function
"Resume" button
Can only be operated if
no batch is enabled and
occupied and if WinCC
has set user authorization
level 5 or 6.
ISTART or ICTRL bit 0

BATCH interface blocks
2.1 IEPH
SIMATIC BATCH Interface Blocks V7.1
Function Manual, 03/2009, A5E02171101-01 17
Representation Input/output field User authorization Block parameters
"Status" display - QUSTAT_L
Buttons "T", "H", "B"
Status in string, hexadecimal,
and binary format
- -
Operation and display "Batch"
Enable for BATCH - BA_EN bit 18
Occupy - OCCUPIED bit 24
Batch no. - VBA_ID
Batch name - VBA_NAME
Step no. - VSTEP_NO
Step time - STEP_T
Number of loops - VLOOP_I
Batch
Average number of steps - Q_STEP_T
Representation Input/output field User authorization Block parameters
Enable for BATCH - BA_EN bit 18 Setpoints
Tabular display of setpoints,
for example, setpoint, actual
value, unit and parameter
name.
- Each row of the list box represents an
IEPAR_ block which is interconnected at input
EPE_CONN.
Representation Input/output field User authorization Block parameters
Enable for BATCH - BA_EN bit 18 Materials
Tabular display of materials: lists
all outputs of the IEPAR_PI and
IEPAR_PO blocks
- Each list box represents an insertion material
or a material yield.
Creating user authorizations
The operator enable option must be set to "Yes" in the "Other" section of the "Properties" tab
in the object properties dialog of the IUNIT and IEPH/IEOP faceplates.
The operator must also be authorized to control an object. The access security levels for
operators are set up by means of the User Administrator in WinCC Explorer:
● Operator input must be enabled at authorization level 5 (process control) or 6 (higher-
priority process control).
● The access security levels can be assigned as follows:
– generally for all units ("Enable" column in the User Administrator)
– unit-specific ("<unit name>" column in the User Administrator)

BATCH interface blocks
2.1 IEPH
SIMATIC BATCH Interface Blocks V7.1
18 Function Manual, 03/2009, A5E02171101-01
Using a template to create a batch faceplate
Graphics Designer (WinCC-Explorer) provides a template for selecting batch faceplates in
PCS 7 OS pictures.
1. Open the required process picture in Graphics Designer.
2. Open the "@Template_Batch.pdl" template file by selecting the File > Open command.
3. Use the "IEPH" block icon to visualize technical functions in the faceplate.
4. Select the block icon from the template file and then copy it to your process picture.
5. Select the block icon in your process picture.
6. Double-click the PCS 7 function "Interconnect faceplate with process tag" in "Standard
dynamics" in the Dynamic Wizard window.
7. Click "Continue" in the Dynamic Wizard, and then click the search function "...".
8. The variable selection dialog displays all instantiated blocks. Select the required block,
and then click OK > Continue > Finish.
Result: You have successfully installed the "IEPH" block icon for calling the corresponding
faceplate in the process picture you edited.

BATCH interface blocks
2.1 IEPH
SIMATIC BATCH Interface Blocks V7.1
Function Manual, 03/2009, A5E02171101-01 19
2.1.3 I/Os of IEPH
I/Os of IEPH
I/O (parameter) Meaning Type Default Type Attribute OCM Valid
values
BA_EN BATCH - occupy enable Bool 1 I +
EPE_CONN Interconnection with
IEPAR blocks
DInt 0 O -
F_TYPE Name of the phase type String[16] ‘‘ I +
IABORT Operator input: Abort Bool 0 IO +
ICONT Sets the CONTINUOUS
ID in the status word
Bool 0 IO +
ICTRL Control word for operator
inputs
DWord 0 I Q +
IHOLD Operator input: Hold Bool 0 IO +
ILOCK Sets the start lock ID in
the status word
Bool 0 IO +
IPARAM New parameter set from
batch control
Bool 0 IO +
IREADY Sets the READY status
bit in the status word
Bool 0 IO +
IREFRESH Sets the REFRESH ID in
the status word
Bool 0 IO QU +
IRESET Operator input: Reset Bool 0 IO +
ISTART Operator input: Start Bool 0 IO +
ISTOP Operator input: Stop Bool 0 IO +
ITERM Operator input: Complete Bool 0 IO +
OCCUPIED BATCH allocation ID Bool 0 I U +
Q_OCCUPI Copy of OCCUPIED Bool 0 O -
Q_STEP_T Process value of step run
time
DInt 0 O U +
QABORT Copy of IABORT Bool 0 O -
QBA_EN Copy of BA_EN Bool 1 O +
QCONT Copy of ICONT Bool 0 O -
QHOLD Copy of IHOLD Bool 0 O -
QLOCK Copy of ILOCK Bool 0 O -
QPARAM Copy of IPARAM Bool 0 O -
QREADY Copy of IREADY Bool 0 O -
QREFRESH Copy of IREFRESH Bool 0 O -
QRESET Copy of IRESET Bool 0 O -
QSTART Copy of ISTART Bool 0 O -
QSTOP Copy of ISTOP Bool 0 O -
QTERM Copy of ITERM Bool 0 O -
QUSTAT_L Status word output DWord 0 O +

BATCH interface blocks
2.1 IEPH
SIMATIC BATCH Interface Blocks V7.1
20 Function Manual, 03/2009, A5E02171101-01
I/O (parameter) Meaning Type Default Type Attribute OCM Valid
values
STEP_T Setpoint for step run time
in seconds
DInt 0 I U +
UBA_ID Batch ID DWord 0 I +
UBA_NAME Batch name String[32] ‘‘ I +
ULOOP_I Number of step
activations
(for loops)
Word 1 I U +
USTAT_L Status word input DWord 0 I Q -
USTEP_NO Step number in the recipe DWord 0 I U +
VBA_ID Copy of UBA_ID DWord 0 O +
VBA_NAME Copy of UBA_NAME String[32] ‘‘ O +
VLOOP_I Copy of ULOOP_I Word 0 O +
VSTEP_NO Copy of USTEP_NO DWord 0 O +
See also
Overview of the Block Description (Page 5)