Translated from Russian to English - www.onlinedoctranslator.

com

EN and ENO for complex operations

KKOOPP

AAWWLL

FFUUPP

SIMATIC S7 Date: 11/5/2005 Informations- und Trainings-Center

Knowledge for automation
Siemens AG 1998. All rights reserved. Date: STOE_3d.13

EN and ENO In complex operations, such as multiplication or division, the BR bit of the
in complex status word is also used as an error bit. If, for example, the overflow bit (OV,
operations OVERFLOW-BIT) is set during multiplication, the output will be RLO = "0" and
ENO = 0 (BR = 0). The middle figure shows the implementation of this function
with an error message as an STL program.

Training Center ST-7STOE

für Automatisierungs- und Antriebstechnik Chapter 3 - 13/16 Programmable Blocks in STEP 7
 Exercise 3.1: Parameterizable FCs (Creation)

Program as Program as
non-parameterizable parameterizable
block FC20 block

A I 1.2
R M 40.0
A I 1.3
FP M 40.1
S M 40.0
A M 40.0
A M 10.3
O
AN M 40.0
A I 1.3
= Q 8.3
(= Q 4.3)

SIMATIC S7 Date: 11/5/2005 Informations- und Trainings-Center

Knowledge for automation
Siemens AG 1998. All rights reserved. Date: STOE_3d.14

Statement of the problem You must write a program for the message function as a parameterized block.
The figure shows part of the description section and part of the program. If
the instruction with an absolute operand was written, for example, as A I1.2, it
will now be written as A Quittieren.

Execution Enter function FC 20 in S7-Programm UEBUNG of the STOE project ,

• Write a program in FC 20,
• Save FC 20,
• You transfer the HW station configuration (System Date folder) to the CPU.
In doing so, you will have access to the clock marker.

Training Center ST-7STOE

für Automatisierungs- und Antriebstechnik Chapter 3 - 14/16 Programmable Blocks in STEP 7
 Exercise 3.2: Parameterized FCs (Call)
1.
Call
FC 20

I1.3 Stoereingang Meldespeicher M 20.0

I1.2 Quittieren Flankenmerker M 20.1
M 10.3 Blinktakt Anzeige Q 8.3 (Q 4.3)

2.
Call
FC 20

I1.4 Stoereingang Meldespeicher M 20.2

I1.3 Quittieren Flankenmerker M 20.3
M 10.3 Blinktakt Anzeige Q 8.4 (Q 4.4)

SIMATIC S7 Date: 11/5/2005 Informations- und Trainings-Center

Knowledge for automation
Siemens AG 1998. All rights reserved. Date: STOE_3d.15

Statement of the problem Call FC 20 in OB 1 twice with different current parameters. Test the function.

Execution Enter two new networks into OB 1.

• Organize both FC 20 calls as shown in the figure,
• Download blocks FC20 and OB1 to the PLC,
• Try the feature.

Training Center ST-7STOE

für Automatisierungs- und Antriebstechnik Chapter 3 - 15/16 Programmable Blocks in STEP 7
 Exercise 3.3: Parameterizable FBs

Functional block FB 20

SIMATIC S7 Date: 11/5/2005 Informations- und Trainings-Center

Knowledge for automation
Siemens AG 1998. All rights reserved. Date: STOE_3d.16

Statement of the problem For storing Flankenmerkers and Meldespeichers, static variable values
should be used, which are located in the DB instance belonging to the FB.
This has the advantage that markers do not need to be used for storage.

The FC 20 program must now be implemented in the FB 20 function block.

Execution Program in S7-Programm UEBUNG FB 20 with the same function as FC 20,

• Replace both calls to FC 20 in OB 1 with calls to FB 20.

(A 4.3)

(A 4.4)

• Load blocks FB 20, DB 20, DB 21 and OB 1 into the CPU,

• Test the function.

Training Center ST-7STOE

für Automatisierungs- und Antriebstechnik Chapter 3 - 16/16 Programmable Blocks in STEP 7
 Checking the installation software

SIMATIC S7 Date: 11/5/2005 Informations- und Trainings-Center

