3.

4 Sequence control and process diagnosis SICAR Standard

Disclaimer

Because of the variety of uses for SICAR described in this publication, those responsible for the use of

SICAR must satisfy themselves that all necessary steps have been taken to assure that each use meets all

performance and safety requirements, including any applicable laws, regulations, codes and standards.

The illustrations, charts, sample programs and layout examples shown in this guide are intended solely for

purposes of example. Since there are many variables and requirements associated with any particular

installation Siemens does not assume responsibility or liability (to include intellectual property liability) for

actual use based upon the examples shown in this publication.

Reproduction of the contents of this copyrighted manual, in whole or in part, without the written permission of

Siemens, is prohibited.

Manual page 1 / 89 Edition: 2012-04

 3.4 Sequence control and process diagnosis SICAR Standard

Table of contents

1. Introduction 4

2. Sequence block overview 4

3. Sequence block (FB1001 – FB1128) 7

3.1 Data-declaration of sequence FB 7
3.2 Sequence block structure 7
3.2.1 Branch distributor 7
3.2.2 Permanent step 8
3.2.3 Selective step 9
3.2.4 Return to step 1 10
3.2.5 Internal conditions of permanent-step and selective-step 11
3.3 Structure of the selective step 12
3.3.1 Manual conditions 13
3.3.2 Automatic conditions 14
3.3.3 Additional automatic conditions 15
3.3.4 Behavior of the variables in the sequential control automatic mode 17
3.3.5 Watchdog time - #Sequence.TWD_Setpoint 18
3.3.6 Waiting time - #Sequence.TWA_Setpoint 21
3.3.7 Branching - #Sequence.Step_n_plus1 23
3.3.8 Hold function - #Sequence.Hold_in_Step_n 24
3.4 Sequence output block (FC1001 – FC1128) 27
3.4.1 Basic functions of sequence output block 27
3.4.2 Sequence call 28
3.4.3 Sequence output 29
3.4.4 One action (output) in several steps 29
3.4.5 Control a Tec-Unit block 30
3.5 Programming limitations for sequencer 31
3.6 Allowed conditions, operands and addressing 32
3.7 Representation on HMI 34
3.8 Multilingual network commentaries for diagnosis at the HMI 35
3.8.1 Add a 3rd language 38
3.9 Operation modes of the sequence blocks 40
3.10 Sequence data block (DB1001-DB1128) 43
3.11 Representation of a sequence block 45

4. Message block 46
4.1 Structure of the message block 46
4.2 Programming limitations for message block 48
4.3 Allowed conditions, operands and addressing 49
4.4 Representation HMI 50
4.5 Call of the message block 52

5. HMI – Sequence diagnosis screen 53

5.1 Interface PLC -HMI 53
5.2 Sequence diagnosis 54
5.2.1 Overview screen 54

Manual page 2 / 89 Edition: 2012-04

 3.4 Sequence control and process diagnosis SICAR Standard

5.2.2 Sequence overview 55

5.2.3 Detailed diagnosis: STL representation 56
5.2.4 Detailed diagnosis: LAD representation 57
5.2.5 Inching 59
5.2.6 Synchronisation 61
5.2.6.1 Manually synchronisation on HMI 61
5.2.6.2 Automatically synchronisation in the PLC 62
5.2.7 Sequence Set Step 63
5.3 Message block diagnosis 65
5.3.1 Detailed diagnosis: STL representation 66
5.3.2 Detailed diagnosis: LAD representation 67

6. Generating of diagnosis data for “Sequence diag screen” 68

6.1 Structure of Textfiles (Language dependent) 71
6.2 Procedure ASCII languages 71
6.2.1 Multi Panel 71
6.2.2 PC 72
6.3 Procedure Unicode languages 73
6.3.1 Multi Panel 73
6.3.2 PC 77

7. Procedure to generate information for the “Detail diagnosis” 78

7.1 Install the Tool SICARGen on your PC. 78
7.2 Activate XML-Import/Export in WinCC flexible 2008 SP1 HF5 / SP2 78
7.3 General function of SICARGen 78
7.4 Procedure with an integrated WinCC flexible project 79
7.4.1 Settings in SICARGen 79
7.4.2 Additional user steps 82
7.5 Procedure with a not integrated WinCC flexible project 83
7.5.1 Settings in SICARGen 83
7.5.2 User action 84
7.5.3 Tool action 86
7.5.4 Further user action 87

Manual page 3 / 89 Edition: 2012-04

 3.4 Sequence control and process diagnosis SICAR Standard

1. Introduction
This document describes the function of the sequence engine, the message block and the diagnosis screen
in the HMI.

2. Sequence block overview

The sequence block FB1000 covers the following functions:

Sequence control management of 128 sequence blocks executed in parallel, with up to 128
steps per sequence block

Management of the operation modes automatic, manual and inching mode

Synchronising of the sequence blocks to the actual state of the installation

Organising and monitoring of the sequence for the automatic and manual mode

This sequence block has been designed for a linear structure. Branchings can be programmed.
The sequence block has two interlock levels. One for automatic and inching mode and one for
manual mode.
Per sequence block one permanent-step can be programmed, it’s conditions are valid for all steps.

Manual page 4 / 89 Edition: 2012-04

 3.4 Sequence control and process diagnosis SICAR Standard

Block overview:

FC986 FB1128
86
:
FB1001
: FC1128

FC1001 FB1000 Sequence

block
UC FC1001
Sequence Sequence DB1128
UC FC1002 output managment

DB1001
UC FC1003

Sequence-DB
:

The following definitions have been established for the individual sequences 1-128:

Sequence - FC = sequence number + 1000

Sequence - FB = sequence number + 1000
Sequence - DB = sequence number + 1000
Sequence - operating mode byte in DB 1000 = sequence number

Sequence 1:
FC1001 Call of block FB1000 and command output
FB1001 Sequence block with up to 128 sequences
DB1001 Sequence management

Sequence 128:
FC1128 Call of block FB1000 and sequence output
FB1128 Sequence block with up to 128 steps
DB1128 Sequence management

Manual page 5 / 89 Edition: 2012-04

 3.4 Sequence control and process diagnosis SICAR Standard

Software structure of the sequence block:

The structure of the sequence with the interlocks and transitions are programmed in the sequence - FBs.
Depending on the operating mode (automatic, inching, manual) of the sequence, the sequence
administration block FB1000 processes the programmed interlocks and the transition condition, and forms
the sequence stepmarker. The actions are executed with the stepmarker stored in the sequence DB. These
actions are programmed in the sequence FC after calling FB1000.

FB 1004

L
#Sequence.Branchdistributor
JL Branchdistributor
BEU
JU
PERM
JU
S001
JU
S002 Permanentstep
:
FC 1004 JU
S00n
FB 1000 BEU: BEU
CALL FB1000,
DB1004
PERM:
Seq_cascade_no:= 4 #Sequence.ILOCK_Auto Selektive step
Waiting_time:=10
Watchdog_time:=20 #Sequence.ILOCK_no_Sync
DB1004
BEU

S001:
#Sequence.ILOCK_Auto
#Sequence.TRANS_Auto

#Sequence.ILOCK_no_Sync
„programming
actions“

BE

Manual page 6 / 89 Edition: 2012-04

 3.4 Sequence control and process diagnosis SICAR Standard

3. Sequence block (FB1001 – FB1128)

3.1 Data-declaration of sequence FB

The internal programming will be done with symbolic variables. Therefore it is necessary to declare the
UDT999 in the declaration-part of the sequence-FB as a static variable with the symbolic name “Sequence“

3.2 Sequence block structure

3.2.1 Branch distributor

In the first network of the sequence FB, a branch distributor must be programmed before the interlocks. In
the branch distributor, the permanent step (JU PERM) must be called first and then the selective steps.

Example:

Network 1: Jump distributor

L #Sequence.Branchdistributor
JL BEU
JU PERM
JU S001
JU S002

JU S00n
BEU: BEU

Manual page 7 / 89 Edition: 2012-04

 3.4 Sequence control and process diagnosis SICAR Standard

3.2.2 Permanent step

The permanent step is always processed before the jump to the active step (SELECTIVE step). It must be
programmed in every sequence block. Conditions are programmed here that apply for all steps in this
sequence. If there are no such conditions for a sequence, only a "BEU" command (block end) has to be
programmed in the permanent step.

In the permanent-step the following conditions can be programmed:

Manual Interlock #Sequence.ILOCK_Manual

Automatic Interlock; no synchronization #Sequence.ILOCK_no_Sync

