Professional Documents
Culture Documents
Manual 3RW44 PCS7 Library v7 v9 Migv80sp4 en-US
Manual 3RW44 PCS7 Library v7 v9 Migv80sp4 en-US
0 1
Introduction
SP4
Information about the library 2
Technical data 7
List of abbreviations A
06/2019
A5E02845977020A/RS-AD/006
Legal information
Warning notice system
This manual contains notices you have to observe in order to ensure your personal safety, as well as to prevent
damage to property. The notices referring to your personal safety are highlighted in the manual by a safety alert
symbol, notices referring only to property damage have no safety alert symbol. These notices shown below are
graded according to the degree of danger.
DANGER
indicates that death or severe personal injury will result if proper precautions are not taken.
WARNING
indicates that death or severe personal injury may result if proper precautions are not taken.
CAUTION
indicates that minor personal injury can result if proper precautions are not taken.
NOTICE
indicates that property damage can result if proper precautions are not taken.
If more than one degree of danger is present, the warning notice representing the highest degree of danger will
be used. A notice warning of injury to persons with a safety alert symbol may also include a warning relating to
property damage.
Qualified Personnel
The product/system described in this documentation may be operated only by personnel qualified for the specific
task in accordance with the relevant documentation, in particular its warning notices and safety instructions.
Qualified personnel are those who, based on their training and experience, are capable of identifying risks and
avoiding potential hazards when working with these products/systems.
Proper use of Siemens products
Note the following:
WARNING
Siemens products may only be used for the applications described in the catalog and in the relevant technical
documentation. If products and components from other manufacturers are used, these must be recommended
or approved by Siemens. Proper transport, storage, installation, assembly, commissioning, operation and
maintenance are required to ensure that the products operate safely and without any problems. The permissible
ambient conditions must be complied with. The information in the relevant documentation must be observed.
Trademarks
All names identified by ® are registered trademarks of Siemens AG. The remaining trademarks in this publication
may be trademarks whose use by third parties for their own purposes could violate the rights of the owner.
Disclaimer of Liability
We have reviewed the contents of this publication to ensure consistency with the hardware and software
described. Since variance cannot be precluded entirely, we cannot guarantee full consistency. However, the
information in this publication is reviewed regularly and any necessary corrections are included in subsequent
editions.
1 Introduction ................................................................................................................................................ 7
1.1 Security information ..................................................................................................................7
1.2 Product specific security information ........................................................................................7
1.3 General .....................................................................................................................................8
1.4 Installing the library ...................................................................................................................8
1.5 Configuration steps ...................................................................................................................9
1.6 Handling the driver generator .................................................................................................10
1.7 Configuring in HW Config .......................................................................................................11
1.8 Parameterization softwares ....................................................................................................13
1.9 Further documentation ............................................................................................................13
2 Information about the library .................................................................................................................... 15
2.1 What's new?............................................................................................................................15
2.2 Faceplates ..............................................................................................................................15
2.2.1 Faceplates ..............................................................................................................................15
2.2.2 General Information ................................................................................................................16
2.3 Block icons ..............................................................................................................................21
3 Soft starter blocks .................................................................................................................................... 25
3.1 Overview of the blocks ............................................................................................................25
3.2 Error numbers .........................................................................................................................26
3.3 Quality codes ..........................................................................................................................27
3.4 SS_DIAG: Diagnostic block ....................................................................................................28
3.4.1 Description ..............................................................................................................................28
3.4.2 Calling OBs .............................................................................................................................29
3.4.3 Called blocks...........................................................................................................................29
3.4.4 Parameterization .....................................................................................................................30
3.4.5 Diagnostic functions ................................................................................................................30
3.4.5.1 Diagnostics of acyclic events ..................................................................................................31
3.4.5.2 Slave diagnostics of the 3RW44 .............................................................................................33
3.4.5.3 Diagnostics of upstream block ................................................................................................38
3.4.6 Message features ...................................................................................................................39
3.4.7 Start-up characteristics ...........................................................................................................41
3.4.8 Interconnection of function blocks ..........................................................................................42
3.4.9 Block parameters ....................................................................................................................43
3.5 SS_DIR: Signal block for direct starter control function ..........................................................45
3.5.1 Description ..............................................................................................................................45
3.5.2 Calling OBs .............................................................................................................................46
3.5.3 Called blocks...........................................................................................................................46
1.3 General
Procedure
1. Configuring with HW Config
2. Make the necessary interconnections for the inputs and outputs in the CFC Editor In so
doing, all of the inputs used must be within the process image.
3. Compile the CFC chart using the "Generate Module Driver" function.
Reference
Additional information is available in the "Process Control System PCS 7 Compendium
Part A - Configuration Guidelines" Operating Manual on the Internet
(https://support.industry.siemens.com/cs/document/107196780).
More information
Additional information regarding GSD files is available in the "SIRIUS 3RW44 Soft Starter"
System Manual > Chapter "Configuration with the GSD File".
GSD, GSDML & EDD files for Soft Starter can be found in the internet. Please follow this
link: http://support.industry.siemens.com and search for
● Soft Starter GSD or
● Soft Starter EDD
See also
Object lists and action lists (Page 139)
Requirements for generating the module drivers (Page 140)
Driver blocks (Page 141)
Note
The following diagrams show example configurations to illustrate configuring in HW Config.
Parameterization Softwares
For parametrizing the device following softwares are availible:
- Soft Starter ES (with OM intergration)
- PDM (with Soft Starter EDD)
- GSD
Overview
For additional information, refer to:
● "SIRIUS 3RW44 Soft Starter" System Manual
● "Getting Started" in the online help for this block library
● Online help for SIMATIC Process Control System PCS 7
● Manuals for SIMATIC Process Control System PCS 7
What's new?
For more details please refer the respective library version Readme.
Please check whether an updated version of readme is available on the internet
(https://support.industry.siemens.com/cs/document/109760625/).
2.2 Faceplates
2.2.1 Faceplates
A faceplate displays all elements of a block graphically. The faceplate is displayed in a
separate window on the Operator Station (OS). You can call the faceplate:
● Using picture selection keys
● From the process tag list
● By clicking the specific block symbol
Tools
The following software and templates are available for configuring the faceplates:
● In WinCCExplorer: the Graphics Designer
● PCS 7-specific standard views
● Templates available from the Faceplate Designer
– Trend
– Batch
– Alarms
● Additionally required views, user objects, and functions
Additional information: You are recommended not to open the PCS 7 Soft Starter SP1
faceplate graphics files (*.pdl) in PCS 7 V7.
Example:
.QCURR:CO_GREEN
Displaying multiple curves:
If multiple curves are to be displayed in the Trend View, parameterize the curves using the
following scheme:
.<Name of structure element 1>:< Color of the curve>,.<Name of structure element 2>:<
Color of the curve>,<Name of structure element 3>:< Color of the curve>
Example:
.QIL1:CO_DKRED,.QIL2:CO_DKBLUE,.QIL3:CO_DKGREEN
Batch View
The Batch View is available in all signal blocks in which the status of batch parameters is
displayed.
Structure
Each block has four assigned block symbols. The different block symbols of the soft starters
are displayed as follows:
If you click the block symbol, the associated faceplate opens. As long as the faceplate is
open, the block symbol is highlighted in color.
The user can configure the block symbol in CFC within the scope of the available selection
via the block symbol number in the object properties of the block.
Symbol STOP
Symbol Error
The symbol flashes when the motor is in the startup or coast-down phase.
⑦ Group display
Reads the message configuration of the block and displays alarms and warnings.
Right-clicking on the group representation of the block symbol opens the Alarm View of the
block.
See also
General (Page 95)
Faceplates (Page 123)
Faceplates (Page 135)
Overview
The SIMOCODE pro PCS 7 Library blocks have an output parameter ErrorNum that can be
used to output internal error states of the block as error numbers. Each error number is
assigned to a specific error. The routine always displays the error number of the error most
recently detected in a block cycle.
"X" = Error occurs in this block. "—" = Error does not occur in this block.
Overview
• QBUSFLT • Failure of a
PROFIBUS DP
station
16#24 2 • QRACK1ERR • Incorrect quality — — — —
or code 2)
QRACK2ERR
• OB is not
loaded
16#60 1 QSIM Simulation — — — —
16#80 0 No error Correct quality code X X X X
"X" = Quality code occurs in this block. "—" = Quality code does not occur in this block.
1) "0" = high
2) Device-specific
3.4.1 Description
Purpose of block
The SS_DIAG block performs the diagnostics of the 3RW44 soft starter:
● It evaluates the acyclic events that are relevant for the 3RW44 soft starter:
– Startup
– DP station failure
– Module error
– Diagnostic interrupt
● It evaluates the diagnostics of the upstream block, e.g.:
– RACKF: Failure of the master system rack
– SUBN1ERR, SUBN2ERR: Subnet error
● It generates the associated quality codes.
● It reads all diagnostic information of the soft starter
● It transfers the diagnostic information to the SS_DIR and SS_MEAS blocks for display in
these blocks.
See also
Technical data (Page 157)
Error numbers (Page 26)
Quality codes (Page 27)
3RW44 soft starter in the Maintenance Station (Page 149)
Module drivers of the soft starter (Page 139)
Block Description
SFB 35 ALARM_8P Generates block-specific messages with values for eight
signals
SFB 52 RDREC Reads a process data set
SFB 54 RALRM Receives the alarm data
SFC 13 DPNRM_DG Reads the diagnostic data of the DP slave
SFC 51 RDSYSST Reads the system status list or the sublist
SFC 6 RD_SINFO Reads the start information of the OB
SFC 64 TIME_TCK Reads the system time
3.4.4 Parameterization
Addressing
The "Generate Module Driver" function assigns all addresses to the SS_DIAG block, for
example:
● LADDR
● DADDR
● RACK_NO
● SLOT_NO
● SUBN1ID
● SUBN_TYP
General
This block executes the following diagnostic functions:
● Acyclic events:
– Rack failure
– QMODF: Module error
– QERR: Priority class error - Malfunction when loading the organization blocks (OB)
● Slave diagnostics:
– QBUSFLT: Failure of a PROFIBUS DP station
● OB_DIAG1: Diagnostics of upstream block
When an error occurs, OMODE=16#40xxxxxx is assigned for the value of the OMODE
output.
If the "Rack failure" error QRACKF=1 occurs, the connection between the PROFIBUS and
the device is canceled. This is indicated as follows: QBUSFLT=1.
When an error occurs, OMODE=16#40xxxxxx is assigned for the value of the OMODE
output.
QERR is only triggered once for one execution cycle of the block.
Block Description
SFC 13 DPNRM_DG Reads the diagnostic data of the PROFIBUS DP slave
SFB 52 RDREC If diagnostic interrupt 82 occurs, this block reads a process
data set.
Byte Meaning
0 Station status 1
1 Station status 2
2 Station status 3
3 Master station number
4 Vendor ID (high byte)
5 Vendor ID (low byte)
6 Further slave-specific diagnostic information
DIAG_DIR
DIAG_DIR is a structured characteristic map that provides the following information.
1) The lost connection is signaled with QBUSFLT and as an alarm in WinCC. See also:
1) This station diagnostics information is mapped onto the QDIAG.DIAG parameter as shown above.
DIAG_MEAS
DIAG_MEAS is a structured characteristic map that provides the following information.
QBUSFLT
DIAG_DIR.DIAG Bit 0 indicates QBUSFLT.
See also
Slave diagnostics of the 3RW44 (Page 33)
OB_DIAG1
The upstream OB_DIAG1 block detects the module failure. The module failure calls the
RACKF parameter and outputs QRACKF parameter sets.
See also
Handling the driver generator (Page 10)
Messages
The diagnostic block outputs the messages via WinCC.
1) The MSG_6, MSG_7 and MSG_8 parameters represent messages that can be user-configured.
2) Parameters with message number for ALARM_8P.
1) The AUX_PR05 bis AUX_PR010 parameters represent auxiliary values for messages that can be user-configured.
The QMS_STAT, QMSG_ACK and QMSG_ERR parameters transfer the information found
in ALARM_8P:
● Status of messages
● Status of an alarm acknowledgement
● Status of errors during data transfer
See also
Block parameters (Page 43)
Description
The identifier for startup is OMODE=16#xx01xxxx. It is entered in OB 100 in the OMODE
output.
All alarm messages are suppressed in OB 100:
The user may define a value for the block parameter RUNUPCYC, different from the default
value of 10 cycles. This is assigned to OB 100 in order to suppress the messages for the
configured cycle count.
OB 100 resets the following errors:
● QERR
● QRACKF
● QMODE
● QRACK1ERR
● QRACK2ERR
See also
CFC charts for 3RW44 soft starter (Page 153)
* = These parameters are structured labels that obtain information from data set 92.
See also
Message features (Page 39)
3.5.1 Description
Purpose of block
The SS_DIR block controls, monitors, and switches the soft starter in the clockwise or
counter-clockwise direction.
This block supports different control functions, such as:
● RUN / STOP
● Monitoring
● Slow speed
● Emergency start
● Lock
● Diagnostics
● Logbook
● Output function
● Trip reset
The SS_DIR block supports various faceplates with block icon for operation and control.
See also
Error numbers (Page 26)
Quality codes (Page 27)
Module drivers of the soft starter (Page 139)
Interconnection of function blocks (Page 42)
CFC charts for 3RW44 soft starter (Page 153)
Technical data (Page 157)
Block Description
SFB 35 ALARM_8P Generates block-specific messages with values for eight
signals
SFB 52 RDREC Reads a data set
SFB 53 WRREC Writes a data set
SFC 20 BLKMOV Copies variables
SFC 6 RD_SINFO Reads the start information of the OB
3.5.4 Parameterization
Note
DPV0 in DP alarm mode
If the device is configured as DPV0 in DP alarm mode in HW Config, these parameters will
not be written to the soft starter.
Parameter sets
The three parameter sets PS1, PS2, and PS3 have been parameterized to specify the basic
parameters, such as:
● Rated operational current
● Velocity
● Torque
● Control functions:
– Startup mode
– Coast-down mode
– Current limits
– ...
See also
CFC charts for 3RW44 soft starter (Page 153)
Parameters View and views for Parameter set 1 to Parameter set 3 (Page 104)
Note
Slow speed must be enabled in order for the Motor CCW operation to be active.
● Trip reset
● Emergency start
● Slow speed
● Output 1
● Output 2
● Disable Quick Stop
The same information is monitored in the faceplate views.
In Manual operation LOCAL mode, the OUT_01 output of the function block monitors the
process image output (PIQ; byte 1 and byte 2). This ensures that the status of the control
output does not change while the CPU switches back to Remote mode.
In Manual operation LOCAL mode, parameterize the parameter sets with Soft Starter ES or
directly in the hardware of the soft starter. These parameters are synchronized with the
parameters of the function block. This ensures that the status of the parameterized values
does not change while the CPU switches back to Remote mode.
The monitoring function does not monitor in Manual operation LOCAL mode.
Switch function block to Auto mode: Set LIOP_SEL = 1 and AUT_L =1 Interlinked parameters
Switch faceplate (OS) to Auto mode: Set LIOP_SEL = 0 and AUT_ON_OP = 1 Operating parameters
Switch function block to Manual mode: Set LIOP_SEL = 1 and AUT_L =0 Interlinked parameters
Switch faceplate (OS) to Auto mode: Set LIOP_SEL = 0 and set AUT_ON_OP = 0 Operating parameters
See also
Standard View (Page 96)
3.5.6 Functions
3.5.6.1 Description
General
The SS_DIR block has the following functions:
● Control
● Monitoring
● Trip reset
● Slow speed
● Emergency start
● Interlock
● Diagnostics
● QGRPERR: Group error
● QCURR: Current message
● Process image input and process image output
● Operator authorizations
● Output 1 and Output 2
● Disable Quick Stop
● Logbook
● Substitute value
● Active parameter sets
● Reading and writing of data sets
● Enabling measurement and statistics
3.5.6.2 Control
Operating mode Manual Operating mode Auto Operating mode Manual Description
operation LOCAL1)
PIQ 0.0 = 1 MOTCW_LI = 1 MOTCW_OP = 1 Motor CW
PIQ 0.1 = 1 MOTCCW_LI = 1 MOTCCW_OP = 1 Motor CCW 2)
PIQ 0.0 = 0 and PII 0.1 = 0 MOTOF_LI = 1 MOTOF_OP = 1 Motor OFF
1) Soft Starter ES
2) The following must be enabled for Motor CCW:
Slow speed SLSPD_LI = 1 in Auto mode, SLSPD_OP = 1 in Manual mode, and PIQ 0.6 = 1
Table 3- 23 General information for Auto and Manual modes: Parameters that indicate the ON/OFF status
3.5.6.3 Monitoring
QMON_ERR, TIME_MON
This function monitors the consistency between the control command and the feedback
signal of the parameter within the specified TIME_MON monitoring time. Each discrepancy is
indicated with monitoring error QMON_ERR.
Table 3- 24 Parameters of control commands with the assigned PIQ and PII bits
The MONITOR parameter indicates whether the monitoring function is enabled or disabled:
MONITOR = 1 enables the monitoring function.
MONITOR = 0 disables the monitoring function.
If the feedback signal of the process image input changes, the monitoring function performs
another check to determine whether a discrepancy exists between the feedback signal and
the process image output. Once the specified monitoring time elapses, any discrepancy is
indicated with monitoring error QMON_ERR.
If the block is in the LOCAL mode, monitoring errors are not checked. The process image
outputs 0.0 and 0.1 monitor the feedback signal of the process image input 0.1. This
prevents a bump from occurring when the operating mode is changed from LOCAL to Auto
or Manual mode.
The monitoring time is specified in seconds. If the monitoring time is less than the sampling
time, the monitoring time will be calibrated to the sampling time.
Purpose
This function allows you to temporarily operate an asynchronous motor in both directions of
rotation at a speed that is less than the rated speed.
The slow speed factor and the slow torque can be entered individually for both directions of
rotation in the Parameters View.
Various parameters are used in the different operating modes to set the slow speed.
Table 3- 25 Parameters for activation of slow speed for each operating mode
1) Precondition for Start Motor CCW is start command Slow speed on the starter.
3.5.6.7 Lock
LOCK, LOCK_ON
The LOCK and LOCK_ON functions are only available in Remote operating mode. An active
lock input prevents switching and disables control commands. LOCK always overwrites
LOCK_ON.
LOCK = 1: LOCK is set to OFF
The control commands are set in order to stop the motor.
QMOT_CW = 0
QMOT_CCW = 0
LOCK_ON = 1: LOCK is set to ON
LOCK_DIR = 0: Motor CW
LOCK_DIR = 1: Motor CCW
The control commands are set in order to start the motor based on the values set in
LOCK_ON and LOCK_DIR:
QMOT_CW = 1
QMOT_CCW = 1
For the LOCK and LOCK_ON functions, the following operating commands and linkable
control commands are disabled:
● MOTCW_OP
● MOTCW_LI
● MOTCCW_LI
The Standard View displays the "padlock" symbol to indicate whether the LOCK and
LOCK_ON functions are set.
Note
If slow speed has not been selected and LOCK_ON, LOCK_DIR command has been
initiated with CCW direction, an error number is generated as ERRORNUM. This status is
displayed in the Standard view in the faceplate as LOCK blinking in the status field.
3.5.6.8 Diagnostics
The SS_DIR block receives diagnostic information from the SS_DIAG block. The SS_DIR
block displays this diagnostic information in various Diagnostics Views.
Note
The SS_DIAG block detects a rack failure and a module failure. These are interconnected
with the SS_DIR block and are indicated at the following outputs:
• QRACKF
• QMODF
See also
Slave diagnostics of the 3RW44 (Page 33)
QGRPERR
The Group error parameter is set when one of the failures or errors listed below is detected.
The Standard View displays these errors as a group error.
● Group error: Process image bit 0.2:
● Module failure
● Rack failure
● Monitoring error
QCURR
Bits 1.0 to 1.5 of the process image input write the current consumption when the motor is
connected. The QCURR output parameter indicates this information in amperes.
3.5.6.11 Process image input and process image output of 3RW44 soft starter
Bit assignment
Byte.Bit Meaning
DP 0.0 Ready to start (automatic)
DP 0.1 Motor ON
DP 0.2 Group error
DP 0.3 Group warning
DP 0.4 Input 1
DP 0.5 Input 2
DP 0.6 Input 3
DP 0.7 Input 4
Motor current
DP 1.0 Motor Current act-bit 0
DP 1.1 Motor Current act-bit 1
DP 1.2 Motor Current act-bit 2
DP 1.3 Motor Current act-bit 3
DP 1.4 Motor Current act-bit 4
DP 1.5 Motor Current act-bit 5
DP 1.6 Manual operation LOCAL mode
DP 1.7 Ramp operation
Byte.Bit Meaning
DP 0.0 Motor CW
DP 0.1 Motor CCW
DP 0.2 Brake
DP 0.3 Trip reset
DP 0.4 Emergency start
DP 0.5 Self-test
DP 0.6 Slow speed
DP 0.7 Reserved
DP 1.0 Output 1
DP 1.1 Output 2
DP 1.2 Active parameter sets 1, 2, 3
DP 1.3
DP 1.4 Reduction factor
DP 1.5
DP 1.6
DP 1.7 Disable Quick Stop
Operator authorizations
The enable parameters allow the operator to issue the desired commands. These
commands are interconnected to the corresponding outputs. This permits operation to be
enabled from the Standard View of the faceplate.
Example:
If the block is in Manual mode and AUTOP_EN = 0, the operator must not change the
operating mode of the block to Auto. He must not change the operating mode from the
Standard View of the faceplate or in the CFC. QAUTOP = FALSE is set in this process.
In a similar manner, every _EN parameter enables the corresponding operation.
PS_OUT1, PS_OUT2
If the outputs device function is applied, the motor starter can carry out various
parameterizable actions. The integer values of PS_OUT1 and PS_OUT2 indicate the various
actions that can be parameterized.
The following parameters are active when setting device functions for Output 1 and Output 2
in Auto or Manual mode.
Table 3- 34 Input parameters for each operating mode, output parameters and bit assignment of the process image for
OUT1 and OUT2
Operating mode Manual Operating mode Auto Output parameter Process image output
Input parameter Input parameter bits
OUT1_OP OUT1_LI QOUTPUT1 PIQ 1.0
OUT2_OP OUT2_LI QOUTPUT2 PIQ 1.1
Table 3- 35 Input parameters for each operating mode, output parameters and bit assignment of the process image
Operating mode Manual Operating mode Auto Output parameter Process image output
Input parameter Input parameter bit
DSQSTP_OP DSQSTP_LI — PIQ 1.7
3.5.6.15 Logbook
Table 3- 36 Messages regarding device errors received from the soft starter, including the related number
Table 3- 37 Messages regarding tripping errors received from the soft starter, including the related number
Table 3- 38 Messages regarding events received from the soft starter, including the related number
SUB_VALUE
The operator parameterizes the substitute value. The SUB_VALUE parameter is 2 bytes
long. The data contained are written to the soft starter via data set 131. If the Response to
CPU/master stop event occurs, the soft starter is switched to the substitute value
parameterized in SUB_VALUE or it retains the last value.
This activation is parameterized at the START_OFF parameter:
PS_SETACT
The process images of output bit PIQ 1.2 and PIQ 1.3 correspond to the settings that the
operator makes for the active parameter sets. These are based on the parameterization of
parameter PS_SETACT = 1, 2, or 3. The digits 1, 2, and 3 refer to the corresponding
parameter sets 1, 2, and 3.
PS_SETACT = 1 (Standard)
PIQ DP 1.2 = FALSE
PIQ DP 1.3 = FALSE
PS_SETACT = 2 (Standard)
PIQ DP 1.2 = TRUE
PIQ DP 1.3 = FALSE
PS_SETACT = 3 (Standard)
PIQ DP 1.2 = FALSE
PIQ DP 1.3 = TRUE
RDREC, WRREC
For detailed information on data sets, refer to the "SIRIUS 3RW44 Soft Starter" System
Manual > Chapter "Communication Module PROFIBUS DP" > "Data Sets"
Table 3- 39 Data set table: Read access and/or write access for each data set
No. Data set no. Read access/ Number of Description of data set
write access bytes
1 68 R/W 8 Reading/Writing the Process Image of the Outputs
2 72 R 126 Log List - Reading device errors
3 73 R 126 Log List - Reading the trippings
4 75 R 126 Log List - Reading events
5 93 W 10 Writing a command
6 131 R/W 138 Technology parameter 2: Set 1
7 132 R/W 64 Technology parameter 3: Set 1
8 141 R/W 138 Technology parameter 2: Set 2
9 142 R/W 64 Technology parameter 3: Set 2
10 151 R/W 138 Technology parameter 2: Set 3
11 152 R/W 64 Technology parameter 3: Set 3
These data sets are based on the read authorization and/or write authorization. The
RDREC function is used to read the values and the WRREC function is used to write the
setting in the soft starter.
The Q_ENRDWR parameter indicates: The read function or write function is being executed.
Read function
Data sets are read with the following parameters:
Write function
The WRREC function writes all values changed by the user to the device.
QERR_WR = 1 indicates errors when writing a data set.
EN_MEAS, EN_STAT
A logical value "1" in the EN_MEAS and EN_STAT parameters activates the link for opening
the faceplates for the measurement block and the statistics block.
Note
Configure the SS_MEAS function block for measurement and the SS_STAT function block
for statistics in the same CFC as the SS_DIR block.
Messages
The following messages are generated:
1) The AUX_PR04 bis AUX_PR07 parameters represent auxiliary values for messages that can be user-configured.
The M_SUP_C input can enable and disable the messages. The QMSG_STAT, QMSG_ACK
and QMSG_ERR parameters transfer the information found in ALARM_8P:
● Status of messages
● Status of an alarm acknowledgement
● Status of errors during data transfer
Description
All alarm messages are suppressed in OB 100:
The user defines a value for RUNUPCY. This is assigned to OB 100 in order to suppress the
messages for the configured cycle count.
Depending on the value set for the START_OFF characteristic, the outputs contain either the
last valid value or the reset substitute value.
QMOT_CCW = 1)
QMOT_SLSPD = 1)
QOUTPUT1 = 1)
QOUTPUT2 = 1)
1) These parameters follow the value in OUT_01 PIQ 0.0 to PIQ 1.7.
If START_OFF = 1, all the outputs indicated above contain the last valid value.
3.5.12 Faceplates
3.5.12.1 General
Table 3- 46 Signal block for direct starter control function SS_DIR: Faceplates with their associated
PDL file names
See also
Block icons (Page 21)
Symbol RUN CW
Symbol STOP
Symbol Error
See also
Operating modes (Page 48)
① EN_STAT This button opens the faceplate for the statistics block.
This control function is available to users with authorization level 5 and higher.
② SUB_VALUE Activates or deactivates substitute values and sets the active parameter set.
This control function is available to users with authorization level 6 and higher.
③ START_OFF Sets the Response to CPU/master stop.
This control function is available to users with authorization level 6 and higher.
④ OUT1_O2 Activates or deactivates the Output2 function.
This control function is available to users with authorization level 6 and higher.
⑤ OUT1_OP Activates or deactivates the Output1 function.
This control function is available to users with authorization level 6 and higher.
① QCURR, PS_COMMON, Displays the current as a bar diagram for parameter sets 1, 2, and 3.
PS1_IRATE, PS1_CURH, Based on the setting in the "Response to current limit value violation" field of
PS1_CURL, PS2_IRATE, the Parameters View, the colors of the limits in the columns change from
PS2_CURH, PS2_CURL, yellow (= warning) to red (= trip).
PS3_IRATE, PS3_CURH,
PS3_CURL
② QCURR Indicates the motor current for the selected parameter set. The selected
parameter set is highlighted in a different color.
③ PS1_CURH, PS1_CURL Parameter set 1 current limits
This control function is available to users with authorization level 6 and higher.
④ PS2_CURH, PS2_CURL Parameter set 2 current limits
This control function is available to users with authorization level 6 and higher.
⑤ PS3_CURH, PS3_CURL Parameter set 3 current limits
This control function is available to users with authorization level 6 and higher.
⑥ ReadData Button for enabling reading of data.
This control function is available to users with authorization level 5 and higher.
The user can define the text on the button: String_1 attribute of RD_DATA
Figure 3-6 SS_DIR: Limits View
3.5.12.7 Parameters View and views for Parameter set 1 to Parameter set 3
Note
Parameter set 1, Parameter set 2, Parameter set 3
The settings in the "Startup mode" and "Coasting method" fields determine whether or not
the field for assigning settings for the soft starter is enabled.
① DEL_LOGEVNT This control function is available to users with authorization level 5 and higher. The user can
define the text on the button:
String_1 attribute of DEL_LOGEVNT
② DEL_LOGTRP This control function is available to users with authorization level 5 and higher. The user can
define the text on the button:
String_1 attribute of DEL_LOGTRP
③ RD_DATA Button for enabling reading of data. This control function is available to users with authorization
level 5 and higher. The user can define the text on the button: String_1 attribute of RD_DATA.
Figure 3-11 SS_DIR: Logbook View
3.5.12.9 Views: Station Diagnostics, Control Diagnostics, Device Diagnostics, and Parameter
Diagnostics
Figure 3-13 SS_DIR: Control Diagnostics View - Switching, controlling, and communication
See also
Slave diagnostics of the 3RW44 (Page 33)
Symbol RUN CW
Symbol STOP
Symbol Error
The symbol flashes when the motor is in the startup or coast-down phase.
⑦ Group display
Reads the message configuration of the block and displays alarms and warnings.
Right-clicking on the group representation of the block symbol opens the Alarm View of the
block.
3.6.1 Description
Purpose of block
The SS_MEAS block provides:
● Measurement information regarding:
– Phase currents
– Thermal motor model
– Output power
– Phase-to-phase voltages
– Line frequency
– Asymmetry
– ...
● Information regarding diagnostics of measurement parameters
The block receives information from the SS_DIAG and SS_DIR blocks.
See also
Error numbers (Page 26)
Quality codes (Page 27)
Module drivers of the soft starter (Page 139)
Interconnection of function blocks (Page 42)
CFC charts for 3RW44 soft starter (Page 153)
Technical data (Page 157)
Recommendation:
You are recommended to insert the block SS_MEAS into OB 32 for cyclic operation.
See also the CFC manual.
Block Description
SFB 35 ALARM_8P Generates block-specific messages with values for eight
signals
SFB 52 RDREC Reads a data set
SFC 6 RD_SINFO Reads the OB start information
SFC 20 BLKMOV Move block
3.6.4 Parameterization
Interconnection
In addition, set: IN_01 = PII address (logical address).
See also
CFC charts for 3RW44 soft starter (Page 153)
3.6.6 Functions
Measurement functions
For detailed information on measured values, refer to the "SIRIUS Soft Starter 3RW44"
System Manual > Chapter "Communication Module PROFIBUS DP" > "Data Sets" > "Data
Set 94 - Reading the Measured Values".
These values are displayed in the faceplate in the Standard View and Standard 2 View.
Name of output parameter Structured characteristic map QDIAGMEAS bit no. Description
DIAG_MEAS
QDIAGMEAS: TMPSNSOVLD 0 Temperature sensor overload
Measurement parameter TMPSNSOPEN 1 Temperature sensor open
diagnostics
TMPSNSSHORT 2 Temperature sensor short
TMMOVLD 3 Thermal motor model overload
OVLDSWOFF 4 Overload switch off
IDLETMACT 5 Idle time active
COOLDNTMACT 6 Cooldown time active
ASYMREC 7 Asymmetry recognized
ASYMSWOFF 8 Asymmetry switch-off
CURLMACT 9 Current limiting active
CURHI 10 Current limit exceeded
CURLO 11 Current limit undershot
CURLMSWOFF 12 Current limit switch-off
MOTSTLSWOFF 13 Motor stalled-switched off
INPUT1 14 Input1 active
INPUT2 15 Input2 active
INPUT3 16 Input3 active
INPUT4 17 Input4 active
GNDFLT 18 Ground fault
GNDFLTSWOFF 19 Ground fault switch off
TMMDEACT 20 Thermal motor model deactivated
PHANGCTRFLT 21 Phase angle control failure
COOLCNTACT 22 Cooldown time contact block active
CTNHOTSTART 23 Contact element too hot for starting
CUROVERFLOW 24 Current range overflow
PREWRNUNDSHT 25 Prewarning limit-prewarning time
undershot
PREWRNHTEXED 26 Prewarning limit-motor heat build-
upexceeded
-- 27...31 Reserved
Messages
The following messages are generated:
1) The AUX_PR04 to AUX_PR010 parameters represent auxiliary values for messages that can be user-configured.
The M_SUP_C input can enable and disable the messages. The QMS_STAT, QMSG_ACK
and QMSG_ERR parameters transfer the information found in ALARM_8P:
● Status of messages
● Status of an alarm acknowledgement
● Status of errors during data transfer
3.6.10 Faceplates
Table 3- 54 Measurement block SS_MEAS Faceplates with their associated PDL file names
Standard View
Standard 2 View
Right-clicking on the group representation of the block symbol opens the Alarm View of the
block.
See also
Block icons (Page 21)
3.7.1 Description
Purpose of block
The SS_STAT block provides statistical information related to:
● Operating hours
● Operating cycles
● Error statistics
● Current measurement
● Maximum pointer
● ...
The block receives information from the SS_DIAG and SS_DIR blocks.
See also
Error numbers (Page 26)
Quality codes (Page 27)
Module drivers of the soft starter (Page 139)
Interconnection of function blocks (Page 42)
CFC charts for 3RW44 soft starter (Page 153)
Technical data (Page 157)
Recommendation:
You are recommended to insert the SS_STAT block into OB 32 for cyclic operation.
See also the CFC manual.
Block Description
SFB 52 RDREC Reads a data set
SFB 53 WRREC Writes a data set
SFC 6 RD_SINFO Reads the start information of the OB
3.7.4 Parameterization
See also
CFC charts for 3RW44 soft starter (Page 153)
3.7.6 Functions
Statistical values
For detailed information on statistical values, refer to the "SIRIUS Soft Starter 3RW44"
System Manual > Chapter "Communication Module PROFIBUS DP" > "Data Sets":
● > Data Set 93 - "Writing a Command"
● > Data Set 95 - "Reading the Statistics Data"
● > Data Set 96 - "Reading the Maximum Pointer"
Table 3- 57 Data set 93, Data set 95, and Data set 96: Read access and/or write access
Statistics function
Data set 95 reads the statistics data. These are displayed in the faceplate in Standard View.
3.7.8 Faceplates
Table 3- 59 Statistics block SS_STAT: Faceplates with their associated PDL file names
Standard View
See also
Block icons (Page 21)
Description
The object lists and the action lists are used to generate the module drivers for these
hardware modules.
The object list contains a unique object identification number for each of these hardware
modules. Each object list is assigned to a particular hardware configuration.
The action list contains a list of actions. These actions must be executed for the object
identification numbers that appear in the object list Examples of such actions include:
● Assigning the device address
● Interconnecting the input and output parameters of the driver block
The "Generate Module Driver" function generates the module drivers when the CFC is
compiled.
See also
Handling the driver generator (Page 10)
Requirements
After generating an instance for a signal block, ensure that the following requirements are
met:
● IN_01 and IN_02 are parameterized.
● The driver blocks have been generated in the CFC with the "Generate module driver"
function when compiling the CFC chart.
Note
To have similar behavior between this library and the PCS 7 Basis Library, a PCS 7 Basis
Library version supporting this functionality needs to be installed as well.
Circuit diagrams
Figure 4-1 Circuit diagram: 3RW44 soft starter directly on the DP master system
Note
The blocks highlighted in yellow are inserted by module driver generator. The blocks
highlighted in white are inserted in CFC charts as part of template.
Note
The blocks highlighted in yellow are inserted by module driver generator. The blocks
highlighted in white are inserted in CFC charts as part of template.
3RW44 soft starter directly on the DP master system - Configuration using the hardware catalog or a
GSD file
The following driver blocks and interconnections are generated when the CFC is compiled:
1. SS_DIAG - Diagnostics for the SIRIUS 3RW44 soft starter
2. OB_DIAG1 - OB diagnostic function
3. OB_BEGIN - CPU function block
4. MOD_SWT - Message diagnostic for slave connected to the DP master system
1) 3RW44 soft starter directly on the DP master system: DP alarm mode is set to DPV1.
2) The driver blocks for PCS 7 V6.1 do not support interconnection of the CPU_DIAG parameter with MOD_SWT.
Note
This table specifies the interconnections between the blocks. For e.g. the first line eplains
that the QRACKF pin of OB_DIAG1 block is interconnected to RACKF pin of SS_DIAG
Block.
3RW44 soft starter following a Y link - Configuration using OM supplied by Soft Starter ES
This configuration cannot be applied.
The driver blocks for PCS 7 V6.1 do not support interconnection of the CPU_DIAG parameter with MOD_SWT.
Note
3RW44 soft starter following a Y link - Configuration using GSD file
If you are using the communication module with firmware version < E*04, a DPV1 following
the Y link is not possible.
More information
Additional information regarding GSD files is available in the "SIRIUS 3RW44 Soft Starter"
System Manual > Chapter "Configuration with the GSD File".
Additional information on:
DPV1 functionality for SIRIUS 3RW44 soft starter following a Y link
(https://support.industry.siemens.com)
1. Enter the following search term in the "Product Name or Part Number" field: y link 3rw44
2. Select the entry.
See also
Handling the driver generator (Page 10)
Figure 5-1 Message diagnostics for PA slave DP V0 linked to the DP master system
Figure 6-1 Path of directory where the CFC charts are stored
Note:
To facilitate the symbolic interconnection of the block inputs and outputs IN_01 and OUT_01
with the inputs and outputs of the device, symbols can be created in the symbol table.
You can find the symbol table in the HW Config Options > Symbol Table.
The inputs and outputs for the device are created here. Since the addresses are available in
BYTE, and the blocks are interconnected with WORD, the data type must be stored
accordingly in the symbol table.
In this example, the symbols In01 and Out01 are assigned for the addresses IW 2 and QW 2
in data type WORD.
The suitable symbol can now be selected when interconnecting.
Alternatively, editing can be carried out without the symbol table. Then a direct
interconnection is made with, for example, IW 2.
See also
Parameterization (Page 46)
Parameterization (Page 116)
Parameterization (Page 129)
Interconnection of function blocks (Page 42)
Table 7- 1 Memory requirement, FB number, and called blocks, per block type
Name of FB no. 2) Length of block Length of block Length of instance Length of instance Temporary Blocks
block 1) in the load in the work data in the load data in the work memory, in called 6)
memory, in memory, in memory, in memory, in bytes 5)
bytes 3) bytes 3) bytes 4) bytes 4)
SS_DIAG 561 5680 4756 1178 418 422 SFB 35
SFB 52
SFB 54
SFC 13
SFC 51
SFC 6
SS_DIR 562 46538 43038 4506 2520 106 SFB 35
SFB 52
SFB 53
SFC 20
SFC 6
SFC 64
SS_STAT 563 5052 4564 906 530 56 SFB 52
SFB 53
SFC 6
SS_MEAS 564 3524 2988 1044 590 62 SFB 35
SFB 52
SFB 6
SFC 20
1) The symbolic designator in the symbol table of the library for the respective function block (FB). It must be unique within
the project.
2) Composed of the block type, e.g., FB for function block and the number.
3) Memory requirement of program code, once per block type.
4) Memory requirement for an instance data block.
5) The memory required for the local data when the block is called in an execution level. This is limited according to the
specific CPU. If this amount is exceeded, you must check the setting in the CPU configuration and redistribute it among
the organization blocks based on the actual requirement.
6) The relevant driver block uses these blocks. They are now located in the user program They are stored in the same
library.
Overview
Abbreviation Meaning
AS Automation station
HMI Human Machine Interface
CFC Continuous Function Chart
CCW Counter-clockwise
CW Clockwise
DC Direct-current voltage
DP Distributed Peripherals
ES Engineering system
FB Function block
GSD Generic Station Description
HW Config "Hardware configuration" module in SIMATIC Manager
ID Identification number
OB Organization block
OS Operator station
PCS 7 Process Control System 7
PIQ Process image output
PII Process image input
PG Programming device
PS Parameter set
RS Formerly: Radio Selector; now usually: Recommended Standard
SFB System function block
SFC Sequential function chart
PLC Programmable logic controller
SS Soft starter
SSL System status list
TIA Totally Integrated Automation