Knowledge for automation
Siemens AG 1998. All rights reserved. Date: STOE_5d.1

Content
Page
Selecting the operating mode ................................................................................................................ 2
Types of launch ....................................................................................................................... 3
Mode switch..................................................................................................................... Reset and new 4
start using the mode switch.................................................................... Selecting the operating 5
mode by software................................................................................... Reset with PG 6
.................................................................................................................... 7
Loading the User Program into the CPU . ... . ... 8
9
10
11
12
13
14
.......................................................................... 15
Example of a software error ............................................................................................... 16
Reading the Diagnostic Buffer .............................................................................................. 17
Interpreting Error Messages ........................................................................................... Opening an 18
Error Block ...............................................................................................……..… Exercise 5.3: Finding 19
Errors That Cause the CPU to STOP ........................................................... Exercise 5.4: Using Error 20
OBs ............................................................................... 21
Exercise 5.5: Estimating Battery Errors .......................................................................... 22
Exercise 5.6: Troubleshooting Logical Programming Errors.................................................... 23

Training Center ST-7STOE

für Automatisierungs- und Antriebstechnik Chapter 5 - 1/23 Checking the installation software
 Selecting the operating mode

SIMATIC S7 Date: 11/5/2005 Informations- und Trainings-Center

Knowledge for automation
Siemens AG 1998. All rights reserved. Date: STOE_5d.2

Transitions between The reason for transitions between operating modes is commands in
operating modes the program or user intervention.

From RUN to STOP The transition "from RUN to STOP" is carried out in the following cases:
• Loading the user program into the CPU
• Loading hardware configuration into CPU
• CPU reset
• User memory compression

From STOP to RUN- This transition causes the CPU to process the startup OB100 and only then
NEW START change the operating mode to RUN. This transition is required in the
following cases:

• After CPU reset

• Loading the user program into the CPU in STOP mode
• U-STACK or B-STACK overflows
• After fixing the error in the program that put the CPU into STOP
• When the set time for restart is exceeded
• After insertion from an additional peripheral module

From STOP to RUN- This type of transition can only be made by an S7-400 with an unchanged
RESTART program from the STOP mode. In this case, the CPU processes OB101 and only
then switches to RUN mode.

Training Center ST-7STOE

für Automatisierungs- und Antriebstechnik Chapter 5 - 2/23 Checking the installation software
 New start Types of launch Restart
New start Restart
manual: STOP --> RUN and for S7-400 Prerequisite: Restart is parameterized manually:
CRST is on STOP --> RUN and WRST is on
automatic: network on automatic: network is on and WRST is on

Displays are removed Processed by OB 101

process,
non-remanent M, T, Z
The rest of the cycle is processed

Processed by OB 100
PIQ is removed (parameterized)

Unblocking outputs
Yes
Specified time
STOR exceeded?
Reading PII
No
Unblocking outputs,
Processed by OB 1
PII reading

Processing OB 1 and at the end

Issuing PIQ to modules
PIQ issuance

SIMATIC S7 Date: 11/5/2005 Informations- und Trainings-Center

Knowledge for automation
Siemens AG 1998. All rights reserved. Date: STOE_5d.3

Introduction SIMATIC S7 has two types of start-up: new start and repeated start (the latter
only in S7-400 and the corresponding parameterization). During start-up, the
start-up OB 100 and OB 101 are processed, in which, for example, the
necessary preliminary actions are programmed.

During launch:

• No time or event processing is possible,

• Timers are made relevant,
• The working time counter is working,
• Digital outputs are blocked.

New start At a new start, the process display and the parameterized non-remanent
markers, timers and counters are first deleted. Then the program in OB 100 is
processed, if it exists. This is followed by a full cycle with reading of PII and the
beginning of processing from the 1st command in OB 1.

Restart The significant difference from a fresh start is that the process display,
markers, timers, counters are not deleted andsoftware processing continues
from where it was interrupted. After the end of the residual cycle, for safety
reasons, the display of the output process can be deleted (parameterized).

When automatically restarting after switching on the network, a time value can
be parameterized that defines the maximum network downtime. During this
time, a restart is possible. If it is exceeded, the CPU remains in the STOP state.