Automatic Interlock #Sequence.ILOCK_Auto
Immediate fault #Sequence.SET_Error
Watchdog time stop #Sequence.TWD_Stop
Waiting time stop #Sequence.TWA_Stop

The conditions that are not programmed are internally preset with status 1.

The step starts from the jump mark „PERM“ and ends with „BEU“ before the jump mark of the next step.
All conditions can be programmed in one network. To program the sequence in ladder diagram you also
have the possibility to program one separate network for each condition.
The results of the logic operations from the permanent step are stored in the sequence block and ANDED
with the results of the logic operations from the selective step.

Example:

Manual page 8 / 89 Edition: 2012-04

 3.4 Sequence control and process diagnosis SICAR Standard

3.2.3 Selective step

Only one step (selective step) of the steps specified in the jump distributor is processed. The following
conditions can be programmed in the selective step:

Interlock manual #Sequence.ILOCK_Manual

Limit manual #Sequence.LIMIT_Manual

Interlock automatic #Sequence.ILOCK_Auto

Transition automatic #Sequence.TRANS_Auto

Interlock automatic ;no synchronization #Sequence.ILOCK_no_Sync

Interlock automatic, synchro + no diagnostics #Sequence.EXT_SYNC
Interlock automatic, no synchro + no diagnostics #Sequence.EXT_INT
Immediate fault #Sequence.SET_Error
Watchdog time stop #Sequence.TWD_Stop
Waiting time stop #Sequence.TWA_Stop

Every step starts from the jump mark of the step and ends with a „BEU“ before the jump mark of the next
step.

In every step a branching and a waiting time and a watchdog time additionally can be set and called.

Manual page 9 / 89 Edition: 2012-04

 3.4 Sequence control and process diagnosis SICAR Standard

3.2.4 Return to step 1

In the last network a return to step 1 has to be programmed.

Manual page 10 / 89 Edition: 2012-04

 3.4 Sequence control and process diagnosis SICAR Standard

3.2.5 Internal conditions of permanent-step and selective-step

In every sequence administration block a permanent-step and a selective-step are fundamentally executed.
The conditions of permanent-step and selective-step are connected by FB 1000 status „&“. I.e. the
conditions of the permanent-step are applicable for all selective-steps of the sequence.

Perm Step #Sequence.ILOCK_Manual

& ILOCK-M
Selektiv Step #Sequence.ILOCK_Manual

Perm step #Sequence.ILOCK_no_Sync

Perm step #Sequence.ILOCK_Auto

------------------------------------------------------------------------------
Selektiv step #Sequence. ILOCK_no_Sync
&
Selektiv step #Sequence.ILOCK_Auto
ILOCK-A Step n
Selektiv step #Sequence.EXT_SYNC

Selektiv step #Sequence.EXT_VER

Manual page 11 / 89 Edition: 2012-04

 3.4 Sequence control and process diagnosis SICAR Standard

3.3 Structure of the selective step

Automatic mode is subdivided into 2 parts (ILOCK-A und TRANS-A).
In the first part (ILOCK-A ) the interlocks are programmed. In the second part (TRANS-A) the transition are
programmed. If the transition is fulfilled the sequence is jumped to the next step. . In manual mode there is
no transition, therefore the term Limit (LIMIT-H) was chosen. A step must be terminated with BEU.

Example:
Manual mode

Movement-
buttons from Visu

Limit conditions

Automatic / Inching mode Crash

interlocks

Transition
conditions

Manual page 12 / 89 Edition: 2012-04

 3.4 Sequence control and process diagnosis SICAR Standard

3.3.1 Manual conditions

Interlock manual - #Sequence.ILOCK_Manual

All interlock conditions (crash interlocks).for the safe execution of an action has to be programmed in the
variable #Sequence.ILOCK_Manual.

Characteristics (behavior in the sequential control):

Log. state for step output: 1bin

Example:

Limit manual - #Sequence.LIMIT_Manual

The limit manual contains the feedback signals of the actions executed at step output. If
#Sequence.LIMIT_Manual is fulfilled, the step is completed -> step output flag goes to 0bin.

Characteristics (behavior in the sequential control):

log. state if programming not carried out: preset with 1bin

log. state for step output: 0bin

Example:

Manual page 13 / 89 Edition: 2012-04

 3.4 Sequence control and process diagnosis SICAR Standard

3.3.2 Automatic conditions

If automatic mode is selected, the sequence engine process the active step.

Interlock automatic - #Sequence.ILOCK_Auto

The variable #Sequence.ILOCK_Auto contains all inputs of the movements to be made in this step.
They are used for interlocking and the unique synchronization of this step.

Properties (behavior in the sequential control):

log. state if programming not carried out preset with 1bin

log. state for step output 1bin
Participation in the synchronization Yes
Automatic diagnostics after expiry of the watchdog time

Example:

Transition automatic - #Sequence.TRANS_Auto

The variable #Sequence.TRANS_Auto contains the feedback of the actions executed at step output. If
#Sequence.TRANS_Auto is fulfilled, the step is completed and the step output flag becomes 0bin. In
automatic mode, the next step is enabled.

Characteristics (behavior in the sequential control):

log. state if programming not carried out preset with 1bin

log. state for step output 0bin
Participation in the synchronization Yes
Automatic diagnostics (TRANS = 0bin) - after expiry of the watchdog time

Example:

Manual page 14 / 89 Edition: 2012-04

 3.4 Sequence control and process diagnosis SICAR Standard

3.3.3 Additional automatic conditions

Enable hardware - #Sequence.ILOCK_no_Sync

The difference to #Sequence.ILOCK_Auto is that the variable #Sequence.ILOCK_no_Sync is not taken

into account at synchronization. #Sequence.ILOCK_no_Sync can be used for conditions that cannot be
derived from the sequence of the machine , e.g. associated fuses, ready signals, and signals from personnel
protection equipment that must not participate in the synchronization.

Characteristics (behaviour in the sequential control):

log. state if programming not carried out: preset with 1bin
log. state for step output: 1bin
Participation in the synchronization: No
Automatic diagnostics after expiry of the watchdog time

Example:

External synchronization conditions - #Sequence.EXT_SYNC

The difference to #Sequence.ILOCK_Auto is that #Sequence.EXT_SYNC influences the watchdog time.

You can use signals from "other sequences" for unique synchronization of a sequence, e.g. after a WAIT
step, (e.g. End Welding, Part in Tool / no part in Tool)

Characteristics (behavior in the sequential control):

log. state if programming not carried out preset with 1bin
log. state for step output 1bin
Participation in the synchronization Yes
Automatic diagnostics No
Watchdog time 0bin -> watchdog time stopped

Example:

Manual page 15 / 89 Edition: 2012-04

 3.4 Sequence control and process diagnosis SICAR Standard

External interlock conditions - #Sequence.EXT_INT

The difference to #Sequence.ILOCK_Auto is that #Sequence.EXT_INT is not taken into account at

synchronization and it affects the sequence of the watchdog time.
All signals not designed to result in automatic diagnostics in this sequence (watchdog time is stopped) are
programmed in this program branch. These are signals of external sequences that must be fulfilled before
step output results (interlock conditions, e.g. tool settings, etc.). It must be ensured that these signals are
programmed at another point (sequence controller) and that they result there in a diagnostics entry (initial
value) in the event of a fault.

Characteristics (behavior in the sequential control):

log. state if programming not carried out preset with 1bin

log. state for step output 1bin
Participation in the synchronization No
Automatic diagnostics No
Watchdog time 0bin -> Watchdog time stopped

Example:

Manual page 16 / 89 Edition: 2012-04

 3.4 Sequence control and process diagnosis SICAR Standard

3.3.4 Behavior of the variables in the sequential control automatic mode

Overview:

#Sequence .ILOCK_Auto .TRANS_Auto .ILOCK_ .EXT_SYNC .EXT_INT

no_Sync
Participation in yes yes no yes no
the
synchronization

Automatic
yes (*) yes (*) yes (*) no no
diagnostics
(Initial value
error display)

(*) After expiry of the watchdog time, the initial value error is displayed and the entry is made in the
diagnostics memory.

Manual:

Perm step #Sequence.ILOCK_Manual

ILOCK-M step n
&
Selektiv step #Sequence.ILOCK_Manual
&
Selektiv step #Sequence.LIMIT_Manual
Auto:

>
Perm Step #Sequence.ILOCK_no_Sync
= 1
Action
Perm Schritt #Sequence.ILOCK_Auto
------------------------------------------------------------- output
Selektiv step #Sequence. LOCK_no_Sync
& ILOCK-A step n
Selektiv step #Sequence.ILOCK_Auto

