Training Curriculum

TIA Portal Module 004

Basics of FC Programming
with SIMATIC S7-1500

139
 TIA Portal Module 004

Table of contents
1 Goal................................................................................................................................................. 141
2 Prerequisite...................................................................................................................................... 141
3 Required hardware and software..................................................................................................... 141
4 Theory.............................................................................................................................................. 142
4.1 Operating system and application program..............................................................................142
4.2 Organization blocks.................................................................................................................. 142
4.3 Process image and cyclic program processing........................................................................144
4.4 Functions.................................................................................................................................. 145
4.5 Function blocks and instance data blocks................................................................................145
4.6 Global data blocks.................................................................................................................... 146
4.7 Library-compatible code blocks................................................................................................ 147
4.8 Programming languages.......................................................................................................... 148
5 Task................................................................................................................................................. 149
6 Planning........................................................................................................................................... 149
6.1 EMERGENCY STOP................................................................................................................ 149
6.2 Manual mode – Conveyor motor in manual mode....................................................................149
7 Structured step-by-step instructions................................................................................................. 150
7.1 Retrieve an existing project...................................................................................................... 150
7.2 Create a new tag table............................................................................................................. 151
7.3 Create new tags within a tag table............................................................................................153
7.4 Import "Tag_table_sorting_station"........................................................................................... 154
7.5 Create function FC1 "MOTOR_MANUAL" for the conveyor motor in manual mode.................156
7.6 Define the interface of function FC1 "MOTOR_MANUAL".......................................................157
7.7 Program FC1: MOTOR_MANUAL............................................................................................ 159
7.8 Program organization block OB1 – Control of the forward belt tracking in manual mode.........165
7.9 Program organization block OB1 – Control of the backward belt tracking in manual mode.....170
7.10 Save and compile the program................................................................................................. 171
7.11 Download the program............................................................................................................. 172
7.12 Monitor program blocks............................................................................................................ 173
8 Checklist.......................................................................................................................................... 176

140
 TIA Portal Module 004

BASICS OF FC PROGRAMMING
1 Goal
In this chapter, you will get to know the basic elements of a control program – the
organization blocks (OBs), functions (FCs), function blocks (FBs) and data blocks
(DBs). In addition, you will be introduced to library-compatible function und function block
programming. You will get to know the Function Block Diagram (FBD) programming
language and use it to program a function (FC1) and an organization block (OB1).

2 Prerequisite
This chapter builds on the hardware configuration of SIMATIC S7 CPU1516F-3 PN/DP.
However, other hardware configurations that have digital input and output cards can be used.

3 Required hardware and software

1 Engineering station: requirements include hardware and operating system
(for additional information, see Readme on the TIA Portal Installation DVDs)

2 SIMATIC STEP 7 Professional software in TIA Portal – as of V13

3 SIMATIC S7-1500/S7-1200/S7-300 controller, e.g. CPU 1516F-3 PN/DP –

Firmware as of V1.6 with memory card and 16DI/16DO and 2AI/1AO
Note: The digital inputs should be fed out to a control panel.

4 Ethernet connection between engineering station and controller

2 SIMATIC STEP 7
Professional (TIA
1 Engineering station
Portal) as of V13

4 Ethernet connection

Control panel
3 SIMATIC S7-1500 controller
141
 TIA Portal Module 004

4 Theory
4.1 Operating system and application program
Every controller (CPU) contains an operating system, which organizes all functions and
processes of the CPU that are not associated with a specific control task. The tasks of the
operating system include the following:
 Performing a warm restart
 Updating the process image of the inputs and outputs
 Cyclically calling the user program
 Detecting interrupts and calling interrupt OBs
 Detecting and handling errors
 Managing memory areas
The operating system is an integral component of the CPU and comes pre-installed.
The user program contains all functions that are necessary for executing your specific
automation task. The tasks of the user program include the following:
 Checking the basic requirements for a warm restart using startup OBs
 Processing of process data, i.e. activation of output signals as a function of the input
