Language Elements for

PS 4-150/-200/-300 and PS 416

Sucosoft S 40
Programming Software

02/00 AWB 2700-1306 GB

1st published 1997, edition 12/97
2nd published 1998, edition 06/98
3rd published 1998, edition 11/98
4th published 1999, edition 03/99
5th published 1999, edition 06/99
6th published 2000, edition 02/00
See list of revisions on page 2
© Moeller GmbH, Bonn
Authors: Karl-Heinz Arndt, Jürgen Herrmann, Eberhard Kastner
Editors: Annette Scholz, Thomas Kracht
Translators: Terence Osborn
 Contents

Contents 1
About This Manual 3
1 Sucosoft Program Structure 5
2 Variable Declaration 7
Data types 7
Variables 15
Instancing of function blocks 27
3 Instruction Section of a POU 29
Instruction set 29
Constants 59
Program 64
Function 65
Function block 67
4 Graphical Programming Languages 73
Introduction 73
Programming in LD 77
Programming in FBD 90
5 Functions 109
6 Function Blocks 203
7 Language Extension 555
Appendix 561
Sucosoft agreements 561
Limit values of Sucosoft 563
Program examples LD/FBD 564
Index 583
02/00 AWB 2700-1306 GB

1
 List of revisions for AWB 2700-1306 GB
The following modifications have been made since
the 06/99 edition:

Page Description new Modified

The PS 416 function blocks CAlarm, FAlarm and TAlarm have been removed. The function blocks Counter-
Alarm, EdgeAlarm and TimerAlarm should now be used for all PLCs.
25 RETAIN ⫻
27 Table, Var_In_Out ⫻
29 ADD ⫻
68 Table, Write input ⫻
158 Description, 2nd paragraph ⫻
181 Example, top ⫻
257 5th paragraph and last paragraph ⫻
258 2nd paragraph ⫻
277 1st paragraph ⫻
287 1st paragraph ⫻
312 Last paragraph ⫻
356 Task of the function block ⫻
405 Error codes with PS 4-200 only ⫻
415 Error codes ⫻
430 ff. SCO ⫻
525 1st paragraph ⫻
562 Keywords ⫻
553 Table, 1st line ⫻ 02/00 AWB 2700-1306 GB

2
 About This Manual

The “Language Elements” manual describes the

programming language as per IEC1131-3, including
functions and function blocks.
The language elements are identical for all controllers
and CPUs in the PS 4 and PS 416 series of
equipment. There may however be differences in the
descriptions due to variations in the memory sizes of
the controllers, or data types supported or a different
I/O system. In such cases your attention will be
drawn to the differences by means of marginal
comments or footnotes. “PS 4-200“ stands here for
controllers PS 4-201-MM1,PS 4-271-MM1,
PS 4-151-MM1 and PS 4-141-MM1, “PS 4-300“
stands for the PS 4-341-MM1 controller. References
to “PS 416” include all CPU types: in other words,
“CPU-200“, “CPU-300“ and “CPU-400“.
Unless explicitly indicated by comments, all
descriptions apply to all controller and CPU types.
02/00 AWB 2700-1306 GB

3
4
02/00 AWB 2700-1306 GB
 1 Sucosoft Program Structure

The Sucosoft programming languages correspond to

Part 3 of the IEC 1131 Standard. This description
presents the language elements.
Three types of program organisation units (POUs)
are available for structuring a user application:
program
function
function block.
Sucosoft provides a series of standard functions and
standard function blocks for common tasks:
Functions and function blocks which are defined
in the IEC 1131-3 Standard are marked with an
IEC symbol in the description of the functions and
function blocks.
Manufacturer-specific functions and function
blocks are marked with a KM symbol in the
description of the functions and function blocks.
When a structured program is being processed, the
invoking POU (program, function or function block)
will be interrupted and the program process
continued in the invoked POU (function or function
block). The invocation can be absolute or
conditional, depending on the current result (CR).
Every POU consists of a declaration section and an
instruction section. All data elements which are used
in an instruction section must be declared in the
02/00 AWB 2700-1306 GB

declaration section. The variable declaration of

different data types is carried out in the individual
declaration blocks which are entered before the
instruction section.

5
 Sucosoft Program
Structure

The program can also contain comments which are

entered between the character combination (* and *).
Comments can be nested. This means that
comments can include further comments.
This makes commenting of program sections easier.
The content of a POU is enclosed in keywords:
PROGRAM...END_PROGRAM or
FUNCTION...END_FUNCTION or
FUNCTION_BLOCK...END_FUNCTION_BLOCK.
The following program example contains the
typical elements of a POU
PROGRAM exp_pou
(* Declaration section*)
VAR
Memory_1 : SR; (* Declaration of the FB"SR" as Memory_1*)
ON AT %I0.0.0.0.0 : BOOL; (* Declaration of variables*)
OFF AT %I0.0.0.0.1 : BOOL;
Enable : BOOL;
Start : BOOL;
. (* Declaration of further variables*)
.
END_VAR
(* Instruction section*)

CAL Memory_1( Set1 := ON (* FB invocation with parameter setting*)

ReSet := OFF)
LD Memory_1.Q1
ST Enable
. (*Program continued*)
.

END_PROGRAM (*End of program*)

02/00 AWB 2700-1306 GB

6
 2 Variable Declaration

Data types The IEC 1131-3 Standard defines elementary and

derived data types.
The keywords for designating data types can be
written in upper or lower case letters.

Elementary data types

The elementary data types are predefined data types
which are identified by means of keywords. The
initialisation value of a data type is defined by the
assignment operator “:=”. If no initialisation value is
assigned, the default value 0 will be assigned for
numeric data types.
02/00 AWB 2700-1306 GB

7
 Variable Declaration

Key word Data type Bits Default value

BOOL Boolean number; accepts value 1 or 0 corresponding to TRUE 1 0
or FALSE
SINT Short Integer; with the value range 8 0
-128 to +127
INT Integer; with the value range -32768 to +32767 16 0
1)
DINT Double Integer; with the value range -2147483648 to 32 0
+2147483647
USINT Unsigned Short Integer; with the value range 0 to 255 8 0
UINT Unsigned Integer; with the value range 0 to 65535 16 0
UDINT1) Unsigned Double Integer; with the value range 0 to 32 0
4294967295
REAL1) Real number with the value range ±3.4 E ±38 32 0.0
TIME Duration – T#0s
Specified in days, hours, minutes or milliseconds
Value range –129d +1 ms to +128 –1 ms;
For PS 4-200: –65d +1 ms to +64d –1 ms
in conjunction with time arithmetic operations 0d to 64d –1 ms
DATE Calendar date in format YYYY-MM-DD – D#1900-01-01
TIME_OF_DAY Time in format HH:MM:SS – TOD#00:00:00
DATE_AND_TIME Date and time – DT#1900-01-01-
00:00:00
2)
STRING Character string of variable length ' ' (empty string)
BYTE Bit sequence of 8 bits 8 0
WORD Bit sequence of 16 bits 16 0
1)
DWORD Bit sequence of 32 bits 32 0

1) Applies to PS 4-300, PS 416

2) The default length of a character string is 32 characters.
If another length is required, this must be defined
between parentheses in the declaration,
06/99 AWB 2700-1306 GB

e. g. text : STRING (12) := ’ABC’;

Max. string length: 253 characters for PS 4-200
1024 characters for PS 4-300,
PS 416

8
 Data types

If various data types are possible for one operand,

they are entered in the following structure:

The data type ADDRESS as well as the category

designation ANY in conjunction with data types
cannot be used for the declaration of derived data
types, variables, parameters, functions or function
blocks. ’Generic’ data types of this kind are only
provided with input and output parameters of
manufacturer functions and function blocks.
BOOL R_EDGE and BOOL F_EDGE
(only PS 4-200, PS 4-300)
The data types BOOL R_EDGE (rising edge) and
BOOL F_EDGE (falling edge) are provided in the
Elementary Data Types list box or can be entered
directly in the variable declaration. The two edge-
triggered data types can only be used as input
variables (VAR_INPUT) for user-defined function
06/99 AWB 2700-1306 GB

blocks. If the value is present at the input during a

rising or falling edge, the input declared with
R_EDGE and F_EDGE is high for the next call.

9
 Variable Declaration

Derived data types

Derived data types are special manufacturer or user-
defined data types derived from elementary data
types and which have been assigned a new name.
They are declared within the keywords
TYPE...END_TYPE and can thus be used with the
new names in variable declarations.
Example of derived data types
Declaring derived data types enables you to create
your own terms for the designation of data types in
declaration blocks VAR...END_VAR. Here, for the
data type INT, the term analog_value is defined:
TYPE
analog_value : INT;
END_TYPE

VAR
Value1: analog_value;
END_VAR

Derived data types are only known in the POU

containing the corresponding type definition. They
cannot therefore be used for declaring function and
function block parameters or for global and external
variables. This is only possible with global data types
that are valid for the entire project.
To define derived data types for an entire project,
declare these with the editor for global types (see
“S 40 user interface“ manual, AWB 2700-1305 GB).
02/00 AWB 2700-1306 GB

10
 Data types

Declaration of a data type with restricted value

range
The use of derived data types enables you to restrict
the value range for the used data type.

If values beyond the value range are assigned,

the nearest limit value is automatically used. This
applies to all defined initial values.
Example: value range –128 ... 128. If the value
256 is assigned, 128 will be used instead.

Example of restricted value ranges

Here the data type INT is not defined within the full
range of values –32768 to +32767. Due to the
assignment of the derived data type ’Temperature’
the variable ’BoilerTemperature’ can only take on
values falling within the range –10 to +10. A similar
restriction applies to the variables ’MeasValue1’ and
’MeasValue2’.
TYPE
analog_VALUE_1 : INT (-128..128);
Voltage : INT (0..150);
Temperature : INT (-10..10);
END_TYPE

VAR
MeasValue1 : analog_VALUE_1;
MeasValue2 : Voltage;
BoilerTemperature : Temperature;
END_VAR

The limit values are entered by using two dots

without spaces to separate them. The positive
numbers can be shown without the + sign.
02/00 AWB 2700-1306 GB

11
 Variable Declaration

Declaration of a data type as enumeration

The declaration of an enumerated data type defines
a list of identifiers whose values may contain a data
element. Enter the variable list in parentheses after
the name in order to declare the enumerated data
type; the individual elements must be separated with
a comma. Enter the initialisation value after the “)”
parenthesis. If an initialisation is not made within the
declaration, the data element will be assigned the
value of the first element in the enumeration list when
processing the program for the first time.
Example of type initialization
The type ’Traffic lights’ can take one of the three
states ’red’, ’amber’ or ’green’. A variable is
initialized with the state ’Amber’. If there is no
initialisation the variable would automatically take on
the value of the first element - i. e. the state ’Red’.
TYPE traffic_lights:
(red,
amber,
green):= amber;
END_TYPE

VAR
Main_street1 : Traffic_lights;
Side_street1 : Traffic_lights;
Side_street2 : Traffic_lights;
Car_stop : BOOL;
END_VAR

The defined, permitted elements can be used directly

in the instruction section of the program.
Example IL
LD Main_street1
EQ red
02/00 AWB 2700-1306 GB

ST Car_stop

12
 Data types

Declaration of a data type as array

Various data elements of the same type can be
combined into an array which can consist of
elementary or derived data types. The data type is
declared with the keyword ARRAY and the definition
of the number of array elements and the data type
involved.
Array variables may be assigned with a direct
address. For this assign an array with an initial
address, e. g. with %IB0.0.0.0 via the AT keyword or
in the address field of the Syntax-Controlled Variable
Editor. See also page 17.
Example of declaring a data array
This declaration makes the Array1 variable into a
data array with five data elements of type INT.
The Array2 variable is a three-dimensional data array
with 24 data elements.
The data element of Array2 which is initialized with
the value 17 is overwritten with the value 5.
PROGRAM ex_array
TYPE
Array_5_INT: ARRAY [1..5] OF INT:=[1,13,5,34,2];
Array_24_INT:ARRAY [1..2,1..3,1..4] OF INT
:=[[[3,7,2,9],[2,8,6,1],[5,7,2,17]],
[[2,3,0,5],[6,1,2,4],[3,0,1,4]]];
END_TYPE

VAR
Array1 : Array_5_INT;
Array2 : Array_24_INT;
END_VAR
.
.
LD 5
ST Array2 [1,3,4]
02/00 AWB 2700-1306 GB

.
END_PROGRAM

13
 Variable Declaration

Declaration of a data type as structure

(PS 416, PS 4-300 only)
Several data elements of different types can be
grouped into a single structure. A structure may
consist of elementary or derived data types.
A structure is declared with the keyword STRUCT
and a list of the structure elements specifying their
data types.
To access a structure element in IL, enter the variable
name declared as structure and – separated by a dot
– the name of the structure element.
Example of initialization in the declaration
PROGRAM structure

TYPE
Plant_data :
STRUCT
MeasValue1 : BOOL := 1;
MeasValue2 : INT := -15;
MeasValue3 : UINT := 100;
MeasValue4 : REAL := 10.2;
END_STRUCT;
END_TYPE

VAR
Station1 : Plant_data;
Station2 : Plant_data;
END_VAR

LD Station1.MeasValue3
.
.
END_PROGRAM
02/00 AWB 2700-1306 GB

14
 Variables

Example of initialization after the declaration

TYPE
Plant_data:
STRUCT
MeasValue1 : BOOL;
MeasValue2 : INT;
MeasValue3 : UINT;
MeasValue4 : REAL;
END_STRUCT := (MeasValue1 := 1,
MeasValue2 := -15,
MeasValue3 := 100,
MeasValue4 := 10.2);
END_TYPE

VAR
Station1 : Plant_data;
Station2 : Plant_data;
END_VAR

Assignment of the type ’Plant_data’ causes the

variables ’Station1’ and ’Station2’ to take on the
properties of the structure ’Plant_data’ - in other
words, they are given in each case a data element of
the type BOOL, INT, UINT or REAL.

If initialization parameters are not transferred

during the type declaration of the derived data
types the individual data elements – with the
exception of the type ’Enumeration’ – will be
assigned the type-dependent default values.

Variables Variables are data elements whose content can

change. The variables can be divided into two
groups:
Variables used for temporary storage of internal
data and
02/00 AWB 2700-1306 GB

directly represented variables which are

connected with the inputs and outputs or
specified markers or communication memories of
the PLC.

15
 Variable Declaration

A variable is identified by a name – the identifier.

The name starts with a letter (a–z) or an underline
character and can consist of a string of upper and
lower case letters, numbers and underline
characters.

Spaces and umlauts are not allowed in the

variable names. Keywords must not be used as
variable names.
Variable names have a maximum length of
64 characters. No distinction is made between
upper and lower case.

Directly represented variables

The physical PLC addresses (PLC inputs and
outputs) can also be addressed directly. Directly
represented variables must also be declared.
Symbolic names do not have to be assigned. In this
case the operands are addressed with their physical
addresses – starting with the % character. In the
declaration block the keyword AT is entered before
the physical address – separated by a space.
Example of declaring physical operands
Declaration of physical operands with and without
assignment of a symbolic name
PROGRAM pou4
VAR
AT %I0.0.0.0.0 : BOOL;
Input_1 AT %I0.0.0.0.1 : BOOL;
Result : BOOL;
END_VAR

LD Input_1
02/00 AWB 2700-1306 GB

AND %I0.0.0.0.0
ST Result
END_PROGRAM

16
 Variables

The use of symbolic names with the directly

represented variables as well is recommended.
A modification of the address assignment on the
input I0.0.0.0.0 without symbolic name requires a
correction in the declaration block as well as in the
entire program at all points where the input I0.0.0.0.0
has been used. On the other hand, to change the
address I0.0.0.0.1, you only need to make a
correction in the declaration block since in the
instruction section the symbolic name Input_1
and not the address I0.0.0.0.1 is used.

Directly represented variables must only be used

in the POUs of the type Program.

You can also assign an array to a direct address.

In this case, observe the following requirements:
All array elements must have the same input /
output type, e. g. %I, %Q or %M.
With bit addresses (%IX) the element data type
must be of type BOOL or be derived from this
type.
With byte addresses (%IB) the element data type
must be of type BYTE, SINT or USINT or be
derived from these types.
With word addresses (%IW) the element data
type must be of type WORD, INT or UINT or be
derived from these types.
With double word addresses (%ID), the element
data type must be of type DWORD, DINT, UDINT
or REAL or be derived from these types.
With arrays of BOOL elements for PS 4-200 and
PS 4-300 the number of array elements must be
02/00 AWB 2700-1306 GB

a multiple of 8 and the bit number must always be

set to 0.

17
 Variable Declaration

Example of array declaration on direct variables

VAR
Marker AT %MW0.0.0.4: ARRAY[1..10] of int;
CounterFlags AT %MB0.0.0.50: ARRAY[1..5, 1..3] of usint;
Flags AT %MX0.0.0.7.0: ARRAY[1..16] of bool;
Status AT %ISX1.2.0.0.0: ARRAY[0..7] of bool;
Array AT %MD0.0.0.400: ARRAY[1..2] of REAL;
END_VAR

If directly represented variables are declared as

global variables in the POU Program, they can be
used as external variables in the function block. The
second option is to transfer the variable parameters
to the function block via VAR_IN_OUT.
This is only possible for PLC outputs, markers and
RD, SD communication data.
Sucosoft supports the following physical addresses:
I: Digital input
Q: Digital output
M: Marker
IA: Analog input
QA: Analog output
IC: Counter input
IS: Status information (diagnostics)
Assignment of IS depends on the device; refer
to the respective manual for details.
SD: Send data for intelligent Suconet K stations
RD: Receive data from intelligent Suconet K
stations
02/00 AWB 2700-1306 GB

18
 Variables

The following physical addresses are used for direct

access of inputs/outputs (➞ Chapter 7):
IP: Digital input (PS 4-200/300)
QP: Digital output (PS 4-200/300)
IPA: Analog input (PS 4-300)
QPA: Analog output (PS 4-300)
IPC: Counter input (PS 4-300)
The available addresses depend on the hardware
configured.
The following symbols can be used for Length:
Symbol Meaning Length Example

X or none: Bit 1 bit %IX0.0.0.0.0 or

%I0.0.0.0.0

B: Byte 8 bits %IB0.0.0.0

W: Word 16 bits %QW0.0.0.0

D: Double word 32 bits %ID0.0.0.4

(PS 416 only)

The organisation of the directly represented variables

supported by Sucosoft is shown in the example of
the output operands (Q):
02/00 AWB 2700-1306 GB

19
 Variable Declaration

Multiple declaration on directly represented

variables (PS 4-200 and PS 4-300 only)
The directly represented variables can be declared in
such a way that a variable with a smaller data type
will be located within this variable with a larger data
type.
Example of multiple declaration on variables
The variable 'Bit_Var' in the first declaration forms
the fifth bit in the variable 'Word_Var'. In the second
declaration the variable 'Byte_Var' is the high byte in
the variable 'Word_Var’.
VAR
Bit_Var AT %I0.0.0.0.4:BOOL;
Word_Var AT %IW0.0.0.0:WORD;
END_VAR

VAR
Byte_Var AT %I0.0.0.1:BYTE;
Word_Var AT %IW0.0.0.0:WORD;
END_VAR

Multiple declaration is not supported with the

PS 416.

Variable types
The types of all variables are defined in the
declaration section of a program organisation unit.
All variables that you use in the instruction section of
a POU must be declared in the declaration section.
The individual variable types are identified with
keywords. Variables of the same type are stored in
the declaration block. A declaration block starts with
a keyword, e. g. VAR or VAR_GLOBAL – depending
02/00 AWB 2700-1306 GB

on the variable type – and ends with the keyword

END_VAR. The following table shows the different
variable types and their use:

20
 Variables

Keyword Use

VAR 'Local variable'; valid only within the POU where

it was declared.

VAR_GLOBAL A variable is declared as a 'global variable' if it is

to be used in a program and in all FBs which can be
called by this program. A global variable called up in
a program is known within this program and within
the FBs that are called up by this program.
The variable must be declared with the same
identifier as VAR_EXTERNAL in all invoked FBs in
which this global value is used.

VAR_EXTERNAL If global variable is used within a FB, it must be

declared as 'VAR_EXTERNAL' with the same
identifier (name).

VAR_INPUT Declare an 'input variable' if the variable is to be

read only within a POU (FB, FU) or if it is to be
used for transferring parameters in a function or a
function block. The variable cannot then be changed
in this POU.

VAR_OUTPUT 'Output variable' of a function block

VAR_IN_OUT An IN_OUT variable is read, processed and output

under the same name by the FB. Since an operation
on an IN_OUT variable has a direct effect on the
contents of the transferred variable, this transferred
variable must not be of a type that does not permit
write operations - in other words, e. g. no INPUT
variable or no variable with the attribute CONSTANT.

TYPE Use the keyword 'TYPE' to declare the derived

data types. Derived data types are special data
types which you can derive from the elementary
data types. You can find detailed explanations in
the section 'Derived data types' on page 10.
02/00 AWB 2700-1306 GB

21
 Variable Declaration

Each declaration block must end with the keyword

'END_VAR' – the declaration of derived data types
with the keyword 'END_TYPE’.
VAR_IN_OUT variables are pointers to variables of
types for which they were declared.
VAR_IN_OUT declarations can only be used in
function blocks. They must always be assigned valid
values.
Uninitialised VAR_IN_OUT variables generate a
syntax error when compiled. These pointers (also
called references) must always be given (initialised)
by the invoking POU, even if this was not used for a
particular call.
Pointers must only be allocated in the parentheses of
the FB invocation.
Example of pointer to an array with 201 words
In the following example, the VAR_IN_OUT variable
'w_array' in the function block 'demo' is not an array
of 201 words but a pointer to an array of 201 words.
The 'demo' function block therefore accesses the
global array 'word_array’.
This solution has the following advantages:
When calling 'demo' it is not necessary to copy
an array (runtime saving) and the access to the
VAR_IN_OUT variable is possible for both read
and write operations.
The function block is neutral since EXTERNAL
declarations that are attached to variable names
are not necessary.
02/00 AWB 2700-1306 GB

22
 Variables

PROGRAM user

VAR_GLOBAL
word_array : array[0..200] of word;
END_VAR

VAR
my_function_block : demo;
END_VAR

cal my_function_block(w_array := word_array)

END_PROGRAM

FUNCTION_BLOCK demo

VAR_IN_OUT
w_array : array[0..200] of word;
END_VAR

VAR
Help1 : word ;
Help2 : word ;
END_VAR

ld w_array[100]
st Help1
ld Help2
st w_array[200]
END_FUNCTION_BLOCK
02/00 AWB 2700-1306 GB

23
 Variable Declaration

The declaration of local and global variables can be

supplemented with the following attributes:
Keyword Use
RETAIN Use 'RETAIN' to declare a retentive local or global
variable. Retentive means that with a warm start
the retentively declared variable keeps the last
valid value it had before the stop. 'RETAIN' is
written behind the keyword VAR, VAR_GLOBAL or
VAR_OUTPUT after a space.
CONSTANT If a local or global data element is to be
constant, i. e. the contents cannot be changed,
the attribute 'CONSTANT' is used. Place the
attribute CONSTANT behind the keyword VAR,
VAR_GLOBAL or VAR_OUTPUT and after a space.
AT If you require a variable with the assignment to
a physical address – a directly represented
variable – identify the variable with AT in the
declaration block.

With the PS 4-200 marker variables are not made

retentive by the attribute RETAIN; they are
directly assigned to a marker from the range
defined as retentive. The retentive marker range
is defined during code generation under
Generate ➝ Program Parameters.
With the PS 4-300 retentive markers can be set
using both the RETAIN keyword and via
Configure PLC.

If variables of a function block for PS 4-200 controller

are to be used as retentive variables, this will not be
possible in relation to individual variables. In this
case the instance of the function block must be
declared as retentive.
02/00 AWB 2700-1306 GB

24
 Variables

Example of retentive declaration with RETAIN

Declaration of a retentive data element, of a retentive
function block and of a constant data element:
VAR RETAIN
CounterValue : UINT;
END_VAR

VAR RETAIN
Counter : CTU;
END_VAR

VAR_GLOBAL CONSTANT
ZeroKelvin : INT := -273;
END_VAR

The keyword 'AT' identifies variables with an

assignment to physical addresses. This keyword can
only be used when declaring local and global
variables within a Program POU, e. g.:
VAR
motor1 AT %Q0.0.0.0.3 : BOOL;
END_VAR

Example of assigning physical addresses

Two local variables with the symbolic names 'pump'
and 'valve' and a global variable with the symbolic
name 'setpoint' are declared. Two declaration blocks
are necessary.
VAR_GLOBAL (*Declaration block*)
setpoint: INT:=25; (* of type global*)
END_VAR

VAR (*Declaration block*)

pump AT %Q0.0.0.0.3: BOOL;(* of type local*)
valve AT %Q0.0.0.3.1: BOOL;
END_VAR

If a directly represented variable without a symbolic

02/00 AWB 2700-1306 GB

name is used in the declaration, e. g. %Q0.0.0.0.3,

the output in the instruction section will be directly
addressed under %Q0.0.0.0.3.

25
 Variable Declaration

The following table shows the use of the individual

types of variables in the three POU types:
Use of FU FB PRG Global
variable types types

Var_Input ✓ ✓

Var_Output ✓

Var_In_Out ✓

Var_Global ✓

Var_External ✓

Var ✓ ✓ ✓

Type ✓ ✓ ✓ ✓

Pay attention to the order:

VAR must not be placed in front of VAR_INPUT,
VAR_OUTPUT, VAR_IN_OUT.

02/00 AWB 2700-1306 GB

26
 Instancing of function
blocks

Instancing of function If a function block is to be called up in another

blocks function block or a program, it is necessary to create
an instance of it, i. e. the function block must be
assigned a user-defined name. Assign the instance
name in the declaration section of the invoking POU,
e. g:
Counter1 : CTU;

The Counter1 variable is thus declared as a function

block of type CTU. Set the parameters for the input /
output variables when the function block is called.
Unlike a function, you only need to set the
parameters for the input variables which are relevant
for the application. An exception to this is input
variables of the type VAR_IN_OUT, for which the
parameters have to be set with every call. If this does
not happen, a syntax error will be reported.
02/00 AWB 2700-1306 GB

27
28
02/00 AWB 2700-1306 GB
 3 Instruction Section of a POU

Instruction set Operator Operand Meaning

type

LD ANY Copies the operand value into the working

register

LDN ANY_BIT Copies the negated operand value into the

working register

ST ANY Sets the operand value to the current result

(CR)

STN ANY_BIT Sets the operand value to the negated value

of the current result

S BOOL Sets boolean operand value to 1 if the

current result is 1

R BOOL Resets boolean operand value to 0 if the

current result is 1

AND1) ANY_BIT Boolean AND

&1) ANY_BIT Boolean AND

ANDN1) ANY_BIT Boolean AND, negated

1)
&N ANY_BIT Boolean AND, negated
1)
OR ANY_BIT Boolean OR

ORN1) ANY_BIT Boolean OR, negated

XOR1) ANY_BIT Boolean Exclusive OR

1)
XORN ANY_BIT Boolean Exclusive OR, negated
1)
ADD ANY_NUM Addition
1)
Instruction can be used in conjunction with a “(”
02/00 AWB 2700-1306 GB

parenthesis if required (deferring the operation).

The instruction then refers to the result of the
parenthesis expression, i. e. operand sequence.
The deferred operation is continued after the “)“.

29
 Instruction Section of a
POU

Operator Operand Meaning

type

SUB1) ANY_NUM Subtraction

1)
MUL ANY_NUM Multiplication

DIV1) ANY_NUM Division

GT1) ANY Comparison greater than

1)
GE ANY Comparison greater than or equal to
1)
EQ ANY Comparison equal

NE1) ANY Comparison not equal

LE1) ANY Comparison less than or equal to

1)
LT ANY Comparison less than

JMP Label Unconditional jump to label

JMPC Label Jump to label with current result 1

JMPCN Label Jump to label with current result 0

CAL Instance Unconditional invocation of a function block

name

CALC Instance Invocation of a function block with current

name result 1

CALCN Instance Invocation of a function block with current

name result 0

RET – Unconditional return

RETC – Return with current result 1

RETCN – Return with current result 0

The letter N at the end of the instruction identifies

the Boolean negation of the operand, e. g. the
instruction
02/00 AWB 2700-1306 GB

1)
Instruction can be used in conjunction with a “(”
parenthesis if required (deferring the operation).
The instruction then refers to the result of the parenthesis
expression, i. e. operand sequence. The deferred
operation is continued after the “)“.

30
 Instruction set

LDN %I 0.0.0.0.0 with status 1 at input I0.0.0.0.

causes a 0 to be entered in the working register.
The instruction sequences must be structured
according to defined rules. The permissible
instruction sequences are explained in detail in the
sections 'Programming rules' and 'Description of the
instructions' (see below in this chapter).

Structure of an instruction
Label Operator Operand Comment

L1: LD %I0.0.0.0.1 (*Loading an input into the

working register*)

Label Identifies an instruction as jump target

(optional).
Operator Depending on the function, one of the
above-mentioned instructions is used.
Operand Variable name; depending on the
declared variable type, the variable
name is the symbolic name; with
directly represented variables the
symbolic name or the physical address
(e.g. %I0.0.0.0.1).
Comment The comment provides more detailed
information on the executed operation.
02/00 AWB 2700-1306 GB

31
 Instruction Section of a
POU

Programming rules
An IL sequence starts with a load instruction (LD or
LDN) and is valid until a new load instruction is used.
This does not apply to unconditional function block
calls and jump / return operations).
IL sequences (overview)
The following syntax chart shows an overview of all
IL sequences for all instruction groups. The use of
the individual instruction groups is explained with
detailed diagrams for each respective group.

End of line

Load instruct.

Label definit
Assignment

Instruct. with parentheses Set/reset

Conditional jump
Instruct. without parenth.

FB invocation

FU invocation
Conditional return

Uncond. FB invocation

Unconditional jump

Unconditional return
02/00 AWB 2700-1306 GB

32
 Instruction set

Use of logical, arithmetical and comparison

operations
Instructions without brackets:

Instructions with brackets:

Arithmetic operators ( Operand )

Comparison operators

Logic operators Instruction with parentheses

Instruction without parenth.

FU invocation

Allocation

Set/reset

Label definition
Labels are used as jump targets. They are entered at
the beginning of an instruction and may only be
positioned at the beginning of a sequence.
02/00 AWB 2700-1306 GB

33
 Instruction Section of a
POU

Description of the instructions

Load instructions

LD Permitted data types: all

Load
Description
The value of the entered operand is loaded into the
working register. The original content of the working
register is overwritten. The operand is not changed.
The data type of the stated operand defines the
permitted data type for the following operand in this
sequence.
Examples
Operation Operand Comment
status

LD %I0.0.0.0.5 1 The signal status 1 on the

I0.0.0.0.5 input is loaded into
the working register

LD %IB0.0.0.0 11010100 The bit pattern at input byte

IB0.0.0.0 is copied directly into
the working register; the
working register contains
11010100.
02/00 AWB 2700-1306 GB

34
 Instruction set

LDN Permitted data type: ANY_BIT

Load negated
Description
The negated value of the entered operand is loaded
into the working register. The original content of the
working register is overwritten. The data type of the
stated operand defines the permitted data type for
the following operand in this sequence.
Example
Operation Operand Comment
status

LDN %I0.0.0.0.3 1 The signal status at input

I0.0.0.0.3 is negated and
loaded into the working
register;
the working register is set to 0.
02/00 AWB 2700-1306 GB

35
 Instruction Section of a
POU

Assignments
ST Permitted data types: all
Store instruction
Description
The content of the working register is assigned to the
entered operand. The original value of the operand is
overwritten. The data type of the entered operand
must be the same as the data type of the data
element in the working register. The data type of the
working register content is defined by the data type
of the variables that is assigned a value first. Further
assignments can only be carried out with variables of
the same data type. It is possible for one assignment
to follow another one (see syntax chart on Page 32).
Examples
Operation Status working Comment
register

ST %Q0.0.0.0.0 1 The status 1 of the working

register is assigned to the
Q0.0.0.0.0 output.The
previous operation forming the
current result must provide a
Boolean result.

ST Result1 1001100100001111 The bit pattern in the working

register is copied into the
Result1 variable which must
be of type WORD.

LD 17 The variables Value1 and

ST Value1 Value2 receive the value 17.
ST Value2 They must be of the same data
type.
02/00 AWB 2700-1306 GB

36
 Instruction set

STN Permitted data type: ANY_BIT

Store negated
Description
The negated content of the working register is
assigned to the operand entered. The original value
of the operand is overwritten. The data type of the
entered operand must be the same as the data type
of the data element in the working register. The
working register is not changed by the assignment
instruction. A STN instruction can be followed by
another ST or STN instruction (see syntax chart on
Page 32).
Example
Operation Status Comment
working
register

STN %Q0.0.0.0.1 1 The negated status 1 of the

working register is assigned to
output Q0.0.0.0.1 which
receives the value 0. The
previous operation forming the
current result must provide a
Boolean result.
02/00 AWB 2700-1306 GB

37
 Instruction Section of a
POU

Bistable data element

A bistable data element can be set to 1 by a fulfilled
set condition, or it can be set to 0 by a fulfilled reset
condition. The status is active until the condition is
fulfilled for the opposite status. If both conditions are
fulfilled at the same time, the data element accepts
the status for which the condition was last
processed. This is called priority setting or resetting.

S Permitted data type: BOOL

Set
Description
The entered operand is set if the content of the
working register is 1. If this set condition is not
fulfilled, the operand will not be changed.
The working register is not changed.
Example
Operation Operand Comment
status

LD %I0.0.0.0.0 1 If input I0.0.0.0.0 has status 1,

output Q0.0.0.0.0 is set. The 0
S %Q0.0.0.0.0 1 status at input I0.0.0.0.0 has no
effect on this output. Only a
reset instruction R with fulfilled
reset condition can set the
output status to 0. 02/00 AWB 2700-1306 GB

38
 Instruction set

R Permitted data type: BOOL

Reset
Description
The entered operand is reset if the content of the
working register is 1. If this reset condition is not
fulfilled, the operand will not be changed.
The working register is not changed.
Example
Operation Operand Comment
status

LD %I0.0.0.0.1 1 If the I0.0.0.0.1 input has the

status 1,
R %Q0.0.0.0.0 1 the Q0.0.0.0.0 output receives
the status 0. The status 0 on the
I0.0.0.0.1 input has no effect on
this output. Only a set
instruction with fulfilled set
condition can set the output
status to 1.
02/00 AWB 2700-1306 GB

39
 Instruction Section of a
POU

Logic operators

AND, & Permitted data types: ANY_BIT

Description
AND operation linking the entered operand with the
content of the working register. The result is stored in
the working register. The original content of the
working register is overwritten. The operand value is
not changed.
With an AND operation of byte / word operands the
individual bits of the entered operand are sequenced
with the appropriate bits of the working register.

02/00 AWB 2700-1306 GB

40
 Instruction set

Examples
Operation Operand Comment
status

LD %I0.0.0.0.0 1 The status 1 in the working

AND Start 0 register is ANDed with the
status 0 of the variable Start
and the result 0 is assigned to
ST Belt 0 the variable Belt.

LD %IB0.0.0.0 11001100 The individual bits of the bit

pattern 11001100 in the
working register are ANDed
AND %IB0.0.0.1 10101010 with the corresponding bits of
the IB0.0.0.1 input byte and the
result is transferred from the
ST Result 10001000 working register to the variable
Result.
02/00 AWB 2700-1306 GB

41
 Instruction Section of a
POU

ANDN, &N negated Permitted data types: ANY_BIT

Description
With binary operation the content of the entered
operand is negated and is ANDed with the content of
the working register. The result is stored in the
working register. The original content of the working
register is overwritten. The operand value is not
changed.
With a negated AND sequence of byte / word
operands, individual bits of the one's complement of
the entered operand are ANDed with the
corresponding bits of the working register.
The result is stored in the working register.
Examples
Operation Operand Comment
status

LD %I0.0.0.0.1 1 The status 1 in the working

ANDN Start 0 register is ANDed with the
ST Belt 1 negated status of the variable
Start and the result 1 is
assigned to the variable Belt.

LD %IB0.0.0.0 11001100 The individual bits of the

IB0.0.0.0 bit pattern in the
working register are ANDed
with the corresponding bites of
&N %IB0.0.0.1 10101010 the one’s complement of the
IB0.0.0.1 input byte. The
01000100 result is transferred
from the working register to the
variable Result.
ST Result 01000100
02/00 AWB 2700-1306 GB

42
 Instruction set

OR Permitted data types: ANY_BIT

ODER
Description
OR operation linking the entered operand with the
content of the working register.The result is stored in
the working register. The original content of the
working register is overwritten. The operand value is
not changed.
With an OR sequence of byte / word operands the
corresponding bits of each operand involved are
sequenced.
Examples
Operation Operand Comment
status

LD Input1 1 The status 1 of the variable

OR Input2 0 Input1 is ORed with the status 0
of the variable Input2 and the
result 1 is assigned to the
variable OR_Bit.
ST OR_Bit 1

LD Byte_1 11001100 The individual bits of the bit

pattern 11001100 of the
variable Byte_1 are ORed with
the corresponding bits of the
OR Byte_2 10101010 variable Byte_2 and the result is
transferred from the working
register to the variable
ST OR_Byte 11101110 OR_Byte.
02/00 AWB 2700-1306 GB

43
 Instruction Section of a
POU

ORN Permitted data types: ANY_BIT

OR negated
Description
With binary operations the content of the entered
operand is negated and ORed with the contents of
the working register. The result is stored in the
working register. The original content of the working
register is overwritten. The operand value is not
changed.
With a negated OR sequence of byte / word
operands, individual bits of the one's complement of
the entered operand are ORed with the
corresponding bits of the working register.
The result is stored in the working register.
ExamplesXOR
Operation Operand Comment
status

LD Input1 0 The status 0 in the working

register is ORed with the
negated status of the variable
ORN Input2 0 Input2. The result 1 is assigned
to the variable ORN_Bit.
ST ORN_Bit 1

LD Byte_1 11001100 The individual bits of bit pattern

11001100 of the variable
Byte_1 are ORed with the
corresponding bits of the one’s
complement of the variable
ORN Byte_2 10101010 Byte_2. The result is
transferred to the variable
ST ORN_Byte 11011101 ORN_Byte.
02/00 AWB 2700-1306 GB

44
 Instruction set

XOR Permitted data types: ANY_BIT

Exclusive OR
Description
Exclusive OR operation of the entered operand with
the content of the working register. The result is
stored in the working register. The original content of
the working register is overwritten. The operand
value is not changed.
With an Exclusive OR sequence of byte / word
operands, the corresponding bits of each operand
involved are sequenced.
Examples
Operation Operand Comment
status

LD Input1 1 The status 1 of the variable

Input1 is Exclusive-ORed with
XOR Input2 1 the status 1 of the variable
Input2 and the result 0 is
assigned to the variable
ST XOR_Bit 0 XOR_Bit.

LD Byte_1 11101111 The individual bits of the bit

pattern 11101111 of the
variable Byte_1 are Exclusive-
XOR Byte_2 10111110 ORed with the corresponding
bits of the variable Byte_2 and
the result is transferred from
the working register to the
ST XOR_Byte 01010001 variable XOR_Byte.
02/00 AWB 2700-1306 GB

45
 Instruction Section of a
POU

XORN Permitted data types: ANY_BIT

Exclusive OR negated
Description
With binary operations the content of the entered
operand is negated and Exclusive-ORed with the
content of the working register. The result is stored in
the working register. The original content of the
working register is overwritten. The operand value is
not changed.
With a negated Exclusive OR sequence of byte /
word operands the individual bits of the one's
complement of the entered operand are Exclusive-
ORed with the corresponding bits of the working
register. The result is stored in the working register.
Examples
Operation Operand Comment
status

LD Input1 1 The status 1 of the variable

Input1 is Exclusive-ORed with
XORN Input2 1 the negated status of the
variable Input2 and the result 1
is assigned to the variable
ST XOR_Bit 1 XOR_Bit.

LD Byte_1 11101111 The individual bits of bit pattern

11101111 of the variable
Byte_1 are Exclusive-ORed with
XORN Byte_2 10111110 the corresponding bits of the
one’s complement of the
variable Byte_2. The result is
transferred from the working
ST XORN_Byte 10101110 register to the variable
XORN_Byte.
02/00 AWB 2700-1306 GB

46
 Instruction set

Arithmetic operators

ADD Permitted data types: ANY_INT, REAL

Addition (REAL applies to PS 4-300 and PS 416 only)
Description
The entered operand value is added to the content of
the working register and the result transferred to the
working register. The original content of the working
register is overwritten. The operand value is not
changed.
Should the result of addition exceed the range of
values permitted for the data type selected, the carry
will be transferred to the carry register.

The function ADD for the multiple addition of

numeric operands and for adding time values and
addresses is described in Chapter 5, ”Functions“.

Example
Operation Comment

LD 23 The content of the working register is added to the

ADD Summand value of the variable Summand.
ST Sum The result is transferred from the working register
to the variable Sum.
02/00 AWB 2700-1306 GB

47
 Instruction Section of a
POU

SUB Permitted data types: ANY_INT, REAL

Subtraction (REREAL applies to PS 4-300 and PS 416 only)
Description
The entered operand (subtrahend) is subtracted from
the content of the working register (minuend) and the
result is stored in the working register. The original
content of the working register is overwritten.
The operand value is not changed.
Should the result of subtraction exceed the range of
values permitted for the data type selected, the carry
will be transferred to the carry register.

The function SUB for the multiple subtraction of

numeric operands and for subtracting time values
and addresses is described in Chapter 5,
”Functions“.

Example
Operation Comment

LD Minuend The value of the variable Subtrahend is subtracted

SUB Subtrahend from the variable Minuend.
ST Difference The result is transferred from the working register
to the variable Difference.

MUL Permitted data types: ANY_INT, REAL

Multiplication (REAL applies to PS 4-300 and PS 416 only)
Description
The entered operand is multiplied with the content of
the working register where the result is stored. The
original content of the working register is overwritten.
The operand value is not changed.
02/00 AWB 2700-1306 GB

Should the result of multiplication exceed the range

of values permitted for the data type selected the
carry will be transferred to the carry register.

48
 Instruction set

The function MUL for the multiple multiplication

of numeric operands and for multiplying
addresses is described in Chapter 5, ”Functions“.

Example
Operation Comment

LD Multiplicand The value of the variable Multiplier is multiplied by

MUL Multiplier the value of the variable Multiplicand. The result is
ST Product transferred from the working register to the
variable Product.

DIV Permitted data types: ANY_INT, REAL

Division (REAL applies to PS 4-300 and PS 416 only)
Description
The content of the working register (dividend) is
divided by the value of the entered operand (divisor)
and the result (quotient) is stored in the working
register. The original content of the working register
is overwritten. The operand value is not changed.
The remainder is stored in the carry register.

The function DIV for the multiple division of

numeric operands and for dividing addresses is
described in Chapter 5, Functions.

Example
Operation Comment

LD Dividend The value of the variable Dividend is divided by the

DIV Divisor value of the variable Divisor
ST Quotient The result is transferred from the working register
to the variable Quotient.
02/00 AWB 2700-1306 GB

49
 Instruction Section of a
POU

Comparison operators

Permitted data types: ANY_INT, ANY_DATE,

ANY_BIT, STRING, TIME
Description
The following comparison operations are possible:
GT greater than
GE greater than or equal to
EQ equal
LE less than or equal to
LT less than
NE not equal
The entered operand is compared with the content of
the working register. The operand is subtracted from
the value of the working register. The fulfilled
comparison is indicated by the Boolean 1 in the
working register; a 0 indicates an unfulfilled
comparison. The original content of the working
register is overwritten. The operand value is not
02/00 AWB 2700-1306 GB

changed.

50
 Instruction set

The comparison operation involves a type

conversion of the working register, i. e. the working
register is of type ANY_INT before the comparison
and afterwards always BOOL.
The Boolean result of a comparison can be used as
a condition for invoking a function block, a jump to a
jump label, further logic operations or a return from a
POU to the next higher POU level.
Example
Label Operation Comment

LD Number1 The value of the variable Number1 is

EQ Number2 checked for equality with the value of the
JMPC M1 variable Number2. If the comparison is
LD 1 fulfilled, the conditional jump to label M1
ADD Number1 is executed.
ST Number1 The variable Number1 is not incremented
if the comparison is fulfilled.

M1: .
.
02/00 AWB 2700-1306 GB

51
 Instruction Section of a
POU

Unconditional and conditional jumps

JMP Permitted data type: not relevant. In the jump

Unconditional jump instruction the jump target (label) is entered as the
operand.
Description
The program is continued from the point specified as
the jump target (label). The jump target must always
be the start of a sequence which is marked with a
label.
This instruction is to be considered as a sequence
which consists of one instruction.
A jump is only possible within a POU.
Example
Label Operation Comment

M1: LD Number1 The program loop (incrementing the

EQ Number2 variable Number1 and the comparison by
JMPC M2 the variable Number2) is processed until
. the comparison is fulfilled.
.

LD 1
ADD Number1
ST Number1 The unconditional jump to label M1 is
JMP M1 carried out after each incrementation.
M2: .
.
02/00 AWB 2700-1306 GB

JMPC / JMPCN Permitted data type: not relevant. The jump target
Conditional jumps (label) is entered as the operand in the jump.

52
 Instruction set

Description
Conditional jump in conjunction with the Boolean
content of the working register.
JMPC: Jump when 1
If the working register has the value 1, the jump will
be executed and the program will continue from the
specified jump target. If the working register has the
value 0, the jump will not be executed. The program
continues with the next instruction after the jump
instruction.
JMPCN: Jump when 0
If the working register has the value 0, the jump will
be executed and the program will continue from the
specified jump target. If the working register has the
value 1, the jump will not be executed. The program
continues with the next instruction after the jump
instruction.
The jump target must always be a sequence start
which is marked with a label. A jump is only possible
within a POU.
Example
Label Operation Comment

M1: LD Number1 If the comparison condition is fulfilled, the

EQ Number2 working register will have the Boolean
JMPC M2 value 1 and thus represent the fulfilled
jump condition. Program processing is
continued at the jump label M2.
.
. This program section is then skipped.
LD 1
ADD Number1
ST Number1
02/00 AWB 2700-1306 GB

JMP M1
M2: .
.

53
 Instruction Section of a
POU

Unconditional and conditional returns

RET Permitted data type: No operand is entered in the

Unconditional return Return instruction.Description
The RET instruction causes an unconditional return
to the invoking POU, e. g. with a POU “Program”, a
return to the system program. With the return to a
POU the invoking POU is continued at the point at
which the subordinate POU was invoked. The
deferred operations are now processed.
Example
Label Operation Comment

LD Error If Error = 0, the RET instruction is skipped.

JMPCN M1 If Error = 1, RET is executed, i. e. the POU
RET is left and the program is continued in the
M1: . invoking POU.
.

02/00 AWB 2700-1306 GB

54
 Instruction set

RETC / RETCN Permitted data type: No operand is entered in the

Conditional returns Return instructions.
Description
Conditional return in conjunction with the Boolean
content of the working register.
RETC: Return with 1
If the working register has the value 1, the return will
be to the next-higher POU, i. e. with a POU Program
to the system program. If the working register has the
value 0, no return will be executed. The program will
continue with the instruction which follows the return
instruction.
RETCN: Return with 0
If the working register has the value 0, the return will
be to the next-higher POU, i. e. with a POU Program
to the system program. If the working register has the
value 1, the return will not be executed. The program
continues with the next instruction after the return
instruction.
Example
Operation Comment

LD Error If Error = 1, the POU will be quit and the program

RETC continue in the invoking POU.
.
.
02/00 AWB 2700-1306 GB

55
 Instruction Section of a
POU

Unconditional and conditional invocation of

function blocks

CAL Description
Unconditional The program is continued in the function block
invocation of function entered as operand. The unconditional invocation
blocks may only be programmed after a sequence is
completed and is not permitted inside parenthesized
operations.

The direct parameter passing within the function

block call of inputs and outputs with instruction
sequences is a Moeller alternative of the function
block call. More information is given in Chapter 7,
”Language Extension“.

Example
Operation Comment

.
.
ST Output2 After the allocation (end of
CAL Pulse generator_2_Hz (Set:=start, sequence) the invocation of the
period:=time value) function block
pulse_generator_2_Hz is
carried out.
02/00 AWB 2700-1306 GB

56
 Instruction set

CALC / CALCN Description

conditional invocation Conditional function block invocation in conjunction
of function blocks with the Boolean content of the working register.
CALC: FB invocation when 1
If the working register has the value 1, the invocation
of the function block which is entered as the operand
is carried out. If the working register has the value 0,
no function block invocation takes place. The
program is continued with the instruction after the
CALC instruction.
CALCN: FB invocation when 0
If the working register has the value 0, the invocation
of the function block which is entered as the operand
is carried out. If the working register has the value 1,
no function block invocation takes place. The
program is continued with the instruction after the
CALCN instruction.
Example
Operation Comment

.
.
ST Output2
LD Result3 If the Boolean variable Result3 = 1, the
CALC Pulse generator_2_Hz invocation of the function block
(Set:=Start, Pulse_generator_2_Hz will be carried
Period:=Time value) out.
.
.
02/00 AWB 2700-1306 GB

57
 Instruction Section of a
POU

Invocation of functions

The function is invoked by entering its name – there

is no keyword for the invocation. You will find further
information in the section ‘Function’ (Page 65).

02/00 AWB 2700-1306 GB

58
 Constants

Constants If fixed data is used in Sucosoft, the data elements

which are declared with the keyword CONSTANT
can be assigned the desired contents by initiali-
sation. Another possibility is to use constants which
are pre-defined values for direct processing within
the program without using a data element with an
identifier.
Example
The variable Value1 which has been increased by
115 is to be assigned to the variable Value2.
LD Value1
ADD 115
ST Value2

The constants of the individual data types require a

special notation. Underline characters can be used
within a constant; they do not affect the value of the
constant. Spaces may not be used in a constant.
Table 3-1: Constants overview

Constants Example Meaning

IINT -13 iinteger -13

45165 or 45_165 iinteger 45165
+125 iinteger 125

REAL1) -13.12 real number -13.12

123.45 real number 123.45
0.123 real number 0.123
-1.23E-3 exponent notation of
real number -0.00123

Dual number 2#0111_1110 or 126 126 decimal

Octal number 8#123 or 83 83 decimal

Hexadecimal 16#123 or 291 291 decimal

02/00 AWB 2700-1306 GB

number

BOOL 0 and 1 or Boolean zero and one

FALSE and TRUE

STRING 'ABC' Character string ABC

59
 Instruction Section of a
POU

Constants Example Meaning

TIME T#12.3ms or Duration of

TIME#12.3ms 12.3 milliseconds

T#12h34m or Duration of
T#12h_34m 12 hours
and 34 minutes

DATE DATE#1995-12-24 or Date 24.12.1995

D#1995-12-24

TIME_OF_DAY TOD#12:05:14.56 or Time 12 o’clock,

TIME_OF_DAY#12:05:14.5 5 minutes and 14.56
6 seconds

DATE_AND_TIME DT#1995-12-24- Date and time

12:05:14.56 or 24.12.1995,
DATE_AND_TIME#1995- 12 o’clock, 5 minutes
12-24-12:05:14.56 and 14.56 seconds
1) for PS 416 and PS 4-300 only

Duration, time and date are represented by the

keywords which can be written in full, e. g.
TIME_OF_DAY#, or in short, e. g. TOD#.
A constant – string of characters – is a sequence of
individual characters which are enclosed by
apostrophes.
This notation allows all characters apart from the $
character to be represented. The $ character has a
special meaning when representing constants. It is
used for the representation of control characters for
the formatted text output, e. g. $L for the line feed.
The $ character also enables you to represent the
individual characters in their two-digit hexadecimal
form, e. g. $0A for the line feed.
02/00 AWB 2700-1306 GB

60
 Constants

.Pre-defined Meaning
Constants

'$'' Apostrophe '

'$$' The $ character itself

'$L' or '$l' Line feed, hexadecimal $0A)

'$N' or '$n' New line

'$P' or '$p' Form feed

'$R' or '$r' Carriage return

hexadecimal $0D)

'$T' or '$t' Tabulator

Examples
Constants Meaning, length of the
character string

'A' The character A, length 1

'' Space, length 1

'' No character, length 0

'$R$L' Carriage return and line feed, length 2

'$0D$0A' Carriage return and line feed, length 2

02/00 AWB 2700-1306 GB

61
 Instruction Section of a
POU

Use of integer constants in the instruction section

The IEC standard 1131-1 defines three different
kinds of constant for integer values:
Unsigned decimal integers, e. g. 127
Signed decimal integers +3000
Unsigned constant with base value,
e.g. 2#1111_1111.
These three types of constants do not require any
explicit data type definition. The data type is
assigned within the context of the command
sequence it is used in.
The value of these constants can be determined
when they are directly assigned to a fixed variable or
parameter. However, the result will not be clear when
used with operators and overloaded functions with
the input parameters ANY or ANY_INT.

Overloaded functions are functions that can be

used for several data types. Refer to Page 113 for
more information.

Example of “Integer constants“

The instruction sequence in a PS 4-200 program
does not supply the required result -5 but the value
32763.
LD 1
SUB 11
DIV 2
ST int_var

The compiler selects the data type UINT for the

sequence result because of the unsigned decimal
02/00 AWB 2700-1306 GB

integers used. The subtraction causes an overflow.

The result is converted from a binary to a decimal
value when assigned to the INT variable int_var.

62
 Constants

However, a small modification in the example will

ensure the correct result:
LD +1
SUB +11
DIV +2
ST int_var

Observe the following points when working with

integers:
Always use signed constants when working with
signed decimal values.
Always use unsigned constants when working
with unsigned decimal values.
When calling one of the IEC selection functions
LIMIT, MAX, MIN, MUX or SEL avoid using
unsigned and signed constants at the same time.
Use constants with base definitions only in
conjunction with ANY_BIT data types. The IEC
standard knows no binary format for the unique
absolute allocation to decimal values apart from
one exception - the numbers “0” and “1” which
are used to replace FALSE and TRUE.
02/00 AWB 2700-1306 GB

63
 Instruction Section of a
POU

Program A program is the higher-level POU of Sucosoft.

The program contains control instructions and
invocations of other POUs (i. e. functions and
function blocks). Enter a name to call up a function
and the CAL instruction to call up a function block.
When functions and function blocks are called up,
their parameters are set.
Example: Program pou1
Program pou1 with invocation of the SHL function
(Shift left) and the CTU function block (up-counter).
PROGRAM poe1
(* Declaration section *)

VAR
Counter1 : CTU; (* Declaration of the FB CTU as counter1 *)
ShiftNumber AT %IW0.0.0.2: WORD; (* Declaration of variables *)
ShiftPlaces : INT := 2; (* which are used by
function SHL *)
ShiftResult : WORD;
Start AT %I0.0.0.0.0 : BOOL; (* Declaration of further variables *)
AT %I0.0.0.0.1 : BOOL;
Impulse AT %I0.0.0.0.2 : BOOL;
AT %I0.0.0.0.3 : BOOL;
Belt AT %Q0.0.0.0.1 : BOOL;
State : INT;
END_VAR
(* Instruction section *)
LD %I0.0.0.0.1
AND Start
ST Belt
LD ShiftNumber (* FU invocation with parameter setting *)
SHL ShiftPlaces
ST ShiftResult
CAL Counter1(CU := Impulse, (* FB invocation with parameter setting*)
ReSet := %I0.0.0.0.3)
LD Counter1.CV
ST State
02/00 AWB 2700-1306 GB

END_PROGRAM (* End of program *)

64
 Function

Function A function can be used where a POU program

contains control tasks that are repeated several
times. A function can contain several input
parameters but only one output parameter, i. e. the
process can only provide one data element as a
result. This can be a single value – with arrays –
multi-valued.
The function has a global scope; it is thus available
for all POUs and does not therefore need to be
declared in the POU containing the invocation.
A function is called up by entering the function name
and by transferring all necessary input parameters.
The first parameter is transferred to the function via
the working register. Further parameters are entered
after the function name, separated by a comma.
The result of a function process is supplied as a
return value with the name of the function and is
made available for the POU containing the invocation
via the working register.
Functions cannot store information. A function with
the same parameters thus always supplies the same
return value when it is called up.
With every function call, local variables are initialised
according to their data type as shown in the table on
page 8. If a function call has been terminated without
the function supplying a result, this automatically
resets the initialisation value of the type concerned.
02/00 AWB 2700-1306 GB

65
 Instruction Section of a
POU

Example: Sum function

Function SUM and its application in the pou2
program displayed in IL and graphic forms
FUNCTION SUM : INT
VAR_INPUT
A : INT;
B : INT; (* Declaration section*)
C : INT;
END_VAR
LD A
ADD B (* Instruction section*)
ADD C
ST SUM
END_FUNCTION

Example: Program pou2

Invocation of the SUM function in the program pou2
PROGRAM pou2
VAR
SUMMAND1 : INT:= 1;
SUMMAND2 : INT:= 2;
SUMMAND3 : INT:= 3;
RESULT : INT;
END_VAR
LD SUMMAND1 (* First operand in the working register *)
SUM SUMMAND2, SUMMAND3 (* Function invocation with parameter
transfer *)
02/00 AWB 2700-1306 GB

ST RESULT (* Read sum of the working register and

assign to the variable RESULT *)
END_PROGRAM

66
 Function block

Further functions can be called up within a function.

Function blocks may not be instantiated in a function
and instance names of function blocks may not be
transferred as input parameters in a function.
Sucosoft also provides various manufacturer-
defined functions for frequently required tasks.

Online modifications and the application of the

status display are possible in the program POU
and in the function blocks but not in user
functions.
In order to check the algorithm of a user function,
first accept it as function block, check it and then
use it as a function.
Functions written by the user are currently not
being supported in PS 4-200 controllers.

Function block In addition to functions, function blocks can also be

used for frequently required tasks. Unlike functions,
function blocks can supply various output operands
as a result. A function block saves its variable values
from one invocation to the next and can use these
values again the next time the function block is
invoked provided the variables have not been
assigned new values.
A function block can call other function blocks.
The following table shows the permissible uses of the
inputs and outputs of function blocks:
02/00 AWB 2700-1306 GB

67
 Instruction Section of a
POU

Use In the function block Outside the function

block

Read LD IN1 LD FBx.IN1

input AND IN2 ST %QW0.0.0.3
ST Q1

Write LD 1000 LD Start

input ST IN1 ST FBx.IN1
CAL FBx

Read LD OUT1 CAL FBx(IN1 := On, ...)

output AND IN1 LD FBx.OUT1
ST OUT1 ST %QW0.0.0.3

Write LD 1000
output ST OUT1 Not permitted

If an input operand is used as an edge, it must be

declared accordingly.
Example: operand as edge
Declaration of an input operand as edge shown in IL
and graphic forms. In S 40 operand as edge applies
only to the PS 4-200 and PS 4-300 series.
Rising edge Falling edge

VAR_INPUT VAR_INPUT

Start : BOOL R_EDGE; Pause : BOOL F_EDGE;

END_VAR END_VAR
02/00 AWB 2700-1306 GB

68
 Function block

The IEC standard provides two equal-ranking

procedures for the invocation of a function block.
They are shown in the pou3 program with the aid of
two instances of a function block.
Example: Function block meanval
A function block for simple averaging and its
application in pou3
Prototype of the meanval function block in IL and
graphic representations
FUNCTION_BLOCK meanval

VAR_INPUT
Reset : BOOL;
Value1 : USINT;
Value2 : USINT;
END_VAR

VAR_OUTPUT
Mean_value : USINT;
END_VAR

LD Value1
ADD Value2
DIV 2
ST Mean_value
END_FUNCTION_BLOCK
02/00 AWB 2700-1306 GB

69
 Instruction Section of a
POU

Example: Program pou3

Instantiation of the meanval function block in the
pou3 program with two different invocation
procedures:
PROGRAM pou3

VAR
Instance1_Name : meanval;
Instance2_Name : meanval;
MeasValue1 AT %IB0.0.0.0 : USINT;
MeasValue2 AT %IB0.0.0.1 : USINT;
Result1 AT %QB0.0.0.0 : USINT;
Result2 AT %QB0.0.0.1 : USINT;
Reset AT % I0.0.0.2.0 : BOOL;
END_VAR

(* 1st procedure FB invocation *)

CAL Instance1_Name (Reset:= reset,
Value1:= MeasValue1,
Value2:= MeasValue2)
LD Instance1_Name.Mean_value
ST Result1
(* 2nd procedure FB invocation *)
LD Reset
ST Instance2_Name.Reset
LD MeasValue1
ST Instance2_Name.value1
LD MeasValue2
ST Instance2_Name.value2
CAL Instance2_Name
LD Instance2_Name.Mean_value
ST Result2

END_PROGRAM

The single function block Mean_val can be

instantiated under different names as often as
required. Define the instances in the declaration
section of the invoking POU by assigning each
application of the function block one instance name
02/00 AWB 2700-1306 GB

(here: 'Instance1_Name' and 'Instance2_Name').

70
 Function block

Sucosoft assigns each instance the required

memory space so that the internal data of each
instance of the function block can be stored.
The parameters for the function block are set when it
is called up with CAL and the appropriate instance
name (CAL Instance1_Name). The input parameters
of the function block are thus assigned the
predefined instance-related variables. The individual
operands are entered in round parentheses,
separated by commas. The value of the output
parameter Instance1_Name.Mean_Value is
transferred after the invocation of the variable
Result1:
LD Instance1_Name.Mean_value
ST Result1

In the second procedure all instance-defined input

parameters are individually transferred to the
function block parameters by means of the working
register before the invocation of the function block.
The invocation of the function block itself does not
contain parameters. The function block results are
stored and can be addressed with the LD instruction.
Another procedure for the function block invocation
is a Moeller variant. The parameters for the input and
output operands are transferred when invoking the
function block, separated by the character ¦ .
Example: Function block invocation with ¦
CAL Instance3_name(Reset := Reset,
Value := MeasValue3
|
Result3 := Mean_value)
02/00 AWB 2700-1306 GB

71
72
02/00 AWB 2700-1306 GB
 4 Graphical Programming Languages

Introduction Sucosoft provides two graphical programming

languages which meet the IEC1131-3 Standard:
Ladder Diagram (LD) and Function Block Diagram
(FBD).
The first section of this manual provides a general
description of the programming languages LD and
FBD and an overview of the manufacturer functions
and function blocks, together with practical
programming examples in FBD. The second section
describes working with LD and FBD in the POU
editor and when testing and commissioning.
The Sucosoft S 40 User Interface reference manual
provides basic information on working with the
software.
A program organisation unit created in the
programming languages LD and FBD consists of
a declaration section and an instruction section.
It thus has the same structure as a POU in the IL
version.
In the programming languages LD and FBD the
declaration section is shown as text just as it is in
the IL programming language. The instruction
section is represented graphically in LD and FBD.
The programming languages IL, LD and FBD are
exchangeable. You can thus create a program in LD
and display and process it in IL and FBD. You will
find further inforamtion in the last section of the
description of the POU editor LD / FBD under
‘Changing between the programming languages’.
02/00 AWB 2700-1306 GB

In the instruction section the individual program

sequences are represented in networks. The network
header includes the serial network number and

73
 Graphical Programming
Languages

below the number a comment can be entered. When

changing from IL to LD or FBD all line comments of a
sequence which were entered in the IL programming
language will automatically be shown in the header
of the corresponding network.
As in the programming language IL, the user is
provided with all operations, functions and function
blocks in the programming languages LD and FBD.
Binary operations are represented by different
graphical symbols in LD and FBD. In both languages
the functions and function blocks are represented as
rectangular graphical symbols with input operands
on the left and output operands on the right side.

02/00 AWB 2700-1306 GB

74
 Introduction

Ladder diagram
VAR
START AT %I0.0.0.0.0: BOOL; (*Motor ON (make contact)*)
OFF AT %I0.0.0.0.1: BOOL; (*Motor OFF (break contact)*)
EMER_STOP AT %I0.0.0.0.2: BOOL; (*Emergency-stop switch (break
contact)*)
Motor AT %Q0.0.0.0.0: BOOL; (*Motor drive*)
Impulse AT %I0.0.0.0.3: BOOL; (*Impulse encoder*)
FinalValue : INT:=20; (*Comparison value for the counter*)
Halt : BOOL; (*Stop signal if counter=20*)
RevolutionsCounter: CTU; (*Impulse counter*)
END_VAR
02/00 AWB 2700-1306 GB

75
 Graphical Programming
Languages

Function block diagram

VAR
START AT %I0.0.0.0.0: BOOL; (*Motor ON (make contact)*)
OFF AT %I0.0.0.0.1: BOOL; (*Motor OFF (break contact)*)
EMER_STOP AT %I0.0.0.0.2: BOOL; (*Emergency-stop switch (break
contact)*)
Motor AT %Q0.0.0.0.0: BOOL; (*Motor drive*)
Impulse AT %I0.0.0.0.3: BOOL; (*Impulse encoder*)
FinalValue : INT:=20; (*Comparison value for the counter*)
Halt : BOOL; (*Stop signal if counter=20*)
RevolutionsCounter : CTU; (*Impulse counter*)
END_VAR

02/00 AWB 2700-1306 GB

76
 Programming in LD

Programming in LD The ladder diagram programming language is

designed for programming logic operations of binary
variables.
Programs are represented in LD by the following
graphical elements:
Scan a variable for status 1

Scan a variable for status 0

Assigning a current result (CR) or a constant to a

variable
Assigning a negated current result or a negated
constant to a variable
Set a variable if current result = 1

Reset a variable if current result = 1

Unconditional jump to a label

Jump to a label if current result = 1

Jump to a label if current result = 0

Unconditional return to invoking program

Return to invoking program if current result = 1

Return to invoking program if current result = 0

The representation of a program sequence in LD is
02/00 AWB 2700-1306 GB

similar to a current path running beween two current

rails. The rails are the vertical outer lines in the
display. A logic sequence is made by combining
individual contacts in series or in parallel.

77
 Graphical Programming
Languages

There is no restriction in the number of contacts that

can be connected in parallel or in series.

Two contact symbols are available for Boolean input

variables:
Contact symbol for a variable that requires the status
1 so that a logic sequence is fulfilled. The status 1 of
variables assigned to physical addresses corres-
ponds to a break contact that has not been actuated
or a make contact that has been actuated.
. Contact symbol for a variable that requires the status
0 so that a logic sequence is fulfilled. The status 0 of
variables assigned to physical addresses corres-
ponds to a break contact that has been actuated or
a make contact that has not been actuated.
The result of a logic sequence of input variables can
be used as the condition of a subsequent operation.
These operations may consist of:
Assignments
Jumps to a point in a program that has been
assigned a jump label
A return to the invoking POU
The current result can be assigned to the output
variable directly or after being negated. There are
therefore two symbols for output variables:
02/00 AWB 2700-1306 GB

78
 Programming in LD

Direct assignment of current result to the output

variable
Assignment of the negated current result to the
output variable
There is no limit to the number of symbols that can
be placed next to each other or above each other.
Variable names can be specified with a maximum
length of 64 characters. Variable names are shown,
however, with up to 3 lines above the contact or
output symbol.

AND sequence
An AND sequence is created in LD by connecting
contacts in series. In order to fulfil the AND condition,
the individual input variables must simultaneously
have the states required by the contact type.

The AND condition shown is fulfilled if the input

variables have the following states:
Input variable Status
Input_1 1
Input_2 0
Input_3 1
The AND_Result output variable is then in status 1.
02/00 AWB 2700-1306 GB

79
 Graphical Programming
Languages

OR sequence
An OR condition is created in LD by connecting
contacts in parallel. The OR condition is fulfilled if at
least one input variable has the status required for
contacting.

The OR sequence shown is fulfilled if at least one of

the input variables has the following status:
Input variable Status
Input_1 1
Input_2 1
Input_3 0
The output variable OR_Result has the status 1.

Mixed sequences
Mixed sequences are combinations of AND and OR
sequences. The sequence is fulfilled if the current
path between the left current rail and the output
symbol is closed via at least one path.
02/00 AWB 2700-1306 GB

80
 Programming in LD

The condition shown is fulfilled if the input variables

have the following states:
Input variable Status
Input_1 or
Input_3 1
Input_2 0
The output variable OR_before_AND_Result then
has status 1.

The sequence is fulfilled if one of the two input

variables has the status 1, i. e. the input variables are
different. The output variable XOR_Result then has
status 1.
02/00 AWB 2700-1306 GB

81
 Graphical Programming
Languages

Negated assignment
An output variable can also be assigned a negated
current result. This status is indicated by an oblique
stroke in the middle of the output symbol.

The input variables are ANDed. The current result is

negated and assigned to the AND_negated output
variable.

The sequence shown represents an equivalence

function. The sequence is only fulfilled if both input
variables have the same status. The current result
will be 0 if the states of the input variables are
different. The output variable XOR_Result is
therefore only 1 if the equivalence is not fulfilled,
i. e. if the input variables are different. The sequence
shown therefore corresponds to an Exclusive OR
sequence.
02/00 AWB 2700-1306 GB

82
 Programming in LD

Retentive assignment
The current result can be assigned to the output
variable retentively. The output will then retain its set
or reset status.
Set
If the current result is 1, the output variable is set,
i. e. is set to 1. The 0 status of the current result has
no effect on the value of the output variable. Setting
is represented by an output symbol with an S in the
middle.

Just a momentary switching to 1 status on the

System_ON input will be enough to switch on the
plant permanently.
Reset
If the current result is 1, the output variable is reset,
i. e. is reset to 0. The current result 0 has no effect
on the value of the output variable. Resetting is
represented by an output symbol with the letter R in
the middle.
02/00 AWB 2700-1306 GB

83
 Graphical Programming
Languages

Just a momentary switching to 1 status on the

System_OFF input will be enough to switch off the
plant permanently

Jumps
The use of jump commands is a way of structuring
programs. They enable networks to be skipped
which are only processed occasionally. Jumps can
be executed depending on or irrespective of a
particular binary current result. The jump destination
is always the start of the network, i. e. the beginning
of a program sequence. A jump label must be
specified in addition to the jump symbol. The same
jump label name must be entered in the destination
network next to the network number.

02/00 AWB 2700-1306 GB

84
 Programming in LD

Unconditional jump
The unconditional jump JMP is executed irrespective
of the current result and is only useful in a program
section that is processed occasionally. An uncondi-
tional jump creates an independent network.
Network 0006 of the program shown contains the
02/00 AWB 2700-1306 GB

unconditional jump to the label Cylinder. The jump

destination is the network 0012, the jump label name
Cylinder is shown in the header of this network.

85
 Graphical Programming
Languages

Conditional jump
JMPC: The conditional jump JMPC is executed if the
current result is 1. The current result 0 causes the
program directly behind the jump operation to be
processed.
JMPCN: The conditional jump JMPCN is executed if
the current result is 0. If the current result is 1, the
program is processed directly after the jump
operation. Network 0003 of the program shown on
page 84 executes a jump to network 0007 if the value
of the variable Aggregate in network 0003 is 0.

Returns
Returns enable the program execution in the current
POU to be interrupted and returned to the program
level from which the POU was invoked. Returns can
be executed dependent on or irrespective of the
current result.
Unconditional return
The unconditional return RET is executed irrespec-
tive of the current result. It is only useful in a program
section that is only processed occasionally and
which is not the last network. An unconditional return
starts a separate network.
Conditional return
RETC: The conditional return RETC is executed if the
current result is 1. If the current result is 0, the
program will be processed directly after the return
operation.
02/00 AWB 2700-1306 GB

86
 Programming in LD

RETCN: The conditional return RETCN is executed if

the current result is 0. If the current result is 1, the
program will be continued directly after the return
operation.

Invocation of functions
Functions in LD and in FBD are represented by a
rectangular graphical symbol. The input variables are
shown on the left-hand connection lines and the
output variables on the right. The name of the
function and the names of the input operands are
shown inside the block.

A network can consist of a series of cascaded

functions.
02/00 AWB 2700-1306 GB

87
 Graphical Programming
Languages

Invocation of function blocks

Function blocks in LD and FBD are shown in the
same way. The function block is shown as a
rectangular block with the connection lines for the
input variables on the left and the connection lines for
the output variables on the right. The name of the
function block is contained inside the block, with the
names of the input operands on the left and the
names of the output operands on the right.
The instance name of the function block is shown
above the block.
A function block counts as an independent network.

The unused input and output operands of the

function block are not assigned a variable name
and their corresponding connection lines are shown
without any designation.
The parameters can be transferred outside of the
function block. In this case the function block is
shown without any external connection.
02/00 AWB 2700-1306 GB

88
 Programming in LD

Only an unconditional function block invocation

can be shown in the graphical programming
languages. If the function block is to be invoked
according to the current result, a conditional jump
to the network must be programmed with the
function block invocation.
02/00 AWB 2700-1306 GB

89
 Graphical Programming
Languages

Programming in FBD In FBD the individual language elements are

represented as graphical symbols.
In FBD several functions can be combined within a
network. A function block is represented in an
individual network.
The following graphical symbols are available for
displaying the program in FBD:
Graphical symbol to show an operation with two
variables. It is used for logical, arithmetic and
comparison functions. In the case of logical
sequences the values of input variables can be
negated before sequencing.This kind of input
variable is marked with a negation symbol such
as Input_2, for example.
Assignment of a current result (CR) or a constant to
a variable

Assignment of a negated current result or a negated

constant to a variable

Setting of a binary variable if CR = 1

Resetting of a binary variable if CR = 1

Unconditional jump to a label

Jump to a label if CR = 1

Jump to a label if CR = 0
02/00 AWB 2700-1306 GB

90
 Programming in FBD

Unconditional return to the invoking program

Return to the invoking program if
CR = 1
Return to the invoking program if
CR = 0
Graphical symbol which indicates a function.
Functions have any number of input operands but
only one output operand.

Graphical symbol which indicates a function block.

Function blocks have any number of input and
output operands.

Variable names of the inputs and outputs can be

entered with a maximum length of 64 characters.
Long variable names, however, will appear in up to
3 lines above the input or output symbol.
02/00 AWB 2700-1306 GB

91
 Graphical Programming
Languages

Logic sequences
The logic sequences AND, OR and XOR are shown
as graphical symbols with several input operands
and one output operand.
The value of an input operand can also be negated.
In this case the operand value is negated first of all,
after which the sequence is formed. These sequenc-
es too are shown with the three basic graphical
symbols for AND, OR and XOR. The operand to be
negated is marked by a negation symbol on the
connection line.
The result of a logic sequence of binary input
variables is a condition for one of the following
operations:
a store operation
a jump to a point in the program which is marked
by a jump label
a return to the invoking program
Logic sequences can refer to variables of the
ANY_BIT data type.
AND sequence
The input operands are ANDed. The current result is
assigned to the output operand.
The individual bits of the first operand of an AND
sequence of byte or word operands are sequenced
with the corresponding bits of the second operand.
02/00 AWB 2700-1306 GB

92
 Programming in FBD

The output variable Result is 1 if the two input

variables are 1.

The value of the Input_2 operand is negated in the

ANDN function shown. The result is ANDed with the
value of the operand Input_1 and assigned to the
ANDN_Res output operand.
The individual bits of the second operand of an
ANDN sequence of byte or word operands are
negated and sequenced with the corresponding bits
of the first operand
OR sequence
The input operands are ORed. The current result is
assigned to the output operand.
02/00 AWB 2700-1306 GB

93
 Graphical Programming
Languages

The individual bits of the first operand of an OR

sequence of byte or word operands are sequenced
with the corresponding bits of the second operand.

The output variable OR_Result is 1 if at least one of

the input variables is 1.

In the sequence shown the value of the operand

Input_1 is negated. The result is ORed with the value
of the operand Input_2 and assigned to the
OR_Result output operand.
In a sequence of byte or word operands the
individual bits of the operand Input_1 are negated
and sequenced with the corresponding bits of the
02/00 AWB 2700-1306 GB

operand Input_2.

94
 Programming in FBD

Exclusive OR sequence
The input operands are XORed. The current result is
assigned to the output operand.
In an XOR sequence of byte or word operands, the
individual bits of the first operand are sequenced
with the corresponding bits of the second operand.

Mixed sequences
Mixed sequences consist of combinations of several
different graphical symbols in the same network.
02/00 AWB 2700-1306 GB

95
 Graphical Programming
Languages

A sequence consisting of several input variables can

be shown in different ways:
By increasing the number of connection lines on
the existing sequence symbol.

By adding a sequence symbol of the same type

upstream or downstream.

Negating intermediate result

When several functions are combined in a network,
02/00 AWB 2700-1306 GB

an intermediate result can be continued after a

negation with a NOT function in the same network.

96
 Programming in FBD

The negation can be used on ANY_BIT data

elements of type.

The variable Display_1 indicates trouble-free

operation.

Assignment
The current result or a constant can be assigned
directly to an output variable or after it has been
negated. There are two output symbols for both
options:
Direct assignment of a current result or a constant to
the output variable.

Assignment of a negated current result or a negated

constant to the output variable.
The negation of byte, word or double word results
corresponds to the negation of the individual bits.
Only binary variables can be negated.
02/00 AWB 2700-1306 GB

97
 Graphical Programming
Languages

Retentive assignment
The binary current result can be assigned retentively
to the output variable, which can also be set or reset
retentively.
Set
If the current result is 1, the output variable is set,
i. e. is set to 1. The 0 status of the current result has
no effect on the value of the output variable. Setting
is represented by an output symbol with an S in the
middle.

If the plant is in status 1 just a momentary switching

to 1 status on the Start input will be enough to switch
on the first phase of the plant permanently.

02/00 AWB 2700-1306 GB

98
 Programming in FBD

Reset
If the current is 1, the output variable is reset, i. e. is
reset to 0. The current result 0 has no effect on the
value of the output variable. Resetting is represented
by an output symbol with an R in the middle.

Just a momentary switching to 1 status on the

Position input or the Halt input is enough to switch off
the motor permanently.

Arithmetic operations
The arithmetic operations addition, subtraction,
multiplication and division can be used on numeric
data types.
Addition
02/00 AWB 2700-1306 GB

The values of variables Number_1 and Number_2 are

added and the result is assigned to the variable Sum.

99
 Graphical Programming
Languages

Subtraction

The value of the variable Subtrahend is subtracted

from the variable Minuend and the result is assigned
to the variable Difference.
Multiplication

The value of the variable Multiplier is multiplied with

the value of the variable Multiplicand and the result is
assigned to the variable Product.
Division 02/00 AWB 2700-1306 GB

The value of the variable Dividend is divided by

the value of the variable Divisor and the result is
assigned to the variable Quotient.

100
 Programming in FBD

Compare operations
A compare operation involves the comparison
between the value of the first operand and the value
of the second operand. The completion of the
comparison is indicated by the status 1 on the output
operand.
All elementary data types can be used.
The graphical symbols are marked with the
appropriate operation name:
GT greater than
GE greater than or equal to
EQ equal
NE not equal to
LE less than or equal to
LT less than
Example: Greater than comparison

If the value of the variable Number_1 is greater than

the value of the variable Number_2, the jump
condition is fulfilled. Program execution is continued
in the network marked Label_1.
02/00 AWB 2700-1306 GB

101
 Graphical Programming
Languages

Jumps
The use of jump commands is a way of structuring
programs. They enable networks to be skipped
which are only processed occasionally. Jumps can
be executed depending on or irrespective of a
particular binary current result. The jump destination
is always the start of the network, i. e. the beginning
of a program sequence. A jump label must be
specified in addition to the jump symbol. The same
jump label name must be entered in the destination
network next to the network number.

02/00 AWB 2700-1306 GB

102
 Programming in FBD

Unconditional jump
The unconditional jump JMP is executed irrespective
of the current result and is only useful in a program
section that is processed occasionally. An uncondi-
tional jump creates an independent network.
Network 0006 of the program shown contains the
02/00 AWB 2700-1306 GB

unconditional jump to the label Cylinder. The jump

destination is the network 0012, the jump label name
Cylinder is shown in the header of this network.

103
 Graphical Programming
Languages

Conditional jump
JMPC: The conditional jump JMPC is executed if
the current result is 1. If the current result is 0, the
program will be processed directly after the jump
operation.
JMPCN: The conditional jump JMPCN is executed if
the current result is 0. If the current result is 1, the
program is processed directly after the jump
operation.
Network 0003 of the program shown on page 102
executes a jump to network 0007 if the current result
in network 0003 is 0.

Returns
Returns enable the program execution in the current
POU to be interrupted and returned to the program
level from which the POU was invoked. Returns can
be executed dependent on or irrespective of the
current result.
Unconditional return
The unconditional return RET is executed
irrespective of the current result. It is only useful in a
program section that is only processed occasionally
and which is not the last network. An unconditional
return starts a separate network.
02/00 AWB 2700-1306 GB

104
 Programming in FBD

Conditional return
RETC: The conditional return RETC is executed if
the current result is 1. If the current result is 0, the
program will be processed directly after the return
operation.
RETCN: The conditional return RETCN is executed if
the current result is 0. If the current result is 1, the
program will be processed directly after the return
operation.

Invocation of functions
Functions in LD and in FBD are represented by a
rectangular graphical symbol. The input variables are
shown on the left-hand connection lines and the
output variables on the right. The name of the
function and the names of the input operands are
shown inside the block.
02/00 AWB 2700-1306 GB

105
 Graphical Programming
Languages

Several functions and operation symbols can be

cascaded within a network. If the data types of the
connected graphical symbols do not match, a type
conversion function must be inserted between the
data types concerned.

The numerical result of the multiplication is

converted into the data type BYTE.

Invocation of function blocks

Function blocks in LD and FBD are shown in the
same way. The function block is shown as a
rectangular block with the connection lines for the
input variables on the left and the connection lines for
the output variables on the right. The name of the
function block is contained inside the block, with
the names of the input operands on the left and the
names of the output operands on the right. The
instance name of the function block is shown above
the block.
02/00 AWB 2700-1306 GB

106
 Programming in FBD

A function block counts as an independent network.

The unused input and output operands of the

function block are not assigned a variable name and
their corresponding connection lines are shown
without any designation
The parameters can be transferred outside of the
function block. In this case the function block is
shown without any external connection.
02/00 AWB 2700-1306 GB

107
 Graphical Programming
Languages

Only an unconditional function block invocation

can be shown in the graphical programming
languages. If the function block is to be invoked
according to the current result, a conditional jump
to the network must be programmed with the
function block invocation.

02/00 AWB 2700-1306 GB

108
 5 Functions

Sucosoft provides a wide variety of functions for

your use. They can be classified into:
Functions as per the IEC 1131-3 Standard
Moeller standard functions.
Functions complying with IEC 1131-3 standard are
defined so as to cover all vendors. PLC programs
which use only IEC functions can therefore be used
with controllers made by different manufacturers.
Moeller has added further functions to the IEC
functions; these are marked ’ ’. With a few
exceptions the KM functions can be used with all
Moeller controllers.
The following table shows an overview of all
functions grouped according to the jobs they do.
Each function is marked with ’IEC’ or ’ ’ and the
controller type specified where the function can be
used without any modification.

Some of the functions described use the data

type ADDRESS. They are used for the automatic
conversions of programs from previous systems
and for this reason cannot be used with all
controllers. Such functions are marked # in the
following table.

A detailed description of the functions (in

alphabetical order) starts on page 116.
06/99 AWB 2700-1306 GB

109
 Functions

PS 4-200

PS 4-300

PS 416
Stand- See
Function Meaning ard page
Converter functions
*_TO_** Type conversion of elementary data types ✓ ✓ ✓ IEC, M 116
Type conversion of time and date – ✓ ✓ 128
TRUNC INT part of a REAL number – ✓ ✓ IEC 202
Numeric functions
ABS Formation of amount ✓ ✓ ✓ IEC 136
NEG Two’s complement ✓ ✓ ✓ M 182
Arithmetic functions
ADD Addition of numeric data types ✓ ✓ ✓ IEC 137
Addition of duration to time and date ✓ ✓ ✓ IEC 139
Addition of addresses ✓, # ✓, # – M 141
MUL Multiplication of numeric data types ✓ ✓ ✓ IEC 176
Multiplication of duration – ✓ ✓ IEC 179
Multiplication of addresses ✓, # ✓, # – M 179
SUB Subtraction of numeric data types ✓ ✓ ✓ IEC 198
Subtraction of duration and time and date ✓ ✓ ✓ IEC 199
Subtraction of addresses ✓, # ✓, # – M 201
DIV Division of numeric data types ✓ ✓ ✓ IEC 150
Division of duration – ✓ ✓ IEC 151
Division of addresses ✓, # ✓, # – M 152
MOD Remainder Division – ✓ ✓ IEC 175
Edge detection
IsCarry Test of carry bit ✓ ✓ ✓ M 162
IsZero Test of zero bit ✓ ✓ ✓ M 165
IsOverflow Test of overflow bit ✓ ✓ ✓ M 163
IsPositive Test whether result is positive ✓ ✓ ✓ M 164
IsBitTrue Test of a bit in the result ✓ ✓ ✓ M 161
GetCarry Get carry with multiplication or remainder
02/00 AWB 2700-1306 GB

Register of a division ✓ ✓ ✓ M 158

Shift functions
SHL Shift left ✓ ✓ ✓ IEC 196
SHR Shift right ✓ ✓ ✓ IEC 197

110
 PS 4-200

PS 4-300

PS 416
Stand- See
Function Meaning ard page
ShiftLeft Shift left with carry
Carry ✓ ✓ ✓ M 194
ShiftRight Shift right with carry
Carry ✓ ✓ ✓ M 195
ROL Rotate left ✓ ✓ ✓ IEC 190
ROR Rotate right ✓ ✓ ✓ IEC 191
Logic (Boolean) functions
AND, & Logic AND function *) ✓ ✓ ✓ IEC 40
*)
OR Logic OR function ✓ ✓ ✓ IEC 43
*)
XOR Logic Exclusive OR function ✓ ✓ ✓ IEC 44
NOT Bit complement formation ✓ ✓ ✓ IEC 183
Comparison functions
GT Comparison function: ’larger than’ *) ✓ ✓ ✓ IEC 50
GE Comparison function: larger than or equal to *) ✓ ✓ ✓ IEC 50
*)
EQ Comparison function: equal to ✓ ✓ ✓ IEC 50
*)
LE Comparison function: smaller than or equal to ✓ ✓ ✓ IEC 50
*)
LT Comparison function: smaller than ✓ ✓ ✓ IEC 50
NE Comparison function: not equal to *) ✓ ✓ ✓ IEC 50
OS system functions
PLC_Message System diagnostics, reading message word ✓ ✓ ✓ M 184
PLC_ReadClock Reading single element from real-time clock ✓ ✓ ✓ M 186
Interrupt functions
Disable_Interrupt Disable alarm ✓ ✓ ✓ M 147
Enable_Interrupt Enable alarm ✓ ✓ ✓ M 153
Character string functions
LEN Determine length of a character string ✓ ✓ ✓ IEC 167
02/00 AWB 2700-1306 GB

CONCAT Concatenation of strings – ✓ ✓ IEC 142

Concatenation of time and date 144

111
 Functions

PS 4-200

PS 4-300

PS 416
Stand- See
Function Meaning ard page
DELETE Delete n characters from a string – ✓ ✓ IEC 145
FIND Find a string within a string – ✓ ✓ IEC 156
INSERT Insert a string in a string – ✓ ✓ IEC 159
LEFT Select n characters left of a string – ✓ ✓ IEC 166
MID Sections of a string – ✓ ✓ IEC 172
REPLACE Replace characters in a string – ✓ ✓ IEC 187
RIGHT Select n characters right of string – ✓ ✓ IEC 189
Selection functions
LIMIT Limitation – ✓ ✓ IEC 168
MAX Maximum selection – ✓ ✓ IEC 170
MIN Minimum selection – ✓ ✓ IEC 174
MUX Multiplexer – ✓ ✓ IEC 180
SEL Conditional operand selection – ✓ ✓ IEC 192

*) The functions that correspond to the IL operators are

described in the section Instruction set starting on
page 29.
This chapter describes the individual functions and
their application by means of simple examples.
The interfaces of the parameter transfer are de-
scribed by means of the prototypes of the individual
functions. A prototype gives an overview of the input
operands of a function. In IL representation the
prototype is the declaration section of the function
with the declaration blocks of the input operands.
For the description of the functions the prototypes
are represented graphically. Here the function is
02/00 AWB 2700-1306 GB

represented as a square graphical symbol with input

operands on the left and the output operands on the
right. The name of the function is shown in the middle
of the graphical symbol. The names of the input

112
 operands appear on the left side. The data types of
the operands are shown outside the graphical
symbol.
Example: prototype representation
Comparison between instruction list and graphical
representations of a prototype function using the
SHR function as an example.
FUNCTION SHR : ANY_BIT
VAR_INPUT
IN : ANY_BIT;
N : ANY_INT;
END_VAR
END_FUNCTION

For the operand IN of the function SHR the data

types BYTE, WORD and DWORD (DWORD only for
PS 4-300/PS 416) can be used for ANY_BIT. This
function is an overloaded function, i. e. the function
can be used for various data types.

Overloaded – non-type-dependent – functions

are only available with standard (manufacturer)
functions. Programming your own overloaded
functions (user-specified functions) is not
possible.
You can find the description of the individual
elementary data types in the section Elementary data
02/00 AWB 2700-1306 GB

types on page 7 of this manual.

113
 Functions

The invocation of a function is carried out by entering

its name and transferring the parameter list for the
individual input operands of the function. The
parameters are listed beside the function name,
separated by a comma.

The first function parameter is provided in the

working register before the function is called.

Type conversion functions

*_TO_** Function name
* Data type of the input operand
** Data type of the output operand
Operands that are sequenced with each other must
always be of the same data type. If, for example,
the data type BYTE is required for an input operand
of a function but the data type of the variable to be
transferred is of type USINT, the type must be con-
verted using the type converting function
USINT_TO_BYTE.
In type conversion the value in the working register is
used as the input operand. The result - the output
operand in the new data type - is made available in
the working register.

When type converting numerical data types make

sure that the permitted value of the target data
type is not exceeded. If the value of the input
operand is too large, the result will be reduced to
the available bit length of the output operand and
will thus supply an incorrect value.
02/00 AWB 2700-1306 GB

114
 Sucosoft provides several type-converting functions
for type conversion between the elementary data
types. The type conversion functions can be used for
the following combinations of data types:

Output

TIME_OF_DAY
DWORD1)

STRING1)
UDINT1)

REAL1)
DINT1)

WORD
USINT

BOOL

DATE
BYTE
UINT
SINT

BCD
INT

Input

SINT x x x x x x x x x x x

INT x x x x x x x x x x x

DINT1) x x x x x x x x x x x

USINT x x x x x x x x x x x

UINT x x x x x x x x x x x x

UDINT1) x x x x x x x x x x x

REAL1) x x x x x x

BOOL x x x x x x x x x

BYTE x x x x x x x x x

WORD x x x x x x x x x

DWORD1) x x x x x x x x x

DATE_AND_TIME x x

TIME x x

BCD x x x x x x
1)
STRING x

ADDRESS2) x
02/00 AWB 2700-1306 GB

1) PS 4-300 and PS 416 only

2) PS 4-200 and PS 4-300 only

115
 Functions

Type conversion ’ANY_INT’ to ’ANY_BIT’

Function prototype

Description
In a real case the character * would be replaced by
the function name. The following type conversions
are possible:
Function name Comment

USINT_TO_BYTE Type conversions without

UINT_TO_WORD data type expansion
UDINT_TO_DWORD1)
INT_TO_WORD
DINT_TO_DWORD1)

USINT_TO_WORD Type conversion with data type expansion from

USINT_TO_DWORD1) a less significant data type to a more significant
UINT_TO_DWORD1) data type without evaluation of the most
significant bit as sign bit.

SINT_TO_WORD Type conversion with data type expansion from

SINT_TO_DWORD1) a less significant data type to a more significant
INT_TO_DWORD1) data type with evaluation of the more significant
bit as sign bit.

UINT_TO_BYTE Type conversion from a higher significant data

UDINT_TO_BYTE1) type into a less significant data type. The result
UDINT_TO_WORD1) is reduced to the length of the destination data
SINT_TO_BYTE type; the higher significant bits are lost.
DINT_TO_BYTE1)
DINT_TO_WORD1)
02/00 AWB 2700-1306 GB

116
 Function name Comment

SINT_TO_BOOL The result has the value 0 with the value 0 of the
UINT_TO_BOOL input operand, otherwise the result is 1.
UDINT_TO_BOOL1)
USINT_TO_BOOL
INT_TO_BOOL
DINT_TO_BOOL1)
1) PS 416, PS 4-300 only

Example: type conversion USINT_TO_WORD

The data element of type USINT (unsigned integer) is
written to the low byte of the data element of type
WORD the high byte is filled with zeros.
High Low
Conversion from 00100101 to 00000000 00100101
USINT WORD

High Low
Conversion from 10100101 to 00000000 10100101
USINT WORD
02/00 AWB 2700-1306 GB

117
 Functions

Example: type conversion SINT_TO_WORD

The bit pattern in the data element of type SINT is in-
terpreted as a signed number. The higher significant
bit (bit 7) is evaluated as a sign bit. The bit pattern is
written to the low byte of the data element of type
INT. If the signed bit has a 0, it is a positive number.
The high byte will therefore be filled with zeros. If bit
7 is 1, the high byte will be filled with ones.

High Low
Conversion from 00100101 to 00000000 00100101
SINT WORD

High Low
Conversion from 10100101 to 11111111 10100101
SINT WORD

Example: invocation of the function

SINT_TO_BYTE
PROGRAM conv1

VAR
Number1 : SINT := -1;
Byte1 : BYTE;
END_VAR

LD Number1
SINT_TO_BYTE
ST Byte1 (* Byte1: 11111111 *)

END_PROGRAM
02/00 AWB 2700-1306 GB

118
 Type conversion of ANY_INT to ANY_INT

Function prototype

Description
In a real case the character * would be replaced by
the function name. The following type conversions
are possible:
Function name Comment

USINT_TO_SINT Type conversions without

SINT_TO_USINT data type expansion
UINT_TO_INT
INT_TO_UINT
UDINT_TO_DINT1)
DINT_TO_UDINT1)

USINT_TO_UINT Type conversion with data type expansion from

USINT_TO_INT a less significant data type to a next-higher data
USINT_TO_UDINT1) type without evaluation of the higher significant
USINT_TO_DINT1) bit as sign bit. The higher significant bits are
UINT_TO_UDINT1) filled with zeros.
UINT_TO_DINT1)

SINT_TO_UINT Type conversion with data type expansion from

SINT_TO_INT a less significant data type to a next-higher data
SINT_TO_UDINT1) type with evaluation of the higher significant bit
SINT_TO_DINT1) as sign bit. The higher significant bits are filled
INT_TO_UDINT1) with the sign bit.
INT_TO_DINT1)
02/00 AWB 2700-1306 GB

119
 Functions

Function name Comment

UINT_TO_USINT Type conversion from a higher significant data

UINT_TO_SINT type into a lower-significance data type. The
INT_TO_USINT result is reduced to the length of the destination
INT_TO_SINT data type.
UDINT_TO_USINT1)
UDINT_TO_SINT1)
UDINT_TO_UINT
UDINT_TO_INT1)
DINT_TO_USINT1)
DINT_TO_SINT1)
DINT_TO_UINT1)
DINT_TO_INT1)
1) PS 416 and PS 4-300 only

02/00 AWB 2700-1306 GB

120
 Type conversion of ANY_BIT to ANY_INT

Function prototype

Description
In a real case the character * would be replaced by
the function name. The following type conversions
are possible:
Function name Comment

BOOL_TO_USINT Type conversion with data expansion. The result

BOOL_TO_UINT has the value of the input operand (0 or 1).
BOOL_TO_UDINT1)
BOOL_TO_SINT
BOOL_TO_INT
BOOL_TO_DINT1)

BYTE_TO_USINT Type conversions without

WORD_TO_UINT data type expansion
DWORD_TO_UDINT1)
BYTE_TO_SINT
WORD_TO_INT
DWORD_TO_DINT1)

BYTE_TO_UINT Type conversion with data type expansion from

BYTE_TO_UDINT1) a less significant data type to a next-higher data
WORD_TO_UDINT1) type without evaluation of the higher significant
bit as sign bit. The higher significant bits are
filled with zeros.

BYTE_TO_INT Type conversion with data type expansion from

BYTE_TO_DINT1) a less significant data type to a next-higher data
WORD_TO_DINT1) type without evaluation of the higher significant
bit as sign bit. The higher significant bits are
02/00 AWB 2700-1306 GB

filled with zeros.

121
 Functions

Function name Comment

WORD_TO_USINT Type conversion from a higher significant data

DWORD_TO_USINT1) type into a lower-significance data type. The
DWORD_TO_UINT1) result is reduced to the length of the destination
WORD_TO_SINT data type; the higher significant bits are lost.
DWORD_TO_SINT1)
DWORD_TO_INT1)
1) PS 416, PS 4-300 only

Example: type conversion BYTE_TO_UINT

The higher significant bit of the data element of type
BYTE is not evaluated. The bit pattern is written to
the low byte of the data element of type UINT; the
high byte is filled with zeros.
High Low
Conversion from 00100101 to 00000000 00100101
BYTE UINT

High Low
Conversion from 10100101 to 00000000 10100101
BYTE UINT

Example: type conversion BYTE_TO_INT

The bit pattern is written to the low byte of the data
element of type INT. The high byte is filled with zeros.
High Low
Conversion from 00100101 to 00000000 00100101
BYTE INT

High Low
Conversion from 10100101 to 00000000 10100101
BYTE INT
02/00 AWB 2700-1306 GB

122
 Example: invocation of the function
BYTE_TO_SINT
PROGRAM conv2

VAR
Byte1 : BYTE := 2#0111;
Number1 : SINT;
END_VAR

LD Byte1
BYTE_TO_SINT
ST Number1 (* Number1: 123 *)

END_PROGRAM
02/00 AWB 2700-1306 GB

123
 Functions

Type conversion ’ANY_BIT’ to ’ANY_BIT’

Function prototype

Description
In a real case the character * would be replaced by
the function name. The following type conversions
are possible:
Function name Comment

BYTE_TO_BOOL The result has the value 0 with the value 0 of the
WORD_TO_BOOL input operand, otherwise the result is 1.
DWORD_TO_BOOL1)

BYTE_TO_WORD Type conversion with data type expansion from

BYTE_TO_DWORD1) a less significant data type to the next-higher
WORD_TO_DWORD1) data type. The higher significant bits are filled
with zeros.

WORD_TO_BYTE Type conversion from a higher significant data

DWORD_TO_BYTE1) type into a lower-significance data type. The
DWORD_TO_WORD1) result is reduced to the length of the destination
data type.

BOOL_TO_BYTE Type conversion with data type expansion. The

BOOL_TO_WORD result has the value of the input operand (0 or 1).
BOOL_TO_DWORD1)

1) PS 416, PS 4-300 only

02/00 AWB 2700-1306 GB

124
 Type conversion ANY_INT to REAL
PS 4-300
PS 416

Function prototype

Description
In a real case the character * would be replaced by
the function name. The following type conversions
are possible:
SINT_TO_REAL
INT_TO_REAL
DINT_TO_REAL
USINT_TO_REAL
UINT_TO_REAL
UDINT_TO_REAL
02/00 AWB 2700-1306 GB

125
 Functions

Type conversion of REAL to ANY_INT

PS 4-300
PS 416

Function prototype

Description
a real case the character * would be replaced by the
function name. The following type conversions are
possible:
REAL_TO_SINT
REAL_TO_INT
REAL_TO_DINT
REAL_TO_USINT
REAL_TO_UINT
REAL_TO_UDINT

In the case of floating point numbers (data type

REAL) with fractional digits smaller than 0.5 the
amounts of the output values are rounded down,
with fractional digits greater than 0.5 they are
rounded up.
Numbers with fractional digits equal to 0.5 are
rounded to the nearest even number. 02/00 AWB 2700-1306 GB

126
 Example: type conversion REAL_TO_INT
Input value : Output value:

–1.4 –1
–1.4 –1
–1.6 –2
–1.6 –2
–1.5 –2
–2.5 –2
–0.5 –0
–3.5 –4

Conversion results which exceed the range of values

of the destination data type are truncated - i. e.
reduced to the bit length available.
Example: type conversion REAL_TO_SINT
Input value Output value:

2049.0 –121
2178.0 –126
02/00 AWB 2700-1306 GB

127
 Functions

Type conversion of time and date

Function prototype

Description
In a real case the character * would be replaced by
the function name. The following type conversions
are possible:
Function name Comment

DATE_AND_TIME_TO_TIME_OF_DAY The time is loaded into the

* or working register from the data
DT_TO_TOD element with the date and time
data.

DATE_AND_TIME_TO_DATE The date is loaded into the

* or working register from the data
DT_TO_DATE element with the date and time
data.

TIME_TO_UINT The duration is converted into

milliseconds and loaded into the
working register. The result must
not exceed the value 65535.

TIME_TO_USINT The duration is converted into

milliseconds and loaded into the
working register. The result must
not exceed the value 255.

* Alternative notation

For the two functions TIME_TO_UINT and

02/00 AWB 2700-1306 GB

TIME_TO_USINT, results with values larger than

65535 and 255 are invalid. This can be scanned
with the IsOverflow function.

128
 Example: invocation of the function
DATE_AND_TIME_TO_TIME_OF_DAY
PROGRAM time

VAR
Date1 : DATE_AND_TIME := DT#1980-01-12-
18:15:00.00;
only_time : TIME_OF_DAY;
END_VAR

LD date1
DATE_AND_TIME_TO_TIME_OF_DAY
ST only_time (*only_time: 18:15:00.00 *)

END_PROGRAM

Example: invocation of the function

DATE_AND_TIME_TO_DATE
PROGRAM date

VAR
Date1 : DATE_AND_TIME := DT#1980-01-12-
18:15:00.00;
only_date: DATE;
END_VAR

LD date1
DATE_AND_TIME_TO_DATE
ST only_date (*only_date: 1980-01-12 *)

END_PROGRAM
02/00 AWB 2700-1306 GB

129
 Functions

Type conversion of UINT to STRING

PS 4-300
PS 416

Function prototype

Description
The two bytes of the input operand of data type UINT
are in each case interpreted as an encoded graphic
character and output as a two-character string. This
type conversion is not useful unless the value of the
input variable actually corresponds to two encoded
characters.
Example: invocation of the function
UNIT_TO_STRING
PROGRAM main

VAR
str1 : STRING(5);
END_VAR
(* The constant 16#4F4B is shown as
the string ’OK’ *)

LD 16#4F4B
UNIT_TO_STRING
ST str1
LD str1

END_PROGRAM
02/00 AWB 2700-1306 GB

130
 Type conversion of STRING to UINT
PS 4-300
PS 416

Function prototype

Description
The two-character string specified in the input
operand of the data type STRING is converted into
the data type UINT. The left-hand character of the
string is supplied in the high byte and the right-hand
character in the low byte. The bit pattern of the input
and output operands remains unchanged.
If the character string consists of more than two
characters only the two left-hand characters are
evaluated. A single character is supplied in the low
byte.
02/00 AWB 2700-1306 GB

131
 Functions

Type conversion of ANY_INT to BCD

Function prototype

Description
In a real case the character * would be replaced by
the function name.
The input value is first converted into a BCD value
which is then output as bit pattern data type
(ANY_BIT). The length of the output variable need not
be the same as the size of the BCD value. The most
significant bits will be lost if the bit pattern data type
assigned for the representation of the BCD result is
too small. The following type conversions are
possible:
Function name Comment

USINT_TO_BCD The result contains the BCD coded input value.

UINT_TO_BCD
UDINT_TO_BCD1)

SINT_TO_BCD The result contains the BCD coded input value. A

INT_TO_BCD negative input number is beforehand converted
DINT_TO_BCD1) to a positive number; the sign cannot be
represented.

1) PS 416, PS 4-300 only

02/00 AWB 2700-1306 GB

132
 Type conversion of BCD to ANY_INT

Function prototype

Description
In a real case the character * would be replaced by
the function name.
The input value coded in a bit pattern of data type
BCD is converted to a binary-coded decimal value.
The input variable can be assigned any bit pattern
data type, irrespective the length of the output
variable.
The following type conversions are possible:
Function name Comment

BCD_TO_USINT The positive BCD value of max. 255 (decimal) is

converted to a decimal value. There is no
overflow with higher input values.

BCD_TO_UINT The positive BCD value of max. 65.535 (decimal)

is converted to a decimal value. There is no
overflow with higher input values.

BCD_TO_UDINT1) The positive BCD value of max. 99.999 (decimal)

is converted to a decimal value.

BCD_TO_SINT The positive BCD value of max. 255 (decimal) is

converted to a decimal value. There is no
overflow with higher input values.

BCD_TO_INT The positive BCD value of max. 65.535 (decimal)

is converted to a decimal value. There is no
02/00 AWB 2700-1306 GB

overflow with higher input values.

BCD_TO_DINT1) The positive BCD value of max. 99.999 (decimal)

is converted to a decimal value.

1) PS 416, PS 4-300 only

133
 Functions

Example: type conversion BCD_TO_USINT

The BCD-coded value 137 (decimal) is converted to
a decimal value and output as data type USINT.
BCD value 137 (decimal) USINT
0000 0001 0011 0111 1000 1001

02/00 AWB 2700-1306 GB

134
 Type conversion of ADDRESS to UINT
PS 4-300
PS 416

Function prototype

Description
The data type of a variable or a function block
parameter is converted from ADDRESS to UINT.
With this, addresses of block copy functions, for
example, can be saved for further evaluation in
variables of type UINT since variables of type
ADDRESS cannot be declared.
Example: invocation of the function
ADDRESS_TO_UINT
PROGRAM addr_conv

VAR
Start_data_field AT %MB0.0.0.0 : BYTE ;
Address1 : UINT ;
Copy : BlockTransfer ;
END_VAR

LD &Start_data_field
ST Copy.SourceAddress
ADDRESS_TO_UINT
ST Address1

END_PROGRAM
02/00 AWB 2700-1306 GB

135
 Functions

ABS
Summation

Function prototype

Description
The function ABS converts the numeric variable to
a summation number; the data type remains
unchanged.
The smallest SINT value (-128) and the smallest INT
value (-32768) are not modified by the ABS function
since the binary values for -128 / +128 and -32768 /
+32768 are identical. If such values occur in the
ABS function, an error message will not be
generated.

02/00 AWB 2700-1306 GB

136
 ADD

ADD
Multiple addition of numeric data types

Function prototype

Meaning of operands
IN1 The first addend must be provided via the
working register.
IN2 Further addends which are included in the
addition.
.
.
INn
Description
The value in the working register is added to the
values of the operands IN2 to INn. All input operands
are of the same numeric data type. The result is
made available in the working register for further
processing. If the result exceeds the range of values
permitted for the data type used an overflow will be
formed.
The data type of the result corresponds to the
selected data type of the input operand.
02/00 AWB 2700-1306 GB

With a function invocation all of the input operands

must be of the same data type.

137
 Functions

Example: addition of numeric data types

PROGRAM add3fach

VAR
A : INT := 7;
B : INT := 2;
Sum : INT;
END_VAR

LD 3
ADD A
ADD B
ST Sum (* Sum: 12 *)
END_PROGRAM

Example: invocation of the function ADD in FBD

The function ADD can be extended in the graphic
representation in LD and FBD - more than two input
operands can be processed.

Example: invocation of the function ADD in FBD

In IL multiple input operands are handled by the
sequential processing of two operands each time.
The following IL listing shows how this is done. The
second listing will produce an error message.
LD Var1 (* Do it like this:*)
ADD Var2
ADD Var3
02/00 AWB 2700-1306 GB

ST Result

LD Var 1 (* Not like this: *)

ADD Var2, Var3
ST Result

138
 ADD

ADD
Addition of duration to time and date

Function prototype

The following data type combinations of the

operands are possible:
Input operand IN1 Input operand IN2 Output operand

TIME TIME TIME

TIME_OF_DAY TIME TIME_OF_DAY

DATE_AND_TIME1) TIME DATE_AND_TIME

1) PS 416, PS 4-300 only

Description
The input variable is increased by a time value and
the result is loaded into the working
register.Example: addition of time values
Only for PS 4-200:
An ADD operation with the data type TIME only
supplies correct results in the positive range.
Do not run this operation with negative values.
02/00 AWB 2700-1306 GB

139
 Functions

Example: “Addition of time”

PROGRAM time_add

VAR
Time1 : TIME_OF_DAY := TOD#15:25:00.00;
Time_value : TIME := T#10h6m15s;
New_time : TIME_OF_DAY;
END_VAR

LD Time1
ADD Time_value
ST New_time
(* New_time: TOD#01:31:15.00 *)
END_PROGRAM

02/00 AWB 2700-1306 GB

140
 ADD

ADD
Addition of addresses

Function prototype

The following data type combinations of the

operands are possible:
Input operand IN1 Input operand IN2 Output operand

ADDRESS ANY_INT ADDRESS

ADDRESS ADDRESS ADDRESS

Description
The input variable is increased and the result is
loaded into the working register.
Loops or conditions for function blocks can be
calculated with ADDRESS parameters, e. g. for
SDAT or BlockCopy. The address of a variable is
loaded by writing the address operand & in front of
the variable name.
Example: addition of addresses
PROGRAM adr_add
VAR
Start_data_field AT %MB0.0.0.0 : BYTE ;
Shift: UINT := 10 ;
Copy : BlockCopy ;
END_VAR
02/00 AWB 2700-1306 GB

LD &Start_data_field
ADD Shift
ST Copy.SourceAddress
END_PROGRAM

141
 Functions

PS 4-300 CONCAT
PS 416 Concatenation of strings

Function prototype

Meaning of operands
IN1 Single strings to be concatenated into one
string.
.
.
INn
Description
String “IN1” in the working register and string “IN2”
to “INn” are concatenated. The resulting string is
loaded into the working register. Strings “IN1” to
“INn” are written from left to right in ascending order.
02/00 AWB 2700-1306 GB

142
 CONCAT

Example “Concatenate strings”

PROGRAM n_texts

VAR
Text1 : STRING := ’ab’;
Text2 : STRING := ’cd’;
Text3 : STRING := ’ef’;
Texts_1_2_3 : STRING;
END_VAR

LD Text1
CONCAT Text2, Text3
ST Texts_1_2_3 (* Texts_1_2_3:
’abcdef’ *)
END_PROGRAM
02/00 AWB 2700-1306 GB

143
 Functions

PS 4-300 CONCAT
PS 416 Concatenation of time and date

Function prototype

Meaning of operands
IN1 Date
IN2 Time1
Description
Date “IN1” and time “IN2” are combined to form a
data element of type DATE_AND_TIME and the result
is loaded into the working register.
Example “Deadline from time and date“
PROGRAM deadline

VAR
Date1 : DATE := D#1997-05-10;
Time : TIME_OF_DAY := T0D#6:35:00.00;
Date_and_Time1 : DATE_AND_TIME;
END_VAR

LD Date1
CONCAT Time1
ST Date_and_Time1
(* Date_And_Time1:
DT#1997-05-10-6:35 *)
END_PROGRAM
02/00 AWB 2700-1306 GB

144
 DELETE

PS 4-300 DELETE
PS 416 Delete n characters from string

Function prototype

Meaning of operands
IN String containing the series characters to be
deleted, made available via the working
register.
L Number of characters to be deleted.
P Position of the character to be deleted from.
1 corresponds to 1st character.
Description
“L” characters from position “P” are to be deleted
from string “IN”. The resulting string is loaded into
the working register.
If L = 0 or P > than the current length of “IN”, IN is
returned unchanged.
02/00 AWB 2700-1306 GB

145
 Functions

Example “Delete three characters from a string”

PROGRAM delete

VAR
Text1 : STRING := ’abABCDcd’;
Length : UINT := 3;
Position : UINT := 5;
Text2 : STRING;
END_VAR

LD Text1
DELETE Length, Position
ST Text2 (* Text2: ’abABd’ *)
END_PROGRAM

02/00 AWB 2700-1306 GB

146
 Disable_Interrupt

Disable_Interrupt
Disable alarm

Function prototype

Description
An interrupt is disabled to prevent it interrupting the
read or write process of a main program. Interrupt
sources are the functions blocks: CounterAlarm,
EdgeAlarm and TimerAlarm for PS 4-300, PS 4-200;
CAlarm, FAlarm and TAlarm for PS 416.
The invocation of the function Disable_Interrupt
disables the Interrupt source which one of the
function blocks mentioned above has previously
started. This synchronises the access of the main
program and the Interrupt routine to common
data. Write accesses are affected (ST, S, R).
The instruction is programmed as an independent
sequence.
An element of the ALARM_CHANNEL enumeration
data type is transferred as argument for the function
Disable_Interrupt:
For PS 4-200
TYPE ALARM_CHANNEL
(CounterAlarm_Channel,
TimerAlarm_Channel,
EdgeAlarm_Channel):= CounterAlarm_Channel;
END_TYPE
02/00 AWB 2700-1306 GB

147
 Functions

For PS 4-300
TYPE ALARM_CHANNEL
(CounterAlarm_Channel, (*0*)
TimerAlarm_Channel, (*1*)
EdgeAlarm_Channel_1, (*2*)
EdgeAlarm_Channel_2):= CounterAlarm_Channel;
END_TYPE

For PS 416
TYPE ALARM_CHANNEL
(CounterAlarm_Channel, (*0*)
TimerAlarm_Channel, (*1*)
EdgeAlarm_Channel_1, (*2*)
EdgeAlarm_Channel_2, (*3*)
EdgeAlarm_Channel_3, (*4*)
EdgeAlarm_Channel_4, (*5*)
EdgeAlarm_Channel_5, (*6*)
EdgeAlarm_Channel_6, (*7*)
EdgeAlarm_Channel_7, (*8*) (*.._8: 9*)
EdgeAlarm_Channel_8):= CounterAlarm_Channel;
END_TYPE

If the Interrupt source is disabled, all instances of

alarm function blocks belonging to this interrupt
source will also be disabled at the same time.

02/00 AWB 2700-1306 GB

148
 Disable_Interrupt

Example: disable interrupt

PROGRAM D_Alarm

VAR_GLOBAL
Buffer : INT ;
Edge_alarm : EdgeAlarm ;
I_Routine : AlarmFB ;
END_VAR

CAL Edge_alarm (EnableDisable := 1,

Number := 0,
RisingEdge := 0,
SetPointValue := 1,
Subroutine := I_Routine)
LD EdgeAlarm_Channel
Disable_Interrupt (* Alarm source for Edge *)
(* Alarm is disabled *)
LD 500
ST Buffer
LD EdgeAlarm_Channel
Enable_Interrupt (* Alarm source is *)
(* enabled again *)
END_PROGRAM

FUNCTION_BLOCK AlarmFB
VAR_EXTERNAL
Buffer : INT ;
END_VAR

LD 30000
ST Buffer
END_FUNCTION_BLOCK
02/00 AWB 2700-1306 GB

149
 Functions

DIV
Division of numeric data types

Function prototype

Meaning of operands
IN1 The dividend is provided via the working
register.
IN2 Divisor
For this function all of the input operands must be of
the same data type.
Description
The value in the working register is divided by the
value of the operand IN2. The two input operands are
of the same data type. The result is made available
in the working register for further processing. If a
division operation results in a remainder this will be
added as a carry to the carry register.
Example: division of numeric data types
PROGRAM divide

VAR
A : INT := 15;
B : INT := 3;
Quotient : INT;
END_VAR

LD A
02/00 AWB 2700-1306 GB

DIV B
ST Quotient (* Quotient: 5 *)

END_PROGRAM

150
 DIV

PS 4-300 DIV
PS 416 Division of duration

Function prototype

Meaning of operands
IN1 Time value of time duration data type
IN2 Value by which the address operand IN1 is
divided.
Example: division of a time value
PROGRAM Divide_time

VAR
Time_old : TIME := T#2h34m;
Number : SINT := 2;
Time_new : TIME;
END_VAR

LD Time_old
DIV Number
ST Time_new (* Time_new :T#1h17m *)

END_PROGRAM
02/00 AWB 2700-1306 GB

151
 Functions

PS 4-200 DIV
PS 4-300 Division of addresses

Function prototype

The following data type combinations of the

operands are possible:
Input operand IN1 Input operand IN2 Output operand

ADDRESS ANY_INT ADDRESS

ADDRESS ADDRESS ADDRESS

Description
The input variable is divided by a divisor and the
result is loaded into the working register.
Loops or conditions for function blocks can be
calculated with ADDRESS parameters, e. g. for
SaveData or BlockCopy. The address of a variable is
loaded by writing the address operand & in front of
the variable name.
Example: division of addresses
PROGRAM addr_div
VAR
Start_Data_Field AT %MB0.0.0.30 : BYTE ;
Offset : UINT := 10 ;
Copy : BlockCopy ;
END_VAR
02/00 AWB 2700-1306 GB

LD &Start_Data_Field
DIV Offset
ST Copy.SourceAddress
END_PROGRAM

152
 Enable_Interrupt

Enable_Interrupt
Enable alarm

Function prototype

Description
An interrupt which has previously been disabled via
the function Disable_Interrupt is enabled via the
Enable_Interrupt function. Interrupt sources are the
CounterAlarm, EdgeAlarm and TimerAlarm function
blocks for PS 4-200 and PS 4-300; CAlarm, EAlarm
and TAlarm for PS 416. The instruction is
programmed as an independent sequence.
An element of enumerated data type
ALARM_CHANNEL is transferred as argument for
the function Enable_Interrupt.
For PS 4-200
TYPE ALARM_CHANNEL
(CounterAlarm_Channel,
TimerAlarm_Channel,
EdgeAlarm_Channel):= CounterAlarm_Channel;
END_TYPE

For PS 4-300
TYPE ALARM_CHANNEL
(CounterAlarm_Channel, (*0*)
TimerAlarm_Channel, (*1*)
EdgeAlarm_Channel_1, (*2*)
EdgeAlarm_Channel_2):= CounterAlarm_Channel;
END_TYPE
02/00 AWB 2700-1306 GB

153
 Functions

For PS 416
TYPE ALARM_CHANNEL
(CounterAlarm_Channel,(*0*)
TimerAlarm_Channel, (*1*)
EdgeAlarm_Channel_1, (*2*)
EdgeAlarm_Channel_2, (*3*)
EdgeAlarm_Channel_3, (*4*)
EdgeAlarm_Channel_4, (*5*)
EdgeAlarm_Channel_5, (*6*)
EdgeAlarm_Channel_6, (*7*)
EdgeAlarm_Channel_7, (*8*) (*.._8: 9*)
EdgeAlarm_Channel_8):= CounterAlarm_Channel;
END_TYPE

If the interrupt source is enabled, all instances of the

alarm function blocks related to this interrupt source
will be enabled simultaneously.
Example: Enable alarm
PROGRAM E_Alarm

VAR_GLOBAL
Buffer : INT ;
Edge_Alarm : EdgeAlarm ;
I_Routine : AlarmFB ;
END_VAR

CAL Edge_Alarm (EnableDisable := 1,

Number := 0,
RisingEdge := 0,
SetPointValue := 1,
Subroutine := I_Routine)
LD EdgeAlarm_Channel
Disable_Interrupt
(*Alarm source for EdgeAlarm is disabled*)
LD 500
ST Buffer
LD EdgeAlarm_Channel
Enable_Interrupt
(*Alarm source is enabled*)
02/00 AWB 2700-1306 GB

END_PROGRAM

154
 Enable_Interrupt

FUNCTION_BLOCK AlarmFB

VAR_EXTERNAL
Buffer : INT ;
END_VAR

LD 30000
ST Buffer

END_FUNCTION_BLOCK
02/00 AWB 2700-1306 GB

155
 Functions

PS 4-300 FIND
PS 416 Find Character Sequence within a String: FIND

Function prototype

Meaning of operands
IN1 Basic string containing a specific sequence
of characters that is to be found. It is made
available via the working register.
IN2 Sequence of characters for which the basic
string “IN1” is searched.
Description
A specific sequence of characters is searched for in
the basic string “IN1”. If the characters searched for
are found, the position of the first character is
entered in the working register. Otherwise the value
“0” is output.
If the succession of characters is present several
times in the basic string, the first string found is
taken. A 0 is returned if one of the parameters is an
empty string.
02/00 AWB 2700-1306 GB

156
 FIND

Example “Find character sequence in string”

PROGRAM find

VAR
Basic_Text : STRING := ’On_condition’;
Find_Text : STRING := ’On’;
Position : INT;
END_VAR

LD Basic_Text
FIND Find_Text
ST Position (* Position: 4 *)
END_PROGRAM
02/00 AWB 2700-1306 GB

157
 Functions

GetCarryRegister
Carry after multiplication or remainder after
division

Function prototype

Description
The function GetCarryRegister refers to the result
of a multiplication or division that has just been
executed. If a multiplication has produced a carry,
this is stored in the carry register. If a division has
produced a remainder, this is also stored in the carry
register. The function GetCarryRegister therefore
accesses the carry register and loads its contents
into the working register.
No carry or remainder is formed after multiplication
of USINT, SINT and real data types (PS 416,
PS 4-300). The compiler supplies the corresponding
error message.
Example: get remainder of a division
PROGRAM remainder
VAR
Number : INT := 127;
Result_integer : INT;
Result_remainder : INT;
END_VAR

LD Number
DIV 4
ST Result_integer (* Result_integer : 31 *)
02/00 AWB 2700-1306 GB

GetCarryRegister
ST Result_remainder (* Result_remainder : 3*)
.
.

END_PROGRAM

158
 INSERT

PS 4-300 INSERT
PS 416 Insert String in String

Function prototype

Meaning of operands
IN1 Basic string in which another string (IN2) is to
be inserted. The basic string is provided via
the working register.
IN2 String to be inserted in the basic string.
P Position of the character in the basic string
from which the string is inserted. 1 means the
1st character.
Description
String “IN2” is inserted into the basic string “IN1”
after the character with the number specified by the
P input operand. The resulting string is loaded into
the working register. If P is greater than the current
length of IN1, IN1 is returned unchanged.
02/00 AWB 2700-1306 GB

159
 Functions

Example “Insert string within string”

PROGRAM insert

VAR
Text1 : STRING := ’abcd’;
Text2 : STRING := ’ABCD’;
Position : INT := 2;
newText : STRING;
END_VAR

LD Text1
INSERT Text2, Position
ST newText (* newText:
’abABCDcd’ *)
END_PROGRAM

02/00 AWB 2700-1306 GB

160
 IsBitTrue

IsBitTrue
Test of a single bit in the result

Function prototype

Meaning of operands
IN Bit pattern in which a specified bit is tested
N Bit position
Input operand Input operand Output operand
ANY_BIT USINT Bool
ANY_BIT UINT Bool

Description
The status of the bit specified by operand N in bit
pattern IN is tested. The resulting value is sent to the
working register as the result.
This function is best used when followed by
conditional operations such as JMPC, JMPCN,
CALC, CALCN, RETC or RETCN.
Example: Testing a single bit in the result
PROGRAM bit_test
VAR
BitPattern : BYTE := 2#11010011;
Position :UINT := 4;
BitValue : BOOL;
END_VAR
02/00 AWB 2700-1306 GB

LD BitPattern
IsBitTrue Position
ST BitValue (* BitValue : 1 *)
END_PROGRAM

161
 Functions

IsCarry
Test of the carry bit

Function prototype

Description
The function IsCarry refers to the result of the previ-
ously executed arithmetic function which checks the
Boolean value of the carry bit and transfers the result
to the working register.
The IsCarry function should only be used with shift
operations (SHL,SHR etc.) since it is the carry bit
which is evaluated here. IsCarry should not be used
for arithmetical operations. To evaluate the
overshoot of the value range in arithmetical
operations, you must use the IsOverflow function.
This function is best used when followed by
conditional operations such as JMPCN, CALCN, or
RETCN.
Example: Testing the carry bit
PROGRAM carrybit
VAR
Edge : R_TRIG;
Signal : AT %I0.0.0.0.0 : BOOL;
Impulse : BOOL;
Byte1 : BYTE := 2#11110000;
END_VAR
LD Byte1
SHL 3
02/00 AWB 2700-1306 GB

BYTE_TO_USINT
IsCarry (* Carry register = 1 *)
CALC Edge (CLK := Signal)
LD Edge.Q
ST Impulse
END_PROGRAM

162
 IsOverflow

IsOverflow
Test of the overflow bit

Function prototype

Description
The function refers to the result of the previously
executed arithmetic function which transfers the
Boolean value of the overflow bit to the working
register. The overflow bit has the Boolean value 1 if
the result of the previous operation exceeds the
entered value range of the data type. If the result is
within the value range, the overflow bit is 0.
This function is best used when followed by
conditional operations such as JMPC, JMPCN,
CALC, CALCN, RETC or RETCN.
Example: Testing the overflow bit
PROGRAM overflow
VAR
Edge : R_TRIG;
Signal : AT %I0.0.0.0.0 : BOOL;
Impulse : BOOL;
Number1 : SINT := 127;
END_VAR

LD Number1
ADD 12
IsOverflow
CALC Edge (CLK := Signal)
LD Edge.Q
02/00 AWB 2700-1306 GB

ST Impulse
END_PROGRAM

163
 Functions

IsPositive
Test whether result is positive

Function prototype

Description
The function IsPositive refers to the result of the
previously executed arithmetic function If the result is
greater than or equal zero, 1 is loaded into the
working register.
The IsPostive function is compatible with Sucosoft
S 30. In the case of unsigned variables (UINT,USINT
etc.) which are greater than the maximum range / 2,
IsPositive will deliver a 0 but in all other cases a 1.
This function is best used when followed by
conditional operations such as JMPCN, CALCN,
RETCN.
Example: Testing whether the result is positive
PROGRAM res_pos

VAR
Edge : R_TRIG;
Signal : AT %I0.0.0.0.0 : BOOL;
Impulse : BOOL;
Number1 : INT := 12;
END_VAR

LD Number1
SUB 10
IsPositive
02/00 AWB 2700-1306 GB

CALC Edge (CLK := Signal)

LD Edge.Q
ST Impulse

END_PROGRAM

164
 IsZero

IsZero
Test of the zero bit

Function prototype

Description
The function IsZero refers to the result of the
previously executed arithmetic function which
transfers the Boolean value of the zero bit to the
working register. The zero bit has the value 0 if the
previous operation supplies the value 0. If the result
is not equal 0, the zero bit is 1.
This function is best used when followed by
conditional operations such as JMPC, JMPCN,
CALC, CALCN, RETC or RETCN.
Example: Testing the zero bit
PROGRAM zero_bit
VAR
Edge : R_TRIG;
Signal : AT %I0.0.0.0.0 : BOOL;
Impulse : BOOL;
Number1 : INT := 12;
END_VAR

LD Number1
SUB 12
IsZero
CALC Edge (CLK := Signal)
LD Edge.Q
ST Impulse
02/00 AWB 2700-1306 GB

END_PROGRAM

165
 Functions

PS 4-300 LEFT
PS 416 Select n Characters Left Of String

Function prototype

Meaning of operands
IN String containing the left section of length L to
be taken. It is loaded into the working register.
L Number of characters left of the STRING
operand IN to be loaded into the working
register.
Description
The function LEFT takes the left section of the
string present in the working register and enters this
section in the working register. The number of
characters to be taken is specified by input
operand L.
Example “Take the first four characters”
PROGRAM le_text

VAR
String1 : STRING := ’Teststring’;
CharNo : INT := 4;
n_left_chars : STRING;
END_VAR

LD String1
LEFT CharNo
ST n_left_chars (* n_left_characters:
02/00 AWB 2700-1306 GB

’Test’ *)
END_PROGRAM

166
 LEN

LEN
Determination of the character string length

Function prototype

Description
The function LEN determines the length of the
character string in the working register (input
operand of data type STRING) and enters the
determined value as INT number into the working
register.
Example: determining the character string length
PROGRAM how_long
VAR
Text : STRING := ’Term’;
TextLength : INT;
END_VAR

LD Text
LEN
ST TextLength (* TextLength: 4 *)

END_PROGRAM
02/00 AWB 2700-1306 GB

167
 Functions

LIMIT
Value limitation

Function prototype

*) Supported data types: ANY_BIT, ANY_INT, ANY_DATE,

TIME, STRING(1).
All parameters must be the same data type.

Meaning of operands
MN Lower limit value
IN Test value
MX Upper limit value
Description
The values “MN” and “MX” specify the upper and
lower limit value. The function compares the test
value “IN” with “MN” and “MX”. If the “IN” value is
between the two limit values, it is loaded into the
working register. If “IN” is less than “MN”, the “MN”
value is output. The “MX” value is output if “IN” is
greater than “MX”.
02/00 AWB 2700-1306 GB

168
 LIMIT

Example “Measured value between 17 and 124”

PROGRAM limits

VAR
max_val : INT := 124;
min_val : INT := 17;
Measval AT %IW0.0.0.10:INT; (*IW0.0.0.10 *)
(* with value 135 *)
Result : INT;
END_VAR

LD min_val
LIMIT Measval, max_val
ST Result (* Result: 124 *)
END_PROGRAM
02/00 AWB 2700-1306 GB

169
 Functions

PS 4-300 MAX
PS 416 Maximum Selection

Function prototype

*) Supported data types: ANY_BIT, ANY_NUM,

ANY_DATE, TIME, STRING.
All parameters must be the same data type.
Meaning of operands
IN1 Input operand for which the highest value is
searched.
.
.
INn
Description
The MAX function determines which of the input
operands has the highest value. The specified
operand is loaded into the working register.
With STRING operands the current length is first
compared and the longer operand is loaded into the
working register. If both operands are the same
length, the operand is loaded which has a more
significant character.
02/00 AWB 2700-1306 GB

170
 MAX

Example “find maximum”

PROGRAM maximum

VAR
Value1 : SINT := 155;
Value2 : SINT := -24;
Value3 : SINT := -3;
Value4 : SINT := 5;
Maximumval : SINT;
END_VAR

LD Value1
MAX Value2, Value3, Value4
ST Maximumval (* Maximumval: 155 *)
END_PROGRAM
02/00 AWB 2700-1306 GB

171
 Functions

PS 4-300 MID
PS 416 Section of a String

Function prototype

Meaning of operands
IN String from which a sequence of characters is
to be removed. It is made available via the
working register.
L number of “IN” string characters to be cut.
P Position of the first character in the string to
be cut.
1 corresponds to the 1st character.
Description
“L” characters are to be cut from string “IN” starting
from position “P”. The cut string is loaded into the
working register. If “P” > current length of “IN”, “IN”
is returned unchanged. 02/00 AWB 2700-1306 GB

172
 MID

Example “Take part of string”

PROGRAM parttext

VAR
String : STRING := ’Test_string’;
CharNo : INT := 7;
Start : INT := 5;
Text_Section : STRING;
END_VAR

LD String
MID CharNo, Start
ST Text_Section
(*Text_section ’Characters’*)
END_PROGRAM
02/00 AWB 2700-1306 GB

173
 Functions

PS 4-300 MIN
PS 416 Minimum Selection

Function prototype
*) Supported data types: ANY_BIT, ANY_NUM,
ANY_DATE, TIME, STRING.
All parameters must be the same data type.
Meaning of operands
IN1 – INn Input operand for which the lowest value
is searched.
Description
The MIN function determines which of the input
operands has the lowest value. The specified
operand is loaded into the working register.
With STRING operands the current length is first
compared and the shorter operand is loaded into the
working register. If both operands are the same
length, the operand is loaded which has a less
significant character.
Example “Find minimum”
PROGRAM minimum
VAR
Value1 : SINT := 155;
Value2 : SINT := -24;
Value3 : SINT := -3;
Value4 : SINT := 5;
02/00 AWB 2700-1306 GB

Minimumval : SINT;
END_VAR
LD Value1
MIN Value2, Value3, Value4
ST Minimumval (* Minimumval: -24 *)
END_PROGRAM

174
 MOD

PS 4-300 MOD
PS 416 Remainder Division

MOD

ANY_INT IN1 ANY_INT

ANY_INT IN2

Function prototype

Description:
The input variable is divided by a divisor and the
remainder is loaded into the working register. The
MOD function is permissible for all ANY_INT types
and is only supported by the PS 416 and PS 416 and
PS 4-300.
On the PS 4-200 the remainder of a division is
processed using the GetCarryRegister function.
Example “MOD function” in the program
“mod_div”
PROGRAM mod_div

VAR
Dividend : UINT := 256;
Divisor : UINT := 50;
Remainder : UINT ;
END_VAR

LD Dividend
MOD Divisor
ST Remainder

END_PROGRAM
02/00 AWB 2700-1306 GB

175
 Functions

MUL
Multiplication of numeric data types

Function prototype

Meaning of operands
IN1 The first operand is supplied via the working
register.
IN2 Further operands involved in the multiplica-
tion.
.
.
INn
With a function invocation all of the input operands
must be of the same data type.
Description
The value in the working register is multiplied by the
values of the operands “IN2” to “INn”. All input
operands are of the same numeric data type. The
result is made available in the working register for
further processing. If the result exceeds the range of
values permitted for the data type used an overflow
will be formed.
02/00 AWB 2700-1306 GB

176
 MUL

Example: multiplication of numeric operands

PROGRAM mul3times

VAR
A : SINT := 5;
B : SINT := 2;
C : SINT := 3;
Product_3times : SINT;
END_VAR

LD A
MUL B
MUL C
ST Product_3times (* Product_3times: 30 *)
END_PROGRAM

Example: invocation of the function MUL in FBD

The MUL function is extendable in the LD and FBD
graphical programming languages – you can specify
more than two input operands.

Example: invocation of the function MUL in IL

In IL, more than two input operands are processed
by multiplying two at a time. The following IL listing
shows how this is done. The second listing produces
an error message.
LD Var1 (* Do it like this:*)
MUL Var2
MUL Var3
02/00 AWB 2700-1306 GB

ST Result

LD Var 1 (* Not like this *)

MUL Var2, Var3
ST Result

177
 Functions

PS 4-300 MUL
PS 416 Multiplication of time

Function prototype

Meaning of operands
IN1 Time value of time duration data type
IN2 Value by which operand “IN1” is to be
multiplied.
Description
The time duration operand “IN1” is multiplied by the
value “IN2” and the result is loaded into the working
register.
Example: multiplication of a time value
PROGRAM time_mul

VAR
Time_old : TIME := T#2h34m;
Number : USINT:= 2;
Time_new : TIME;
END_VAR

LD Time_old
MUL Number
ST Time_new (* Time_new: T#5h8m *)

END_PROGRAM
02/00 AWB 2700-1306 GB

178
 MUL

PS 4-200 MUL
PS 4-300 Multiplication of addresses

Function prototype

The following data type combinations of the

operands are possible:
Input operand IN1 Input operand IN2 Output operand

ADDRESS ANY_INT ADDRESS

ADDRESS ADDRESS ADDRESS

Description
The input variable is increased by a factor and the
result is loaded into the working register.
Loops or conditions for function blocks can be
calculated with ADDRESS parameters, e. g. for
SDAT or BlockCopy. The address of a variable is
loaded by writing the address operand & in front of
the variable name.
Example: multiplication of addresses
PROGRAM adr_mul

VAR
Start_ Datafield AT %MB0.0.0.2 : BYTE ;
Offset : UINT := 10 ;
Copy : BlockCopy ;
END_VAR
02/00 AWB 2700-1306 GB

LD &Start_ Datafield
MUL Offset
ST Copy.SourceAddress
END_PROGRAM

179
 Functions

PS 4-300 MUX
PS 416 Multiplexer

Function prototype

Meaning of operands
K Selection operand. Its numeric value depends
on the selected input operand IN0 to INn. It is
made available via the working register.
The permissible range of values for “K” is 0 – 6.
If the value is outside of the permissible range,
the highest permissible value will be taken.
IN0 Up to seven input operands between which
the selection is made. The input operand with
the number is selected that matches the value
“K”.
.
.
IN6
Description
The MUX function selects an input operand between
02/00 AWB 2700-1306 GB

“IN0” and “IN6” and transfers it to the working

register. The selection criterion is the operand
number 0 to 6 defined by input operand “K”.

180
 MUX

Example “Select second input operand”

PROGRAM select

VAR
IN_Nr : USINT := 2;
Numb0 : INT := 15;
Numb1 : INT := -123;
Numb2 : INT := 1;
SelectedNo : INT;
a, b, c, d, e, f, g, h, i, j, K : BYTE;
result : BYTE;
END_VAR

LD IN_Nr
MUX Numb0, Numb1, Numb2
ST SelectedNo (* SelectedNo: 1 *)
END_PROGRAM

Example “Selection with more than seven input

operands”
If more than seven parameters are required, the MUX
command must be converted into several
conditional calls
(* 10 input_operands..*)

LD K
MUX a, b, c, d, e, f, g, h, i, j
ST result

(* to be converted for operands 1 to 7: *)

LD K
GE 7
JMPC mux2

LD K
MUX a, b, c, d, e, f, g
ST result
JMP go_on

(* and operands 8 to 10: *)

MUX2:
02/00 AWB 2700-1306 GB

LD K
SUB 7
MUX h, i, j
ST result
go_on:

181
 Functions

NEG
Two’s complement

Function prototype

Description
The two's complement is formed for the numeric
value of data type ANY_INT. The result is made
available in the working register for further
processing. The two's complement of signed
numbers corresponds to the negation of a numeric
value. For example, 100 is converted to -100. With
unsigned values the two's complement formed is a
different value.
Example: two's complement
LD Signed_Number
NEG

Example: invocation of the function NEG

PROGRAM complement

VAR
Number : INT := 230;
Complement_Number : INT;
END_VAR

LD Number
NEG
ST Complement_Number (* Now contains the
value -230 *)

END_PROGRAM
02/00 AWB 2700-1306 GB

182
 NOT

NOT
Bitwise complement formation

Function prototype

Description
If the input operand is of data type BOOL, the bit in
the working register is negated. If the input operand
is of data type BYTE, WORD or DWORD1) the indivi-
dual bits are negated, i. e. the one’s complement is
formed.
The result is made available in the working register
for further processing.
The NOT function is set if it is necessary to load or
assign a negated value of data type BOOL, BYTE,
WORD or DWORD1).
Example: function NOT
LD BitPattern
NOT

Example: binary complement formation

PROGRAM negation
VAR
BitString : BYTE := 2#00110101;
Negation_Result : BYTE;
END_VAR

LD BitString
NOT
ST Negation_Result (* Negation_Result
2#11001010 *)
02/00 AWB 2700-1306 GB

END_PROGRAM

1) PS 416 and PS 4-300 only

183
 Functions

PLC_Message
System diagnostics evaluate message

Function prototype

Description
An element of the enumerated data type
Message_Type is sent to the input of type
Message_Type via the working register. The return
value is a BOOL value and indicates the status of the
bit in the message word selected via the enumerated
data element.
The enumeration type Message_Type which should
be used contains the following elements:
For PS 4-200
TYPE
MESSAGE_TYPE:
(ISA, (*First cycle after start*)
IRE, (*RESET button has been pressed*)
IFO, (*Forcing in RUN active *)
REC, (*Remaining cycle processed after
restart*)
ICS, (*PLC cold started *)
NKD_1, (*New data to SBI 1*)
NKD_2, (*New data to SBI 2*)
NKD_3 (*New data to SBI 3*)
) := ISA;
END_TYPE
02/00 AWB 2700-1306 GB

184
 PLC_Message

For PS 4-300
TYPE
MESSAGE_TYPE:
(ISA, (* =0:First cycle after start *)
IRE, (* =1:RESET button actuated *)
IFO, (* =2:Forcing in RUN active *)
REC, (* =3:Remaining cycle run
after restart
ICS, (* =4:PLC cold started*)
NKD_1, (* =5:New data to SBI 1*)
NKD_2, (* =6:New data to SBI 2*)
NKD_3, (* =7:NeW data to SBI 3*)
ICT, (* =8:ECT in first cycle *)
IAH, (* =9:EAH in first cycle *)
IRT, (* =10:ERT in first cycle *)
) := ISA;
END_TYPE

PS 416
TYPE
MESSAGE_TYPE:
(ICS, (* =0:Initial Cold Start cycle*)
ISA, (* =1:Initial Start Again*)
RTW, (* =2:Run Time Warning*)
REC, (* =3:Rest Cycle*)
DAKE,(* =AK Error; card not addressable or
not fitted*)
KOM, (* =5:Communication partner failed*)
) := ISA;
END_TYPE

The data type has been defined by Moeller and can

be used in the POUs immediately. The standard
setting is ISA.
Example: evaluating system diagnostics
message
LD SA
PLC_Message
02/00 AWB 2700-1306 GB

JMPCN No_new_start

185
 Functions

PLC_ReadClock
Read a single element of the real-time clock

Function prototype

Description
An element of the enumerated data type
PLC_CLOCK is sent to the input of type
CLOCK_ELEMENT via the working register. The
return value is of type USINT and indicates the value
of the specified element of the real-time clock.
The enumerated data type PLC_CLOCK to be used
contains the following elements:
TYPE
PLC_CLOCK:
(CK_YEAR, (*Year*)
CK_MONTH, (*Month*)
CK_DAY, (*Day*)
CK_WEEKDAY, (*Weekday; 0 = Sunday*)
CK_HOURS, (*Hours*)
CK_MINUTES, (*Minutes*)
CK_SECONDS (*Seconds*)
) := CK_YEAR;
END_TYPE

The data type is defined by Moeller and can be used

in the POUs immediately. CK_YEAR is the standard
setting.
Example: read an element of the real-time clock
PROGRAM RD_Clock
VAR
Hours : USINT ;
02/00 AWB 2700-1306 GB

END_VAR
LD CK_HOURS
PLC_ReadClock
ST Hours
END_PROGRAM

186
 REPLACE

PS 4-300 REPLACE
PS 416 Replace Characters in a String

Function prototype

Meaning of operands
IN1 String containing characters to be overwritten. It
is made available via the working register.

IN2 String in which string IN1 is used.

L Number of characters to be deleted.

P Position of the character in the string from which

the exchange is to be made.
1 corresponds to the 1st character

Description
A number of characters in string “IN1” as specified
by the input operand “L” is overwritten from position
P with string “IN2”. The number of deleted and
inserted characters can vary. The resulting string is
loaded into the working register.
L = 0 corresponds to the INSERT function. If P >
current length of IN1, IN1 is returned unchanged.
02/00 AWB 2700-1306 GB

187
 Functions

Example “Replace sections of a string”

PROGRAM replace

VAR
Old_Text : STRING := ’abbCDEe’;
New_Chars : STRING := ’cd’;
New_Text : STRING;
END_VAR

LD Old_Text
REPLACE New_Chars, 4, 3 (*L=4, P=3*)
ST New_Text (* New_Text:
’abcde *)
END_PROGRAM

02/00 AWB 2700-1306 GB

188
 RIGHT

PS 4-300 RIGHT
PS 416 Selection of n Characters Right of String

Function prototype

Meaning of operands
IN String containing right section of length “L” to
be taken. It is made available via the working
register
L Number of characters from right of STRING
operand “IN” to be loaded in the working
register.
Description
The function “RIGHT” takes the right section of the
string in the working register and transfers it to the
working register. The number of characters to be
taken is specified by input operand “L”.
Example “Take right section of a string”
PROGRAM re_text

VAR
String1 : STRING := ’Teststring’;
CharNo : INT := 5;
n_right_chars : STRING;
END_VAR

LD String1
RIGHT CharNo
ST n_right_chars (* n_right_chars:
02/00 AWB 2700-1306 GB

’String’ *)
END_PROGRAM

189
 Functions

ROL
Rotation left

Function prototype

Meaning of operands
IN The number (bit pattern) to be rotated of the
data type “BYTE”, “WORD” or “DWORD“1).
N Number of places by which the operand “IN”
is rotated to the left.
Description
The bit pattern entered as the operand “IN” is shifted
to the left by the number of places specified in the
operand “N”. The free places are filled with the
shifted bits. This shifted bit pattern is provided in the
working register. The result has the same data type
as the input operand “IN”.
Example: bit pattern rotation to the left
PROGRAM rot_le
VAR
Bit_pattern : BYTE := 2#01110001;
Places : INT := 3;
NewBitPattern: BYTE;
END_VAR

LD Bit_pattern
ROL Places
ST NewBitPattern (* NewBitPattern:
2#10001011 *)
02/00 AWB 2700-1306 GB

END_PROGRAM

1) For PS 4-300 and PS 416 only

190
 ROR

ROR
Rotation right

Function prototype

Meaning of operands
IN The number (bit pattern) to be rotated. Of data
type BYTE, WORD or DWORD1).
N Number of places by which the operand “IN”
is rotated to the right.
Description
The bit pattern entered as the operand “IN” is shifted
to the right by the number of places specified in the
operand “N”. The free places are filled with the
shifted bits. This shifted bit pattern is provided in the
working register. The result has the same data type
as the input operand “IN”.
Example: bit pattern rotation to the right
PROGRAM rot_ri
VAR
Bit_pattern : BYTE := 2#01110001;
Places : INT := 2;
NewBitPattern : BYTE;
END_VAR

LD Bit_pattern
ROR Places
ST NewBitPattern (* NewBitPattern:
2#01011100 *)
02/00 AWB 2700-1306 GB

END_PROGRAM

1) For PS 4-300 and PS 416 only

191
 Functions

PS 4-300 SEL
PS 416 Conditional Operand Selection

Function prototype

*) Supported data types: ANY_INT, ANY_BIT,

ANY_DATE, TIME, STRING.
Parameters IN0 and IN1 must be the same data
type.
Meaning of operands
G Boolean selection criterion
IN0 The first operand to be selected
IN1 The second operand to be selected
Description
The selection criterion “SEL” selects an input
operand “IN0” and “IN1”. The selection criterion is
the logic state of the input operand “G”. The operand
IN0 is selected with status “0” and input “IN1” with
status “1” of operand “G”. The selected operand is
loaded into the working register.
02/00 AWB 2700-1306 GB

192
 SEL

Example “Select either 'ABC' or 'abc' ”

PROGRAM select

VAR
Text1 : STRING := ’ABC’;
Text2 : STRING := ’abc’;
SelectorSwitch AT %I0.0.0.0.3 : BOOL;
Selected : STRING;
END_VAR

LD SelectorSwitch
SEL Text1, Text2
ST Selected (* The contents of the
variable selected
depends on the status
of I0.0.0.0.3 *)
END_PROGRAM
02/00 AWB 2700-1306 GB

193
 Functions

ShiftLeftCarry
Shift left with carry

Function prototype

Description
The bit pattern specified as the input operand is
shifted one bit to the left in the working register.
The bit position which becomes free is assigned the
original carry bit and the bit removed becomes the
new carry bit.
Data element of type BYTE:

Example: shift left with carry

PROGRAM shi_le
VAR
Bit_pattern : BYTE := 2#01100110;
NewBitPattern : BYTE;
END_VAR

LD Bit_pattern
ShiftLeftCarry
ST NewBitPattern (* NewBitPattern:
. 1100110x, x at the bit position 0 is
. the old value of the carry bit *)
END_PROGRAM
02/00 AWB 2700-1306 GB

194
 ShiftRightCarry

ShiftRightCarry
Shift right with carry

Function prototype

Description
The bit pattern specified as the input operand is
shifted one bit to the right in the working register.
The bit position which becomes free is assigned the
original carry bit and the bit removed becomes the
new carry bit.
Data element of type BYTE:
bit

Example: shift right with carry

PROGRAM shi_ri

VAR
Bit_pattern : BYTE := 2#01011100;
NewBitPattern : BYTE;
END_VAR

LD Bit_pattern
ShiftRightCarry
ST NewBitPattern
.
.
02/00 AWB 2700-1306 GB

END_PROGRAM

195
 Functions

SHL
Shift left

Function prototype

Meaning of operands
IN The number (bit pattern) to be shifted of the
data type BYTE, WORD or DWORD1).
N Number of places by which the operand “IN”
is shifted to the left.
Description
The bit pattern entered as the operand “IN” is shifted
to the left by the number of places specified in the
operand “N”. The free places are filled with the
zeroes. This shifted bit pattern is provided in the
working register. The result has the same data type
as the input operand “IN”.
Example: shift bit pattern left
PROGRAM shi_le

VAR
Bit_pattern : BYTE := 2#00111011;
Places : INT := 3;
NewBitPattern : BYTE;
END_VAR

LD Bit_pattern
SHL Places
ST NewBitPattern (* NewBitPattern
02/00 AWB 2700-1306 GB

2#11011000 *)
END_PROGRAM

1) Only for PS 416 and PS 4-300

196
 SHR

SHR
Shift right

Function prototype

Meaning of operands
IN The number (bit pattern) to be shifted of the
data type “BYTE”, “WORD” or “DWORD”1).
N Number of places by which the operand “IN”
is shifted to the right.
Description
The bit pattern entered as the operand “IN” is shifted
to the right by the number of places specified in the
operand “N”. The free places are filled with the zeros.
This shifted bit pattern is provided in the working
register. The result has the same data type as the
input operand “IN”.
Example: shift bit pattern right
PROGRAM shi_ri

VAR
Bit_pattern : BYTE := 2#00111011;
Places: INT:= 2;
NewBitPattern : BYTE;
END_VAR

LD Bit_pattern
SHR Places
ST NewBitPattern (* NewBitPattern:
02/00 AWB 2700-1306 GB

2#00001110 *)

END_PROGRAM

1) Only for PS 416 and PS 4-300

197
 Functions

SUB
Subtraction of numeric data types

Function prototype

Meaning of operands
IN1 Minuend from which the operand “IN2”
is subtracted. The minuend is supplied
via the working register.
IN2 Subtrahend which is subtracted from “IN1”.
Description
Operand “IN2” is subtracted from the value in the
working register (operand “IN1”). The result is made
available in the working register for further process-
ing. When negative numbers are subtracted, an
overflow will be sent to the overflow register if the
result exceeds the value range of the data type used.
With a function invocation all of the input operands
must be of the same data type.
Example: subtraction of numeric data types
PROGRAM aminusb
VAR
A : INT:= 123;
B : INT:= 12;
Difference : INT;
END_VAR

LD A
02/00 AWB 2700-1306 GB

SUB B
ST Difference (* Difference: 111 *)
END_PROGRAM

198
 SUB

SUB
Subtraction of time and date

Function prototype

The following data type combinations of the

operands are possible:
Input operand “IN1“ Input operand “IN2“ Output operand

TIME TIME TIME

DATE1) DATE TIME

TIME_OF_DAY TIME TIME_OF_DAY

TIME_OF_DAY TIME_OF_DAY TIME

1)
DATE_AND_TIME TIME DATE_AND_TIME
1)
DATE_AND_TIME DATE_AND_TIME TIME
1) Only for PS 416 and PS 4-300

Description
The input variable “IN1” is reduced by the value of
“IN2” and the result is loaded into the working
register.

Only PS 4-200:
SUB operation with the data type TIME supplies
only correct values in the positive value range.
Never carry out operations with negative values.
02/00 AWB 2700-1306 GB

199
 Functions

Example: subtraction of time values

PROGRAM time_sub

VAR
Time1 : TIME_OF_DAY := TOD#15:25:00.00;
Time_value : TME := T#3h6m15s;
New_time : TIME_OF_DAY;
END_VAR

LD Time1
SUB Time_value
ST New_time
(* New_time: TOD#12:18:45 *)

END_PROGRAM

02/00 AWB 2700-1306 GB

200
 SUB

PS 4-200 SUB
PS 4-300 Subtraction of addresses

Function prototype

The following data type combinations of the

operands are possible:
Input operand Input operand Output operand
IN1 IN2

ADDRESS ANY_INT ADDRESS

ADDRESS ADDRESS ADDRESS

Description
The input variable is decreased and the result is
loaded into the working register.
Loops or conditions for function blocks can be
calculated with ADDRESS parameters, e. g. for
SDAT or BlockCopy. The address of a variable is
loaded by writing the address operand & in front of
the variable name.
Example: subtraction of addresses
PROGRAM adr_sub
VAR
Start_Data_Field AT %MB0.0.0.20 : BYTE ;
Offset : UINT := 10 ;
Copy : BlockCopy ;
END_VAR
02/00 AWB 2700-1306 GB

LD &Start_Data_Field
SUB Offset
ST Copy.SourceAddress
END_PROGRAM

201
 Functions

TRUNC
PS 4-300
Integer part of a floating point number
PS 416

Function prototype

Description
The TRUNC function transfers the integer part of a
floating-point number (REAL variable) to a signed
integer variable.
The choice of data type for the result is dependent on
the value of the integer part of the input operand.
Example “Transfer integer part of number”
The program “integ_part” transfers the integer part
(up to 16 positions) of the variable “Fl_Pt_Number” to
the variable “Int_Value”.
PROGRAM integ_part

VAR
Fl_Pt_Number : REAL := 123.5;
Int_Value : INT;
END_VAR

LD Fl_Pt_Number
TRUNC
ST Int_Value (* Int_Value: 123 *)

END_PROGRAM
02/00 AWB 2700-1306 GB

202
 6 Function Blocks

Sucosoft provides a wide variety of function blocks

for your use. They can be classified into:
Function blocks as per the IEC 1131-3
Standard,
Moeller standard function blocks.
Function blocks complying with IEC 1131-3 standard
are defined so as to cover all vendors. PLC programs
which use only IEC function blocks can therefore be
used with controllers made by different manu-
facturers.
Moeller has added further function blocks to the
IEC functions. With a few exceptions the KM function
blocks can be used with all Moeller controllers.
The following table shows an overview of all function
blocks grouped according to the jobs they do. Each
function block is marked with ’IEC’ or ’ ’ and the
controller type specified where the function block
can be used without any modification.

Some of the functions described used the data

type ADDRESS. They are used for the automatic
conversion of programs from previous systems
and for this reason cannot be used with all
controllers. Such functions are marked # in the
following table.
The use of ARRAYs means that you have
functionally identical alternatives which can be
used with all controllers. Please use these when
you write new programs.
03/99 AWB 2700-1306 D

203
 Function Blocks
SSI

PS 4-200

PS 4-300

PS 416
Stand- See
Function block Meaning ard page
Edge detection
F_TRIG Edge evaluation, falling edge ✓ ✓ ✓ IEC 315
R_TRIG Edge evaluation, rising edge ✓ ✓ ✓ IEC 394
Bistable function blocks
RS RS-Flip-Flop ✓ ✓ ✓ IEC 417
SR SR-Flip-Flop ✓ ✓ ✓ IEC 490
Date and time
DATconcat Concatenate the data type DT ✓ ✓ ✓ M 277
DATsplit Split the data type DT ✓ ✓ ✓ M 281
DateConcat Concatenate the data type DATE ✓ ✓ ✓ M 277
DateSplit Split the data type DATE ✓ ✓ ✓ M 279

GetRealTimeClock Evaluation of the real-time clock ✓ ✓ ✓ M 325

RealTimeClock Comparing the real-time clock ✓ ✓ ✓ M 409
RTC Setting the real-time clock ✓ ✓ ✓ IEC 419
SetRealTimeClock*) Setting the real-time clock ✓, # ✓, # – M 459
TimeConcat Concatenate the data type TIME ✓ ✓ ✓ M 517
TimeSplit Split the data type TIME ✓ ✓ ✓ M 529
TODconcat Concatenate the data type TOD ✓ ✓ ✓ M 531
TODsplit Split the data type TOD ✓ ✓ ✓ M 533
Timer function blocks
MS_TimeFalling Off-delay timer milliseconds ✓ ✓ ✓ M 344
MS_TimeRising On-delay timer milliseconds ✓ ✓ ✓ M 347
S_TimeFalling Off-delay timer seconds ✓ ✓ ✓ M 421
S_TimeRising On-delay timer seconds ✓ ✓ ✓ M 424
TimeGenerator Pulse generator ✓ ✓ ✓ M 519
TimePulse Impulse timer ✓ ✓ ✓ M 521
TOF Off-delay ✓ ✓ ✓ IEC 535
TON On-delay ✓ ✓ ✓ IEC 537
TP Impulse ✓ ✓ ✓ IEC 539
03/99 AWB 2700-1306 D

204
 PS 4-200

PS 4-300

PS 416
Stand- See
Function block Meaning ard page
Alarm function blocks
CounterAlarm Counter alarm ✓ ✓ ✓ M 256
EdgeAlarm Edge-controlled alarm ✓ ✓ ✓ M 310
TimerAlarm Timer alarm ✓ ✓ ✓ M 523
Counter and comparison function blocks
_16BitCounter 16-bit up/down counter ✓ ✓ ✓ M 214
_32BitCounter 32-bit up/down counter – ✓ ✓ M 220
CounterLE Block for addressing the counter LE ✓ ✓ – M 261
CTD Down counter ✓ ✓ ✓ IEC 267
CTU Up counter ✓ ✓ ✓ IEC 268
CTUD Up/down counter ✓ ✓ ✓ IEC 269
_16Bit_Compare 16-bit compare ✓ ✓ ✓ M 210
_32Bit_Compare 32-bit compare – ✓ ✓ M 216
SSIEncoder Absolute encoder – ✓ – M 504
IncEncoder Incremental encoder – ✓ – M 327
Register function blocks
SR_x 1-bit shift register ✓ ✓ ✓ M 492
SRB_x 8-bit shift register ✓ ✓ ✓ M 496
SRW_x 16-bit shift register ✓ ✓ ✓ M 500
LifoBx 8-bit-LIFO register ✓ ✓ ✓ M 331
LifoWx 16-bit-LIFO register ✓ ✓ ✓ M 335
FifoBx 8-Bit-FIFO-Register ✓ ✓ ✓ M 317
FifoWx 16-Bit-LIFO-Register ✓ ✓ ✓ M 321
Code converter
_16BitBinaryToBCD 16-bit binary/decimal code converter ✓ ✓ ✓ M 212
_32BitBinaryToBCD 32-bit binary/decimal code converter – ✓ ✓ M 218
BCDTo16BitBinary 16-bit decimal/binary code converter ✓ ✓ ✓ M 227
BCDTo32BitBinary 32-bit decimal/binary code converter208 - ✓ ✓ M 229
06/99 AWB 2700-1306 GB

205
 Function Blocks

PS 4-200

PS 4-300

PS 416
Stand- See
Function block Meaning ard page
Array operations
BlockCompare *) Data-block comparison or searching for
values ✓, # ✓, # – M 231
BlockTransfer *) Copy or initialise data blocks
Comparison of arrays ✓, # ✓, # – M 236
CompareArray Transfer of arrays ✓ ✓ ✓ M 250
TransferArray Transfer data structures to an array ✓ ✓ ✓ M 541
Serialize Transfer array to data structures ✓ ✓ ✓ M 453
Deserialize ✓ ✓ ✓ M 298
Character string processing
ADRtoSTR Copy marker area to string ✓, # ✓, # – M 222
STRtoADR Copy string to a marker area ✓, # ✓, # – M 507
COMtoSTR Copy received characters to string ✓ ✓ ✓ M 254
STRtoCOM Copy string to marker area ✓ ✓ ✓ M 509
Sequential control function block
SFC_x Sequence control function block ✓ ✓ – M 462
Communication function blocks
COM Serial communication – – ✓ M 249
SCO *) Block for serial communication ✓ ✓ – M 430
PSCO Communication block Profibus ✓ ✓ – M 387
DialOrHangup Establish or clear a connection to a 301
DTE via modem – ✓ ✓ M 301
SendATCommand Send AT commands to a modem – ✓ ✓ M 446
MOD200 MODBUS communication – – ✓ M 343
SUCOM_A Emulation of programming protocol – ✓ ✓ M 511
SuconetP PROFIBUS-FMS communication – – ✓ M 515
SuconetS_BGKS INTERBUS communication – – ✓ M 516
DE4netK Frequency inverter DF 4 ✓ ✓ ✓ M
MI4K Touchpanel MI 4 ✓, # ✓, # – M 339
MI4netK Touchpanel MI 4 ✓ ✓ ✓ M 341
PdpStationDiag PROFIBUS-DP communication – ✓ ✓ M 369
ASi_PARAM ASI slave parameter function block ✓ ✓ – M 224
06/99 AWB 2700-1306 GB

DE4netDP Frequency inverter DF 4 – ✓ ✓ M 283

PdpFreezeSync PROFIBIS-DP control commands – ✓ ✓ M 355

206
 PS 4-200

PS 4-300

PS 416
Stand- See
Function block Meaning ard page
Read/write from/to memory card
SetMCFileLength Create and initialise data file on memory card – – 3 M 456
ReloadData *) Load data from memory card ✓, # 3 – M 414
SaveData *) Save data on memory card ✓, # 3 – M 427
3 3
ReadMC Read data from memory card ✓ 3
M 404
WriteMC Write data to memory card ✓ 3 M 550
OS system function blocks
PS_Diagnostic PS diagnostics words – – ✓ M 377
PS_Message PS message words – – ✓ M 381
PS_SwitchPosition PS switch positions – ✓ ✓ M 385
PS_GetDateAndTime Access to the real-time clock – ✓ ✓ M 379
PS_ApplicationHalt Pause the user program – ✓ ✓ M 373
PS_ReadOSInfo Check the operating system version ✓ ✓ ✓ M 383
PS_ClearKOMBit Acknowledge communication error – – ✓ M 375
CPUDataExchange Data exchange between CPUs – – ✓ M 263
ColdstartRetention Definition of a marker area which retains data
even after cold start – – ✓ M 245
Peripheral access
ReadDirect Direct reading from digital inputs – – ✓, # M 401
WriteDirect Direct writing to digital outputs – – ✓, # M 546
ReadAnalogDirect Direct reading from analog inputs – – ✓ M 395
WriteAnalogDirect Direct writing to analog outputs – – ✓ M 543
ReadCounterDirect Direct reading of counter inputs – – ✓ M 398
Conversion functions
DataScale Scaling of data ✓ ✓ ✓ M 271
PTtoCelsius Linearisation of PT1000 values ✓ 1) – – M 390
PTtoFahrenheit Linearisation of PT1000 values ✓ 1) – – M 392
NItoCelsius Linearisation of NI1000 values ✓ 1) – – M 350
NItoFahrenheit Linearisation of NI1000 values ✓ 1) – – M 352
IEEE to Real Number conversion – ✓ ✓ M 326
Real to IEEE Number conversion – ✓ ✓ M 408
06/99 AWB 2700-1306 GB

1) PS 4-271 only
*) These function blocks operate in a marker area which must be defined under
‹ Generate ➞ Program Parameters› when generating the code.

207
 Function Blocks

A detailed description of the function blocks (in

alphabetical order) starts on Page 210.
The interfaces of the parameter transfer are de-
scribed by means of the prototypes of the individual
function blocks. A prototype gives an overview of the
input and output operands of a function block. In IL
representation the prototype is the declaration section
of the function block with the declaration blocks of the
input and output operands contained in it.
For ease of understanding, the graphic prototype
representation is used in the description of the func-
tion blocks. Here the function block is represented as
a square graphical symbol with input operands on
the left and the output operands on the right side.
The name of the function block is shown in the
middle of the graphical symbol. The name of the
input operands appear on the left-hand side and the
names of the output operands on the right-hand
side. The data types of the operands are shown
outside the graphical symbol.
Taking the function block “R_TRIG” as an example
the prototype representation of the function block is
shown as an instruction list and also in graphic form.

06/99 AWB 2700-1306 GB

208
 Example: prototype representation
Comparison of an instruction list and graphical
representations of a prototype function block using
the R_TRIG function as an example.
FUNCTION_BLOCK R_TRIG

VAR_INPUT
CLK : BOOL;
END_VAR

VAR_OUTPUT
Q : BOOL;
END_VAR

END_FUNCTION_BLOCK

An instance is entered in the declaration section of

the invoking POU for a special application of a
function block. The name of the instance is entered
and the parameters are transferred when calling the
function block via the CAL command. You can find
further detailed information on function blocks and
their invocation in the program in the section
'Function blocks' (page 67).
06/99 AWB 2700-1306 GB

209
 Function Blocks

_16Bit_Compare
16-Bit Comparator

Prototype of the function block

Meaning of operands
InputValue1 First comparison value

InputValue2 Second comparison value

Greater Result: first value greater

Equal Result: both values equal

Less Result: first value less

Description
The _16Bit_Compare function block compares
InputValue1 to InputValue2 to see whether the value
of the number InputValue1 is greater, equal or less
compared with the value of the number InputValue2.
The result of the comparison is indicated by the three
output operands as follows:
Less Equal Greater

InputValue1 < InputValue2 1 0 0

InputValue1 = InputValue2 0 1 0
06/99 AWB 2700-1306 GB

InputValue1 > InputValue2 0 0 1

210
 _16Bit_Compare

Example: 16-bit comparator

PROGRAM length

VAR
Length_Compare : _16Bit_Compare;
Length1 : INT := 10;
Length2 : INT := 10;
L1_equal_L2 : BOOL;
END_VAR

CAL Length_Compare(InputValue1:=Length1,
InputValue2:=Length2)
LD Length_Compare.Equal
ST L1_equal_L2

END_PROGRAM
06/99 AWB 2700-1306 GB

211
 Function Blocks

_16BitBinaryToBCD
16-Bit Binary/Decimal Code Converter

Prototype of the function block

Meaning of operands
BinaryValue Binary-coded number

Signed Sign of BCD number, 0 for positive,

1 for negative number

DecimalHigh 5th decade of BCD number

DecimalLow 1st to 4th decade of BCD number

Description
A 16-bit binary number between -32768... +32767
at the BinaryValue operand is converted into a
BCD value. The four least significant digits of the
BCD value (1st – 4th decade) are written to the four
nibbles of the 16-bit DecimalLow operand in the
range. The most significant digit of the BCD value
(5th decade) is written to the least significant
nibble of the DecimalHigh operand. The sign of the
BCD value is shown in the Boolean Signed operand.
06/99 AWB 2700-1306 GB

212
 _16BitBinaryToBCD

Binary Value Binary Value Signed DecimalHigh DecimalLow

(hexadecimal) (decimal)

0000 0 0 0000 0000

0001 1 0 0000 0001
. . . . .
. . . . .
. . . . .
7FFF 32767 0 0003 2767
8000 –32768 1 0003 2768
8001 –32767 1 0003 2767
. . . . .
. . . . .
. . . . .
FFFF –1 1 0000 0001

Example: 16-bit binary/decimal code converter

PROGRAM du16_bcd

VAR
Converter1 : _16BitBinaryToBCD;
BinaryNumber : INT;
Sign : BOOL;
HighNumber : UINT;
LowNumber : UINT;
END_VAR

.
.
CAL Converter1 (BinaryValue := BinaryNumber)
LD Converter1.Signed
ST Sign
LD Converter1.DecimalHigh
ST HighNumber
LD Converter1.DecimalLow
ST LowNumber
.
.

END_PROGRAM
06/99 AWB 2700-1306 GB

213
 Function Blocks

_16BitCounter
16-Bit up/down counter

Prototype of the function block

Meaning of operands
Forward Up counter pulse, rising edge

Backward Down counter pulse, rising edge

Set Set condition, rising edge

ReSet Reset condition

InputValue Set value

Zero Signal: Counter status = 0

OutputValue Counter status

Description
The _16BitCounter function block is used for the up-
ward and downward counting of signals. Each rising
edge on the Forward input operand increments the
counter by one. A rising edge on the Backward input
operand decrements the counter by one. The current
06/99 AWB 2700-1306 GB

counter status is shown in the OutputValue operand.

A rising edge on the Set input transfers the value of
the InputValue to the counter. The counter is cleared
when the ReSet input is 1, and other counting
functions are disabled while the ReSet is 1.

214
 _16BitCounter

The counter range is between 0 and 65535. The

counter returns to 0 after it is incremented to 65535
and to 65535 after it is decremented to 0. A carry is
not formed in either case.
If the counter is not instantiated as retentive, it is
assigned the value 0 when it is initialised. The zero
output operand will then be 1. A retentive instantia-
tion of a counter retains its original value.
Example: 16-bit up counter
PROGRAM parts_16

VAR RETAIN
Count_parts : _16BitCounter;
END_VAR

VAR
Light_barrier AT %I0.0.0.0.0 : BOOL;
Quantity : UINT;
Clear AT %I0.0.0.0.1 : BOOL;
END_VAR

CAL Count_parts(Forward := Light_barrier,

ReSet := Clear)
LD Count_parts.OutputValue
ST Quantity

END_PROGRAM
06/99 AWB 2700-1306 GB

215
 Function Blocks

PS 4-300 _32Bit_Compare
PS 416 32-bit comparator

Prototype of the function block

Meaning of operands
InputValue1 First comparison value

InputValue2 Second comparison value

Greater Result: first value greater

Equal Result: both values equal

Less Result: first value less

Description
The _32Bit_Compare function block compares
InputValue1 to InputValue2 to see whether the value
of the number InputValue1 is greater, equal or less
compared with the value of the number InputValue2.
The result of the comparison is indicated by the three
output operands as follows:
Less Equal Greater

InputValue1< InputValue2 1 0 0

InputValue1 = InputValue2 0 1 0
06/99 AWB 2700-1306 GB

InputValue1 > InputValue2 0 0 1

216
 _32Bit_Compare

Example: 32-bit comparator

PROGRAM length

VAR
Length_Compare : _32Bit_Compare;
Length1 : DINT := 10;
Length2 : DINT := 10;
L1_equal_L2 : BOOL;
END_VAR

CAL Length_Compare(InputValue1:=Length1,
InputValue2:=Length2)
LD Length_Compare.Equal
ST L1_equal_L2

END_PROGRAM
06/99 AWB 2700-1306 GB

217
 Function Blocks

PS 4-300 _32BitBinaryToBCD
PS 416 32-bit binary/decimal code converter

Prototype of the function block

Meaning of operands
BinaryValue Binary-coded number

Signed Sign of BCD number, 0 for positive,

1 for negative number

OutputDecade1_4 1st to 4th decade of BCD number

OutputDecade5_8 5th to 8th decade of BCD number

OutputDecade9_10 9th to 10th decade of BCD number

Description
A 32-bit binary number between -2147483648...
+2147483647 at the BinaryValue operand is
converted to a BCD value. The individual digits of
the BCD number are output in the nibbles of the
operands OutputDecade1_4, OutputDecade 5_8 and
OutputDecade 9_10. The sign of the BCD value is
shown in the Boolean Signed operand.
06/99 AWB 2700-1306 GB

218
 _32BitBinaryToBCD

Binary Value Binary Value Signed OutputDecade1_4 OutputDecade5_8 OutputDecade9_10

(hexadec.) (decimal)

00000000 0 0 0000 0000 0000

00000001 1 0 0000 0000 0001
. . . . . .
. . . . . .
. . . . . .
7FFFFFFF 2147483647 0 0021 4748 3647
80000000 –2147483648 1 0021 4748 3648
80000001 –2147483647 1 0021 4748 3647
. . . . . .
. . . . . .
. . . . . .
FFFFFFFF –1 1 0000 0000 0001

Example: 32-bit binary/decimal code converter

PROGRAM du32_bcd

VAR
Converter2 : _32BitBinaryToBCD;
BinaryNumber : DINT;
Sign : BOOL;
Decade1_4 : UINT;
Decade5_8 : UINT;
Decade9_10 : UINT;
END_VAR

.
.
CAL Converter2(BinaryValue := BinaryNumber)
LD Converter2.Signed
ST Sign
LD Converter2.OutputDecade1_4
ST Decade1_4
LD Converter2.OutputDecade5_8
ST Decade5_8
LD Converter2.OutputDecade9_10
06/99 AWB 2700-1306 GB

ST Decade9_10
.
.
END_PROGRAM

219
 Function Blocks

PS 4-300 _32BitCounter
PS 416 32-bit up/down counter

Prototype of the function block

Meaning of operands
Forward Up counter pulse, rising edge

Backward Down counter pulse, rising edge

Set Set condition, rising edge

ReSet Reset condition

InputValue Set value

Zero Signal: Counter status = 0

OutputValue Counter status

Description
The _32BitCounter function block is used for the
upward and downward counting of signals. Each
rising edge on the Forward input operand increments
the counter by one. A rising edge on the Backward
input operand decrements the counter by one. The
06/99 AWB 2700-1306 GB

current counter status is shown in the OutputValue

operand. A rising edge on the Set input transfers the
value of the InputValue to the counter.

220
 _32BitCounter

The counter is cleared when the ReSet input is 1,

and other counting functions are disabled while the
ReSet is 1.
The counter range is between 0 and 4294967295.
The counter returns to 0 after it is incremented to
4294967295 and to 4294967295 after it is
decremented to 0. A carry is not formed in either
case.
If the counter is not instantiated as retentive, it is
assigned the value 0 when it is initialised. The zero
output operand will then be 1. A retentive instantia-
tion of a counter retains its original value.
Example: 32-bit up counter
PROGRAM parts_32

VAR RETAIN
Count_parts : _32BitCounter;
END_VAR

VAR
Light_barrier : AT %I0.0.0.0.6 : BOOL;
Quantity : UDINT;
Clear : AT %I0.0.0.0.7 : BOOL;
END_VAR

CAL Count_parts(Forward := Light_barrier,

ReSet := Clear)
LD Count_parts.OutputValue
ST Quantity

END_PROGRAM
06/99 AWB 2700-1306 GB

221
 Function Blocks

ADRtoSTR
Convert Received Characters to STRING

Prototype of the function block

Meaning of operands
Enable Enable the conversion

StrLen Number of characters to be converted

ReceiveVariable Start address of the marker area in which the data to

be converted is stored

TextString String created from the converted data in the marker

area

Description
The function block is used to convert text data
received via an interface and stored in a marker area
to a variable of data type ANY_STRING.
A static “1” or TRUE at the Enable input starts the
conversion. The input parameter “StrLen” defines
the number of characters to be converted and thus
the length of the resulting string.
If the declared length of TextString is insufficient to
hold all the converted data, characters are only
copied into it until it is full.
06/99 AWB 2700-1306 GB

222
 ADRtoSTR

Example: conversion of received characters into

string
PROGRAM Str_Gen

VAR
Marker_to_String : ADRtoSTR;
ReceiveText : STRING(4) := ’HALT’;
StartAddress AT %MB0.0.0.100 :
ARRAY[1..20] of BYTE;
ReceiveLength : UINT := 4;
END_VAR

CAL Marker_to_String (Enable := 1,

StrLen := ReceiveLength,
ReceiveVariable := &StartAddress,
TextString := ReceiveText)

END_PROGRAM
06/99 AWB 2700-1306 GB

223
 Function Blocks

PS 4-200 ASi_PARAM
PS 4-300 Change Slave Parameters During Operation

Prototype of the function block

Meaning of operands
Strobe Initiate an acyclic job (rising edge)
CardAddress Module number of the LE4-505-BS1 (1 or 2)
Command Command type
StationNo Address of slave (1 – 31) to be assigned
parameters
Parameter Parameters for the slave
Active Function block status
RetParam Send or read parameters
Error Result of job or detected errors

Description
The ASi-PARAM function block is used for changing
slave parameters during operation. Only one function
block needs to be active for each ASi LE.
A rising edge at the Strobe input causes the input
parameters to be transferred. At the same time the
Active output is set to 1 and keeps this state until the
job is completed. If the Active output is 0, the values
06/99 AWB 2700-1306 GB

at the “RetParam” and “Error” outputs can be

accepted.

224
 ASi_PARAM

The command type is input at the Command input:

02: Write parameters
03: Read parameters
Write parameters
When using the Write command the write address
must be specified at the StationNo input and the pa-
rameter at the Parameter input. The parameter is in
byte format. Only the 4 least significant bits are used.
Each bit represents a function of the ASi slaves.
Correct command execution is indicated with
“Active” = 0 and “Error” = 0, the slave has accepted
the data and the sent parameters are shown at the
RetParam output.
If the write command is not executed correctly, the
Error output will send an error code (see table).
Read parameters
When using the Read command the read address
must be specified at the StationNo input. Correct
command execution is indicated with “Active” = 0
and “Error” = 0, the slave has accepted the data and
the sent parameters are shown at the RetParam
output.
If the command is not executed correctly, the “Error”
output supplies the appropriate error code as a
decimal value instead of 0 (see table).

Error code Meaning when write command incorrectly Meaning when read command
(dec.) executed incorrectly executed

00 Everything OK
02 Invalid station number (cause: number less than 1 or greater than 31)
06/99 AWB 2700-1306 GB

03 Existing station not configured –

05 Station not responding (cause: line faulty or –
station missing)
08 – Command not executable at present, e. g.
due to absence of Asi voltage

225
 Function Blocks

Error code Meaning when write command incorrectly Meaning when read command
(dec.) executed incorrectly executed

Error code Meaning when write command incorrectly Meaning when read command incorrectly
(dec.) executed executed
17 ASi master not present, not configured, incorrect module type or module type or
CardAddress less than 1 or greater than 2
35 Invalid command
38 Command still active (the message only appears if a command has been started on a
second function block for the same ASi-LE)
39 “Parameter” is greater than 15 –

A more detailed description of this function block is

given in the manual AWB 27-1314-GB “Hardware
and Engineering, LE 4-505-BS1 (ASi LE)“.
Example “ASi_PARAM”
PROGRAM param
VAR
ASIPAbau : ASi_PARAM ;
Command1 : USINT : = 03 ;
ASiadr : USINT : = 02 ;
SLadr : USINT : = 01 ;
Data : Byte : = 2 ;
Pulse AT %I0.0.0.0.0 : BOOL ;
Busy : BOOL ;
Response : Byte ;
Diagnostics : USINT ;
END_VAR
CAL ASIPAbau(Strobe : = Pulse,
Command : = Command1,
CardAddress : = ASiadr,
StationNo : =SLadr,
Parameter : = Data
)
(*Output*)
LD ASIPAbau.Active
ST Busy
06/99 AWB 2700-1306 GB

LD ASIPAbau.RetParam
ST Response
LD ASIPAbau.Error
ST Diagnostics
END_PROGRAM

226
 BCDTo16BitBinary

BCDTo16BitBinary
16-bit decimal/binary code converter

Prototype of the function block

Meaning of operands
Signed Sign of the BCD number

DecimalValue BCD number, 4 nibbles

BinaryValue Binary number

Description
A BCD number between -9999 .... +9999 in the
4 nibbles of the DecimalValue operand, specified as
positive or negative by the Signed operand is
converted to a binary number and output via the
BinaryValue operand.
Signed Decimal Value Binary Value Binary Value
(decimal) (hexadecimal)

0 0011 11 B
0 9999 9999 270F
1 –1 3 1 1 –1311 FAE1
1 –9 9 9 9 –9999 D8F1
06/99 AWB 2700-1306 GB

227
 Function Blocks

Example: 16-bit decimal/binary code converter

PROGRAM bcd_du16

VAR
Converter3 : BCDTo16BitBinary;
DecimalNumber : UINT := 16#13;
Sign : BOOL := 0;
BinaryNumber : INT;
END_VAR

.
.
CAL Converter3(Signed := Sign,
DecimalValue := DecimalNumber)
LD Converter3.BinaryValue
ST BinaryNumber
.
.

END_PROGRAM

06/99 AWB 2700-1306 GB

228
 BCDTo32BitBinary

PS 4-300 BCDTo32BitBinary
PS 416 3232-bit decimal/binary code converter

Prototype of the function block

Meaning of operands
Signed Sign of the BCD number

DecimalValue BCD number, 8 decades

BinaryValue Binary number

Description
A BCD number between -99999999.... +99999999 in
the 8 digits of the DecimalValue operand, specified
as positive or negative by the Signed operand is
converted to a binary number and output via the
BinaryValue operand.
06/99 AWB 2700-1306 GB

229
 Function Blocks

Example: 32-bit decimal/binary code converter

PROGRAM bcd_du32

VAR
Converter4 : BCDTo32BitBinary;
DecimalNumber : UDINT := 13;
Sign : BOOL := 0;
BinaryNumber : DINT;
END_VAR

.
.
CAL Converter4(Signed := Sign,
DecimalValue := DecimalNumberl)
LD Converter4.BinaryValue
ST BinaryNumber
.
.

END_PROGRAM

06/99 AWB 2700-1306 GB

230
 BlockCompare

PS 4-200 BlockCompare
PS 4-300 Data Block Comparison or Value Search

Prototype of the function block

Meaning of operands
Mode Operating mode (0 = search, 1 = block
comparison)

SourceAddress Start address of search range

DestinationAddress Start address of destination range

ElementNumber Number of elements to be compared

Greater “Greater” indicator for comparison result

Equal “Equal” indicator for comparison result

Less “Less” indicator for comparison result

Output Indicates where unequal data or the specified

search value is located

Error Error code

Description
The BlockCompare function block has two operating
modes: Value Search or Block Comparison.
06/99 AWB 2700-1306 GB

The mode is set with the Mode input.

Use CompareArray in new programs instead of

BlockCompare.

231
 Function Blocks

Value Search mode

The Value Search mode is used to search for a
specified value in a data block. The value to search
for is specified in the marker entered under
SourceAddress. The start of the data block to be
searched is specified by DestinationAddress.
The length of the data block to be searched for is
specified by ElementNumber.
The Equal output will be set if the search criterion
is found within the data range specified by
SourceAddress and ElementNumber. Output
indicates the position of this value within the data
range:
Output = 0.. ElementNumber-1; Equal = 1;
The outputs Greater and Less are 0 in this case.
If the search criterion is not found, Output is set to
the same value as ElementNumber. The Equal output
is 0 and the outputs Greater and Less are set
accordingly.
Error codes at the Error output:
0 Data limits permissible
1 Number of elements (ElementNumber) is 0
2 Invalid source address at SourceAddress
3 Invalid destination address at
DestinationAddress
4 Source address is same as destination address
06/99 AWB 2700-1306 GB

232
 BlockCompare

Example: searching for data value

The following example searches in the marker area
from %MB0.0.0.27 to %MB0.0.0.32 for the value 7D
stored in %MB0.0.0.23.

PROGRAM search
VAR
search_fb: BlockCompare;
SourceAddress AT %MB0.0.0.23 : BYTE := 16#7D;
(* Marker byte 23 initialised with the
search value 7D hex *)
DestinationAddress AT %MB0.0.0.27 : BYTE;
Start AT %I0.0.0.0.0 : BOOL;
(* Start search *)
Found : USINT;
Result_greater : BOOL;
Result_equal : BOOL;
Result_less : BOOL;
END_VAR

LD Start
CALC search_fb(Mode := 0,(*Data search mode*)
SourceAddress := &SourceAddress,
DestinationAddress :=
06/99 AWB 2700-1306 GB

&DestinationAddress,
ElementNumber := 6)
(*Search range of 6 bytes*)
LD search_fb.Output
ST Found

233
 Function Blocks

(* Location where the search value is found *)

(* „DestinationAddress“ plus „Output“ *)
LD search_fb.Greater
ST Result_greater
LD search_fb.Equal
ST Result_equal
LD search_fb.Less
ST Result_less
END_PROGRAM

Block Comparison mode

The Block Comparison mode is used to compare
two data blocks. The start of the two data blocks is
specified with SourceAddress and
DestinationAddress. The size of the data blocks is
specified with ElementNumber.
If both data blocks are found to be identical, Output
will be set to the same value as ElementNumber and
the Equal output will be set to 1.
If the data blocks are not the same, Output will
indicate the location where there is a difference.
The Equal output will be set to 0 and the Greater or
Less outputs will be set according to the result of
comparison at the location where the discrepancy
was found.
Example of block comparison
06/99 AWB 2700-1306 GB

234
 BlockCompare

PROGRAM compare
VAR
compare_fb : BlockCompare;
Source_Address AT %MB0.0.0.23 : BYTE;
Destination_Address AT %MB0.0.0.30 : BYTE;
Start AT %I0.0.0.0.0 : BOOL;
(*Start the comparison*)
Discrepancy : USINT;
Result_greater : BOOL;
Result_equal : BOOL;
Result_less : BOOL;
END_VAR

LD Start
CALC compare_fb (Mode := 1,(*Block comparison mode*)
SourceAddress := &SourceAddress,
DestinationAddress := &DestinationAddress,
ElementNumber := 4)
(*Compare range of 4 bytes *)
LD compare_fb.Output
ST Discrepancy
(*Location where the blocks are different:*)
(* „DestinationAddress“ plus „Output“ *)
LD compare_fb.Greater
ST Result_greater
LD compare_fb.Equal
ST Result_equal
LD compare_fb.Less
ST Result_less
END_PROGRAM
06/99 AWB 2700-1306 GB

235
 Function Blocks

PS 4-200 BlockTransfer
PS 4-300 Copy or Initialise Data Blocks

Prototype of the function block

Meaning of operands
Mode Operating mode (0 = Initialise, 1 = Copy)

SourceAddress Start address of source range

DestinationAddress Start address of destination range

ElementNumber Number of elements to be copied

Error Error code

Description
The BlockTransfer function block allows system
support for transferring data blocks. Data is trans-
ferred from the source address defined at the
SourceAddress input to the destination in the PLC
memory defined at the DestinationAddress input.
The Mode input defines the operating mode to be
used: Copy mode or Initialise mode.
The size of the data block is defined in byte at the
ElementNumber input.
The Error output indicates the following error code:
0 Data limits permissible
06/99 AWB 2700-1306 GB

1 Number of elements (ElementNumber) is 0

2 Invalid source address at SourceAddress

236
 BlockTransfer

3 Invalid destination address at

DestinationAddress
4 Source address is same as destination address

Use TransferArray in new programs instead of

BlockTransfer.

Copy mode
In Copy mode the function block copies a complete
data range from a source address to a destination
address.
Example of Copy Mode
The contents of the data block marker bytes 23 to 26
are copied to marker area 30 to 33.

PROGRAM copy
VAR
copy_fb : BlockTransfer;
SourceAddress AT %MB0.0.0.23 : BYTE;
DestinationAddress AT %MB0.0.0.30 : BYTE;
Start AT %I0.0.0.0.0 : BOOL;
06/99 AWB 2700-1306 GB

(*Start copying*)
END_VAR

237
 Function Blocks

LD Start
CALC copy_fb (Mode := 1, (* Copy Mode ! *)
SourceAddress := &SourceAddress,
DestinationAddress
:= &DestinationAddress,
ElementNumber := 4)
(*Constant number of 4 bytes *)

END_PROGRAM

Initialise mode
In Initialise mode the function block copies a
specified value from the source address to a data
block starting with the destination address.
Example of Initialise Mode
The value of the marker byte specified in
SourceAddress is transferred into the number of
marker bytes specified in ElementNumber. The copy
operation starts from DestinationAddress. The
marker field %MB0.0.0.27 to %MB0.0.0.32 is
initialised with the data value 7D stored in
%MB0.0.0.23.

06/99 AWB 2700-1306 GB

238
 BlockTransfer

PROGRAM init

VAR
init_fb : BlockTransfer;
SourceAddress AT %MB0.0.0.23 : BYTE := 16#7D;
(* MarkerByte 23 initialised with the data value 7D hex *)
DestinationAddress AT %MB0.0.0.27 : BYTE;
Start AT %I0.0.0.0.0 : BOOL;
(*Start initialising*)
END_VAR

LD Start
CALC init_fb(Mode := 0, (* Initialise Mode *)
SourceAddress := &SourceAddress,
DestinationAddress := &DestinationAddress,
ElementNumber := 6)
(*Constant number of 6 bytes *)

END_PROGRAM
06/99 AWB 2700-1306 GB

239
 Function Blocks

PS 416 CAlarm
Counter Alarm Function Block

Prototype of the function block

Meaning of operands
Handle Reference to an external alarm routine function
block

EnableDisable Enable and disable alarm function

0: disable
1: enable

Number Alarm channel number (for PS 416 always 0)

Predivide Predivider for the counter,

valid range: 1 – 65535

SetpointValue Setpoint input for the alarm counter,

valid range: 1 – 65535

Error Error output

CountValue Counts hardware input signals when the CAlarm

function block is enabled.

CallUpNumber Counts alarm events when the CAlarm function

block is enabled.
06/99 AWB 2700-1306 GB

240
 CAlarm

Description
The CAlarm function block is used to count or detect
high-speed external signals. If an alarm is detected,
there are two possible responses to the alarm:
Interrogate the CallUpNumber output
The CallUpNumber output is incremented each
time an alarm event occurs. The user program
can interrogate this output to see whether and / or
how often an alarm has been triggered.
Execute an alarm routine
The alarm routine specified with Handle is called
each time an alarm event occurs. This allows an
event-controlled reaction to the alarm.
In the basic rack of the PS 416 CPU, the CAlarm
function block is permanently assigned to alarm
input %I0.0.0.0.0.
The edge-triggered EnableDisable input controls
the counter. The input is evaluated on an edge-
controlled basis. On detecting a rising edge at this
input (0->1, enable), the parameters of the input
operands are checked and the counter is started.
The alarm block has been successfully activated
when the Error output has 0 after the block is called.
A falling edge (1->0) stops the counter and the
outputs CountValue and CallUpNumber are reset.
The Predivide input specifies how many signals are
required on the hardware input to increment the
alarm counter by one.
The SetpointValue input specifies how many alarm
events are required to increment CallUpNumber by
one. If an alarm routine function block has been
06/99 AWB 2700-1306 GB

specified, it is then called.

241
 Function Blocks

A maximum counting frequency of 500 Hz can be

guaranteed with the setting Predivide = “1”
regardless of the PLC load.
The Error output can return the following values:
0 No errors, function block successfully activated
1 SetpointValue is “0”
2 Predivide is “0”
4 CAlarm function block already instantiated. This
error indicates that the CAlarm block has been
instantiated more than once.
5 Function block version not compatible with the
OS40 operating system of the PS 416.
10 Handle is invalid.
The CountValue output counts the number of signals
received at the hardware input %I0.0.0.0.0.
CountValue is reset to “0” each time Predivide is
reached.
The CallUpNumber output indicates how often
SetpointValue has been reached.
The Handle input specifies the optional external
alarm routine to be called. Specify 16#55AA if an
external alarm routine is not required.
For further information on handling alarm blocks see
the Appendix, page 564. 06/99 AWB 2700-1306 GB

242
 CAlarm

Example: CAlarm function block

Invocation of the CAlarm function block without
external alarm routine

PROGRAM CntAlarm

VAR CONSTANT
No_alarm_routine : UINT := 16#55aa;

END_VAR

VAR
EnableCAlarm AT %I0.0.0.0.7 :BOOL;
ErrorCAlarm : USINT;
CountValueCAlarm : UINT;
CallUpNumberCAlarm : UINT;
CAlarmFB : CAlarm;
Output AT %Q0.0.0.0.0 : BOOL;
Error AT %Q0.0.0.0.7 : BOOL;

END_VAR

(* CAlarm is permanently assigned to digital input I0.0.0.0.0

All rising edges at this input are detected
and counted. *)

CAL CAlarmFB (Handle := No_alarm_routine,

EnableDisable := EnableCAlarm,
Number := 0,
Predivide := 5,
SetpointValue := 1,
|
ErrorCAlarm := Error,
CountValueCAlarm := CountValue,
:= CallUpNumber )

LD EnableCAlarm
JMPCN CONTINUE
LD ErrorCAlarm
EQ 0
06/99 AWB 2700-1306 GB

JMPCN ERROR_CALARM
LD CAlarmFB.CallUpNumber
ST CallUpNumberCAlarm
JMP CONTINUE

243
 Function Blocks

ERROR_CALARM:

(* Error handling *)
LD 1
ST Error

CONTINUE: (* Another part of the user program *)

LD CallUpNumberCAlarm
GT 3
JMPC SET_1
LD 0
ST Output
JMP END

SET_1:

LD 1
ST Output
END:

END_PROGRAM

06/99 AWB 2700-1306 GB

244
 ColdstartRetention

PS 416 ColdstartRetention
Definition of a Marker Area with Cold Start
Retention

Prototype of the function block

Meaning of operands
Enable A rising edge enables the definition of the cold
start retentive marker area

SetpointStartMarker Starting byte address of marker area

SetpointLength Number of marker bytes

Error Error output

0 Last call without errors
1 Starting byte address too large or defined
marker area exceeds MB4345
2 Operating system version older than V1.09

ActualStartMarker Current starting byte address of cold start

retentive marker area; only relevant if
ActualLength > 0

ActualLength Current size of the cold start retentive marker

area (in bytes)

Description
The ColdstartRetention function block is used to
define a block of marker bytes within the PS 416-
CPU marker area (MB 0 – MB 4345) which is cold
06/99 AWB 2700-1306 GB

start retentive, i. e. the data is retained following a

cold start of the program rather than using the
initialisation values of the variables. This allows
several user programs to share the same data.

245
 Function Blocks

Please note the following constraints when defining

the cold start retentive marker area.
The OS40 operating system version must be
V 1.09 or later.
All markers which should also be retentive
following a warm start must be declared in the
program with the RETAIN keyword; according to
requirements this also applies to markers defined
with this function block as cold start retentive.
The ColdstartRetention function block must be
called in the first program cycle following a cold
start.
The ColdstartRetention function block does not carry
out management of the cold start retentive marker
area.
After loading the operating system, the length of the
cold start retentive marker area is zero until the
ColdstartRetention function block has been called
for the first time. In this case, all variables are
initialised with the values specified in the program or
with default values.
The cold start retentive marker area remains valid
until it is redefined by calling the function block
again, even if other user programs are started which
do not use the defined marker area.
The definition of the cold start retentive marker area
can be deleted by loading the OS40 operating
system into the PLC again or booting from a memory
card.
The current definition of the cold start retentive
06/99 AWB 2700-1306 GB

marker area can be checked by calling the function

block with the Enable input set to “0” or “FALSE”.

246
 ColdstartRetention

Example: cold start retention

Invocation in the program
PROGRAM Retention

VAR RETAIN

(* Declaration of warm start retentive markers *)

M10 AT%MB0.0.2.10 : USINT := 2;
M12 AT%MB0.0.2.12 : USINT := 2;
M14 AT%MB0.0.2.14 : USINT := 2;

(* Declaration of cold and warm start retentive markers *)

M20 AT%MB0.0.2.20 : USINT := 3;
M22 AT%MB0.0.2.22 : USINT := 3;
M24 AT%MB0.0.2.24 : USINT := 3;

END_VAR

VAR
SetValues AT%i0.0.0.0.0 : BOOL ;
RetentiveError AT%q0.0.0.0.0 : BOOL ;
Retentive : ColdstartRetention ;
FirstCycle : PS_Message ;

END_VAR

(* The cold start retentive marker area must be defined

in the first program cycle following a cold start.*)
CAL FirstCycle( MessageType := ICS )
LD FirstCycle.Result
JMPCN NORMAL_CYCLE

(* An existing cold start retentive marker area should not be changed

Accordingly a check is made for a previously defined marker area.*)
CAL Retentive( Enable := FALSE )
LD RetentiveError
EQ 0
LD Retentive.ActualLength
GT 0
JMPC NORMAL_CYCLE
06/99 AWB 2700-1306 GB

247
 Function Blocks

(* If the length of a previously defined cold start retentive marker

area is zero, define a range for cold start retentive markers
as follows.
Start of range : MB 20; Length of range : 6 bytes *)
CAL Retentive(Enable := TRUE,
SetpointStartMarker := 20,
SetpointLength := 6
|
:=Error,
:=ActualStartMarker,
:=ActualLength )

LD RetentiveError
EQ 0
JMPCN ERROR
JMP NORMAL_CYCLE

ERROR:
(* Execute error routines *)
LD 1
ST RetentiveError

NORMAL_CYCLE:
(* This part of the program only serves to illustrate
the different retention behaviour of the declared variables.
The following markers are retentive
with a user-program warm start *)
LD M10
LD M12
LD M14

(* The following markers are cold and warm start retentive

with a user program *)
LD M20
LD M22
LD M24
LD SetValues
JMPCN ENDE
LD 44
ST M10
ST M12
ST M14
06/99 AWB 2700-1306 GB

ST M20
ST M22
ST M24

ENDE:
END_PROGRAM

248
 COM

PS 416 COM
Function block for serial communication

Prototype of the function block

Description
The COM function block is used for serial com-
munication with the PS 416-COM-200 card.
Please refer to the manual “Hardware and
Engineering PS 416-COM-200 – Communication
Module” (AWB 27-1237-GB) for a description of this
function block and some application notes.
06/99 AWB 2700-1306 GB

249
 Function Blocks

CompareArray
Data Block Comparison or Value Search

Prototype of the function block

Meaning of operands
Mode Operating mode (0 = search, 1 = block
comparison)

Source Source area

Destination Destination area

SourceOffset Offset in source area

DestinationOffset Offset in destination area

ElementNumber Number of elements to be compared

Greater “Greater” indicator for comparison result

Equal “Equal” indicator for comparison result

Less “Less” indicator for comparison result

06/99 AWB 2700-1306 GB

Output Indicates where unequal data or the specified

search value is located

Error Error code

250
 CompareArray

Description
The CompareArray function block has two operating
modes: Value Search or Block Comparison.
The mode is set with the Mode input.
The source and the destination can be of any
required size. All types of type ANY_INT and
ANY_BIT are permissible as array element types
apart from BOOL.
Error codes at the Error output:
0 No errors
1 Number of elements (ElementNumber) is 0
2 Source offset is outside the source area.
3 Number of elements exceeds the source area.
4 Destination offset is outside the destination area
5 Number of elements exceeds the destination
area.
Value Search mode
The Value Search mode is used to search for a
specified value in an array.The value to search for is
contained in the array specified with Source and
SourceOffset.
The start of the array to be searched for is specified
with Destination and DestinationOffset.
The length of the data block to be searched is
specified with ElementNumber. The Equal output will
be set if the search criterion is found within the data
block defined by the destination address and
ElementNumber.
Output indicates the position of this value within the
array:
06/99 AWB 2700-1306 GB

Output = 0.. ElementNumber-1; Equal = 1

The outputs Greater and Less are 0 in this case.

251
 Function Blocks

If the search criterion is not found, Output is set to

the same value as ElementNumber and the Equal,
Greater and Less are set to 0.
Example: search for data
PROGRAM search
VAR
search_fb : CompareArray;
SourceAddress AT %MB0.0.0.23 : ARRAY [1..1] OF BYTE := [16#7D];
(* MarkerByte 23 initialised with search value *)
DestinationAddress AT %MB0.0.0.27 : ARRAY [1..1] OF BYTE;
Start AT %I0.0.0.0.0 : BOOL; (* Start search operation *)
Found : USINT;
Result_greater : BOOL;
Result_equal : BOOL;
Result_less : BOOL;
END_VAR

LD Start
CALC search_fb (Mode := 0, (* Data search mode *)
Source := SourceAddress,
Destination := DestinationAddress,
ElementNumber := 6) (* Search range of 6 bytes *)

LD search_fb.Output
ST Found (* Location of the search value *)
(* "Destination" plus "Output" *)
LD search_fb.Greater
ST Result_greater
LD search_fb.Equal
ST Result_equal
LD search_fb.Less
ST Result_less

END_PROGRAM

Block Comparison mode

The Block Comparison mode is used to compare two
data blocks which can be parts of arrays or entire
arrays.
06/99 AWB 2700-1306 GB

The start of the two data blocks is specified with

Source and SourceOffset and/or Destination and
DestinationOffset respectively. The size of the data
blocks is specified with ElementNumber.

252
 CompareArray

If both data blocks are found to be identical, Output

will be set to the same value as ElementNumber and
the Equal output will be set to 1.
If the data blocks are not the same, Output will
indicate the location in the array where there is a
difference. The Equal output will be set to 0 and the
Greater or Less outputs will be set according to the
result of comparison at the location where the
discrepancy was found.
Example: comparing data
PROGRAM compare
VAR
compare_fb : CompareArray;
SourceAddress AT %MB0.0.0.23 : ARRAY [1..7] OF BYTE := [16#7D];
DestinationAddress AT %MB0.0.0.30 : ARRAY [1..7] OF BYTE := [16#7D];
Start AT %I0.0.0.0.0 : BOOL; (* Start compare operation *)
Deviation : USINT;
Result_greater : BOOL;
Result_equal : BOOL;
Result_less : BOOL;
END_VAR

LD Start
CALC compare_fb(Mode := 1, (* Block comparison *)
Source := SourceAddress,
Destination := DestinationAddress,
ElementNumber := 4) (* Comparison range: 4 bytes *)

LD compare_fb.Output
ST Deviation (* Location where blocks *)
(* differ: "Destination" plus "Output" *)
LD compare_fb.Greater
ST Result_greater
LD compare_fb.Equal
ST Result_equal
LD compare_fb.Less
ST Result_less
END_PROGRAM
06/99 AWB 2700-1306 GB

253
 Function Blocks

COMtoSTR
Convert Received Characters to String

Prototype of the function block

Meaning of operands
ReceiveVariable Start address of the marker range where the data to
be converted is located

TextString String to contain the converted data from the array

StrLen Number of characters to be converted

Enable Enable the conversion

Description
The function block is used to convert text data
received via an interface and stored in an array to a
variable of data type ANY_STRING.
A static “1” or TRUE at the Enable input starts the
conversion. The input parameter “StrLen” defines
the number of characters to be converted and thus
the length of the resulting string.
If the declared length of TextString is insufficient to
hold all the converted data, characters are only
copied into it until it is full. The data is copied to the
string 1:1 without ASCII conversion.
06/99 AWB 2700-1306 GB

254
 COMtoSTR

Example: converting received characters

into a string
PROGRAM Str_Gen

VAR
EnableReceive AT%I0.0.0.0.0 : BOOL;
Array_to_String : COMtoSTR;
ReceiveText : STRING(20):
ReceiveArray : ARRAY[1..20] of byte;
ReceiveLength : UINT;
ReceiveFromSerial : COM ;
END_VAR

(* Receive data from serial interface *)

LD EnableReceive
ANDN ReceiveFromSerial.ReceiveActive
ST ReceiveFromSerial.ReceiveStrobe
CAL ReceiveFromSerial(Mode := 1;
ReceiveStrobe := ;
SlotNumber := 6; (* COM200 on slot 6 *)
ReceiveNumber := 20 ;
ReceiveVariable := ReceiveArray;
|
ReceiveActive := ;
ReceivedBytes := ;
ReceiveError := ;
InterfaceStatus := ;
SlotError := )

(* Copy string to array *)

LD EnableReceive
ANDN ReceiveFromSerial.ReceiveActive
ST Array_to_String.Enable
CAL Array_to_String (Enable := ;
StrLen := ReceiveFromSerial.ReceivedBytes;
TextString := ReceiveText,
ReceiveVariable := ReceiveArray)

END_PROGRAM
06/99 AWB 2700-1306 GB

255
 Function Blocks

PS 4-200 1) CounterAlarm
PS 4-300 Counter Alarm Function Block
PS 416

Prototype of the function block

Meaning of operands
EnableDisable Enabling and disabling of alarm execution
Start condition positive edge (0 = Disable,
1 = Enable)

Number Alarm channel number

for PS 4-141/-151/-201/-341 = 0)

Predivide Predivider for the counter

SetpointValue Setpoint entry for the counter

SubRoutine Instance name of the function block called by the

alarm

Error Error code

CountValue Counter pulse actual value

CallUpNumber Number of alarm-controlled function block calls

Description
The CounterAlarm function block is assigned in the
PS 4-341-MM1, PS 4-201-MM1 PS 4-141-MM1 and
06/99 AWB 2700-1306 GB

PS 4-151-MM1 basic units to hardware input

%I0.0.0.0.0.0.
1) Not for PS 4-271

256
 CounterAlarm

The input EnableDisable controls the start of the

counter. The counter is started if there is a positive
edge at this input. It is stopped and reset if the input
status changes from “1” or TRUE to “0” or FALSE.
The current number of count pulses of the hardware
counter are indicated at the “CountValue” output.
The input “Predivide” (value range: 1 – 65535) is
used to define the number of signals required at the
hardware input to increment the counter. The
“SetPointValue” (value range: 1 – 65535) input
defines the number of counted signals required to
activate the alarm or call the function block.
The maximum permissible system capacity depends
on the following three factors: “Predivide”,
“SetPointValue” and the frequency set. These
factors must be selected so that no more than two
interrupts occur per millisecond.
Irrespective of the PLC load (Suconet / PC
communication), the setting “Predivide” > 1 setting
ensures a counter frequency of 3 kHz with PS 4-200
and 50 kHz with PS 4-300
The Error output indicates the following error code:
0 No errors
1 SetpointValue is “0”
2 Predivide is “0”
Error code with PS 4-300 only
3 Invalid alarm channel number
4 Alarm channel number already used
5 Counter channel not set as Up/Down counter
The “CallUpNumber” output (value range: 1 – 65535)
06/99 AWB 2700-1306 GB

indicates how often the value defined at the

SetpointValue input has been reached.

257
 Function Blocks

The SubRoutine input allows event-controlled

programming to be implemented. This is done by
stating the instance name of the function block to be
activated when the event is reached. If no instance is
specified, the CountValue will continue to be
incremented without triggering the alarm.
The function block called by the alarm function block
must not have any VAR_IN_OUT parameters. This
kind of instance must only have local variables (VAR)
or global variables that have been declared externally
as VAR_EXTERNAL variables.

06/99 AWB 2700-1306 GB

258
 CounterAlarm

The following points must be observed for the event-

driven program:
After the event has occurred, the user program is
interrupted, the register status is saved and the
subprogram specified by Subroutine is executed.
The alarm function block cannot be interrupted by
other alarm function blocks (all alarm function blocks
have the same priority). The maximum execution
time of alarm function blocks is to be restricted to
5 ms (approx. 1K IL instructions) in the user program
since the alarm function blocks cannot be inter-
rupted even by the operating system in the event of
a voltage drop. If the execution time is exceeded, an
EDC error may occur when switching off the power
supply.
The execution time of the alarm function block is
added to the execution time of the cyclical user
program and also monitored by the cycle time
monitoring function.
Since event-driven program processing is allowed
access to the entire image register, access to data
that is used by the event-controlled and cyclical user
program must be disabled. Bit accesses may only
occur on the same byte in the cyclical user program
and in the Alarm function block if the access is
synchronized with Disable_Interrupt and
Enable_Interrupt.
Due to its fast reactions an Alarm function block
requires a high-speed peripheral access (direct
output). The QB, QPB peripheral operands available
in the basic unit should therefore be used.
06/99 AWB 2700-1306 GB

An alarm function block can be used several times

(multiple instantiation) although this should normally
be avoided since each function block group has the
same event source and only the last function block

259
 Function Blocks

instance in the program is valid. Multiple instantiation

is only useful if the parameters of the function block
are set again within an interrupt routine and an edge
disable is to be implemented.
By multiple instantiation is meant the reservation of
several data ranges for each parameter set of a
particular function block type.

The input parameters of an alarm function block

should only be assigned between the
parentheses when it is called. An explicit
parameter assignment outside of the
parentheses before or after the invocation is not
possible.

Example: counter alarm function block

The pulses of a rotary encoder are to be counted.
The time between the pulses is less than the cycle
time of the PLC. The encoder supplies 1000 pulses
per degree of rotation. The scaling ratio should be set
to 100 on the function block so that the position of
rotation is provided at the CNT output in 1/10 degree
of rotation.
PROGRAM calarm
VAR
CountAlarm : CounterAlarm;
Error : USINT;
CountValue : UINT;
END_VAR

CAL CountAlarm (EnableDisable := 1,

Number := 0,
Predivide := 100,
SetpointValue := 1)

LD CountAlarm.Error
ST Error
06/99 AWB 2700-1306 GB

LD CountAlarm.CountValue
ST CountValue
(*This shows the current counter value *)

END_PROGRAM

260
 CounterLE

PS 4-200 CounterLE
PS 4-300 Control of the Counter LE Module

Counter-LE

USINT LENumber Error USINT

BOOL ChannelNumber ReferenceOutput BOOL
BOOL >ReferenceInput OutputLow UINT
OutputHigh UINT
Output UDINT
*

Prototype of the function block (* PS 4-300 only)

Meaning of operands
LENumber Module address of LE
(can only be 1 or 2)

ChannelNumber Channel number (0 = Channel 1; 1 = Channel 2)

ReferenceInput Edge-controlled 0 -> 1: Set reference flip flop

(Mode 1 + 2) or set counter actual value to 0
(Mode 3)

Error Error messages

ReferenceOutput 0 = 0 = Reference flip flop reset (Modes 1 + 2)

1 = 1 = Reference flipflop set (Modes 1 + 2)
Direction indication (Mode 3); this shows the
status of the LE input “Y”

OutputLOW Current counter value (lower word)

OutputHigh Current counter value (higher word)

Output Current counter value (only for PS 4-300)

06/99 AWB 2700-1306 GB

261
 Function Blocks

Description
The CounterLE function block controls the
LE 4-622-CX1. The following functions can be
executed:

A function block instance is assigned to every

channel of the LE. The function block instances are
not retentive, i. e. the counter actual values are lost in
the event of a voltage drop.
The “LENumber” and “ChannelNumber” inputs are
used to define the counter channel whose current
counter value can be called using the “OutputLOW”
and “OutputHigh” parameters below:

Structure of the 24-bit counter value

06/99 AWB 2700-1306 GB

The counter status is refreshed every time the

CounterLE function block is processed.
For further details on the operation and special
features of the LE 4-622-CX1, please refer to the
manual AWB 27-1263-GB.

262
 CPUDataExchange

PS 416 CPUDataExchange
Exchange Data Between PLCs

Prototype of the function block

Meaning of operands
SlotNumber Slot number of the CPU which exchanges data

Direction Direction of data transfer

CD_READ: from the master CPU to a slave CPU
CD_WRITE: from a slave CPU to the master CPU

SourceOffset Offset of memory location, first byte to read

DestinationOffset Offset of memory location, first byte to write

Length Number of bytes to read or write

DataBuffer Array variable for exchanging data with the CPU

Errorcode Error code

Description
If several CPUs of types PS 416-CPU-200/300/400
are installed in the same rack, the
CPUDataExchange function block can be used to
exchange data between them. The same function
block is used for both master and slave CPUs.
06/99 AWB 2700-1306 GB

The PS 416 system must be configured as follows:

Slot 2: MASTER_CPU; PS 416 CPU
Slot 4/6/8/...: SLAVE_CPUs; PS 416 CPU

263
 Function Blocks

Data exchange takes place using a special memory

chip of size 2032 bytes. This memory area is read or
written to with a function block call.
Please refer to the manual “Sucosoft S 40,
User Interface (AWB 27-1305-GB) for information on
configuring the PS 416 system and programming the
CPUs.
SlotNumber specifies the slot number of the CPU
which receives the data or from which the data is
read. Permissible values are 2, 4, 6,...
The Direction input specifies the direction of data
transfer:
CD_READ: data transfer from the master CPU to
a slave CPU
CD_WRITE: data transfer from a slave CPU to the
master CPU
SourceOffset specifies the offset of the memory
location from which the first byte is read.
For CD_READ, SourceOffset specifies a memory
location in the special memory area of the PS 416-
CPU. For CD_WRITE, SourceOffset specifies a
memory location in the array DataBuffer from which
the first byte to be written is read. Permissible values
for SourceOffset are 0 - 2031.
For CD_READ, DestinationOffset specifies a memory
location in the array DataBuffer into which the first
byte read from the special memory area is written.
For CD_WRITE, DestinationOffset specifies a
memory location in the special memory area into
which the first byte from the array DataBuffer is
06/99 AWB 2700-1306 GB

written. Permissible values for DestinationOffset

are 0 – 2031.

264
 CPUDataExchange

Length specifies the number of bytes to read or write.

Permissible values are 1 – 2032.
The Array variable DataBuffer contains the data to
be transferred. The contents are dependent on the
direction of transfer: For CD_READ, after the function
block has executed DataBuffer contains the data
read from the special memory area. For CD_WRITE,
DataBuffer must contain the data to be transferred to
the special memory area before the function block is
called.
ErrorCode provides feedback on the processing
state following execution of the command.
0 No error occurred during execution of the
command.
1 SlotNumber specifies an invalid slot number.
Permissible values are 2, 4, 6, 8 etc.
2 SourceOffset is larger than the maximum value of
2031.
3 DestinationOffset is larger than the maximum
value of 2031.
4 Length is larger than 2032, or Length +
SourceOffset or DestinationOffset exceeds the
size of the special memory area (2032 bytes) of
the size of the array DataBuffer.
5 DataBuffer is not or incorrectly specified.
6 The Direction input has been configured with an
illegal value.
06/99 AWB 2700-1306 GB

265
 Function Blocks

Example: data exchange between PLCs

PROGRAM cde

VAR
DataExchange : CPUDataExchange ;
EnableRead AT%i0.0.0.0.0 : Bool ;
ReadData : Array[1..20] of Byte;
ReadError : Uint ;
END_VAR

LD EnableRead
CALC DataExchange (SlotNumber := 4,
Direction := CD_READ,
SourceOffset := 0,
DestinationOffset := 0,
Length := 20,
DataBuffer := ReadData
|
ReadError := Errorcode )

END_PROGRAM

06/99 AWB 2700-1306 GB

266
 CTD

CTD
Down Counter

Prototype of the function block

Meaning of operands
CD Counter pulses, rising edge

Load Set condition

PV Initial value

Q Message: counter status ≤ 0

CV Counter status

Description
The function block CTD is used for the down
counting of impulses provided at the input operand
“CD”. The counter is set to “0” when initialised.
The value defined by the operand “PV” is loaded into
the counter as the initial value if the value of the
operand “Load” is “1”.
Each rising edge on the input “CD” is decremented,
i. e. reduced by one.
The output operand “CV” outputs the current
counter value. If the counter value is above the value
“0”, the output operand “Q” has the Boolean value
06/99 AWB 2700-1306 GB

“0”. The output “Q” is set to “1” when reaching or

dropping below the counter value “0”.

267
 Function Blocks

CTU
Up Counter

Prototype of the function block

Meaning of operands
CU Counter pulses, rising edge

ReSet Reset condition

PV Counter limit

Q Signal: counter status PV

CV Counter status

Description
The function block CTU is used for the up counting
of impulses provided by the input operand “CU”.
The counter is set to “0” when initialised. Each rising
edge on input “CU” increments the counter, i. e.
increases its value by one.
The counter value can be cleared with the value “1”
at the operand “ReSet”.
The output operand “CV” outputs the current
counter value. If the counter value is below the limit
value “PV”, the output operand “Q” has the Boolean
value “0”. The output “Q” is set to “1” when reaching
06/99 AWB 2700-1306 GB

or exceeding the limit value.

268
 CTUD

CTUD
Up And Down Counter

Prototype of the function block

Meaning of operands
CU Counter pulses for up counting, rising edge

CD Counter pulses for down counting, rising edge

ReSet Reset condition

Load Load condition

PV Load value

QU Message: counter status greater than or equal to

PV

QD Message: counter status less than or equal to 0

CV Counter status

Description
The function block CTUD is used for the counting up
and down of impulses. The counter is set to “0” when
06/99 AWB 2700-1306 GB

initialised. Each rising edge on input “CU” incre-

ments the counter, i. e. increases its value by one.
A rising edge on input “CD” decrements the counter,
i. e. reduces its value by one.

269
 Function Blocks

The value defined by the operand “PV” is loaded into

the counter if the value of the operand “Load” is “1”.
The counter value can be deleted with the value “1”
of the operand “ReSet”. While the static status “1” of
the operands “ReSet” is kept, the fulfilled counter or
load conditions have no effect on the counter value.
The output operand “CV” provides the current
counter value. If the counter value is below the load
value “PV”, the output operand “QU” has the
Boolean value “0”. The output “QU” is set to “1”
when reaching or exceeding the load value. If the
counter value is over the value “0”, the output
operand “QD” has the Boolean value “0”. The output
“QD” is set to “1” when reaching or dropping below
the counter value “0”.
Example: upward and downward counting
PROGRAM visitors

VAR
PersonCounter : CTUD;
Lightbarrier1 AT %I0.0.0.0.2 : BOOL;
Lightbarrier2 AT %I0.0.0.0.3 : BOOL;
Reset AT %I0.0.0.0.1 : BOOL;
PersonNumber AT %QW0.0.0.0 : INT;
END_VAR

CAL PersonCounter(CU := Lightbarrier1,

CD := Lightbarrier2,
ReSet:= Reset)
LD PersonCounter.CV
ST PersonNumber

END_PROGRAM
06/99 AWB 2700-1306 GB

270
 DataScale

DataScale
Scaling of data

DataScale

BOOL Set OutputValue INT

INT InputValue Status USINT
INT InputRangeBegin Error USINT
INT InputRangeEnd
INT OutputRangeBegin
INT OutputRangeEnd
INT OutputLimitLow
INT OutputLimitHigh

Prototype of the function block

Meaning of operands
Set Activates the function block

InputValue Input value (IV) which can vary within the input
range; IRB IV ≤ IRE

InputRangeBegin Bottom of input range (IRB)

IRB < IRE

InputRangeEnd Top of input range (IRE)

OutputRangeBegin Bottom of output range (ORB)

ORB < ORE

OutputRangeEnd Top of output range (ORE)

OutputLimitLow Lower limit (OLL)

OLL < OLH ≤ ORE and OLL ≥ ORB

OutputLimitHigh Upper limit (OLH)

OLH > OLL ≥ ORB and OLH ≤ ORE

OutputValue Output value

06/99 AWB 2700-1306 GB

Status Messages (range overshoots)

Error Error messages (parameters)

271
 Function Blocks

Description
The input range within which the value to be proc-
essed (IV) can vary is defined with the values IRE
(greatest input value) and IRB (smallest input value).
You can assign any output range you wish (ORE and
ORB) to this input range. The input value is converted
using the ratio of input range to output range. 2 limit
values (OLL and OLH) must be defined within this
output range.
If the converted value exceeds or undershoots a
limit, a message is output.

When the Set input has status 1, the range values

set by the user are checked. Incorrect values are
signalled at the Error output byte. The value at the
InputValue input is converted and sent to the
OutputValue output.
If the limit is undershot or overshot, the OutputValue
output is set to the relevant limit and the error bits set
at the Status output.
When there is no error, conversion continues for as
06/99 AWB 2700-1306 GB

long the Set input has status 1.

272
 DataScale

Changes to the value range are accepted once the

Set input has been set to 0 then back to 1 again.
When the Set input has status 0, output OutputValue
= ORB, output Error = 0 and output Status = 0.
Error Error messages (parameters)
(Value)
0 no error
1 IRB ≥ IRE
2 ORB ≥ ORE
3 OLL > OLH, OLL < ORB, OLL > ORE,
OLH < ORB, OLH > ORE
Status Messages (range overshoots)
(Value)
0 no error
1 OV < OLL
2 OV > OLH
3 IV < IRB
4 IV > IRE
Removal of the error causes the byte to be reset to 0.
06/99 AWB 2700-1306 GB

273
 Function Blocks

Example “Scaling”
PROGRAM analog_processing

VAR
Converter: DataScale;
Start AT %I0.0.0.0.0: BOOL;
Analog_Input AT %IAW0.0.0.4: INT;
Analog_Output: INT;
Continuation: INT;
Range_Error: USINT;
Parameter_Error: USINT;
END_VAR

CAL Converter(Set := Start,

InputValue := Analog_Input,
InputRangeBegin := 200,
InputRangeEnd := 400,
OutputRangeBegin := 200,
OutputRangeEnd := 4000,
OutputLimitLow := 250,
OutputLimitHigh := 3800
|
Analog_Output, := OutputValue,
Range_Error := Status,
Parameter_Error := Error)
LD Analog_Output
ST Continuation

END_PROGRAM

06/99 AWB 2700-1306 GB

274
 DATconcat

DATconcat
Concatenate Date and Time

Prototype of function block

Meaning of operands
MilliSecond Milliseconds part of date and time

Second Seconds part of date and time

Minute Minutes part of date and time

Hour Hours part of date and time

Day Day part of date and time

Month Month part of date and time

Year Year part of date and time

OutputDAT Resulting value for date and time

Error Error message

06/99 AWB 2700-1306 GB

275
 Function Blocks

Description
The values specified as input operands of data type
UINT are combined to a value for date and time in the
output operand “OutputDAT”.
The function block converts the individual values of
the input operands to the appropriate sections for
date and time. The input operands must not exceed
the value ranges specified for a date and a time.
The year number must be between 1993 – 2092. If
the specified value ranges are exceeded, the status
“1” will show at the Error output.
Example: Concatenating date and time
PROGRAM dtgen

VAR
DateTimeConcatenation : DATconcat;
MilliSec : UINT := 0;
Sec : UINT := 30;
Min : UINT := 10;
Hr : UINT := 3;
Dy : UINT := 12;
Mnth : UINT := 12;
Yr : UINT := 1997;
Err : BOOL;
Date_1 : DATE_AND_TIME;
END_VAR

CAL DateTimeConcatenation(MilliSecond := MilliSec,

Second := Sec,
Minute := Min,
Hour := Hr,
Day := Dy,
Month := Mnth,
Year := Yr
|
Date_1 := OutputDAT,
Error := Err)

END_PROGRAM
06/99 AWB 2700-1306 GB

276
 DateConcat

DateConcat
Concatenate Date

Prototype of function block

Meaning of operands
Day Day part of a date

Month Month part of a date

Year Year part of a date

OutputDate Value resulting from the defined date sections

Error Error message

Description
The values entered as input operands of data type
UINT are combined to a date value in the output
operand “OutputDate”. The input operands must be
outside of the permissible value range for dates.
The year value must be between 1993 – 2092.
The Error output will be set to “1” if an impermissible
value is entered.
06/99 AWB 2700-1306 GB

277
 Function Blocks

Example: concatenate date

PROGRAM dategen

VAR
Dateconcaten : DateConcat;
Date1 : Date;
Dy : UINT := 24;
Mnth : UINT := 12;
Yr : UINT := 1996;
Err : BOOL;
END_VAR

CAL Dateconcaten(Day := Dy,

Month := Mnth,
Year := Yr
|
Date1 := OutputDate,
Error := Err)

END_PROGRAM

06/99 AWB 2700-1306 GB

278
 DateSplit

DateSplit
Split DATE Data Type

Prototype of function block

Meaning of operands
InputDate Date

Day Day part of date

Month Month part of date

Year Year part of date

Error Error message

Description
The date value specified via the input operand
“InputDate” is divided into elements that are each
output as UINT data types.
The year value must be between 1993 – 2092.
The output operand Error will be set to “1” if an
impermissible year value is entered.
06/99 AWB 2700-1306 GB

279
 Function Blocks

Example: splitting date value

PROGRAM datetln

VAR
DateElements : DateSplit;
Date1 : Date := D#1999-12-24;
Dy : UINT;
Mnth : UINT;
Yr : UINT;
Err : BOOL;
END_VAR

CAL DateElements(InputDate := Date1

|
Dy := Day,
Mnth := Month,
Yr := Year,
Err := Error)

END_PROGRAM

06/99 AWB 2700-1306 GB

280
 DATsplit

DATsplit
Split DATE_AND_TIME Data Type

Prototype of function block

Meaning of operands
InputDAT Date and time

MilliSecond Milliseconds part of date and time

Second Seconds part of date and time

Minute Minutes part of date and time

Hour Hours part of date and time

Day Day part of date and time

Month Month part of date and time

Year Year part of date and time

Error Error message

06/99 AWB 2700-1306 GB

281
 Function Blocks

Description
The date and time value specified via input operand
“InputDAT” is divided into elements that are each
output as UINT data types.
The year number must be between 1993 – 2092.
The output operand Error will be set to “1” if an
impermissible year value is entered.
Example: Splitting date and time values
PROGRAM dtsplit

VAR
DT_Elements : DATsplit;
Date_1 : DT := DT#1999-11-20-22:13:12;
Millisec : UINT;
Sec : UINT;
Min : UINT;
Hr : UINT;
Dy : UINT;
Mnth : UINT;
Yr : UINT;
Err : BOOL;
END_VAR

CAL DT_Elements(InputDAT := Date_1

|
Millisec := MilliSecond,
Sec := Second,
Min := Minute,
Hr := Hour,
Dy := Day,
Mnth := Month,
Yr := Year,
Err := Error)

END_PROGRAM
06/99 AWB 2700-1306 GB

282
 DE4netDP

PS 4-300 DE4netDP
PS 416 PROFIBUS-DP connection for frequency
inverters of series DF 4-120 and DF 4-34x

DE4netDP

BOOL Enable SendData ARRAY [0..11] of BYTE

BOOL Start StatusWord WORD
BOOL Quickstop ActualFrequency INT
BOOL DCBrake EchoCommand BYTE
BOOL TripReset EchoParameternumber UINT
BOOL ParameterSet EchoSubindex USINT
INT ReferenceFrequency Busy BOOL
BYTE Command ReceiveValue UINT
UINT Parameternumber ReceiveValueOffset UINT
USINT Subindex ErrorCode WORD
UINT TransmitValue
UINT TransmitValueOffset
ARRAY [0..11] of BYTE ReadData

Prototype of function block

Meaning of operands
Enable “1” signal activates frequency inverter. “0” signal
disables any further control commands. With drive
running, change of signal from “1” to “0” causes
motor to coast.
Start A “1” state enables the motor drive, the output
frequency is integrated to the specified setpoint
according to the defined acceleration ramp. A
change from “1” to “0” stops the motor with the
defined deceleration ramp.
Quickstop At “1” state, motor brakes to standstill using the
quick-stop ramp. The ramp time is adjustable with
the parameter 105 (PNU 105) (only DF 4-34x).
06/99 AWB 2700-1306 GB

283
 Function Blocks

DCBrake “1” state activates DC injection braking. Brakes

motor to standstill.
The DC injection braking remains active as long as
the signal state is “1”.
TripReset With change of signal from “0” to “1”, the current
error is reset.
ParameterSet “0” activates parameter set 1.
“1” activates parameter set 2.
Reference Frequency setpoint for motor speed. The actual
Frequency output frequency is limited by fmax. Positive values
mean clockwise phase sequence, negative values
mean anticlockwise phase sequence. A 500 means
50.0 Hz output frequency, i. e. the required value has
to be multiplied “10”.
Command Execute command: 0 - no execute
1 - Read parameter
2 - Write parameter
Parameternumber Parameter number to be read/written. All available
parameter numbers that can be transferred are to be
found in the manual for the motor controller.
Subindex Subindex of parameter numbers to be read/written.
All available parameter numbers with subindex that
can be transferred are to be found in the manual for
the motor controller (always zero for DF 4).
TransmitValue Parameter value to transfer.
The last two places of the value entered are always
interpreted as decimal places. E. g. 223.10 = 22310
or 1 = 100.
I. e. the required value has to be multiplied by “100”.
The valid value range (depending on parameter
number) is to be found in the manual for the drive
controller.
06/99 AWB 2700-1306 GB

284
 DE4netDP

TransmitValueOffset An offset can be entered here for parameter values

greater than 655.35 (65535), which the function
block adds to “TransmitValue”. The last two places of
the value entered are similarly interpreted as decimal
places.
ReadData First byte in receive register (%IBx.y.0.0) which is
written by the function block. The entire input data
range must be declared in the variable editor as an
“array”.
SendData First byte in receive register (%QBx.y.0.0) which is
read by the function block. The entire output data
range must be declared in the variable editor as an
“array”.
StatusWord The status word contains the current state of the
motor controller in bit code. A detailed description of
the status word is to be found in the manual for the
DE 4-NET-DP module (AWB 823-1290 D).
ActualFrequency This displays the current output frequency of the
DF 4 in Hz. Positive values mean clockwise phase
sequence, negative values mean anticlockwise
phase sequence. A 500 means an output frequency
of 50.0 Hz.
EchoCommand Execute command: 0 = No command
1 = Read parameter
2 = Write parameter
EchoParameternumber Parameter number that was read/written.
EchoSubindex Subindex that was read/written.
(always zero for DF 4)
Busy “1” state indicates that a command is presently
being executed. When this is completed, the signal
status changes to “0”.
06/99 AWB 2700-1306 GB

285
 Function Blocks

ReceiveValue Received parameter value. The last two places of the

displayed value must be interpreted as decimal
places.
E.g. 22310 = 223.10 or 100 = 1.
When ReceiveValue is 65535 => don’t forget
ReceiveValueOffset!
ReceiveValueOffset If the value range of ReceiveValue has been
exceeded (> 65535), an offset is entered here, which
the user must add to the value in ReceiveValue. The
last two places of the displayed value must similarly
be interpreted as decimal places.
ErrorCode Error messages during parameter transfer:
0000hex No error
6300hex No access right
6510hex Impermissible command parameter
6511hex Invalid subindex
6712hex Data length too large
6700hex Object does not exist
6800hex Data types do not agree
8021hex Cannot be executed due to local
control
8022hex Cannot be executed due to operating
state of device
8030hex Outside value range
8040hex Collision with other values
8020hex Command cannot be executed at
present
00FEhex Time out (reaction time of a
command > 5 s) 06/99 AWB 2700-1306 GB

286
 DE4netDP

Description
The “DE4netDP” function block is used to transfer
process and parameter data. The identifier of the
user data length in the PROFIBUS configurator must
be “B7hex 71hex”. This means, 8 bytes are trans-
mitted via the DP parameter channel plus 2 words of
process data.
The mode of the frequency inverter must first be set
to 3 “Fieldbus mode”. This can be done with the
keyboard, operating software or even via the field
bus.
As soon as communication is established between
PLC and the DF 4, the process data is transferred
automatically and continuously with no explicit
programming required. If other parameters of the
DF 4 are to be changed via PROFIBUS-DP, this is
done via the parameter channel.
Process input data:
Enable, Start, Quickstop, DCBrake, TripReset,
ParameterSet, ReferenceFrequency:
Process output data:
StatusWord, ActualFrequency

To achieve the shortest possible reaction times,

you should call this function block once only in
each user program cycle in order to update the
inputs and outputs.

All further parameters of the frequency inverter must

be read or written via the parameter data channel.
Read parameter:
왘 Specify parameter number in
06/99 AWB 2700-1306 GB

“Parameternumber“
왘 Specify subindex “Subindex“ (always equals zero
for the DF 4)

287
 Function Blocks

왘 Specify “Command = 1”. “Busy” changes from

“0” to “1” automatically
왘 Wait until Busy goes from “1” to “0”:
If ErrorCode is 0:
Accept “ReceiveValue” and possibly
“ReceiveValueOffset”
If “ErrorCode” is not “0”:
command was not executed,
check “ErrorCode”
왘 Specify “Command = 0”. Next command can be
started
Write parameter:
왘 Specify parameter number in
“Parameternumber”
왘 Specify subindex “Subindex“ (always equals zero
for the DF 4)
왘 Specify parameter value in “TransmitValue” and
possible “TransmitValueOffset”
왘 Specify Command = 2. “Busy” changes from “0”
to “1” automatically
왘 Wait until “Busy” has changed from “1” to “0”:
If “ErrorCode” is 0:
command was correctly executed,
If “ErrorCode” is not 0:
command was not executed,
check “ErrorCode”
왘 Specify “Command = 0”. Next command can be
started
06/99 AWB 2700-1306 GB

288
 DE4netDP

Response when bus interrupted (PNU 4000)
This parameter is only available for communi-
cation via PROFIBUS and is therefore not
described in the manual for the frequency
converter.
This parameter, and thus the response, is not
stored voltage failure safe in the DF 4 frequency
inverter but in the optional DE 4-NET-DP module.

PNU 4000 defines the response of the frequency

inverter if the PROFIBUS-DP connection is
interrupted.
PNU 4000 = 0:
no action, the motor retains the current state
(factory setting)
PNU 4000 = 1:
“Controller disable”, the motor coasts
PNU 4000 = 2:
“Quickstop”, the motor brakes to a standstill
using the quickstop ramp. The controller is then in
the disabled state.
06/99 AWB 2700-1306 GB

289
 Function Blocks

Example
The following example shows the declaration in the
variable editor:
VAR
Drive_1 : DE4netDP;
IN_PDP_S1T3at%IB1.3.0.0 : Array [0..11] of BYTE;
OUT_PDP_S1T3at%QB1.3.0.0 : Array [0..11] of BYTE;
END_VAR

The following example shows the “DE4netDP”

function block in the POU editor:
CAL Drive_1(
Enable := ,
Start := ,
Quickstop := ,
DCBrake := ,
TripReset := ,
ParameterSet := ,
ReferenceFrequency := ,
Command := ,
Parameternumber := ,
Subindex := ,
TransmitValue := ,
TransmitValueOffset := ,
ReadData := IN_PDP_S1T3,
|
OUT_PDP_S1T3 :=SendData
:=StatusWord,
:=ActualFrequency,
:=EchoCommand,
:=EchoParameternumber,
:=EchoSubindex
:=Busy,
:=ReceiveValue,
:=ReceiveValueOffset,
:=ErrorCode
06/99 AWB 2700-1306 GB

290
 DE4netK

DE4netK
Frequency inverter DF 4

Prototype of function block

Meaning of operands
SendData Operator list for the send register

ReadData Operator list for the receive register

06/99 AWB 2700-1306 GB

Enable 1: Enable frequency inverter

0: Disable frequency inverter

291
 Function Blocks

Start 1: Accelerate motor to frequency setpoint,

0: Brake motor using braking ramp

Quickstop 1: Brake motor to standstill using

quick-stop ramp

DCBrake 1: Activate DC injection braking

TripReset Signal transition 0 to 1: Reset last error

ParameterSet 0: Activate parameter set 1

1: Activate parameter set 2

MotorPotUp 1: Activate function “Motor potentiometer UP”

MotorPotDown 1: Activate function “Motor potentiometer

DOWN”

FixedFrequency1 1: Activate jog frequency 1 if

“FixedFrequency2” and
“FixedFrequency3” = 0

FixedFrequency2 1: Activate jog frequency 2 if

“FixedFrequency3” = 0

FixedFrequency3 1: Activate jog frequency 3

Reversal Reverse motor

FreezeRamp 0: Enable acceleration ramp

1: Freeze acceleration ramp

ReferenceFrequency Frequency setpoint for motor speed

Command Execute command (0: No command,

1: Read parameter, 2: Write parameter)

Parameternumber Parameter number to transfer

TransmitValue Parameter value to transfer

TransmitValueOffset Offset for parameter values above 655.35

StatusWord Drive controller status information

06/99 AWB 2700-1306 GB

ActualFrequency Display current output frequency

EchoCommand Command executed (0: No command,

1: Read parameter, 2: Write parameter)

292
 DE4netK

EchoParameter- Parameter number of command executed

number

Busy 1: Command being processed

ReceiveValue Received parameter value

ReceiveValueOffset Offset for parameter values above 655.35

ErrorCode Error messages

Description
The DE4netK function block forms the interface
between a PLC program and the DE 4-NET-K
Fieldbus module.
As soon as communication is established between
the PLC and the DF 4, process data is exchanged
automatically and continuously without requiring
explicit programming. Other DF 4 parameters are
changed via Suconet using the parameter channel.

To minimise reaction times, call the function

block just once per program cycle in order to
update the inputs and outputs.

The following inputs and outputs are read and / or

written by the function block each time it is called
(process data):
Inputs: Enable, Start, Quickstop, DCBrake,
TripReset, ParameterSet, MotorPotUp,
MotorPotDown, FixedFrequency1,
FixedFrequency2, FixedFrequency3, Reversal,
FreezeRamp, ReferenceFrequency.
Outputs: StatusWord, ActualFrequency
All other DF 4 parameters are read and / or written
06/99 AWB 2700-1306 GB

using the parameter channel.

293
 Function Blocks

The operators SendData and ReadData must be

assigned to the first send data and / or receive data
byte, respectively. The following 11 bytes are then
automatically declared by the array (see example).
The motor drive is enabled by a 1 at the Start input.
The output frequency of the drive is accelerated to
the specified frequency setpoint using the confi-
gured acceleration ramp. A transition from 1 to 0 at
the Start input stops the motor with the configured
deceleration ramp.
ReferenceFrequency specifies the frequency set-
point, i. e. the required motor speed. Positive values
correspond to clockwise rotation and negative
values correspond to anti-clockwise rotation.
500 signifies an output frequency of 50.0 Hz, i. e. the
required value must be multiplied by a factor of 10.
Please see the user manual for the respective
frequency inverter model (motor drive controller), for
information on available parameter numbers,
permissible ranges for parameters and the device
status word.
The last two digits of a parameter value at the
TransmitValue input are interpreted as decimal
places, e. g. 223.10 = 22310 (factor 1 = 100). In other
words, the value in the user manual for the frequency
inverter must be multiplied by 100 in the program.
For parameter values larger than 655.35 (i. e. 65535)
you must specify an offset in TransmitValueOffset
which is added to the value in TransmitValue. In
TransmitValueOffset too, the last two digits are
interpreted as decimal places.
06/99 AWB 2700-1306 GB

The status word returns current drive status

information in bit-mapped format.

294
 DE4netK

The current output frequency of the DF 4 is indicated

by ActualFrequency in Hz. Positive values corre-
spond to clockwise rotation and negative values
correspond to anti-clockwise rotation. 500 signifies
an output frequency of 50.0 Hz.
The last two digits of a parameter value at the
ReceiveValue output are interpreted as decimal
places, e. g.: 22310 ≡ 223,10 or 100 ≡ 1.
For parameter values larger than 655.35 (i. e. 65535)
the remainder of the total parameter value required
is automatically entered in ReceiveValueOffset.
The last two digits are interpreted here too as
decimal places.
Read parameter:
왘 Specify parameter number in Parameternumber

왘 Specify “Command = 1”. “Busy” changes from

“0” to “1” automatically
왘 Wait until Busy goes from “1” to “0”:
If ErrorCode is 0:
Accept “ReceiveValue” and
“ReceiveValueOffset” if required
If “ErrorCode” is not 0:
Command was not executed,
check “ErrorCode”
왘 Specify “Command = 0”. Next command can be
started
06/99 AWB 2700-1306 GB

295
 Function Blocks

Write parameters:
왘 Specify parameter number in Parameternumber

왘 Specify parameter value in TransmitValue

(and in TransmitValueOffset if reqd.)
왘 Specify “Command = 2”. “Busy” changes from
“0” to “1” automatically
왘 Wait until Busy goes from “1” to “0”:
If ErrorCode is 0:
Command was executed correctly,
If ErrorCode is not 0:
Command was not executed, check ErrorCode
왘 Specify “Command” = 0. Next command can be
started
Error codes for parameter data transfer at the
ErrorCode output:
0 No errors
1 Invalid service
5 Invalid parameter number
6 Invalid command parameter
10 Access not allowed, e. g. write request for read-
only parameters
14 Permissible range exceeded, e. g. value too
high
254 Timeout if the reaction time to a read/write
command is longer than 5 seconds
255 Other error – command cannot be executed at
present
06/99 AWB 2700-1306 GB

296
 DE4netK

Example: function block DE4netK

Declare station 1 on line 1
VAR
Drive_1 :DE4netK;
RD_S1T1 at %RDB1.1.0.0 :ARRAY[0..11] OF BYTE;
SD_S1T1 at %SDB1.1.0.0 :ARRAY[0..11] OF BYTE;
END_VAR

CAL Drive_1(Enable := ,
Start := ,
Quickstop := ,
DCBrake := ,
TripReset := ,
ParameterSet := ,
MotorPotUp := ,
MotorPotDown := ,
FixedFrequency1 := ,
FixedFrequency2 := ,
FixedFrequency3 := ,
Reversal := ,
FreezeRamp := ,
ReferenceFrequency := ,
Command := ,
Parameternumber := ,
TransmitValue := ,
TransmitValueOffset := ,
SendData := SD_S1T1,
ReadData := RD_S1T1
|
:=StatusWord,
:=ActualFrequency,
:=EchoCommand,
:=EchoParameternumber,
:=Busy,
:=ReceiveValue,
:=ReceiveValueOffset,
:=ErrorCode)
06/99 AWB 2700-1306 GB

297
 Function Blocks

Deserialize
Extract Data from Arrays

Prototype of function block

Meaning of operands
Destination Destination variable

Buffer Source area

BufferOffset Offset in source area

DestinationLength Length of destination variable in bytes

Error Error code

Description
The Deserialize function block extracts any required
data type from a source area at a starting position
specified by “Buffer + BufferOffset”.
The DestinationLength output specifies the length of
the destination data type in bytes.
Buffer is an array of any size. All ANY_BIT and
ANY_INT types apart from BOOL are permissible as
array elements.
06/99 AWB 2700-1306 GB

298
 Deserialize

Error codes at the Error output:

0 No errors
1 Buffer overflow
2 Offset lies outside the buffer
3 Destination lies within the buffer
4 DestinationLength is “0”

The destination data type BOOL is not supported

and will result in an error during compilation.
For this see the function “Serialize” on page 453.

Example: Extracting 20 bytes from a 30-byte array

PROGRAM sendstruct
VAR
deserie_fb : Deserialize;
struct_buffer AT %RDB1.1.0.0 : ARRAY [1..30] OF BYTE;
CheckSumOffset : UINT := 0;
CheckSum : UINT;
DTOffset : UINT := 2;
ReceiveDatum : DT; (* Receive date *)
DataOffset: UINT := 10;
ReceiveData :Array [1..20] OF BYTE; (* User data *)
DeserializedLength : UINT;
Error : USINT;
END_VAR

(* Extract receive data *)

CAL deserie_fb( Destination := CheckSum,
Buffer := struct_buffer,
BufferOffset := CheckSumOffset,
|
DeserializedLength := DestinationLength)
LD deserie_fb.Error
USINT_TO_BOOL (* Any Error ? *)
JMPC _Fail (* Error handling *)

CAL deserie_fb( Destination := ReceiveDatum,

Buffer := struct_buffer,
BufferOffset := DTOffset,
|
06/99 AWB 2700-1306 GB

DeserializedLength := DestinationLength)
LD deserie_fb.Error
USINT_TO_BOOL (* Any Error ? *)
JMPC _Fail (* Error handling *)

299
 Function Blocks

CAL deserie_fb( Destination := ReceiveData,

Buffer := struct_buffer,
BufferOffset := DataOffset,
|
DeserializedLength := DestinationLength)

LD deserie_fb.Error
USINT_TO_BOOL (* Any Error ? *)
JMPC _Fail (* Error handling *)

(* Received data complete *)

_Fail: (* Error handling *)

06/99 AWB 2700-1306 GB

300
 DialOrHangup

PS 4-300 DialOrHangup
PS 416 Establish or Clear a Connection to a DTE via
Modem

Prototype of function block

Meaning of operands
Prefix Dialling prefix before telephone number (for
example, “0W“)
If no prefix is required, the associated string
variable must at least contain an empty string
(String(0):=”;).

PhoneNumber Telephone number (sum of Prefix and

PhoneNumber max 34 characters)

ResponseString Modem response string (max. 254 bytes)

Strobe Enable function block

SlotNumber Selection of PLC interface:

06/99 AWB 2700-1306 GB

0: PS 416-CPU 400/300-SBI or
PS 4-341-MM1 SBI (transparent mode),
4...20: Slot for appropriate COM card

FBMode Mode “Dial” or “Hangup”

301
 Function Blocks

DialMode Dialling mode “Tone” or “Pulse”

TimeOut Wait for response (10..90 seconds),

Default: 60 seconds

Active Status of function block processing

1: Function block active (parameters accepted)
1 -> 0: Function block completed

ConnectOK CONNECT string in ResponseString

1: CONNECT received, 0: CONNECT not received

HangupOK OK string in ResponseString

1: OK received,
0: OK not received

ResponseStrLen Number of characters received

Error Error code

Description
The DialOrHangup function block has two modes:
Dial and Hangup. This is specified with the FBMode
input:
TYPE tFBMODE:
( Dial,
Hangup ):=Dial;
END_TYPE

In Dial mode, the specified telephone number is

dialled to establish a connection to a DTE via
modem.
In Hangup mode, an existing connection to a DTE is
cleared.
The function block requires that both PLC and DTE
are connected to modems; furthermore, the
parameters of the serial interface should be set to the
06/99 AWB 2700-1306 GB

same values on the PLC and the PLC modem.

302
 DialOrHangup

An active send operation will be aborted on the

PS 416-COM-200 card if the Modem function block
is activated via the “TransmitActive” output of the
COM function block. This can be avoided by starting
a timer with the TransmitActive output, that causes a
delay according to the specified baud rate and the
data volume to be sent. This does not affect Trans-
parent mode with the central unit.
Error codes are output to the Error output. Errors 1 to
11 can occur during function block execution; with
errors 16 to 25 the function block was not executed.
0 No error
1 ResponseString contains an unknown response
2 ResponseString incomplete or is longer than the
declared length of the ResponseString variable
3 ResponseTimeOut. For example, no response
received because
– Problem with connection to modem,
– Interface parameters for the PLC and modem
do not match,
– Modem not active.
4 Error when receiving data
5 Error when transmitting data
6 ResponseString contains: BUSY Remote phone
number engaged
7 ResponseString contains: NO CARRIER
No modem connect possible or modem carrier
lost for more than 10 seconds
8 ResponseString contains: ERROR
Invalid modem command
9 ResponseString contains: NO DIALTONE
No dial tone received
06/99 AWB 2700-1306 GB

303
 Function Blocks

10 ResponseString contains for example:

DIAL LOCKED, .. DELAYED
Dialling locked
11 ResponseString contains: NO ANSWER
Remote phone number does not answer
16 SlotNumber invalid (0, 4...20)
20 TimeOut not in permissible range (10...90)
21 CPU 400-SBI/COM 200: Transparent mode not
or incorrectly set
22 COM 200: Not in specified slot
23 COM 200: No or incorrect IFM inserted
25 Modem not configured for Echo-OFF
Dial Mode
On detecting a rising edge at the Strobe input, all
input parameters (SlotNumber, FBMode, DialMode,
Prefix, PhoneNumber and TimeOut) are read.
The settings for the parameters DialMode and Prefix
are dependent on the type of modem and telephone
connection. DialMode specifies the two different
dialling methods which are used.
Type tDIALMODE:
( Tone,
Pulse ) :=Tone;
END_TYPE

The parameters Prefix, DialMode and PhoneNumber

are assembled by the function block into an AT
command and sent to the modem.
After enabling the function block, Active is set to “1”.
Active is set back to “0” if a modem response is
received, if a parameter error is detected or if the
timeout is exceeded.
06/99 AWB 2700-1306 GB

The timeout is specified with TimeOut in seconds.

Signal transitions at the Strobe input are ignored
while Active is “1”.

304
 DialOrHangup

ResponseString contains the entire response string

from the modem. ConnectOK is set to “1” if the
modem has returned a connect message.
The HangupOK output is not used in Dial mode.
Error is “0” if no error was detected. It contains an
error code if an error was detected or the modem
response is not a connect message.
Hangup Mode
On detecting a rising edge at the Strobe input, an
existing connection to a DTE is cleared. The Prefix
and PhoneNumber output are not used in Hangup
mode but must still be specified.

The function block automatically configures the

modem as follows
– Modem result codes on,
– Modem result codes plain text (verbose) on and
– Modem command echo off.
Other function blocks can also be used to access
the COM or SBI interface. Conflicts can occur if
several function blocks try to access the same
interface. If necessary, the user program should
include interlocks to make sure that this cannot
happen.
06/99 AWB 2700-1306 GB

305
 Function Blocks

Example: establishing a connection

and hanging up
PROGRAM Dial_Com_Hangup
(* Press strobe button=Dial -> Send message with FB "COM"
-> Press strobe button=Hangup *)

VAR
FB_DAH : DialOrHangup;
FB_SEND : COM;
StringToArray : STRtoCOM;
DAH_FallingEdge : F_TRIG;
SEND_FallingEdge : F_TRIG;
Make_Dial : BOOL;
DAHFlag : BOOL;
SENDFlag : BOOL;
PhoneString : String(30);
FB_Strobe AT %I0.0.0.0.0 : BOOL;
Display_DAH_Active AT %Q0.0.0.0.0 : BOOL;
Display_ConnectOK AT %Q0.0.0.0.1 : BOOL;
Display_HangupOK AT %Q0.0.0.0.2 : BOOL;
Display_DAH_Error AT %QW0.0.0.2 : UINT;
Prefix : STRING(3):=‘00W‘;
PhoneNumber : STRING(13):=‘0228,602,1414‘;
Response : STRING(254);
message : String(54):=‘Hello, this is the PS 416 $R$L‘;
sendString : String(80);
sendData : ARRAY [1..256] OF BYTE;
receiveData : ARRAY [1..256] OF BYTE;
...
END_VAR

FbMODE: (* FBMode_Selection: Dial or hangup mode *)

LD Make_Dial
JMPC disconnect
LD Dial
ST FB_DAH.FBMode
JMP Phone

Disconnect:
LD Hangup
ST FB_DAH.FBMode
JMP Start
06/99 AWB 2700-1306 GB

Phone:
LD PhoneNumber
St PhoneString
JMP Start

306
 DialOrHangup

Start: (* Enable Dial or Hangup *)

LD DAHFlag
JMPC CheckAnswer

Call:
CAL FB_DAH( Strobe :=FB_Strobe, (* Button *)
SlotNumber :=10,
FBMode :=,
DialMode :=Tone,
Prefix :=Prefix,
PhoneNumber :=PhoneString,
ResponseString :=Response,
TimeOut := 60
|
Display_DAH_Active :=Active,
Display_ConnectOK :=ConnectOK,
Display_HangupOK :=HangupOK,
:=ResponseStrLen,
Display_DAH_Error :=Error)

LD Response
LD DAHFlag (* Detect falling edge on FB_Active *)
JMPC CheckAnswer
CAL DAH_FallingEdge(
CLK :=FB_DAH.Active
|
:=Q)
LD DAH_FallingEdge.Q
JMPCN End
LD 1
ST DAHFlag

CheckAnswer:
...
LD FB_DAH.Error
GT 0
JMPC Error
LD FB_DAH.ConnectOK
JMPC Connect
LD FB_DAH.HangupOK
JMPC Disconnected
JMP End
06/99 AWB 2700-1306 GB

Connect: (* Send text, set strobe *)

...
LD 1
ST FB_SEND.TransmitStrobe
JMP Send

307
 Function Blocks

Disconnected:
...
LD 0
ST Make_Dial (* Redial is now allowed *)
LD 0
ST SENDFlag
ST DAHFlag
LD 0 (* Send text, reset strobe *)
ST FB_SEND.TransmitStrobe
JMP Send

Send: (* Convert string to ByteArray *)

LD message
ST sendString
CAL StringToArray( Enable :=1,
TextString :=sendString,
TransmitVariable :=sendData
|
:=StrLen )
CAL FB_SEND( ReSet :=,
Mode :=1,
TransmitStrobe :=,
ReceiveStrobe :=,
SlotNumber :=10,
TransmitNumber :=StringToArray.StrLen,
ReceiveNumber :=,
TransmitVariable :=sendData,
ReceiveVariable :=receiveData
|
:=TransmitActive,
:=ReceiveActive,
:=TransmitError,
:=ReceiveError,
:=ReceivedBytes,
:=InterfaceStatus,
:=SlotError)

(* Detect falling edge on FB_TransmitActive *)

LD SENDFlag
JMPC CheckSendAnswer
CAL SEND_FallingEdge( CLK :=FB_SEND.TransmitActive
|
06/99 AWB 2700-1306 GB

:=Q )

LD SEND_FallingEdge.Q
JMPCN End
LD 1
ST SENDFlag

308
 DialOrHangup

CheckSendAnswer:
...
LD 0
ST DAHFlag
LD 0
ST Make_Dial (* Data sent, hang up *)
JMP End

Error:
...
LD 1
ST Make_Dial (* Dialling error, hang up *)
LD 0
ST SENDFlag
ST DAHFlag

End:
END_PROGRAM
06/99 AWB 2700-1306 GB

309
 Function Blocks

PS 4-200 1) EdgeAlarm
PS 4-300 Edge-Controlled Alarm Function Block
PS 416

Prototype of function block

Meaning of operands
EnableDisable Enable and disable alarm execution
Start condition rising edge (0 = Disable, 1 =
Enable)

Number Alarm channel number

(for PS 4-141/-151/-201 = 0
for PS 4-341 = 0 and 1

RisingEdge Edge selection (0 = rising, 1 = falling)

SetpointValue Setpoint entry for the counter

SubRoutine Instance name of the function block called by the

alarm

Error Error messages

CallUpNumber Number of alarm-controlled function block calls

06/99 AWB 2700-1306 GB

1) Not for PS 4-271

310
 EdgeAlarm

Description
The EdgeAlarm function block is permanently
assigned in the PS 4-201-MM1 to the hardware input
%I0.0.0.0.0; on the PS 4-141-MM1 and PS 4-151-
MM1 this permanently assigned input is %I0.0.0.1.0.
The PS 4-341-MM1 controller is provided with two
EdgeAlarm inputs: %I0.0.0.0.1.0 and %I0.0.0.1.1.
The input EnableDisable starts and stops the
counter. With a rising edge (0–1 transition) the
counter is started. The counter is stopped and reset
if the input status changes from “1” or TRUE to “0” or
FALSE.
The RisingEdge input is used to define which signal
edge is to be evaluated.
The SetPointValue input defines the number of
signals to be counted before the alarm and the
function block are activated.
The maximum system capacity depends on the
following three factors: “Predivide”, “SetPointValue”
and the frequency set. These factors must be
selected so that no more than two interrupts occur
per millisecond.
The Error output indicates the following error code:
0 No errors
1 Setpoint is 0
3 Invalid alarm channel number

Error code with PS 4-300 only

4 Alarm channel number already used
The “CallUpNumber” output (value range: 0 – 65535)
06/99 AWB 2700-1306 GB

indicates how often the value defined at the

SetpointValue input has been reached.

311
 Function Blocks

The SubRoutine input allows event-controlled

programming to be implemented. This is done by
stating the instance name of the function block to be
activated when the event is reached. If no instance
is specified, the count value CallUpNumber will
continue to be incremented without triggering the
alarm.

The following points must be observed for the event-

driven program:
After the event has occurred, the user program is
interrupted, the register status is saved and the
function block instance defined at SubRoutine is
executed. The function block called by the alarm
06/99 AWB 2700-1306 GB

function block must not have any VAR_IN_OUT

parameters. This kind of instance must only have
local variables (VAR) or global variables that have
been declared externally as VAR_EXTERNAL
variables.

312
 EdgeAlarm

The alarm function block cannot be interrupted by

other alarm function blocks (all alarm function blocks
have the same priority). The maximum execution
time of alarm function blocks is to be restricted to
5 ms (approx. 1K IL instructions) in the user program
since the alarm function blocks cannot be interrupt-
ed even by the operating system in the event of a
voltage drop. If the execution time is exceeded, an
EDC error may occur when switching off the power
supply.
The execution time of the alarm function block is
added to the execution time of the cyclical user
program and also monitored by the cycle time
monitoring function.
Since event-driven program processing is allowed
access to the entire image register, access to data
that is used by the event-controlled and cyclical user
program must be disabled. Bit accesses to the same
byte may only occur in the cyclical user program and
in the Alarm function block if the access is synchro-
nized with Disable_Interrupt and Enable_Interrupt.
Since, due to its fast reaction times, an Alarm
function block requires a high-speed peripheral
access (direct output), the QB, QPB peripheral
operands available in the basic unit should be used.
An alarm function block can be used several times
(multiple instantiation) although this should normally
be avoided since each function block group has the
same event source and only the last function block
instance in the program is valid. Multiple instantiation
is only useful if the parameters of the function block
are set again within an interrupt routine and an edge
06/99 AWB 2700-1306 GB

disable is to be implemented.

313
 Function Blocks

By multiple instantiation is meant the reservation of

several data ranges for each parameter set of a
particular function block type.

The input parameters of an alarm function

block should only be assigned between the
parentheses when it is called. An explicit
parameter assignment outside of the parenthe-
ses before or after the invocation is not possible.

Example: event-driven program processing with

EdgeAlarm
PROGRAM alarm

VAR
Edgealarm : EdgeAlarm;
Error : USINT;
CountValue : UINT;
Pump : react_fb;
(*Declaration of function block
that is activated in the event of an alarm *)
END_VAR

(* Call EdgeAlarm function block

to call a function block for pumping -
when a particular water level
is reached in tank.
This is indicated via a rising edge *)

CAL EdgeAlarm(EnableDisable := 1,
Number := 0,
RisingEdge := 0,
SetPointValue := 1,
Subroutine := Pump)
LD EdgeAlarm.Error
ST Error
LD EdgeAlarm.CallUpNumber
ST CountValue
(*This indicates the number of alarms *)
06/99 AWB 2700-1306 GB

END_PROGRAM

314
 F_TRIG

F_TRIG
Edge Detection of the Falling Edge

Prototype of function block

Meaning of operands
CLK Input operand whose falling edge is detected.

Q Output operand; indicates the falling edge of

“CLK”.

Description
The function block “F_TRIG” evaluates the status of
the input operand “CLK”. It detects the status
change from “1” in a processing cycle to “0” in the
subsequent cycle and indicates this on the output
“Q” with the Boolean value “1”. The output is only set
to “1” during the processing cycle in which the
change of the status of “CLK” and a falling edge was
detected.
06/99 AWB 2700-1306 GB

315
 Function Blocks

Example: evaluating edges

PROGRAM edges

VAR
Signal1_incoming : R_TRIG;
Signal1_outgoing : F_TRIG;
Signal1 AT %I0.0.0.0.2 : BOOL;
Pulse_0_1 : BOOL;
Pulse_1_0 : BOOL;
END_VAR

CAL Signal1_incoming(CLK := Signal1)

LD Signal1_incoming.Q
ST Pulse_0_1
CAL Signal1_outgoing(CLK := Signal1)
LD Signal1_outgoing.Q
ST Pulse_1_0

END_PROGRAM

06/99 AWB 2700-1306 GB

316
 FifoBx

FifoBx
8-Bit FirstIn-FirstOut Register (Queue)

Prototype of function block

Meaning of operands
FillPulse Fill pulse

ReadOutPulse Readout pulse

ReSet Reset

DataInput Data input

Full Register full

Empty Register empty

DataOutput Data output

Description
There are 128 function block prototypes. The follow-
ing names can be used for *:
FifoB1
FifoB2
.
.
FifoB128
06/99 AWB 2700-1306 GB

317
 Function Blocks

The numbers 1 ... 128 indicate the register length –

the number of 8-bit register fields – of the individual
prototypes.
A rising edge on the FillPulse operand transfers the
value at the DataInput operand to the lowest free
register field of the register. The register can be filled
with every FullPulse signal until all register fields are
assigned. When the Full output is 1, the register is
full.

Contents of the FifoB8 register before and after a fill pulse 06/99 AWB 2700-1306 GB

318
 FifoBx

A rising edge on the ReadOutPulse operand reads

the first register field that has been written (the lowest
in the queue register) and transfers it to the
DataOutput operand. Each further ReadOutPulse
signal initiates the transfer of the next lowest
elements of the register field to the DataOutput
operand. When the Empty output is 1, this indicates
that the last register field has been read and the
register is empty.

Contents of the FifoB8 register before and after a ReadOut

pulse

If the ReSet operand is set to 1, this clears the

contents of the entire register.
06/99 AWB 2700-1306 GB

319
 Function Blocks

Example: Queue with FifoB32

PROGRAM fifo8_1

VAR
Queue_32_byte : FifoB32;
Pulse1 : BOOL;
Pulse2 : BOOL;
Reset : BOOL;
QueueData : USINT;
Full : BOOL;
Empty : BOOL;
Outputdata : USINT;
END_VAR

.
.
CAL Queue_32_byte(FillPulse := Pulse1,
ReadOutPulse := Pulse2,
ReSet := Reset,
DataInput := QueueData)

LD Queue_32_byte.Full
ST Full
LD Queue_32_byte.Empty
ST Empty
LD Queue_32_byte.DataOutput
ST Outputdata
.
.

END_PROGRAM

06/99 AWB 2700-1306 GB

320
 FifoWx

FifoWx
16-Bit FirstIn-FirstOut Register
(Queue)

Prototype of function block

Meaning of operands
FillPulse Fill pulse

ReadOutPulse Readout pulse

ReSet Reset

DataInput Data input

Full Register full

Empty Register empty

DataOutput Data output

Description
There are 128 function block prototypes. The follow-
ing names can be used for *:
FifoW1
FifoW2
.
06/99 AWB 2700-1306 GB

.
FifoW128

321
 Function Blocks

The numbers 1 ... 128 indicate the register length –

the number of 16-bit register fields – of the individual
prototypes.
A rising edge on the FillPulse operand transfers the
value at the DataInput operand to the lowest free
register field of the register. The register can be filled
with every FullPulse signal until all register fields are
assigned. When the Full output is 1, the register is
full.

Contents of the FifoW8 register before and after a fill pulse

03/99 AWB 2700-1306 D

322
 FifoWx

A rising edge on the ReadOutPulse operand reads

the first register field that has been written (the lowest
in the queue register) and transfers it to the
DataOutput operand. Each further ReadOutPulse
signal initiates the transfer of the next lowest
elements of the register field to the DataOutput
operand. When the Empty output is 1, this indicates
that the last register field has been read and the
register is empty.

Contents of the FifoW8 register before and after a ReadOut

pulse

If the ReSet operand is set to 1, this clears the

contents of the entire register.
06/99 AWB 2700-1306 GB

323
 Function Blocks

Example: Queue with FifoW16

PROGRAM fifo16_1

VAR
Queue_16_word : FifoW16;
Pulse1 : BOOL;
Pulse2 : BOOL;
Reset : BOOL;
QueueData : UINT;
Full : BOOL;
Empty : BOOL;
Outputdata : UINT;
END_VAR

.
.
CAL Queue_16_word(FillPulse := Pulse1,
ReadOutPulse := Pulse2,
ReSet := Reset,
DataInput := QueueData)
LD Queue_16_word.Full
ST Full
LD Queue_16_word.Empty
ST Empty
LD Queue_16_word.DataOutput
ST Outputdata
.
.

END_PROGRAM

06/99 AWB 2700-1306 GB

324
 GetRealTimeClock

GetRealTimeClock
Evaluation of the Real-Time Clock

Prototype of function block

Meaning of operands
Year Current year (two-digit)

Month Month

Day Day

Weekday Weekday (0 = Sunday)

Hour Hour

Minute Minute

Second Second

Description
The GetRealTimeClock function block gets the
current time and date from the real-time clock and
provides them at the output. An enable input is not
required. The function block provides values as soon
as it is called.
06/99 AWB 2700-1306 GB

325
 Function Blocks

PS 4-300 IEEE_To_Real
PS 416 Conversion of numbers from IEEE 754
standard format to data type REAL

IEEE_To_Real

BYTE EXPO_In Real_Out REAL

BYTE Mant_2_In Error BOOL
BYTE Mant_1_In
BYTE Mant_0_In

Prototype of function block

Meaning of operands
EXPO_In IEEE floating-point number to be converted:
exponent (inc. sign)
Mant_2_In IEEE floating-point number to be converted:
mantissa byte 2 (inc. 1 bit exponent)
Mant_1_In IEEE floating-point number to be converted:
mantissa byte 1
Mant_0_In IEEE floating-point number to be converted:
mantissa byte 0
Real_Out Converted real number
Error Error during conversion:
IEEE cannot be represented

Description
The function block IEEE_To_Real converts a floating-
point number of the IEEE format to the data type REAL.
To represent the floating-point number, four bytes
(32 bit) are needed. The format used conforms to the
IEEE 754 standard format (32 bit):

EXPO_In Mant_2_In Mant_1_In Mant_0_In

06/99 AWB 2700-1306 GB

The IEEE format is mostly used for the transfer of

floating-point number to other systems (e.g. via
PROFIBUS).

326
 IncEncoder

PS 4-300 IncEncoder
Control of local incremental encoder

IncEncoder

BOOL Enable State INT

Bool_R_Edge SetRefValue Error UINT
UINT RefMode CurrentValue UDINT
UDINT RefValue

Prototype of function block

Meaning of operands
Enable Enable for processing

SetRefValue Initiate transfer of reference value via software

RefMode Calibration mode:

0 = by edge on SetRefValue
1 = once via hardware
2 = permanently via hardware

RefValue 32-bit start value of counter in

Reference point/home position

State Calibration status:

0 = not calibrated, no counter values
1 = calibrated, normal operation

Error Error message:

0 = No errors
1 = Incremental encoder not configured
2 = Incorrect RefMode
3 = Internal error

CurrentValue Current counter value 32-bit

06/99 AWB 2700-1306 GB

327
 Function Blocks

Description
The IncEncoder function block counts the pulses of
an encoder connected locally to the PS 4-300.

Refer to AWB 2700-1311 GB for information on

the connection and engineering of the incremen-
tal encoder.

The following functions are possible:

Initiate reference approach
Define type of reference
Specify the counter value at zero point
(home position)
Scan counter actual value
The “Enable” input operand starts the evaluation of
the incremental encoder.
The “SetRefValue” operand allows the counter start
value “RefValue” to be transferred irrespective of the
encoder enable signal. This input is only evaluated
with reference mode “0”.
Define the type of calibration and reference
procedure via the “RefMode”. “0” initialises the start
value of the counter with “RevValue” with each edge
on “SetRefValue”, irrespective of a hardware signal.
“1” initialises the counter with the first pass via the
reference point. The subsequent passes are no
longer registered. “2”, on the other hand, calibrates
the counter with every pass over the reference point.

The setting of the counter via the hardware signal

is only possible if +24 V is supplied to input I0.3
of the PS 4-341-MM1 +24 V (see AWB 2700-
06/99 AWB 2700-1306 GB

1311).

328
 IncEncoder

Before counting can be started, the so-called

reference step must be carried out. This procedure is
for moving to the home position that is the basis for
moving to other positions during operation.
The reference step must be initiated each time the
application is started. For this define the required
type of calibration (RefMode) as well as the counter
start value for the home position (RefValue) and start
the reference procedure with the set Enable input.
Once calibration is completed the “State” output will
switch to 1. The current counter value can then be
scanned via the “CurrentValue” output if the
“Enable” input is set.
A falling edge on the “Enable” input stops counting
and resets the function block outputs.

The function block should only be instantiated

once.
06/99 AWB 2700-1306 GB

329
 Function Blocks

Example:
PROGRAM IncEncTest

VAR

IncEncChannel: IncEncoder ;
ActualPosition : UDINT ;
ErrorIncEnc: UINT ;
END_VAR

CAL IncEncChannel (
Enable :=1, (* Enable Incremental Encoder *)
SetRefValue :=0,
RefMode :=1, (* Reference step once via Hardware *)
RefValue :=10000 (* Zero point with 10,000 increments *)
|
:=State,
:=Error,
:=CurrentValue
)

(* Errors? *)
ld IncEncChannel.Error
st ErrorIncEnc
eq 0
jmpcn ERROR

(* Encoder calibrated? *)
ld IncEncChannel.State
eq 1
jmpcn NO_REF

(* Encoder calibrated; counter values are permissible *)

ld IncEncChannel.CurrentValue
st ActualPosition
jmp EOP

NO_REF:
(* Continue program code *)

ERROR:
(* Troubleshooting *)
06/99 AWB 2700-1306 GB

EOP:
(* End Of Program *)

END_PROGRAM

330
 LifoBx

LifoBx
8-Bit LastIn-FirstOut Register
(Stack Register)

Prototype of function block

Meaning of operands
FillPulse Fill pulse

ReadOutPulse Readout pulse

ReSet Reset

DataInput Data input

Full Register full

Empty Register empty

DataOutput Data output

Description
There are 128 function block prototypes. The follow-
ing names can be used for *:
LifoB1
LifoB2
.
.
06/99 AWB 2700-1306 GB

LifoB128

331
 Function Blocks

The numbers 1 ... 128 indicate the register length –

the number of 8-bit register fields – of the individual
prototypes.
A rising edge on the FillPulse operand transfers the
value at the DataInput operand to the lowest free
register field of the stack register. The stack register
can be filled with every FullPulse signal until all
register fields are assigned. When the Full output is
1, the stack register is full.

Contents of the stack LifoB8 register before and after a fill

pulse
06/99 AWB 2700-1306 GB

332
 LifoBx

A rising edge on the ReadOutPulse operand reads

the register field last written and transfers it to the
DataOutput operand. Each further ReadOutPulse
signal initiates the transfer of the next lowest
elements of the register field to the DataOutput
operand. When the Empty output is 1, this indicates
that the last register field has been read and the
register is empty.

Contents of the stack LifoB8 register before and after a

readout pulse

If the ReSet operand is set to 1, this clears the

contents of the entire stack register.
06/99 AWB 2700-1306 GB

333
 Function Blocks

Example: Stack register with LifoB64

PROGRAM lifo8_1

VAR
Queue_64_byte : LifoB32;
Pulse1 : BOOL;
Pulse2 : BOOL;
Reset : BOOL;
QueueData : USINT;
Full : BOOL;
Empty : BOOL;
Outputdata : USINT;
END_VAR

.
.
CAL Queue_64_byte(FillPulse := Pulse1,
ReadOutPulse := Pulse2,
ReSet := Reset,
DataInput := QueueData)

LD StackRegister_64_byte.Full
ST Full
LD StackRegister_64_byte.Empty
ST Empty
LD StackRegister_64_byte.DataOutput
ST Outputdata
.
.

END_PROGRAM

06/99 AWB 2700-1306 GB

334
 LifoWx

LifoWx
16-Bit LastIn-FirstOut Register
(Stack Register)

Prototype of function block

Meaning of operands
FillPulse Fill pulse

ReadOutPulse Readout pulse

ReSet Reset

DataInput Data input

Full Register full

Empty Register empty

DataOutput Data output

Description
There are 128 function block prototypes. The follow-
ing names can be used for *:
LifoW1
LifoW2
.
06/99 AWB 2700-1306 GB

.
LifoW128

335
 Function Blocks

The numbers 1 ... 128 indicate the register length –

the number of 16-bit register fields – of the individual
prototypes.
A rising edge on the FillPulse operand transfers the
value at the DataInput operand to the lowest free
register field of the stack register. The stack register
can be filled with every FullPulse signal until all
register fields are assigned. When the Full output is
1, the stack register is full.

Contents of the stack LifoW8 register before and after a fill

pulse
06/99 AWB 2700-1306 GB

336
 LifoWx

A rising edge on the ReadOutPulse operand reads

the register field last written and transfers it to the
DataOutput operand. Each further ReadOutPulse
signal initiates the transfer of the next lowest
elements of the register field to the DataOutput
operand. When the Empty output is 1, this indicates
that the last register field has been read and the
register is empty.

Contents of the stack LifoW8 register before and after a

readout pulse

If the ReSet operand is set to 1, this clears the

contents of the entire stack register.
06/99 AWB 2700-1306 GB

337
 Function Blocks

Example: Stack register with LifoW32

PROGRAM lifo16_1

VAR
Stackregister_32_byte : LifoW32;
Pulse1 : BOOL;
Pulse2 : BOOL;
Reset : BOOL;
StackData : UINT;
Full : BOOL;
Empty : BOOL;
Outputdata : UINT;
END_VAR

.
.
CAL Stackregister_32_word(FillPulse := Pulse1,
ReadOutPulse := Pulse2,
ReSet := Reset,
DataInput := StackData)
LD Stackregister_32_word.Full
ST Full
LD Stackregister_32_word.Empty
ST Empty
LD Stackregister_32_word.DataOutput
ST Outputdata
.
.

END_PROGRAM

06/99 AWB 2700-1306 GB

338
 MI4K

PS 4-200 MI4K
PS 4-300 Communication Function Block MI 4

Prototype of function block

Meaning of operands
RDB_Start Start address of the Suconet data exchange
interface input buffer (RDB)
e.g.. MI 4 as slave 1 on line 1
&%RDB1.1.0.0

SDB_Start Start address of the Suconet data exchange

interface output buffer (SDB)
e.g. . MI 4 as slave 1 on line 1
&%SDB1.1.0.0

Status MI 4 communication status

Description
The MI4K function block is used for communication
between the MI 4 series visualisation systems and
the PLC via Suconet K.
Status returns information on and error codes for the
communication:
01h: PLC is sending a data packet to the MI 4
02h: PLC is receiving a data packet from the MI 4
04h: PLC is receiving a data packet from the MI 4
C0h: Error in input parameters
80h: MI 4 has sent an invalid operation code /
06/99 AWB 2700-1306 GB

communication error
81h: Marker area exceeded / telegram length error
when reading markers from the PLC

339
 Function Blocks

82h: Marker area exceeded / telegram length error

when writing markers to the PLC
Please refer to the manual “Communication
MI 4-PLC” (AWB 27-1303 GB) for a detailed
description of this function block.

06/99 AWB 2700-1306 GB

340
 MI4netK

MI4netK
Communication Function Block MI 4 and MV 4

Prototype of function block

Meaning of operands
RDB_Start Suconet K data exchange interface input buffer
(RDB), e. g. MI 4 as slave 1 on line 1 with data
buffer 20/20:
AT %RDB1.1.0.0 ARRAY [1..20] OF BYTE

SDB_Start Suconet K data exchange interface output

buffer(SDB), e. g. MI 4 as slave 1 on line 1 with
data buffer 20/20:
AT %SDB1.1.0.0 ARRAY [1..20] OF BYTE

Status MI 4 communication status

Description
The MI4netK function block is used for communica-
tion between the MI 4 and MV 4 series of visualisa-
tion systems and the PLC via Suconet K.
Status returns information on and error codes for
communication:
01h: PLC is sending a data packet to the MI 4
02h: PLC is receiving a data packet from the MI 4
04h: No data request
C0h: Error in input parameters
80h: MI 4 has sent an invalid operation code /
06/99 AWB 2700-1306 GB

communication error
81h: Marker area exceeded / telegram length error
when reading markers from the PLC

341
 Function Blocks

82h: Marker area exceeded / telegram length error

when writing markers to the PLC
Please refer to the manuals “Communication MI 4 -
PLC” (AWB 27-1303 GB) and “Communication
MV 4-PLC“ (AWB-C 2700-1349 GB) for a detailed
description of this function block.

06/99 AWB 2700-1306 GB

342
 MOD200

PS 416 MOD200
Block for Serial Communication via
MODBUS / JBUS

Prototype of function block

Description:
The MOD200 function block is used to handle serial
communication via the MOD-BUS / JBUS card
PS 416-MOD-200.
Please refer to the manual “Hardware and
Engineering, PS 416-MOD-200-MOD-BUS / JBUS
Slave” (AWB-EM 27-1244-GB) for a description of
this function block and some application notes.
06/99 AWB 2700-1306 GB

343
 Function Blocks

MS_TimeFalling
Off-Delay Timer, Milliseconds

Prototype of function block

Meaning of operands
Set Start condition, rising edge

ReSet Reset condition

Hold Time interruption

PresetTime Time setpoint in milliseconds

OutputControl Control output

ElapsedTime Actual time value in milliseconds

06/99 AWB 2700-1306 GB

344
 MS_TimeFalling

Description

Time diagram

A rising edge on the Set input transfers the

PresetTime value as delay time T in milliseconds to
the timer. The OutputControl output switches to 1.
The time is started when the Set input switches to 0.
The OutputControl output switches off, i. e. set to 0
(1), after the delay time T has elapsed). The
ElapsedTime output shows the current time value in
milliseconds. If the status 0 at the Set input is shorter
than T, the OutputControl output stays 1.
Elapsing of the delay time can be stopped by setting
the Hold input to 1. The held delay time then
continues to run when the Hold input is reset to 0.
The off-delay time is therefore lengthened by the
duration of the Hold signal, i. e. T+THALT (2).
If the Hold input is 1 when the rising edge occurs on
the Set input, the start of the PresetTime value will be
delayed further by the duration of the 1 signal on the
Hold input. The status 1 will also be delayed on the
06/99 AWB 2700-1306 GB

OutputControl output (4).

345
 Function Blocks

If the Set input is reset from 1 to 0 while the Hold

input is set to 1, the time is started if Hold is then
reset to 0. The off-delay time is therefore lengthened
by the duration of the Hold signal, i. e. T+THALT (3).
If the Set input switches to “1” and then back to “0”
whilst the Hold input is set to “1” the OutputControl
output will remain “0”.
The timer is reset when the ReSet input is 1. A rising
edge on the Set input is only recognised as a start
when the ReSet has changed from 1 to 0 (5).
Example: Off-delay, 25 millisecond
PROGRAM time4

VAR
Timer4 : S_TimeFalling;
Start AT %I0.0.0.0.0 : BOOL;
Halt AT %I0.0.0.0.1 : BOOL;
TimeValue4 : UINT := 25;
(* TimeValue4 = 25 milliseconds *)
Output4 AT %Q0.0.0.0.0 : BOOL;
END_VAR

CAL Timer4(Set := Start,

Hold := Halt,
PresetTime := TimeValue4)
LD Timer4.OutputControl
ST Output4

END_PROGRAM 06/99 AWB 2700-1306 GB

346
 MS_TimeRising

MS_TimeRising
On-Delay Timer, Milliseconds

Prototype of function block

Meaning of operands
Set Start condition, rising edge

ReSet Reset condition

Hold Time interruption

PresetTime Time setpoint in milliseconds

OutputControl Control output

ElapsedTime Actual time value in milliseconds

06/99 AWB 2700-1306 GB

347
 Function Blocks

Description

Time diagram

A rising edge on the Set input transfers the

PresetTime value as delay time T in milliseconds to
the timer and starts the time. The OutputControl
output switches to 1 after the delay time has elapsed
and keeps this status until the Set input is reset to 0
(1). The ElapsedTime output shows the current time
value in milliseconds. If the status 1 at the Set input
is shorter than T, the OutputControl output stays
at 0.
Elapsing of the delay time can be stopped by setting
the Hold input to 1. The held delay time then
continues to run when the Hold input is reset to 0.
The delay time is therefore lengthened by the
duration of the Hold signal, i. e. T+THOLD (2).
If the Hold input is 1 when the rising edge occurs on
the Set input, the start of the time delay will be
delayed further by the duration of the 1 signal on the
Hold input (4). If Set input is reset from 1 to 0 after the
06/99 AWB 2700-1306 GB

time has elapsed, and while the Hold input is set to

1, OutputControl output returns to 0 when the Hold
input is reset to 0 (3).

348
 MS_TimeRising

The timer is reset when the ReSet input is 1. The time

cannot be started when the ReSet input is 1. A rising
edge on the Set input is only recognised as a start
when the ReSet has changed from 1 to 0 (5).
Example: On-delay, 7 milliseconds
PROGRAM time3

VAR
Timer3 : MS_TimeRising;
Start AT %I0.0.0.0.0 : BOOL;
Halt AT %I0.0.0.0.1 : BOOL;
Reset AT %I0.0.0.0.2 : BOOL;
TimeValue3: UINT := 7;
(* TimeValue3 = 7 milliseconds *)
ActTime3 AT %QW0.0.0.2 : BOOL;
Output3 AT %Q0.0.0.0.0 : BOOL;
END_VAR

CAL Timer3(Set := Start,

ReSet := Reset,
Hold := Halt,
PresetTime := TimeValue3)
LD Timer3.OutputControl
ST Output3
LD Timer3.ElapsedTime
ST ActTime3

END_PROGRAM
06/99 AWB 2700-1306 GB

349
 Function Blocks

PS 4-271 NItoCelsius
Linearisation of NI1000 values

NItoCelsius

INT InputValue Temperature INT

INT Offset Error BOOL

Prototype of function block

Meaning of operands
InputValue Value of resistance thermometer
The input can accept the following values including
offset (InputValue + Offset) depending on the
resistance thermometer:
695 (= –60.0 ºC) to 1500 (= 82.5 ºC)

Offset Offset in ohms which is added to the InputValue.

e. g. to take account of the resistance of the cable

Temperature Limits in ºC
–600 (= –60.0 ºC) to 825 (= 82.5 ºC)

Error Status = “1” when InputValue rises above or falls

below the indicated limits.
When in the normal range, the error bit is set to 0.

Description
The function block is used in conjunction with the
NI1000 input of the PS 4-271-MM1.
It linearises the converted value (0 to 1500) of a
NI1000 resistance into a temperature value.
The process of linearisation conforms to DIN IEC 751
for NI1000 resistances. Since the value stated in the
tables is for the NI100 resistance, it is necessary to
multiply the value for the NI1000 resistor by 10.
06/99 AWB 2700-1306 GB

350
 NItoCelsius

Example of linearisation
PROGRAM boiler_temperature
VAR
Temperature_sensed AT %IAW0.0.0.8: INT;
Offst: 2;
Temperature_value: INT;
Error: BOOL;
END_VAR

CAL NItoCelsius (InputValue := Temperature_sensed,

Offset := Offst
|
Error := Err)
LD NItoCelsius.Temperature
ST Temperature_value

END_PROGRAM
06/99 AWB 2700-1306 GB

351
 Function Blocks

PS 4-271 NItoFahrenheit
Linearisation of NI1000 values

NItoFahrenheit

INT InputValue Temperature INT

INT Offset Error BOOL

Prototype of function block

Meaning of operands
InputValue Value of the resistance thermometer
The input can accept the following values including
offset (InputValue + Offset) depending on the
resistance thermometer:
695 (= –76.0 ºF) to 1500 (= 180.6 ºF)

Offset Offset in ohms which is added to InputValue.

e.g. to take account of resistance of the cable

Temperature Limits in ºF
–760 (= –76.0 ºF) to 1806 (= 180.6 ºF)

Error Status = “1” when InputValue increases above or

falls below the limits.
When in the normal range, the error bit is set to 0.

Description
The function block is used in conjunction with the
NI1000 input of the PS 4-271-MM1.
It linearises the converted value (0 to 1500) of a
NI1000 resistance into a temperature value. The
process of linearisation conforms to DIN IEC 751 for
NI1000 resistances. Since the value stated in the
tables is for the NI100 resistor, it is necessary to
multiply the value for the NI1000 resistance by 10.
06/99 AWB 2700-1306 GB

352
 NItoFahrenheit

Example of linearisation
PROGRAM boiler_temperature
VAR
Temperature_sensed AT %IAW0.0.0.8: INT;
Offst: 2;
Temperature_value: INT;
Error: BOOL;
END_VAR

CAL NItoFahrenheit (InputValue := Temperature_sensed,

Offset := Offst
|
Error := Err)
LD NItoFahrenheit.Temperature
ST Temperature_value

END_PROGRAM
06/99 AWB 2700-1306 GB

353
354
Function Blocks

06/99 AWB 2700-1306 GB

 PdpFreezeSync

PdpFreezeSync
Send PROFIBUS-DP control commands to
DP slaves

PdpFreezeSync

BOOL Strobe Active BOOL

USINT MasterSlot Error UINT
tControlCommand Command
BYTE GroupSelect

Prototype of function block

Meaning of operands

Strobe Initiate a Freeze, UnFreeze, Sync or UnSync command

MasterSlot Slot number of DP master

PS 416: value range 4 to 19 (permissible slot)
PS 4-300: value range 1, 2 (permissible LE)

Command Permitted command are

Freeze
UnFreeze (default)
Sync
UnSync
TYPE tControlCommand
(UnFreeze,
Freeze,
UnSync,
Sync) := UnFreeze;
END_TYPE
06/99 AWB 2700-1306 GB

355
 Function Blocks

GroupSelect Select which group or combinations of groups of

slaves are to be addressed.
Value range: 0 to FFHex
Meaning:
0: all slaves connected to the DP line (default value)
Bit(0) = 1 : Group 1
Bit(1) = 1 : Group 2
...
Bit (7) = 1 : Group 8
FFHex = all groups 1 to 8 are addressed
(for this, see DP configurator)

Active State of command execution

1: Command accepted
1->0: Command completed

Error Error messages/error code:

0 No error
> 0 Error, for error code see description

Task of the function block

The “PdpFreezeSync” function block allows you to
send the PROFIBUS-DP control commands
“Freeze”, “Unfreeze”, “Sync” and “Unsync” to one or
several groups of DP slaves. The division of slave
into a maximum of 8 groups is carried out in the DP
Configurator.
The master sends the “Freeze” command to one or
several groups of slaves to read the current input
data, to send on the bus and to freeze it. Any input
data that changes after this point is not passed onto
the bus by the slave until the next “Freeze”
command is issued.
06/99 AWB 2700-1306 GB

356
 PdpFreezeSync

After every other subsequent “Freeze” command,

the last input data is read simultaneously by the
slaves, transferred to the bus and then frozen once
more.
The “Unfreeze” command is used to deactivate
“Freeze“ for one or several groups of slaves .
The master uses the Sync command to order one or
several groups of slaves to transfer the accept the
freeze and output the output data on the bus. The
data subsequently transferred on the bus is then no
accepated by the bus until the next “Sync”
command is issued.
After every other “Sync” command the output data is
accepted by the slaves simultaneously, frozen once
more and output.
The “Unsync” command deactivates “Sync”
command for one or several groups of slaves.
The commands “Freeze“, “UnFreeze“, “Sync” and
“UnSync” must only be carried out/activated in
succession. “Sync” and “Freeze” can, however, be
active at the same .

All PROFIBUS-DP function blocks

(PdpStationDiag, PdpFreezeSync) may access
the DP master sequentially only and should
therefore be instanced only once for each DP
master. If this not observed, error code 15 is
output.

A rising edge at the Strobe input triggers the function

block which causes the master to execute the
control command entered in Command. The group
06/99 AWB 2700-1306 GB

of slaves addressed is the one entered in

GroupSelect.
When the rising edge is detected, the function
block becomes active. The output Active has the

357
 Function Blocks

value 1. After the plausibility check of the input

values of the function block and the check of the
operating state of the DP master, the entered control
command is transferred to the master. The Active
output is reset (falling edge, 1 to 0), when the
command has been successfully completed or an
error occurred.
The function block detects the following errors (error
code):
1 The FB is faulty (internal error).
2 The entered command cannot be executed
(internal error).
3 The execution of the command was incorrect
(internal error).
4 The specified slot number is invalid.
7 No DP master is specified in the topology
configuration for the slot number entered.
8 The DP master is not configured at the slot
number specified in the topology configuration or
the firmware is older than version 1.2.
9 The DP master is not ready.
10 The transferred command is not valid (internal
error).
12 The user program was unable to access the
DualPortRam of the DP master (internal error)
13 The FB was unable to access the DualPortRam of
the DP master (internal error)
15 The slot is already occupied by another FB;
function blocks “PdpStationDiag” or
“PdpFreezeSync” were not called sequentially, at
least one of these function blocks is still active.
The bit of the group to be addressed is to be set in
06/99 AWB 2700-1306 GB

the input byte GroupSelect. 0 is to be set for Group1,

1 is to be set for Group2, etc.. All bit combinations
are permissible.

358
 PdpFreezeSync

Note: if no bit is set, all slaves connected to the

master are addressed!
Points to remember with the execution of the Freeze
and Sync commands:
The PLC user program cycle (PLC cycle) and the
DP cycle work independently of each other
(asynchronous). For synchronisation of the control
commands Freeze or Sync to the input and output
data, the following must be noted for calls of the
function block and for detection of the Active output.
The function block may only be called once in the
PLC cycle and must, if it has been activated, be
called in each subsequent cycle!
Freeze command:
The function block checks that the frozen input
data belongs to the specified freeze command.
The function block notifies the user program that
the slaves have executed the command and that
the associated input data is valid by resetting
(falling edge) the Active output.
The Active output is reset after no less than 5
PLC cycles. The number of cycles increases if the
DP cycle is longer than the PLC cycle or there are
access conflicts when data is exchanged via the
DualPortRam of the DP master.
Sequence in the user program:
1. Activate FB with Freeze command,
Active = 1 (1st PLC cycle)
2. Wait for falling edge at Active,
(2nd to mth PLC cycle)
3. Falling edge detected at Active,
Freeze was successfully executed, the input
06/99 AWB 2700-1306 GB

data now received by the user program

belong to this Freeze cycle, next Freeze
command can be started (5th to nth PLC
cycle).

359
 Function Blocks

Sync command:
The function block checks that the output data
from the PLC cycle are frozen by activating the
Sync command. The function block notifies the
user program that the slaves have executed the
Sync command by resetting (falling edge) the
Active output.
The Active output is reset after no less than 5
PLC cycles. The number of cycles increases if the
DP cycle is longer than the PLC cycle or there are
access conflicts when data is exchanged via the
DualPortRam of the DP master.
Sequence of the user program:
1. Output data processed and activate FB with
Sync command, Active = 1
(1st PLC cycle)
2. Wait for falling edge of Active,
(2nd to mth PLC cycle)
3. Falling edge of Active detected,
Sync was successfully executed, prepare new
output data,
next Sync command can be triggered
(5th to nth PLC cycle).

06/99 AWB 2700-1306 GB

360
 PdpFreezeSync

Example for Freeze and UnFreeze

PROGRAM docfreeze

(*
A Freeze command is sent to slaves of group 3 in cycles
of 100 ms. If the FB is active longer than 100 ms, the
Strobe is not executed for a further 100 ms etc.
The frozen values are stored for further processing after
the falling edge of Active has been detected.
Edge detection is performed by the F_TRIG function block.
Freeze mode is terminated with an UnFreeze command if 100
Freeze input bytes (FreezeByteCounter) have been logged.

Condition:
Connected to the DP_Master are at least 3 slaves which
have the addresses 2, 4 and 125 and have at least 1 input
byte. The slaves were combined as Group 3 in the DP
configurator. In the topology configurator, the DP master
was configured at slot 7.
The DP line has the number 2.
*)

VAR
FBPulse : TimeGenerator;
FBStrobe : R_TRIG;
FBFreezeSync : PdpFreezeSync;
FBActiveFallingEdge : F_TRIG;

(*DP line 2 station 2*)

Slave2_IB0 AT %IB2.2.0.0 : BYTE;
(*...*)
(*DP line 2 station 4*)
Slave4_IB0 AT %IB2.4.0.0 : BYTE;
(*...*)
(*DP line 2 station 125*)
Slave125_IB0 AT %IB2.125.0.0 : BYTE;
(*...*)

(* FreezeValues *)
FreezeByte1 : BYTE;
FreezeByte2 : BYTE;
FreezeByte3 : BYTE;
06/99 AWB 2700-1306 GB

(*...*)

361
 Function Blocks

(* Freeze Counter *)
FreezeByteCounter : USINT;

(* UnFreezeFlag *)
UnFreezeFlag : BOOL;

END_VAR
(*...*)

(* pulse generator with a period of 100 ms *)

CAL FBPulse(
Set :=1,
Period :=100
|
:=PulseOutput)

(* Rising edge detection of the pulse generator. *)

(* After 100 ms each time, Q is 1 for a cycle *)
CAL FBStrobe(
CLK :=FBPulse.PulseOutput
|
:=Q)

(* UnFreeze abort condition *)

LD UnFreezeFlag
JMPC _UnFreezeEnd

(* Freeze abort condition *)

LD FreezeByteCounter
EQ 100
JMPC _UnFreeze

(* Freeze command **********************************)

(* FB call *)
CAL FBFreezeSync(
Strobe :=FBStrobe.Q, (* ignored if
Active = 1 *)
MasterSlot :=7, (* DP master located
in Slot 7*)
Command :=Freeze,
GroupSelect :=16#04 (* Bit 2 set =
Group 3 *)
06/99 AWB 2700-1306 GB

|
:=Active,
:=Error)

362
 PdpFreezeSync

(* Falling edge detection*)

CAL FBActiveFallingEdge(
CLK :=FBFreezeSync.Active
|
:=Q)
LD FBActiveFallingEdge.Q
JMPCN _NextCycle
LD FBFreezeSync.Error
EQ 0
JMPCN _FBError

(* Falling edge detected and no error occurred *)

(* Freeze InputData are current after falling edge *)
(* Active and are assigned to FreezeByte1 to 3 *)
(* for further processing *)

LD Slave2_IB0
ST FreezeByte1
LD Slave4_IB0
ST FreezeByte2
LD Slave125_IB0
ST FreezeByte3

LD FreezeByteCounter
ADD 1
ST FreezeByteCounter
(*...*)

(* Error detection *)
_FBError:
(*...*)

(* Wait for falling edge *)

_NextCycle:
(*...*)

JMP _End

_UnFreeze:
(* UnFreeze command ********************************)

(* FB call *)
CAL FBFreezeSync(
06/99 AWB 2700-1306 GB

Strobe :=1, (* ignored if

Active = 1 *)
MasterSlot :=7, (* DP master located
in slot 7*)
Command :=UnFreeze,

363
 Function Blocks

GroupSelect :=16#04 (* Bit 2 set =

Group 3 *)
|
:=Active,
:=Error)

(* Falling edge detection*)

CAL FBActiveFallingEdge(
CLK :=FBFreezeSync.Active
|
:=Q)

LD FBActiveFallingEdge.Q
JMPCN _End

LD FBFreezeSync.Error
EQ 0
JMPCN _FBUnFreezeError

(* UnFreeze executed *)
LD 1
ST UnFreezeFlag

JMP _UnFreezeEnd

(* Error detection *)
_FBUnFreezeError:
(*...*)

_UnFreezeEnd:

(* Freeze mode has been terminated. *)

LD Slave2_IB0
LD Slave4_IB0
LD Slave125_IB0

_End:

END_PROGRAM
06/99 AWB 2700-1306 GB

364
 PdpFreezeSync

Example for Sync and UnSync

PROGRAM docsync

(*
A Sync command is sent to slaves of group 3 in cycles of
100 ms. If the FB is active longer than 100 ms, the Strobe
is not executed for a further 100 ms etc.
The output values are changed after the falling edge of
Active is detected (increased by 1 in this case) and
transferred to the master.
The function block F_TRIG performs edge detection.
The Sync is terminated with an UnSync command when the
output value (SyncByteCounter) is 100.

Condition:
Connected to the DP master must be at least 3 slaves which
have the addresses 99, 4 and 125 and at least 1 output
byte. The slaves were combined as Group 8 in the DP
configurator. In the topology configurator, the DP master
must be configured at slot 7.
The DP line must have the number 2.
*)

VAR
FBPulse : TimeGenerator;
FBStrobe : R_TRIG;
FBFreezeSync : PdpFreezeSync;
FBActiveFallingEdge : F_TRIG;

(*DP line 2 station 99 *)

Slave99_QB0 AT %QB2.99.0.0 : BYTE;
(*...*)
(*DP line 2 station 4, module 2 *)
Slave4_QB0 AT %QB2.4.2.0 : BYTE;
(*...*)
(*DP line 2 station 125, module 3 *)
Slave125_QB0 AT %QB2.125.3.0 : BYTE;
(*...*)

(* SyncValue *)
SyncByteCounter : USINT;
(*...*)
06/99 AWB 2700-1306 GB

(* UnSync Flag *)
UnSyncFlag : BOOL;

END_VAR

365
 Function Blocks

(* Example for the *)

(* output of counter values to a group of *)
(* slaves with the certainty that each counter value *)
(* is output with synchronisation by the slaves. *)

(*...*)

(* Pulse generator with a period of 100 ms *)

CAL FBPulse(
Set :=1,
Period :=100
|
:=PulseOutput)

(* Rising edge detection of the pulse generator. *)

(* After 100 ms each time, Q is 1 for one cycle *)
CAL FBStrobe(
CLK :=FBPulse.PulseOutput
|
:=Q)

(* UnSync abort condition *)

LD UnSyncFlag
JMPC _UnSyncEnd

(* Sync abort condition *)

LD SyncByteCounter
EQ 100
JMPC _UnSync

(* Sync command ************************************)

(* FB call *)
CAL FBFreezeSync(
Strobe :=FBStrobe.Q, (* ignored when
Active = 1 *)
MasterSlot :=7, (* DP master located
in Slot 7*)
Command :=Sync,
GroupSelect :=16#80 (* Bit 7 set =
Group 8 *)
|
:=Active,
06/99 AWB 2700-1306 GB

:=Error)

366
 PdpFreezeSync

(* Falling edge detection*)

CAL FBActiveFallingEdge(
CLK :=FBFreezeSync.Active
|
:=Q)

LD FBActiveFallingEdge.Q
JMPCN _NextCycle

LD FBFreezeSync.Error
EQ 0
JMPCN _FBError

(* Falling edge was detected and an error has *)

(* occurred. *)
(* New output data can be sent on the bus, *)
(* After 100 ms, a Sync command is initiated. *)
(* The new output data are accepted by the slaves *)
(* of Group 8 and frozen. *)
(* This ensures that each value of the variable *)
(* SyncByteCounter is sent to the slaves. *)

LD SyncByteCounter
ADD 1
st SyncByteCounter
USINT_TO_BYTE
ST Slave4_QB0
ST Slave99_QB0
ST Slave125_QB0

(*...*)

(* Error detection *)
_FBError:
(*...*)

(* Wait for FallingEdge *)

_NextCycle:
(*...*)

JMP _End
06/99 AWB 2700-1306 GB

_Unsync:

367
 Function Blocks

(* UnSync command *********************************)

(* FB call *)
CAL FBFreezeSync(
Strobe :=1, (* ignored when
Active = 1 *)
MasterSlot :=7, (* DP master located
in Slot 7*)
Command :=UnSync,
GroupSelect :=16#80 (* Bit 7 set =
Group 8 *)
|
:=Active,
:=Error)

(* Falling edge detection*)

CAL FBActiveFallingEdge(
CLK :=FBFreezeSync.Active
|
:=Q)

LD FBActiveFallingEdge.Q
JMPCN _End

LD FBFreezeSync.Error
EQ 0
JMPCN _FBUnSyncError

(* UnSync executed *)
LD 1
ST UnSyncFlag

JMP _UnSyncEnd

(* Error detection *)
_FBUnSyncError:
(*...*)

_UnSyncEnd:

(* Sync mode has been terminated. *)

(*...*)
06/99 AWB 2700-1306 GB

_End:

END_PROGRAM

368
 PdpStationDiag

PS 416 PdpStationDiag
Request Diagnostics Data from PROFIBUS-
DP Station

Prototype of function block

Meaning of operands

Strobe Initiate diagnostics job

MasterSlot Slot number of DP master

Value range for PS 416: 4 to 19 decimal
Value range for PS 4-300: 1, 2

StationAddress Network address of the DP slave

Active State of job execution

1: Job accepted
1 –> 0: Job completed

State1 Standard diagnostics byte 1 of PROFIBUS-DP

State2 Standard diagnostics byte 2 of PROFIBUS-DP

State3 Standard diagnostics byte 3 of PROFIBUS-DP

MasterAddress Address of master card, assigned to the scanned

06/99 AWB 2700-1306 GB

slave.

Ident ID of the PROFIBUS-DP station

Error Error messages

369
 Function Blocks

Description
The “PdpStationDiag” enables the diagnostics
data of a PROFIBUS-DP slave to be scanned. The
function block must only be instantiated once in the
user program for each PS 416-NET-440.
The Diagnose parameter defines an array with
100 elements of type BYTE into which the PS 416-
NET-440 enters the extended diagnostics data of the
addressed slave.
A successful job will cause the PS 416-NET-440 to
return 100 bytes, irrespective of the actual
diagnostics data length.

The field that you have transferred at the

Diagnose input and output must be 100 Byte.
The relevant diagnostics bytes for the application
are described in the documentation of the DP
slave. Ignore the other values.

A rising edge at the Strobe input starts the

diagnostics function.
Active output = 1 indicates that the job was accepted
after a plausibility check on the input values.The
status of the Strobe input is ignored for as long as the
Active output has the value 1.
If Active changes from 1 to 0, this means that the job
was completed.
The Error output indicates whether an error has
occurred. Error = 0 indicates that the job was
completed without errors.
06/99 AWB 2700-1306 GB

370
 PdpStationDiag

0 No error
1 FB faulty (faulty function block library)
2 Diagnostics data cannot be requested
3 Error when receiving diagnostics data
4 Invalid slot number (permissible values from
4 to 19)
5 Invalid station address (permissible values from
1 to 125)
7 No card defined in the topology configuration for
the slot specified.
8 No PS 416-NET-440 defined in the topology
configuration for the slot specified. Instead,
a different card was defined.
9 The PS 416-NET-440 is not ready for operation.
10 The specified station is not included in the
DP configuration.
11 No diagnostics data available for the specified
station.
12 The slot is already occupied by a different
function block; the function blocks
PdpStationDiag or PdpFreezeSync were not
called sequentially, at least one of these function
blocks is still active.
When job processing is successful, the function
block returns three standard PROFIBUS-DP
diagnostics bytes:
“State 1” diagnostics byte:
Bit 0: Station not responding
Bit 1: Station not ready for data exchange
Bit 2: Incorrect station parameters
Bit 3: Station-specific diagnostics data present
06/99 AWB 2700-1306 GB

Bit 4: Station has detected an unknown command

Bit 5: Station response not plausible
Bit 6: Incorrect parameter setting (e.g. ID number)

371
 Function Blocks

Bit 7: Station parameters set by a different master

“State2” diagnostics byte
Bit 0: Station parameters not set
Bit 1: Static diagnostics
Bit 2: Value permanently at 1
Bit 3: Watchdog active
Bit 4: Freeze command active
Bit 5: Sync command active
Bit 6: reserved
Bit 7: Station not included in the DP configuration.
“State3” diagnostics byte
Bit 0..6: reserved
Bit 7: The extended diagnostics data of the station
is longer than 100 Bytes.
A detailed description of this function block is
provided in the manual AWB 27-1330-GB “Hardware
and Engineering, PS 416-NET-440” (PROFIBUS-DP-
card).

06/99 AWB 2700-1306 GB

372
 PS_ApplicationHalt

PS 4-300 PS_ApplicationHalt
PS 416 Stop the User Program

Prototype of function block

Meaning of operands
Enable Event which stops program execution

Errorcode User-defined error number which is output following

a program halt when Enable changes to “1”.

Description
The PS_ApplicationHalt function block can be used
to halt a user program in the PS 4-300 or PS 416
controller in the event of a fatal error status defined
by the user. The error status is defined as an event in
the program.
The status of the event is assigned to the Enable
input which stops the program when its value
changes to “1”.
Errorcode specifies a user-defined error number
which the function block outputs to Sucosoft S 40
when the event occurs.
If status “1” occurs at the Enable input, the user
program is stopped. The PS 4-300 and PS 416
06/99 AWB 2700-1306 GB

switch from RUN to NOT READY. The outputs of

both PLCs are set to zero.

373
 Function Blocks

After the cause of the error is rectified, the user

program can only be restarted via a cold start.
You can inspect the error number in Sucosoft S 40 in
the Test and Commissioning tool in the Program
Diagnostics dialog box.
The event which stops the user program can be for
example an error message from a monitoring
program or a critical process condition which is
notified through a physical address.
Example: Halting a program and reporting an
error
PROGRAM proghalt

VAR
Halt_on_Error : PS_ApplicationHalt;
Error17 AT %I0.0.0.0.0 : BOOL;
END_VAR

CAL Halt_on_Error(Enable := Error17,

Errorcode := 17)

END_PROGRAM

06/99 AWB 2700-1306 GB

374
 PS_ClearKOMBit

PS 416 PS_ClearKOMBit
Clear “KOM” Diagnostic Bit

Prototype of function block

Meaning of operands
Enable Enables function block

Description
The PS_ClearKOMBit function block is used to clear
the “KOM” diagnostic bit. In certain situations it is
necessary to temporarily suppress the setting of the
“KOM” error bit (“Suconet K communication partner
has failed”). This may be necessary e. g. for
Suconet K stations which start up very slowly (PC
with EPC 335 card) or when replacing a Suconet K
station.
If the operating system of the PS 416 CPU has not
detected any other errors when the function block is
called, the call will clear the “error” LED on the front
of the CPU.

The function block should be called at the start of

the user program, and in any case before
checking the “KOM” bit.
Since the Suconet K line is checked cyclically by
the operating system of the PS 416 CPU at the
start of each program cycle, the “error” LED may
flash slightly if the error persists.
06/99 AWB 2700-1306 GB

375
 Function Blocks

Example: Clearing the KOM diagnostic bit

PROGRAM CheckKOM

VAR
ClearKOMBit : PS_ClearKOMBit ;
CheckKOMBit : PS_Message;
StartupDelay : TON ;
KOMError AT%Q0.0.0.0.0 : BOOL;
END_VAR

CAL StartupDelay( IN := 1,
PT := t#120s )

LDN StartupDelay.Q
CALC ClearKOMBit(Enable := 1)
CAL CheckKOMBit(MessageType := KOM
|
KOMError := Result )

END_PROGRAM

06/99 AWB 2700-1306 GB

376
 PS_Diagnostic

PS 416 PS_Diagnostic
Read Diagnostic Flags

Prototype of function block

Meaning of operands
DiagnosticType Read diagnostic flags using the Moeller enumerated
data type DIAGNOSTIC_TYPE

Result Status “1”: diagnostics bit is set

Status “0”: diagnostics bit is not set

Description
When calling the PS_Diagnostic function block, the
diagnostics flag to be monitored must be specified in
DiagnosticType.
DIAGNOSTIC_TYPE is defined as follows:
TYPE DIAGNOSTIC_TYPE:
( DBM,
DBC,
DAK) := DBM;
END_TYPE

DBM indicates the status of the backup battery on

the CPU. DBC indicates the status of the memory
card battery. The DAK flag indicates whether all
cards defined in the device configuration have been
installed. Status 1 for the individual data elements
has the following meaning:
DBM Failure of the CPU battery
06/99 AWB 2700-1306 GB

DBC Failure of the memory card battery

DAK Card missing

377
 Function Blocks

Example: checking battery state

PROGRAM battery

VAR
CPU_Bat_Test : PS_Diagnostic;
MC_Bat_Test : PS_Diagnostic;
CPU_Bat_Empty : BOOL;
MC_Bat_Empty : BOOL;
END_VAR

CAL CPU_Bat_Test(DiagnosticType := DBM)

CAL MC_Bat_Test(DiagnosticType := DBC)
LD CPU_Bat_Test.Result
ST CPU_Bat_Empty
LD MC_Bat_Test.Result
ST MC_Bat_Empty

END_PROGRAM

06/99 AWB 2700-1306 GB

378
 PS_GetDateAndTime

PS 4-300 PS_GetDateAndTime
PS 416 Get Date and Time

Prototype of function block

Meaning of operands
Item Scan of real-time clock via Moeller structure
ELEMENT_OF_DATE

CDT Returns the current date and time from the CPU in the format
of the DT data type

Description
The PS_GetDateAndTime function block is used to
read the real time clock and allows the PLC program
to react to particular time-related events and / or
execute time-dependent routines (e.g. to execute a
particular action at midday).
Item is a VAR_IN_OUT data element. When the
function block is invoked, the date elements are
automatically stored in the structure.
ELEMENT_OF_DATE is defined as follows:
TYPE ELEMENT_OF_DATE:
STRUCT
Millisecond : UINT;
Second : USINT;
Minute : USINT;
Hour : USINT;
Day : USINT;
Month : USINT;
Year : USINT;
06/99 AWB 2700-1306 GB

WeekDay : USINT;
END_STRUCT;
END_TYPE

379
 Function Blocks

Example: Reading time and date from the PLC

PROGRAM clock

VAR
RealtimeClock : PS_GetDateAndTime;
Date : ELEMENT_OF_DATE
Year : USINT;
Month : USINT;
Day : USINT;
DateTime : DT
END_VAR

CAL RealtimeClock(Item := Date)

LD Date.Year
ST Year
LD Date.Month
ST Month
LD Date.Day
ST Day
LD Date.CDT
ST DateTime

END_PROGRAM

06/99 AWB 2700-1306 GB

380
 PS_Message

PS 416 PS_Message
Read Cycle Status

Prototype of function block

Meaning of operands
MessageType Read the cycle flag via the Moeller enumerated data
type MESSAGE_TYPE

Result Status “1”: the bit is set

Status “0”: the bit is not set

Description
The messages and error messages output from a
running PLC program which can be displayed in
Sucosoft S 40 with the “Diagnostics” button in the
“Program Status” window of the “Test and
Commissioning” tool can be read and processed by
the PLC program itself by using the PS_Message
function block. For example, this can be used to
carry out a particular initialisation routine when the
program has just started (i. e. during the first cycle).
The Moeller enumerated data type MESSAGE_TYPE
is defined as follows:
TYPE MESSAGE_TYPE:
( ICS,
ISA,
RTW,
REC,
DAKE,
06/99 AWB 2700-1306 GB

KOM) := ICS;
END_TYPE

381
 Function Blocks

Status 1 for each of the data elements has the

following significance:

ICS 1st cycle after cold start is running

ISA 1st cycle after warm start is running

RTW Run Time Warning when a variable exceeds the

admissible range. Does not stop the program.
The variable which exceeded the admissible range is
not indicated.

REC Rest Cycle. Indicates that after a warm start the

program is continuing from the position of
interruption to the end of the cycle. The output states
are not refreshed during the rest cycle.

DAKE One of the configured cards is not fitted.

KOM A communication partner (SUCOnet K or

InterBus S) has failed.

Example: Reading program status

PROGRAM cycle

VAR
Coldstart_Test : PS_Message;
RestCycle_Test : PS_Message;
Coldstart : BOOL;
RestCycle : BOOL;
END_VAR

CAL Coldstart_Test(MessageType := ICS)

CAL RestCycle_Test(MessageType := REC)
LD Coldstart_Test.Result
ST Coldstart
LD RestCycle_Test.Result
ST RestCycle

END_PROGRAM
06/99 AWB 2700-1306 GB

382
 PS_ReadOSInfo

PS_ReadOSInfo
Read Operating System Information

Prototype of function block

Meaning of operands
OSIdentification Operating system identification text

Enable Enable the function block

OSVersion Operating system version number

Description
This function block is used to read the type and
version number of the operating system running in
the PLC.
If the Enable input is set to “1”, the operating system
version number is output to “OSVersion” and the
operating system identification text is output to
“OSIdentification”. The information is still available if
the Enable input returns to “0”.
The operand “OSIdentification” must be assigned to
an IN_OUT variable of type STRING and length 16.

The content of the OSVersion must be interpreted

as a 2-byte decimal value
Example: Version 1.00 -> 0100 Hex = 256 Dec
06/99 AWB 2700-1306 GB

383
 Function Blocks

Example: Read operating system information

PROGRAM os_info

VAR
FB_OS_Info : PS_ReadOSInfo;
Ident : STRING(16);
Enable AT %I0.0.0.0.0 : BOOL;
Version: UINT;
END_VAR

CAL FB_OS_Info(OSIdentification:= Ident,

Enable := Enable
|
Version := OSVersion)

END_PROGRAM

06/99 AWB 2700-1306 GB

384
 PS_SwitchPosition

PS 4-300 PS_SwitchPosition
PS 416 Read Switch Position

Prototype of function block

Meaning of operands
Result Check the position of the operating mode selector
switch via the Moeller enumerated data type
SWITCH_POSITION.

Description
The function block PS_SwitchPosition allows the
PLC program to check the status of the operating
mode switch, for example to react to a change in the
switch position in order to output an appropriate
warning.
The data type SWITCH_POSITION is defined as
follows:
TYPE SWITCH_POSITION:
( RUN,
RUN_MR,
HALT) := RUN;
END_TYPE
06/99 AWB 2700-1306 GB

385
 Function Blocks

Example: Checking the location of the operating

mode switch
PROGRAM switch
VAR
SWITCH : PS_SwitchPosition;
Indicate_RUN : BOOL;
Indicate_RUN_MR : BOOL;
Indicate_HALT : BOOL;
END_VAR

CAL SWITCH
LD SWITCH.Result
EQ RUN
JMPCN _RUN_MR
LD 1
ST Indicate_RUN
LD 0
ST Indicate_RUN_MR
ST Indicate_HALT
JMP _OUT

_RUN_MR :
LD SWITCH.Result
EQ RUN_MR
JMPCN _HALT
LD 1
ST Indicate_RUN_MR
LD 0
ST Indicate_RUN
ST Indicate_HALT
JMP _OUT

_HALT :
LD1
ST Indicate_HALT
LD 0
ST Indicate_RUN
ST Indicate_RUN_MR
_OUT:

END_PROGRAM
06/99 AWB 2700-1306 GB

386
 PSCO

PS 4-200 PSCO
PS 4-300 Profibus FMS Communication Block

Prototype of function block

Meaning of operands
Set Initiate job

Command Job type

CardAddress Interface selection

ObjectIndex Logical addressing of communication objects

(variables data arrays) of a station

MemoryAddress Start address of source and destination range

DataSize Size of source and destination range

Busy Function block status

Error Error messages

Description
The PSCO function block is used for handling
PROFIBUS communication via the LE 4-503-BS1
local expansion module. A function block instance is
used by the PLC program to access objects from the
06/99 AWB 2700-1306 GB

LE 4.
To find out more about possibilities and procedures
in PROFIBUS communication with the LE 4-503-BS1
local expansion module please refer to the manual

387
 Function Blocks

AWB 27-1264-GB for the module.

No more than one function block instance can be

used per object.

A 1 at the Set input starts the job specified at the

Command input. The function block stays active for
as long as the Set input is 1. A 0 or FALSE at the Set
input deactivates the function block. Any job being
processed will thus be aborted.
The parameters are checked after the function block
has been started. Incorrect parameters are indicated
by a message on the Error output.
The Command parameter is used to specify the job.
The following commands are available:
0 PUT OBJECT
1 GET OBJECT
2 PUT OBJECT CONTROL
3 CHECK
The individual commands are described in the
corresponding sections.
The number of the LE 4 module is set at the
“CardAddress” input. The value 1 is used since only
one communication LE is allowed for each PLC.
The LE 4-503-BS1 supports the logical addressing
of objects via the ObjectIndex parameter. Objects
are logically addressed via the parameter
“ObjectIndex” (see AWB 27-1264-GB, Appendix:
Object directory PROFIBUS properties). An object
cannot be accessed by several function block
instances.
06/99 AWB 2700-1306 GB

The MemoryAddress input defines the start address

of the data block in the marker area that is defined as
the data destination or source of a job.

388
 PSCO

The DataSize input defines the size of the data field,

i. e. the number of data bytes. When using command
3 (CHECK) a 1 should always be entered as the data
size.
The Busy output is only used in conjunction with the
PUT OBJECT CONTROL command.
1 = Job being processed
0 = Job completed.
The Error output indicates the following error code:
0 No error
1 Invalid command
2 Invalid module address (CardAddress)
3 Invalid object index
4 Start address of the data field + data field size
violates range limit
5 Incorrect operand type on
MemoryAddress input
6 Number data bytes (DataSize) does not match
the object size
7 Incorrect access to object, e. g. PUT command to
WRITE object
8 Hardware error on local expansion module
9 Access attempt of several function blocks to one
object
Please see the documentation for the LE 4-503-BS1
module (AWB 27-1264-GB) for details of the
commands and the PROFIBUS services.
06/99 AWB 2700-1306 GB

389
 Function Blocks

PS 4-271 PTtoCelsius
Linearisation of PT1000 values

PTtoCelsius

INT InputValue Temperature INT

INT Offset Error BOOL

Prototype of function block

Meaning of operands
InputValue Value of resistance thermometer
The input can accept the following values including
offset (InputValue + Offset) depending on the
resistance thermometer:
185 (= –200.0 ºC) to 1500 (= 130.5 ºC)

Offset Offset in ohms which is added to the InputValue.

e. g. to take account of the resistance of the cable

Temperature Limits in ºC
–2000 (= –200.0 ºC) to 1305 (= 130.5 ºC)

Error Status = “1” when InputValue rises above (>) or

falls below (<) the indicated limits.
When in the normal range, the error bit is set to 0.

Description
The function block is used in conjunction with the
PT1000 input of the PS 4-271-MM1.
It linearises the converted value (0 to 1500) of a
PT1000 resistance into a temperature value. The
method of linearisation conforms to DIN IEC 751 for
PT1000 resistances. Since the value stated in the
tables is for the PT100 resistance, it is necessary to
multiply the value for the PT1000 resistance by 10.
06/99 AWB 2700-1306 GB

390
 PTtoCelsius

Example of linearisation
PROGRAM boiler_temperature
VAR
Temperature_sensed AT %IAW0.0.0.8: INT;
Offst: 2;
Temperature_value: INT;
Err: BOOL;
END_VAR

CAL PTtoCelsius (InputValue := Temperature_sensed,

Offset := Offst
|
Error := Err)
LD PTtoCelsius.Temperature
ST Temperature_value

END_PROGRAM
06/99 AWB 2700-1306 GB

391
 Function Blocks

PTtoFahrenheit
Linearisation of PT1000 values

PTtoFahrenheit

INT InputValue Temperature INT

INT Offset Error BOOL

Prototype of function block

Meaning of operands
InputValue Value of the resistance thermometer
The input can accept the following values including
offset (InputValue + Offset) depending on the
resistance thermometer:
185 (= –328.0 ºF) to 1500 (= 266.8 ºF)

Offset Offset in ohms which is added to InputValue.

e.g. to take account of resistance of the cable

Temperature Limits in ºF
–3280 (= –328.0 ºF) to 2668 (= 266.8 ºF)

Error Status = “1” when InputValue increases above (>)

or falls below (<) the limits.
When in the normal range, the error bit is set to 0.

Description
The function block is used in conjunction with the
PT1000 input of the PS 4-271-MM1.
It linearises the converted value (0 to 1500) of a
PT1000 resistance into a temperature value. The
process of linearisation conforms to DIN IEC 751 for
PT1000 resistances. Since the value stated in the
tables is for the PT100 resistor, it is necessary to
multiply the value for the PT1000 resistance by 10.
06/99 AWB 2700-1306 GB

392
 PTtoFahrenheit

Example: Linearisation
PROGRAM boiler_temperature
VAR
Temperature_sensed AT %IAW0.0.0.8: INT;
Offst: 2;
Temperature_value: INT;
Err: BOOL;
END_VAR

CAL PTtoFahrenheit (InputValue := Temperature_sensed,

Offset := Offst
|
Error := Err)
LD PTtoFahrenheit.Temperature
ST Temperature_value

END_PROGRAM
06/99 AWB 2700-1306 GB

393
 Function Blocks

R_TRIG
Edge Detection, Rising Edge

Function block prototype

Meaning of the operands

CLK Input operand whose rising edge is detected.

Q Output operand; indicates the rising edge of

“CLK”.

Description
The function block R_TRIG evaluates the status of
the input operand “CLK”. It detects the status
change from “0” in a processing cycle to “1” in the
subsequent cycle and indicates this on the output
“Q” with the Boolean value “1”. The output is only set
to “1” during the processing cycle in which the
change of the status of “CLK” and a rising edge was
detected.

06/99 AWB 2700-1306 GB

394
 ReadAnalogDirect

PS 416 ReadAnalogDirect
Direct Reading of Analog Inputs

Prototype of function block

Meaning of operands
Slot Slot for an analog card in the basic unit (4..20)

WordMask Bit mask specifying which channels are to be read

AnalogInValues Contains the current values after call

Error Error messages

Description:
The ReadAnalogDirect function block allows direct
reading of analog input channels in the PS 416 basic
unit.
The data is not read from the inputs at the start of
the cycle but directly during the current cycle. This
function block therefore allows a fast and direct
response to events such as required in alarm
routines. The maximum on/off delay of the analog
cards for the controller should be taken into account
when using this function block.
06/99 AWB 2700-1306 GB

395
 Function Blocks

The Slot input specifies the slot in which the card to

be read is fitted.
The WordMask input specifies which channels are to
be read on the card. The bit position determines the
channel:
Bit 0: channel 0
Bit 1: channel 1, etc.
This therefore enables you to specify which channels
are to be read.
The AnalogInValues input is used to save the read
values in the array. Only the values for the channels
specified in Wordmask are updated.
The Error output specifies the error code:
0 No error
1 Invalid slot
2 No PS 416-AIO-400 or PS 416-AIN-400 present
on the slot
3 Incorrect channel number requested via mask

06/99 AWB 2700-1306 GB

396
 ReadAnalogDirect

Example “Read analog data direct”

PROGRAM ReadAnalog
VAR
ReadAnalog : ReadAnalogDirect;
AnalogData : ARRAY[0..7] OF UINT;
ReadError : UINT;
END_VAR
CAL ReadAnalog(Slot := 11, (* Card in Slot 11 *)
Wordmask := 16#5, (* Read channel no.0 and no.2 *)
AnalogInValues := AnalogData
|
ReadError = Error )
LD ReadError
EQ 0
JMPCN READ_ERROR
LD AnalogData[0] (* Read data Channel no.0 *)
LD Analogdata[2] (* Read data Channel no.2 *)
JMP Read_DONE
READ_ERROR: (* Troubleshooting *)
READ_DONE: (* Further parts of user program *)
END_PROGRAM
06/99 AWB 2700-1306 GB

397
 Function Blocks

PS 416 ReadCounterDirect
Direct Reading of Counter Inputs

Prototype of function block

Meaning of operands
Slot Slot for a counter card in the basic unit

WordMask Bit mask specifying which channels are to be read

CountValues Contains the current values after the call for the
channel required

Error Error messages

Description:
The ReadCounterDirect function block allows direct
reading of the counter channels in the basic unit of
the PS 416.
The data is not read from the inputs at the start of the
cycle but directly during the current cycle. This
function block therefore allows a fast and direct
response to events such as required in alarm
routines. The maximum on/off delay of the analog
cards for the controller should be taken into account
when using this function block.
The Slot input specifies the slot in which the PS 416
06/99 AWB 2700-1306 GB

CNT-200 card to be read is fitted.

398
 ReadCounterDirect

The WordMask input specifies which channels are to

be read on the card. The bit position determines the
channel:
Bit 0 – channel 0
Bit 1 – channel 1
Bit 2 – ...
This therefore enables you to specify which channels
are to be read.
The read values are saved via the CountValue input.
Only the channel values selected via WordMask are
updated in the field.
The Error output specifies the error code:
0 No error
1 Invalid slot
2 No PS 4-300-CNT-200 present on the slot
3 Incorrect channel number requested via mask
06/99 AWB 2700-1306 GB

399
 Function Blocks

Example “Read counter data direct”

PROGRAM ReadCounter
VAR
ReadCounter: ReadCounterDirect;
CounterData: ARRAY[0..5] OF UINT;
ReadError: UINT;
END_VAR
CAL ReadCounter(Slot := 7, (* Card in Slot 7 *)
Wordmask := 16#4, (* Read channel no. 2 *)
CountValues := CounterData
|
ReadError = Error )
LD ReadError
EQ 0
JMPCN READ_ERROR
LD CounterData[2] (* Read data channel no.2*)
JMP Read_DONE
READ_ERROR: (* Troubleshooting *)
READ_DONE: (* Further parts of user program *))
END_PROGRAM

06/99 AWB 2700-1306 GB

400
 ReadDirect

PS 416 ReadDirect
Direct Reading of Digital Inputs

Prototype of function block

Meaning of operands
Mode Access mode

StartAddress Byte or word address of the digital input;

permissible value range:
for bit/byte access: 0 – 127,
for word access: 0 – 126

BitPosition Bit position for bit access

permissible value range: 0 – 7

ReadData Data which is read

Error Error message

Description:
The ReadDirect function block allows direct read
access to digital input cards in the basic rack of the
PS 416. The data is read directly from the inputs
during the user program cycle rather than at the start
of the cycle. This function block can thus be used for
fast and direct reactions to events, e. g. in alarm
routines. When using this function block, observe the
maximum on/off delay of the digital I/O cards for the
06/99 AWB 2700-1306 GB

PS 416 system.

401
 Function Blocks

The Mode input defines the access type:

1 Read a single bit from an input card
2 Read a byte (8 bit) from an input card
3 Read a word (16 bit) from an input card.
The Address and BitPosition inputs address an input
and are dependent on Mode. BitPosition is only
relevant for Mode = 1. Examples (depending on
access type):
Mode = 1 “StartAddress” = 4, “BitPosition” := 6
=> %I0.0.0.4.6,
Mode = 2 “StartAddress” = 2 => %IB0.0.0.2,
Mode = 3 “StartAddress” = 126 => %IW0.0.0.126.
The ReadData output contains the data value read
from the input card. Before the output value is
processed it may be necessary to carry out a type
conversion with WORD_TO_xxx. However, direct
access to individual bits of ReadData is also
possible. Depending on the Mode the following bits
are relevant:
Mode = 1 ReadData.0
Mode = 2 ReadData.0 to ReadData.7
Mode = 3 ReadData.0 to ReadData.15

Input variables declared in the main program

cannot be used directly for the ReadData output
since input variables can only be read whereas
outputs of function blocks can only be written.
06/99 AWB 2700-1306 GB

402
 ReadDirect

Error codes at the Error output:

0 No error, ReadData valid
1 Value of Mode input invalid
2 Value of StartAddress input is too large.
3 Value of StartAddress input not an even number
(only Mode = 3)
4 Value of BitPosition input invalid
Example: Directly reading a block input
PROGRAM ReadIO
VAR
ReadEnable AT%I0.0.0.0.0 : BOOL;
ReadIODirect : ReadDirect;
ReadData : WORD;
ReadError : UINT;
IOPoint5_3 : BOOL;
END_VAR
(* Direct read access to the digital
I/O. I/O byte 5, Bit 3 is
read.This corresponds to the variable
declaration %I0.0.0.5.3 :BOOL;*)
LD ReadEnable
CALC ReadIODirect(Mode := 1, (* Bit access *)
StartAddress := 5, (* Byte address 5 *)
BitPosition := 3 (* Bit position 3 *)
|
ReadData := ReadData,
ReadError := Error)
LD ReadError
EQ 0
JMPCN READ_ERROR
LD ReadData.0
ST IOPoint5_3
JMP READ_DONE
READ_ERROR:
(* Error handling *)
READ_DONE:
(* Further parts of the program *)
END_PROGRAM
06/99 AWB 2700-1306 GB

403
 Function Blocks

ReadMC
Read Data from Memory Card

Prototype of function block

Meaning of operands
DestinationAddress Buffer for data to be read
Strobe Start transfer
SegmentNumber Source segment number (0 – n)
DataLength Number of data bytes of type USINT to be read
Active Data read operation active
MaxSegmentNumber Highest possible segment number in the file
Error Error code

Description
The ReadMC function block allows data to be read
from the PLC's memory card (MC). Together with the
WriteMC function block, important applications of
this function block are data backup, process data
acquisition, saving recipe data and / or saving
variables before a program update.

Only insert or remove the memory card when the

PLC power supply is off.

The memory card is addressed by segment number.

06/99 AWB 2700-1306 GB

The function block can read up to 128 bytes from the

memory card.

404
 ReadMC

To determine the MC file size, call the function block

with DataLength set to “0”. This does not read from
the memory card. MaxSegmentNumber then
indicates the highest segment number in the MC file.
The function block is executed asynchronously in
relation to the user program cycle and can take
several program cycles. The Active output is set to
“1” during this time. Error-free completion of the
function block is indicated by the Active output
changing to 0 and by 0 at the Error output.
You can activate several function block instances
simultaneously. They will be processed one after the
other in the order that they were called.
Error codes at the Error output:
0 Function block execution completed without
errors.
1 No memory card inserted
4 SegmentNumber exceeds the value of
MaxSegmentNumber
5 DataLength is larger than 128 bytes or
Destination Address is the wrong size.
6 Start address is invalid
Error codes with PS 4-200 only:
2 No access possible due to an online connection
3 No access possible since memory card is
currently being accessed by WriteMC
7 No access possible since MC is currently being
used as a source memory.
Error code with PS 4-300 only
8 The MC was formatted without recipe data range
Error codes with PS 416 only:
06/99 AWB 2700-1306 GB

10 Memory card is not of type SRAM.

11 Memory card is not formatted.
12 Memory card is read only.

405
 Function Blocks

13 Not enough free memory in the memory card to

generate the file RSDAT.DAT.
14 The file RSDAT.DAT does not have the required
minimum size of 128 bytes.
15 Internal error during execution of the function
block
The following information applies to the block
ReadMC only in conjunction with the PS 416
controller:
The following information applies to the block
ReadMC only in conjunction with the PS 416
controller:
The data is saved on the memory card in the
MS-DOS file “RSDAT.DAT” and can be read and
processed with a PCMCIA drive.The file is subdivid-
ed into 128 byte segments and its size is only limited
by the capacity of the memory card used.
If a memory card is inserted and the file
“RSDAT.DAT” is not present on the memory card
when the function block is first called, it is created
automatically with a default size of 512 x 128 byte
(64 KByte). All sectors are initialised with the value
“0xFF”. Other file sizes can be created with the
SetMCFileLength function block.
Only for PS 4-200
The ACTIVE active output of these function blocks is
always “0” when used in PS 4-200 and PS 4-150
controllers. The current function block status can be
scanned via the Error output when the function
blocks are called again. If the Error output is “0”,
processing was carried out error-free. If the output is
“3”, the function block is processing.
06/99 AWB 2700-1306 GB

To refresh the Error output of this function block a

new edge on the Strobe input must be generated.
Otherwise the error message will be kept (with 1 on
Strobe) or will be set to 0 (with 0 on Strobe).

406
 ReadMC

Example: Reading data from memory card

PROGRAM RELOAD
VAR
StrobeReload AT %I0.0.0.0.0 :BOOL;
ActiveReload AT %Q0.0.0.0.0 :BOOL;
ErrorReload : USINT;
FBReloadData : ReadMC;
SegmentNumb : UINT;
DataLength : USINT;
LastSegmentNumber : UINT;
DataArea : ARRAY[0..15] of USINT;
END_VAR
LD 8
ST SegmentNumber
LD 16
ST DataLength
(* Read 16 bytes from segment 8
into the array DataArea *)
CAL FBReloadData(Strobe := StrobeReload,
SegmentNumber := SegmentNumb,
DataLength := DataLength,
DestinationAddress := DataArea
|
ActiveReload := Active,
LastSegmentNumber := MaxSegmentNumber,
ErrorReload := Error)
LD ActiveReload
JMPC CONTINUE
LD ErrorReload
EQ 0
JMPCN ERRORHANDLING
(* Continue processing read data *)
JMP CONTINUE
ERRORHANDLING:
(* Error handling *)
CONTINUE:
(* Further parts of user program *)
END_PROGRAM
06/99 AWB 2700-1306 GB

407
 Function Blocks

PS 4-300 Real_To_IEEE
PS 416 Conversion of numbers of data type REAL into
IEEE 754 standard format

Real_To_IEEE

REAL Real_In EXPO_Out BYTE

Mant_2_Out BYTE
Mant_1_Out BYTE
Mant_0_Out BYTE

Prototype of function block

Meaning of operands
Real_In Real number to be converted
EXPO_Out IEEE floating-point number: exponent (inc. sign)
Mant_2_Out IEEE floating-point number: mantissa byte 2
(inc. 1 bit exponent)
Mant_1_Out IEEE floating-point number: mantissa byte 1
Mant_0_Out IEEE floating-point number: mantissa byte 0

Description
The function block Real_To_IEEE converts a number
of data type REAL into an IEEE floating-point
number.
To represent the floating-point number, four bytes
(32 bit) are needed. The format used conforms to the
IEEE 754 standard format (32 bit):

EXPO_Out Mant_2_Out Mant_1_Out Mant_0_Out

The IEEE format is mostly used for the transfer of

floating-point numbers to other systems (e.g. via
06/99 AWB 2700-1306 GB

PROFIBUS).

408
 RealTimeClock

RealTimeClock
Compare With Real-Time Clock

Prototype of function block

Meaning of operands
Set Enable signal for comparing the time of the PLCs
real-time clock with the input values

RealTime Time (hours, minutes) that is compared with the PLCs

real-time clock. This is a constant that is entered
during programming and is not changed while the
program is running.

WeekDay Weekday that is compared with the PLCs real-time

clock. This is a constant that is entered during
programming and is not changed while the program
is running.
“DAY_OF_WEEK” is a Moeller data type that is
defined as follows:
TYPE DAY_OF_WEEK:
( Sunday,
Monday,
Tuesday.
Wednesday,
Thursday,
06/99 AWB 2700-1306 GB

Friday,
Saturday ) := Monday;
END_TYPE

409
 Function Blocks

RealDate Date (day and month) that is compared with the PLCs
real-time clock. This is a constant that is entered
during programming and is not changed while the
program is running.

VariableDate Specified day and month as variable comparison

value for comparison with the status of the real-time
clock. The day is entered as a binary value in the high
byte, the month in the low byte.

VariableTime Variable time for comparing with the status of the

real-time clock. The hours are entered as a binary
value in the high byte, the minutes in the low byte.

Greater Status 1: the entered comparison value is greater

than the status of the real-time clock.

Equal Status 1: the entered comparison value is the same

as the status of the real-time clock.

Less Status 1: the entered comparison value is less than

the status of the real-time clock.

Error Status 1: the values entered are impermissible

Description
The function block compares the current status of
the real time clock with the specified values “tREF”,
that are entered via input operands. Two different
types of comparison are possible.
06/99 AWB 2700-1306 GB

410
 RealTimeClock

Example 1:

The function block compares the status of the

running real-time clock with the values of the
constants Time and WeekDay and outputs the
signal Greater, Equal or Less accordingly. This
comparison is only possible if the Set operand
is 1 and the operands VariableDate and
VariableTime were not set when the function
block was invoked.
06/99 AWB 2700-1306 GB

411
 Function Blocks

Example 2:

While the Set operand is 1, the function block

compares the status of the running real-time
clock with the variable values of the operand
VariableDate and / or VariableTime and outputs
the Greater, Equal or Less signal accordingly.
The change from Greater to Less is carried out
according to the input operands entered:
with VariableTime operands this is at 24 hours,
with VariableDate operand this is on the last day
of the month at 24 hours,
with VariableTime and VariableDate operand at
24 hours at the end of the year.
The function block is enabled by setting the Set input
to 1. If Set is 0, the comparison is disabled and all
outputs are set to 0.
06/99 AWB 2700-1306 GB

412
 RealTimeClock

Example: Time comparison

PROGRAM clock

VAR
Time : RealTimeClock;
Clock_free : BOOL;
Time : TIME_OF_DAY := TOD#12:00:00;
Date : DATE := D#1996-12-12;
Midday AT %Q0.0.0.0.0 : BOOL;
END_VAR

.
.
CAL Time(Set := Clock_free,
RealTime := Time,
RealDate := Date
WeekDay := Monday)
LD Time.Equal
ST Midday

END_PROGRAM
06/99 AWB 2700-1306 GB

413
 Function Blocks

PS 4-200 ReloadData
PS 4-300 Read Data From Memory Card

Prototype of function block

Meaning of operands
Strobe Start transfer

SegmentNumber Segment number (0 – n)

DataLength Number of data bytes of type USINT to be read,

range of values: 1 – 128

DestinationAddress Start address of the marker area in which the

ADDRESS-type data should be stored

Active Reload active

MaxSegmentNumber Maximum possible number of segments in file

Error Error messages

Description
The ReloadData function block is used to read data
from the PLC's memory card and store it in a marker
area in the PLC memory.
The memory card is logically divided into 512
segments of 128 bytes each. The function block can
read up to 128 bytes with one invocation.
An important application of this function block is to
06/99 AWB 2700-1306 GB

save the retentive marker area (the recipe range that

was specified in the compiler configuration during
code generation) with SaveData and to read it back
again after changing the device configuration.

414
 ReloadData

The Error output indicates the following error code:

1 No memory module present
2 No access possible due to online connection
3 No access possible due to simultaneous access
via SaveData function block
4 Invalid segment number (permissible: 0 – 511)
5 Invalid data length (valid range for Data
Length: 1 – 128)
6 DestinationAddress invalid
Error code with PS 4-200 only
7 No access possible. MC is used as a source.
Error code with PS 4-300 only
8 The MC was formatted without recipe data range
Only for PS 4-200
The ACTIVE active output of these function blocks is
always “0” when used in PS 4-200 and PS 4-150
controllers. The current function block status can be
scanned via the Error output when the function
blocks are called again. If the Error output is “0”,
processing was carried out error-free. If the output is
“3”, the function block is processing.
To refresh the Error output of this function block a
new edge on the Strobe input must be generated.
Otherwise the error message will be kept (with 1 on
Strobe) or will be set to 0 (with 0 on Strobe).

The SaveData function block allows data to be

written to the memory card.
06/99 AWB 2700-1306 GB

415
 Function Blocks

Example: Read data from memory card

PROGRAM R_Card
VAR
ReadData : ReloadData;
Start AT %I0.0.0.0.2 : BOOL;
Mem_start AT %MB0.0.0.100 : BYTE;
Segment_NR : UINT;
DataLength1 : USINT;
ErrorMessage : USINT;
END_VAR
CAL ReadData(Strobe := Start,
DestinationAddress := &Mem_start,
SegmentNumber := Segment_NR,
DataLength := DataLength1)

LD ReadData.Error
ST ErrorMessage
NE 0 (*If content not equal to 0, then error *)
JMPC ErrorEvaluation
.
.
ErrorEvaluation:
.
.
END_PROGRAM

06/99 AWB 2700-1306 GB

416
 RS

RS
Flip Flop With Reset Dominant

Prototype of function block

Meaning of operands
SET Set condition

RESET1 Reset condition

Q1 Output state of the bistable element

Description
The characteristic feature of the “RS” function block
is to statically set a data element – the output “Q1” –
to the Boolean status “1” or “0”. Switching between
the two states is controlled by the Boolean input
operands “SET1” and “RESET1”.
The output “Q1” is initialised with the value “0” when
starting the process. The first processing of the
function block with the value “1” of the operand
“SET” causes the output “Q1” to be set to “1”.
A change of the value of “SET” no longer then effects
the output “Q1”. The value “1” of the input operand
“RESET1” sets the output “Q1” to “0” – the output is
reset.
If both input operands have the value “1”, the fulfilled
set condition is dominant, i. e. Q1 is reset with
priority.
06/99 AWB 2700-1306 GB

417
 Function Blocks

Example: Fill and close valve again

PROGRAM fill

VAR
Valve1 : RS;
Position AT %I0.0.0.0.0 : BOOL;
Barrel_Full AT %I0.0.0.0.1 : BOOL;
Halt AT %I0.0.0.0.2 : BOOL;
Valve1_Shut : BOOL;
Valve1_Open_Shut AT %Q0.0.0.0.3 : BOOL;
END_VAR

LD Barrel_Full
OR Halt
ST Valve1_Shut
CAL Valve1(SET := Position,
RESET1 := Valve1_Shut)
LD Valve1.Q1
ST Valve1_Open_Shut

END_PROGRAM

06/99 AWB 2700-1306 GB

418
 RTC

RTC
Set Real-Time Clock

Prototype of function block

Meaning of operands
EN Set condition

PDT Manipulated value for the real-time clock, valid

years from 1993 to 2092

Q Indication whether valid value at “CDT”

CDT Current date and time value

Description
The manipulated value Date and Time specified with
the operand PDT is transferred to the real-time clock
with the rising edge of the operand EN. The output
operand “Q” indicates the validity of CDT.
The current clock state is output via the operand CDT
independent of the state of “EN”.
06/99 AWB 2700-1306 GB

419
 Function Blocks

Example: Setting the real-time clock

PROGRAM clock

VAR
Set_Clock : RTC;
Set_Input AT %I0.0.0.0.0 : BOOL;
Date_and_Time: DATE_AND_TIME := DT#1995-01-
01-00:00:00;
Clock_Set : BOOL;
Clock_Status : DATE_AND_TIME;
END_VAR

CAL Set_Clock (EN := Set_Input,

PDT := Date_and Time)
LD Set_Clock .Q
ST Clock_Set
LD Set_Clock .CDT
ST Clock_Status

END_PROGRAM

06/99 AWB 2700-1306 GB

420
 S_TimeFalling

S_TimeFalling
Off-Delay Timer, Seconds

Prototype of function block

Meaning of operands
Set Start condition, rising edge

ReSet Reset condition

Hold Time interruption

PresetTime Time setpoint in seconds

OutputControl Control output

ElapsedTime Actual time value in seconds

06/99 AWB 2700-1306 GB

421
 Function Blocks

Description

Time diagram

A rising edge on the Set input transfers the

PresetTime value as delay time T in seconds to the
timer and starts the time. The OutputControl output
is set to 1. The time is started when the Set input is
reset to 0. The OutputControl output is reset to 0
once the delay time has elapsed, i. e. it returns to “0”
(1). The ElapsedTime output shows the current time
value in seconds. If the status 0 at the Set input is
shorter than T, the OutputControl output stays at 1.
Elapsing of the delay time can be stopped by setting
the Hold input to 1. The held delay time then
continues to run when the Hold input is reset to 0.
The off-delay time is therefore lengthened by the
duration of the Hold signal, i. e. T+THALT (2).
If the Hold input is 1 when the rising edge occurs
on the Set input, the start of the time delay will be
delayed further by the duration of the 1 signal on the
Hold input. The OutputControl (4) output also has the
06/99 AWB 2700-1306 GB

delayed status 1.

422
 S_TimeFalling

If the status on the Set input changes from 1 to 0

while the Hold input is 1, the time is started when
Hold is reset to 0. The off-delay time is thus
increased by the duration of the Hold signal, i. e.
T+THALT (3).
The timer is reset when the ReSet input is 1. A rising
edge on the Set input is only recognised as a start
when the ReSet has changed from 1 to 0.
Example: 32 seconds off-delay
PROGRAM time2

VAR
Timer2 : S_TimeFalling;
Start AT %I0.0.0.0.0 : BOOL;
Halt AT %I0.0.0.0.1 : BOOL;
TimeValue2 : UINT:= 32;
(* TimeValue2 = 32 seconds *)
Output2 AT %Q0.0.0.0.0 : BOOL;
ActTime2 AT %QW0.0.0.2 : UINT;
END_VAR

CAL Timer2(Set := Start,

Hold := Halt,
PresetTime := TimeValue2)
LD Timer2.OutputControl
ST Output2
LD Timer2.ElapsedTime
ST ActTime2

END_PROGRAM
06/99 AWB 2700-1306 GB

423
 Function Blocks

S_TimeRising
On-Delay Timer, Seconds

Prototype of function block

Meaning of operands
Set Start condition, rising edge

ReSet Reset condition

Hold Time interruption

PresetTime Time setpoint in seconds

OutputControl Control output

ElapsedTime Actual time value in seconds

06/99 AWB 2700-1306 GB

424
 S_TimeRising

Description

Time diagram

A rising edge on the Set input transfers the

PresetTime value as delay time T in seconds to the
timer and starts the time. The OutputControl output
switches to 1 after the delay time has elapsed and
keeps this status until the Set input is reset to 0 (1).
The ElapsedTime output shows the current time
value in seconds. If the status 1 at the Set input is
shorter than T, the OutputControl output stays at 0.
Elapsing of the delay time can be stopped by setting
the Hold input to 1. The held delay time then
continues to run when the Hold input is reset to 0.
The on-delay time is therefore lengthened by the
duration of the Hold signal, i. e. T+THOLD (2).
06/99 AWB 2700-1306 GB

425
 Function Blocks

If the Hold input is 1 when the rising edge occurs

on the Set input, the start of the time delay will be
delayed further by the duration of the 1 signal on the
Hold input (4. If the Set input is reset from 1 to 0 after
the time has elapsed, and while the Hold input is set
to 1, the OutputControl output returns to 0 when the
Hold input is reset to 0 (3).
The timer is reset when the ReSet input is 1. The time
cannot be started when the ReSet input is 1. A rising
edge on the Set input is only recognised as a start
when the ReSet has changed from 1 to 0 (5).
Example: 12 seconds on-delay
PROGRAM time1

VAR
Timer1 : S_TimeRising;
Start AT %I0.0.0.0.0 : BOOL;
Halt AT %I0.0.0.0.1 : BOOL;
TimeValue1 : UINT := 12;
(* TimeValue1 = 12 seconds *)
Output1 AT %Q0.0.0.0.0 : BOOL;
END_VAR

CAL Timer1(Set := Start,

Hold := Halt,
PresetTime := TimeValue1)
LD Timer1.OutputControl
ST Output1

END_PROGRAM
06/99 AWB 2700-1306 GB

426
 SaveData

PS 4-200 SaveData
PS 4-300 Save Data on Memory Card

Prototype of function block

Meaning of operands
Strobe Start save operation
SegmentNumber Segment number (0 – n)
DataLength Number of data bytes of type USINT to be stored,
range of values: 1 – 128
SourceAddress Start address of the data area to be saved
Active Data save operation active
MaxSegmentNumber Highest segment number in the file
Error Error code

Description
The SaveData function block allows data to be saved
to the PLC's memory card. The memory card is
logically divided into 512 segments of 128 bytes
each. The function block can transfer up to 128 bytes
to the memory card.
An important application of this function block is to
save the retentive marker area (the recipe range that
was specified in the compiler configuration during
code generation) and to read it back again with
06/99 AWB 2700-1306 GB

ReloadData after changing the device configuration.

427
 Function Blocks

The Error output indicates the following error codes:

1 No memory module present
2 No access possible due to online connection
3 No access possible due to simultaneous access
via ReloadData function block
4 Invalid segment number (valid range
for PS 4-200: 0 – 511, for PS 4-300: depending
on memory card fitted 0 – 1023)
5 Invalid data length (valid range for Data
Length: 1 – 128)
6 SourceAddress invalid
Error code with PS 4-200 only
7 no access possible. MC is used as a source
Error code with PS 4-300 only
8 The MC was formatted without recipe data range
Only for PS 4-200
The ACTIVE active output of these function blocks is
always “0” when used in PS 4-200 and PS 4-150
controllers. The current function block status can be
scanned via the Error output when the function
blocks are called again. If the Error output is “0”,
processing was carried out error-free. If the output is
“3”, the function block is processing.
To refresh the Error output of this function block a
new edge on the Strobe input must be generated.
Otherwise the error message will be kept (with 1 on
Strobe) or will be set to 0 (with 0 on Strobe).

The ReloadData function block allows data to be

read back from the memory card.
06/99 AWB 2700-1306 GB

428
 SaveData

Example: Writing data to the memory card

PROGRAM S_Card

VAR
SendData : SaveData;
Start AT %I0.0.0.0.2 : BOOL;
Mem_start AT %MB0.0.0.100 : BYTE;
Segment_NR : UINT;
DataLength : USINT;
ErrorMessage : USINT;
END_VAR

CAL SendData(Strobe := Start,

SourceAddress := &Mem_start,
SegmentNumber := Segment_NR,
DataLength := DataLength)

LD SendData.Error
ST ErrorMessage
NE 0 (*If content not equal then error*)
JMPC ErrorEvaluation
.
.
ErrorEvaluation:
.
.

END_PROGRAM
06/99 AWB 2700-1306 GB

429
 Function Blocks

PS 4-200 SCO
PS 4-300 Serial Communication Function Block:

SCO

BOOL Strobe
USINT Command Busy BOOL
USINT CardAddress ElementNumber USINT
ADDRESS MemoryAddress Error USINT
USINT DataSize
tBaudrate Baudrate**
tSTOPBIT StopBits*
tPARITY Parity*

Prototype of function block

Meaning of operands
Strobe Initiate job (rising edge)
Command Job type
CardAddress Interface selection (0 = RS 232, 1 = RS 485)
MemoryAddress Start address of send or receive range
DataSize Size of send or receive data
Busy Function block status
ElementNumber Number of data bytes sent/received
Error Error messages
Baudrate* Transfer speed,
Default: 9600 Baud
StopBit Number of stopbits, Default: 1
Parity Transmission parity, Default: without
06/99 AWB 2700-1306 GB

430
 SCO

Description
The SCO function block allows transparent
communication between the user program and the
connected data terminals via the RS 232 and RS 485
interfaces of the PLC.
The function block can control send operations and
(non-simultaneously) receive operations. Since the
transfer is executed in half-duplex mode,
simultaneous sending and receiving is not possible.
A send job has priority over a receive job.
The SCO function block must be called twice for
communication using both the RS 232 and RS 485
interfaces simultaneously: once for operating the
RS 232 interface and once for operating the RS 485
interface. For ease of operation it is advisable to
create a separate function block instance for each
interface.
There are no retentive settings for the function block.
No CTS/RTS handshake lines are used.
The Strobe input is edge-triggered. A change from 0
to 1 or from FALSE to TRUE starts the job specified
via the Command input. All input parameters of the
function block are saved with the Strobe signal.
If the Strobe input triggers a send job or readiness to
receive, this is indicated at the Busy output by a 1.
The Busy output shows the active status of the
function block. Readiness to receive can be stopped
with a falling edge on the Strobe input.
The response of the SCO function block to a
communication abort depends on the interface used.
06/99 AWB 2700-1306 GB

When using the RS 485 interface the data received

so far is kept in the receive buffer and is made
available.
When using the RS 232 interface the data in the

431
 Function Blocks

receive buffer is not refreshed until reception

(defined by the entry on the DataSize input) has been
completed. No current data bytes are made available
in the receive buffer if reception is aborted.
The mode of the SCO function block is set at the
Command input. The mode set does not become
active until a rising edge is sent to the Strobe input.
1. Send job
The RS 232 or RS 485 interface is first of all initialised
and then the send job is executed.
2:Readiness to receive with receive buffer reset
The RS232 or RS485 interface is first initialised. The
receive buffer is cleared and is available in the size
specified at the DataSize input. The number of data
bytes to be received is indicated at the
ElementNumber output. If the receive buffer is full,
the Busy output is reset to 0.
A new edge at the Strobe input clears the already
received data.
3: Readiness to recive without receive buffer reset

When using the RS 232 on the PS 4-300, this

function corresponds to mode 2.

06/99 AWB 2700-1306 GB

432
 SCO

Mode 3 can be used if the connection via mode 1 or

2 has been established since only in these two
SUCOM modes is it possible to switch to serial
communication via the SCO.
The number of received data bytes is indicated at the
ElementNumber output.
The receive buffer is not reset in this mode. If the data
of a previous job is present in the receive buffer, new
receive data will only be written to the unoccupied
buffer space. If the receive buffer is full, the Busy
output switches to 0".
4: Deactivation of serial communication via SCO
(SUCOM is activated).

The PS 4-200 switches automatically to SUCOM

operation if more than 63 data bytes were
received via RS 232. This changeover does not
happen with the PS 4-300.

The CardAddress input is used to select the

interface required for communication:
0: RS 232
1: RS 485
The MemoryAddress input defines the start address
of the send or receive range. The receive data is
entered directly in the specified range. Ranges
%MB, %SDB and %RDB with a one-byte data width
can be used.
06/99 AWB 2700-1306 GB

433
 Function Blocks

The DataSize input defines the necessary size of the

receive buffer and the number of data bytes to be
sent.
The following values can be set:
Interface RS2321 to 63
Interface RS4851 to 127
The Busy output indicates the status of the SCO
function block:
0 = Function block inactive
1 = Function block active.
The active status of a function block is indicated via
Busy=1 if a send job or readiness to receive have
been started. The Busy output switches to 0 as soon
as the send job has been completed or when the
receive buffer is full.
The ElementNumber output indicates the number of
data bytes already received.
PS 4-300:
When using the RS 232 interface, the number of
received data bytes is indicated as soon has the
number selected at the DataSize input has been
reached.
With a send job the number of sent data bytes is
indicated (only with RS 232 and RS 485).
06/99 AWB 2700-1306 GB

434
 SCO

The Error output indicates the following error codes:

0: No error
1:Command input incorrectly set. Valid
parameters from 1 to 4
2: CardAddress input is incorrectly set. Valid
parameters are 0 (RS232) and 1 (RS485)
3: Conflict due to SUCOM or Suconet operation
Possible causes:
With RS232: SUCOM protocol currently active
With RS485: incorrect parameters in Topology
Configurator
4: Marker address (MemoryAddress) is too big. The
marker range used must be within marker range
defined for the CPU (configuration in menu
Options -> Compiler" of the Sucosoft S4 Program
Code Generation function).
5: "DataSize" parameters incorrect. The following
values can be set:
Interface RS2321 to 63
Interface RS4851 to 127
6: "MemoryAddress" parameters incorrect. The
combination of "MemoryAddress" and
"DataSize" violates the active marker area
specified in the configuration for the PLC.
Example: active marker area: 120
MemoryAddress (100) + DataSize (40) = 140 =>
too big
7: Overflow of receive buffer. More than 63 or 127
bytes were received.
8: Parity error RS485: interface parameters of
sender and receiver do not match.
9: A send and receive job were started
simultaneously via this interface.
06/99 AWB 2700-1306 GB

435
 Function Blocks

Interface settings
The RS 232 and RS485 interfaces are available for
operating the SCO function block.
The RS 232 interface parameters for the PS 4-300
are set via the SCO inputs tBaudrate, tStopBits and
tParity.
PS 4-200 communication via the RS232 interface is
done with the fixed transfer parameters: baud rate
9600 Baud, 8 Data bit, 1 Stop bit without parity
check. Up to 63 bytes can be transferred..
The RS 485 interface is assigned with parameters via
the Sucosoft S 40 Topology Configurator. For this
choose Edit->Parameters, select Transparent mode
and click the Interface Parameters button. The
permissible data volume that can be transferred is
between one and 127 bytes.
Impermissible combinations are detected by the
software and are not accepted.
The application of the SCO function block will be
demonstrated in the following example.
Communication PLC <-> Terminal
Data communication between a PLC and a
terminal
06/99 AWB 2700-1306 GB

436
 SCO

Example "Communication PLC -> Terminal", SCO

Data communication between a PLC and a PC with
a terminal emulation program or a terminal.

Requirements for the following example:

Hardware: PLC, e.g. PS4-201-MM1 from version 04
or PS 4-341-MM1
Digital simulator ZB4-108-ES1
Cable ZB4-303-KB1
with RS 485 communication:
UM1.5 interface converter,
NG31 power supply unit
for the interface converter,
KPC-PS306 adapter cable
Software: Sucosoft S 40 from version 4.0
Terminal emulation program
The interface parameters of the terminal are set
accordingly in the terminal emulation program.
06/99 AWB 2700-1306 GB

437
 Function Blocks

Function
The data exchange between the controller and the
terminal is carried out via the program SCO_BSP1.
Send
Input %I0.0.0.0.3 is used to set the required
interface. Set 1 for the RS 485 interface.
Input %I0.0.0.0.4 is used to select between text 1
and text 2:
%I0.0.0.0.4 = 1On condition 1 fulfilled
%I0.0.0.0.4 = 0Limit switch 2 reached.
The bytes to be sent are located in the memory from
marker byte 200. The address of this marker byte is
automatically sent to the MemoryAddress input.
The DataSize input is automatically set according to
the text selected.
The Command input is automatically set to mode 1
(send).
A rising edge at input %I0.0.0.0.0 sends the text to
the terminal.

06/99 AWB 2700-1306 GB

438
 SCO

Receive
For receive operations use the same interface
settings as for send operations.

The Command input is automatically set to mode 2

(receive).
In order for the function block to copy the receive
data to the marker range from address
%MB0.0.0.400, the start address is automatically
sent to the MemoryAddress input.
The number of bytes to be received (=size of receive
buffer) is automatically entered at the DataSize input.
%I0.0.0.0.1 switches the SCO to receive mode, and
the Busy output shows 1 to indicate that the function
block is active.
The ElementNumber output shows the number of
bytes already received. If the receive buffer is
completely full with data (Element-Number =
DataSize), Busy switches to 0. If %I0.0.0.0.1 is
triggered again, the function block is ready to receive
again. The clearing of the receive buffer is indicated
by 0 at the ElementNumber output.
In this example program one instance of the SCO
was used for sending and for receiving. Multiple
instancing would not save time since the PLC only
works in half-duplex mode.

Multiple instancing of the SCO function blocks

will cause a communication malfunction
06/99 AWB 2700-1306 GB

Switching to SUCOM mode

Input %I0.0.0.0.2 (in the example Switch _Strobe)
enables you to switch to SUCOM mode after SCO
communication via the RS 232 interface.

439
 Function Blocks

The Command input is automatically set to mode 4

(disconnect serial communication).
A rising edge on input %I0.0.0.0.2 triggers the
changeover..

.To run the example via both the RS 232 interface

(using the interface converter) and the RS 485
interface, set the PLC in the Sucosoft S40
Topology Configurator to Transparent mode and
then change the interface via input I0.0.0.0.3 (in
example PRG_SBI).

06/99 AWB 2700-1306 GB

440
 SCO

PROGRAM SCO_BSP1

VAR
(* Directly represented variables *)
Send_Strobe : BOOL AT %I0.0.0.0.0;
Rcve_Strobe : BOOL AT %I0.0.0.0.1;
Changeover_Strobe : BOOL AT %I0.0.0.0.2;
PRG_SBI : BOOL AT %I0.0.0.0.3; (* 0 = RS232; 1 = RS485 *)
SendText_No : BOOL AT %I0.0.0.0.4; (* 0 = Text1; 1 = Text2 *)
SCO_outputs : BYTE AT %QB0.0.0.0;
(*Indication: Receive volume if Bit7=0, Error message if Bit7=1*)

Send_buffer AT%MB0.0.0.200: ARRAY[1..127] of BYTE;

Receive_buffer AT%MB0.0.0.400: ARRAY[1..127] of BYTE;

(* Local variables/intermediate markers *)

Text : STRING;
Text2 : STRING := 'Limit switch 2 reached $R$L';
(* Text variable 'Text2' is initialised here directly with Text*)

Send_active : BOOL;
Rcve_active : BOOL;
Changeover_active : BOOL;
Receive_No: USINT := 16; (* 16 Char. for example *)

(* FB instances *)
CommunicationFB : SCO; (*SCO instance for send/receive*)
Send_converter : STRtoADR;
Rcve_converter : ADRtoSTR;
END_VAR

(* General SCO setting *)

LD PRG_SBI
BOOL_TO_USINT
ST CommunicationFB.CardAddress(* RS232/RS485 *)
06/99 AWB 2700-1306 GB

LD Changeover_active
JMPCChangeover_Scan (*Changeover job in progress*)

LD Changeover_Strobe
JMPCChangeover_Job (*Changeover to Sucom mode *)

441
 Function Blocks

LD Rcve_active
JMPCRcve_Scan (* Receive job in progress *)

LD Send_active
JMPCSende_Scan (* Send job in progress *)

LD Rcve_Strobe
ANDNSend_Strobe (* Send and receive not at same time *)
JMPCRcve_Job (* Start receive job *)

LD Send_Strobe
ANDNRcve_Strobe
JMPCSend_ Job

LD 0
ST CommunicationFB.Strobe

(* Strobe reset, since no job or job end *)

JMPSCO_Call

(* *********** Processing a send job *********** *)

Send_job:
(* Text transfer at start of send job *)
LD 'On condition 1 fulfilled $R$L'(*Text variable 1*)
ST Text
LD SendText_No
JMPC TextConvert

LD Text2 (* Text variable 2 *)

ST Text

TextConvert:
CALSend_converter( Enable := 1,
TextString:= Text,
TransmitVariable:= &Send_buffer
06/99 AWB 2700-1306 GB

LD Send_converter.StrLen
UINT_TO_USINT
ST CommunicationFB.DataSize(* Parameter transfer to SCO FB*)

442
 SCO

LD 1
ST CommunicationFB.Command(* Send Mode *)
LD &Send_buffer
ST CommunicationFB.MemoryAddress
LD 1
ST CommunicationFB.Strobe (* Send*)

CAL CommunicationFB (* SCO call *)

LD CommunicationFB.Error
NE 0
JMPCCommunication_Error
LD CommunicationFB.Busy
ST Send_active

Send_Scan:
LD CommunicationFB.Busy
JMPCNSend_Mark

LD 0
ST CommunicationFB.Strobe
(* Send job in progress, complete job *)
JMPSCO_call

Send_Mark:
LD Send_Strobe
(* New send job should not be possible until after edge change *)
JMPCEnd

LD 0
ST Send_active
JMPEnd

(* ************* Processing a receive job ************ *)

Rcv_Job:
LD 0
ST SCO_outputs
06/99 AWB 2700-1306 GB

Rcv_Scan:
LD Receive_No
ST CommunicationFB.DataSize(*Receive job, 16 Char. *)
LD 2
ST CommunicationFB.Command(* Receive mode *)

443
 Function Blocks

LD &Receive_buffer
ST CommunicationFB.MemoryAddress
LD 1
ST CommunicationFB.Strobe(* Receive *)

CAL CommunicationFB (* SCO call *)

LD CommunicationFB.Error
NE 0
JMPCCommunication_Error

LD CommunicationFB.Busy
ST Rcve_active
LD CommunicationFB.ElementNumber
USINT_TO_BYTE
ST SCO_outputs

(* Example display of first 5 characters *)

ld Receive_buffer [1]
ld Receive_buffer [2]
ld Receive_buffer [3]
ld Receive_buffer [4]
ld Receive_buffer [5]

(* Strobe change ends the receive job *)

ld Rcve_Strobe
JMPCEnd

LD 0
ST CommunicationFB.Strobe
ST Rcve_active
(* Receive job in progress, Complete job *)
JMPEnd

Communication_Error:
LD CommunicationFB.Error
USINT_TO_BYTE
06/99 AWB 2700-1306 GB

OR 16#80 (* For troubleshooting, Bit7 = 1 *)

ST SCO_outputs (* Bits 0-6 indicate the error *)
LD 0
ST CommunicationFB.Strobe (* Job abort*)
JMPSCO_Call

444
 SCO

(* Processing a job for switching to Sucom mode *)

Changeover_Job:
LD 0
ST SCO_outputs
LD 4
ST CommunicationFB.Command
LD 1
ST CommunicationFB.Strobe(*Change to Sucom *)
ST Changeover_active
JMPSCO_call

Changeover_Scan:
LDN Send_Strobe
ANDN Rcve_Strobe
ANDNChangeover_Strobe
(*New send / receive job not possible until after edge change *)
JMPCNEnd

LD 0
ST Send_active
ST Rcve_active
ST Changeover_active
ST CommunicationFB.Strobe

SCO_call:
CAL CommunicationFB (* SCO call *)

End:
END_PROGRAM
06/99 AWB 2700-1306 GB

445
 Function Blocks

PS 4-300 SendATCommand
PS 416 Send AT Commands to a Modem

Prototype of function block

Meaning of operands
ATCommand AT command to send to modem (max. 254 bytes)

ResponseString Response to AT command (max. 254 bytes)

Strobe Enable function block

SlotNumber Selection of PLC interface:

0 CPU 400/300-SBI or
PS 4-341-MM1 SBI (transparent mode)
1 CPU 400/300/200-PRG (transparent mode)
4..20 Slot number of associated COM card

TimeOut Wait for response to AT command,

(range 10 ... 90 seconds,
default: 60 seconds)
06/99 AWB 2700-1306 GB

Baudrate Transmission speed, specified via “tBAUDRATE”

StopBit Number of stop bits, specified via “tSTOPBIT”

Parity Transmission parity, specified via “tPARITY”

446
 SendATCommand

Active State of job processing

1: Job accepted
1->0: Job ended

ResponseStrLen Number of received characters

ResponseOK Response in ResponseString:

1: OK or CONNECT received.
0: Neither OK nor CONNECT received

Error Error code

Description
The SendATCommand function block is used to
send AT commands to a modem which is attached to
one of the following PLC interfaces
CPU 400/300/200-PRG interface,
CPU 400/300-SBI interface or
PS 4-341-MM1-SBI/PRG interface
COM-200 interface.
To allow the PLC and modem to communicate with
each other, the interface parameters baud rate, stop
bits, parity and data bits should be set to the same
values on the PLC and the modem. Refer to your
modem manual for information on setting the
modem interface parameters.
The SendATCommand function block controls the
TxD (transmit data) and RxD (receive data) lines.
Control lines are not supported.
Before sending an AT command, you must set
parameters for the CPU PRG interface. You must
specify the baud rate, stop bits and parity with the
following data types. The number of data bits is
06/99 AWB 2700-1306 GB

always 8.

447
 Function Blocks

TYPE tBAUDRATE:
( Baud_2400,
Baud_4800,
Baud_9600,
Baud_19200,
Baud_38400,
Baud_57600 ):=Baud_9600;
END_TYPE

TYPE tSTOPBIT:
( ONE_Stop_Bit,
TWO_Stop_Bits) := ONE_Stop_Bit;
END_TYPE

TYPE tPARITY:
( NONE_Parity,
ODD_Parity,
EVEN_Parity ):=NONE_Parity;
END_TYPE

You can choose between an RS 232 or RS 485

interface with the switch on the front of the CPU 400/
300/200.
Parameters for the CPU 400/300-SBI interface and
the COM 200 interface are set in the topology
configuration as follows.
For the CPU 400/300 SBI interface, you can
configure transparent mode and the values for baud
rate, parity, stop bits and data format. Interface
defaults to RS 485.
For the COM 200 interface, you can configure baud
rate, parity, stop bits and data format and the full
duplex mode, no handshake and no start and stop
code. Interface module can be set to IFM 232.1 or
IFM 232.2.
06/99 AWB 2700-1306 GB

The SendATCommand function block can be used to

send all Hayes-compatible AT commands to a

448
 SendATCommand

modem and to receive the modem responses.

Refer to your modem manual for information on

the AT commands supported by your modem.

The AT command is specified as a string which must

start with “AT” and end with “$R$L”. “$R” is the code
for “Carriage Return” and “$L” is the code for “Line
Feed”.
Example: “ATZ $R$L” is used as the AT command to
reset the modem.
A rising edge at the Strobe input accepts all input
parameters.
If SlotNumber is “1” (CPU 400/300/200 PRG
interface), the interface parameters are set before
sending the AT command to the modem. For the
other interfaces, only the AT command is sent (the
interface parameters are already specified in the
topology configuration).
After enabling the function block, Active is set to “1”.
SIt is set back to “0” if a modem response is
received, if a parameter error is detected or if the
timeout is exceeded. The timeout is specified with
TimeOut in seconds.
Signal transitions at the Strobe input are ignored
while Active is “1”.
06/99 AWB 2700-1306 GB

449
 Function Blocks

An active send operation will be aborted on the

PS 416-COM-200 card if the Modem function block
is activated via the “TransmitActive” output of the
COM function block. This can be avoided by starting
a timer with the TransmitActive output, that causes a
delay according to the specified baud rate and the
data volume to be sent. This does not affect
Transparent mode with the central unit.
ResponseString contains the entire response string
from the modem. The length of the response string is
contained in ResponseStrLen. ResponseOK is “1” if
the modem responds with OK or a connect message.
Error codes at the Error output:
0 No error
1 ResponseString contains an unknown response
2 ResponseString incomplete or is longer than the
declared length of the ResponseString variable
3 ResponseTimeOut. For example, no response
received because:
Problem with connection to modem,
Interface parameters for the PLC and modem do
not match,
Modem not active.
4 Error when receiving data
5 Error when transmitting data
16 SlotNumber invalid (0, 1, 4...20)
17 ATCommand does not begin with “AT”
18 ATCommand does not end with “$R$L”
19 ATCommand greater than 254 characters
20 TimeOut value invalid
21 CPU 400/300-SBI/COM-200: Transparent mode
not or incorrectly set
22 COM-200: Not in specified slot
06/99 AWB 2700-1306 GB

23 COM-200: No or incorrect IFM inserted

24 CPU 400/300/200 PRG: Transparent mode
cannot be set

450
 SendATCommand

25 Modem not configured for Echo-OFF

26 CPU 400/300/200 PRG: Transmit and receive

error
The function block automatically configures the
modem as follows
– Modem result codes on,
– Modem result codes plain text on
– Modem command echo off.
Other function blocks can also be used to access
the COM or SBI interface. Conflicts can occur if
several function blocks try to access the same
interface. If necessary, the user program should
include interlocks to make sure that this cannot
happen.

Example: Switching off modem echo with ATE0

PROGRAM echo_off
VAR
FB_ECHO_OFF : SendAtCommand;
FallingEdge : F_TRIG;
FB_Strobe AT %I0.0.0.0.0 : BOOL;
ATCommand_ECHO_OFF : STRING(8) := 'ATE0$R$L';
FB_Active : BOOL;
ECHO_OFF_Response : STRING(254);
ECHO_OFF_Response_Length : USINT;
ECHO_OFF_ResponseOK AT %Q0.0.0.0.0 : BOOL;
FB_Error : UINT;
...
END_VAR
...
06/99 AWB 2700-1306 GB

451
 Function Blocks

CAL FB_ECHO_OFF(Strobe := FB_Strobe,

SlotNumber := 1,
ATCommand := ATCommand_ECHO_OFF,
ResponseString := ECHO_OFF_Response,
TimeOut := 20,
Baudrate := Baud_9600,
StopBit := ONE_Stop_Bit,
Parity := NONE_Parity
|
FB_Active := Active,
ECHO_OFF_Response_Length := ResponseStrLen,
ECHO_OFF_ResponseOK = ResponseOK,
FB_Error := Error)
CAL FallingEdge(CLK := FB_Active (* Detects falling edge *)
|
:=Q)
LD FallingEdge.Q
JMPCN AwaitAnswer
CheckAnswer: (* Falling edge on Active output *)
LD FB_Error (* Error handling *)
GT 0
JMPC Error
(* No error, modem echo switched off; modem response handling *)
...
JMP End
AwaitAnswer: (* Active is 0 or 0->1, request is being processed,
will be checked again in next cycle *)
...
JMP End
Error: (* Error handling *)
...
End:
END_PROGRAM
06/99 AWB 2700-1306 GB

452
 Serialize

Serialize
Copy Data Structure to Array

Prototype of function block

Meaning of operands
Source Source variable

Buffer Destination area

BufferOffset Offset in destination area

SourceLength Length of source variable in bytes

Error Error code

Description
The Serialize function block copies any required data
type to a destination area at a starting position
specified by “Buffer + Bufferoffset”. The data can
then be sent, for example as an array to another PLC
and then unpacked with the Deserialize function
block.
The SourceLength output specifies the length of the
source data type in bytes.
Buffer is an ARRAY OF BYTE, ARRAY OF USINT or
ARRAY OF SINT of any required size.
06/99 AWB 2700-1306 GB

453
 Function Blocks

Error codes at the Error output:

0 No error
1 Buffer overflow
2 Offset lies outside the buffer
3 Source lies within the buffer
4 SourceLength is “0”

The source data type BOOL is not supported and

will result in an error during compilation.

Due to the different memory layout techniques

available, the Serialize function will produce different
results (e.g. structures) with all PLC types.
If you wish to exchange data between different PLC
types, copy only elementary data types and arrays of
type ANY_BIT or ANY_INT. Data types BOOL,
STRING, ARRAY OF BOOL are not permissible for
this operation. They have been implemented
differently as derived types in the PLCs concerned.
The restriction does not apply if the data exchange is
between PLCs of the same type.
Example: Copying 20 bytes into a 30-byte array
PROGRAM sendstruct

VAR
serie_fb : Serialize;
struct_buffer AT %SDB1.1.0.0 :
ARRAY [1..30] OF BYTE;
CheckSumOffset : UINT := 0;
CheckSum : UINT;
DTOffset : UINT := 2;
TransDate : DT; (* Send date *)
DataOffset: UINT := 10;
TransmitData : Array [1..20] OF BYTE;
(* User data *)
06/99 AWB 2700-1306 GB

SerializedLength : UINT;
Error : USINT;
END_VAR

454
 Serialize

(* Prepare send data *)

CAL serie_fb(Source := CheckSum,
Buffer := struct_buffer,
BufferOffset := CheckSumOffset,
|
SerializedLength := SourceLength)

LD serie_fb.Error
USINT_TO_BOOL (* Any error ? *)
JMPC _Fail (* Error handling *)

CAL serie_fb(Source := TransDate,

Buffer := struct_buffer,
BufferOffset := DTOffset,
|
SerializedLength := SourceLength)

LD serie_fb.Error
USINT_TO_BOOL (* Any Error ? *)
JMPC _Fail (* Error handling *)

CAL serie_fb(Source := TransmitData,

Buffer := struct_buffer,
BufferOffset := DataOffset,
|
SerializedLength := SourceLength)
LD serie_fb.Error
USINT_TO_BOOL (* Any Error ? *)
JMPC _Fail (* Error handling *)

(* Structure complete, data can be sent *)

_Fail: (* Error handling *)

06/99 AWB 2700-1306 GB

455
 Function Blocks

PS 416 SetMCFileLength
Create and Initialise Data File

Prototype of function block

Meaning of operands
Strobe Create file RSDAT.DAT

ClearData 0 Do not initialise file contents

1 Initialise file contents with 0xFF

DeleteFile 0: Do not delete existing data file on the

Memory Card
1: Delete existing data file on the Memory Card

NumberOfSegments Number of 128 byte segments to create

Active File create operation active

Error Error code

Description:
The SetMCFileLength function block creates the file
RSDAT.DAT on an SRAM memory card (MC).
The number of 128 byte data segments is specified
with NumberOfSegments and is only limited by the
capacity of the memory card used. The following
maximum values apply if the memory card is
formatted with a PS 416:
06/99 AWB 2700-1306 GB

456
 SetMCFileLength

MC capacity 512 kB 3944 segments

MC capacity 1 MB 7944 segments
The ClearData input specifies whether the file should
be initialised with the data value “0xFF”. If the
function block is called with “ClearData” = 0, the
initial file content is not defined.
The input operand “DeleteFile” determines whether a
file already in the memory card should be deleted.
“DeleteFile” = “0” Do not delete existing data
file on the Memory Card
“DeleteFile” = “1” Delete existing data file on
the Memory Card
The function block is executed asynchronously in
relation to the user program cycle and can take
several program cycles. The Active output is set to 1
during this time. Error-free completion of the function
block is indicated by the Active output changing to 0
and by 0 at the Error output.
Error codes at the Error output:
0 Function block execution completed without
errors.
1 No memory card inserted.
10 Memory card type not SRAM.
11 Memory card is not formatted.
12 Memory card is write protected.
13 Insufficient free memory on memory card to
create the file “RSDAT.DAT”.
14 File “RSDAT.DAT” does not have the required
minimum size of 128 bytes.
15 File “RSDAT.DAT” already exists.
16 Internal error during execution of the function
06/99 AWB 2700-1306 GB

block

457
 Function Blocks

Example: Create and initialise file RSDAT.DAT on

the memory card
PROGRAM INITIALISE
VAR
StrobeInit AT %I0.0.0.0.0 : BOOL;
ActiveInit AT %Q0.0.0.0.0 : BOOL;
ErrorInit :USINT;
FBInitRSData : SetMCFileLength;
NumberOfSegments :UINT;
END_VAR
LD 3222
ST NumberOfSegments
CAL FBInitRSData(Strobe := StrobeInit,
ClearData := 1,
DeleteFile := 0,
NumberOfSegments := NumberOfSegments,
|
ActiveInit := Active,
ErrorInit := Error)
LD ActiveInit
JMPC CONTINUE
LD ErrorInit
EQ 0
JMPC CONTINUE
ERROR HANDLING:
(* Carry out error handling *)
CONTINUE:
(* Further parts of user program *)
END_PROGRAM

06/99 AWB 2700-1306 GB

458
 SetRealTimeClock

PS 4-200 SetRealTimeClock
PS 4-300 Set Real-Time Clock

Prototype of function block

Meaning of operands
Set Enable for accepting the set values, rising edge

DataAddress Start address of range for the set values

Error Error messages

Description
A rising edge at the Set input sets the real-time clock
with the values stored in the DataAddress data
range. The set or default values are provided in seven
consecutive byte data elements. The bytes are in the
order year, month, day, weekday, hours, minutes
and seconds.
A rising edge at the Set input causes all values to be
transferred, but not, however, selected data such as
only hour or year.
The data type declared for the data elements in
which the set values are stored must be in byte
format, i. e. data types BYTE, SINT or USINT.
Using data type USINT is recommended.
06/99 AWB 2700-1306 GB

459
 Function Blocks

The Error output indicates the following error code:

1 Incorrect DataAddress
2 Invalid year (valid range: 0-99)
3 Invalid month (valid range: 1-12)
4 Invalid day (valid range: 1-31)
5 Invalid weekday (valid range: 0-6, 0 = Sunday)
6 Invalid hour (valid range: 0-23)
7 Invalid minute (valid range: 0-59)
8 Invalid second (valid range: 0-59)

Use RTC in new programs instead of

SetRealTimeClock.

06/99 AWB 2700-1306 GB

460
 SetRealTimeClock

Example: Setting the real-time clock

PROGRAM Clock

VAR
Year AT %MB0.0.0.0 : USINT := 97;
Month AT %MB0.0.0.1 : USINT := 1;
Day AT %MB0.0.0.2 : USINT := 1;
Weekday AT %MB0.0.0.3 : USINT := 2;
(* 2 = Tuesday*)
Hour AT %MB0.0.0.4 : USINT := 12;
Minute AT %MB0.0.0.5 : USINT;
Second AT %MB0.0.0.6 : USINT;
(* Default value
Tuesday, 1.1.1997 12.00h *)
Set_time : SetRealTimeClock;
(* Function block declaration *)
Set : BOOL AT %I0.0.0.0.0;
(* Declare set input*)
END_VAR

LD 98
ST Year (* Set year to 1998 *)
LD 9
ST Month (* Set month to September *)
LD 12
ST Day (* Set day to the 12th *)
LD 6
ST Weekday (* Set weekday to Saturday *)
(* Clock is completely reset
via function block *)
(*CAUTION: 12.00 is used as default setting *)
CAL Set_time (Set := Set,
DataAddress := &Year)
LD Set_time.Error
NE 0 (* Scan for no errors *)
JMPC Error evaluation
.
.

END_PROGRAM
06/99 AWB 2700-1306 GB

461
 Function Blocks

PS 4-200 Sfc_x
PS 4-300 Sequence Control Function Block
(x = 1..128)

Prototype of function block

Meaning of operands
Set Activate the sequential control function block

ReSet Reset and call initialisation step

StepInputNumber Step number input

InitStep Instance name of the initialisation step

Step_x Instance name of the steps to be called (FBs).

There are as many Step parameters as steps in
the sequence

Error Error messages

StepOutputNumber Step number output

StepToggle Step toggle

Description
06/99 AWB 2700-1306 GB

The sequential control function block makes it

possible to ensure that the user program is
structured simply and clearly. Each sequential
control function block can call up to 128 steps.
Each step can itself call an entirely new sequence,

462
 Sfc_x

thus allowing a maximum nesting depth of 8 levels.

The individual steps consist of function blocks that
contain the actions to be executed. The logical
structure of a sequence control can be applied to the
user program directly.
For basic information on sequence control
programming see also AWB 27-1186-GB.
The Step_x inputs define the steps to be executed by
means of the corresponding function blocks. The
actions making up each step are contained in the
appropriate function blocks.

The step function block instances that are called

from a sequential control function block must not
have any input or output parameters. An instance
of this kind must only contain local variables
(VAR) or externally declared global variables
(VAR_EXTERNAL).
Only for PS 4-200
In PS 4-200 programs the InitStep and Step_x
parameters can only be assigned a function block
instance with the SFC_x call if it was defined in the
main program. Since the called sequential control
function block only works with global data, an
instance defined locally in another function block
cannot be assigned.
The instance of an SFC function block can only be
called once in a PS 4-200 program since the step
sequence defined by the first instance cannot be
changed when the program is running, not even via
the Online modification function.
The sequential control function block is activated via
06/99 AWB 2700-1306 GB

the Set input. The Reset input is used to reset the

function block and call the initialisation function
block specified at the “InitStep” input/output.
The StepInitNumber input defines the next step to be

463
 Function Blocks

executed.
The Error output indicates the error code (further
information below).
The StepOutputNumber output shows the number of
the current step.
The StepToggle output shows the step transition.
Normally this output is 1 or TRUE; only in the first
cycle after a transition is the output assigned a 0 or
FALSE.
Program sequence with the SFC_x function block
The use of the sequential control function block
involves the following three program stages:
1. Initialising the sequential control function block
2. Processing the sequential control function block
3. Processing status signals of the sequential
control function block
1. Initialising
The StepInputNumber input specifies which step
should be edited. Before calling the sequence for the
first time, the number of the first step to be
processed should be assigned.
The sequential control function block is initialised
with the Init function block. It is called for as long as
the ReSet input is 1.
To implement an automatic initialisation with the Init
function block use the status bit of the PLC for
marking the first cycle. This will set the Reset input
to 1 or TRUE during the first cycle.
The Init function block assigns the StepInputNumber
06/99 AWB 2700-1306 GB

input with the number of the first step to be

processed. This therefore ensures that the number of
the first step is known to the sequential control
function block directly after the program is started.

464
 Sfc_x

The StepInputNumber input is then only changed via

a global variable in the individual step function blocks
(in the following example via the variable
“StepNumber”). This ensures the clear logical
sequencing of the function block.
Example: Initialising the SFC_3
PROGRAM sequ

VAR_GLOBAL
StepNumber : USINT ;
BasicSetting AT %I0.0.0.0.0 : BOOL ;
SafetyDoorClosed AT %I0.0.0.0.1 : BOOL ;
END_VAR

VAR
sequence : SFC_3 ;
First_Cycle : BOOL ;
Initial : Init_FB ;
fill : FB1 ;
heat : FB2 ;
drain : FB3 ;
END_VAR

LD ISA
PLC_Message
ST First_Cycle
CAL sequence (Set := TRUE,
ReSet := First_Cycle,
StepInputNumber := StepNumber,
InitStep := Initial,
Step_1 := fill,
Step_2 := heat,
Step_3 := drain
|
:=Error,
:=StepOutputNumber,
:=StepToggle)

END_PROGRAM
06/99 AWB 2700-1306 GB

465
 Function Blocks

FUNCTION_BLOCK Init_FB
VAR_EXTERNAL
StepNumber : USINT ;
BasicSetting : BOOL ;
SafetyDoorClosed : BOOL ;
END_VAR

LD BasicSetting
AND SafetyDoorClosed
(* If safety not fulfilled then return to
to program.
The StepInputNumber = 0 => neutral*)
RETCN
LD 1 (* Step 1 "fill is defined
as first step *)
ST StepNumber
END_FUNCTION_BLOCK

2. Processing
In order to activate the function block the Set input
must be 1 or TRUE. This activates simultaneously the
step that is defined at the StepInputNumber input. If
the Set and ReSet inputs are set to 1 at the same
time, only the initialisation function block is
processed. In the following examples, the Set input
is permanently set to TRUE. The logical sequences
before the RETC or RETCN commands are
transitions that can be selected as required Step
enabling conditions (=transitions).
The sequential control function block can call several
actions. These actions are active for as long as the
transition condition at the end of the step concerned
is fulfilled. If the transition condition is fulfilled the
StepInputNumber input is assigned the number of
the next step to be processed. In the following cycle
the new step is automatically activated and the old
one deactivated.
06/99 AWB 2700-1306 GB

466
 Sfc_x

The following example tests one transition.

Example: Processing SFC_3
PROGRAM T_check

VAR_GLOBAL
StepNumber : USINT ;
BasicSetting AT %I0.0.0.0.0 : BOOL ;
SafetyDoor_closed AT %I0.0.0.0.1 : BOOL ;
OFF AT %I0.0.0.0.2 : BOOL ;
Boiler_full AT %I0.0.0.0.3 : BOOL ;
Temperature_reached AT %I0.0.0.0.4 : BOOL ;
Valve_open AT %Q0.0.0.0.0 : BOOL ;
Heating_on AT %Q0.0.0.0.1 : BOOL ;
END_VAR

VAR
sequence : SFC_3 ;
First_cycle : BOOL ;
Initial : Init_FB ;
fill : FB1 ;
heat : FB2 ;
drain : FB3 ;
END_VAR

LD ISA
PLC_Message
ST First_cycle
CAL sequence(Set := TRUE,
ReSet := First_cycle,
StepInputNumber := Schrittnummer,
InitStep := Initial,
Step_1 := fill,
Step_2 := heat,
Step_3 := drain
|
:=Error,
:=StepOutputNumber,
:=StepToggle)

END_PROGRAM
06/99 AWB 2700-1306 GB

467
 Function Blocks

FUNCTION_BLOCK FB1

VAR_EXTERNAL
StepNumber : USINT ;
OFF : BOOL ;
Boiler_full : BOOL ;
Valve_open : BOOL ;
END_VAR

LD Boiler_full
OR OFF
RETC
LD TRUE
S Valve_open
LD 2 (*Step "2" heat is defined as next
step*)
ST StepNumber

END_FUNCTION_BLOCK

FUNCTION_BLOCK FB2

VAR_EXTERNAL
StepNumber : USINT ;
OFF : BOOL ;
Heating_on : BOOL ;
Temperature_reached : BOOL ;
Boiler_full : BOOL ;
Valve_open : BOOL ;
END_VAR

LD Boiler_full
OR OFF
OR Temperature_reached
RETC
LD TRUE
R Valve_open
S Heating_on
LD 3 (* Step 3 "drain" is defined as next
step *)
ST StepNumber

END_FUNCTION_BLOCK
06/99 AWB 2700-1306 GB

468
 Sfc_x

Once a step function block has been processed, the

main program is continued directly afterwards,
irrespective of whether the transition was fulfilled or
not. If the transition was fulfilled the step change
will be executed in the next program cycle. If the
transition condition was not fulfilled, the same step
will be carried out as before.
06/99 AWB 2700-1306 GB

469
 Function Blocks

3. Status indication
Various status outputs are provided for monitoring a
step sequence. Error output indicates the following
error codes during processing:
Error Cause of error Error behaviour
number
1 0 present at the Function block is not active No
StepInput number step processed.
input (when Set = 1).
2 Step number entered Error output set. The function
exceeds maximum block stays in the current status.
permissible number of
steps.
4 No function block Error output set. The selected
name at the parameter step is accepted. No processing
of the selected step present since no step function
block entered.

The StepOutputNumber output indicates the current

step number. If, for example, the output indicates the
value 2, the step function block defined at Step_2
has been selected. The value 0 indicates that the
next step selected is the initialisation step.
The StepToggle output indicates the transition from
one step to the next. The output stays at 1 or TRUE
for as long as the step is active. Only in the next cycle
after the change to the new step is StepToggle set to
0 or FALSE.
06/99 AWB 2700-1306 GB

470
 Sfc_x

The StepToggle output can be used to initialise

individual steps. For example, a time monitoring
function can be implemented. If a step is taking too
long because a limit switch has not been reached or
an electrical fault is present, an appropriate fault
message can be output.
The StepToggle pulse is used to initialise a timer.
06/99 AWB 2700-1306 GB

471
 Function Blocks

Example:SFC_3 for time monitoring

PROGRAM Steptime
VAR
Step_Timer : TON ;
Sequence : SFC_3 ;
.
.
.
END_VAR
LD ISA
PLC.MESSAGE
ST First_Cycle
CAL Step_Timer(IN := Sequence.StepToggle,
PT := T#3s) (* Step change starts *)
(* time set for 3s *)
LD Step_Timer.Q
JMPC Fault
(* If the timer is not reset after 3s
jump to a fault subroutine *)
.
.
END_PROGRAM

06/99 AWB 2700-1306 GB

472
 Sfc_x

Other programming examples

When programming ensure that meaningful function
block names, jump labels and variable names are
used. This will simplify programming and the trans-
parency of the programs. The following examples
show typical applications with sequential control
function blocks. The programs are designed for a
paint filling plant.
Example: Linear sequence
Once the system has been switched on the control
system is in wait mode. Only after the start button is
pressed are the steps processed in succession.
The program returns to Step 2 “ConveyorMotor_On”
from Step 4 “CloseValve”.
06/99 AWB 2700-1306 GB

473
 Function Blocks

PROGRAM linear

VAR_GLOBAL
Sequence : SFC_4 ;
Init : Init_FB ;
FB_Start : Start_FB ;
Motor_on : MotonFB ;
Motor_off : MotoffFB ;
Valve_closed : VentClFB ;
First_cycle : BOOL ;
StepNumber : USINT ;
Start AT %I0.0.0.0.0 : BOOL ;
LightBarrier AT %I0.0.0.0.1 : BOOL ;
Quantity AT %I0.0.0.0.2 : BOOL ;
Flow AT %I0.0.0.0.3 : BOOL ;
Motor AT %Q0.0.0.0.0 : BOOL ;
FillingValve AT %Q0.0.0.0.1 : BOOL ;
END_VAR

LD ISA
PLC_Message
ST First_cycle
CAL Sequence(Set := TRUE,
ReSet := First_cycle,
StepInputNumber := StepNumber,
InitStep := Init,
Step_1 := FB_Start,
Step_2 := Motor_on,
Step_3 := Motor_off,
Step_4 := Valve_closed)

END_PROGRAM

FUNCTION_BLOCK Init_FB

VAR_EXTERNAL
StepNumber : USINT ;
END_VAR

(*Initialisation of the function block and

move to first step *)
06/99 AWB 2700-1306 GB

LD 1
ST StepNumber

END_FUNCTION_BLOCK

474
 Sfc_x

FUNCTION_BLOCK Start_FB

VAR_EXTERNAL
Start : BOOL ;
StepNumber : USINT ;
END_VAR

LD Start
RETCN (* Return to main program
if start button not pressed *)
LD 2 (* otherwise move to step two *)
ST StepNumber

END_FUNCTION_BLOCK

FUNCTION_BLOCK MotonFB

VAR_EXTERNAL
LightBarrier : BOOL ;
Motor : BOOL ;
StepNumber : USINT ;
END_VAR

LD TRUE
ST Motor (* Conveyor motor switched on *)
LD LightBarrier

RETC (* Return if light barrier not

interrupted*)
LD 3 (* otherwise move to step three *)
ST StepNumber

END_FUNCTION_BLOCK
06/99 AWB 2700-1306 GB

475
 Function Blocks

FUNCTION_BLOCK MotoffFB

VAR_EXTERNAL
Motor : BOOL ;
Quantity : BOOL ;
FillingValve : BOOL ;
StepNumber : USINT ;
END_VAR

(*Step stops conveyor motor and opens filling

valve *)
LD FALSE
ST Motor (*1st action motor off *)
LD TRUE
ST FillingValve (*2nd action: filling valve
open *)
LD Quantity
RETCN (*No move to step 4 if *)
(*fill quantity not yet reached *)
LD 4
ST StepNumber

END_FUNCTION_BLOCK

FUNCTION_BLOCK ValveClFB
VAR_EXTERNAL
Flow : BOOL ;
FillingValve : BOOL ;
StepNumber : USINT ;
END_VAR
LD FALSE
ST FillingValve (*Valve closed *)
LD Flow
RETC (*When flow really 0 then
step 2 again*)
LD 2
ST StepNumber

END_FUNCTION_BLOCK
06/99 AWB 2700-1306 GB

476
 Sfc_x

Example: OR Sequence
Red or blue paint is to be filled alternately.
A selector can be used to select either the red or blue
containers.

A sequential control function block must be used for

the OR sequence since only one sequence can be
run at a time. As soon as one of the two transitions
(T1 or T3) is fulfilled, the sequence the sequence
proceeds to the appropriate branch. This branch can
then no longer be changed, even if the other
transition were then fulfilled later.
Transitions T1 and T3 are programmed at the end of
the first step (FB “Motor_off”. A jump table is created
06/99 AWB 2700-1306 GB

for this purpose. The step number to be processed is

then defined by loading the values 2 or 3.

477
 Function Blocks

PROGRAM or1

VAR_GLOBAL
Sequence : SFC_4 ;
Init : Init_FB ;
Motor_off : MotoffFB ;
Selector_red : RED_FB ;
Selector_blue : BLUE_FB ;
Valve_open : Valve_FB ;
First_cycle : BOOL ;
StepNumber : USINT ;
Paint_RED AT %I0.0.0.0.0 : BOOL ;
Paint_BLUE AT %I0.0.0.0.1 : BOOL ;
Tank_RED AT %I0.0.0.0.2 : BOOL ;
Tank_BLUE AT %I0.0.0.0.3 : BOOL ;
PaintSelector AT %Q0.0.0.0.0 : BOOL ;
FillingValve AT %Q0.0.0.0.1 : BOOL ;
Motor AT %Q0.0.0.0.2 : BOOL ;
END_VAR
LD ISA
PLC_Message
ST First_cycle
CAL Sequence(Set := TRUE,
ReSet := First_cycle,
StepInputNumber := StepNumber,
InitStep := Init,
Step_1 := Motor_off,
Step_2 := Selector_red,
Step_3 := Selector_blue,
Step_4 := Valve_open)

END_PROGRAM

FUNCTION_BLOCK Init_FB

VAR_EXTERNAL
StepNumber : USINT ;
END_VAR
(*Initialise function block and move to
first step *)
06/99 AWB 2700-1306 GB

LD 1
ST StepNumber

END_FUNCTION_BLOCK

478
 Sfc_x

FUNCTION_BLOCK MotoffFB

VAR_EXTERNAL
Motor : BOOL ;
Paint_RED : BOOL ;
Paint_BLUE : BOOL ;
StepNumber : USINT ;
END_VAR

(* Step stops conveyor motor and opens

filling valve *)
LD FALSE
ST Motor (*Action: Motor off*)
LD Paint_RED
JMPCN Not_RED (*Test colour required RED *)
LD 2 (*Move to step 2 if RED*)
ST StepNumber

Not_RED:
LD Paint_BLUE
RETCN (*Test colour wish BLUE *)
LD 3 (*If BLUE move to step 3*)
ST StepNumber

END_FUNCTION_BLOCK

FUNCTION_BLOCK RED_FB

VAR_EXTERNAL
PaintSelector : BOOL ;
Tank_RED : BOOL ;
StepNumber : USINT ;
END_VAR
(*PaintSelector set to RED *)
LD TRUE
ST PaintSelector
LD Tank_RED
RETCN (*Return if tank empty *)
LD 4 (*Continue to valve opening *)
ST StepNumber
06/99 AWB 2700-1306 GB

END_FUNCTION_BLOCK

479
 Function Blocks

FUNCTION_BLOCK BLUE_FB

VAR_EXTERNAL
PaintSelector : BOOL ;
Tank_BLUE : BOOL ;
StepNumber : USINT ;
END_VAR

(*PaintSelector set to BLUE *)

LD FALSE
ST PaintSelector
LD Tank_BLUE
RETCN (*Return if tank empty *)
LD 4 (*Continue to valve opening *)
ST StepNumber

END_FUNCTION_BLOCK

FUNCTION_BLOCK Valve_FB

VAR_EXTERNAL
FillingValve : BOOL ;
StepNumber : USINT ;
END_VAR

LD TRUE
ST FillingValve
(*Further actions could be followed
here then transition condition for
a next step *)

END_FUNCTION_BLOCK 06/99 AWB 2700-1306 GB

480
 Sfc_x

Example: AND Sequence with Synchronisation

Only one colour mix is to be produced. This example
mixes the paint by filling both paint components via
two different valves at the same time. The metering
is variable according to the shade of colour required.

With the AND sequence the entire sequence is

divided into several parallel sequences. Each
individual branch requires its own sequential control
function block that is called by the central sequence.
06/99 AWB 2700-1306 GB

The parallel branches are combined by a

synchronisation function.

481
 Function Blocks

Before the transition to the next step of the lower

sequence, a scan is made to check whether both
parallel branches are processing their last step.

06/99 AWB 2700-1306 GB

482
 Sfc_x

PROGRAM ANDsequence

VAR_GLOBAL
MainSequence : SFC_3 ;
Main_Init : Init_FB ;
Sequence_1 : SFC_2 ;
Init_Sequence_1 : Init_1 ;
Sequence_2 : SFC_2 ;
Init_Sequence_2 : Init_2 ;
Motor_on : MotonFB ;
Motor_off : MotoffFB ;
Red_open : REDopenFB ;
Blue_open : BLUEopenFB ;
Red_closed : REDclosedFB ;
Blue_closed : BLUEclosedFB ;
First_Cycle : BOOL ;
StepNumber : USINT ;
Speed : UINT ;
Supply AT %I0.0.0.0.0 : BOOL ;
RedProportion AT %I0.0.0.0.1 : BOOL ;
BlueProportion AT %I0.0.0.0.2 : BOOL ;
FillingValve_red AT %Q0.0.0.0.0 : BOOL ;
FillingValve_blue AT %Q0.0.0.0.1 : BOOL ;
Conveyormotor AT %Q0.0.0.0.2 : BOOL ;
Mix : MixFB
END_VAR

LD ISA
PLC_Message
ST First_Cycle
CAL MainSequence(Set := TRUE,
ReSet := First_Cycle,
StepInputNumber :=
StepNumber,
InitStep := Main_Init,
Step_1 := Motor_off,
Step_2 := MixFB,
Step_3 := Motor_on

END_PROGRAM
06/99 AWB 2700-1306 GB

483
 Function Blocks

FUNCTION_BLOCK Init_FB

VAR_EXTERNAL
StepNumber : USINT ;
END_VAR

(*Initialise the function block and move to

next step *)
LD 1
ST StepNumber

END_FUNCTION_BLOCK

FUNCTION_BLOCK MotoffFB

VAR_EXTERNAL
ConveyorMotor : BOOL ;
Speed : UINT ;
StepNumber : USINT ;
END_VAR

(*Step switches off the conveyor motor and

checks when the conveyor has stopped *)
LD FALSE
ST Motor (*Action: Motor off*)
LD Speed
NE 0 (*Check whether conveyor is really
standing already *)
RETC
LD 2(*If yes, then to main sequence, step 2*)
ST StepNumber

END_FUNCTION_BLOCK

FUNCTION_BLOCK MixFB

VAR_EXTERNAL
MainSequence : SFC_3 ;
Main_Init : Init_FB ;
06/99 AWB 2700-1306 GB

Sequence_1 : SFC_2 ;
Init_Sequence_1 : Init_1 ;
Sequence_2 : SFC_2 ;
Init_Sequence_2 : Init_2 ;
Motor_on : MotonFB ;
Motor_off : MotoffFB ;

484
 Sfc_x

Conveyormotor : BOOL ;
Red_open : REDopenFB ;
Red_closed : REDclosedFB ;
Blue_open : BLUEopenFB ;
Blue_closed : BLUEclosedFB ;
First_Cycle : BOOL ;
StepNumber : USINT ;
Speed : UINT ;
Supply : BOOL ;
FillingValve_red : BOOL ;
FillingValve_blue : BOOL ;
END_VAR

VAR
Reset_Subsequence : BOOL ;
END_VAR

LD MainSequence.StepToggle
STN Reset_Subsequence (*Reset if
MainSequence does not toggle *)

CAL Sequence_1(Set := TRUE,

ReSet := Reset_Subsequence,
StepInputNumber := ,
InitStep := Init_Sequence_1,
Step_1 := Red_open,
Step_2 := Red_closed,

CAL Sequence_2(Set := TRUE,

ReSet := Reset_Subsequence,
StepInputNumber := ,
InitStep := Init_Sequence_2,
Step_1 := Blue_open,
Step_2 := Blue_closed,
(*ynchronisation: Sequence 1 already
completed ?*)
LD Sequence_1.StepOutputNumber
EQ 2
JMPCN End
06/99 AWB 2700-1306 GB

485
 Function Blocks

(*Synchronisation: Sequence 2 already

completed ?*)
LD Sequence_2.StepOutputNumber
EQ 2
JMPCN End
(* Supply = 0 ?*)
LD Supply
JMPCN Ende
(*Move to third step of MainSequence *)
LD 3
ST MainSequence.StepInputNumber

End:

END_FUNCTION_BLOCK

FUNCTION_BLOCK MotonFB

VAR_EXTERNAL
Conveyormotor : BOOL ;
END_VAR

LD 1
ST Conveyormotor
(*...*)

END_FUNCTION_BLOCK

FUNCTION_BLOCK Init_1

VAR_EXTERNAL
Sequence_1 : SFC_2 ;
END_VAR

LD 1
ST Sequence_1.StepInputNumber

END_FUNCTION_BLOCK
06/99 AWB 2700-1306 GB

486
 Sfc_x

FUNCTION_BLOCK REDopenFB

VAR_EXTERNAL
Sequence_1 : SFC_2 ;
FillingValve_red : BOOL ;
RedProportion : BOOL ;
END_VAR

(*Open valve for red paint *)

LD 1
ST FillingValve_red
LD RedProportion
JMPCN End (*If RedProportion not yet
reached, continue filling*)
(*Otherwise move to next
step in sequence *)
LD 2
ST Sequence_1.StepInputNumber

End:

END_FUNCTION_BLOCK

FUNCTION_BLOCK REDclosedFB

VAR_EXTERNAL
FillingValve_red : BOOL ;
END_VAR

LD 0
ST FillingValve_red

END_FUNCTION_BLOCK

FUNCTION_BLOCK Init_2

VAR_EXTERNAL
Sequence_2 : SFC_2 ;
END_VAR

(* Move to first cycle of

06/99 AWB 2700-1306 GB

send sequence;
Initialisation*)
LD 1
ST Sequence_2.StepInputNumber

END_FUNCTION_BLOCK

487
 Function Blocks

FUNCTION_BLOCK BLUEopenFB

VAR_EXTERNAL
Sequence_2 : SFC_2;
FillingValve_blue : BOOL ;
BlueProportion : BOOL ;
END_VAR

(*Open valve for blue paint*)

LD 1
ST FillingValve_blue
LD BlueProportion
JMPCN End (*If blue proportion not
yet reached, continue *)
(*Otherwise move to next
step of sequence *)
LD 2
ST Sequence_2.StepInputNumber

End:

END_FUNCTION_BLOCK

FUNCTION_BLOCK BLUEclosedFB

VAR_EXTERNAL
FillingValve_blue : BOOL ;
END_VAR

LD 0
ST FillingValve_blue

END_FUNCTION_BLOCK
06/99 AWB 2700-1306 GB

488
06/99 AWB 2700-1306 GB

Sfc_x

489
 Function Blocks

SR
Flip Flop with Set Dominant

SR

BOOL SET1
BOOL RESET Q1 BOOL

Prototype of the function block

Meaning of operands
SET1 Set condition

RESET Reset condition

Q1 Output state of the bistable element

Description
The characteristic feature of the SR function block is
to statically set a data element – the output Q1 – to
the Boolean status 1 or 0.
Switching between the two states depends on the
value of the Boolean input operands Set1 and ReSet.
The output Q1 is initialised with the value 0 when
starting the process. The first processing of the
function block with the value 1 of the operand Set1
causes the output Q1 to be set to 1. A change of the
value of Set1 no longer then effects the output Q1.
The value 1 at the input operand ReSet sets the
output Q to 0 – the output is reset.
If both input operands have the value 1, the fulfilled
set condition will be dominant, i. e. Q1 is set with
priority.
06/99 AWB 2700-1306 GB

490
 SR

Invocation of the function block SR in the

program “malfunction”
PROGRAM malfunction

VAR
Malfunction1_message : SR;
Malfunction1 AT %I0.0.0.0.0 : BOOL;
Acknowledge_malfunction AT %I0.0.0.0.1 : BOOL;
Display_malfunction1 AT %Q0.0.0.0.6 : BOOL;
END_VAR

CAL Malfunction1_message (SET1 := Malfunction1,

RESET := Acknowledge_malfunction)
LD Malfunction1_message.Q1
ST Display_malfunction1

END_PROGRAM
06/99 AWB 2700-1306 GB

491
 Function Blocks

SR_x
1-Bit Shift Register

Prototype of the function block

Meaning of operands
ForwardPulse Pulse input, forward

BackwardPulse Pulse input, backward

ReSet Reset

ForwardData Data input, forward

BackwardData Data input, backward

Output_1 Output 1

Output_n Last output

Description
There are 128 prototypes of the function block.
The following names can be used for *:
SR_1
SR_2
06/99 AWB 2700-1306 GB

.
.
SR_128

492
 SR_x

The numbers 1 ... 128 indicate the register length, the

number of 1-bit output register fields of the individual
prototypes.
A rising edge on the ForwardPulse operand transfers
the value at the ForwardData operand in the first
register field Output_1. The original contents of the
register fields are moved by one field in the direction
of the higher field numbers.

Contents of the SR_8 shift register before and after a

Forward pulse
06/99 AWB 2700-1306 GB

493
 Function Blocks

A rising edge on the BackwardPulse operand

transfers the value at the BackwardData operand in
the last register field. The original contents of the
register fields are moved by one field in the direction
of the lower field numbers.

Contents of the SR_8 shift register before and after a

Backward pulse

The status 1 of the ReSet clears the entire Output_1

... Output_n Output register.
06/99 AWB 2700-1306 GB

494
 SR_x

Invocation of the function block SR_4 in the

program “sh_reg1”
PROGRAM sh_reg1

VAR
Shift_register_4_bit : SR_4;
Pulse1 : BOOL;
Pulse2 : BOOL;
Reset : BOOL;
Data_bit1 : BOOL;
Data_bit2 : BOOL;
Output1 : BOOL;
Output2 : BOOL;
Output3 : BOOL;
Output4 : BOOL;
END_VAR

CAL Shift_register_4_bit (ForwardPulse := Pulse1,

BackwardPulse := Pulse2,
ReSet := Reset,
ForwardData := Data_bit1,
BackwardData := Data_bit2)
LD Shift_register_4_bit.Output_1
ST Output1
LD Shift_register_4_bit.Output_2
ST Output2
LD Shift_register_4_bit.Output_3
ST Output3
LD Shift_register_4_bit.Output_4
ST Output4

END_PROGRAM
06/99 AWB 2700-1306 GB

495
 Function Blocks

SRB_x
8-Bit shift register

Prototype of the function block

Meaning of operands
ForwardPulse Pulse input, forward

BackwardPulse Pulse input, backward

ReSet Reset

ForwardData Data input, forward

BackwardData Data input, backward

Output_1 Output 1

Output_n Last output

Description
There are 128 function block prototypes. The follow-
ing names can be used for *:
SRB_1
SRB_2
.
06/99 AWB 2700-1306 GB

.
SRB_128

496
 SRB_x

The numbers 1 ... 128 indicate the register length, the

number of 8-bit output register fields of the individual
prototypes.
A rising edge on the ForwardPulse operand transfers
the value at the ForwardData operand in the first
register field Output_1. The original contents of the
register fields are moved by one field in the direction
of the higher field numbers.

Contents of the SRB_8 shift register before and after a

Forward pulse
06/99 AWB 2700-1306 GB

497
 Function Blocks

A rising edge on the BackwardPulse operand trans-

fers the value at the BackwardData operand in the
last register field. The original contents of the register
fields are moved by one field in the direction of the
lower field numbers.

Contents of the SRB_8 shift register before and after a

Backward pulse

The status 1 of the ReSet operand clears the entire

Output_1 ... Output_n output register. 06/99 AWB 2700-1306 GB

498
 SRB_x

Invocation of the function block SRB_2 in the

program “sh_reg8”
PROGRAM sh_reg8

VAR
Shift_register_2_byte : SRB_2;
Pulse1 : BOOL;
Pulse2 : BOOL;
Res : BOOL;
Data1 : USINT;
Data2 : USINT;
Output1 : USINT;
Output2 : USINT;
END_VAR

CAL Shift_register_2_byte (ForwardPulse := Pulse1,

BackwardPulse := Pulse2,
ReSet := Res,
ForwardData := Data1,
BackwardData := Data2)
LD Shift_register_2_byte.Output1
ST Output1
LD Shift_register_2_byte.Output2
ST Output2

END_PROGRAM
06/99 AWB 2700-1306 GB

499
 Function Blocks

SRW_x
16-Bit shift register

Prototype of the function block

Meaning of operands
ForwardPulse Pulse input, forward

BackwardPulse Pulse input, backward

ReSet Reset

ForwardData Data input, forward

BackwardData Data input, backward

Output_1 Output 1

Output_n Last output

Description
There are 128 function block prototypes. The follow-
ing names can be used for *:
SRW_1
SRW_2
.
.
06/99 AWB 2700-1306 GB

SRW_128
The numbers 1 ... 128 indicate the register length,
the number of 16-bit output register fields of the
individual prototypes.

500
 SRW_x

A rising edge on the ForwardPulse operand transfers

the value at the ForwardData operand in the first
register field Output_1. The original contents of the
register fields are moved by one field in the direction
of the higher field numbers.

Contents of the SRW_8 shift register before and after a

Forward pulse
06/99 AWB 2700-1306 GB

501
 Function Blocks

A rising edge on the BackwardPulse operand

transfers the value at the BackwardData operand in
the last register field. The original contents of the
register fields are moved by one field in the direction
of the lower field numbers.

Contents of the SRW_8 shift register before and after a

Backward pulse

The status 1 of the ReSet operand clears the entire

Output_1 ... Output_n register.
06/99 AWB 2700-1306 GB

502
 SRW_x

Invocation of the function block SRW_2 in the

program s_reg16
PROGRAM s_reg16

VAR
Shift_register_2_word : SRW_2;
Pulse1 : BOOL;
Pulse2 : BOOL;
Res : BOOL;
Data1 : UINT;
Data2 : UINT;
Output1 : UINT;
Output2 : UINT;
END_VAR

CAL Shift_register_2_word (ForwardPulse := Pulse1,

BackwardPulse := Pulse2,
ReSet := Res,
ForwardData := Data1,
BackwardData := Data2)
LD Shift_register_2_word.Output1
ST Output1
LD Shift_register_2_word.Output2
ST Output2

END_PROGRAM
06/99 AWB 2700-1306 GB

503
 Function Blocks

PS 4-300 SSIEncoder
Control of LE 4-633-CX1 local expansion
module

SSIEncoder

USINT LENumber ActualPosition UDINT

USINT ChannelNumber SpecialBit BOOL
UINT ClockFrequency Error USINT
USINT ResolutionPerRevolution
USINT NumberPerRevolution
BOOL SpecialBitUsed
BOOL GrayCode
BOOL CountDirection

Prototype of the function block

Meaning of the operands

LENumber Module address of LE 1 = 1st LE; 2 = 2nd LE

ChannelNumber Channel number

1 = Channel 1; 2 = Channel 2; 3 = Channel 3

ClockFrequency Clock output frequency in kHz

125 = 125 kHz; 250 = 250 kHz

ResolutionPer- Bit no. of increments per revolution of SSI

Revolution absolute value encoder

NumberPer-Revolution Bit no. of revolutions of SSI absolute value

encoder

SpecialBitUsed Special bit of SSI absolute value encoder

0 = No special bit;
1 = Special bit present

GrayCode Code used by SSI absolute value encoder

0 = binary code; 1 = Gray code
06/99 AWB 2700-1306 GB

CountDirection Change counting direction

0 = no counter direction change
1 = Counter direction change

ActualPosition Current position value

504
 SSIEncoder

SpecialBit With special bit active (SpecialBitUsed =1),

the value of the special bit is output

Error Error messages

0 = No error
1 = LE 4-633-CX1 not present
2 = Incorrect parameters
4 = Wire break on SSI absolute value encoder

Description
The SSIEncoder function block controls the
LE 4-633-CX1. The following functions are possible:
Set LE number
Set channel number
Set absolute value encoder parameters
Scan actual position
Scan special bit
Scan error messages
Each LE channel can be assigned one function block
instance. The “LENumber” and “ChannelNumber”
are used to specify the SSI absolute encoder for
which the current position is to be scanned. The
current position value is updated every time the
“SSIEncoder” function block is processed.
06/99 AWB 2700-1306 GB

505
 Function Blocks

Example “Control of LE 4-633-CX1 local

expansion module”
An SSI absolute encoder is connected to channel no.
1 of the 1st LE. The SSI absolute encoder has the
following parameters:
Increments per revolution: 4096 (12-bit)
No. of revolutions: 4096 (12-bit)
Code: Gray
Special bit: no
PROGRAM SSIAbsoluteValue

VAR
ssiLE1_Channel1 : SSIEncoder ;
ActualPosition24Bit : UDINT ;
Error : USINT ;
END_VAR

CAL ssiLE1_Channel1(
LENumber :=1, (* 1st LE *)
ChannelNumber :=1, (* Channel no. 1 *)
ClockFrequency :=125, (* Clockfrequency = 125 kHz *)
ResolutionPerRevolution :=12, (* No. of bits per revolution=12-bit*)
NumberPerRevolution :=12, (* No. of bits per revolution=12-bit*)
SpecialBitUsed :=0, (* No special bit *)
GrayCode :=1, (* Graycode *)
CountDirection :=0 (* No direction change *)
)

ld ssiLE1_Channel1.Error
st Error

ld ssiLE1_Channel1.ActualPosition
st ActualPosition24Bit

END_PROGRAM
06/99 AWB 2700-1306 GB

506
 STRtoADR

PS 4-200 STRtoADR
PS 4-300 Copy String to Marker Area

Prototype of the function block

Meaning of operands
TextString String to be stored in the marker range

TransmitVariable Start address of the marker range in which the data

is to be stored

Enable Number of converted characters

StrLen Enable of conversion process

Description
The STRtoADR function block is primarily used to
copy a string to a marker area with the start address
“TransmitVariable” The SCO function block which
requires the same start address as an input para-
meter then outputs this string through a serial
interface.
A “1” or TRUE on the Enable input starts the
conversion. The output parameter StrLen indicates
the number of characters which were copied to the
marker area and can pass on the amount of data to
be transferred to a communication function block
such as SCO.
06/99 AWB 2700-1306 GB

If the length of TextString is longer than the declared

marker area, the string is truncated.

507
 Function Blocks

Invocation of the “STRtoADR” function block in

the “Textcopy” program
PROGRAM Textcopy

VAR
String_to_Marker : STRtoADR;
SendText : STRING := 'Small Example';
StartAddress AT %MB0.0.0.100 : BYTE;
SendLength : UINT;

END_VAR

CAL String_to_Marker(Enable := 1,
TextString := SendText,
TransmitVariable := &StartAddress)

(* String is stored in the marker area

from MB100 *)
LD String_to_Marker.StrLen
ST SendLength

END_PROGRAM

06/99 AWB 2700-1306 GB

508
 STRtoCOM

STRtoCOM
Copy string to Array

Prototype of the function block

Meaning of operands
TextString String to be stored in the array

TransmitVariable Start address of the array in which the data is to be

stored

Enable Enable the conversion

StrLen Number of converted characters

Description
The STRtoCOM function block is primarily used to
store a string from the start address TransmitVariable
to the marker range. The COM or SCO function block
which requires the same start address as an input
parameter then outputs this string on a serial
interface.
A 1 or TRUE on the Enable input starts the
conversion. The output parameter StrLen indicates
the number of characters copied to the marker range
and passes on the number of data units to be
transferred to a communication function block such
as COM or SCO. If the length of the string is longer
06/99 AWB 2700-1306 GB

than the declared marker area, the string is truncated

when copied and StrLen shows the size of the array.

509
 Function Blocks

Invocation of the function block STRtoCOM in the

program “textcopy”
PROGRAM Textcopy

VAR
String_to_Array : STRtoCOM;
SendText : STRING := 'Small Example';
SendArray : ARRAY [1..100] OF BYTE;
SendLength : UINT;
END_VAR

CAL String_to_ Array(Enable := 1,

TextString := SendText,
TransmitVariable := SendArray
|
SendLength :=.StrLen)

END_PROGRAM

06/99 AWB 2700-1306 GB

510
 SUCOM_A

PS 4-300 SUCOM_A
PS 416 Protocol Emulation for Direct Memory Access

Prototype of the function block

Meaning of operands
Enable Enable

SlotNumber Slot of the assigned card

0 PS 416-CPU-400/300 or
PS 4-341-MM1 with
SBI interface
4...20 PS 416-COM-200 with RS 232 interface

ReceiveError Error message on receive job

TransmitError Error message on send job

SlotError Error message when no SUCOM-A compatible card is

fitted at the addressed slot.

InterfaceStatus Indicates the operating status of the card and the

fitted modules

TransmitActive FB is processing Send job when “1“

ReceiveActive FB is processing Receive job when “1“

06/99 AWB 2700-1306 GB

511
 Function Blocks

Description
The SUCOM_A function block is used to emulate the
programming protocol for direct access to markers,
diagnostics and the status word.
The following interfaces can be used to access the
marker, status and diagnostic bits of the PS 416
controller:
PRG interface of a PS 416-CPU-400/300/200
card
SBI interface of a PS 416-CPU-400/300 card
(Transparent mode)
SBI interface of the PS 4-341-MM1
(Transparent mode)
RS 232 interface of a PS 416-COM-200 card
Access takes place through the proprietary Moeller
SUCOM-A protocol using external software. The
marker area can be read and written to. Status and
diagnostic bits can only be read.
The SUCOM-A protocol is detected automatically on
the PRG interface of the PS 416-CPU-400 card by
the operating system.
If you are using the SBI interface of the
PS 416-CPU-400 card or the RS 232 interface of
the PS 416-COM-200 card, it is first necessary to
initialize the interface accordingly. Specify in the
Interface Parameters window of the Topology
Configurator the Baud rate, Data format, Parity and
Stop bits parameters for the connected device.
If data communication in a PS 416 system takes
place both through the SBI interface of the CPU card
06/99 AWB 2700-1306 GB

and also through one or more PS 416-COM-200

cards, it is necessary to program separate instances
of the SUCOM_A function block for each of the
interfaces and to specify the respective slot number.

512
 SUCOM_A

The slot number is specified with SlotNumber.

Specify “0” for an SBI interface; specify the
appropriate slot number for the PS 416-COM-200
card(s).
The SUCOM_A emulation can be operated
simultaneously on the SBI interface and up to
6 PS 416-COM-200 cards.
In order to activate the SUCOM_A emulation for a
single interface, you only need to call the respective
instance of the function block once in your program
with Enable = “1”. The emulation remains active until
the function block is called again with Enable = “0”.
However, the function block outputs are only up-
dated if the function block is called cyclically with
Enable = 1.
The reaction time is dependent on the number of
simultaneously active interfaces and the interface
being used:
PRG interface of the PS 416-CPU: approx. 30 ms
SBI interface of the PS 416-CPU: approx. 100 ms
Interface of the PS 416-COM-200: approx. 200 ms
The reaction time is not affected if the SUCOM_A
function block is called more than once within the
same program cycle.
The external software should be programmed to wait
for a response from the PLC or to have a timeout
value of one second, after which the request should
be repeated if necessary.
06/99 AWB 2700-1306 GB

513
 Function Blocks

The function block outputs ReceiveError,

TransmitError and SlotError can be used for
diagnostics. If there are no errors, all three outputs
are set to “0”. If an error occurs, the associated error
and status messages are output. The codes of
the messages are identical to those of the
PS 416-COM-200 and can be found in the manual
“PS 416-COM-200 Point-to-Point Communication
Card” (AWB 27-1237-GB) in the section “Test and
Commissioning”.
The interface converter UM 1.5 can be used to adapt
the signal levels between RS 232 and RS 485
interfaces (e.g. SBI interface).

If the function block is instanced more than once

in your program and/or the markers in your
program are also used for other purposes, e. g.
for PROFIBUS communication, take care to avoid
overlaps of the marker areas to avoid
unintentional changes to data.

Invocation of the SUCOM_A function block for a

card in slot 6 in the “protocol” program
PROGRAM protocol

VAR
Sucom_A_FB : SUCOM_A;
Enable_SucomA AT %I0.0.0.0.0 : BOOL;
END_VAR

CAL Sucom_A_FB(Enable := Enable_SucomA,

SlotNumber := 6)

END_PROGRAM
06/99 AWB 2700-1306 GB

514
 SuconetP

PS 416 SuconetP
Profibus-FMS Communication

Prototype of the function block

Description
The SuconetP function block is used to handle
PROFIBUS communication via the PROFIBUS-FMS
card PS 416-NET230.
Please refer to the manual “Additional Information on
PROFIBUS, PS 416-NET230 - Suconet-P Card”
(AWB 27-1235-GB) for a description of this function
block and some application notes.
06/99 AWB 2700-1306 GB

515
 Function Blocks

PS 416 SuconetS_BGKS
InterBus Communication

Prototype of the function block

Meaning of operands
Strobe Start bit-controlled command sequence

SequenceNr Bit number of the command sequence

(value range 0-15 decimal

Slot Slot for PS 416-NET-220 card (value 4-19 decimal)

ReSet Initial status

Active Execution of command sequence active

Error Error message

Description
The SuconetS_BGKS function block is used to
access the bit-mapped command sequences of the
PS 416-NET-220 card.
Please refer to the manual “Hardware and
Engineering, PS 416-NET-220, Suconet-S Card”
(AWB 27-1236-GB) for a description of this function
block.
06/99 AWB 2700-1306 GB

516
 TimeConcat

TimeConcat
Generate time duration

Prototype of the function block

Meaning of operands
MilliSeconds Milliseconds part of a time duration

Seconds Seconds part of a time duration

Minutes Minutes part of a time duration

Hours Hour part of a time duration

Days Day part of a time duration

Sign Sign of a time duration

OutputTime Resulting value of time duration

Overflow Overflow

Description
The individual time elements that are specified as
input operands are combined to form a time duration
value of data type TIME in the OutputTime output
06/99 AWB 2700-1306 GB

operand.
The function block converts the individual values into
the appropriate component of the time duration
concerned and also forms a carry if necessary.

517
 Function Blocks

The input variables can take any value permissible

for UINT data types provided that the total result
does not exceed T#63d23h59m59s999ms. If this
value is exceeded, the Overflow output will indicate
a 1.
The sign bit of the Sign input operand affects the
result: Sign = 0 positive result value, Sign = 1
negative result value of the OutputTime operand.
Invocation of the function block TimeConcat in
the program “time_gen”
PROGRAM time_gen

VAR
TimeConcaten : TimeConcat;
Millisec : UINT;
Sec : UINT;
Min : UINT;
Hrs : UINT;
Dys : UINT;
Sgn : BOOL := 0;
TimeStructure : TIME;
Overflow : BOOL;
END_VAR

CAL TimeConcaten (MilliSeconds := Millisec,

Seconds := Sec,
Minutes := Min,
Hours := Hrs,
Days := Dys,
Sign := Sgn
|
TimeStructure :=
OutputTime,
Overflow := Overflow)

END_PROGRAM
06/99 AWB 2700-1306 GB

518
 TimeGenerator

TimeGenerator
Pulse generator

Prototype of the function block

Meaning of operands
Set Start condition, rising edge

Period Period in milliseconds

PulseOutput Pulse output

Time diagram

Description
A rising edge on the Set input transfers the Period
value as period duration T in milliseconds to the
timer. As long as the Set input is 1 the PulseOutput
will then supply an output pulse sequence for the
duration defined on the Period input at a pulse/pause
ratio of 1 : 1.
The period duration can be set at the Period input
06/99 AWB 2700-1306 GB

between 1 and 65535 ms.

If the Period value is changed during pulse
generation, the frequency is not adapted

519
 Function Blocks

immediately. The new value is not transferred until

the next rising edge on the Set input.
The accuracy of the period duration output depends
on the cycle time of the program and the calculation
time of the operating system and deviates by these
times.
An uneven value for the period duration is rounded
off internally to the next even value. If the period
duration is approximately that of the program cycle
time or even less than it, the output period duration
will be very inaccurate. Calling the function block
several times in one program cycle helps to reduce
this deviation.
Example “320 milliseconds frequency”
PROGRAM frequency

VAR
ClockGenerator : TimeGenerator;
Start AT %I0.0.0.0.0 : BOOL;
PeriodTime: UINT := 320;
Pulse : BOOL;
END_VAR

CAL ClockGenerator(Set := Start,

Period := PeriodTime)
LD ClockGenerator.PulseOutput
ST Pulse

END_PROGRAM
06/99 AWB 2700-1306 GB

520
 TimePulse

TimePulse
Time pulse

Prototype of the function block

Meaning of operands
Set Start condition, rising edge

ReSet Reset condition

PresetTime Time setpoint in milliseconds

PulseOutput Control output

ElapsedTime Time actual value in milliseconds

Description

Time diagram

A rising edge on the Set input transfers the

06/99 AWB 2700-1306 GB

PresetTime value as a delay time T in milliseconds

to the time pulse generator and starts it. The
PulseOutput switches to 1 and keeps this status for
the duration of the time set.

521
 Function Blocks

A status change on the Set input has no effect during

the running of the pulse generator.
The ElapsedTime output shows the current time
value in milliseconds.
The timer is reset when the ReSet input is set to 1
during operation.
Example: 125 milliseconds impulse
PROGRAM pulse

VAR
Pause : TimePulse;
Start AT %I0.0.0.0.0 : BOOL;
PulseDuration: UINT := 125;
OutputPulse : BOOL;
ActualTime : UINT;
END_VAR

CAL Pause(Set := Start,

PresetTime := PulseDuration)
LD Pause.PulseOutput
ST OutputPulse
LD Pause.ElapsedTime
ST ActualTime

END_PROGRAM

06/99 AWB 2700-1306 GB

522
 TimerAlarm

PS 4-200 TimerAlarm
PS 4-300 Alarm function block Time
PS 416

TimerAlarm

BOOL EnableDisable
USINT Mode Error UINT
UINT Predivide CallUpNumber UINT
UINT SetpointValue
ANY_FUNCTION_BLOCK SubRoutine

Prototype of the function block

Meaning of operands
EnableDisable Enable and disable of alarm execution
(0 = Disable, 1 = Enable)
Mode Operating mode (1 = Timer, 2 = Pulse generator)
Predivide Predivider for the counter
SetPointValue Setpoint number pulses
SubRoutine Instance name of the function block called by the
alarm
Error Error messages
CallUpNumber Number of alarm-controlled function block
invocations

Description
The input EnableDisable controls the start of the
counter. The counter is started if this input is set to 1
or TRUE and the function block instance to be called,
Predivide and SetPointValue are accepted and
temporarily saved. The value of CallUpNumber is
reset. The function block is stopped and reset if the
06/99 AWB 2700-1306 GB

input status changes from 1 or TRUE to 0 or FALSE.

In the operating mode Mode = 1 the function block is
a Timer. The Predivide input then defines the time
base in ms (e. g. 1000 = 1 ms). The smallest pulse

523
 Function Blocks

length is 512 µs. SetPointValue defines the setpoint

of the Timer. After the setpoint number of pulses has
elapsed the counter CallUpNumber is increased and,
if entered, a function block instance is called via
SubRoutine.
In the operating mode Mode = 2 the function block is
a pulse generator which is connected with the
hardware output %Q0.0.0.0.0 of the basic unit of the
PLC. Then the Predivide input defines the pulse
length and the time base in ms. SetPointValue
(= sum edge rising/falling) causes the half number of
pulses on output %Q0.0.0.0.0
%Q0.0.0.0.0 is continuously output and
CallUpNumber counts how often the predefined
setpoint was reached.

The maximum system capacity depends on the

following three factors: Predivide, SetPointValue
and the frequency set.
These factors must be selected so that no more
than two interrupts occur per millisecond.

The Error output indicates the error codes:

0 No error
1 SetPointValue = 0
2 Predivide less than 512
3 Mode has invalid value
Error code with PS 4-300 only
4 Alarm channel number already used.
The SubRoutine input allows event-controlled pro-
gramming to be implemented. This is done be stating
the instance name of the function block to be
06/99 AWB 2700-1306 GB

activated when the event is reached. If no instance is

specified, the CountValue will continue to be
incremented without triggering the alarm. The
function block instance called by the alarm function
block must not have anyVAR_IN_OUT parameters.

524
 TimerAlarm

This kind of instance must only have local variables

(VAR) or global variables that have been declared
externally as VAR_EXTERNAL variables.
06/99 AWB 2700-1306 GB

Observe the following notes for event-driven

program processing:

525
 Function Blocks

After the event has occurred, the user program is

interrupted, the register status is saved and the
subprogram specified by Subroutine is executed.
The alarm function block cannot be interrupted by
other alarm function blocks (all alarm function blocks
have the same priority). The maximum execution
time of alarm function blocks is to be restricted to
5 ms (approx. 1K IL instructions) in the user program
since the alarm function blocks cannot be inter-
rupted even by the operating system in the event of
a voltage drop. If the execution time is exceeded, an
EDC error may occur when switching off the power
supply.
The execution time of the alarm function block is
added to the execution time of the cyclical user
program and also monitored by the cycle time
monitoring function.
Since the event-driven program processing enables
access to the entire image register, access to data
that is used by the event-controlled and cyclical user
program must be disabled. Bit accesses may only
occur on the same byte in the cyclical user program
and in the Alarm function block if the access is
synchronized with Disable_Interrupt and
Enable_Interrupt.
Since, due to its fast reactions, an Alarm function
block requires, a high-speed peripheral access
(direct output), the QB, QPB peripheral operands
available in the basic unit should be used.
An alarm function block can be used several times
(multiple instantiation) although this should normally
06/99 AWB 2700-1306 GB

be avoided since each function block group has the

same event source and only the last function block
instance in the program is valid. Multiple instantiation
is only useful if the parameters of the function block

526
 TimerAlarm

are set again within an interrupt routine and an edge

disable is to be implemented.
By multiple instantiation is meant the reservation of
several data ranges for each parameter set of a
particular function block type.
The following example shows the invocation of the
Timer alarm function block operating as a pulse
generator (Mode = 2). The time base, i. e. pulse
length is 1 ms (Predivide = 1000). The output at
%Q0.0.0.0.0 is as follows (a total of 50 pulses are
output):

The input parameters of an alarm function block

should only be assigned between the parenthe-
ses when it is called. An explicit parameter
assignment outside of the parentheses before
or after the invocation is not permissible.
06/99 AWB 2700-1306 GB

527
 Function Blocks

Example: TimerAlarm as pulse generator

PROGRAM talarm

VAR
T_Alarm : TimerAlarm;
Error : USINT;
CountValue : UINT;
END_VAR

CAL T_Alarm (EnableDisable := 1,

Mode := 2,
Predivide := 1000,
SetPointValue := 100)
LD T_Alarm.Error
ST Error
LD T_Alarm.CallUpNumber
ST CountValue (*This gives the number
of complete pulse series
that have been output*)
END_PROGRAM

06/99 AWB 2700-1306 GB

528
 TimeSplit

TimeSplit
Split TIME variable type

Prototype of the function block

Meaning of operands
InputTime Time duration to be divided in time elements

MilliSeconds Milliseconds part of time duration

Seconds Seconds part of time duration

Minutes Minutes part of time duration

Hours Hour part of time duration

Days Day part of time duration

Sign Sign of time duration

Description
The time duration value specified via the InputTime
input operand is divided into time elements that are
each output as UINT data types.
The sign of the time duration specified is indicated by
06/99 AWB 2700-1306 GB

the Boolean output operand Sign. 0 indicates a

positive value, 1 indicates a negative value.

529
 Function Blocks

Example: Split time duration into time elements

PROGRAM ti_split

VAR
TimeElements : TimeSplit;
Duration : TIME := T#20d22h13m12s800ms;
Millisec : UINT;
Sec : UINT;
Min : UINT;
Hrs : UINT;
Dys : UINT;
Sgn : BOOL;
END_VAR

CAL TimeElements(InputTime := Duration

|
Milliseconds := MilliSec,
Seconds := Sec,
Minutes := Min,
Hours := Hrs,
Days := Dys,
Sign := Sgn)

END_PROGRAM

06/99 AWB 2700-1306 GB

530
 TODconcat

TODconcat
Generate time

Prototype of the function block

Meaning of operands
MilliSecond Milliseconds part of time

Second Seconds part of time

Minute Minutes part of time

Hour Hours part of time

OutputTOD Resulting value for time

Error Error messages

Description
The individual time elements specified as input
operands are combined to a time value in the output
operand OutputTOD. The input operands must not
exceed the permissible value ranges for a time.
The output operand Error will be set to 1 if the
permissible range of a time value is exceeded.
06/99 AWB 2700-1306 GB

531
 Function Blocks

Example: Generate time of day

PROGRAM time2

VAR
TimeOfDay : TODconcat;
Millisecond : UINT;
Sec : UINT;
Min : UINT;
Hr : UINT;
TODStructure : TIME_OF_DAY;
Error : BOOL;
END_VAR

CAL TimeOfDay(MilliSecond := Millisecond,

Second := Sec,
Minute := Min,
Hour := Hr
|
TODStructure:= OutputTOD,
Error:= Error)

END_PROGRAM

06/99 AWB 2700-1306 GB

532
 TODsplit

TODsplit
Split TIME_OF_DAY data type

Prototype of the function block

Meaning of operands
InputTOD Time

MilliSecond Milliseconds part of time

Second Seconds part of time

Minute Minutes part of time

Hour Hours part of time

Description
The time value specified via the InputTOD input
operand is divided into time elements that are output
as UINT data types.
06/99 AWB 2700-1306 GB

533
 Function Blocks

Example: Split time of day into time elements

PROGRAM time1

VAR
Split_time : TODsplit;
TimeOfDay : TOD := TOD#12:13:12;
Millisec : UINT;
Sec : UINT;
Min : UINT;
Hrs : UINT;
END_VAR

CAL Split_time(InputTOD := TimeOfDay

|
Milliseconds := Millisec,
Seconds := Sec,
Minutes := Min,
Hours := Hrs)

END_PROGRAM

06/99 AWB 2700-1306 GB

534
 TOF

TOF
Off delay

Prototype of the function block

Meaning of operands
IN Start condition

PT Predefined time value

Q Binary status of timer

ET Current time value

Description

Time diagram

The status 1 of the input operand IN is transferred to

the output operand Q without delay. The falling edge
of IN starts the time function of the timer TON for the
duration of the time value defined by the operand PT.
06/99 AWB 2700-1306 GB

The change of the status on the input IN to 0 during

the running time does not effect the operation. After
the time has elapsed, the status of the operand Q
changes to 0. If the PT value changes after the start,

535
 Function Blocks

it has only effect with the next rising edge of the

operand IN.
The output operand ET indicates the current time
value. After the time has elapsed, the operand ET
keeps its value as long as the operand IN has the
status 1. If the status of the operand IN changes to 0,
the value of ET changes to 0.
Deactivating the input IN causes the output Q to be
switched off, delayed by the predefined time.
Example: Switch off delayed by 125 milliseconds
PROGRAM time2

VAR
Timer3 : TOF;
Start AT %I0.0.0.0.0 : BOOL;
Duration : TIME := T#125ms;
Output AT %Q0.0.0.0.0 : BOOL;
Actual_time : TIME;
END_VAR

CAL Timer3(IN := Start,

PT := Duration)
LD Timer3.Q
ST Output
LD Timer3.ET
ST Actual_time

END_PROGRAM
06/99 AWB 2700-1306 GB

536
 TON

TON
On delay

Prototype of the function block

Meaning of operands
IN Start condition

PT Predefined time value

Q Binary status of the timer

ET Current time value

Description

Time diagram

The rising edge of the input operand IN starts the

time function of the timer TON for the duration of the
time value defined by the operand PT.
During this time the output operand Q has the
06/99 AWB 2700-1306 GB

status 0. After the time has elapsed, the status

changes to 1 and is kept until the operand IN
changes to 0.

537
 Function Blocks

If the PT value changes after the start, it has only

effect with the next rising edge of the operand IN.
The output operand ET indicates the current time
value. After the time has elapsed, the operand ET
keeps its value as long as the operand IN has the
status 1. If the status of the operand IN changes to 0,
the value of ET changes to 0.
If the status of the operand IN changes to 0 during
the running time, the operation is stopped and the
operand ET is again 0.
The activation of the input IN causes the output Q to
be switched on, delayed by the predefined time.
Example: Switch on delayed by 12 milliseconds
PROGRAM time1

VAR
Timer2 : TON;
Start AT %I0.0.0.0.0 : BOOL;
Duration : TIME := T#12ms;
Output AT %Q0.0.0.0.0 : BOOL;
Actual_time : TIME;
END_VAR

CAL Timer2(IN := Start,

PT := Duration)
LD Timer2.Q
ST Output
LD Timer2.ET
ST Actual_time

END_PROGRAM
06/99 AWB 2700-1306 GB

538
 TP

TP
Impulse

Prototype of the function block

Meaning of operands
IN Start condition

PT Predefined time value

Q Binary status of the timer

ET Current time value

Description

Time diagram

The rising edge of the input operand IN starts the

time function of the timer TP for the duration of the
time value defined by the operand PT.
During this time the output operand Q has the status
06/99 AWB 2700-1306 GB

1. The change of the status on the input IN does not

effect the operation.

539
 Function Blocks

If the PT value changes after the start, it has only

effect with the next rising edge of the operand IN.
The output operand ET indicates the current time
value. If the operand IN is 1 after the time has
elapsed, the operand ET keeps its value.
Each edge occurring when the timer is not active
initiates a pulse for the set duration.
Example: 125 milliseconds impulse
PROGRAM impulse

VAR
Timer1 : TP;
Start AT %I0.0.0.0.0 : BOOL;
Impulse_duration: TIME := T#125ms;
Output_impulse : BOOL;
Actual_time : TIME;
END_VAR

CAL Timer1(IN := Start,

PT := Impulse_duration)
LD Timer1.Q
ST Output_impulse
LD Timer1.ET
ST Actual_time

END_PROGRAM

06/99 AWB 2700-1306 GB

540
 TransferArray

TransferArray
Copy or Initialise Array

Prototype of the function block

Meaning of operands
Source Source area

Destination Destination area

Mode Operating mode (0 = Initialise, 1 = Copy)

SourceOffset Offset in Source area

DestinationOffset Offset in Destination area

ElementNumber Number of bytes to be copied

Error Error messages

Description
The TransferArray function block has two operating
modes: Initialise and copy.
The mode is set with the Mode input.
06/99 AWB 2700-1306 GB

The source and the destination can be arrays of any

size. All ANY_BIT and ANY_INT arrays apart from
BOOL are permissible as array elements.

541
 Function Blocks

Error codes at the Error output:

0 No error
1 Number of elements (ElementNumber) is 0
2 Source offset is outside the source area.
3 Number of elements exceeds the source area.
4 Destination offset is outside the destination area
5 Number of elements exceeds the destination area
6 Source and destination addresses are identical
Initialise mode
In Initialise mode the function block copies the
contents of the array element specified by “Source +
SourceOffset” to a data block specified by
“Destination + DestinationOffset”. Source and
destination can lie within the same array.
Copy mode
In Copy mode the function block copies part of an
array or an entire array from “Source + SourceOffset”
to “Destination + DestinationOffset”. The number of
elements to copy is specified with ElementNumber.
Source and destination can lie within the same array
to allow block moves.
Please see the description of the BlockTransfer
function block for examples of using TransferArray,
since these function blocks are very similar. You only
need to change the declarations – replace source
and destination address by array declarations.
06/99 AWB 2700-1306 GB

542
 WriteAnalogDirect

PS 416 WriteAnalogDirect
Direct Writing to Analog Outputs

Prototype of the function block

Meaning of operands
AnalogOutValues Contains the values for all required channels that are
to be output

Slot Slot of a PS 4-300-AIO card in the basic unit (4..20)

WordMask Bit mask specifying which channels are to be written

Error Error messages

Description
The WriteAnalogDirect function block allows direct
write access to analog output channels in the basic
unit of the PS 416. The data is not written to the
outputs at the end of a cycle but directly during the
current cycle. This function block therefore allows
fast and direct response to events such as required
in alarm routines. The maximum on/off delay of the
analog cards for the controller should be taken into
account when using this function block.
The Slot input specifies the slot in which the card to
be accessed is fitted. The WordMask input specifies
which channels are to be write accessed on the card.
06/99 AWB 2700-1306 GB

543
 Function Blocks

The bit position determines the channel:

Bit 0 – channel 0
Bit 1 – channel 1
Bit 2 – ...
This therefore enables you to specify channels to be
write accessed as required.
The AnalogOutValues input is used to transfer the
write values. Only the values for the channels
specified in Wordmask are output.
The Error output specifies the error codes:
0 No error
1 Invalid slot
2 No PS 4-300-AIO-400 present on the slot
3 Incorrect channel number requested via mask

06/99 AWB 2700-1306 GB

544
 WriteAnalogDirect

Example “Write analog data direct”

PROGRAM WriteAnalog

VAR
WriteAnalog : WriteAnalogDirect;
AnalogData : ARRAY[0..3] OF UINT;
WriteError : UINT;
END_VAR

LD 1234
ST AnalogData[0] (* Data channel no.0 *)
LD 567
ST Analogdata[1] (* Data channel no.1 *)
CAL WriteAnalog(Slot := 5, (* Card fitted in slot 5 *)
Wordmask := 16#3, (* Write channel no. 0 and no.1 *)
AnalogOutValues := AnalogData
|
WriteError = Error)
LD WriteError
EQ 0
JMPC WRITE_DONE

(* Error handling *)

WRITE_DONE:

(* Further sections of the program *)

END_PROGRAM
06/99 AWB 2700-1306 GB

545
 Function Blocks

PS 416 WriteDirect
Direct Writing to Digital Outputs

Prototype of the function block

Meaning of operands
Mode Access mode

StartAddress Byte or word address of the digital output,

permissible value range:
Bit and byte access: 0 – 127,
Word access: 0 – 126

BitPosition Bit position with bit access

Permissible range: 0 – 7

WriteData Data value to be written

Error Error message

Description
The WriteDirect function block allows direct write
access to digital output cards in the basic rack of the
PS 416-CPU. The data is written directly to the
outputs during the user program cycle rather than at
the start of the cycle. This function block can thus be
used for fast and direct reactions to events, e. g. in
alarm routines. When using this function block,
06/99 AWB 2700-1306 GB

observe the maximum on/off delay of the digital I/O

cards for the PS 416 system.

546
 WriteDirect

The Mode input defines the access type.

Mode = 1: Write a single bit to an output card.
Mode = 2: Write a byte (8 bit) to an output card.
Mode = 3: Write a word (16 bit) to an output card.
The StartAddress and BitPosition inputs address an
output and are dependent on Mode. BitPosition is
only relevant for Mode = 1. Examples:
Mode = 1: StartAddress := 4, Position := 6 ==>
%Q0.0.0.4.6
Mode = 2 StartAddress := 2 ==> %QB0.0.0.2
Mode = 3 StartAddress := 126 ==>
%QW0.0.0.126.
The WriteData input must contain the data value to
write to the output card. The WORD data type allows
individual bits of WriteData to be accessed.
Depending on the Mode the following bits are
relevant:
Mode = 1 WriteData.0
Mode = 2 WriteData.0 - WriteData.7
Mode = 3 WriteData.0 - WriteData.15.
06/99 AWB 2700-1306 GB

547
 Function Blocks

Outputs written by the WriteDirect function block

must be declared in the declaration section of the
user program to allow them to be reset by the
PLC operating system when the user program is
stopped.

Warning
Undeclared outputs written by the WriteDirect
function block can result in hazardous states
of the machine, since they are not
automatically reset in the READY state of the
PLC.
Ensure that the outputs that are written with
“WriteDirect” are declared in the user program
and that the declaration and the values output
with “WriteDirect” are identical.

Error codes at the Error output:

0 No error, WriteData valid
1 Value of Mode input invalid
2 Value of StartAddress input is too large.
3 Value of StartAddress input not an even number
(only Mode = 3)
4 Value of BitPosition input invalid

06/99 AWB 2700-1306 GB

548
 WriteDirect

Invocation of the WriteDirect function block

PROGRAM WriteIO

VAR
WriteEnable AT%I0.0.0.0.1:BOOL;
WriteIODirect :WriteDirect;
WriteData :WORD;
WriteError :UINT;

(* The following declaration ensures that output byte 32 is reset

to a defined state by the PLC operating system if the user program
is stopped. *)
IOByte32 AT %QB0.0.0.32 :USINT;
END_VAR

(*Further parts of the program *)

LD IOByte32
ADD 1
ST IOByte32
...

LD IOByte32
USINT_TO_WORD
ST WriteData

(*Direct write access to the digital I/O. Data is written to I/O

byte 32. This corresponds to the variable declaration %IB0.0.0.32 : USINT;*)
LD WriteEnable
CALC WriteIODirect(Mode := 2,(* Byte access *)
Address := 32, (* Byte address 32*)
BitPosition := , (* Unused *)
WriteData := WriteData
|
WriteError := Error )

LD WriteError
EQ 0
JMPCN WRITE_DONE

WRITE_ERROR:

(*Error handling *)
06/99 AWB 2700-1306 GB

WRITE_DONE:

(*Further parts of the program *)

END_PROGRAM

549
 Function Blocks

WriteMC
Save Data on Memory Card

Prototype of the function block

Meaning of operands
SourceAddress Data buffer with the data to be saved

Strobe Start save operation

SegmentNumber Segment number (0 - n)

DataLength Number of data bytes to be saved

Active Save operation running

MaxSegmentNumber Last possible segment number of the file

Error Error message

Description
The WriteMC function block allows data to be saved
to the PLCs memory card (MC). Together with the
ReadMCFB_ReadMC function block, important
applications of this function block are data backup,
process data acquisition, saving recipe data and/or
saving variables before a program update or the
handing of recipe data.

06/99 AWB 2700-1306 GB

Only insert or remove the memory card when the

PLC power feed is off.

550
 WriteMC

The memory card is addressed by segment number.

The function block can write up to 128 bytes to the
memory card.
To determine the MC file size, call the function block
with DataLength set to “0”. This does not write to the
memory card. MaxSegmentNumber then indicates
the highest segment number in the MC file.
The function block is executed asynchronously of
the user program cycle and can take several program
cycles. The Active output is set during this time.
Error-free completion of the function block is indicat-
ed by the Active output changing to 0 and by 0 at the
Error output.
You can activate several function block instances
simultaneously. They will be processed one after the
other in the order that they were called.
Error codes at the Error output:
0 Function block execution completed without
errors
1 No memory card inserted
2 No access possible due to an online connection
3 No access possible since memory card is
currently being accessed by ReadMC
4 SegmentNumber exceeds the value of
MaxSegmentNumber
5 DataLength is larger than 128 bytes or
SourceAddress is the wrong size
Error codes with PS 4-200/141/151 only:
2 No access possible due to Online connection
3 No access possible due to simultaneous access
via “ReadMC“
06/99 AWB 2700-1306 GB

7 No access possible, MC being used as source

directory.

551
 Function Blocks

Error code with PS 4-300 only

8 The MC was formatted without recipe data range
Error codes with PS 416 only:
10 Memory card type is not SRAM.
11 Memory card is not formatted.
12 Memory card is write-protected.
13 Insufficient free memory on memory card to
create the file “RSDAT.DAT”.
14 File “RSDAT.DAT” does not have the required
minimum size of 128 bytes.
15 Internal error during execution of the function
block.
The following information on the WriteMC function
block only apply to the PS 416 controller:
The data is saved on the memory card in the
MS-DOS file “RSDAT.DAT” and can be read and
processed with a PCMCIA drive. The file is sub-
divided into 128 byte segments and its size is only
limited by the capacity of the memory card used.

06/99 AWB 2700-1306 GB

552
 WriteMC

If a memory card is inserted and the file

“RSDAT.DAT” is not present on the memory card
when the function block is first called, it is created
automatically with a default size of 512 x 128 byte
(64 KByte) and all sectors are initialised with the
value “0xFF”. Other file sizes can be created with the
SetMCFileLength.

The ACTIVE output of these function blocks is

always “0” when used in PS 4-200 and PS 4-150
controllers. The current function block status can
be scanned via the Error output when the function
blocks are called again. If the Error output is “0”,
processing was carried out error-free. If the
output is “3”, the function block is processing. To
refresh the Error output of this function block a
new edge on the Strobe input must be generated.
Otherwise the error message will be kept (with 1
on Strobe) or will be set to 0 (with 0 on Strobe).
06/99 AWB 2700-1306 GB

553
 Function Blocks

Invocation of the function block WriteMC

PROGRAM SAVE
VAR
StrobeSave AT %I0.0.0.0.0 : BOOL;
ActiveSave AT %Q0.0.0.0.0 : BOOL;
ErrorSave : USINT;
FBSaveData : WriteMC;
SegmentNumber : UINT;
DataLength : USINT;
LastSegmentNumber : UINT;
DataArea : ARRAY[0..31] of USINT;
END_VAR

LD ActiveSave
JMPCN CONTINUE

(* Prepare data to save *)

CONTINUE:
LD 47
ST SegmentNumber
LD 32
ST DataLength

(* Write from array DataArea a total of 32 bytes to memory card

segment 47 *)
CAL FBSaveData(Strobe := StrobeSave,
SegmentNumber := SegmentNumber,
DataLength := DataLength,
SourceAddress := DataArea
|
ActiveSave := Active,
LastSegmentNumber := MaxSegmentNumber,
ErrorSave := Error)

LD ErrorSave
EQ 0
JMPC NO_ERROR

(* Error handling *)

NO_ERROR:
06/99 AWB 2700-1306 GB

(* Further parts of user program *)

END_PROGRAM

554
 7 Language Extension

Single-bit access
In the program you can access an individual bit
located in a data element declared as BYTE, WORD
or DWORD and specify the corresponding bit
number, separated by a dot. The bit number,
beginning with '0' for the least significant bit, is
specified:
0..7 in the byte
0..15 in the word
0...31 in the double word
Example
PROGRAM only1bit

VAR
BitPattern1 : BYTE := 2#10101010;
BitPattern2 AT %IW0.0.0.0 : WORD;
END_VAR

(*Copying of bit 15 *)
LD BitPattern2.15 (*from BitPattern2 *)
ST BitPattern1.0 (*to bit 0 of BitPattern1 *)
.
.

END_PROGRAM

FB invocation with direct parameter passing

Two ways of invoking a function block are described
in Chapter 3 from page 67 onwards. The two variants
are defined in accordance with the IEC standard.
06/99 AWB 2700-1306 GB

In addition Moeller offers a further variant whereby

upon invocation of the function block the parameters
are passed directly to all operands used in the
function block concerned. The input operands are

555
 Language Extension

configured together after the CAL command and

then, separated by the | character, the output
operands.
Example
CAL SR_Instance_1(Set1 := ON,
ReSet := OFF
|
Result := Q1)

Direct peripheral I/O access for PS 4-200

and PS 4-300
If the value once updated at the start or end of the
cycle is not to be used for a directly declared input or
output but instead the value at the time of processing
in the user program is used, the following should be
taken into account when declaring these variables
(see also example on page 557):
1. Direct access is only possible for input byte
%IB0.0.0.0 or output byte %QB0.0.0.0
on a bit and / or byte basis.
This restriction only applies to the PS 4-200!
As described in point 3, words and double words
can also be addressed with the PS 4-300.
The entire %I, %Q, %IA, %QA, %IC image of the
can be explicitly addressed.
2. The memory location information for such a
variable includes the additional letter 'P': i. e. for
an input byte %IPB0.0.0.0 and for an output byte
%QPB0.0.0.0.
3. Only BOOL_EXP, BYTE_EXP, SINT_EXP and
USINT_EXP are permitted as data type.
06/99 AWB 2700-1306 GB

The following data types are also permissible for

PS 4-300 only:
WORD_EXP, DWORD_EXP, INT_EXP,
UINT_EXP, DINT_EXP and UDINT_EXP.

556
 The image register is refreshed at the end of a cycle.
The image register of the PS 4-300 is refreshed
immediately.
Example
VAR
Input AT %IP0.0.0.0.0: BOOL_EXP;
Output AT %QPB0.0.0.0: USINT_EXP;
END_VAR

This access method is useful in alarm routines where

as a rule a rapid reaction is required (see also
„CounterAlarm“, Page 256; „EdgeAlarm“, Page 310;
„TimerAlarm“, Page 523).
With the PS 416 it is possible to program direct I/O
access with the function blocks ReadDirect and
WriteDirect.
06/99 AWB 2700-1306 GB

557
 Language Extension

Parameter passing
A Moeller variation of function block calls allows the
direct passing of function block inputs (VAR_INPUT
parameters) and outputs (VAR_OUTPUT parameters)
via instruction sequences in the call. This call
variation is not part of the IEC standard.
With conditional function block calls, the input and
output allocations are only processed if the function
block is called.
Passing of FB input parameters
Before the function block call the instruction
sequence is processed and the sequence result is
assigned to the function block input. Other direct
parameter passing is then carried out and the
function block is called.
Example “Passing of inputs”
(* FUNCTION_BLOCK meanval
VAR_INPUT
Val1 : USINT;
Val2 : USINT;
END_VAR

AR_OUTPUT
Average : USINT;
END_VAR *)

PROGRAM Pou4

VAR
Instance : meanval;
Measval1 AT %IB0.0.0.0 : USINT;
Measval2 AT %IB0.0.0.1 : USINT;
END_VAR

CAL meanval(Val1 := (Measval1

add 2
06/99 AWB 2700-1306 GB

),
Val2 := (Measval2
add 2add 3
)
)

558
 Passing of FB outputs
After the function block is called the instruction
sequence is processed and the sequence result is
assigned to the variables in front of the assignment
operator “:=”. The first operand of the sequence
must be the output parameter of the function block
called.
Example “Passing of outputs”
VAR
Instance : meanval;
Measval1 AT %IB0.0.0.0 : USINT;
Measval2 AT %IB0.0.0.1 : USINT;
Result AT %QB0.0.0.0 : USINT;
Measval : USINT;
END_VAR

CAL meanval(Val1 := Measva1,

Val2 := (Measval2
add 3
)
|
Result := (Average
sub 2
)
)

Passing of function inputs

A Moeller variation of function calls allows the direct
passing of inputs (VAR_INPUT parameters) using
instruction sequences when the function is called.
This call variation is not part of the IEC standard.
The instruction sequence is processed before the
function is called and the sequence result is assigned
to the input directly. Other parameter allocations
are then carried out and the function is called.
The parameter allocations are carried out from left
06/99 AWB 2700-1306 GB

to right.

559
 Language Extension

Example “Connecting inputs of a function”

VAR
a : word;
b : word;
END_VAR;

LD a
SHR (b
WORD_TO_UINT
)

06/99 AWB 2700-1306 GB

560
 Appendix

Sucosoft agreements Keywords

Reserved keywords in Sucosoft
Reserved keywords are character combinations of
the IEC 1131-3 Standard or Sucosoft which have a
defined meaning. These keywords must not be used
as identifiers: for example as variable names, jump
labels or POU names.
Individual special characters such as the semicolon
or the dollar characters must not be used in
identifiers either.
06/99 AWB 2700-1306 GB

561
 Appendix

List of reserved keywords

..._to_... ctd f_edge max sel udint

(all combinations of ctu f_trig mid sema uint
the elementary data ctud false min shiftleftcarry ulint
types) find mod shiftrightcarry until
date for move shl usertype
abs date_and_time from mul shr usint
acos delete function mux sin
action dint function_block ne single var_access
add div neg sint var_external
address do ge not sqrt var_global
and dt getcarryregister sr var_in_out
andn dword gt of st var_input
any on step var_output
any_array else if or sstn
any_bit elsif initial_step ornpriority string while
any_date end_action insert struct with
any_enum end_case int program sub word
any_function_block end_configuratio interval
any_int n iscarry r tan xor
any_num end_for iszero r_edge task xorn
any_real end_function isoverflow r_trig then
any_string end_function_bl ispositive read_only time
array ock isbittrue read_write time_of_day
asin end_if real to
at end_program jmp repeat tod
atan end_repeat jmpc replace tof
end_resource jmpcn resource ton
bool end_step ld ret tp
by end_struct ldn retain transition
byte end_transition le retc true
end_type left retcn trunc
cal end_var len return type
calc end_while limit right
calcn eq lint rol
case exit ln ror
06/99 AWB 2700-1306 GB

concat exp lreal rs

configuration expt log rtc
constant lt
cos lword

562
 Limit values of Sucosoft

Limit values of Sucosoft

PS 4-200 PS 4-300 PS 416

Project management restrictions
Max. number of POUs/Program 256 256 256
Max. length of project names. Project names must be 32 characters 32 characters 32 characters
different within the first eight characters.
Editor restrictions
Max. number of lines in a POU 64 kByte 64 kByte 64 kByte
Max. length of a variable name 64 characters 64 characters 64 characters
Max. length of a POU name 32 characters 32 characters 32 characters
Status display restrictions
Max. number of simultaneously displayable variables approx. 501) – –
Restrictions of the Topology Configurator
Max. number of components per configuration 2) 175 630 753
Max. number of simultaneously selectable 10 10 10
components in the I/O monitor
Restrictions due to the CPU and the compiler
Max. program size including all FBs (Code + Data) 63 kByte 512 kByte CPU 200: 256 kB
CPU 300: 512 kB
CPU 400: 1 MB
Max. code size of a POU in the controller 56 kByte 64 kByte 64 kByte
Max. size of the total of all variables in the main 32000 global 16000 global 16000 global
program and all function blocks 32000/POU local 16 kB/POU local 16 kB/POU local
Max. depth of the instance tree (max. number of 8 16 16
nested instances)
Max. depth of the function block invocation tree 16 16 16
2)
Max. number of instances per program 4000 4000 4000
Max. number of AT declarations 2) 16 kByte 16 kByte 5450
Max. size of an array 8 kByte 16 kByte 16 kByte
Max. number of array dimensions 3 4 4
06/99 AWB 2700-1306 GB

Range of values of an array index 0 to 255 –2147483648 to +2147483647

Max. number of enumerations per type 256 65000 65000
Max. length of a string 253 characters 1024 characters 1024 characters
Max. number of global type definitions 1100 1100 1100

563
 Appendix

PS 4-200 PS 4-300 PS 416

Permissible range of values of the data type TIME +63/-64 days +127/-128 days
23 hrs., 59 min. 23 hrs., 59 min.
59 sec., 999 ms 59 sec., 999 ms
Permissible range of values of the data type DATE 1900-1-1 to 2154-12-31
Max. size of an S 30 program which can be converted 54 kByte no limit
and loaded into the PLC
Max. definable cycle time 255 ms 1000 ms 1000 ms
Recommended program code size of a POU for < 2 kByte < 8 kByte < 8 kByte
efficient on-line processing

1)
Depending on data type. If the limit value is exceeded, “?” will be inserted instead of values.
2)
Restricted also by the PLC main memory available.

Program examples The programming examples presented here are part

LD/FBD of complex control tasks. The used manufacturer
functions and function blocks have been combined
into useful processes. The variable declarations only
contain the variables used in the programming
examples.

06/99 AWB 2700-1306 GB

564
 Program examples LD/FBD

Programming examples of functions

Task 1
The rotation to right of a robot arm is to be halted
when the end position is reached or the Halt button
is pressed.
The following variables are defined:
Value of the variable Actual_Position. The value is the
same as the counter status that is supplied via a
pulse generator.
Value of the variable Reference_Point.
Value of the variable End_Position.
VAR
Act_Position : INT;
Reference_Point : INT;
End_Position : INT;
Halt AT %I0.0.0.0.0 : BOOL;
Motor_ri AT %Q0.0.0.0.0 : BOOL;
END_VAR
06/99 AWB 2700-1306 GB

565
 Appendix

Task 2
The variable Act_Position in task 1 shows the
distance of the robot arm from the reference point as
a pulse number. Eight pulses are equivalent to a 1 cm
movement. In network 0007 the absolute position is
to be output in centimetres. The SHR shift function is
used for converting the pulse number into
centimetres.
Additional declaration:
VAR
Position_in_cm : INT;
END_VAR

06/99 AWB 2700-1306 GB

566
 Program examples LD/FBD

Task 3
A part of the operating elements of an operator
panel is connected with the IB0.0.0.0 input byte.
The program section where the operating elements
are evaluated should only be executed if there is a
different status compared with the previous program
cycle in the operator panel.
VAR
Operator_panel_new AT %IB0.0.0.0 : BYTE;
Operator_panel_old : BYTE;
END_VAR
06/99 AWB 2700-1306 GB

567
 Appendix

Task 4
The robot arm is moved into the Hand operating
mode via bits 0 to 5 of the operating elements listed
in task 3. In this operating mode only one single
process activity may be executed by a short key
stroke. Variable declaration will be completed.
The program is continued from network 0007 task 3.
Additional declarations:
VAR
Automatic AT %I0.0.0.1.6 : BOOL;
Hand AT %I0.0.0.1.7 : BOOL;
Raise_Arm AT %Q0.0.0.1.0 : BOOL;
Lower_Arm AT %Q0.0.0.1.1 : BOOL;
Move_Arm_ri AT %Q0.0.0.1.2 : BOOL;
Move_Arm_le AT %Q0.0.0.1.3 : BOOL;
Close_Clamp AT %Q0.0.0.1.4 : BOOL;
Open_Clamp AT %Q0.0.0.1.5 : BOOL;
Arm_up AT %I0.0.0.1.0 : BOOL;
Arm_down AT %I0.0.0.1.1 : BOOL;
Arm_right AT %I0.0.0.1.2 : BOOL;
Arm_left AT %I0.0.0.1.3 : BOOL;
Clamp_closed AT %I0.0.0.1.4 : BOOL;
Clamp_opened AT %I0.0.0.1.5 : BOOL;
END_VAR

06/99 AWB 2700-1306 GB

568
 Program examples LD/FBD
06/99 AWB 2700-1306 GB

569
570
Appendix

06/99 AWB 2700-1306 GB

 Program examples LD/FBD

Function blocks
A single function block can be programmed in a
network in the LD/FBD editor. There are two ways of
transferring the parameters to the function block:
Entering the variable names or values at the indi-
vidual connection lines directly when calling the
function block where only the parameters for the
relevant operands must be set.
Assigning the variable names or values to the in-
put operands in the networks before calling the
function block and sequencing the output oper-
ands in networks after calling the function block.
06/99 AWB 2700-1306 GB

571
 Appendix

Programming examples of function blocks

Task 5
An error recognised by the monitoring program is
indicated by an acoustic signal and a 1-Hz flashing
light. An acknowledge button switches off the
acoustic signal immediately but not the flashing light
unless the error message is no longer active.
VAR
Error_Edge : R_TRIG ;
Acknow_Edge : R_TRIG ;
Hooter_ON_OFF : SR ;
Pulse_Enable : SR ;
Pulse : TimeGenerator ;
Error : BOOL ;
Acknow_Button AT %I0.0.0.0.1 : BOOL ;
Hooter AT %Q0.0.0.0.0 : BOOL ;
Flashing_Light AT %Q0.0.0.0.1 :BOOL ;
Edge : BOOL ;
Pulse_OFF : BOOL ;
Flashing : BOOL ;
END_VAR

06/99 AWB 2700-1306 GB

572
 Program examples LD/FBD
06/99 AWB 2700-1306 GB

573
 Appendix

Task 6
A conveyor belt is controlled by a motor at the drive
shaft. There are proximity switches at the two drive
shafts which provide at least 5 pulses per second
when the belt is running at the required speed.
A monitoring program outputs an error message if
the number of revolutions is too low after a startup
time of 8 seconds
or
the belt is broken.
With an error message the motor is switched off and
a fault indication is activated.
VAR
Belt_Motor : RS ;
Message : SR ;
Revolutions : TOF ;
Belt_broken : CTUD ;
Startup_Time : TP ;
Acknow_Edge : R_TRIG ;
Motor_ON AT %I0.0.0.0.0 : BOOL ;
OFF AT %I0.0.0.0.1 : BOOL ;
EMERG_STOP AT %I0.0.0.0.2 : BOOL ;
Lamp_Acknow AT %I0.0.0.0.3 : BOOL ;
NS_Drive AT %I0.0.0.0.4 : BOOL ;
NS_2 AT %I0.0.0.0.5 : BOOL ;
Lamp AT %Q0.0.0.0.0 : BOOL ;
Motor AT %Q0.0.0.0.1 : BOOL ;
END_VAR
06/99 AWB 2700-1306 GB

574
 Program examples LD/FBD
06/99 AWB 2700-1306 GB

575
576
Appendix

06/99 AWB 2700-1306 GB

 Program examples LD/FBD

Task 7
An installation report can be created and printed out.
A manually initiated protocol job is executed
immediately or within 24 hours. With a time-
dependent job the time is set via a 4-digit decade
switch which is used to set hours and minutes in
decimal form.
VAR
Clock : PS_GetDateAndTime ;
Job : RS ;
Edge_1 : R_TRIG ;
Edge_2 : R_TRIG ;
TimeValue : ELEMENT_OF_DATE ;
Hours AT %IB0.0.0.0 : BYTE ;
Minutes AT %IB0.0.0.1 : BYTE ;
Time_Job AT %I0.0.0.2.0 : BOOL ;
Immediate_Job AT %I0.0.0.2.1 : BOOL ;
Printing : BOOL ;
END_VAR
06/99 AWB 2700-1306 GB

577
578
Appendix

06/99 AWB 2700-1306 GB

 Program examples LD/FBD
06/99 AWB 2700-1306 GB

579
 Appendix

Task 8
In a paint preparation plant paints are mixed
according to different recipes from various basic
elements and the prepared paint is poured into cans
of different sizes. Selection of an ordered recipe and
a type of can is carried out by setting the corres-
ponding 4-digit order number on a decade switch.
After a button is pushed as confirmation the job goes
into a queue which can manage up to 10 jobs.
If the plant is in status Ready and the jobs are stored
in the queue, the first job is read automatically and
the process is started.
VAR
Converter_1:BCDTo16BitBinary;
Converter_2:_16BitBinaryToBCD;
Queue:FifoW10;
Job AT %IW0.0.0.0:UINT;
Release_Job AT %I0.0.1.0.0:BOOL;
Delete_Jobs AT %I0.0.1.0.1:BOOL;
Display_Current_Job AT%QW0.0.3.0:UINT;
Display_Input_Disable AT %Q0.0.2.0.0:BOOL;
System_Ready: BOOL;
END_VAR

06/99 AWB 2700-1306 GB

580
 Program examples LD/FBD
06/99 AWB 2700-1306 GB

581
582
Appendix

06/99 AWB 2700-1306 GB

 Index

Symbols B
# character 203 BCD_TO_DINT 133
& 40 BCD_TO_INT 133
&N 42 BCD_TO_SINT 133
*_TO_** 114 BCD_TO_UDINT 133
_16Bit_Compare 210 BCD_TO_UINT 133
_16BitBinaryToBCD 212 BCD_TO_USINT 133
_16BitCounter 214 BCDTo16BitBinary 227
_32Bit_Compare 216 BCDTo32BitBinary 229
_32BitBinaryToBCD 218 Bistable data elements 38
_32BitCounter 220 Bistable elements 490
Bit string functions
A Rotation functions 190,
ABS 136 191
ADD Shift functions 194, 195,
Addresses 141 196, 197
Numeric 137 BlockCompare 231
numeric 47 BlockTransfer 236
Time values 139 BOOL_TO_BYTE 124
Addition 47, 99 BOOL_TO_DINT 121
ADDRESS_TO_UINT 135 BOOL_TO_DWORD 124
ADRtoSTR 222, 224 BOOL_TO_INT 121
Alarm BOOL_TO_SINT 121
Disabling 147 BOOL_TO_UDINT 121
Enabling 153 BOOL_TO_UINT 121
Alarm Function Block BOOL_TO_USINT 121
Counter 240, 256 BOOL_TO_WORD 124
Alarm function block BYTE_TO_BOOL 124
Edge-controlled 310 BYTE_TO_DINT 121
AND 40 BYTE_TO_DWORD 124
AND sequence BYTE_TO_INT 121
in FBD 92 BYTE_TO_SINT 121
in IL 40 BYTE_TO_UDINT 121
in LD 79 BYTE_TO_UINT 121
06/99 AWB 2700-1306 GB

ANDN 42, 93 BYTE_TO_USINT 121

Arithmetic operators 47 BYTE_TO_WORD 124
Assignments 36
AT 24, 25 C
CAL 56

583
 Index

CAlarm 240 Constants, Pre-defined 61

CALC 57 Constants, Pre-defined
CALCN 57 constants 61
Check battery via flags 377 convert binary to decimal
Cold Start Retention 245 212, 218
ColdstartRetention 245 Counter
COM 249 decrementing 267
Commands decrementing and incre-
Arithmetic operators 47 menting 269
Assignments 36 incrementing 268
Bistable data elements CounterAlarm 256
38 CounterLE 261
Comparison operators CPUDataExchange 263
50 Create RSDAT.DAT 456
Conditional and uncon- CTD 267
ditional jumps 52 CTU 268
Conditional and uncon- CTUD 269
ditional returns 54 Current result
FBD representation 90 Assign 78, 97
Invocation function Negate 82, 96
blocks 56
Invocation of functions D
58 Data types 7
LD representation 77 Derived 10
load instructions 34 Elementary 7
Logic operators 40 DataScale 271
Comments DATconcat 275
Notation 6 DATE_AND_TIME_TO_
Compare TIME_OF_DAY 128
16-bit values 210 DATE_AND_TIME_TO_DAT
32-bit values 216 E 128
Compare operations 101 DateConcat 277
CompareArray 250 DateSplit 279
Comparison operators 50 DATsplit 281
Complement DE4netDP 283
Bitwise 183 DE4netK 291
Two’s 182 DELETE 145
COMtoSTR 254 Derived data types
06/99 AWB 2700-1306 GB

CONCAT 142, 144 Array 13

CONSTANT 24, 25 Declaration 10
Constants 24 Enumeration 12
Character string 60 Keywords 10
Overview 59 Structure 15

584
 Index

Deserialize 298 END_VAR 22

Diagnostic bit "KOM" 375 EQ 50, 101
DialOrHangup 301 Equivalence function 82
DINT_TO_BCD 132 Exclusive OR sequence
DINT_TO_BOOL 117 in FBD 95
DINT_TO_DWORD 116 in IL 45
DINT_TO_INT 120 in LD 82
DINT_TO_REAL 125
DINT_TO_SINT 120 F
DINT_TO_UDINT 119 F_TRIG 315
DINT_TO_UINT 120 FBD, programming in 90
DINT_TO_USINT 120 FifoBx 317
Direct reading of inputs FifoWx 321
Analog inputs 395 FIND 156
Counter input 398 Frequency inverter 291
Digital inputs 401 Function
Directly represented Application range 65
variables 16 Data type of operands
Declaration 16 114
Disable_Interrupt 147 Example 66
DIV 150 Invocation 58, 65, 105
Addresses 152 Invocation in LD 87
Duration 151 Overloaded 113
Division 49, 100 Parameter transfer 65
Remainder 158 Prototype representati-
DWORD_TO_BOOL 124 on 112
DWORD_TO_BYTE 124 Function block 67
DWORD_TO_DINT 121 Call 27
DWORD_TO_INT 122 Example 69
DWORD_TO_SINT 122 Instance 27, 70
DWORD_TO_UDINT 121 Invocation 88, 106
DWORD_TO_UINT 122 Invocation conditional 57
DWORD_TO_USINT 122 Invocation unconditional
DWORD_TO_WORD 124 56
Parameter transfer 70,
E 88, 107
Edge detection Prototype representati-
Falling edge 315 on 208
06/99 AWB 2700-1306 GB

Rising edge 394 Retentive 25

EdgeAlarm 310 Function blocks
Elementary data types 7 Direct parameter pas-
Enable_Interrupt 153 sing 555
END_TYPE 22 Overview 109, 203

585
 Index

Parameter transfer 571 Enabling 153

Programming examples IsBitTrue 161
572 IsCarry 162
Functions IsOverflow 163
Overview 109, 203 IsPositive 164
Programming examples IsZero 165
565
Type conversion 114 J
JMP 52, 85, 103
G JMPC 53, 86, 104
GE 50, 101 JMPCN 53, 86, 104
Get date and time 379 Jump
GetCarryRegister 158 Conditional 52, 86, 104
GetRealTimeClock 325 Return 54, 86
Global variable 21 Unconditiona 103
Graphical programming Unconditional 52, 85
languages 73 Jump commands
GT 50, 101 in FBD 102
in IL 52
I in LD 84
IEEE_To_Real 326 Jump destination 84, 102
IL sequences, overview 32 Jump label 33, 84
IN_OUT variable 21
IncEncoder 327 K
Input variable 21 Keywords 561
INSERT 159 of variable types 21, 24
Instance 27, 70
Instructions L
Sequences 32 Label 32, 33
Structure 31 LD 34
INT_TO_BCD 132 LD, Programming in 77
INT_TO_BOOL 117 LDN 35
INT_TO_BYTE 116 LE 50, 101
INT_TO_DINT 119 LEFT 166
INT_TO_DWORD 116 LEN 167
INT_TO_REAL 125 LifoBx 331
INT_TO_SINT 120 LifoWx 335
INT_TO_UDINT 119 LIMIT 168
06/99 AWB 2700-1306 GB

INT_TO_UINT 119 Load instructions 34

INT_TO_USINT 120 Local variable 21
INT_TO_WORD 116 Logic operators 40
Interrupt Logic sequences 79, 92
Disabling 147 LT 50, 101

586
 Index

M Arithmetic operators 47
Marker 18 assignments 36
MAX 170 Bistable data elements
Memory card 38
Initialising 456 Comparison operators
Readout 414 50
Save data 427, 550 Conditional and uncon-
MID 172 ditional jumps 52
MIN 174 Conditional and uncon-
Mixed sequences 80 ditional returns 54
MOD 200 343 Invocation function
Modem blocks 56
Establish data connec- Invocation of functions
tion 301 58
Sending data to 446 Load instructions 34
MS_TimeFalling 344 Logic operators 40
MS_TimeRising 347 Overview 29
MUL OR 43
Addresses 179 OR sequence
Multiplication of numeric in FBD 94
data types 176 in IL 43
Numeric 48 in LD 80
Time duration 178 ORN 44
Multiple instancing 314 Output symbols 78, 97
Multiplexer 180 Output variable 21, 78, 98
Multiplication 48, 100 Outputs, writing direct to
Carry 158 543, 546
MUX 180 Overloaded function 113

N P
NE 50, 101 Parameter passing, direct
NEG 182 555
Negation symbol PdpFreezeSync 355
in FBD 92 PdpStationDiag 369
in LD 82 PLC_Message 184
NItoCelsius 350 PLC_ReadClock 186
NItoFahrenheit 352 POU Editor 73
NOT 96, 183 PROFIBUS diagnostic data
06/99 AWB 2700-1306 GB

Numeric 49 369
Program 64
O Program organisation units
Operand 31 5
Operators Comments 6

587
 Index

Structure 5 Counter input 398

Variable declaration 5 Digital inputs 401
Programming examples ReadMC
LD/FBD 564 Memory card
Programming language Readout 404
FBD 90 REAL _TO_ SINT 126
Programming languages REAL_TO_DINT 126
Convert 73 Real_To_IEEE 408
LD 77 REAL_TO_INT 126
Programming rules 32 REAL_TO_UDINT 126
PS_ApplicationHalt 373 REAL_TO_UINT 126
PS_ClearKOMBit 375 REAL_TO_USINT 126
PS_Diagnostic 377 Real-time clock
PS_GetDateAndTime 379 Compare 409
PS_Message 381 Evaluate 325
PS_ReadOSInfo 383 Set 459
PS_SwitchPosition RealTimeClock 409
Operating mode selec- ReloadData 414
tor switch REPLACE 187
Read switch position Reserved keywords 561
385 Reset 39, 83, 99
PSCO 387 RET 54, 86, 104
PTtoCelsius 390 RETAIN 24
PTtoFahrenheit 392 RETC 55, 86, 105
RETCN 55, 87, 105
Q retentive variables 24
Queue 317, 321 Return 54
Conditional 86, 105
R Unconditional 86, 104
R 39 RIGHT 189
R_TRIG 394 ROL 190
Read diagnostic flags 377 ROR 191
Read operating system Rotation functions 190,
information 383 191
Read out date 186 RS 417
Read out time 186 RTC 419
ReadAnalogDirect 395
ReadCounterDirect 398 S
06/99 AWB 2700-1306 GB

ReadDirect 401 S 38
Reading diagnostic flags S_TimeFalling 421
18 S_TimeRising 424
Reading inputs directly SaveData 427
Analog inputs 395 SCO 430

588
 Index

SEL 192 Standard function blocks

Selection 109, 203
Input operand 180, 192 Standard functions 109,
Limiting values 168 203
Maximum 170 Status information 18
Minimum 174 STN 37
SendATCommand 446 String
Sending AT commands Concatenating 142
446 Copy to array 509
Sequence control function Copy to marker range
block 462 507
Sequences Deleting characters from
in FBD 96 145
in LD 79 Determining the length
Serial communication 430 167
Serialize 453 Finding 156
Set 38, 83, 98 Inserting a further 159
SetMCFileLength 456 Removing a sequence of
SetRealTimeClock 459 characters from 172
Sfc_x 462 Replacing characters in
Shift functions 194, 195, a 187
196, 197 Selecting characters
ShiftLeftCarry 194 from left 166
ShiftRightCarry 195 Selection of characters
SHL 196 from right of 189
SHR 197 STRtoADR 507
Single-bit access 555 STRtoCOM 509
SINT_TO_BCD 132 STRUCT 14
SINT_TO_BOOL 117 Structure 14
SINT_TO_DINT 119 SUB 198
SINT_TO_DWORD 116 Addresses 201
SINT_TO_INT 119 Numeric 48
SINT_TO_REAL 125 Time values 199
SINT_TO_UDINT 119 Subtraction 48, 100
SINT_TO_UINT 119 Summation 136
SINT_TO_USINT 119
SINT_TO_WORD 116 T
SR 490 Text from S. 12a 27
06/99 AWB 2700-1306 GB

SR_x 492 TIME_TO_UINT 128

SRB_x 496 TIME_TO_USINT 128
SRW_x 500 TimeConcat 517
ST 36 TimeGenerator 519
Stack register 331, 335 TimePulse 521

589
 Index

Timer USINT_TO_REAL 125

Off-delay 344 USINT_TO_SINT 119
On-delay 347 USINT_TO_UDINT 119
TimeSplit 529 USINT_TO_UINT 119, 120
TODconcat 531 USINT_TO_WORD 116
TODsplit 533
TOF 535 V
TON 537 VAR 21
TP 539 VAR_EXTERNAL 21
TransferArray 541 VAR_GLOBAL 21
Transition 466 VAR_IN_OUT 21
TRUNC 202 VAR_INPUT 21
TYPE 21 VAR_OUTPUT 21
Type conversion functions Variable types
114 Overview use in POUs
26
U Variables 15, 79, 91
UDINT_TO_BCD 132 constant 25
UDINT_TO_BOOL 117 Declaration 20
UDINT_TO_BYTE 116 Directly represented 16
UDINT_TO_DWORD 116, retentive 24
119 Types, Overview 21, 24
UDINT_TO_INT 120 Version number 383
UDINT_TO_REAL 125
UDINT_TO_SINT 120 W
UDINT_TO_USINT 120 WORD_TO_BOOL 124
UDINT_TO_WORD 116 WORD_TO_BYTE 124
UINT_TO_BCD 132 WORD_TO_DINT 121
UINT_TO_BOOL 117 WORD_TO_DWORD 124
UINT_TO_BYTE 116 WORD_TO_INT 121
UINT_TO_DINT 119 WORD_TO_SINT 122
UINT_TO_DWORD 116 WORD_TO_UDINT 121
UINT_TO_INT 119 WORD_TO_UINT 121
UINT_TO_REAL 125 WORD_TO_USINT 122
UINT_TO_SINT 120 WriteAnalogDirect 543
UINT_TO_UDINT 119 WriteDirect 546
UINT_TO_USINT 120 WriteMC 550
UINT_TO_WORD 116 Writing direct
06/99 AWB 2700-1306 GB

USINT_TO_BCD 132 to analog outputs 543

USINT_TO_BYTE 116, 117 to digital outputs 546
USINT_TO_DINT 119
USINT_TO_DWORD 116 X
USINT_TO_INT 119 XOR 45, 95

590
06/99 AWB 2700-1306 GB

XORN 46
Index

591
592
06/99 AWB 2700-1306 GB