Selektiv step #Sequence.EXT_SYNC

&
Selektiv step #Sequence.EXT_INT

Selektiv Stepp #Sequence.TRANS_Auto

Manual page 17 / 89 Edition: 2012-04

 3.4 Sequence control and process diagnosis SICAR Standard

3.3.5 Watchdog time - #Sequence.TWD_Setpoint

Every step of a sequence contains a function. This is usually the execution of a movement (action). It must
be executed within a finite time dependent on the process. The watchdog time is used to monitor the time
taken to execute the step and if the set time is exceeded, this results in an entry (initial value) being made in
the error log memory.

The watchdog time can be set with the parameter “watchdog time“ of the FB 1000. This parameter states the
general watchdog time for all steps of the sequence. If another time span is needed for a definite step, in the
network of the step, Sequence.TWD_Setpoint (DBW16) in the sequence work-DB has to be set to the
appropriate value. The time value is calculated by multiplying the constant in #Sequence.TWD_Setpoint with
the value of the clock pulse (e.g.20*pulse(100ms) =2 sec).

A watchdog error will not prevent Interlock. If you want to prevent interlock in case of a watchdog error, the
variable #Sequence.TWD_Error (DBX9.4) has to be programmed in the interlock. The scan can be
programmed in every step of the sequence. This bit depends on the sequence, i.e. the status is assigned
anew for each sequence and every step

Corresponding information in the sequence work-DB:

#Sequence.TWD_Setpoint : Rated value watchdog time (DBW16)

#Sequence.TWD_Actual_value : Actual value watchdog time (DBW20)
#Sequence.TWD_Error : Watchdog time error (DBX9.4)

Example: Step with scan of the watchdog time and watchdog time referring to the step

Manual page 18 / 89 Edition: 2012-04

 3.4 Sequence control and process diagnosis SICAR Standard

Watchdog time stop - #Sequence. TWD_Stop

The watchdog time can be stopped with the varible #Sequence. TWD_Stop. The signal has no influence on
the step output.

Properties (behavior in sequence control):

log. state if programming not carried out preset with 1bin

Watchdog time 0bin causes stop of watchdog time
log. state for step output no influence

Example: Step “waiting”

The particularity of the step “waiting” is based on the simultaneous assignment of #Sequence.TWD_Stop
and #Sequence.TRANS_Auto

Manual page 19 / 89 Edition: 2012-04

 3.4 Sequence control and process diagnosis SICAR Standard

Immediate error - #Sequence.SET_Error

The variable #Sequence.SET_Error makes it possible to trigger a diagnosis independent from the watchdog
time value.

Properties (behavior of sequence control):

log. state if programming not carried out preset with 1bin

automatic Diagnose 0bin causes immediate error
log. state for step output no influence

Example: Missing signal of parts check immediately creates a sequence error.

Manual page 20 / 89 Edition: 2012-04

 3.4 Sequence control and process diagnosis SICAR Standard

3.3.6 Waiting time - #Sequence.TWA_Setpoint

The dwell time in a step can be controlled by the waiting time. The waiting time can be set with the
parameter ”Waiting_time“ of the FB1000. This parameter specifies the general waiting time for all steps of
the sequence. If, however, a different time span is needed to set a certain step, the variable
#Sequence.TWA_Setpoint (DBW14) in the sequence DB must be set to the appropriate value in the
network of the step.
The time value is calculated by multiplying the constant in DW #Sequence.TWA_Setpoint with the value of
the clock pulse (e.g. 100*pulse (100ms) = 10 sec.). The parameter “Waiting_time“ automatically applies
again in the following step. The waiting time is not started or edited in the manual mode.

A waiting time that has not yet expired will not prevent enabling of the next step. If a step is not to be enabled
until after the waiting time, the variable #Sequence.TWA_Active must be programmed in the Transition. The
scan can be programmed in every step of the sequence. This flag depends on the sequence, that is, it is
regenerated for every sequence and every step.

Scan of #Sequence.TWA_Active in the Transition can be used to delay step enabling, e.g. for masking out
"bouncing" signals (steadying time)

Associated information in the sequence DB:

#Sequence.TWA_Setpoint : Rated value waiting time (DBW14)

#Sequence.TWA_Actual_value: Actual value waiting time (DBW18)
#Sequence.TWA_active: 1 = waiting time active, 0 = waiting time elapsed (DBX 23.7)

Example: step with scan of waiting time and waiting time referring to the step

Manual page 21 / 89 Edition: 2012-04

 3.4 Sequence control and process diagnosis SICAR Standard

Waiting time stop - #Sequence. TWA_Stop

The waiting time can be stopped with the variable #Sequence. TWA_Stop. The signal has no influence on
the sequence output.

Properties (behavior in sequence control):

log. state if programming not carried out preset with 1bin

waiting time 0bin causes waiting time stop
log. state for step output no influence

Example: Waiting time should only become active if command release is fulfilled

Manual page 22 / 89 Edition: 2012-04

 3.4 Sequence control and process diagnosis SICAR Standard

3.3.7 Branching - #Sequence.Step_n_plus1

With the value of the variable #Sequence.Step_n_plus1 the FB1000 sequence organization is given a
sequence number, with which the branching is carried out at the next step change (TRANS-A=1bin). As a
result the linear sequence block is abandoned.

Example:

The next step to be executed is set dependent on the status of flag M 600.2:

If the condition is M600.2=1bin, step 5 will be executed if the Transition is fulfilled

(TRANS=1bin ) not step 3.

Note: The branching address will be loaded independently from the status in #Sequence.TRANS_Auto.
In general the verification should only be processed after the Transition in M3.3 are performed.

Manual page 23 / 89 Edition: 2012-04

 3.4 Sequence control and process diagnosis SICAR Standard

3.3.8 Hold function - #Sequence.Hold_in_Step_n

If mode “automatic” is selected, actuating the pushbutton “stop“ at HMI or other consoles deselects the mode
“automatic” and the sequence is put on hold.
This procedure can be controlled by the variable #Sequence.Hold_in_Step_n (DBB24) in the sequence DB.

Programming possibilities:

0 immediate stop of sequence

255 the current step is finished and next step is enabled
1 sequence is put on hold once step 1 is reached
8 sequence is put on hold once step 8 is reached

Associated information in sequence DB:

#Sequence.OM_SB_until_Step_1 = Hold selected (DBX 8.4)

#Sequence.OM_SB_reached_Step_1 = Hold achieved (DBX 8.5)

Example 1: Current step must always be finished -> #Sequence.Hold_in_Step_n = 255 in permanent
sequence

Manual page 24 / 89 Edition: 2012-04

 3.4 Sequence control and process diagnosis SICAR Standard

Example 2: If the sequence is in step 3, continue until step 5, otherwise stop immediately

Step Perm

Step: 3

Step: 4

Manual page 25 / 89 Edition: 2012-04

 3.4 Sequence control and process diagnosis SICAR Standard

Note:

In case that the watchdog time = 0 the sequence will stop immediately independent from
the value of the variable #Sequence.Hold_in_Step_n.

Manual page 26 / 89 Edition: 2012-04

 3.4 Sequence control and process diagnosis SICAR Standard

3.4 Sequence output block (FC1001 – FC1128)

3.4.1 Basic functions of sequence output block

Call of sequence organization FB1000 with transfer of specific parameters

Assignment of outputs with step flags

OM Manual

#Sequence.ILOCK_Manual

&

#Sequence.LIMIT_Manual

Sequence output block

(FC1001 ...FC1128)
OM Automatic
> squence data block
1 output bits
#Sequence.ILOCK_Auto
= Action
(DBB72 ... DBB87)

#Sequence.ILOCK_no_Sync

#Sequence.EXT_Sync
&

#Sequence.EXT_INT

#Sequence.TRANS_Auto

Manual page 27 / 89 Edition: 2012-04

 3.4 Sequence control and process diagnosis SICAR Standard

3.4.2 Sequence call

FB1000 is called to sequence output block FC1001-1128.

Description of parameter:

Instance DB: The FB1000 requires a data block (sequence DB) for each sequence block
The sequence DB is generated as instance DB when call to FB1000.

Sequenc_block_number: Defines sequence block (sequence FB = sequence no. + 1000), in

which the order release, transition and sequence structure is programmed.

Waiting_time: Time value for waiting time (waiting_time *100ms), valid for all
(Waiting time) steps of this sequence, unless it was not redefined in the steps of the
sequence block.