signal states
 Reaction to interrupts and interrupt inputs
 Error handling during normal program execution

4.2 Organization blocks

Organization blocks (OBs) form the interface between the operating system of the controller
(CPU) and the application program. They are called from the operating system and control the
following operations:
 Cyclic program processing (e.g. OB1)
 Startup characteristics of the controller
 Interrupt-driven program processing
 Error handling
A project must have an organization block for cyclic program processing at a minimum.
An OB is called by a start event as shown in Figure 1. In addition, the individual OBs have
defined priorities so that, for example, an OB82 for error handling can interrupt the cyclic OB1.

142
 TIA Portal Module 004

Figure
1: Start events in the operating system and OB call
When a start event occurs, the following reactions are possible:
 If an OB has been assigned to the event, this event triggers the execution of the assigned
OB. If the priority of the assigned OB is greater than the priority of the OB that is currently
being executed, it is executed immediately (interrupt). If not, the assigned OB waits until
the higher-priority OB has been completely executed.
 If an OB is not assigned to the event, the default system reaction is performed.
Table 1 gives a couple of examples of start events for a SIMATIC S7-1500, their possible OB
number(s) and the default system reaction in the event the organization block is not present in
the controller.

Start event Possible OB Default system

numbers reaction

Startup 100,  123 Ignore

Cyclic program 1,  123 Ignore
Time-of-day interrupt 10 to 17,  123 -
Update interrupt 56 Ignore
Scan cycle monitoring time 80 STOP
exceeded once

Diagnostic interrupt 82 Ignore

Programming error 121 STOP

IO access error 122 Ignore

Table 1: OB numbers for various start events

143
 TIA Portal Module 004

4.3 Process image and cyclic program processing

When the cyclic user program addresses the inputs (I) and outputs (O), it does not query the
signal states directly from the input/output modules. Instead, it accesses a memory area of the
CPU. This memory area contains an image of the signal states and is called the process
image.
The cyclic program processing sequence is as follows:
1. At the start of the cyclic program, a query is sent to determine whether or not the
individual inputs are energized. This status of the inputs is stored in the process image of the
inputs (PII). In doing so, the information 1 or "High" is stored for energized inputs and the
information 0 or "Low" for de-energized inputs.
2. The CPU now executes the program stored in the cyclic organization block. For the
required input information, the CPU accesses the previously read process image of the
inputs (PII) and the results of logic operation (RLOs) are written to a so-called process
image of the outputs (PIQ).
3. At the end of the cycle, the process image of the outputs (PIQ) is transferred as the
signal state to the output modules and these are energized or de-energized. The sequence
then continues again with Item 1.

1. Save status of inputs in PII.

PLC program in the PII

program memory
2. Processing the Local data
program instruction-by- 1st instruction
instruction with access 2nd instruction
3rd instruction Bit memory
to PII and PIQ
4th instruction
... Data blocks

PIQ
Last instruction

3. Transfer status from the PIQ to the outputs.

Figure 2: Cyclic program processing

Note: The time the CPU needs for this sequence is called cycle time. This depends, in turn,
on the number and type of instructions and the processor performance of the controller.

144
 TIA Portal Module 004

4.4 Functions
Functions (FCs) are logic blocks without memory. They have no data memory in which
values of block parameters can be stored. Therefore, all interface parameters must be
connected when a function is called. To store data permanently, global data blocks must be
created beforehand.
A function contains a program that is executed whenever the function is called from another
code block.
Functions can be used, for example, for the following purposes:
 Math functions – that return a result dependent on input values.
 Technological functions – such as individual controls with binary logic operations.
A function can also be called several times at different points within a program.

Organization block
Main [OB1]

Calls the MOTOR_MANUAL

MOTOR_MANUAL [FC1]
[FC1] function
Contains a program for
controlling a conveyor
in manual mode, for
example.

The function has no

memory.

