Beruflich Dokumente
Kultur Dokumente
http://support.automation.siemens.com/WW/view/en/36435784
WCF_BLOCKS_MOTOR (FB620)
V 1.01, Entry ID: 36435784
SIMATIC
WCF_BLOCKS_MOTOR (FB620)
Application
WCF_BLOCKS_MOTOR (FB620)
V 1.01, Entry ID: 36435784
Automation Task
Automation Solution
Basic Information
Functional Mechanisms
Configuration and
Settings
Starting up the
Application
Operation of the
Application
Block Connectors
Further Notes
Bibliography
10
History
11
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 sound 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 this application example 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). However, claims arising from a breach of a
condition which goes to the root of the contract shall be limited to the foreseeable
damage which is intrinsic to the contract, unless caused by intent or gross
negligence or based on mandatory liability for injury of life, body or health. The
above provisions do not imply a change of the burden of proof to your detriment.
It is not permissible to transfer or copy these Application Examples or excerpts of
them without first having prior authorization from Siemens Industry Sector in
writing.
For questions about this document please use the following e-mail address:
online-support.automation@siemens.com
WCF_BLOCKS_MOTOR (FB620)
V 1.01, Entry ID: 36435784
Table of Contents
Table of Contents
Warranty and Liability ................................................................................................. 4
1
Automation Task................................................................................................ 7
1.1
Overview .............................................................................................. 7
Overview .............................................................................................. 9
Hardware and software components used......................................... 10
4.1
4.2
4.2.1
4.2.2
4.2.3
4.2.4
4.2.5
4.3
4.3.1
4.3.2
4.4
4.4.1
4.5
4.5.1
4.6
4.6.1
4.6.2
4.6.3
4.6.4
4.6.5
4.6.6
4.6.7
4.6.8
5
WCF_BLOCKS_MOTOR (FB620)
V 1.01, Entry ID: 36435784
Table of Contents
Bibliography..................................................................................................... 61
11
History............................................................................................................... 62
10
WCF_BLOCKS_MOTOR (FB620)
V 1.01, Entry ID: 36435784
Automation Task
Automation Task
1.1
Overview
Introduction
The example blocks for STEP 7 and WinCC flexible offer the user to utilize various
automation functions or to use these blocks as templates for the configuration of
individual blocks.
The example configuration shows how the technological blocks are called and
interconnected in STEP 7 and WinCC.
The advantages when using faceplates in WinCC flexible shall be illustrated:
Central changeability
When changes are made at a block, all locations where this block is used are
automatically updated.
WCF_BLOCKS_MOTOR (FB620)
V 1.01, Entry ID: 36435784
Automation Task
On/off switch
Simulation
Off
Starting
On
Stopping
The following errors are evaluated, displayed in the screen window, and saved in
Alarm Logging:
ATTENTION
External error
Feedback On/Off
Interlock error
Dry-running protection
Before using the block in your own projects, check the proper functioning
of the block and adjust it to your individual requirements where
necessary. The block described in this application is just intended as a
template for the creating your own blocks.
WCF_BLOCKS_MOTOR (FB620)
V 1.01, Entry ID: 36435784
Automation Solution
Automation Solution
2.1
Overview
Display
The following figures show the block in the controller, the block icon, and the
faceplate window for controlling, operating and monitoring motors with fixed speed
and rotational direction.
Table 2-1
Block Icon and Faceplate
Block
WCF_BLOCKS_MOTOR (FB620)
V 1.01, Entry ID: 36435784
Automation Solution
2.2
Hardware components
Table 2-2
Component
Number
Note
Development system
S7-300 CPU
or
S7-400 CPU
Software components
Table 2-3
Component
Number
Note
6ES7810-4CC08-0YA7
6AV6613-0AA51-3CA5
S7-PLCSIM V5.4
6ES7841-0CC05-0YA5
[Optional]
10
Note
36435784_S7_WCF_Blocks_CODE.zip
36435784_S7_WCF_Blocks_DOCUMENTS_e.zip
WCF_BLOCKS_MOTOR (FB620)
V 1.01, Entry ID: 36435784
Basic Information
Basic Information
Introduction
Faceplates are objects put together from existing graphical objects.
Faceplates provide the following advantages:
Central changeability
You generate and change faceplates in the "Blocks" editor. The generated blocks
are adopted in the "Project Library" and can be added into pictures like other
objects.
Using a faceplate
After you have generated a faceplate, the faceplate appears as an object in the
project library.
You add the faceplate into your process images and configure it for its respective
usage location in the Properties window.
Faceplate instance
When adding a faceplate into a process image, an instance of this faceplate is
generated. When editing the faceplate in the project library the resulting faceplate
instance is automatically updated.
Reusing faceplates in several projects
WinCC flexible enables you to add faceplates to a global library. This way,
faceplates can also be reused in other projects.
As soon as you add a faceplate from a global library into a picture, the faceplate is
also filed in the project library. You only change the faceplate in the project library,
the changes are not automatically adopted in the global library.
WCF_BLOCKS_MOTOR (FB620)
V 1.01, Entry ID: 36435784
11
Functional Mechanisms
Functional Mechanisms
4.1
Figure 4-1
12
A dynamic property is always connected with a tag via the interface which
supplies the property in Runtime with values.
Static properties are either configured directly in the picture editor, the
properties are then stored together with the faceplate, or at the interface of the
faceplate. Static properties cannot be changed in Runtime.
WCF_BLOCKS_MOTOR (FB620)
V 1.01, Entry ID: 36435784
Functional Mechanisms
4.2
4.2.1
Animations
The tags of this group serve for display and representation of the faceplate window,
the process connection is optional.
Visibility
The Visibility property is used for influencing the display properties of the
faceplate window during runtime.
The following properties are influenced:
Open
Close
Minimize
Maximize
Table 4-5
Copyright Siemens AG 2009 All rights reserved
Tag used
Symbolic name
MotorDB.OP_VISIBILITY
Data type
Byte
Address
DB 620 DBB 98
Length
1 Byte
Reading cycle
100 ms
Acquisition mode
Bits 0..6 are used for opening or selecting the individual tabs of the faceplate
window (maximized representation). If more than one bit has been set, only the
background of the faceplate window is displayed. If Bit 7 has been set, only the title
bar of the faceplate window is displayed (minimized representation), irrespective of
the status of the remaining bits. If none of the bits has been set, the faceplate
window is closed.
The following table shows the setup of the tags.
Table 4-6
Bit
Select
Minimize
Note
Tab 3
Tab 2
Tab 1
The tag can also be defined as internal tag without PLC connection if only a
restricted number of control tags is available.
Read and write access from the controller is possible if the tag has a PLC
connection. Apart from the known picture selection the faceplate window can
also be opened from the controller and a certain tab be selected.
WCF_BLOCKS_MOTOR (FB620)
V 1.01, Entry ID: 36435784
13
Functional Mechanisms
4.2.2
Process
The variables of this group have a process connection and are the basic interface
between controller and operating unit. If you do not need messages and service
modifications these process tags are enough for rudimentary operation.
Command
The Command property is used to transmit commands from WinCC flexible to the
controller. The PLC block analyses the control command, executes the desired
action and initiates then a reset of all pending control commands. For this purpose,
the value of the control parameter is set to 0.
Table 4-7
Symbolic name
MotorDB.OPdwCmd
Data type
DWord
Address
DB 620 DBD 72
Length
4 Byte
Reading cycle
100 ms
Acquisition mode
14
START
STOP
MONFLOW OFF
MONFLOW ON
MONITOR OFF
MONITOR ON
SIMULATION
PROCESS
REMOTE
LOCAL
AUTO
MANUAL
RESET
Bit
31
30
29
28
27
26
25
24
23
22
21
20
19
18
17
16
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0
Table 4-8
Signal
Tag used
WCF_BLOCKS_MOTOR (FB620)
V 1.01, Entry ID: 36435784
Functional Mechanisms
Instance
The Instance property is a text string with a field length of 16 characters and has
two usage locations:
The tag is used as filter criterion for the message display of the faceplate
window. This ensures that only those messages referring to this faceplate
window are displayed.
The tag is displayed in the right half of the title bar to differentiate between the
individual faceplate instances.
Table 4-9
Tag used
Symbolic name
MotorDB.INSTANCE
Data type
String
Address
DB 620 DBB 24
Length
16 Byte
Reading cycle
1s
Acquisition mode
Figure 4-2
ATTENTION
The content of the tag must be adapted for each instance of a faceplate.
The content of the variables is given as start value in the declaration part
of the respective FB. Ensure that the messages in the bit alarm editor of
WinCC flexible contain not only the actual message text, but also the
same text string as well.
WCF_BLOCKS_MOTOR (FB620)
V 1.01, Entry ID: 36435784
15
Functional Mechanisms
State
The State property is used to display the different states in the WinCC flexible
faceplate.
Table 4-10
Tag used
Symbolic name
MotorDB.QdwState
Data type
DWord
Address
DB 620 DBD 44
Length
4 Byte
Reading cycle
100 ms
Acquisition mode
16
QSTOPPING
QRUN
QSTARTING
QSTOP
QMPS
Q_FLOW_ERR
Q_FLOW_MON
QMON_ERR
QMON
QSIM
QREMOTE
QMAN_AUT
LOCK
QLOCK
QERR_EXT
QERR
Signal
Bit
31
30
29
28
27
26
25
24
23
22
21
20
19
18
17
16
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0
Table 4-11
WCF_BLOCKS_MOTOR (FB620)
V 1.01, Entry ID: 36435784
Functional Mechanisms
4.2.3
Process_Service_Monitoring
The variables of this group contain a process connection and can be operated and
monitored in the Service tab.
They are used for monitoring the motor during starting or stopping.
Service_ProAV_Start
The Service_ProAV_Start property shows the already elapsed monitoring time
(actual value) during motor start.
Table 4-12
Tag used
Symbolic name
MotorDB.QMON_T
Data type
Time
Address
DB 620 DBD 52
Length
4 bytes
Reading cycle
100 ms
Acquisition mode
Service_ProAV_Stop
The Service_ProAV_Stop property shows the already elapsed monitoring time
(actual value) during motor stop.
Table 4-13
Tag used
Symbolic name
MotorDB.QMON_T_STOP
Data type
Time
Address
DB 620 DBD 56
Length
4 bytes
Reading cycle
100 ms
Acquisition mode
Service_ProLi_Start
The Service_ProLi_Start property shows the maximal monitoring time (limit value)
during motor start.
Table 4-14
Tag used
Symbolic name
MotorDB.MON_T
Data type
Time
Address
DB 620 DBD 2
Length
4 bytes
Reading cycle
1s
Acquisition mode
WCF_BLOCKS_MOTOR (FB620)
V 1.01, Entry ID: 36435784
17
Functional Mechanisms
Service_ProLi_Stop
The Service_ProLi_Stop property shows the maximal monitoring time (limit value)
during motor stop.
Table 4-15
Tag used
4.2.4
Symbolic name
MotorDB.MON_T_STOP
Data type
Time
Address
DB 620 DBD 6
Length
4 bytes
Reading cycle
1s
Acquisition mode
Process_Service_FlowMonitoring
The variables of this group contain a process connection and can be operated and
monitored in the Service tab.
MotorDB.FLOW
Data type
Real
Address
DB 620 DBD 12
Length
4 bytes
Reading cycle
100 ms
Acquisition mode
Service_FlowAV_Start
The Service_FlowAV_Start property shows the already elapsed monitoring time
(actual value) until the activation of an error detection.
Table 4-17
Tag used
Symbolic name
18
MotorDB.QFLOW_MT
Data type
Time
Address
DB 620 DBD 62
Length
4 bytes
Reading cycle
100 ms
Acquisition mode
WCF_BLOCKS_MOTOR (FB620)
V 1.01, Entry ID: 36435784
Functional Mechanisms
Service_FlowLi_Flow
The Service_FlowLi_Flow property shows minimal flow (limit value) the falling
short of which triggers an error.
Table 4-18
Tag used
Symbolic name
MotorDB.FLOW_LL
Data type
Real
Address
DB 620 DBD 16
Length
4 bytes
Reading cycle
1s
Acquisition mode
Service_FlowLi_Start
The Service_FlowLi_Start property shows the delay time (limit value) until the
activation of an error detection.
Table 4-19
Copyright Siemens AG 2009 All rights reserved
Tag used
Symbolic name
MotorDB.FLOW_MT
Data type
Time
Address
DB 620 DBD 20
Length
4 bytes
Reading cycle
1s
Acquisition mode
WCF_BLOCKS_MOTOR (FB620)
V 1.01, Entry ID: 36435784
19
Functional Mechanisms
4.2.5
Process_Service_Simulation
The variables of this group contain a process connection and can be operated and
monitored in the Service tab.
They are used in the simulation mode for monitoring the motor during starting or
stopping.
Service_SimAV_Start
The Service_SimAV_Start property shows the already elapsed monitoring time
(actual value) during motor start.
Table 4-20
Tag used
Symbolic name
MotorDB.QSIM_T
Data type
Time
Address
DB 620 DBD 82
Length
4 bytes
Reading cycle
100 ms
Acquisition mode
Service_SimAV_Stop
The Service_SimAV_Stop property shows the already elapsed monitoring time
(actual value) during motor stop.
Table 4-21
Tag used
Symbolic name
MotorDB.QSIM_T_STOP
Data type
Time
Address
DB 620 DBD 90
Length
4 bytes
Reading cycle
100 ms
Acquisition mode
Service_SimSP_Start
The Service_SimSP_Start property shows the maximal monitoring time (limit
value) during motor start.
Table 4-22
Tag used
20
Symbolic name
MotorDB.SIM_T
Data type
Time
Address
DB 620 DBD 78
Length
4 bytes
Reading cycle
1s
Acquisition mode
WCF_BLOCKS_MOTOR (FB620)
V 1.01, Entry ID: 36435784
Functional Mechanisms
Service_SimSP_Stop
The Service_SimSP_Stop property shows the maximal monitoring time (limit
value) during motor stop.
Table 4-23
Tag used
4.3
Symbolic name
MotorDB.SIM_T_STOP
Data type
Time
Address
DB 620 DBD 86
Length
4 bytes
Reading cycle
1s
Acquisition mode
4.3.1
Label
The properties of this group serve for labeling the faceplate windows.
Text
The Text property is a text string and is displayed in the left half of the title bar.
Here, for example, the higher level definition (HLD) or the location of usage can be
shown.
Figure 4-3
4.3.2
UserManagement
The properties of this group serve for assigning the user rights.
Service
The Service property is an HMI object and is used as access protection for the
Service tab.
ATTENTION
In this application the authorization used is the Group Service and the
User Service. The password is preset to 100 and can be changed in
the User Administration of WinCC flexible.
If you create a new instance of the faceplate window and do not
interconnect the Service property, the Service tab has no access
protection.
WCF_BLOCKS_MOTOR (FB620)
V 1.01, Entry ID: 36435784
21
Functional Mechanisms
4.4
Figure 4-4
In the interface of the block icon only the dynamic properties are accessed.
4.4.1
Process
The variables of this group have a process connection and are the basic interface
between controller and operating unit.
State
The State property is used to display the different states in the WinCC flexible
faceplate.
Table 4-24
Tag used
Symbolic name
MotorDB.QdwState
Data type
DWord
Address
DB 620 DBD 44
Length
4 bytes
Reading cycle
100 ms
Acquisition mode
22
QSTOPPING
QRUN
QSTARTING
QSTOP
QMPS
Q_FLOW_ERR
Q_FLOW_MON
QMON_ERR
QMON
QSIM
QREMOTE
QMAN_AUT
LOCK
QLOCK
QERR_EXT
QERR
Bit
31
30
29
28
27
26
25
24
23
22
21
20
19
18
17
16
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0
Table 4-25
Signal
A dynamic property is always connected with a tag via the interface which supplies
the property in Runtime with values.
WCF_BLOCKS_MOTOR (FB620)
V 1.01, Entry ID: 36435784
Functional Mechanisms
Visibility
The Visibility property is used for influencing the display properties of the
faceplate window during runtime.
The following properties are influenced:
Note
Open
Close
Minimize
Maximize
The block icon always downloads the value 1 upon clicking the
OP_VISIBILITY tag. The result of this is that the respective faceplate window is
shown with Tab 1.
Table 4-26
Tag used
Symbolic name
MotorDB.OP_VISIBILITY
Data type
Byte
Address
DB 620 DBB 98
Length
1 Byte
Reading cycle
100 ms
Acquisition mode
Select
Minimize
Note
Tab 3
Tab 2
Tab 1
The tag can also be defined as internal tag without PLC connection if only a
restricted number of control tags is available.
Read and write access from the controller is possible if the tag has a PLC
connection. Apart from the known picture selection the faceplate window can
also be opened from the controller and a certain tab be selected.
WCF_BLOCKS_MOTOR (FB620)
V 1.01, Entry ID: 36435784
23
Functional Mechanisms
4.5
4.5.1
Message tag
Table 4-28
Tag used
Symbolic name
MotorDB.QwAlarm
Data type
Word
Address
DB 620 DBW 68
Length
2 bytes
Reading cycle
100 ms
Acquisition mode
Cyclically continued
The following table shows the setup of the tags. The message texts were preceded
by the filter attribute Motor_001 for the first instance of the motor faceplate
window.
Table 4-29
Bit
Signal
QMON_ERR
QFLOW_ERR
QMPS
3
4
Motor_001:
QLOCK
24
Message text
QERR_EXT
QERR
QSTOP
QSTARTING
10
QRUN
11
QSTOPPING
12
LOCK
13
QREMOTE
14
QMAN_AUT
15
QSIM
WCF_BLOCKS_MOTOR (FB620)
V 1.01, Entry ID: 36435784
Functional Mechanisms
4.6
4.6.1
QdwState
QwState
QSTOPPING
LIOP_SEL
L_AUT
QSTOP
QSTARTING
L_REMOTE
Copyright Siemens AG 2009 All rights reserved
L_SIM
QRUN
QCMD_ON
L_RESET
AUT_ON
MAN_ON
SIM_ON
FB_ON
QMON
QMON_ERR
QMON_T
QMON_T_STOP
QFLOW_MON
L_MON
QFLOW_MT
MON_T
QFLOW_ERR
MON_T_STOP
QMPS
MPS
L_FLOW_MON
FLOW
QERR
QMAN_AUT
QREMOTE
FLOW_LL
QSIM
FLOW_MT
QLOCK
INSTANCE
QERR_EXT
VISIBILITY
QwAlarm
RESTART
ENO
OPdwCmd
WCF_BLOCKS_MOTOR (FB620)
V 1.01, Entry ID: 36435784
START
STOP
MONFLOW OFF
MONFLOW ON
MONITOR OFF
MONITOR ON
SIMULATION
PROCESS
REMOTE
LOCAL
AUTO
MANUAL
RESET
Signal
Bit
31
30
29
28
27
26
25
24
23
22
21
20
19
18
17
16
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0
Table 4-30
25
Functional Mechanisms
4.6.2
QdwState
LOCK
ERR_EXTERN
QwState
QSTOPPING
LIOP_SEL
QSTOP
L_AUT
QSTARTING
L_REMOTE
L_SIM
QRUN
QCMD_ON
L_RESET
QMON
AUT_ON
QMON_ERR
MAN_ON
QMON_T
SIM_ON
QMON_T_STOP
FB_ON
QFLOW_MON
L_MON
QFLOW_MT
MON_T
QFLOW_ERR
MON_T_STOP
QMPS
MPS
QERR
L_FLOW_MON
FLOW
QMAN_AUT
QREMOTE
FLOW_LL
QSIM
FLOW_MT
QLOCK
INSTANCE
QERR_EXT
VISIBILITY
QwAlarm
RESTART
ENO
OPdwCmd
26
QSTOPPING
QRUN
QSTARTING
QSTOP
QMPS
Q_FLOW_ERR
Q_FLOW_MON
QMON_ERR
QMON
QSIM
QREMOTE
QMAN_AUT
LOCK
QLOCK
QERR_EXT
QERR
Signal
Bit
31
30
29
28
27
26
25
24
23
22
21
20
19
18
17
16
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0
Table 4-31
WCF_BLOCKS_MOTOR (FB620)
V 1.01, Entry ID: 36435784
Functional Mechanisms
4.6.3
FB_ON
QdwState
QwState
QSTOPPING
QSTOP
QSTARTING
QRUN
QCMD_ON
QMON
QMON_ERR
QMON_T
QMON_T_STOP
QFLOW_MON
L_MON
QFLOW_MT
MON_T
QFLOW_ERR
MON_T_STOP
MPS
L_FLOW_MON
FLOW
FLOW_LL
QMPS
QERR
QMAN_AUT
QREMOTE
QSIM
FLOW_MT
QLOCK
INSTANCE
QERR_EXT
VISIBILITY
QwAlarm
RESTART
ENO
OPdwCmd
LIOP_SEL
If the LIOP_SEL input is set, the mode is determined via the control input
L_AUT.
If the LIOP_SEL input is not set, the mode is determined by the operator
(OP_dwCmd [Bit 16 and 17]).
L_AUT
Input L_AUT is only effective if the input LIOP_SEL has been set.
LIOP_SEL = 1 AND L_AUT = 0 Manual
LIOP_SEL = 1 AND L_AUT = 1 Automatic
OPdwCmd
The operator commands of the control word OPdwCmd are only active if the
LIOP_SEL input has not been set.
LIOP_SEL = 0 AND OPdwCmd [Bit 16] = 1 Manual
LIOP_SEL = 0 AND OPdwCmd [Bit 17] = 1 Automatic
WCF_BLOCKS_MOTOR (FB620)
V 1.01, Entry ID: 36435784
27
Functional Mechanisms
QMAN_AUT
The mode is displayed at block output QMAN_AUT.
QMAN_AUT
= 0 Manual
QMAN_AUT
= 1 Automatic
QdwState
The current operating mode is transferred to WinCC flexible in status word
QdwState by means of the two separate bits 16 and 17. If neither or both bits
are set, an error has occurred.
QdwState [Bit 16] = 1 Manual
QdwState [Bit 17] = 1 Automatic
4.6.4
Figure 4-8
Motor (FB 620)
EN
LOCK
ERR_EXTERN
LIOP_SEL
L_AUT
L_REMOTE
L_SIM
L_RESET
AUT_ON
MAN_ON
SIM_ON
FB_ON
QdwState
QwState
QSTOPPING
QSTOP
QSTARTING
QRUN
QCMD_ON
QMON
QMON_ERR
QMON_T
QMON_T_STOP
QFLOW_MON
L_MON
QFLOW_MT
MON_T
QFLOW_ERR
MON_T_STOP
MPS
L_FLOW_MON
FLOW
QMPS
QERR
QMAN_AUT
QREMOTE
FLOW_LL
FLOW_MT
QSIM
QLOCK
INSTANCE
QERR_EXT
VISIBILITY
QwAlarm
RESTART
ENO
OPdwCmd
28
WCF_BLOCKS_MOTOR (FB620)
V 1.01, Entry ID: 36435784
Functional Mechanisms
LIOP_SEL
If input LIOP_SEL has been set, the mode is defined by the control input
L_REMOTE.
If the LIOP_SEL input is not set, the mode is determined by the operator
(OPdwCmd [Bit 18 and 19]).
L_REMOTE
Input L_REMOTE is only effective if the input LIOP_SEL has been set.
LIOP_SEL = 1 AND L_REMOTE = 0 Local
LIOP_SEL = 1 AND L_REMOTE = 1 Remote
OP_dwCmd
The operator commands of the control word OP_dwCmd are only effective if
the LIOP_SEL input has not been set.
LIOP_SEL = 0 AND OPdwCmd [Bit 18] = 1 Local
LIOP_SEL = 0 AND OPdwCmd [Bit 19] = 1 Remote
QREMOTE
The operating mode is displayed at block output QREMOTE.
QREMOTE = 0 Local
QREMOTE = 1 Remote
WCF_BLOCKS_MOTOR (FB620)
V 1.01, Entry ID: 36435784
29
Functional Mechanisms
4.6.5
QdwState
LOCK
ERR_EXTERN
QwState
QSTOPPING
LIOP_SEL
L_AUT
QSTOP
QSTARTING
L_REMOTE
L_SIM
QRUN
QCMD_ON
L_RESET
AUT_ON
QMON
QMON_ERR
MAN_ON
SIM_ON
QMON_T
QMON_T_STOP
FB_ON
L_MON
QFLOW_MON
QFLOW_MT
MON_T
QFLOW_ERR
MON_T_STOP
QMPS
MPS
L_FLOW_MON
FLOW
QERR
QMAN_AUT
QREMOTE
FLOW_LL
QSIM
FLOW_MT
INSTANCE
QLOCK
QERR_EXT
VISIBILITY
QwAlarm
RESTART
ENO
OPdwCmd
AUT_ON
Input AUT_ON starts or stops the motor in automatic mode.
AUT_ON = 1 AND QMAN_AUT = 1 Starting
AUT_ON = 0 AND QMAN_AUT = 1 Stopping
MAN_ON
Input MAN_ON starts or stops the motor in manual mode.
MAN_ON = 1 AND QMAN_AUT = 0 Starting
MAN_ON = 0 AND QMAN_AUT = 0 Stopping
SIM_ON
Input SIM_ON starts or stops the motor in simulation mode.
SIM_ON = 1 AND QSIM = 1 Starting
SIM_ON = 0 AND QSIM = 1 Stopping
30
WCF_BLOCKS_MOTOR (FB620)
V 1.01, Entry ID: 36435784
Functional Mechanisms
OPdwCmd
Bits 0 and 1 in the control word OPdwCmd are used for WinCC Runtime
operation.
LIOP_SEL = 0 AND OPdwCmd [Bit 0] = 1 Stop
LIOP_SEL = 0 AND OPdwCmd [Bit 1] = 1 Start
QwState(INT)
The current operating mode is displayed at the QwState output with a
numerical value.
QwState = 0 Off or error
QwState = 1 Starting
QwState = 2 On
QwState = 3 Stopping
This signal is used internally for calculating the status transitions.
= 1 Off
(QwState = 0)
= 1 On
(QwState = 2)
QdwState
The current operating state Stop/Starting/Run/Stopping is displayed in the
status double word by means of bits 0 to 3.
QdwState Bit 0 = 1 Off
QdwState Bit 1 = 1 Starting
QdwState Bit 2 = 1 On
QdwState Bit 3 = 1 Stopping
WCF_BLOCKS_MOTOR (FB620)
V 1.01, Entry ID: 36435784
31
Functional Mechanisms
The table below illustrates the possible operating modes in WinCC flexible:
Table 4-32
QwState
Small icon
Large icon
Flashing
Off
No
Starting
Yes
On
No
Stopping
Yes
Error
Yes
Operating
mode
32
WCF_BLOCKS_MOTOR (FB620)
V 1.01, Entry ID: 36435784
Functional Mechanisms
4.6.6
QdwState
QwState
ERR_EXTERN
LIOP_SEL
L_AUT
L_REMOTE
L_SIM
QSTOP
QSTARTING
QRUN
QCMD_ON
L_RESET
AUT_ON
MAN_ON
SIM_ON
FB_ON
Copyright Siemens AG 2009 All rights reserved
QSTOPPING
QMON
QMON_ERR
QMON_T
QMON_T_STOP
QFLOW_MON
L_MON
QFLOW_MT
MON_T
QFLOW_ERR
MON_T_STOP
MPS
QMPS
QERR
L_FLOW_MON
FLOW
FLOW_LL
QMAN_AUT
QREMOTE
QSIM
FLOW_MT
QLOCK
INSTANCE
QERR_EXT
VISIBILITY
QwAlarm
RESTART
ENO
OPdwCmd
MPS
=1
QMPS = 1
QMPS = 1
QERR = 1
MPS
WCF_BLOCKS_MOTOR (FB620)
V 1.01, Entry ID: 36435784
33
Functional Mechanisms
4.6.7
Simulation On/Off
The respective signal can be simulated by means of the Simulation ON mode.
This is an important function, e. g. to test automatic functions already during the
configuration phase when a connection to the process is not yet available. Without
feedback simulation, many automation functions (e.g. step sequences) cannot be
successfully performed, since the feedback signals are often required for switching
conditions or for triggering error messages.
Output QCMD_ON, which starts the motor, is deactivated in simulation mode.
Figure 4-11
Motor (FB 620)
EN
LOCK
ERR_EXTERN
LIOP_SEL
L_AUT
L_REMOTE
L_SIM
L_RESET
AUT_ON
MAN_ON
SIM_ON
FB_ON
QdwState
QwState
QSTOPPING
QSTOP
QSTARTING
QRUN
QCMD_ON
QMON
QMON_ERR
QMON_T
QMON_T_STOP
QFLOW_MON
L_MON
QFLOW_MT
MON_T
QFLOW_ERR
MON_T_STOP
MPS
L_FLOW_MON
FLOW
FLOW_LL
QMPS
QERR
QMAN_AUT
QREMOTE
QSIM
FLOW_MT
INSTANCE
QLOCK
QERR_EXT
VISIBILITY
QwAlarm
RESTART
ENO
OPdwCmd
LIOP_SEL
If input LIOP_SEL is enabled, simulation will be switched on or off by control
input SIM_L.
If the LIOP_SEL input is not set, the simulation is switched on/off by the
operator (OP_dwCmd [Bit 20 and 21]).
L_SIM
LIOP_SEL = 1 AND L_SIM = 0 Simulation OFF
LIOP_SEL = 1 AND L_SIM = 1 Simulation ON
34
WCF_BLOCKS_MOTOR (FB620)
V 1.01, Entry ID: 36435784
Functional Mechanisms
OPdwCmd
The operator commands of the control word OPdwCmd are only effective if
the LIOP_SEL input has not been set.
LIOP_SEL = 0 AND OPdwCmd [Bit 20] = 1 Simulation OFF
LIOP_SEL = 0 AND OPdwCmd [Bit 21] = 1 Simulation ON
QSIM
The Simulation mode is displayed at the block output QSIM.
QSIM = 0 Simulation OFF
QSIM = 1 Simulation ON
QdwState
The currently active operating mode Simulation is indicated in the status word
by bit 18.
QdwState [Bit 18] = 0 Simulation OFF
WCF_BLOCKS_MOTOR (FB620)
V 1.01, Entry ID: 36435784
35
Functional Mechanisms
4.6.8
QwState
ERR_EXTERN
LIOP_SEL
QSTOPPING
QSTOP
L_AUT
QSTARTING
L_REMOTE
L_SIM
QdwState
QRUN
QCMD_ON
L_RESET
QMON
AUT_ON
MAN_ON
QMON_ERR
QMON_T
SIM_ON
FB_ON
QMON_T_STOP
QFLOW_MON
L_MON
QFLOW_MT
MON_T
QFLOW_ERR
MON_T_STOP
MPS
L_FLOW_MON
FLOW
FLOW_LL
QMPS
QERR
QMAN_AUT
QREMOTE
QSIM
FLOW_MT
QLOCK
INSTANCE
VISIBILITY
QERR_EXT
QwAlarm
RESTART
ENO
OPdwCmd
LOCK
The input signal LOCK includes the interlock condition. If the interlock is
pending, the specific block function (Motor ON) cannot be performed.
LOCK = 0 Interlock not pending
LOCK = 1 Interlock pending
L_RESET
When a positive edge is present at the input L_RESET the output QLOCK
will be reset.
36
WCF_BLOCKS_MOTOR (FB620)
V 1.01, Entry ID: 36435784
Functional Mechanisms
OP_dwCmd
Clicking the RESET button in the faceplate of the block type enables Bit 24 in
the control word OP_dwCmd. The control system evaluates this bit and
resets the QLOCK output.
QLOCK
The output signal QLOCK is set if the LOCK input is active and the block
has status QSTARTING or QRUN.
QLOCK = 1 Error interlock active
QLOCK = 0 Error interlock not active
QdwState
The states Interlock condition active (LOCK=1) and Interlock error
(QLOCK=1) are indicated in the status word by bits 26 and 27.
QdwState [Bit 27] = 1 LOCK = 1 (interlock condition active)
WCF_BLOCKS_MOTOR (FB620)
V 1.01, Entry ID: 36435784
37
how the faceplates of the application are structured. This information is necessary
if you wish to design the faceplate according to your requirements.
Principle of level technology
For the faceplates of this application the principle of level technology was used.
Level technology enables differentiated editing of the faceplate objects.
The faceplate editor as well as the picture editor have 32 levels, however, the
levels of the faceplate are only available within the faceplate editor. After adding a
faceplate from the library into the picture editor (creating a faceplate instance) it, as
well as any other picture object, can only be assigned a level within the picture
editor.
However, the offset in depth within the faceplate remains.
38
WCF_BLOCKS_MOTOR (FB620)
V 1.01, Entry ID: 36435784
Figure 5-13
When opening a picture or a faceplate, all 32 levels are always displayed. In the
icon bar "Levels" you can hide all levels except the active level. Then you edit the
objects of the active level directly.
WCF_BLOCKS_MOTOR (FB620)
V 1.01, Entry ID: 36435784
39
5.1
5.1.1
Level 0 - Frame
Level 0 contains all important objects required for displaying the faceplate
window. This objects represents the frame of the faceplate window.
Figure 5-14
40
Open
Close
Minimize
Maximize
WCF_BLOCKS_MOTOR (FB620)
V 1.01, Entry ID: 36435784
State
Visibility
Range
Visible
From 1 to 127
The following table shows the status of the Visibility tag when Opening the
faceplate window.
Table 5-34
Bit
Value
Note
The block icon always downloads the value 1 upon clicking the Visibility tag.
The result of this is that the respective faceplate window is shown with Tab 1.
The following table shows the status of the Visibility tag when Maximizing the
faceplate window. Depending on which tab was selected before Minimizing, one
of the Bits 0..2 is set Bit 7 must not have been set here.
Table 5-35
Bit
Value
WCF_BLOCKS_MOTOR (FB620)
V 1.01, Entry ID: 36435784
41
Minimize
The representation type Minimize only shows the title bar of the faceplate window
and enables viewing the faceplates behind.
Figure 5-15
All objects of the title bar have the following visibility settings:
Table 5-36
Tag
State
Visibility
Range
Hidden
From 0 to 0
The following table shows the status of the Visibility tag when Minimizing the
faceplate window. As soon as Bit 7 has been set, only the title bar of the faceplate
window is displayed irrespective of the remaining status.
Table 5-37
Bit
Value
Close
The representation type Close hides all objects of the screen window.
The following table shows the status of the Visibility tag when Closing the
faceplate window.
Table 5-38
42
Bit
Value
WCF_BLOCKS_MOTOR (FB620)
V 1.01, Entry ID: 36435784
5.1.2
Level 1 Tab 1
The following picture shows Level 0 and Level 1.
Figure 5-16
State
Visibility
Range
Visible
From 1 to 1
The following table shows the status of the Visibility tag for the display of Level 1
(Tab 1) of the faceplate window.
Table 5-40
Bit
Value
WCF_BLOCKS_MOTOR (FB620)
V 1.01, Entry ID: 36435784
43
5.1.3
Level 2 Tab 2
All objects of Level 2 have the following visibility settings:
Table 5-41
Tag
State
Visibility
Range
Visible
From 2 to 2
The following table shows the status of the Visibility tag for the display of Level 2
(Tab 2) of the faceplate window.
Table 5-42
Bit
Value
5.1.4
Level 3 Tab 3
State
Visibility
Range
Visible
From 4 to 4
The following table shows the status of the Visibility tag for the display of Level 3
(Tab 3) of the faceplate window.
Table 5-44
44
Bit
Value
WCF_BLOCKS_MOTOR (FB620)
V 1.01, Entry ID: 36435784
Note
The application provides a runnable project. You only need to perform the steps
explained in this chapter if you wish to integrated the blocks into your own
project.
If you only wish to gain an overview of the functionality of this application, it is
sufficient to open the file 36435784_S7_WCF_Blocks_CODE.zip in the
SIMATIC Manager via the command File > Retrieve.
Save the blocks into an S7 controller of your choice and start the HMI station
(WinCC flexible RT) integrated in the project on a connected PC.
ATTENTION
The process connection was configured for Industrial Ethernet. Adjust the
settings of CPU, HMI Station, and PG/PC Interface if necessary.
WCF_BLOCKS_MOTOR (FB620)
V 1.01, Entry ID: 36435784
45
6.1
Step
46
Description
1.
2.
Insert blocks
The block uses the standard block TON (SFB 4), which also needs to
be added to the project.
Should you use a new project then also add the calling block OB1 and
the instance data block DB620 to your project.
3.
For an empty project you copy the icon table of the application into the
respective directory of the S7 program.
Should you use an existing project, the complete the existing icon table
with the entries of the application.
4.
When using an existing project, you must integrate the FB620 block into
the PLC cycle. The required instance data block is generated
automatically.
5.
WCF_BLOCKS_MOTOR (FB620)
V 1.01, Entry ID: 36435784
6.2
Table 6-46
Step
Procedure
1.
Open the WinCC flexible project via the context menu of the SIMATIC Manager.
2.
Select library
3.
Via the context menu Library > New library you select the dialog for creating a
global library.
WCF_BLOCKS_MOTOR (FB620)
V 1.01, Entry ID: 36435784
47
Step
4.
Procedure
Create a global library
Note
A global library can be accessed from several configuration computers. It therefore makes
sense to store the library on a network drive with joint access.
5.
48
WCF_BLOCKS_MOTOR (FB620)
V 1.01, Entry ID: 36435784
Step
Procedure
6.
7.
Draw the faceplate objects contained there into your project via Drag&Drop.
WCF_BLOCKS_MOTOR (FB620)
V 1.01, Entry ID: 36435784
49
Step
8.
Procedure
Integrating the messages and tags
Draw the messages MotorAlarms into the folder Alarm Management > Discrete
Messages and the tag MotorTags into the folder Communication > Tags.
Attention:
The message numbers of this application assign the number space as of 10001.
Prior to integrating the messages you check your existing project and enable this area, if
assigned.
Furthermore, check the symbolic connection of the tags and restore it, if necessary.
9.
50
Interconnect the dynamic properties of the faceplate window. For further information,
please refer to Chapter 4.2.
Interconnect the static properties of the faceplate window. For further information, please
refer to Chapter 4.3.
Interconnect the dynamic properties of the faceplate icon. For further information, please
refer to Chapter 4.4.
WCF_BLOCKS_MOTOR (FB620)
V 1.01, Entry ID: 36435784
7.1
Faceplate icon
Figure 7-17
State Off/Starting/On/Stopping
Simulation feedback
Interlock
Displayed error:
General error
Operation:
WCF_BLOCKS_MOTOR (FB620)
V 1.01, Entry ID: 36435784
51
QdwState
Icon
Flashing
Off
Bit 0 = 1
No
Starting
Bit 1 = 1
Yes
On
Bit 2 = 1
No
Stopping
Bit 3 = 1
Yes
Fault
Bit 24 = 1
Yes
State
Icon
Local
Remote
Manual
Automatic
Simulation ON
Simulation OFF
Interlock OFF
Interlock ON
Interlock triggered
52
WCF_BLOCKS_MOTOR (FB620)
V 1.01, Entry ID: 36435784
7.2
Faceplate window
The faceplate window has the following properties:
Overview
Figure 7-18
WCF_BLOCKS_MOTOR (FB620)
V 1.01, Entry ID: 36435784
53
Table 7-49
Operating
mode
QdwState
Icon
Flashing
Off
Bit 0 = 1
No
Starting
Bit 1 = 1
Yes
On
Bit 2 = 1
No
Stopping
Bit 3 = 1
Yes
Fault
Bit 24 = 1
Yes
54
Icon
Off
Icon
On
Flashing
Interlock
Yes
Monitoring
No
Simulation
Yes
Flow monitoring
No
Status
No
Operating mode
No
Control
No
External Error
No
Feedback Monitor
No
No
Motor Protecting
Switch
No
Interlock
No
WCF_BLOCKS_MOTOR (FB620)
V 1.01, Entry ID: 36435784
Messages
Figure 7-19
Acknowledgement of alarms.
WCF_BLOCKS_MOTOR (FB620)
V 1.01, Entry ID: 36435784
55
Service
Figure 7-20
ATTENTION
56
Maximal start and stop time can be defined independent of each other
Delay time for activating the flow monitoring given in TIME format
Switchover between simulation / real process mode. (The condition for this is
remote operation)
Maximal start and stop time can be defined independent of each other
WCF_BLOCKS_MOTOR (FB620)
V 1.01, Entry ID: 36435784
Icon OFF
Icon ON
Monitoring
Dry-running monitoring
Simulation
WCF_BLOCKS_MOTOR (FB620)
V 1.01, Entry ID: 36435784
57
Block Connectors
Block Connectors
8.1
Input parameters
Table 8-52
Parameter
Data type
Default setting
Description
EN
BOOL
FALSE
Release
LOCK
BOOL
FALSE
1 = Interlock pending
ERR_EXTERN
BOOL
FALSE
1 = External Error
LIOP_SEL
BOOL
FALSE
0= Operator, 1=Interconnection
L_AUT
BOOL
FALSE
0 = Manual, 1 = Automatic
L_REMOTE
BOOL
FALSE
0= Local, 1= Remote
L_SIM
BOOL
FALSE
0 = Process 1 = Simulation
L_RESET
BOOL
FALSE
AUT_ON
BOOL
FALSE
0 = Stop, 1 = Start
(Automatic mode, pos. edge)
MAN_ON
BOOL
FALSE
0 = Stop, 1 = Start
(manual mode, pos. edge)
SIM_ON
BOOL
FALSE
0 = Stop, 1 = Start
(Simulation mode)
FB_ON1)
BOOL
FALSE
1= Feedback motor ON
L_MON
BOOL
TRUE
MON_T
TIME
T#5S
MON_T_STOP
TIME
T#5S
MPS
BOOL
FALSE
L_FLOW_MON
BOOL
FALSE
FLOW
REAL
0.0
Current flow
FLOW_LL
REAL
5,0
FLOW_MT
TIME
T#8S
INSTANCE
STRING[16]
Motor_001
RESTART
BOOL
FALSE
VISIBILITY
BYTE
B#16#0
Representation of the
faceplate window
OPdwCmd
DWORD
DW#16#0
58
WCF_BLOCKS_MOTOR (FB620)
V 1.01, Entry ID: 36435784
Block Connectors
8.2
Output parameters
Table 8-53
Parameter
Data type
Default setting
Description
QdwState
DWORD
DW#16#0
QwState
INT
QSTOPPING
BOOL
FALSE
1= Motor stopping
QSTOP
BOOL
FALSE
1= Motor is off
QSTARTING
BOOL
FALSE
1= Motor starting
QRUN
BOOL
FALSE
1= Motor is on
QCMD_ON
BOOL
FALSE
1= Stop motor,
1= Start motor
QMON
BOOL
FALSE
1= Feedback monitoring
active
QMON_ERR
BOOL
FALSE
1= Feedback error
QMON_T
TIME
T#0MS
QMON_T_STOP
TIME
T#0MS
QFLOW_MON
BOOL
FALSE
QFLOW_MT
TIME
T#0MS
QFLOW_ERR
BOOL
FALSE
1 = Error
Dry-running monitoring
QMPS
BOOL
FALSE
QERR
BOOL
FALSE
1= Error
QMAN_AUT
BOOL
FALSE
0 = Manual, 1 = Automatic
QREMOTE
BOOL
FALSE
0= Local, 1= Remote
QSIM
BOOL
FALSE
0 = Process 1 = Simulation
QLOCK
BOOL
FALSE
1 = Interlock error
QERR_EXT
BOOL
FALSE
1= External error
QwAlarm
WORD
W#16#0
Alarm tag
ENO
BOOL
FALSE
Enable
WCF_BLOCKS_MOTOR (FB620)
V 1.01, Entry ID: 36435784
59
Further Notes
Further Notes
Further blocks for this application
Table 9-54
Block
Description
MOTOR
Visualization and operator control of a motor with fixed speed and rotational
direction
VALVE
DIGITAL
ANALOG
PIDCTRL
MM440
SIMODIR
SIMOREV
SINAG120
60
WCF_BLOCKS_MOTOR (FB620)
V 1.01, Entry ID: 36435784
Bibliography
10
Bibliography
This list is not intended to be exhaustive and only represents a selection of the
relevant literature.
Table 10-55
Subject
Title
http://support.automation.siemens.com/WW/view/en/36435784
\2\
http://support.automation.siemens.com
\3\
http://support.automation.siemens.com/WW/view/en/18656980
\4\
Creating faceplates
http://support.automation.siemens.com/WW/view/en/23425423
\1\
WCF_BLOCKS_MOTOR (FB620)
V 1.01, Entry ID: 36435784
61
History
11
History
Table 11-56 History
Version
Date
Modifications
20.08.2009
First issue
V1.01
18.09.2009
V1.0
62
WCF_BLOCKS_MOTOR (FB620)
V 1.01, Entry ID: 36435784