Training Center ST-7STOE

für Automatisierungs- und Antriebstechnik Chapter 5 - 3/23 Checking the installation software
 Mode switch

RUN-P

RUN

STOP

MRES

SIMATIC S7 Date: 11/5/2005 Informations- und Trainings-Center

Knowledge for automation
Siemens AG 1998. All rights reserved. Date: STOE_5d.4

Operating modes The following operating modes are available:

CPU • RUN-P with the right to access the user program, i.e. the program can be
changed
• RUN with access protection i.e. read-only access
• STOP
• MRES - reset

Indication The CPU switches from STOP to RUN mode if no errors are detected.

Training Center ST-7STOE

für Automatisierungs- und Antriebstechnik Chapter 5 - 4/23 Checking the installation software
 Reset and restart using the mode switch
works

RUN-P RUN-P RUN-P RUN-P RUN-P

RUN RUN RUN RUN RUN

STOP STOP STOP STOP STOP

MRES MRES MRES MRES MRES

1. Turn the operation mode switch to STOP.

2. Turn it to the MRES position and hold it there until the STOP LED flashes
slowly twice.
3. Turn it back to STOP and as quickly as possible back to MRES (Reset
has occurred if the STOP LED is flashing rapidly)
4. Select the RUN-P position (a new start occurs when the switch is turned
from STOP to RUN/RUN-P)

SIMATIC S7 Date: 11/5/2005 Informations- und Trainings-Center

Knowledge for automation
Siemens AG 1998. All rights reserved. Date: STOE_5d.5

Reset Before switching to RUN mode after reset, a hardware test is performed. If
there is a MEMORY-CARD, the program is copied from it to the working
memory.

New start When a new start is made, the process mapping and non-remanent data are
deleted. Then, after reading the process mapping, a new cycle begins.

Training Center ST-7STOE

für Automatisierungs- und Antriebstechnik Chapter 5 - 5/23 Checking the installation software
 Selecting the operating mode programmatically

SIMATIC S7 Date: 11/5/2005 Informations- und Trainings-Center

Knowledge for automation
Siemens AG 1998. All rights reserved. Date: STOE_5d.6

Show and change Using the programming device, the operating mode is displayed and
operating mode changed as shown below.
It makes no difference whether you are offline or online. Follow
these steps:

• Select S7-Programm or in "Accessible Nodes" object MPI = 2

• Open the corresponding Dialogbox with the menu commandPLC ->Operating
Mode. The current operating mode is shown.
• Press the corresponding button of the operating mode you want to
change to.

Training Center ST-7STOE

für Automatisierungs- und Antriebstechnik Chapter 5 - 6/23 Checking the installation software
 Reset with PG

SIMATIC S7 Date: 11/5/2005 Informations- und Trainings-Center

Knowledge for automation
Siemens AG 1998. All rights reserved. Date: STOE_5d.7

Introduction When the CPU is reset, all "old" blocks are deleted from memory. Reset can
only occur if the CPU is in STOP mode. The following actions are performed
during reset:

• All user data - except MPI parameters - are deleted

• CPU breaks all existing connections
• If EPROM (boot memory) is present, the CPU copies its contents to the RAM
area (working memory) after reset.

What remains? Reset does not work on:

• Contents of the diagnostic buffer

• MPI parameter (MPI address) of the CPU

Training Center ST-7STOE

für Automatisierungs- und Antriebstechnik Chapter 5 - 7/23 Checking the installation software
 Loading the user program into the CPU

Download button
The user can load the entire
project or selected blocks into
the CPU. To do this, they need
to be marked
and press the button or select PLC-
>Download from the menu

SIMATIC S7 Date: 11/5/2005 Informations- und Trainings-Center

Knowledge for automation
Siemens AG 1998. All rights reserved. Date: STOE_5d.8

Loading the programWhen testing a user program, it is often required that user
a separate block was loaded into the CPU in STOP or RUN-P mode.

If a program is loaded into the CPU in RUN-P mode, the CPU switches to
STOP mode if the block parameters have changed or if there is no called
block.