Figure 3: Function with call from organization block Main [OB1]

4.5 Function blocks and instance data blocks

Function blocks are code blocks that store their input, output and in-out tags as well as static
tags permanently in instance data blocks, so that they are available after the block has been
executed. For this reason, they are also referred to as blocks with "memory".
Function blocks can also operate with temporary tags. Temporary tags are not stored in the
instance DB, however. Instead, they are only available for one cycle.
Function blocks are used for tasks that cannot be implemented with functions:
 Whenever timers and counters are required in the blocks.
 Whenever information must be saved in the program, such as pre-selection of the
operating mode with a button.

145
 TIA Portal Module 004

Function blocks are always executed when called from another code block. A function block
can also be called several times at different points within a program. This facilitates the
programming of frequently recurring complex functions.
A call of a function block is referred to as an instance. Each instance of a function block is
assigned a memory area that contains the data that the function block uses. This memory is
made available by data blocks created automatically by the software.
It is also possible to provide memory for multiple instances in one data block in the form of a
multi-instance. The maximum size of instance data blocks varies depending on the CPU. The
tags declared in the function block determine the structure of the instance data block.

Instance data block

MOTOR_AUTO_DB1
Organization block [DB1] as memory
Main [OB1] for the call of
Function block
function block
Calls function block MOTOR_AUTO [FB1]
MOTOR_AUTO
MOTOR_AUTO [FB1] [FB1]
together with its Contains a program for
instance data block controlling a conveyor
MOTOR_AUTO_DB1 in automatic mode, for
[DB1] example
The function block
uses instance data
block
MOTOR_AUTO_DB1
[DB1] as memory in
this call.

Figure 4: Function block and instance with call from organization block Main [OB1]

4.6 Global data blocks

In contrast to logic blocks, data blocks contain no instructions. Rather, they serve as memory
for user data.
Data blocks thus contain variable data that is used by the user program. You can define the
structure of global data blocks as required.
Global data blocks store data that can be used by all other blocks (see Figure 5). Only the
associated function block should access instance data blocks. The maximum size of data
blocks varies depending on the CPU.

146
 TIA Portal Module 004

Function_10
Global DB
Access for all blocks
(DB_Global)

Function_11

Function_ Instance DB Access only for function data block_12

block_12 (DB_Instance)

Figure 5: Difference between global DB and instance DB.

Application examples for global data blocks are:

 Saving of information about a storage system. "Which product is located where?"
 Saving of recipes for particular products.

4.7 Library-compatible code blocks

A user program can be created with linear or structured programming. Linear programming
writes the entire user program in the cycle OB, but is only suitable for very simple programs for
which other less expensive control systems, such as LOGO!, can now be used.
Structured programming is always recommended for more complex programs. Here, the
overall automation task can be broken down into small sub-tasks in order to implement a
solution for them in functions and function blocks.
In this case, library-compatible logic blocks should be created preferentially. This means that
the input and output parameters of a function or function block are defined generally and only
supplied with the current global tags (inputs/outputs) when the block is used.

147
 TIA Portal Module 004

Figure 6: Library-compatible function with call in OB1

4.8 Programming languages

The available programming languages for programming functions are Function Block Diagram
(FBD), Ladder Logic (LAD), Statement List (STL) and Structured Control Language (SCL). For
function blocks, the GRAPH programming language is additionally available for programming
graphical step sequences.
The Function Block Diagram (FBD) programming language will be presented in the
following.
FBD is a graphical programming language. The representation is based on electronic
switching systems. The program is mapped in networks. A network contains one or more logic
operation paths. Binary and analog signals are linked by boxes. The graphical logic symbols
known from Boolean algebra are used to represent the binary logic.
You can use binary functions to query binary operands and to logically combine their signal
states. The following instructions are examples of binary functions: "AND operation", "OR
operation" and "EXCLUSIVE OR operation". These are shown in Figure 7.

Figure 7: Binary functions in FBD and associated logic table