Watchdog_time: Time value of watchdog time (watchdog_time*100ms), valid for all

(Watchdog time) steps of this sequence, unless it was not redefined in the steps of the
sequence block.

There is a strict connection between the sequence No. and the blocks:

Sequence block - FC = sequence no. + 1000

Sequence block - FB = sequence no. + 1000
Sequence block - DB = sequence no. + 1000
Sequence block – operating mode byte in DB 1000 = sequence no.

Manual page 28 / 89 Edition: 2012-04

 3.4 Sequence control and process diagnosis SICAR Standard

3.4.3 Sequence output

In the simplest case, the outputs are actuated by assigning the step memory to the output.

3.4.4 One action (output) in several steps

In certain cases it is necessary, depending on the mechanic of the system, to carry out actions in several
steps. In the sequence block (FB1001..FB1128), the manual part is programmed in one step and only the
automatic part is programmed in the following steps. The output is actuated by the step flags in the
sequence output block (FC1001..FC1128).

Manual page 29 / 89 Edition: 2012-04

 3.4 Sequence control and process diagnosis SICAR Standard

3.4.5 Control a Tec-Unit block

Below a sample to control a Tec-Unit block by parameterizing the Enable signals.
More information concerning Tec-Unit blocks in the according documentation.

Manual page 30 / 89 Edition: 2012-04

 3.4 Sequence control and process diagnosis SICAR Standard

3.5 Programming limitations for sequencer

The permanent step (jump to label „PERM“) and the selectiv steps (jump to label „S001“ ,… max. „S128“) of
the sequencer block are shown on the HMI.
Important: The used naming for jump / label “PERM“, „S001“, „S002“,....“S128“ is fixed and used to find
and analyse the right diagnostic area for the steps.

Rules for programming of one step( incl. permanent step):

Start of a new step will be a new network with the jump label “Sxxx”
Inside the logic it´s only allowed to program certain types of conditions / operands / adressing.
all others will be representate on the HMI with special characters from „$“ to „$$$$“ inside the
logic
More than one Network for one step logic part can be connected with RLO Signals, see screenshot
below
Rule: Network x = last condition with “=” <operand x>
Network x+1 = first condition with “A” <operand x> follow with IO-result=1
or Network x+1 = first condition with “AN” <operand x> follow with IO-result=0
1. Manual Mode: Rules for programming:
First manual interlock conditions “= #sequence.ILOCK_Manual”
Than the limit conditions for “= #sequence.LIMIT_Manual”
= End of diagnosis view for “Manual”
all conditons behind will be disabled from diagnosis view in manual mode
2. Automatic Mode: Rules for programming after Manual Mode:
First the additonal conditions for different interlocks like „= #sequence.ILOCK_no_Sync“
Than the finalize Interlock conditions for „= #sequence.ILOCK_Auto“ (last Interlock)
At least the conditions for „= #sequence.TRANS_Auto“
= End of diagnosis view for “Automatic”
all conditons behing will be disabled from diagnosis view like the “MOVE” in this example

The following example explane the rules:

Base = LAD programming for “Manual” and “Automatic” of Sequence x, Step 2:

Manual page 31 / 89 Edition: 2012-04

 3.4 Sequence control and process diagnosis SICAR Standard

3.6 Allowed conditions, operands and addressing

Following conditions(STL) or contacts, connections(LAD) are allowed for indication on HMI:

STL LAD
ON <Operand> <Operand>

AN <Operand> <Operand>