Function Individual blocks are always loaded into the boot memory (RAM), while
executable parts of blocks are loaded into the working memory.

CPU memory
Program-
motor
Loading...
Loading Working
zochnaya
programs memory
memory
In CPU RAM
Executable
parts
programs
RAM

Training Center ST-7STOE

für Automatisierungs- und Antriebstechnik Chapter 5 - 8/23 Checking the installation software
 Exercise 5.1: Loading the User Program

Step Conducting Result

1 Switch CPU with key The CPU goes into STOP
select the operating mode in STOP. state.

3 Open S7-Programm DEMO by S7-Programm and user program

clicking on the “Blocks” are open.
object.

4 Select a menu itemPLC -> PG connection with AG (PLC) is established

Download and all blocks are loaded into AG

SIMATIC S7 Date: 11/5/2005 Informations- und Trainings-Center

Knowledge for automation
Siemens AG 1998. All rights reserved. Date: STOE_5d.9

Introduction With the Simatic Manager you can load a block or several blocks
simultaneously into the CPU. If the user program consists of more than one
block - OB, FC and FB -, the entire program must be loaded in the STOP
operating mode. This ensures that there are no problems such as loading a
block that calls another block that is not yet in the CPU. If all blocks are loaded
into the CPU, the CPU must be set back to the RUN operating mode.

Possibilities when loading into the CPU with SIMATIC Manager:

• The entire program is postponed
• One or more blocks from one program are transferred at the same
time
• One or more blocks are transferred from different programs

Possibilities when loading into CPU from LASD/STL/FBD editor:

• The block opened in the editor is moved
• If more than one block is open, each block is transferred separately

Position of the CPU operating mode switch and boot capability (in
CPU):
• STOP position (CPU in STOP) All download options are
available
• RUN position (CPU to RUN) Upload not allowed
• RUN position (CPU in STOP) Upload not allowed
• Position RUN-P (CPU in STOP) All download options are
available
• RUN-P position (CPU in RUN) All download options are
available

Pay attention to the order in which the blocks are loaded.

Training Center ST-7STOE

für Automatisierungs- und Antriebstechnik Chapter 5 - 9/23 Checking the installation software
 Exercise 5.2: Functional Test for Troubleshooting
errors in the program

Inductive sensors Photocell

INI 1 INI 2 INI3LS1

S1 S2 S3
M1 Indicators
Motor H1 H2 H3 S4

SIMATIC S7 Date: 11/5/2005 Informations- und Trainings-Center

Knowledge for automation
Siemens AG 1998. All rights reserved. Date: STOE_5d.10

Turning on The device is switched on by switch I 0.0 and switched off by I 0.1 Output Q 8.1
(Q 4.1) reports the status. The switched on device can then be set to the
operating mode: manual or automatic.

Manual mode The manual operating mode is selected by the signal state "0" in
works I 0.4 front in I 0.5. In manual mode, the product can be moved in the direction of the
last stage of installation using switch I0.2 or in the opposite direction using switch
I0.3, until the corresponding contact is closed. At the same time, indicator H1
flashes as a warning for the service personnel.

Auto Automatic operation mode can be selected for the switched-on

operating mode device by the signal state "1" in I 0.4 and the front in I 0.5.
Place the product in front of INI 1. The tape starts moving after a delay (1s) in the
direction of the last stage of installation. Before the start of movement, a siren
sounds and the H1 lamp shines while the tape continues to move. If the product
passes the photocell, the tape stops.
Here the product is weighed, this is simulated by an analog value. If the product is
lighter than 2000 or heavier than 2500 units, then it is a reject and it is
transported to the left. When the belt moves, the H1 lamp shines again. The
product will not be recorded as suitable in the list of manufactured products for
this shift. If the weight is within the tolerance range, then this product will be
recorded in the list of the set shift.
This process is repeated until 5 good products are produced. Then the H4
indicator lights up continuously and the conveyor is blocked until it is
acknowledged by the S4 switch in the model.
The shift progress is shown on the digital indicator. On request (switch I 0.7) the
current weight can be reported.
In the digital setter, the shift number is set with the right 2 digits, and the number
of products with the left digits. If the shift number is incorrect, Q 8.6. (Q4.6) flashes.
On request with I 0.6, the set number of products is compared with the total
number of copies of all shifts. When executed, Q 8.7 (Q4.6) flashes.