148
 TIA Portal Module 004

You can thus use simple instructions, for example, to control binary outputs, evaluate edges
and execute jump functions in the program.
Program elements such as IEC timers and IEC counters provide complex instructions.
The empty box serves as a placeholder in which you can select the required instruction.
Enable input EN (enable)/ Enable output ENO (enable output) mechanism:
 An instruction without EN/ENO mechanism is executed independent of the signal state at
the box inputs.

 Instructions with EN/ENO mechanism are only executed if enable input "EN input has
signal state "1". When the box is processed correctly, enable output "ENO" has signal
state "1". As soon as an error occurs during the processing, the "ENO" enable output is
reset. If enable input EN is not connected, the box is always executed.

5 Task
The following functions of the sorting station process description will be planned, programmed
and tested in this chapter:
 Manual mode – Conveyor motor in manual mode

6 Planning
The programming of all functions in OB1 is not recommended for reasons of clarity and
reusability. The majority of the program code will therefore be moved into functions (FCs) and
function blocks (FBs). The decision on which functions are be moved to FCs and which is to
run in OB 1 is planned below.

6.1 EMERGENCY STOP

The EMERGENCY STOP does not require a separate function. Just like the operating mode,
the current state of the EMERGENCY STOP relay can be used directly at the blocks.

6.2 Manual mode – Conveyor motor in manual mode

Manual mode of the conveyor motor is to be encapsulated in a function (FC)
"MOTOR_MANUAL". On the one hand, this preserves the clarity of OB1. On the other hand, it
enables reuse if another conveyor belt is added to the station. Table 2 lists the planned
parameters.

Input Data Comment

type
Manual_mode_active BOOL Manual mode activated
Pushbutton_manual_mode BOOL Pushbutton manual mode conveyor on
Enable_OK BOOL All enable conditions OK

Safety_shutoff_active BOOL Safety shutoff active, e.g. emergency stop

pressed

Output

Conveyor_motor_manual_mode BOOL Control of the conveyor motor in manual

mode
Table 2: Parameters for FC "MOTOR_MANUAL"

149
 TIA Portal Module 004

Output Conveyor_motor_manual_mode is ON as long as Pushbutton_manual_mode is

pressed, manual mode is activated, the enable conditions are OK and the safety shutoff is not
active.

7 Structured step-by-step instructions

You can find instructions on how to carry out planning below. If you already have a good
understanding of everything, it will be sufficient to focus on the numbered steps. Otherwise,
simply follow the detailed steps in the instructions.

7.1 Retrieve an existing project

 Before we can start programming the function (FC) "MOTOR_MANUAL", we need a
project with a hardware configuration (e.g.
SCE_EN_012_101_Hardware_Configuration_S7-1516F_R1502.zap). To retrieve an
existing project that has been archived, you must select the relevant archive with 
Project  Retrieve in the project view Confirm your selection with Open. ( Project 
Retrieve  Select a .zap archive  Open)

 The next step is to select the target directory where the retrieved project will be stored.
Confirm your selection with "OK". ( Target directory  OK)

150
 TIA Portal Module 004

7.2 Create a new tag table

 In the project view, navigate to the  PLC tags of your controller and create a new tag
table by double-clicking  Add new tag table.

 Rename the tag table you just created as "Tag_table_sorting_station" ( right-click

"Tag_table_1"  "Rename"  Tag_table_sorting_station).

151
 TIA Portal Module 004

 Open this tag table with a double-click. ( Tag_table_sorting_station)

152
 TIA Portal Module 004

7.3 Create new tags within a tag table

 Add the name Q1 and confirm the entry with the Enter key. If you have not yet created
additional tags, TIA Portal now automatically assigns data type "Bool" and address %I0.0
(I 0.0) ( <Add>  Q1  Enter).

 Change the address to %Q0.0 (Q 0.0) by entering this directly or by clicking the drop-
