4.
User Guideline SICAR@TIA DiagAddOn
Warranty and Liability
The Application Examples are not binding and do not claim to be complete regarding the circuits shown,
equipping and any eventuality. The Application Examples do not represent customer-specific solutions. They
are only intended to provide support for typical applications. You are responsible for ensuring that the
described products are used correctly. These application examples do not relieve you of the responsibility to
use safe practices in application, installation, operation and maintenance. When using these Application
Examples, you recognize that we cannot be made liable for any damage/claims beyond the liability clause
described. We reserve the right to make changes to these Application Examples at any time without prior
notice. If there are any deviations between the recommendations provided in these application examples and
other Siemens publications – e.g. Catalogs – the contents of the other documents have priority.
We do not accept any liability for the information contained in this document.
Any claims against us – based on whatever legal reason – resulting from the use of the examples,
information, programs, engineering and performance data etc., described in this Application Example shall
be excluded. Such an exclusion shall not apply in the case of mandatory liability, e.g. under the German
Product Liability Act (“Produkthaftungsgesetz”), in case of intent, gross negligence, or injury of life, body or
health, guarantee for the quality of a product, fraudulent concealment of a deficiency or breach of a condition
which goes to the root of the contract (“wesentliche Vertragspflichten”). The damages for a breach of a
substantial contractual obligation are, however, limited to the foreseeable damage, typical for the type of
contract, except in the event of intent or gross negligence or injury to life, body or health. The above
provisions do not imply a change of the burden of proof to your detriment. Any form of duplication or
distribution of these Application Examples or excerpts hereof is prohibited without the expressed consent of
Siemens Industry Sector.
Manual page 1 / 24 Edition: 2019-01
4. User Guideline SICAR@TIA DiagAddOn
Table of contents
1. SICAR@TIA Demoprogramm 3
1.1 Guideline for PLC settings 3
1.1.1 System Resources 5
1.1.2 Clock memory & system memory 6
1.1.3 Basic monitoring 7
2. SICAR HMI 8
2.1 Guideline for HMI settings in WinCC 8
2.1.1 Device Setting WinCC Advanced´ 8
2.1.2 Connection Setting WinCC Advanced 9
2.2 Settings DiagAddOn 10
2.2.1 Configuration of movements 11
3. Implementation of an additional HMI 14
3.1 Changes in PLC-Project 14
4. User-Interface DB1000 15
4.1 OM_Seq 15
4.2 Common 16
4.3 OP-Mode 1..8 16
4.4 Lock Movement screens 17
4.4.1 Use case 1 19
4.4.2 Use case 2 19
4.4.3 Use case 3 20
4.4.4 Use case 4 21
5. External Screen select 22
5.1 PLC - „SCREENSELECT_DIAGADDON“ FC977 22
5.2 HMI 23
6. Misc 24
6.1 Sequence permanent in OM Auto 24
Manual page 2 / 24 Edition: 2019-01
4. User Guideline SICAR@TIA DiagAddOn
1. SICAR@TIA Demoprogramm
The TIA-project SICAR_TIA_DiagAddOn_Demo should be the entry to build up a project and contains all
basic function.
It´s prepared for a line with 1 HMI and 1 operation mode area.
1.1 Guideline for PLC settings
Rename the SICAR Demoproject with your own project name
TIA-Portal / Devices & Networks
Check PLC and IPC and change if necessary
Important PLC:
Indicate MB1 as clock memory byte
Indicate MB2 as system memory byte
Init „CALL_INIT_FC“ (FC1981):
Block „GLOBAL_INFO_FB“
In “PLC Tags” adjust constants for number operation modes and Panel.
See Online help.
HMI and operation mode area „CALL_OPMODE_PANEL_FC“ (FC1983):
Call and parameterize blocks „HMI_PANEL_FC“ und „OPMODE_FC“.
See Online help.
Call HMI, communication and op-mode areas for DiagAddOn – FC983:
Per HMI one call FC997
Per HMI one call FB962
Per op-mode area call FC995
See chapter 31_Initialization and operation modes
First block should be a generell message block without assignment to an operation mode area.
This block can include e.g. Profinet faults, …….
(Generell messages -> FB1001)
For each op-mode area the signals "Emergency stop", “Safety doors”, “Basic start conditions”
must be programmed in a message block.
Depending on the project additional signal like “Initial position” / “Position stop end of cycle”
(Op-mode area 1 -> FB1002)
Program user sequence cascades
- Sequence -FC (FC1004, etc.)
- Call “Sequence” FC998 and parameterisation of sequence infos
- Control outputs with step flags
- Call of Tec-unit, Drive interface, …..
“Sequence_Call” FC988
- Adjust Jump distributor
- Call sequence-FB with Instance-DB, e.g. FB1004, DB1004
- No calls of message blocks here
Program FC986
- Calls sequence-FCs for message blocks and sequence blocks
Manual page 3 / 24 Edition: 2019-01
4. User Guideline SICAR@TIA DiagAddOn
Sequence FB (FB1004, etc.)
- Programm Automatic
- Program Monitoring times per step or automatical measurement
- Branchings
Note for generation diagnosis:
It´s allowed to programm the sequence blocks (FB´s) in STL or LAD.
For reasons of diagnosis in this blocks it´s only allowed to use inputs / outputs / flags and databits of not
optimized datablocks.
If you need information of optimized datablocks you have to transfer this into flags or not optimized
datablocks.
Programming manual movements in the sequence blocks
Production datas
Manual page 4 / 24 Edition: 2019-01
4. User Guideline SICAR@TIA DiagAddOn
1.1.1 System Resources
Function Range
Blocks FB FC DB UDT Flag bytes
System library:
Initialisation and
MB1
sequence control 900-1299 900-1299 900-1299 900-999
MB2
incl. process-
diagnosis
The block range is reserved for sequence diagnosis and necessary blocks and it´s not allowed to
change.
MB1 and MB 2 is reserved for clock and system flags.
Manual page 5 / 24 Edition: 2019-01
4. User Guideline SICAR@TIA DiagAddOn
1.1.2 Clock memory & system memory
In the PLC hardware configuration it is mandatory to set
- the clock memory to memory byte 1
- the system memory byte to byte 2
Manual page 6 / 24 Edition: 2019-01
4. User Guideline SICAR@TIA DiagAddOn
1.1.3 Basic monitoring
The monitoring for operation modes should be programmed in the first message-FB of each op-mode area,
e.g. FB1002.
The following memory bits are relevant for starting an operation mode.
If one is missing a started operation mode is switched off immediately.
M 10.0 OP-Mode 1 emergency_stop
M 10.1 OP-Mode 1 safety door
M 10.4 OP-Mode 1 basic start condit
In the project SICAR_basic all these bits are preset with log1.
All project specific conditions have to be programmed instead of the log1 bit.
Additional messages can be programmed in additional messages.
The diagnosis of these messages will be displayed in the “diagosis” screen.
Manual page 7 / 24 Edition: 2019-01
4. User Guideline SICAR@TIA DiagAddOn
2. SICAR HMI
2.1 Guideline for HMI settings in WinCC
The Step7 demo_project contains a WinCC project.
2.1.1 Device Setting WinCC Advanced´
Configuration of the project specific used HMI type in menu “Device configuration / Device view / Properties
/ General / Change device” and select new device
Manual page 8 / 24 Edition: 2019-01
4. User Guideline SICAR@TIA DiagAddOn
2.1.2 Connection Setting WinCC Advanced
Configuration of the PLC - HMI connection in menu “Connections”
Configuring time synchronization for integrated devices
In our sample PLC is Master and synchronize the HMI´s.
Imortant: WINCC Advanced RT has to be started with admin rights.
Change properties of file “StartCenter.exe”, Properties/Compatibility/Run this program as an administrator
This is a precondition to write the time to the PC operation system.
Manual page 9 / 24 Edition: 2019-01
4. User Guideline SICAR@TIA DiagAddOn
2.2 Settings DiagAddOn
Project
Panel number (If you change the Panel number, restart DiagAddOn)
IP address of PLC
Manual page 10 / 24 Edition: 2019-01
4. User Guideline SICAR@TIA DiagAddOn
2.2.1 Configuration of movements
2.2.1.1 Parameterization of movement overview
A movement screen is activated by parameterization a text for the movement screen.
Manual page 11 / 24 Edition: 2019-01
4. User Guideline SICAR@TIA DiagAddOn
A movement row is activated by parameterization a movement text for the movement row in the middle field.
A movement row is deleted if you delete the corresponding movement.
Manual page 12 / 24 Edition: 2019-01
4. User Guideline SICAR@TIA DiagAddOn
Following entries can be done in a movement row:
1 2 3
45 5 6 7 8 9 10
1. Text for active indication
2. Text for limit position indication
3. Movement text has the most important function; the movement row is deleted if the movement text
has been deleted
4. Parameterization of the operand for the active indication
5. Symbol (e.g. item designation) of the active operand
6. Parameterization of up to 8 operands for the limit position indication
7. Symbol (e.g. item designation) of the limit position operand
8. Input of sequence to be effected by movement key
9. Input of step to be effected by movement key
10. Position value: Parameterization of data block and data double word
Hint: Use capital letters, DBx.DBDy
The parameterizations for the movement keys right are analogical.
The operands for the indications of action and limit position can also be used inversely by setting a slash
before.
If no operands for limit position / action are given the indications are generated directly out of the system.
- Limit position is feedback of LIMIT-M
- Action is feedback of ILOCK-M = 1 and LIMIT-M = 0.
Manual page 13 / 24 Edition: 2019-01
4. User Guideline SICAR@TIA DiagAddOn
3. Implementation of an additional HMI
If you want to connect more than one HMI with a PLC
- Insert an additional HMI in WINCC
- Change in WINCC Connections / Areapointer to IF_HMI_IDB_HMI[HMI_NR].Areapointer……
- The projects of the DiagAddOn must be identical on both HMI´s, *.mdb, *.s7l, *.sdf
- Adjust in DiagAddOn / System settings / Panel number and IP-Adress
- After change of Panel number restart DiagAddOn
3.1 Changes in PLC-Project
Change user constants No_HMI_panel
Change FC1983
Add a call HMI_PANEL_FC (FC9)
Add the new HMI to OP_MODE_FC (FC8)
Change FC983
Additional call FC997
Additional call FB962
Adjust IP-Adress in DB962
Manual page 14 / 24 Edition: 2019-01
4. User Guideline SICAR@TIA DiagAddOn
4. User-Interface DB1000
The interface between user-software and DiagAddOn-software is the user interface DB1000.
All necessary information’s are provided in DB1000 and can be used for further programming.
4.1 OM_Seq
Operation mode information per sequence 1-128 is provided in a databyte.
For further use in your program use symbolic programming.
Structure OP-Mode byte
.0= Automatik
.1= Inching
.2= Manual
.3= Inching_Step_+1 (activate step in Inching mode) / Hold in Step 1 (Automatic mode)
.4= Start
.5= Acknowledge (restart sequence watchdog time)
.6= Clock
.7= Synchronize
Manual page 15 / 24 Edition: 2019-01
4. User Guideline SICAR@TIA DiagAddOn
4.2 Common
Here is a general information if there is at least one message or sequence fault, e.g. control of a error lamp.
4.3 OP-Mode 1..8
In this section are specific information for each operation mode available.
// Sample to control a horn
Manual page 16 / 24 Edition: 2019-01
4. User Guideline SICAR@TIA DiagAddOn
4.4 Lock Movement screens
Lock of movements can be necessary if you work with several HMI.
Following signals in the User Interface DB1000 can be used.
Feedback from HMI_x – Movement button is pressed in any movement screen
Feedback from HMI_x – which movement screen is open, Value 1- 64
Lock all movement screens on HMI_x
Manual page 17 / 24 Edition: 2019-01
4. User Guideline SICAR@TIA DiagAddOn
Lock sequences belonging to a operation mode area on a specific HMI_x
Manual page 18 / 24 Edition: 2019-01
4. User Guideline SICAR@TIA DiagAddOn
4.4.1 Use case 1
If a movement is activated on HMI 1 all other HMI should be locked.
4.4.2 Use case 2
E.g. Lock movement screens 2 + 3 in HMI 2, if they are opened in HMI 2.
Manual page 19 / 24 Edition: 2019-01
4. User Guideline SICAR@TIA DiagAddOn
4.4.3 Use case 3
E.g. Lock HMI 2, if on HMI 1 movement screens 4 + 5 opened and a movement button is pressed.
Manual page 20 / 24 Edition: 2019-01
4. User Guideline SICAR@TIA DiagAddOn
4.4.4 Use case 4
Lock movements of sequences on HMI x, belonging to a specific operation mode area.
Line with HMI 1 and HMI 2.
HMI1 can execute movements in OP-Mode area 1 and 2
HMI2 can execute only movements in OP-Mode 2
OP-Mode 1 = Sequence 2 - 9
OP-Mode 2 = Sequence 10 - 30
Means, all movements for sequences in OP-Mode 1 = 2 – 9 locked on HMI 2
Manual page 21 / 24 Edition: 2019-01
4. User Guideline SICAR@TIA DiagAddOn
5. External Screen select
If you want to switch from the WINCC application to a specific DiagAddOn screen you can use the PLC block
„SCREENSELECT_DIAGADDON“ FC977., e.g. from a overview screen in WINCC directly to a movement
screen in DiagAddOn.
5.1 PLC - „SCREENSELECT_DIAGADDON“ FC977
Call FC977 in FC983
HMI_panel_number: The HMI you want to activate the DiagAddOn screen
Main_screen_no_to_HMI: e.g. 4 – Movementscreen
Sub_screen_no_to_HMI: max number of movementscreens 64. e.g. 1
Activate_Screen_Select: Bit to activate the screen
Remark: Bit is reset from FC977
Manual page 22 / 24 Edition: 2019-01
4. User Guideline SICAR@TIA DiagAddOn
5.2 HMI
Create a button and use the property Events
Event “Press”
- activate script “SwitchToDiagAddOn”
- Setbit any Bit in PLC for further use on FC997
Remark: Bit is reset from FC977
Manual page 23 / 24 Edition: 2019-01
4. User Guideline SICAR@TIA DiagAddOn
6. Misc
Different information concerning additional functionalities or handling.
6.1 Sequence permanent in OM Auto
If you want to keep a sequence e.g. in OM Auto independent of the selected OP-Mode in a OP-Mode area
you can realize by programming like this.
Sample: Sequence 4
In Seq-FC you overwrite the respective bits „OM_Seq[4].xxxx“ in DB1000.
Programming must be done before Call FC998.
Manual page 24 / 24 Edition: 2019-01