Training Center ST-7STOE

für Automatisierungs- und Antriebstechnik Chapter 5 - 10/23 Checking the installation software
 Types of errors

Types of errors Example CPU response

External Wire break in STOP if the error and diagnostics OB is

error analog input not loaded in the module
block unlocked

Internal Error STOP if the error and diagnostics OB is

error ADC conversions not loaded in the module
unlocked

Systemic Hardware error STOP

error MPI connections

Error in Call STOP if error OB is not loaded

program non-existent
user block

Filming and Removing the module in S4-400 STOP if the OB is not loaded errors
installation in RUN mode
modules in S7-
400

SIMATIC S7 Date: 11/5/2005 Informations- und Trainings-Center

Knowledge for automation
Siemens AG 1998. All rights reserved. Date: STOE_5d.11

Type of error In the table you can see the different types of errors that can occur in the
SIMATIC S7 system.
Each of these errors represents a diagnostic event that generates a
diagnostic signal to the CPU. This results in the error being written to the
diagnostic buffer and in the CPU going into STOP mode if no error
organization block has been programmed.

Training Center ST-7STOE

für Automatisierungs- und Antriebstechnik Chapter 5 - 11/23 Checking the installation software
 Synchronous errors

Synchronous errors correspond to a specific command in the

program

Type of error Example OV

mistakes

Software The called block OB 121 is not loaded into the

error CPU

Access error Direct access to a defective or OB 122

non-existent module

SIMATIC S7 Date: 11/5/2005 Informations- und Trainings-Center

Knowledge for automation
Siemens AG 1998. All rights reserved. Date: STOE_5d.12

Synchronous errorsThese errors occur directly during command processing.

For example, the instruction CALL FC 10 is programmed in the program.
The called block FC 10 is, however, missing.

OB errors With the help of the error OB, it is possible to determine the occurrence of an error. If there
is no error OB in the CPU, then in case of an error, the CPU goes to STOP.

Training Center ST-7STOE

für Automatisierungs- und Antriebstechnik Chapter 5 - 12/23 Checking the installation software
 Asynchronous errors
Asynchronous errors cannot be assigned to any specific section of the
program, i.e. they occur asynchronously with respect to the program's
operation.

Type of error Example OB errors

Temporary error Exceeded max. Cycle time OB 80

Power supply error The buffer battery has failed OB 81

Diagnostic signal Broken input wire in module with OB 82

diagnostics

Pick-up/Put-in signal The signal module is removed from the S7-400 in OB 831)
operating mode

CPU hardware error Bad signal levels in MPI connection OB 841)

Software error Error updating process display area OB 85

sequences (defective module)
1)only at
S7-400
1)
Error in the carrier Defective power supply in the decentralized OB 86
2)no stop
modules peripheral module carrier
without OB errors

Communication Wrong telegram header OB 87

mistakes

SIMATIC S7 Date: 11/5/2005 Informations- und Trainings-Center

Knowledge for automation
Siemens AG 1998. All rights reserved. Date: STOE_5d.13

Introduction The table shows asynchronous errors.

Time Error By default (standard) the maximum cycle time is set to 150 ms. If the cycle
continues for more than 150 ms, a time error occurs. If this error occurs twice
in a row, the CPU goes into STOP.

Error If the buffer battery is missing or discharged, and in the S7-400

nutrition additionally if one of the batteries is missing.
24 V power supply in the central basket or expansion basket.
Unlike other types of error, a CPU without a corresponding error block remains
in the RUN state and this is indicated by the red error LED in the CPU.

Diagnostic Blocks with diagnostics, such as analog blocks, can generate an alarm signal
error in the event of an error.
The block must be parameterized in such a way that diagnostics must be
enabled.

Pickup error/ Occurs when removing or installing blocks in