down arrow to open the Addressing menu, changing the operand identifier to Q and
confirming with Enter or by clicking the check mark. ( %I0.0  Operand identifier  Q
 )

 Enter the "Conveyor motor M1 forwards fixed speed" comment for the tag.

153
 TIA Portal Module 004

 Add a new Q2 tag in line 2. TIA Portal has automatically assigned the same data type as
in line 1 and has incremented the address by 1 to %Q0.1 (Q0.1). Enter the comment
"Conveyor motor M1 backwards fixed speed".

( <Add>  Q2  Enter  Comment  Conveyor motor M1 backwards fixed speed)

7.4 Import "Tag_table_sorting_station"

 To insert an existing symbol table, right-click on an empty field of the created
"Tag_table_sorting_station". Select "Import file" in the shortcut menu.

( Right-click in an empty field of the tag table  Import file)

 Select the desired symbol table (e.g. in .xlsx format) and confirm the selection with
"Open".

( SCE_EN_020-100_Tag_table_sorting_station…  Open)

 When the import is finished, you will see a confirmation window and have an opportunity
to view the log file for the import. Click  OK.

154
 TIA Portal Module 004

 You can see that some addresses have been highlighted in orange. These are duplicate
addresses and the names of the associated tags have been numbered automatically to
avoid confusion.

 Delete the duplicate tags by selecting the lines and pressing the Del key on your
keyboard or by selecting "Delete" in the shortcut menu.

( Right-click on selected tags  Delete)

 You now have a complete symbol table of the digital inputs and outputs in front of you.
Save your project under the name 032-100_FCProgramming.

( Project  Save as ...032-100_FCProgramming  Save)

155
 TIA Portal Module 004

7.5 Create function FC1 "MOTOR_MANUAL" for the conveyor

motor in manual mode
 In the PLC programming section of the portal view, click "Add new block" to create a new
function.

( PLC programming  Add new block  )

 Rename your new block to: "MOTOR_MANUAL", set the language to FBD and keep
automatic assignment of the number. Select the "Add new and open" check box. You are
then taken automatically to your created function block in the project view.Click "Add".

( Name: MOTOR_MANUAL Language: FBD  Number: Automatic  Add new

and open  Add)

156
 TIA Portal Module 004

7.6 Define the interface of function FC1 "MOTOR_MANUAL"

 If you selected "Add new and open", the project view opens with a window for creating the
block you just added.

 You can find the interface description of your function in the upper section of your
programming view.

157
 TIA Portal Module 004

 A binary output signal is needed for controlling the conveyor motor. For this reason, we
first create local output tag #Conveyor_motor_manual_mode of the "Bool" type. Enter
comment "Control of the conveyor motor in manual mode" for the parameter.

( Output: Conveyor_motor_manual_mode  Bool  Control of the conveyor motor in

manual mode)

 Add parameter #Manual_mode_active as the input interface under Input and confirm the
entry with the Enter key or by exiting the entry field. Data type "Bool" is assigned
automatically. This will be retained. Next, enter the associated comment "Manual mode
activated".

( Manual_mode_active  Enter  Bool  Manual mode activated)

 Add parameters #Pushbutton_manual_mode, #Enable_OK and #Safety_shutoff_active

as additional binary input parameters under Input and check their data types. Add
descriptive comments.

158
 TIA Portal Module 004

 For purposes of program documentation, assign the block title, a block comment and a
helpful network title for Network 1.

( Block title: Motor control in manual mode  Network 1: Control of the conveyor motor
in manual mode)

7.7 Program FC1: MOTOR_MANUAL

 Below the interface description, you see a toolbar in the programming window with
various logic functions and below that an area with networks. We have already specified
the block title and the title for the first network there. Programming is performed within the
networks using individual logic blocks. Distribution among multiple networks helps to
preserve the clarity of the program. In the following, you will get to know the various ways
you can insert logic blocks.

 You can see a list of instructions you can use in the program on the right side of your