O(

A(

O <Operand>

A <Operand>

= <Operand> <Operand>
=
S <Operand> <Operand
S
R <Operand> <Operand>

Allowed operands and addressing:

Addressing Operands
0.0 65535.7 I (Input)
0.0. 65535.7 Q (Output)
0.0 65535.7 M (Flag)
DB0.DBx0.0 DB.DBX
(Data Block, Data Bit)
DB65535.DBx8181.7
X=1-512 = #message.no_X
Fix for every sequence =#Sequence.ILOCK_Auto
Fix for every sequence =#Sequence.TRANS_Auto
Fix for every sequence =#Sequence.ILOCK_no_Sync
Fix for every sequence =#Sequence.SET_Error
Fix for every sequence =#Sequence.TWD_Stop
Fix for every sequence =#Sequence.TWA_Stop
Fix for every sequence =#Sequence.ILOCK_Manu
Fix for every sequence =#Sequence.Limit_Manu
Fix for every sequence = #Sequence.EXT_SYNC
Fix for every sequence =#Sequence.EXT_INT
Fix for every sequence =#Sequence.TWA_active
Fix for every sequence =#Sequence.TWD_Error

Manual page 32 / 89 Edition: 2012-04

 3.4 Sequence control and process diagnosis SICAR Standard

Important:
Not allowed / not supported conditions, operands or addressing will be representate in diagnosis
view on HMI with following special characters:
$ = no Bitoperations like L, T, …etc.
$$ = Bitoperations like X, XN,… etc
$$$ = Addressing 8192.0 or higher
$$$$ = Jump / Label
$$$$$ = Timer, Counter

All thise special characters will be shown in LAD with following graphical element without animation:
?
„Missing Conditions“ disabled on HMI all viewing of not allowed conditions

Manual page 33 / 89 Edition: 2012-04

 3.4 Sequence control and process diagnosis SICAR Standard

3.7 Representation on HMI

Example for mode „Manual“ = active

Example for mode „Automatic“ = active:

Remarks for the use of #sequence.LAD_AUX:

„#sequence.LAD_AUX“ is used if you want to work with more than one assignment in one LAD
network. This is a behavior of Step 7.
“#sequence.LAD_AUX” is not shown in the HMI diagnosis.

Limitations for viewing of one step (incl. permanent step):

STL: max. 1024 Line
LAD: Graphic-Matrix: max. 32 Line and 32 Column
Diagnosis view only for the active operation mode, Manual or Auto / Inching
Criteria analysis of Error with logic result 1 (IO result =0)
Other diagnosis view can be activate with parametrization of IDB. DBX196.x
Change LAD view for operands between absolute and symbolic representation
control with “DB_Param” (DB940). DBX 22.4

Manual page 34 / 89 Edition: 2012-04

 3.4 Sequence control and process diagnosis SICAR Standard

3.8 Multilingual network commentaries for diagnosis at the HMI

The naming on the left side of the sequence diag screen must be written in the Title of the respective FB.
To design the step commentaries dependent on the respective language that can be set in the network
commentary by adding a key word. The key word is composed of „Title_“ and „language“ (the language
denotation exactly has to correspond with one of the languages that can be chosen at the „HMI“ in the
system screen).
Important: Key word must be written correct

Sample: Title FB1004 (Max. 24 Character)

Sample: Sequence diag screen

Manual page 35 / 89 Edition: 2012-04

 3.4 Sequence control and process diagnosis SICAR Standard

To get the step information on the right side of the sequence diag screen the information about the step must
be written in the network with the jump label. (Max. 40 Character)
To design the step commentaries dependent on the respective language they can set in the network
commentary by adding a key word. The key word is composed of „title“ and „language“ (the language
denotation exactly has to correspond with one of the languages that can be chosen at the „HMI“ in the
system screen):

Manual page 36 / 89 Edition: 2012-04

 3.4 Sequence control and process diagnosis SICAR Standard

Multilingual network commentaries for diagnosis at the HMI:

„Title_english“ for view language English:

„Title_deutsch“ for view language German:

„Title_other“ for 3rd view language

Manual page 37 / 89 Edition: 2012-04

 3.4 Sequence control and process diagnosis SICAR Standard

3.8.1 Add a 3rd language

SICAR supports 3 languages:
English
German
and one additional language.

How to activate an additional language for WinCC flexible can be found in Chapter “3.1 Initialization and
Operation modes”

In the message blocks or sequence blocks you have to use the key words “Title_other” for the 3rd language.

Sample: Chinese as 3rd language

Manual page 38 / 89 Edition: 2012-04

 3.4 Sequence control and process diagnosis SICAR Standard

Manual page 39 / 89 Edition: 2012-04

 3.4 Sequence control and process diagnosis SICAR Standard

3.9 Operation modes of the sequence blocks

The structure of the operation mode byte (OM byte) of the sequence is described in the following. If the
operation mode block delivered with the software package is used, the BA bytes are supplied automatically
and the following description only gives further information about the possibilities of the sequence. BA bytes
are stored in the DB 1000 data byte 1 to 128.

.0= Automatic mode

.1= Inching mode
.2= Manual mode
.3= Step + 1 (in inching mode) / stop in step 1 (in automatic mode)
.4= Start key
.5= Explicit acknowledgement
.6= Pulse
.7= Synchronization

OM: Automatic mode, manual mode inching mode and Start

The parameters ‘automatic mode’, ‘inching mode’ and ‘manual mode’ serve to pre-set the operation mode of
the sequence. With ‘Start’ the operation mode is activated. If the parameters are not unequivocal, no
operation mode will be set, e.g. if automatic and manual mode are selected at the same time. If no operation
mode is activated, the sequence has the operation mode ‘off’.

Corresponding information in the sequence work-DB:

#Sequence.OM_SB_Automatic (DBX8.0) = automatic mode
#Sequence.OM_SB_Inching (DBX8.1) = inching mode
#Sequence.OM_SB_Manual (DBX8.2) = manual mode

OM: Step +1 (in inching mode)

If inching mode is active, this command will be stored after a positive edge change of the request for a
transition (step +1), until the transition has been made to the next step or the operation mode has been
changed. The inching mode does not differ otherwise from automatic mode. Inching mode might be viewed
as a curbed automatic mode.

Corresponding information in the sequence work-DB:

#Sequence.OM_SB_Inching_plus1 (DBX8.3) = transition S+1

OM: Hold in step n (automatic mode)

In operating mode "Automatic", the sequence is stopped in accordance with the function selected in the
#Sequence.Hold_in_Step_n if “Hold” is requested.

Parameterization options of #Sequence. Hold_in_Step_n (DBB24):

0 immediate stop of sequence
255 the ongoing step is finished and next step is enabled
1 the sequence is stopped after reaching step 1
8 the sequence is stopped after reaching step 8

Corresponding information in the sequence work-DB:

#Sequence.OM_SB_until_Step_1 (DBX8.4) = Hold selected
#Sequence.OM_SB_reached_Step_1 (DBX8.5) = Hold reached

Manual page 40 / 89 Edition: 2012-04

 3.4 Sequence control and process diagnosis SICAR Standard

OM: Explicit acknowledgement

With this parameter it is possible to reset a watchdog time error. The reset will be done with the negative
edge of the bit “explicit acknowledgement”.

If this parameter is preset with “1” the step enabling will be blocked while watch dog time error occurs.
The step output signal will not be influenced. Therefore the bit #Sequence.TWD_Error has to be
programmed to the ILOCK-A.

OM: Pulse

The bit ‘pulse’ is used as a timer clock pulse for watchdog time and waiting time. If either of these times are
used, you have to set a parameter for the clock pulse.

OM: Synchronization

With this parameter you can start the synchronization. If no operation mode has been set (operation mode
‚off‘) and a synchronization is required, all steps are tested whether they are executable in automatic mode,
as far as they are not skipped over by a branching. With the synchronization the branchings are executed,
too.

This is determined via interlock-automatic = 1

External synchronization conditions = 1 and
Transition-automatic = 0.

OM-OFF

#Sequence.ILOCK_Auto
executable
&
#Sequence.EXT_SYNC

#Sequence.TRANS_Auto

If one step is unequivocally found, the sequence will be set to this step (synchronised). After changing to
the automatic mode the sequence is continued in this step.

Manual page 41 / 89 Edition: 2012-04

 3.4 Sequence control and process diagnosis SICAR Standard

The corresponding information in sequence work-DB is:

#Sequence. FB_SynAuto_oneStep (DBX9.5) only one executable step found

#Sequence. FB_SynAuto_multipleSteps (DBX9.6) more than one executable step found

#Sequence. FB_SynAuto (DBB11) Number of the found step, only if

one step was found.
if more than one step = 255
if no step =0

#Sequence.Step_n (DBB12) actual step-No

#Sequence. First_sync_Step (DBB28) 1. founded step if more than one step was
found

#Sequence. Second_sync_Step (DBB29) 2. founded step if more than one step was
found

#Sequence.Sync_Auto[1..128] (DBW56..) Is there one executable step found during

synchronization, the corrosponding bit in the
bit-area will be set to “1“. Each data bit of
DBX56.0-DBX71.7 is assigned to one step
from 1 to 128.

#Sequence.Stepmarker[1..128] (DBW72) This bit array represent the active step in

OM Auto / Manual. Each data bit of
DBX72.0-DBX…. is assigned to one step
from 1 to 128. These bits are used in the
Sequence-FC to control the Tec-units or
directly outputs.

Manual page 42 / 89 Edition: 2012-04

 3.4 Sequence control and process diagnosis SICAR Standard

3.10 Sequence data block (DB1001-DB1128)

Each sequence (FB1001 ... FC1128) uses one sequence data block (DB1001 ... DB1128) for saving variable
data.

Manual page 43 / 89 Edition: 2012-04

 3.4 Sequence control and process diagnosis SICAR Standard

Manual page 44 / 89 Edition: 2012-04

 3.4 Sequence control and process diagnosis SICAR Standard

3.11 Representation of a sequence block

In the following chapters the sequence is shown. The representation begins with the IEC-outline and
proceeds via function chart to the representation of the criteria for diagnostics and synchronization.

Figure: Diagram of a sequence

IEC outline Function chart (rough structure)

S
step 1
R

step 1
transition

S
step 2
R

step 2

transition

S
step 3
R

step 3
transition

Manual page 45 / 89 Edition: 2012-04

 3.4 Sequence control and process diagnosis SICAR Standard

4. Message block
FB1001

Network : n
Emergency Stop
A Mx.y
FC1001 =message_no1
***

Network: n+1
Protection Door
CALL FB1001, D B1001 A M x.z
=message_no2
***

DB1001

FC1000
CALL FC1000
Message_DB:=1001

Messages and information which is not logged using the sequence can be programmed in the message
modules.

4.1 Structure of the message block

The message module works with the UDT998 and an instance DB in which the message flag and the
internal auxiliary flag are stored.

The message module must be programmed as an FB within the number range from FB1001 to FB1128.
FC1000 ‘message analysis’ must be called from the message module.

A network must be programmed for each message.

Up to 512 messages can be programmed in a message module.

The message number is programmed using the symbol variabel “#message.no_”+ message number
(#message.no_1...512).

Example: #message.no_3 = 1 message no. 3 is active

#message.no_3 = 0 message no. 3 is not active

Manual page 46 / 89 Edition: 2012-04

 3.4 Sequence control and process diagnosis SICAR Standard

The namimg on the left side of the sequence diag screen must be written in the Title of the respective FB.
To design the step commentaries dependent on the respective language they can be set in the network
commentary by adding a code word. The code word is composed of „title“ and „language“ (the language
denotation exactly has to correspond with one of the languages that can be chosen at the „HMI“ in the
system screen):

Sample: Title FB1001 (Max. 24 Character)

The message text in the diagnostics system is the network name.

The message text (network name) can consist of up to 40 characters.

In order to benefit from multilingual functionality for the message text, they can be entered with a
keyword in the network comment. The keyword is made up as follows: “Title_” and language (the
language name must agree exactly with one of the languages which can be selected from the HMI).

Example: “Title_english” Emergency Stop active

“Title_deutsch” Not-Aus bestätigt

Manual page 47 / 89 Edition: 2012-04

 3.4 Sequence control and process diagnosis SICAR Standard

4.2 Programming limitations for message block

Rules for programming of one message:
STL: max. 1024 instructions
LAD: Graphic-Matrix: max. 32 x 32
Start of every logic for a message will be a new network
o Inside the logic should be used only allowed types of conditions / operands / adressing.
all others will be representate on HMI with special characters
from „$“ to „$$$$“ inside the logic
o More than one Networks for one message can be connected with RLO Signals:
Rule: NW x = last condition with “=” <operand x>
NW x+1 = first condition with “A” <operand x> follow with IO-result = 0
or NW x+1 = first condition with “AN” <operand x> follow with IO-result = 1
o previous rule for first network not used / not valid:
Special-Rule: first network will be used only for diagnosis view (not for message)
Setpoint of IO-result can be configured inside of IDB DBX 196.x
End of every logic for a message will be the last RLO result of this message
following logic parts will be disabled on HMI up to the start of a new message
STL/ LAD programming with
1st main path(s) = complete conections of conditions -
2nd alternative path(s) open from main path min. 1st condition after
example:

allowed
=
following
the rule

not allowed

The following example explane the rules:

Base = LAD programming for a message x:

Manual page 48 / 89 Edition: 2012-04

 3.4 Sequence control and process diagnosis SICAR Standard

4.3 Allowed conditions, operands and addressing

Following conditions(STL) or contacts, connections(LAD) are allowed for viewing on HMI:
STL LAD
ON <Operand> <Operand>

AN <Operand> <Operand>

O(

A(

O <Operand>

A <Operand>

= <Operand> <Operand>
=
S <Operand> <Operand
S
R <Operand> <Operand>

Allowed operands and addressing:

Addressing Operands
0.0 65535.7 I (Input)
0.0. 65535.7 Q (Output)
0.0 65535.7 M (Flag)
DB0.DBx0.0 DB.DBX
(Data Block, Data Bit)
DB65535.DBx8181.7
X = 1-512 #message.no_X

Important:
Not allowed / not supported conditions, operands or addressing will be representate in diagnosis
view on HMI with following special characters:
$ = not Bitoperations like L, T, …etc.
$$ = Bitoperations like X, XN,… etc
$$$ = Addressing 8192.0 or higher
$$$$ = Jump / Label
$$$$$ = Timer, Counter
For every special character following LAD-Grafic will be shown without animation in the logic:
?

not allowed instanz data bit (DIX) view condition without addressing

Button „Missing Conditions“ disable on HMI all viewing of not allowed conditions

Manual page 49 / 89 Edition: 2012-04

 3.4 Sequence control and process diagnosis SICAR Standard

4.4 Representation HMI

Example = LAD programming with STEP7

STL view with HMI:

LAD view with HMI:

Manual page 50 / 89 Edition: 2012-04

 3.4 Sequence control and process diagnosis SICAR Standard

Rules for viewing of one message:

STL: max. 1024 Line
LAD: Graphic-Matrix: max. 32 Line and 32 Column
Diagnosis view only for one selective message from overview picture
Analysis of Error with logic result 1 (IO result =0)
Other diagnosis view can be activate with parametrization of IDB. DBX196.x
Change LAD view for operands between absolute and symbolic representation
control with “DB_Param” (DB940). DBX 22.4

Manual page 51 / 89 Edition: 2012-04

 3.4 Sequence control and process diagnosis SICAR Standard

4.5 Call of the message block

The call of the message module must be programmed in the message FC. The number of the message FC
must be identical to the FB number. The DB number of the instance DB must be identical to the FB number.

Important: FC-no = FB-no = DB-no; permissible 1001...1128

Manual page 52 / 89 Edition: 2012-04

 3.4 Sequence control and process diagnosis SICAR Standard

5. HMI – Sequence diagnosis screen

The diagnosis screen can be opened up from the “Main screen” by pressing “Seq_Diag”

5.1 Interface PLC -HMI

As an interface between PLC and HMI the block FC941 is used and called in the FC983.
This block coordinate the communication for the screens “OP Mode” and “Seq DIAG” by using DB941 and
DB942.

No changes, adjustments by the user are required.

Manual page 53 / 89 Edition: 2012-04

 3.4 Sequence control and process diagnosis SICAR Standard

5.2 Sequence diagnosis

5.2.1 Overview screen

In the diagnosis screen the operating states and the diagnosis information of the sequence-/ message
blocks are displayed.
This screen is ready developed in WinCC flexible and need no further engineering work in WinCC flexible.
You reach this screen from every other screen by pressing the button “Seq_Diag”.
All necessary diagnosis information are generated in the WinCC flexible Runtime environment by using of
scripting in the background. The steps are described lateron in this chapter.

The screen is divided into two areas:

In the left section the existing sequence- / message blocks are displayed.

In the right section the detail diagnosis of the block selected on the left is presented.

Zone selection buttons on the left side

By pressing the Zonebuttons Z1…….Z8 you will see only the sequence / message blocks
belonging to the selected zone
If no Button is pressed all sequences / message blocks are indicated.
The number of Buttons are shown depends on the activated zones in the PLC and works
automatically.

Manual page 54 / 89 Edition: 2012-04

 3.4 Sequence control and process diagnosis SICAR Standard

Function buttons

These buttons are used to navigate the cursor in the left or right field
Line up, Line down -> one line up / down
Page up, Page down -> 16 lines up / down

Change active cursor from / to left or right field

5.2.2 Sequence overview

The sequence overview indicates the sequence number, the sequence commentary and the current step.

The individual sequence background colors show the operating mode and has the following significance:

Automatic -> green

Manual -> light blue
Inching started -> dark green
Inching active -> light green
Off -> white
Primary fault -> red
Secondary fault -> dark red

Per zone one primary fault is indicated, means the first fault which appears in this zone.
All other faults in this zone, appearing after a primary fault, are secondary faults and displayed in dark red
colour.

Buttons on the right

If a sequence has a fault, the button shows the kind of fault like PERM, ILOCK or TRANS is missing.

Manual page 55 / 89 Edition: 2012-04

 3.4 Sequence control and process diagnosis SICAR Standard

5.2.3 Detailed diagnosis: STL representation

Sequence block
Depending on the active operation mode the assignments of ILOCK / TRANS conditions of the actual step
are indicated on the HMI.

What will be indicated:

Command, Operand, state of the operand , symbolic and commentary from the step7 symbollist.

With the buttons in the footer you can select which part of the sequence you want to see:
ILOCK = show only Interlock conditions
TRANS = show only Transition conditions
PERM = show only Permanent step consitions
Missing conditions = show only Missing conditions

The missing conditions are shown with a red sqare on the left side.

Diagnosis buttons:
Missing Conditions = view only missing conditions except all special codes
LAD View = change view to LAD

Navigation button:
Line UP = scroll view one Line Up
Page UP = scroll view one Page Up
Line DN = scroll view one Line Down
Page DN = scroll view one Page Down

Manual page 56 / 89 Edition: 2012-04

 3.4 Sequence control and process diagnosis SICAR Standard

5.2.4 Detailed diagnosis: LAD representation

The headline shows for one certain LAD element the respective information from the symbolist, here I5.5
By touching another LAD element on the screen whose information are shown in the headline.

Change LAD view for operands between absolute and symbolic representation
control with “DB_Param” (DB940). DBX 22.4

Diagnosis button:
Missing Conditions = view only missing conditions except all special codes
STL View = change view to STL

Navigation button:
Cn Left = scroll view one Column Left
Cn Right = scroll view one Column Right
Line UP = scroll view one Line Up
Page UP = scroll view one Page Up
Line DN = scroll view one Line Down

Manual page 57 / 89 Edition: 2012-04

 3.4 Sequence control and process diagnosis SICAR Standard

Page DN = scroll view one Page Down

Manual page 58 / 89 Edition: 2012-04

 3.4 Sequence control and process diagnosis SICAR Standard

5.2.5 Inching
In inching mode (sequence engine executed automatic conditions) you can control sequence blocks step by
step by using the buttons Inch-S and Inch-A.

To proceed Inching you have to activate inching mode for the appropriate Zone in the operating mode
screen.
A sequence which is in Inching mode is indicated in dark green colour.

Inching mode active

Inch-S – Inching one step

Activate operation mode “Inching” in the operating mode screen

Select with the cursor on the left side the sequence you want to inch
Press the Button “Inch-S” on the right side
The step is now active and the colour of the sequence change to lime green
If the step is finished the colour return to dark green

Inch-A – Inching all sequences of a zone

Activate operation mode “Inching” in the operating mode screen

Select with the Zone button the desired zone or without selecting a zone all sequences are
inched
Press the Button “Inch-A” on the right side
The steps of the sequences are now active and the colour of the sequence change to lime green
If the step of a sequence is finished the colour return to dark green

Manual page 59 / 89 Edition: 2012-04

 3.4 Sequence control and process diagnosis SICAR Standard

Step active after pressing Inch-S or Inch-A

Manual page 60 / 89 Edition: 2012-04

 3.4 Sequence control and process diagnosis SICAR Standard

5.2.6 Synchronisation

5.2.6.1 Manually synchronisation on HMI

With the buttons Sync-S and Sync-A you can synchronize one or all sequence blocks to the current line
situation.
In the orange field you find the first founded step, in the yellow field the second founded step.
If only one step is found the sequence is set automatically to this step.
If no step or 2 or more steps are found the sequence remains his current step and the Sync result is
indicated in red colour.

Sync-S – Synchronise one step

Select operation mode “Off”, sequence is indicated with white colour

Select with the cursor on the left side the sequence you want to synchronize
Press the Button “Sync-S” on the right side
The synchronization result appears
To switch off the synchronization result press button “Sync Off”

Sync-A – Synchronise all steps

Select operation mode “Off”, sequence is indicated with white colour

Select with the Zone button the desired zone or without selecting a zone all sequences will be
synchronized
Press the Button “Sync-A” on the right side
The synchronization result appears
To switch off the synchronization result press button “Sync Off”

Picture Sequence 4: Mode “Off”

Manual page 61 / 89 Edition: 2012-04

 3.4 Sequence control and process diagnosis SICAR Standard

Picture Sequence 4: Sync Result appears after pressing Sync-S or Sync-A

Only one step found

Possible results:
No step found

More than 2 steps found

5.2.6.2 Automatically synchronisation in the PLC

If you want to synchronize automatically use the block FC974. This block has to be called in the last network
of FC983
The synchronization of a zone is executed, if you preselect operation mode Auto.
E.g. OM Manual is active and now you press the button Automatic, synchronization is executed.
If operating mode Auto is active and you press again the button Automatic, the function synchronization is
not executed.

Manual page 62 / 89 Edition: 2012-04

 3.4 Sequence control and process diagnosis SICAR Standard

5.2.7 Sequence Set Step

The function “Sequence Set Step” allows you to set a sequence to a desired step.
This could be necessary if the synchronization failed and you need to restart the line in a certain step.

Select operation mode “Off”, sequence is indicated with white colour

Select with the cursor on the left side the sequence you want to set to a certain step
Change the cursor to the right side
Press the Button “Seq_Set_Step” on the right side
The background change to light blue and Button “Confirm” appears
Select the desired step with the right cursor
Press button “Confirm” on the right side
The sequence is set now to the selected step

Sequence is in OM “Off”, Sequence is selected and Seq Set Step is active

Cursor now active on the right side

Manual page 63 / 89 Edition: 2012-04

 3.4 Sequence control and process diagnosis SICAR Standard

Desired step is selected

Sequence is set to new step by pressing button “Confirm”

Manual page 64 / 89 Edition: 2012-04

 3.4 Sequence control and process diagnosis SICAR Standard

5.3 Message block diagnosis

The background colours of the individual message block have the following meanings:

No diagnostics white
Error red

If the cursor is placed on the left side on a message block, an overview of the messages programmed are
displayed on the right side of the screen.
The message texts are displayed corresponding to the network comments of the S7-block.
All messages with an error are red highlighted.

Example: no diagnostics

Example: Error

Manual page 65 / 89 Edition: 2012-04

 3.4 Sequence control and process diagnosis SICAR Standard

5.3.1 Detailed diagnosis: STL representation

Automatically the missing conditions are indicated, means you can see the bit information which is
responsible for the message. Button „Missing conditions“ has a green background.
By pressing the button „Missing conditions“ you can switch between the views „Show all conditions“ and
„Show only missing conditions“.
The viewing of sequence follows the same rule.

Diagnosis buttons:
Missing Conditions = view only missing conditions except all special codes
LAD View = change view to LAD

Navigation button:
Line UP = scroll view one Line Up
Page UP = scroll view one Page Up
Line DN = scroll view one Line Down
Page DN = scroll view one Page Down

Manual page 66 / 89 Edition: 2012-04

 3.4 Sequence control and process diagnosis SICAR Standard

5.3.2 Detailed diagnosis: LAD representation

With button “STL View “ / “LAD View” the viewing representation can be changed.

Change LAD view for operands between absolute and symbolic representation
control with “DB_Param” (DB940). DBX 22.4

Diagnosis button:
Missing Conditions = view only missing conditions except all special codes
STL View = change view to STL

Navigation button:
Cn Left = scroll view one Column Left
Cn Right = scroll view one Column Right
Line UP = scroll view one Line Up
Page UP = scroll view one Page Up
Line DN = scroll view one Line Down
Page DN = scroll view one Page Down

Manual page 67 / 89 Edition: 2012-04

 3.4 Sequence control and process diagnosis SICAR Standard

6. Generating of diagnosis data for “Sequence diag screen”

The required data which are displayed in the sequence diagnosis screen must be generated by the user with
information from the current S7 project.

The procedure is as follows:

An STL source is generated from the programmed sequence/message FBs.

Open a block in your current STEP7-project.

Select in the menu bar “File” and the sub menu “Generate source”.

Enter object name (user defined). Suggestion: Project_1

Press “OK”

Select from the list in the left window all sequence- / message blocks (FB1001 - 1128) and move it to the
right window by using the arrows.
It is important to note that you have to select “Absolute” in the field “Addresses”.

Manual page 68 / 89 Edition: 2012-04

 3.4 Sequence control and process diagnosis SICAR Standard

Press “OK”.

In the container ‘Sources‘ select the newly created source with the right mouse button and execute the
function “Export source”. Export the Source e.g. to a USB-Stick for a transfer to the Multi-Panel or PC.

Mandatory:
The file must have the same name as the project subfolder e.g.“Project_1.s7l”.

Manual page 69 / 89 Edition: 2012-04

 3.4 Sequence control and process diagnosis SICAR Standard

To have the chance to use different projects it is necessary to create project subfolders

Project structure MP:

Project structure PC:

Manual page 70 / 89 Edition: 2012-04

 3.4 Sequence control and process diagnosis SICAR Standard

6.1 Structure of Textfiles (Language dependent)

English-language personal computers used a 7-bit character code called American Standard Code for
Information Interchange (ASCII), which allows for a charcter set of 128 items of upper and lower case Latin
letters, Arabic numerals, signs, and control characters to be used (2^7 = 128 code points).

In the case of languages such as Chinese, which has a huge character set with tens of thousands of
characters, a 16-bit, or two-byte, character code is employed. A two-byte character code allows for up to
65,536 items to be encoded (2^16 = 65,536 code points) (Unicode)

6.2 Procedure ASCII languages

6.2.1 Multi Panel

The generated source file must be stored onto a USB-Stick, CF-card, MMC-card or flash-disc on the Multi
panel.
The storage medium and storage path must be specified on the Multi panel in the System screen.

E.g. Storage medium: \Storage Card MMC\ or \flash\ or other removable medium
E.g. Storage Path: SICAR\Project_x

It´s mandatory to activate the “ASCII-Format” check mark.

With the button “Save Settings” the information about the storage medium, storage path and file format is
saved in \Flash\SICAR\Panel_No.csv,

By pressing the button “Init Diag” the source file is prepared automatically for the use in the diagnosis
screen.

Manual page 71 / 89 Edition: 2012-04

 3.4 Sequence control and process diagnosis SICAR Standard

6.2.2 PC
The generated source file must be stored on C:\SICAR\Projectname

The storage path automatically generated by the system.

Storage path: C:\
Folder: SICAR\Project_x

It´s mandatory to activate the “ASCII-Format” check mark.

With the button “Save Settings” the information about the storage path and folder is saved into the file
C:\SICAR\Panel_No.csv.

By pressing the button “Init Diag” the source file is prepared automatically for the use in the diagnosis
screen.

Manual page 72 / 89 Edition: 2012-04

 3.4 Sequence control and process diagnosis SICAR Standard

6.3 Procedure Unicode languages

6.3.1 Multi Panel

Note:
To work with an unicode language on your engeneering station it is necessary to activate this language in
the system settings of your operating system.
That´s not possible on a WINCE based system, like the multi panel.

On this reason there are 3 additional steps necessary to generate the information of the diagnosis screen.

Step 1:
The exported sourcefile from Step7 must be stored as an Unicode-file.
Open the sicar_sample.s7l with the Microsoft Notepad.
Select in the menu bar “File”, “Save as”

Change Coding from “ANSI” to “Unicode” and save the file.

Step 2:
On the SICAR-CD a file-extractor is located, “S7L_Extractor.exe”
Copy this exe-file to your engineering station with the WinCC flexible engineering software.
Start the file-extractor “S7L_Extractor.exe”.

Select the “S7 Source”, means the folder with the generated Step 7 source file.
Select the “Target Folder”. The “S7L_Extractor” generate the necessary txt-files for the multi panel and a
csv-file for the import into WinCC flexible.
Press the button “Go” to generate the files. Wait till you see information “Process finished”.

Manual page 73 / 89 Edition: 2012-04

 3.4 Sequence control and process diagnosis SICAR Standard

Content of the folder D:\TEMP\S7l Source\Generated files

Manual page 74 / 89 Edition: 2012-04

 3.4 Sequence control and process diagnosis SICAR Standard

Step 3:
Open your current WinCC flexible project.
Select csv-import.

Select only the Type “Text lists”.

Select the folder with the generated csv-file of the “S7L_Extractor”.
Press “Import”

In the Text List a new Entry with the name “Chinese Textlist” is generated. This textlist contains all the
Chinese characters of the Step7 Source file.

Transfer your project now to the target device, e.g. MP277.

Manual page 75 / 89 Edition: 2012-04

 3.4 Sequence control and process diagnosis SICAR Standard

Step4:
All generated txt-files of the “S7L_Extractor” in the directory D:\TEMP\S7l Source\Generated files must be
stored onto a USB-Stick, CF-card or MMC-card on the Multi panel.
The storage medium and storage path must be specified on the Multi panel in the System screen.

E.g. Storage medium: \Storage Card MMC\ or \flash\ or other removable medium
E.g. Storage Path: SICAR\Project_x
It´s mandatory to activate the “Unicode-Format” check mark.
With the button “Save Settings” the information about the storage medium, storage path and file format is
saved.

The Init-Diag button is hidden, due to the fact that the informations for the diagnosis screen are already
generated by the S7 Extractor.

Manual page 76 / 89 Edition: 2012-04

 3.4 Sequence control and process diagnosis SICAR Standard

6.3.2 PC
Note:
To display and to work with Unicode languages it is necessary to install this language in your operating
system.
E.g. Chinese, you have to install files for east asian languages.
Start / Settings / Control Panel / Regional and Language Settings /
Tab: Languages
Mark Checkbox “Install files for east asian languages”

Step1:
The exported sourcefile from Step7 must be stored as an Unicode-file.
Open the sicar_sample.s7l with the Microsoft Notepad.
Select in the menu bar “File”, “Save as”

Change Coding from “ANSI” to “Unicode” and save the file.

Step2:
Transfer the sourcefile to the PC and place it in C:\SICAR.

The storage medium and storage is automatically preset by the system.

Storage medium: C:\
Storage Path: SICAR\Project_x
It´s mandatory to activate the “Unicode-Format” check mark.
With the button “Save Settings” the information about the storage medium, storage path and file format is
saved.

Step3:

By pressing the button “Init Diag” the source file is prepared automatically for the use in the diagnosis
screen.

Manual page 77 / 89 Edition: 2012-04

 3.4 Sequence control and process diagnosis SICAR Standard

7. Procedure to generate information for the “Detail diagnosis”

The diagnosis data which are displayed in the detailed diagnosis screen must be generated from the user
with the Tool “SICARGen” based on the information of the current S7 project.

7.1 Install the Tool SICARGen on your PC.

SICARGen is tested with WINXP SP3 and WINDOWS 7.
SICARGen needs .Net Framework 4.0 Client.
Install first : „dotNetFx40_Client_x86_x64.exe“ from the folder 30_Software/Tools/DotNet.

Installation “SICARGen”
Start “Setup.exe” from 30_Software/Tool/SICAR-Gen and follow the instructions

7.2 Activate XML-Import/Export in WinCC flexible 2008 SP1 HF5 / SP2

Doubleclick on “activate.exe” in 30_Software/Tool/WCF2008_Activate
This installation activates the XML Import Export interface of WinCC flexible.

7.3 General function of SICARGen

SICARGen works in two different ways.
It depends if the user works with an integrated WinCC flexible project or with a not integrated WinCC flexible
project.

Manual page 78 / 89 Edition: 2012-04

 3.4 Sequence control and process diagnosis SICAR Standard

7.4 Procedure with an integrated WinCC flexible project

Note:
Only in an integrated project the command interface of WinCC flexible works.
Before you can use SICARgen at least one time the WinCC flexible project has to be compiled.

Tool actions:
1. Generate and export from Step7 a sourcefile of FB1001 – FB1128 and the symbollist.
2. Export from WinCC flexible three certain textlists in XML-format.
3. Analysing the sourcefiles and symbolist from Step7
4. Generating DB´s in Step 7 with diagnosis information
5. Generate Textlists and import into WinCC flexible

User action:
Download new generated DB´s (Default: DB1301 – DB 1428) into the PLC.
Download WinCC flexible project to target device.

7.4.1 Settings in SICARGen

1. Select your current S7-project from the pull down menu.

You get the known overview from Step 7.

Manual page 79 / 89 Edition: 2012-04

 3.4 Sequence control and process diagnosis SICAR Standard

An integrated WinCC flexible project is automatically detected and shown in 4 “WinCC flexible Project”

Manual page 80 / 89 Edition: 2012-04

 3.4 Sequence control and process diagnosis SICAR Standard

2. You can also select the S7-project with the “Storage path” using this button

An integrated WinCC flexible project is automatically detected and shown in 4 “WinCC flexible Project”

3. Select S7-Programm using the drop down menu.

4. Select WinCC flexible Project

If there is only one WinCC flexible project integrated, it´s automatically detected.
For the case that there are more than one project is integrated you have to select the appropriate one.

Manual page 81 / 89 Edition: 2012-04

 3.4 Sequence control and process diagnosis SICAR Standard

5. Language Symbolic
This setting depends on your language concerning the symbolist in Step 7.
SICARGen creates the textlists in WinCC flexible depending on this setting.

6. Codepage Symbolic
For the use with Unicode languages

7. Start-FB, Start-DB
Start-FB: FB1001 and the next 127 blocks. No change possible
That’s the FB´s which must be evaluated by the Tool, means all sequence and message blocks.

Start-DB: Default 1301 and following 127 DB´s.

The evaluated information of the FB1001 – FB1128 is stored in the DB1301 – DB1428.
Information FB1001 -> DB1301
Information FB1002 -> DB1302
.
.
Information FB1128 -> DB1428

Here you can change the DB. The new value has to be changed also in the PLC DB940.DBW6, because
that´s the information for the HMI.

8. Folder Output
In this folder the Tool stores all relevant information about the last generation.

9. WinCC flexible EXE

The WinCC flexible.exe (HmiES.exe) is automatically detected.

10. Start
With the Start button the generation will be started.
In the right window you get the information about the ongoing work steps.

10. Languages
Here you can select the language of the user interface.

7.4.2 Additional user steps

Download the new generated DB´s to the PLC (DB1301 – DB1428)

Download the WinCC flexible runtime

Manual page 82 / 89 Edition: 2012-04

 3.4 Sequence control and process diagnosis SICAR Standard

7.5 Procedure with a not integrated WinCC flexible project

7.5.1 Settings in SICARGen

1. Select the storage path of your generated and exported AWL-sourcefile

2. Select the storage path of your exported XML-sourcefile

3. Select the storage path of your exported symbollist

4. Select the storage path of the generated db sourcefile

5. Select the storage path of the generated xml sourcefile

6. Press “Start” and the Tool generates the both Targetfiles DB and XML

7. Mark “extended logs” to activate generation of Log-files

Log-files stored in the path “Targetfile DB”

Manual page 83 / 89 Edition: 2012-04

 3.4 Sequence control and process diagnosis SICAR Standard

7.5.2 User action

Step 7:Generate a source of all sequence/message FB (FB1001 – FB1128)

Export the sourcefile with the extension *.s7l

Manual page 84 / 89 Edition: 2012-04

 3.4 Sequence control and process diagnosis SICAR Standard

Step 7: Export the symbollist as *.sdf

WinCC flexible: Export three certain textlists in xml-format.

SS-37_Diag_Adress_extract_from_Tool
SS-37_Diag_Symbolic_extract_from_Tool
SS-37_Diag_Commentary_extract_from_Tool

Manual page 85 / 89 Edition: 2012-04

 3.4 Sequence control and process diagnosis SICAR Standard

7.5.3 Tool action

Analysing the sourcefiles from Step7 and WinCC flexible
Generating DB´s with the diagnosis information as sourcefiles
Generate Textlists as a xml-file

Manual page 86 / 89 Edition: 2012-04

 3.4 Sequence control and process diagnosis SICAR Standard

7.5.4 Further user action

Delete current Diag-DB´s

Import AWL-sourcefile into Step7 as an external source

Select the generated sourcefile *.awl

Manual page 87 / 89 Edition: 2012-04

 3.4 Sequence control and process diagnosis SICAR Standard

Compile the source

Download new generated DB´s (Default: DB1301 – DB 1428) into the PLC.

Import generated xml-file into WinCC flexible

Manual page 88 / 89 Edition: 2012-04

 3.4 Sequence control and process diagnosis SICAR Standard

Open Import file

Select the three textlistsand press “Run”

Download WinCC flexible project to your target device.

Manual page 89 / 89 Edition: 2012-04