installations the S7-400 automation system.

Hardware errorINS7-400 detects errors in the MPI connection on the K-bus or

connecting the CPU of decentralized peripherals.

Software errorOccurs when the display process is updated. sequences

Media error Occurs in block carriers, in remote automation systems or decentralized

modules periphery stations
.
Communication It occurs in S7-300 when the header of the received global data telegram or
error data blocks is incorrect. In S7-400 there are other reasons, such as the
transmitter failing to send a synchronization message.

Training Center ST-7STOE

für Automatisierungs- und Antriebstechnik Chapter 5 - 13/23 Verifying the Installation Software
 Using Organization Blocks for Errors

· To doCPU is error-tolerant, you can place an empty

organization block corresponding to the error

· You can program the desired response into the error OB for this
error

· SFC 46 puts the CPU into STOP state

· In the OB the error is placed at startup information that allows for a

more detailed error and that can be evaluated programmatically

· Description of the error codes are inON-LINE help or in the

manual for system and standard functions

SIMATIC S7 Date: 11/5/2005 Informations- und Trainings-Center

Knowledge for automation
Siemens AG 1998. All rights reserved. Date: STOE_5d.14

Usage Please note the rules for using error organization blocks.

Start informationThe descriptive part of each organizational block defines

temporary variables in which the operating system provides startup
information. In startup information, the operating system provides additional
information about why the OS was called.
The starting information of OV 81 is shown as an example.

The OB81_FLT_ID variable has the following values: B#16#21: At

least a buffer battery in the central
the device is discharged (missing) (BATTF)
B#16#22: Battery voltage in the central unit
reduced (BAF).
B#16#23: 24V power supply failure in the central unit.
B#16#31: At least the buffer battery in
the expansion device is discharged (missing)
B#16#32: Battery voltage in the expansion device
lowered
B#16#33: 24V power supply failure in the expansion device.

Training Center ST-7STOE

für Automatisierungs- und Antriebstechnik Chapter 5 - 14/23 Checking the installation software
 Example of an organizational block of errors

SIMATIC S7 Date: 11/5/2005 Informations- und Trainings-Center

Knowledge for automation
Siemens AG 1998. All rights reserved. Date: STOE_5d.15

Statement of the problem As a result of battery failure, an error notification should occur on the
operator's console, and a notification should also occur after changing the
battery.

Description In case of power supply errors, for example, battery failure, the operating
system calls OB 81 once. After the error is corrected, OB 81 is called again.

In the program example, the variable OB81_FLT_ID is evaluated to determine

whether the battery has failed. In this case, the variable contains the value
22H. The result of the comparison is stored in the marker M 81.1.

Error notification should occur when the battery fails (incoming event) and
after the error is cleared (outgoing event).

The variable OB81 _ EV _ CLASS contains the following information:

• B#16#39 coming event

• B#16#38 passing event.

As a result of evaluating these variables, the auxiliary feedback marker will be

set. It is implemented in M 81.0. In the program cycle, it is necessary to
connect the auxiliary marker M81.0 with the clock marker and output the
result. The output shines then until the battery is discharged or absent.

Training Center ST-7STOE

für Automatisierungs- und Antriebstechnik Chapter 5 - 15/23 Checking the installation software
 Example of a software error

Program structure

Error block

SIMATIC S7 Date: 11/5/2005 Informations- und Trainings-Center

Knowledge for automation
Siemens AG 1998. All rights reserved. Date: STOE_5d.16

Software In the upper part of the figure you see the program structure of the
mistakes erroneous program. In OB 1 the function FC 1 is called.
In FC 1, the marker word MW 10 must be stored in the data block DB 10. The
data block DB 10 is not present in the CPU. Since there is no error OB, the CPU
goes into STOP mode.
Finding an error After an error occurs, open the diagnostic buffer. To do this, do:

• Select SIMATIC Manager

• Select S7-Program
• Use the menu itemPLC -> Module Information
• Click on the bookmarkDiagnostic Buffer

Training Center ST-7STOE

für Automatisierungs- und Antriebstechnik Chapter 5 - 16/23 Checking the installation software