programming window. Under  Basic instructions  Bit logic operations, find function –
[=] (Assignment) and use a drag-and-drop operation to move it to Network 1 (green line
appears, mouse pointer with + symbol).

( Instructions  Basic instructions  Bit logic operations  –[=])

159
 TIA Portal Module 004

 Now use drag-and-drop to move your output parameter #Conveyor_motor_manual_mode

onto <??.?> above the block you just inserted. The best way to select a parameter in the

interface description is by "grabbing" it at the blue symbol .

( Conveyor_motor_manual_mode)

160
 TIA Portal Module 004

 This determines that the #Conveyor_motor_manual_mode parameter is written by this

block. Still missing, however, are the input conditions so that this actually happens. For
this, use drag-and-drop to move input parameter #Manual_mode_active to the left side of
the assignment block.

( Manual_mode_active)

 The input of the assignment block will also be logically combined with other parameters
by an AND logic operation. To do this, first click the input of the block to which
#Manual_mode_active is already connected, so that the input line has a blue background.

161
 TIA Portal Module 004

 Click the icon in your logic toolbar to insert an AND logic operation between the
#Manual_mode_active tag and your assignment block.

 Double-click the second input of the & logic operation <??.?> and enter the letter "P" in
the field that appears in order to see a list of available tags starting with "P".Click the
#Pushbutton_manual_mode tag and apply with  Enter.

