32 - HMI and Systemdiagnostics
32 - HMI and Systemdiagnostics
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
Reproduction of the contents of this copyrighted manual, in whole or in part, without the written permission of
Siemens, is prohibited.
Table of contents
1. Introduction 5
5. Manual Operating 29
5.1 Overview 29
5.1.1 Layout and basic functionality of the manual operating screens 29
5.1.2 Elements of the movment / function line 32
5.1.3 Assignment of the function numbers 34
5.2 Purpose of the individual manual operating screens 35
5.2.1 Manual operation 35
5.2.2 User operation screens 35
5.2.3 Special function screens 35
5.3 Configuration and runtime interface 36
5.4 Configuration 37
5.4.1 Global configuration 37
6. Production-Data 55
6.1 Overview production data 55
6.2 Process Counter 56
6.2.1 Programming FB982 57
6.2.2 Reset Process counter in the PLC 57
6.2.3 Parameterization of Texts 58
6.3 Shift counter 59
6.3.1 Programming FB982 60
6.3.2 Reset Shift counter in the PLC 60
6.3.3 Reset Shift counter in the HMI 61
6.3.4 Parameterization of Target Values 62
6.3.5 Parameterization of Texts 63
6.4 Cycle time 64
6.4.1 Programming FB982 65
6.4.2 Parameterization of Target Values 66
6.4.3 Parameterization of Texts 67
6.5 Limit values 68
6.5.1 Alarm handling 69
6.5.2 Indication of active Prealarm or Alarm 70
6.5.3 Programming FB982 71
6.5.4 Parameterization of Set- and Prealarm values 72
6.5.5 Parameterization of Texts 72
6.6 Used PLC-Blocks and structure 73
6.7 Initialization of additional screens 74
7. Diagnostics 75
7.1 RSE – Report system error 75
7.1.1 Activating RSE 76
7.2 Messages screen and Message archive screen 78
7.2.1 Layout of the screen and functionality 78
7.2.2 Runtime interface 79
7.2.3 Configuration 79
7.3 DataInterface screen 80
7.3.1 Layout of the screen 80
7.3.2 Runtime interface 81
7.3.3 Configuration 81
7.3.4 PLC-Interface 82
7.4 Version screen 84
8. Hardware Diagnostics 86
1. Introduction
The following description contains the information of the SICAR standard for HMI and the
corresponding PLC interface .
Note
A detailed description for working with data blocks is contained in the Step7
online help.
(1) Header
The upper area of each screen contains the header. It contains significant status information,
such as operating mode, initial state, etc. This area also contains the message line for alarms
and messages.
The header can be configured in two different types of representation. Whereas one of the
representation types shows the status information as text, the other representation type shows
the status information as graphic elements. Further details about the header are contained in
Chapter 4 of this manual.
DetaiFigure 0-2 Structure of the menu for operator panels with 10" screen display
Main OEM
menu
Alarm Alarm Manual Detail Cursor Line Page Line Page Main Seq
History Operation Diag to right Up Up Dn Dn menu Diag
Submenus Main
menu
The machine manufacturer should give the operator a graphic overview of the associated
machine in the main screen. From this screen, the horizontal softkeys can be used to change to
one of the eight main menus.
Note
The menu structure shown here is the standard menu structure for SICAR. The
menu structure can be customized for specific projects.
The gray-shaded buttons are navigation and function keys assigned to the individual screens in
the corresponding submenus.
Click the "Main menu" button to return from the current menu to the main menu ("Plant
overview" screen). The "Return" button is configured in the third menu level to return to the
second menu level.
The "Page up"/"Page down" keys and the "Absolute/Symbolic" toggle keys required in the
operating screens are described in Chapter 5.
All WinCC flexible elements, such as screens, variables, graphics and symbol lists have been
named using uniform designation conventions.
The designation structure must provide the following information:
Who created the associated element?
Who changed the element?
How are the individual elements linked with each other?
In other words: All WinCC flexible elements that can be changed by the user (configuring) are
designated with "SO_". When the elements in WinCC flexible are sorted according to name,
these elements appear at the start of the list.
In addition, the designations can be used to determine all elements assigned to a screen.
All WinCC flexible elements, such as screens, variables, graphics and symbol lists must be
named using these uniform designation conventions (see Table 3-1).
Icon Description
A Who created the associated screen element?
S: Siemens
O: OEM (machine manufacturer)
C: Customer
B Who should change the screen element?
S: Siemens
O: OEM (machine manufacturer)
C: Customer
XX Assignment of the screen elements to each other
(e.g. 62: means all elements of the "Workpiece counter" screen)
Name Designation of the screen element
(e.g. "PartCounter")
Table 0-1 Syntax of the designation convention for screen elements in Pro Tool
Example
S S _ 11 _ManualMovement
The name of the screen form is
"ManualMovement”
The number of the screen element is 11.
The screen form may only be changed by
Siemens.
The screen form was created by Siemens.
All other elements only used in the "ASIDiagnostic" screen, such as variables or symbol lists,
also have the identification 51.
E.g.: Variable: SS_11_ManualMovment
Text list: SO_11_ManualMovement
All screen elements not uniquely assigned to a specific screen have the identification 00 (e.g.
the variables or symbol lists used in the header).
In some cases, screen elements, e.g. variables, are used together by complete screen groups.
A common group identification is then assigned to such screen elements.
For example, all screen elements used by all operating screens have the identification 10.
Screen elements used only for a specific operating screen have the associated identification of
the corresponding screen to which they are assigned (e.g. for the "SS_11_ManualMovement"
screen).
To avoid using any timer of the CPU, all time functions within the SICAR blocks
are realized using the CPU system time. The system time is fetched with the
SFC64 and further processed.
The SFC 1 ("READ_CLK") is used to read the date and time of the PLC from the
"FC_HMI_BASIC" block. The system time will be written in the
"AREAPOINTER.DATE_TIME_PLC [1..12]" data area of the "DB_HMI_DATA".
The "Controller date/time" area pointer is read from the panel with an acquisition cycle of 120
seconds and a synchronization with the OP clock is performed. If, for some reason, the
synchronization of the clocks has been disabled, the "Controller date/time" area pointer must be
deleted from the WinCC flexible configuration.
Note
The acquisition cycle of the "PLC date and time" area pointer should not be
chosen too small, because it affects the communications capability of the
operator panel. By default, 120 seconds (2 minutes) are set for the acquisition
cycle.
The information which screen is selected on the operator panel is made available in the WinCC
flexible "SS_00_ScreenIdentification" variable. For the screen construction, the corresponding
value is written in the variable; for screen removal, the variable is set to zero.
To keep the cycle time of the controller as small as possible, the program code for a specific
screen should be executed only when the corresponding screen is selected.
Tag: SS_00_ScreenIdentification
Format: WORD
PLC address: "DB_HMI_DATA".GLOBAL.SCREEN_ID
WinCC Designation of the system screen Code to identify the screen form
flexible High Low [dec.] [hex.]
screen byte byte
number
111 SO_111_Man_Overview_1
112 SO_112_Man_Overview_2
121 SO_121_User_Overview_1
122 SO_121_User_Overview_2
131 SO_131_Special_Overview_1
reserved
21 SS_21
22 SS_22
23 SS_23
24 SS_24
25 SS_25
26 SS_26
Drive G120
41 SS_41_FB307_CU240x_Status
42 SS_42_FB307_CU240x_Values
43 SS_43_FB307_CU240x_Alarms
44 40 4 10244 0x2804
45 40 5 10245 0x2805
WinCC Designation of the system screen Code to identify the screen form
flexible High Low [dec.] [hex.]
screen byte byte
number
50 SS_50_Drive_Overview
Machine information
61 SO_61_MachineOverview 60 1 15361 0x3C01
62 60 2 15362 0x3C02
63 60 3 15363 0x3C03
65 60 5 15365 0x3C05
67 SS_67_DataInterface 60 7 15367 0x3C07
PNIO diagnostics
70 SS_70_HardwareDiagnostic 70 0 17920 0x4600
71 SS_71_StationOverview1 70 1 17921 0x4601
72 SS_72_StationOverview2 70 2 17922 0x4602
73 SS_73_StationOverview3 70 3 17923 0x4603
74 SS_74_StationOverview4 70 4 17924 0x4604
75 SS_75_StationDetail 70 5 17925 0x4605
76 SS_76_DiagnosticRepeater 70 6 17926 0x4606
77 SS_77_HistoryTrigger 70 7 17927 0x4607
78 SS_78_Legend 70 8 17928 0x4608
WinCC Designation of the system screen Code to identify the screen form
flexible High Low [dec.] [hex.]
screen byte byte
number
305 SS_
Structure
The job mailbox has a defined length of four words. The structure is shown in the following
table:
The first word always contains the job number. Depending on the associated control job, up to
three parameters can be specified.
The job number corresponds to the screen identification number. This enables all actions
initated by a specific screen to be determined exactly by the screen identification. The
parameters specify the action to be performed. Details can be found in the descriptions of the
associated screens.
Because only status changes for keys and buttons can be transferred to the controller, the
connection between the operator panel and the controller must be monitored for correct
operation. This monitoring is performed using the sign-of-life bit of the operator panel from the
"Coordination" area pointer. The sign-of-life bit is inverted by the operator panel in one second
intervals.
The "FC_HMI_MANUAL" function checks cyclically whether the sign-of-life bit has been inverted
to determine whether the connection to the operator panel still exists. If no inversion of the sign-
of-life bit has been determined during a time interval, the job mailbox will be cleared. The time
interval is defined by the following parameters:
DB_HMI_CONFIG.MANUAL_COMMON. SCREEN_ACTIVE_TIME
! Important
Because the sign-of-life bit is not a real-time signal, depending on the data traffic
on the network and the number of processes running on the operator panel, it can
take longer than one second before the signal has changed its status. To ensure
shorter response times and a faster shutdown of the manual operations, we
recommend that the function keys of the operator panel are used as PROFIBUS
DP direct keys.
The machine manufacturer is responsible for the reliable execution of the manual
operation.
The controller can use this data area to query the status of the operator panel, e.g. startup of
the operator panel, current operating mode and ready for communication.
The structure of the "Coordination" area pointer with the length of one word:
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Startup
bit
Operating
mode
Sign-of-life bit
Bit assigned
Bit not assigned (reserved)
3.9 FC_HMI_BASIC
The basic functions of SICAR are realized using the "FC_HMI_BASIC" function. This FC is
responsible for the coordination of the interface DBs and HMI screens.
Figure 3-7 shows the parameters of the FC; Table 3-4 describes its parameters.
FC_HMI_BASIC parameters
If several SICAR operator panels are to be connected with a controller, a new DB interface must
be provided in the controller for the second and each additional operator panel. This requires
the duplication of the SICAR DBs and the modification of the numbers in Step7 and WinCC
flexible.
The following table lists the steps required to change the DB numbers.
Because at any one time only a single operator panel can access the hardware diagnosis, an
operator panel change must be configured for this purpose.
! Important
4.1 Header
The SICAR header shows the operator general information about the machine status.
(7)
The following states are possible for the machine status display:
Runtime interface
The "Status display" is controlled with the following status bits in the DB_HMI_DATA data block:
The following states are possible for the initial state display:
Interface
The "initial state" display is made using the following bit in the
DB_HMI_DATA data block:
Configuration
No configuring required.
The user has two text fields available to display machine-specific text.
Runtime interface
The text is controlled using two variables in "DB_HMI_DATA". The text assigned to the value of
the variable of the WinCC flexible – text list is displayed as text.
Configuration
The "SO_00_HeaderText2" text list is preconfigured so that the screen name of the selected
screen is displayed.
This requires that the screen number of the selected screen is transferred from the WinCC
flexible "Screen number" area pointer into the "DB_HMI_DATA.HEADER.TEXTINDEX_2"
variable.
For example:
L DB_HMI_DATA.AREAPOINTER.SCREEN_NUMBER.SCREENNUMBER
T DB_HMI_DATA.HEADER.TEXTINDEX_2
This is programmed in the FC67 in the Demo program.
The machine manufacturer must extend the "SO_00_HeaderText2" text list if new screens are
to be added to the WinCC flexible configuration.
The sign-of-life in the header displays the operating mode of the PLC. A periodic flashing in
intervals of approximately one second indicates that the controller is in the "RUN" operating
mode.
The "STOP" operating mode is indicated by a orange smiley.
Field Interface
No communication between HMI and PLC
Runtime interface
Field Interface
Sign-of-life DB_HMI_DATA. HEADER.WATCHDOG
Display of the sign-of-life of the CPU
The machine status display in the header can be displayed as a symbol or as text.
The "SS_00_SelectHeader" screen provides both views.
The replacement of the header elements in the permanent window for WinCC flexible with the
corresponding elements from the "SS_00_SelectHeader" screen can be used to change the
display of the status signals.
The operator information is a text output field used to display information for the operator. The
text display is located above the horizontal buttons.
Runtime interface
Two runtime variables are used to control the dynamic behavior of the text output field.
The first variable, "DB_HMI_DATA. GLOBAL.PROMPT.INDEX", is used to select which text
from the WinCC flexible text list is to be displayed.
The second variable, "DB_HMI_DATA.GLOBAL. PROMPT.ATTRIBUT", is linked with the
attribute of the text output field. The variable so controls the color change of the flashing of the
text output field.
Configuration
The WinCC flexible SO_00_OperatorPrompt text list contains the text to be displayed in the text
field for operator information.
5. Manual Operating
5.1 Overview
The operator can use the manual operating screens to perform movements, activate/deactivate
machine elements, select cycle type and perform other actions for which a selection must be
made.
All screens from the manual operation area have the same general structure (see Figure 5-1)
(1) The two upper vertical softkeys are not assigned to any function line.
(2) This button is assigned to the left-hand function in the first line.
(3) This button is assigned to the right-hand function in the first line.
Assignment to the corresponding function lines
The "symbolic/absolute" toggle key can be used to switch between the symbolic and the
absolute designation of the inputs and outputs (e.g. I1.0, O1.0) that are assigned to the
corresponding movements/functions (see Figure 5-3).
The represention in absolute form is displayed only for a parameterizable time. After this time
has expired, the SICAR system switches automatically to the symbolic representation.
Scrolling
A scroll function can be used to fetch all configured actions for a maximum display of five (10"
device) or three (6" device) movements/functions per page.
When the scroll function is performed, the complete screen is always opened (all displayed
function lines will be replaced by the function lines present on the next page).
When the last page is reached and the page-up key is pressed, the display changes back to the
first page. Similarly, when the first page is reached and the page-down key is pressed, the
display jumps to the last page.
You cannot change the screen (the page is locked) while a movement or function is being
performed.
The current page number and the total number of pages are displayed at the bottom in each
screen. The page number field, which is an input field, can be used to directly select a page by
entering the appropriate page number from the keyboard or keypad.
Other than the keys at the immediate left and right of each movement or function, the screens
for the manual operation also support touch panel operation (for operator panels with touch
functionality).
As shown in Figure 5-4, each movement/function can be initiated by touching the corresponding
function in the appropriate areas.
To prevent the inadvertent initiation of a movement, the system is designed so that to initiate a
movement, it must first be selected by touching the appropriate touch-sensitive surface. The
selection of the movement is confirmed by a flashing square next to the movement arrow (see
number (2) in the figure.
Once the movement has been confirmed, the movement can be initiated by subsequently
touching the touch-sensitive area. As confirmation, the square next to the triangle becomes dark
blue.
The function remains selected until one of the following events occurs:
Another movement is selected.
Scroll to another page.
Select another screen.
The sign-of-life monitoring deactivates the movement.
Designation (4)
The "Designation" object is the title for the movements/functions. Scrolling the screen updates
the designations of the functions with the associated description of the associated line on the
current page.
The text items are configured in text lists for WinCC flexible. The "Designation" element does
not have any runtime interface.
Position (9)
The "Position" object can be used to display a numeric position value. The position field is
optional and can be hidden for each movement or function.
Executability (1 and 7)
The "Final state" element represents movement- or function-specific end positions in both
directions (e.g. left/right, up/down, open/closed).
If a target position has not yet been reached, the associated text of this position appears on
a gray background.
If the target position has been reached, the appropriate text is displayed with a yellow (left-
hand side) or green (right-hand side) background.
Various text items for the symbolic and the absolute view can be displayed for each "Final state"
element. The text items are configured in text lists for WinCC flexible.
The status information must be supplied as binary signals via the runtime interface.
Execution (3 and 5)
The "Execution" element shows the status of the output from which the associated
movement/function is controlled.
If the output is deactivated, the associated text appears with a gray background.
If the output is activated, the appropriate text is displayed with a yellow (left-hand side) or
green (right-hand side) background.
Various text items for the symbolic and the absolute view can be displayed for each "Execution"
element. The text items are configured in text lists for WinCC flexible.
The status information must be supplied as binary signals via the runtime interface.
The "Key/button activated" element indicates whether or a key, button or a touch-sensitive area
has been confirmed by the control program (processed). The status information is supplied by
the corresponding function block from SICAR.
The "Key/button activated" element acts as follows for a key-operated panel:
When a key is pressed and confirmed by the controller, the rectangle becomes dark blue.
If a key has not been pressed or not confirmed by the PLC, the rectangle is represented as
an unfilled contour.
The "Key/button activated" element confirms the preselection or selection of a function on the
touch display with the following states (further details for the preselection are contained in the
"Touch panel support" section):
If a function has been preselected, this is indicated by the flashing of the rectangle (a dark-
blue and contoured rectangle flashes in intervals of approximately 0.25 seconds).
If the touch-sensitive surface of a function is activated a second time and this is confirmed
by the controller, the rectangle becomes dark blue.
If the function is not active or preselected, the rectangle is displayed as an unfilled contour.
Each assigned function line is assigned to a fixed function number. The first line is assigned
function number 1, the second line is assigned function number 2, etc.
Lines that are not displayed (all elements hidden) do not interrupt the assignment.
Figure 5-6 shows the assignment of the function numbers over several pages.
The manual operating screen contains a maximum of 100 movement or function lines. This
allows special movements to be performed manually using keys. Every movement can be
performed in two directions, such as input/output, open/close, up/down, forwards/backwards.
It is also possible to track each movement during its execution.
If there are more movements than can be displayed on the screen at the same time, the
movements will be displayed on several pages. The individual pages can be grouped. This
means each group forms its own manual operating screen for the operator and, for example,
can be assigned to a specific plant section.
Each manual operating screen has its own text lists, parameter records and controller interface.
These parameters and text lists have the same basic structure and are defined using the name
of the associated screen.
The "DB_HMI_CONFIG" configuration DB and the "DB_HMI_DATA" runtime DB have their own
data area for each screen; this data area is also defined by the designation of the associated
screen. The name of the variable areas of each manual operating screen in the data blocks is
shown in the table.
The name of the screen in The name of the area in "DB_HMI_DATA" and
WinCC flexible "DB_HMI_CONFIG"
SS_11_ManualMovement SCREEN_MANUAL
SS_12_UserOperation SCREEN_USER
SS_13_SpecialFunction SCREEN_SPECIAL
5.4 Configuration
The time after which the absolute designation is switched back to the symbolic designation is
stored in DB_HMI_CONFIG:
Address: DB_HMI_CONFIG.MANUAL_COMMON.
ABSOLUTE_DISPLAY_TIME
Format: TIME
Range of values: T#1MS…T#24D20H31M23S647MS
Default setting: T#10S (10 seconds)
This parameter is independent of the screen.
The time factor that determines how long a preselection initiated by touch remains active for a
function is defined in DB_HMI_CONFIG in the following data address:
The number of required movement or function lines must be defined for each manual operating
screen in the associated data block variable in DB_HMI_CONFIG.
Address: DB_HMI_CONFIG.
SCREEN_AAAAAA.NUMBER_OF_ROWS
where AAAAAA = name of the screen (see Table 5-1)
Format: INT
Range of values: 1…64 – for the "setup" and "power up condition"
1…32 – for units, nut runners and nut runner groups
1…16 – for the cycle type and the OEM screen
Default setting: The maximum number of available lines
To assign the manual operation to function groups, the manual operating screen can be
selected more than once with different movement lines on the operator panel. When the screen
is selected, the first and the last page number of the pages relevant for this screen selection
must be entered for the variables specified below. This is done using the WinCC flexible
"SetzeWert" function that is configured in addition to the "ActivateScreen" function on the key or
button that selects the manual operating screen. Note that the page number of the last page
must be assigned before the page number of the first page.
WinCC flexible configuration of the screen selection of the manual operating screen in groups:
Note
Note that the page number of the last page must be assigned before the page
number of the first page.
The individual function lines are configured at the following address in the
Address: DB_HMI_CONFIG.SCREEN_AAAAAA.ROW_XX
where AAAAAA = name of the screen (see Table 5-1)
and XX is the number of the associated function line
Format: BYTE
Range of values: See Figure 5-9 and Figure 5-2
Default setting: B#16#00
Byte n
Nibbling n Nibbling n+1
7 6 5 4 3 2 1 0
Configuration 1: hidden left
Configuration 1: hidden right
Configuration 1: position hidden
Configuration 1: all other elements hidden
Bit assigned
Bit not assigned (reserved)
Manual operating screen – structure of the configuration interface
Only one configuration can be active for all movements or functions at any one time. The
associated active configuration (configuration 1 or 2) can be selected dynamically using the
"SELECT_CONFIG" input parameter for the "FC_HMI_MANUAL" function.
The dynamic changing of the configuration settings allows movement or function elements to be
displayed or hidden depending on the associated machine status (e.g. machine in manual
operation). Typical examples are:
The table shows all possible parameter values for the various configurations.
Example configurations
Note
SICAR does not interlock the output signals with the "hidden" configuration
settings. This means, even when the "Executable" and "Key pressed" elements
are configured as hidden, the output signals will still be initiated by pressing the
keys to the left or right of the movement or function or by touching the buttons.
The machine-specific control program must realize any required interlock
functionality.
All text items displayed in the manual operating screens are configured in the WinCC flexible
text lists. Each screen has its own text list, where the text can be specified for each element.
The text lists have the structure shown in the figure.
Display Text
Format Decimal
Value 10 Line #1 - function name – symbolic
Value 11 Line #1 - function name – absolute
Value 12 Line #1 – left confirmation – symbolic
Value 13 Line #1 – left confirmation – absolute
Value 14 Line #1 – left final state – symbolic
Value 15 Line #1 – left final state – absolute
Value 16 Line #1 – right confirmation – symbolic
Value 17 Line #1 – right confirmation – absolute
Value 18 Line #1 – right final state – symbolic
Value 19 Line #1 – right final state – absolute
Value 20 Line #2 - function name – symbolic
Value 21 Line #2 - function name – absolute
…
Manual operating screens – structure of the text lists
The following examples show all required steps for configuring the display text for a movement
to be displayed in the third line on the first screen page.
The movement to be specified is a numeric axis that is to move left or right.
The movement is initiated by the Q0.1 and Q1.1 outputs. The movement is limited by limit
switches connected to the I0.1 and I0.1 inputs. Consequently, the display text is as follows:
The following tables show all required positions of the text lists based on the above assignment:
Color changes show the details of the binary state of a movement or function
Only the "Position" element shows a numeric position value.
The data addresses in the DB_HMI_DATA data block control the details concerning the binary
state of a movement or function.
Address: "DB_HMI_DATA".SCREEN_AAAAAA.ROW[XX]
where AAAAAA = name of the screen (see Table 5-1)
and XX is the number of the associated function
Format: BYTE
Range of values: See Figure 5-13 and Figure 5-14
Default setting: ---
Each grouping element represents a movement or function.
The figure describes the structure of the interface for the function byte.
Byte n
7 6 5 4 3 2 1 0
Executability, left-hand side
executable, right-hand side
Execution confirmation, left-hand side
Execution confirmation, right-hand
Finalside
position, left-hand side
Final position, right-hand side
Bit assigned
Bit not assigned (reserved)
Manual operating screens – structure of the runtime interface
Bits 0…5 control the display of the information concerning the binary status (the function for bits
6 ... 7 is described in Section 8.6).
! Important
Bits 6 and 7 of the runtime data interface are used as control signals (operator
panel controller). This means the bits that supply information about the status
must be addressed individually. If all status information was written concurrently
with a single byte transfer command, the control signals would be overwritten and
falsified.
Guidelines
The information items that provide the binary status are not mutually interlocked so that a real
representation of the input and output signals is produced.
The following guidelines, however, provide a general statement of how the information items
that provide the binary status can be used in practice:
The two "Execution" displays should never be active concurrently for a single movement.
Otherwise this would provide the impression that the movement would be performed at the
same time in both directions.
The two "Final status" displays should never be active concurrently for a single movement.
This would provide the impression that the movement had reached both end positions (at
opposite directions) at the same time.
The two "Executable" and "Final status" displays should never be active concurrently for a
single movement. Otherwise this would provide the impression that the movement is
executable although the final position has already been reached.
The "Execution" and "Final status" displays should never be active concurrently for a single
movement. This would indicate that a movement or function is currently active although the
final position has already been reached.
In contrast to the interface for the binary status, the "Position" interface does not have its own
data address for the individual movements or functions.
Example
A position value should be displayed for the manual movement no. 3 (display in the
"SS_11_ManualMovement" screen, page 1, line 3).
Consequently, the machine-specific program must implement the following logic:
IF (active screen == "SS_11_ManualMovement" screen) AND
IF (current page == 1), THEN
DB_HMI_DATA.MANUAL_COMMON.POSITION[3] = value
The selected screen and the active page can be determined using the following data addresses
in the DB_HMI_DATA data block:
Selected screen
Address: DB_HMI_DATA.
GLOBAL.SCREEN_ID
Format: WORD
Range of values: W#16#0000 … W#16#FFFF (1…65535)
for the idenitification of the screen, see Table 5-4
Default setting: ---
Current page
Address: DB_HMI_DATA.
MANUAL_COMMON.CURRENT_PAGE
Format: BYTE
Range of values: B#16#01…B#16#13 (1…13)
Default setting: ---
Address: DB_HMI_DATA.MANUAL_COMMON.
ROW_VISIBLE_FIRST
DB_HMI_DATA.MANUAL_COMMON.
ROW_VISIBLE_LAST
Format: WORD
Range of values: W#16#0001…W#16#0040 (1…64)
Default setting: ---
The "first and last line" details can be used as an alternative method to determine whether the
movement is currently being displayed.
! Important
A movement or function can be initiated using one of the following operator actions:
with the keys indicated by the corresponding triangle icon;
by touching the appropriate button for the corresponding movement.
SICAR provides two different interfaces that the machine-specific program can use to evaluate
these operator commands.
The "job mailbox" is used as data interface to send jobs from the operator panel to the
controller. A job to be performed by the control program is then initiated with an operator input.
The "job mailbox" is used by all SICAR screens.
The other interface is screen-specific and, in contrast to the "job mailbox", uses binary signals.
Either the "job mailbox" or the "binary control interface" can be used to initiate a movement or
function.
The data addresses of the "job mailbox" belong to the DB_HMI_DATA.GLOBAL and defined as
follows:
Address: DB_HMI_DATA.
GLOBAL.JOB.NUMBER
GLOBAL.JOB.PARAMETER_1
GLOBAL.JOB.PARAMETER_2
GLOBAL.JOB.PARAMETER_3
Format: WORD
Range of values: W#16#0000…W#16#FFFF
Default setting: ---
When the operator panel initiates a movement or function (for example, an operator presses a
key at the left or right of the movement), the following information will be displayed in the "job
mailbox":
The code for identifying the screen ("job number" parameter in the job mailbox) for the manual
operating screens is described in table:
The "SS_11_ManualMovement" screen is active and displays the first screen page.
When the operator presses the left key that shows the triangle of the second movement line
(function number 2), the following data will be displayed in the "job mailbox":
When the operator releases the key, the values for parameter 1 and parameter 2 will be cleared
(value W#16#0000).
! Important
The "job number" will not be cleared when the operator releases a key used to
initiate a movement.
The "job number" will be set when one of the operating screens becomes active.
The machine-specific user program must analyze the "job mailbox" data and initiate the required
commands for performing the movement or function.
The "binary control interface" is a interface that uses binary signals. Each movement or function
is assigned two binary signals that represent a possible direction of the associated movement or
function.
Address: DB_HMI_DATA.SCREEN_AAAAAA.ROW[XX]
where AAAAAA = name of the screen (see Table 5-1)
and XX is the number of the associated function
Format: BYTE
Range of values: See Figure 5-13 and Figure 5-14
Default setting: ---
Byte n
7 6 5 4 3 2 1 0
Left movement/function activated
Right movement/function activated
Bit assigned
Bit not assigned (reserved)
Manual operating screens – structure of the control interface
When a movement or function is initiated from the operator panel (for example, when the
operator presses a key assigned to a function line), the control bits will be set; the control bit will
be reset when the function key is released.
Example
A manual operating screen is active and displays the first screen page.
When the operator presses the left key that shows the triangle of the second movement line
(function number 2), bit 6 for DB_HMI_DATA.SCREEN_MANUAL.ROW[2] will be set.
The bit will be reset when the operator releases the key.
5.7 FC_HMI_MANUAL
FC_HMI_MANUAL parameters
Note
The following table summarizes the steps required to create a manual operating screen.
All other operating screens differ only in the listed data addresses and the WinCC flexible
textlists.
6. Production-Data
Max. number of
Number per screen
screens
Shift counter 10 8
Process counter 20 8
Limit value 10 8
Cycle time 20 8
The production data screens can be selected via the function button “Production data” from the Main menu.
1 Process counter
1 Shift counter
1 Cycle time
1 Limit value
Depending on the number of activated screens in the PLC, you can select with the buttons on the left side
the respective screen.
The buttons are automatically shown on the screen, no user action necessary.
The naming for this buttons is to realize directly in WinCC flexible ES.
Depending on the number of activated screens in the PLC, you can select with the buttons on the left side
the respective screen.
The buttons are automatically shown on the screen, no user action necessary.
The naming for this buttons is to realize directly in WinCC flexible ES.
While pressing the Reset Total button, two additional buttons appear.
Pressing “Reset” resets the 10 shift counter of the selected screen.
Pressing “Cancel” abort the Reset function.
Pressing one of the indication fields change the indication between Target / Value and Average / Count.
The value “Average” is the calculated result of the number of indicated cycles “Counts”.
The values Average and Counts can be reset in the PLC.
Depending on the number of activated screens in the PLC, you can select with the buttons on the left side
the respective screen.
The buttons are automatically shown on the screen, no user action necessary.
The naming for this buttons is to realize directly in WinCC flexible ES.
In order to measure the runtimes of individual steps in a sequence cascade, the appropriate sequence
markers could, for example, be pointed at the “Run bits”.
For reset of Average and Count in all screens you have to assign value 1 to the variable
“#Cycle_time_pic_1.Cycle_time_Reset_Average”
Value 1 will be reset from the block FB997.
If value “Remain” has reached the “value “Prewarn” the respective line is indicated in orange colour and in
the PLC a bit is available for further use e.g. in an alarm system.
If value “Remain” has reached 0 the respective line is indicated in red colour and in the PLC a bit is available
for further use e.g. in an alarm system.
While reaching value 0, a button “Reset” appears on the right side of the respective limit value.
Depending on the number of activated screens in the PLC, you can select with the buttons on the left side
the respective screen.
The buttons are automatically shown on the screen, no user action necessary.
The naming for this buttons is to realize directly in WinCC flexible ES.
Alarm:
If Remain value = 0, the appropriate line is given a red background and a user bit is supplied for further
evaluation.
The Line could be stopped with this bit, using the basic start condition for the respective zone.
Reset of alarms:
During every time it is possible to set the “Remain” value to the “Set” value.
Press the field with the describing test of the limit value you wish to set.
On the right a “Reset” button appears.
If value “Remain” has reached 0, a button “Reset” appears automatically on the right side of the respective
limit value.
If there is one active prealarm or alarm in the limit value screens, this is indicated on each button “Production
data”.
There are “Prewarn” and “Alarm” bits available for each limit value for further use in the PLC.
There are also information about "Prewarn" and "Alarm" per screen, as well as the information for
"Prewarn_active" and "Alarm_active" overall is available.
These values are only provided in "Limit_value_pic_1.x"
If there is a need of additional screens the respective entries must be done in the section static variables of
the FB982.
The following example shows the initialisation for 3 process counter screens, 3 shift counter screens, 2 cycle
time screens and 2 limit value screens.
After each modification in the static part of the FB982, the DB996 has to be regenerated:
In FC151, select network with the call FB982, DB996 and regenerate the DB996.
Download the blocks to the PLC.
7. Diagnostics
RSE diagnostics are generated based on the specific Hardware Configuration, the required Diagnostic
blocks, and the configured Message and Error texts
Select this both check box if the dialog for configuring RSE should be called up while the configuration is
being saved and compiled
Note:
If you are working with an integrated WINCCflex project no further actions are necessary in WINCCflex.
The alarm screens display the alarm messages, general messages and system messages in
tabular form. The "messages" screen displays the messages and alarms currently pending; the
"message archive" screen displays the contents of the alarm buffer.
Alarm events are saved to an internal, non-volatile buffer. The size of this alarm buffer depends
on the HMI device type.
The screen structure of the two "messages" and "message archive" screen forms is identical.
The "interface for alarms and messages" data block is defined by the WinCC flexible
"SO_00_Alarm" and "SO_00_Message" variables for fault messages and operational
messages, respectively.
7.2.3 Configuration
The alarm or message text is configured in the area of the message display object. For further
information, refer to the documentation for WinCC flexible.
The message display of the alarm view displays selected message events from the alarm
buffer. The configuration specifies which events are displayed. The alarm window shows the
alarm events selected in the properties dialog.
Setting for the alarm display object in the "Alarm archive" screen
The "DataInterface" screen can be used to display for diagnostic purposes the signals
transferred between the controller and the external devices. Up to sixteen diagnostic interfaces
with freely configurable names can be created. Each diagnostic interface can display 16 inputs
and 16 outputs. The interface can be selected in a selection window.
The runtime interface for the "Interface" screen consists of three variables. The first,
DB_HMI_1_DATA.SCREEN_INTERLOCK.SELECTION, represents the current interface
selected from the selection window.
The inputs/outputs to be visualized must then be copied to the following addresses depending
on the currently selected interface:
Address: DB_HMI_1_DATA
SCREEN_INTERLOCK.SIGNALS.INPUT
Format: WORD
Range of values: The status of each bit is displayed in the screen by the
associated LED element.
Default setting: -
Address: DB_HMI_1_DATA
SCREEN_INTERLOCK.SIGNALS.OUTPUT
Format: WORD
Range of values: The status of each bit is displayed in the screen by the
associated LED element.
Default setting: -
7.3.3 Configuration
Up to sixteen interface descriptions can be defined and selected from a selection window. A
WinCC flexible text list can be used to specify a name for each of these interfaces:
The following text lists can be used to specify a designation for each input and output of all the
interfaces:
7.3.4 PLC-Interface
Programming of the DataInterface has to be done in FC64.
FC64 is called in FC67.
Change in the next two networks the respective inputs and outputs,
You can see here the current SICAR Version as well as the versions of all encrypted Sicar system blocks.
This screen shows the Set-Version belonging to the current SICAR Version and the Online block version in
the PLC.
If there are differences the respective blocks are indicated with red or orange colour.
Orange: Development block is loaded
Red: Versions are different
PLC-blocks:
DB940: Block-name, Block-number, Set -and Online version are stored in DB940. and is prepared for 40
blocks.
E.g. FB943, Version 1.1
The Online version is written from each system block itself into the DB940.
FC942: Comparision of Set –and Online version, result is stored in DB940, Check_x.
8. Hardware Diagnostics
With the button “Hardware Diagnostic” the following screen is coming up and displays
the actual status of the DP-Mastersystem/PNIO-System, MLFB of PLC and the
Firmware Version
The diagnosis is based on the PNIODiag standard diagnostic package that can be
downloaded from the article ID:26996747 in the Siemens product support.
(1)
(2)
The selection box can be used select a single station for which detailed diagnostic data can be
displayed.
The "Legend" screen shows the states that a station can assume in the network overview.
The "Detailed diagnosis" screen displays detailed diagnostic information for the selected station
and groups them into two main areas.
(1)
(2)
Station diagnosis
The station diagnosis of the screen shows the basic information for the selected station.
Station status
Manufacturer identification
Device name
Subnetmask
Gateway address
Number of faults present, sorted according to fault type and total number of faults
(This information are only diplayed in case of an error)
The information actually displayed in the "Detailed fault information" screen area depends on
the diagnostic capabilities of the selected station.
The fault information supplies the fault location (slot number, subslot number, channel) and the
designation of the fault (wire breakage). Additional details, such as the data format and the
channel type, are also displayed. The fault information is also displayed in hexadecimal
notation.
If required, the device manual can be consulted to obtain the meaning of the hexadecimal
value.
A station diagnosis can be fetched for each detected station. The format of the displayed data
depends on the station type:
For PROFIBUS DP slaves, the channel diagnosis is output in text form with the device-specific
diagnosis shown in hexadecimal notation.
The diagnosis of PROFINET IO stations differentiates between direct PROFINET IO devices
and PROFIBUS slaves connected with a PROFINET IO system using an IE/PB link:
- PROFINET device:
The channel and slot diagnosis is output in text form. The manufacturer-specific diagnostics are
displayed in hexadecimal notation.
- PROFIBUS slaves on the IE/PB link:
The diagnostic data (structure, see EN 50 170 Volume 2, PROFIBUS) is shown only in
hexadecimal format. Only the status of the module is displayed for an IE/PB link itself.
You can set in the "Trigger history" screen which station in which system is to be monitored in
order to monitor transient events and also view the recorded events.
This is particularly useful when the events are too fast for them to be evaluated in the station
diagnosis.
(1)
(2)
(3)
Press "Start trigger" to activate the trigger. The state remains active even for a change to a
different screen and continues to run in the background. The trigger is running when the
background is green.
Press "Stop trigger" to deactivate the trigger after which the events can be viewed. The trigger is
stopped when the background is red.
Press "Clear ring buffer" to clear the ring buffer. To prevent data falsification, clear the ring
buffer before using the trigger and when the address is reset. Clearing the ring buffer places the
trigger in the stopped state should it be active.
The PNIODiag function block can be used for the diagnosis of PROFINET IO and PROFIBUS
DP systems. For this purpose, the PNIODiag function block determines general system status
information and, if required, detailed diagnostic information. This information is then displayed
using the visualization.
The PNIODiag function block provides the following functions for PROFIBUS DP and
PROFINET IO systems:
The PNIODiag function block call must be made in the OB1, OB82, OB83, OB86 and OB100
(OB101, OB102) execution levels. The order and content of the 20-byte temporary local data of
the organization blocks must not be changed.
The IN0 input parameter specifies the DB number 128 for saving the diagnostic data. Because
the creation of the data block for the data storage is specified in OB100, the DB number must
also be specified in the OB100. If no value is specified, the DB200 data block will be created
automatically.
Should an error occur while processing the block, the "OUT1" output parameter will contain an
error code that helps the Support department with troubleshooting.
Note
The required S7 data blocks and the S7 function block do not contain any symbol
information. An interface description for the S7 modules is not available. The S7
modules should be used only in conjunction with the provided visualization.
Note
Note
The "Drive status" screen displays the control and status signals of the drive selected from the
selection window.
(1)
(2) (3)
The "Drive alarms" screen displays the malfunctions and warnings of the selected axis.
(1)
(2)
(3)
The "Drive values" screen displays the actual values, set values and the staus of the
Drive FB.
(1)
(2) (4)
(5)
(4)
(6)
WinCC flexible "SO_40_Drive_G120_Name" text list. Each configured drive must have a
position in the text list.
The "Moby-I diagnostics" screen shows the status signals and error messages of a read-write
device (SLG). The data is fetched and assigned by a standard block from the Moby interface
module (ASM).
The signals and error messages from several interface modules can be displayed in the screen.
You can select several Moby SLGs in the selection field. Each Moby SLG provides its own
interface.
"Status of the SLG" area displays the states of the selected SLG.
The "MOBY SLG error messages" area displays MOBY-specific error messages.
The following table contains a list of all supported MOBY interface modules with the
associated FC:
The data exchange between the controller and the ASM is performed using the FC44, FC45 or
FC46 function, depending on the ASM type. The control and feedback signals to and from the
ASM, and the error messages can be found in the so-called command data block.
The "Moby I diagnostics" screen displays the information contained in these command data
blocks.
The structure of the command data block depends on the associated block.
The designations of the read-write devices must be specified. The text items are stored in the
WinCC flexible "SO_57_MobySLGName" text list. Each configured MOBY SLG must have an
entry in the text list.
! Important
The text items for non-configured (unused) MOBY SLGs must be deleted.
The FC_HMI_MOBY supplies data to the WinCC flexible screens for the Moby diagnostics. The
displayed data is fetched from the command data block.
The user must call this function once cyclically in the OB1 for each configured MOBY SLG,
where MOBY_INDEX matches the corresponding values from the WinCC flexible "SO_57_
MobySLGName" text list (see sample program).
The "SINAMICS status" screen shows the control and status signals of the SINAMICS axis
selected from the selection window.
The "SINAMICS position" screen shows the positioning status signals and positioning data,
such as position, block and override of the selected axis. The data, however, is available only
for those SINAMICS axes operated as positioning axes (EPOS).
Note
The "SINAMICS position" screen does not contain any information when a
SINAMICS S120 without positioning functionality is used.
The designations of the axes must be configured. The text items are stored in the
"SO_80_SinamicsAxis" WinCC flexible text list. A position in the text list must be present for
each configured axis. The text list that must be created for each drive group is displayed or
hidden depending on the selected CU.
! Important
! Important
The value of the text list entry must match the drive object number of the drive
group.
The FB_HMI_SINAMICSCU3x0 supplies the WinCC flexible screens for the SINAMICS
diagnostic screens. The displayed data is fetched directly from the drive as parameter requests
using acyclical communications services.
The function block must be fetched once cyclically with the appropriate diagnostic address
("DRIVE_DIAGADDR" parameter) for each CU. The "DRIVE_ENABLE" parameter assigned to
the selected CU (drive group) must be used to enable the FB call. In addition, the text list with
the associated drive object numbers assigned to the drive group must be displayed.
9. System screens
The "System" screen contains general system functions, such as password and user
administration, the language setting for the user interface, lamp test, clear alarm history and
message archive.
"System" screen
Import/export password
This function can be used to export the password list to a memory card or import the password
list from a memory card. This makes it possible to specify the password list for only one
machine and then transfer it to the other machines.
User logoff
This function is used to reset the current password level to level 0 (user without any special
rights).
This function is used to clear the message buffer. This includes all messages that have
occurred until this time.
Lamptest
The DB_HMI_DATA.GLOBAL.LAMPTEST variable has the 1-signal while the key or button
remains pressed.
The "Change language" button can be used to switch between the languages installed on the
operator panel.
A maximum of three languages can be loaded onto the operator panel. The standard project for
SICAR is delivered in two languages:
German
English (United States)
F-Program Signature
If a Failsafe-PLC is in use the CRC-checksum of the failsafe program has to be shown here.
It must be programmed in FC984.
PLC-cycle time
The current PLC cycle time has to be shown here.
It´s programmed in OB1.
Increase/reduce contrast
These function keys are used to set the contrast of the operator panel.
System control
Pressing this function key opens the window for the system control of the operating system.
After pressing the "Clean screen" function key, the operator panel user interface switches for a
parameterizable time to an empty screen page on which the touch function is deactivated.
During this time, it is possible to clean the screen without the danger of inadvertently initiating
some function.
Pressing the "Touch calibration" button starts the calibration of the touch screen.
Exit runtime
Pressing this button exits the WinCC flexible runtime environment and switches to the operating
system level.
The user can use this screen to monitor the control variables for diagnostic or maintenance
purposes.