( &- block  <??.?>  P  #Pushbutton_manual_mode  Enter)

Note: When assigning tags in this way, there is a risk of a mix-up with the global tags from the
tag table. The previously presented procedure using drag and drop from the interface
description should therefore be used preferentially.

162
 TIA Portal Module 004

 To ensure that the output can only be controlled when the enable conditions are met and
the safety shutoff is not active, the #Enable_OK and #Safety_shutoff_active input tags
are logically combined with the AND logic operation. To do this, click twice on the yellow

star of your AND block to add two additional inputs.

 Add input tags #Enable_OK and #Safety_shutoff_active to your newly created inputs of
the AND block.

 Negate the input connected to parameter #Safety_shutoff_active by selecting it and

clicking .

163
 TIA Portal Module 004

 Do not forget to click . The finished function "MOTOR_MANUAL" [FC1] in

FBD is shown below.

 Under "General" in the properties of the block, you can change the "Language" to LAD
(Ladder Logic) (Properties  General  Language: LAD)

 The program has the following appearance in LAD.

164
 TIA Portal Module 004

7.8 Program organization block OB1 – Control of the forward belt

tracking in manual mode
 Before programming organization block "Main [OB1]", we switch the programming
language to FBD (Function Block Diagram). To do so, first click on "Main [OB1]" in the
"Program blocks" folder.

( CPU_1516F[CPU 1516F-3 PN/DP  Program blocks  Main [OB1]  Switch

programming language  FBD)

 Open the "Main [OB1]" organization block with a double-click.

165
 TIA Portal Module 004

 Assign Network 1 the name "Control conveyor tracking forward in manual/jog mode"

( Network 1:... Control conveyor motor forwards in manual mode)

 Use drag-and-drop to move your "MOTOR_MANUAL [FC1]" function onto the green line
in Network 1.

166
 TIA Portal Module 004

 A block with the interface you defined and connections EN and ENO are inserted in
Network 1.

 To insert an AND before input parameter "Enable_OK", select this input and insert the

AND by clicking the icon in your logic toolbar ( ).

167
 TIA Portal Module 004

 Click the yellow star of the AND block to add another input ( ).

 To connect the block to the global tags from "Tag_table_sorting_station", we have two
options:

 Either select the "Tag_table_sorting_station" in the project tree and use drag-and-drop to
move the desired global tag from the Details view to the interface of FC1
( Tag_table_sorting_station  Details view.  -SO2  Manual_mode_active)

168
 TIA Portal Module 004

 Or, enter the starting letters (e.g. "-S") of the desired global tag for <??.?> and select the
global input tag "-S0" (%I0.2) from the displayed list ( Manual_mode_active  -S 
-S0).

 Insert the other input tags "-S3", "-K0", "-B1", "-S4" and "-A1" and insert output tag "-Q1"
(%Q0.0) at output "Conveyor_motor_manual_mode".

 Negate the querying of input tags "-S0", "-S4" and "-A1" by selecting them and clicking

( -S0   -S4   -A1  ).

169
 TIA Portal Module 004

7.9 Program organization block OB1 – Control of the backward

belt tracking in manual mode
 Assign Network 2 the name "Control conveyor motor backwards in manual mode" and
insert your "MOTOR_MANUAL [FC1]" function using drag-and-drop, as you did
previously in Network 1.

 Connect your function as shown here. You obtain the following result in the FBD
(Function Block Diagram) programming language.

170
 TIA Portal Module 004

 The result in the LAD (Ladder Logic) programming language has the following
appearance.

7.10 Save and compile the program

 To save your project, select the button in the menu. To compile all blocks,

click the "Program blocks" folder and select the icon for compiling in the menu

(  Program blocks  ).

171
 TIA Portal Module 004

 The "Info", "Compile" area shows which blocks were successfully compiled.

7.11 Download the program

 After successful compilation, the complete controller with the created program, as
previously described in the modules for hardware configuration, can be downloaded

( ).

172
 TIA Portal Module 004

7.12 Monitor program blocks

 The desired block must be open for monitoring the downloaded program. The monitoring

can be activated/deactivated by clicking the icon. ( Main [OB1]  )

Note: The monitoring here is signal-related and controller-dependent. The signal states at the
terminals are indicated with TRUE or FALSE.

173
 TIA Portal Module 004

 The "MOTOR_MANUAL" [FC1] function called in the "Main [OB1]" organization block can
be selected directly for "Open and monitor" after right-clicking ( "MOTOR_MANUAL"
[FC1]  Open and monitor).

Note: The monitoring here is function-related and controller-independent. The actuation of

sensors and the station status are shown here with TRUE or FALSE.

174
 TIA Portal Module 004

 If a particular point of use of the "MOTOR_MANUAL" [FC1] function is to be monitored,

the call environment can be selected using the icon (  Call environment 
OK)

175
 TIA Portal Module 004

8 Checklist
No. Description Completed

1 Compiling successful and without error message

2 Download successful and without error message

Switch on station (-K0 = 1)

Cylinder retracted / Feedback activated (-B1 = 1)
EMERGENCY OFF (-A1 = 1) not activated
3
MANUAL mode (-S0 = 0)
Activate conveyor manual mode conveyor forward (-S3 = 1)
then conveyor motor forwards fixed speed (-Q1 = 1)

4 Same as 3 but activate EMERGENCY OFF (-A1 = 0)  -Q1 = 0

5 Same as 3 but AUTO mode (-S0 = 1)  -Q1 = 0

6 Same as 3 but switch off station (-K0 = 0)  -Q1 = 0

7 Same as 3 but cylinder not retracted (-B1 = 0)  -Q1 = 0

Switch on station (-K0 = 1)

Cylinder retracted / Feedback activated (-B1 = 1)
EMERGENCY OFF (-A1 = 1) not activated
8
MANUAL mode (-S0 = 0)
Activate conveyor manual mode reverse (-S4 = 1)
then conveyor motor backwards fixed speed (-Q2 = 1)

9 Same as 8 but activate EMERGENCY OFF (-A1 = 0)  -Q2 = 0

10 Same as 8 but AUTO mode (-S0 = 1)  -Q2 = 0

11 Same as 8 but switch off station (-K0 = 0)  -Q2 = 0

12 Same as 8 but cylinder not retracted (-B1 = 0)  -Q2 = 0

Same as 8 but also activate manual mode conveyor forwards

13
(-S3 = 1)  -Q1 = 0 and -Q2 = 0

14 Project successfully archived

176