Controlling a D435 via TM54F and F-CPU Function Example No

Applikationen & Tools

Answers for industry.

Cover

Controlling a D435 via TM54F and F-CPU

Function Example No. MC-FE-I-007-V12-EN

SIMOTION with SINAMICS S120

Application February 2012

2 SIMOTION with SINAMICS S120, Failsave drives

V1.2, Item-ID: 31410726

Co

pyr

igh

t

Sie

me

ns

AG

20

12

All

righ

ts r

ese

rve

d

Siemens Industry Online Support

This article is taken from the Siemens Industry Online Support. The following link takes you directly to the download page of this document:

http://support.automation.siemens.com/WW/view/en/31410726

Caution The functions and solutions described in this article confine themselves to the realization of the automation task predominantly. Please take into account furthermore that corresponding protective measures have to be taken up in the context of Industrial Security when connecting your equipment to other parts of the plant, the enterprise network or the Internet. Further information can be found under the Item-ID 50203404.


If you have any questions concerning this document please e-mail us to the following address:

mailto: [email protected]

You can also actively use our Technical Forum from the Service & Support Portal regarding this subject. Add your questions, suggestions and problems and discuss them together in our strong forum community:

http://www.siemens.com/forum-applications



mailto:[email protected]?subject=MC-FE-I-007-V12-DE%20,%20Beitrags-ID:%2031410726

http://www.automation.siemens.com/WW/forum/guests/Conference.aspx?ForumID=230&Language=en

SIMOTION with SINAMICS S120, Failsave drives V1.2, Item-ID: 31410726 3

Co

pyr

igh

t

Sie

me

ns

AG

20

12

All

righ

ts r

ese

rve

d

s

SIMOTION with SINAMICS S120 Failsafe drives Controlling a D435 via TM54F and F-CPU

Automation function

1

Required components

2

Configuration and wiring

3

Overview and operation

4

Example project

5

Contact

6

Warranty and liability


V1.2, Item-ID: 31410726

Co

pyr

igh

t

Sie

me

ns

AG

20

12

All

righ

ts r

ese

rve

d

Warranty and liability

Preliminary remarks

Functional examples for the topic "Safety Integrated" are fully-functioning and tested automation configurations based on standard I DT & IA products for simple, fast and low-cost implementation of automation tasks in safety engineering. Each of the functional examples presented deals with sub-task of a typical problem that customers are frequently confronted with in safety engineering.

Besides listing all the necessary software and hardware components, and describing their interconnection, the functional examples also include tested and commented code. This means that the functions described here can be set up within a short time and can thus be used as the basis for expanded and adapted solutions.

Note 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 here of is prohibited without the expressed consent of Siemens Industry Sector.

Table of contents

SIMOTION with SINAMICS S120, Failsave drives V1.2, Item-ID: 31410726 5

Co

pyr

igh

t

Sie

me

ns

AG

20

12

All

righ

ts r

ese

rve

d

Table of contents Warranty and liability................................................................................................... 4 1 Automation function.......................................................................................... 6

1.1 Description of the function example ..................................................... 6 1.2 Advantages / customer benefits........................................................... 9

2 Required components..................................................................................... 10 2.1 Hardware components ....................................................................... 10 2.2 Software components......................................................................... 11 2.2.1 Engineering software.......................................................................... 11 2.2.2 Firmware ............................................................................................ 11

3 Configuration and wiring ................................................................................ 12 3.1 Overview of the hardware configuration............................................. 12 3.2 Wiring of the hardware components .................................................. 12 3.2.1 Wiring the control voltage................................................................... 12 3.2.2 Principle connection of the F-CPU to the TM54F .............................. 14 3.2.3 DRIVE-CLiQ interconnection ............................................................. 15 3.3 Important settings of the hardware components................................ 16 3.3.1 Bus interfaces..................................................................................... 16 3.3.2 Bus topology....................................................................................... 18

4 Overview and operation.................................................................................. 19 4.1 Description of operation ..................................................................... 19 4.2 Summary of the input signals............................................................. 21

5 Example project ............................................................................................... 22 5.1 Passwords.......................................................................................... 22 5.2 Hardware configuration of the fail-safe control .................................. 23 5.3 Programming the fail-safe control ...................................................... 27 5.4 Configuring the drives ........................................................................ 30 5.4.1 Inserting SIMOTION into the existing SIMATIC project ..................... 30 5.4.2 Basic commissioning of the SINAMICS drives (without safety) ......... 33 5.5 Parameterizing the safety functions in SINAMICS Integrated ........... 39 5.5.1 Configuring the message frame ......................................................... 39 5.5.2 Configuring the fail-safe TM54F terminal module .............................. 40 5.5.3 Configuring the safety functions in the drives .................................... 43 5.5.4 Configuring the safety data block on the SINAMICS side.................. 47 5.6 SIMOTION.......................................................................................... 49 5.6.1 Creating SIMOTION axes .................................................................. 49 5.6.2 SIMOTION programs ......................................................................... 57 5.6.3 Configuration of the execution system............................................... 61 5.6.4 SIMOTION messages ........................................................................ 62 5.7 Download of the project example....................................................... 62 5.7.1 Downloding the S7-F-CPU project configuration ............................... 63 5.7.2 Downloading the project configuration of SIMOTION and

SINAMICS Integrated......................................................................... 64 5.8 Acceptance test.................................................................................. 66

6 Contact.............................................................................................................. 66

Table of contents


V1.2, Item-ID: 31410726

Co

pyr

igh

t S

iem

en

s A

G 2

01

2 A

ll rig

hts

re

serv

ed

1 Automation function

1.1 Description of the function example

The following safety functions according to IEC 61800-5-2 are integrated in SINAMICS S120 drives:

Name Function Description

STO Safe Torque Off • The torque-generating energy-feed to the motor is switched off in a safety-oriented fashion.

• The closing lock-out prevents the drive unit from being restarted. (Stop function, Category 0 according to EN 60204-1)

SBC Safe Brake Control

• SBC is only used when there is a motor brake; the motor brake is connected to the power connector through the outputs.

• SBC always responds in conjunction with STO or when internal safety monitoring functions respond with safe pulse suppression.

SS1 Safe Stop 1 • The drive is quickly and safely stopped along the OFF3 ramp and is safely monitored.

• Transition to STO after a delay time has expired or the shutdown speed has been reached. (Stop function, Category 1 according to EN 60204-1)

SS2 Safe Stop 2 • The drive is quickly and safely stopped along the OFF3 ramp and is safely monitored.

• Transition into SOS after a delay time has expired; the drive remains in closed-loop control. (Stop function, Category 2 according to EN 60204-1)

SOS Safe Operating Stop

• This function serves to safely monitor the standstill position of a drive; the drive remains in closed-loop control.

SLS Safely-Limited Speed

• The drive speed is safely monitored. • Parameterizable shutdown response when

the limit value is violated. SSM Safe Speed

Monitor • Safely displays when a speed limit is fallen

below (n < nx)

These extended safety functions can be controlled via PROFIsafe with PROFIBUS as well as via a TM54F terminal expansion module. In this example, the safety functions are controlled via the TM54F.

Task description

A system equipped with SINAMICS S120 drives is controlled from a SIMOTION D435. Different safety functions are required in the system.

SIMOTION with SINAMICS S120, Failsave drives 31410726

I DT Safety Integrated Page 7/66 V1.2

Co

pyr

igh

t S

iem

en

s A

G 2

01

2 A

ll rig

hts

re

serv

ed

3

141

072

6_

mc_

fe_

i_00

7_

v12

_en

.do

c

SIMOTION itself has no safety functions. The extended safety functions integrated in the SINAMICS S120 drives are used.

These safety functions integrated in the drive are to be controlled from a TM54F using hardware signals. The drives belong to different drives groups. An F-CPU handles the safety-oriented logical pre-processing of the input signals.

This function example is based on the SIMOTION D435 training case (6ZB2 470-0AE00) and the SAFETY training case.

A typical overview of the assumed machine configuration is shown in the following diagram.

Table of contents


V1.2, Item-ID: 31410726

Co

pyr

igh

t S

iem

en

s A

G 2

01

2 A

ll rig

hts

re

serv

ed

The following safety functions are used as basis for further consideration.

Safety function

Description Response

SF1 The Emergency Stop button is actuated.

Drive 1 is quickly stopped in a controlled fashion -> subsequent pulse suppression (SS1).

Drive 2 is stopped with immediate pulse suppression (STO).

SF2

Opening safety door 1 while Drive 1 is turning, Drive 1 should be stopped quickly due to the violation of safety condition. After Drive 1 is stopped with speed setpoint = 0 the standstill position is safely monitored.

The SIMOTION brakes drive 1 in the closed-loop position controlled mode. The standstill position is safely monitored (SOS) after a delay time has expired

SF3 When safety door 2 is open, Drive 2 must not exceed the user defined safe speed.

The speed of drive 2 is monitored (SLS)

Solution

Hardware overview

This function example shows how the STO, SS1, SOS and SLS safety functions are controlled via the terminal expansion module TM54F at a SIMOTION D435 with a SINAMICS S120 drive group.

The drive line-up in the booksize format comprises an infeed and a Double Motor Module. A SIMOTION D435 is used for the closed-loop motion control and closed-loop motor control. The two servomotors, which are independent of one another,



Co

pyr

igh

t S

iem

en

s A

G 2

01

2 A

ll rig

hts

re

serv

ed

3

141

072

6_

mc_

fe_

i_00

7_

v12

_en

.do

c

are controlled from the Double Motor Module. A Smart Line Module is used as infeed.

The safety-oriented signals are sensed using fail-safe inputs of the ET200M and evaluated in the F-CPU. The pre-processed signals are transferred to the TM54F terminal expansion module via fail-safe ET200M outputs. These control the safety functions integrated in the SINAMICS S120 drive.

When Emergency Stop is initiated, drive 1 is stopped using the SS1 function integrated in the drive and drive 2 is stopped with STO.

The other two switches (-S2 and -S3) in the Safety training case each simulate a safety door for drive 1 and 2. If safety door 1 is opened, then SIMOTION brakes drive 1 down to standstill (zero speed). After a configurable safe delay time has expired, the standstill position is safely monitored (the SOS function is selected). When the door is closed, axis 1 restarts (the SOS function is deselected). When safety door 2 is opened, the speed of drive 2 is monitored against an user defined safe speed setpoint value in both directions (SLS function). The setpoint speed is limited to 80% of the selected SLS stage, where up to 4 SLS stages can be defined and selected. The speed limit is withdrawn if the simulated door is closed again. The other drive is not influenced.

1.2 Advantages / customer benefits

• The safety functions integrated in the drive are simply controlled.

• Simple design using standard technology.

• The existing system can be quickly and simply expanded.

• Space-saving and favorably-priced design using integrated safety functions – additional hardware is not required.

• User-friendly evaluation and diagnostic information is available in the SIMOTION system.

• Other safety concepts can be realized using this as basis.

Table of contents


V1.2, Item-ID: 31410726

Co

pyr

igh

t S

iem

en

s A

G 2

01

2 A

ll rig

hts

re

serv

ed

2 Required components The hardware components and software versions required in this function example are listed in this chapter.

2.1 Hardware components

SAFETY training case (essential components)

Component Type MLFB/Ordering data Qty Manufacturer

SITOP power supply SITOP SMART 120W 6EP1333-2AA01 1 Siemens

CPU 315F-2 PN/DP 6ES7315-2FH13-0AB0 1 Siemens

SIMATIC S7-300 CPU SIMATIC Micro Memory Card, 512KB

6ES7953-8LJ20-0AA0 1 Siemens

SIMATIC S7 fail-safe input module

SM 326 F-DI 24 6ES7326-1BK01-0AB0 1 Siemens

SIMATIC S7 fail-safe output module

SM 326 F-DO 8 6ES7326-1BF40-0AB0 1 Siemens

SINAMICS fail-safe Terminal Module

TM54F 6SL3055-0AA00-3BA0 1 Siemens

Drive-CLiQ Cable, gray, metal connector 6FX2002-1DC00-1AC0 1 Siemens

Toggle switch 0-I, latching, 16mm, black

3SB2000-2AB01 2 Siemens Safety door simulation switches

S2 and S3 Holder with solder pins 3SB2908-0AB 2 Siemens

Mushroom pushbutton, red, 16mm

3SB2000-1AC01 1 Siemens Emergency Stop command device

S1 Holder with solder pins 3SB2908-0AB 1 Siemens

Pushbutton, flat button, 16 mm, white

3SB2000-0AG01 1 Siemens Reset button

S4 Holder with lamp holder, lamp and solder pins

3SB2455-1B 1 Siemens

Load resistors R1 .. R8

1kOhm 1W

Type PO595-0 Style 0207

Power metal oxide film resistors

1 Yageo Europe

ST 2.5-QUATTRO-TG 3038451 8 Phoenix Contact Terminals for load

resistors (R1..R8) P-CO component connector 3036796 8

Phoenix Contact

Load resistor R9 SMA0207 1K2 1% TK

WID_MET_SHT_1K2_+-

1%_600mW_+50ppm_0207

1 Beyschlag

TERMINALS_ACCESSORY_EMPTY

CONNECTOR_TYPE1_GRAY

280-801 1 WAGO Terminals for load resistor

(R9)

TERMINAL_4-CONDUCTOR_GRAY

280-686 1 WAGO



Co

pyr

igh

t S

iem

en

s A

G 2

01

2 A

ll rig

hts

re

serv

ed

3

141

072

6_

mc_

fe_

i_00

7_

v12

_en

.do

c

SIMOTION training case


SIMOTION training case D435 6ZB2470-0AE00 1 SIEMENS

Note For this function example a SIMOTION D435 6AU1435-0AA00-0AA1 HW Release D or higher and a Double Motor Module that part number ends with -AA3 or higher is required.

Note The function example was tested with the hardware components listed here. Alternatively, other components with the same function may be used. In such a case, a different parameterization and different wiring of the components may be required.

2.2 Software components

2.2.1 Engineering software


STEP 7 V5.4 SP4 6ES7810-4CC08-0YA5 1 Siemens

S7 Distributed Safety programming

V5.4 SP4 6ES7833-1FC+02-0YA5 1 Siemens

S7 F ConfigurationPack V5.5 SP5 1 Siemens

SIMOTION SCOUT V4.1 SP2 6AU1810-1BA41-2XA0 1 Siemens

2.2.2 Firmware

All SINAMICS components must have firmware release V2.5 SP1 or higher.

SIMOTION must be operated with a firmware release V4.1 SP1 or higher.

https://mall.automation.siemens.com/DE/member/bizLogic/bizGotoMLFB.asp?nodeID=10027665&mlfb=6AU1810%2D0BA40%2D0XA0&siteID=DE&lang=de

Table of contents


V1.2, Item-ID: 31410726

Co

pyr

igh

t S

iem

en

s A

G 2

01

2 A

ll rig

hts

re

serv

ed

3 Configuration and wiring

3.1 Overview of the hardware configuration

Basic configuration

3.2 Wiring of the hardware components

3.2.1 Wiring the control voltage



Co

pyr

igh

t

Sie

me

ns

AG

20

09

All

righ

ts r

ese

rve

d

31

410

726

_m

c_fe

_i_

007

_v1

2_

en.d

oc

3 2BConfiguration and wiring


V1.2, Item-ID: 31410726

Co

pyr

igh

t

Sie

me

ns

AG

20

12

All

righ

ts r

ese

rve

d

3.2.2 Principle connection of the F-CPU to the TM54F

failsafe digital output module (ET200S/

ET200M) TM54F

-X5201 L3+2 M1

1 L1+-X521

2 DI 0

3 DI 1+4 DI 2

5 DI 3+6 DI 1-

7 DI 3-8 M1

F-DI 0

F-DI 1

DO 0+

DO 0-

M1

F-DO 0R2R1

Connection, F-DO P/M switching (F-CPU) → F-DI (TM54F)

Dimensioning the load resistors

Any conditions specified for the digital output in the manufacturer's documentation, (e.g. a minimum load or a maximum load resistance) should be taken into account.

For example, the range for the load resistance from 12Ω up to 1 kΩ is specified for the SIMATIC ET200S 4 F-DO I/O module.

A resistance is required if the residual current (at “0” signal) of the P- or M-switch is higher then 0.5mA. If it is less no resistance is necessary. The resistance of the F-DI at the TM54F is high enough that it can be disregarded for the calculation of the resistance. The maximum voltage for “0” signal at the F-DI (TM54F) is 5V. To calculate the value of the resistance you can use this formula:

]A[currentresidual

V5Rx ≤

The thermal power loss at this resistance can be calculated like shown:

V8.28%20V24V;R

VP

2

=+==

Note: When using regulated SITOP power supplies, the voltage tolerance on the 24 V side is significantly less than the maximum permissible tolerance of +20% of the power supply voltage at the ET200S modules. The power dissipated in the resistor is, in this case, less than the maximum power calculated above.

Note: If a ET200S 4 F-DO module is used we recommend to use a 1 F-RO module instead of the resistors.


I DT Safety Integrated Page 15/66

Co

pyr

igh

t

Sie

me

ns

AG

20

12

All

righ

ts r

ese

rve

d

3.2.3 DRIVE-CLiQ interconnection

The SINAMICS units should be connected-up using the DRIVE-CLiQ cable as shown in the following diagram.

TM54F

DRIVE-CLiQ-X500-X501

D435


-X102-X103

PROFIBUS

SLM

-X126

DMM


-X202-X203

Encoder 2

Encoder 1

-X127

Ethernet-X120

-X130

DRIVE-CLiQ interconnection



V1.2, Item-ID: 31410726

Co

pyr

igh

t

Sie

me

ns

AG

20

12

All

righ

ts r

ese

rve

d

3.3 Important settings of the hardware components

In this function example, the PROFIBUS interfaces of the F-CPU and the D435 are only used for programming. Hardwired 24 V signals are used exclusively for the safety-oriented signal exchange between the F-CPU and the TM54F.

3.3.1 Bus interfaces

Programming device / PC

• PROFIBUS address = 0

• As the F-CPU used is the bus master, the PROFIBUS interface of the programming device must not be configured as the only master on the bus (do not enter a checkmark in the field "PG/PC is the only master on the bus").



Co

pyr

igh

t

Sie

me

ns

AG

20

12

All

righ

ts r

ese

rve

d

SIMOTION D435


• The PROFIBUS address is set via HW Config.

SIMATIC 315F-2 PN/DP CPU




V1.2, Item-ID: 31410726

Co

pyr

igh

t

Sie

me

ns

AG

20

12

All

righ

ts r

ese

rve

d

3.3.2 Bus topology

View in NetPro

Conditions for operation

• The SIMATIC components have been mounted and connected with one another. The PROFIsafe addresses of the fail-safe input and output modules must be set using the DIL switch; see Chapter 5.2.

• All of the components are connected as specified in Chapter 3.2.

• The DRIVE-CLiQ topology of the SINAMICS components has been maintained.

• The motors are connected to the Motor Module using the power and encoder cable.

• The Motor Module is correctly connected with the infeed (DC link and 24 V DC control voltage).

• The infeed is connected to the line supply.

• The components are supplied with 24 V DC.

4 Overview and operation


Co

pyr

igh

t

Sie

me

ns

AG

20

12

All

righ

ts r

ese

rve

d


4.1 Description of operation

Hardware overview

In order to operate the drives, SIMOTION must first be switched into the "RUN" state. In the example, this is realized using SCOUT. To do this, object D435 is selected and the righthand mouse key pressed. The following selection should now be made: Target device -> Operating state

The window then opens in which you can set the operating state of SIMOTION. The rotary switch should be set to the RUN position.



V1.2, Item-ID: 31410726

Co

pyr

igh

t

Sie

me

ns

AG

20

12

All

righ

ts r

ese

rve

d

Switches -S1 to -S4 are located on a switchbox that belongs to the Safety training case. The various safety functions are selected using these switches. Switches -S5 to -S10 are located on a switchbox that belongs to the SIMOTION training case. These switches are used to switch axis enable signals, start travel programs, initiate the test function for the safety functions and acknowledge faults.

The Emergency Stop button S1 must be released in order to be able to operate the drives

The axis enable signals for drive 1 (upper/red motor) are switched using switch -S5. The associated travel program can be started and stopped using -S6. For axis 2 (lower/blue motor), -S7 is used to issue the enable signal and the travel program is activated or deactivated with -S8. Pending alarms on the SIMOTION as well as drive alarms can be acknowledged using -S9. The safety alarms are the exception in this case, as they must be acknowledged in a fail-safe fashion using -S4. The test stop to be cyclically executed for the safety functions in the drives as well as the TM54F is activated using -S10.

If the Emergency Stop pushbutton -S1 is pressed, then for drive 1 (upper/red motor), safety function SS1 is initiated; i.e. the drive is braked along the OFF3 ramp and then STO is activated. STO is directly initiated for drive 2 (lower/blue motor); i.e. the drive coasts down. When Emergency Stop is initiated drive 1 comes to a standstill before drive 2.

Drive 1 can be operated when safety door 1 is closed (toggle switch -S2). If -S2 is opened, then safety function SOS is initiated; i.e. SIMOTION brakes the drive down to standstill. The drive standstill position is safely monitored after an user configurable safe timer has expired. If the simulated safety door -S2 is closed again, then the travel program is restarted. In this case, an ON command is not necessary.

Drive 2 can be operated at any speed when safety door 2 is closed (toggle switch -S3). If -S3 is opened, then SIMOTION limits the travel speed to 80% of the speed limit value of stage 1 of safety function SLS. This limit value is monitored by safety function SLS after a defined time has expired. If -S3 is closed again, then SLS is switched-out and the speed limit on the SIMOTION is withdrawn. The drive can now be operated again with the configured speed.



Co

pyr

igh

t

Sie

me

ns

AG

20

12

All

righ

ts r

ese

rve

d

4.2 Summary of the input signals

Digital inputs of the SINAMICS Integrated at the SIMOTION D435

DI0 -S5 Drive 1 Sets / withdraws axis enable signals

DI1 -S6 Drive 1 Starts/stops the travel program

DI2 -S7 Drive 2 Sets / withdraws axis enable signals

DI3 -S8 Drive 2 Starts/stops the travel program

DI6 -S9 Drive 1 / Drive 2 / TM54F / SIMOTION

Acknowledges alarms

DI7 -S10 Drive 1 / Drive 2 / TM54F Initiates a test stop

Fail-safe inputs at the F-DI module

F-DI0 -S1 Emergency Stop button Drive 1: SS1 Drive 2: STO

F-DI1 -S2 Safety door 1 (for drive 1) SOS

F-DI2 -S3 Safety door 2 (for drive 2) SLS

F-DI3 -S4 Acknowledgement button

Fail-safe acknowledgement (drive 1 & 2) and depassivation (all F slaves)

5 Example project


V1.2, Item-ID: 31410726

Co

pyr

igh

t

Sie

me

ns

AG

20

12

All

righ

ts r

ese

rve

d

5 Example project In this chapter, you get to know how the individual components must be parameterized. SIMOTION SCOUT is used as the engineering software for SIMOTION and the SINAMICS Integrated S120. Distributed Safety is a prerequisite for programming the F-CPU.

This chapter will show in steps how the software project belonging to this function example was set-up.

5.1 Passwords

For reasons of simplicity, in the project, a common safety password is used for the program and hardware on the SIMATIC components. Also when configuring the Safety functionality of the SINAMICS components, one password is used for the drives and for the TM54F terminal expansion module.

• Safety password on the F-CPU: "0"

• Safety password on SINAMICS components: "1"

These passwords should be changed for real applications!

5 Example project


Co

pyr

igh

t

Sie

me

ns

AG

20

12

All

righ

ts r

ese

rve

d

5.2 Hardware configuration of the fail-safe control

Description Remark

In the SIMATIC Manager, insert a SIMATIC 300 station into the project.

Completely create and parameterize the station in HW Config. To do this, in the parts list from Chapter 2.1, drag the modules from the catalog window and drop them into the configuration window. Set the address of the DP interface as described in Chapter 4.3.

5 Example project


V1.2, Item-ID: 31410726

Co

pyr

igh

t

Sie

me

ns

AG

20

12

All

righ

ts r

ese

rve

d

Description Remark

Configuring the F CPU In the properties window of the F-CPU, under the Protection tab, activate access protection for the F-CPU and protect using a password. Activate the safety program ("CPU contains safety program").

Configuring the F-DI module. Configure the PROFIsafe address using DIL switches.

Configuring the F-DI module. Configuring F-DI 0 (channels 0, 12)

5 Example project


Co

pyr

igh

t

Sie

me

ns

AG

20

12

All

righ

ts r

ese

rve

d

Description Remark

Configuring the F-DI module. Configuring F-DI 1 (channels 1, 13) Configuring F-DI 2 (channels 2, 14) Configuring F-DI 3 (channels 3, 15) Configuring F-DI 5 (channels 5, 17)

Configuring the F-DO module. Configure the PROFIsafe address using DIL switches.

5 Example project


V1.2, Item-ID: 31410726

Co

pyr

igh

t

Sie

me

ns

AG

20

12

All

righ

ts r

ese

rve

d

Description Remark

Configuring the F-DO module. Configuring F-DO 0 Configuring F-DO 1 Configuring F-DO 2 Configuring F-DO 5 Configuring F-DO 7

Save and compile HW Config. Download HW Config into the F-CPU.

5 Example project


Co

pyr

igh

t

Sie

me

ns

AG

20

12

All

righ

ts r

ese

rve

d

5.3 Programming the fail-safe control

The safety program was deliberately selected to be as simple as possible. In this particular case, the main task of the safety program is to transfer the signals at the F-DIs to the F-DOs. The F-DOs are connected to the F-DIs of the TM54F. The safety functions of the drives are controlled from the TM54F. The blocks required for the safety program are first created.

Caution: In this form, it is not permissible that the program is used for a real application.

You start with the F-call block. This is required to call the safety program. To do this, a function (in this case, FC1) must be inserted into the block folder using the F-call programming language. Cyclic interrupt OB35 is required to cyclically call the safety program.

In this example, the actual safety program is executed in a function block (here, FB1), this means that FB 1 must now be inserted using the F-LAD or F-FBD programming language.

Description Remark

Programming OB35 Calling the safety program

5 Example project


V1.2, Item-ID: 31410726

Co

pyr

igh

t

Sie

me

ns

AG

20

12

All

righ

ts r

ese

rve

d

Description Remark

Programming FB1 Network 1: Activate automatic acknowledgement Network 2: Control signal lamp in -S4.

Programming FB1 Network 3: -S1 (Emergency Stop) is interconnected to F-DO 0. Network 4: -S2 is interconnected, inverted to F-DO 1. Network 5: -S3 is interconnected to F-DO2. Network 6: -S4 is interconnected to F-DO5. Network 7: -S4 is used for acknowledgement.

5 Example project


Co

pyr

igh

t

Sie

me

ns

AG

20

12

All

righ

ts r

ese

rve

d

Description Remark

Creating the new F-Runtime group Here, the safety program (FB1) is assigned to FC1 and the associated I-DB is defined.

Then, generate the safety program and download into the CPU. In addition, download the standard blocks into the F-CPU.

5 Example project


V1.2, Item-ID: 31410726

Co

pyr

igh

t

Sie

me

ns

AG

20

12

All

righ

ts r

ese

rve

d

5.4 Configuring the drives

The basic configuring of SINAMICS Integrated is described in this section. Safety commissioning is discussed in the next point.

5.4.1 Inserting SIMOTION into the existing SIMATIC project

Description Remark

Insert an additional SIMATIC 300 station into the existing object.

5 Example project


Co

pyr

igh

t

Sie

me

ns

AG

20

12

All

righ

ts r

ese

rve

d

Description Remark

Then (if required) rename the station, e.g. as "SIMOTION D"

Select the appropriate SIMOTION component from the catalog and transfer into the work area (drag & drop).

5 Example project


V1.2, Item-ID: 31410726

Co

pyr

igh

t

Sie

me

ns

AG

20

12

All

righ

ts r

ese

rve

d

Description Remark

Configure and network the DP interface of the SIMOTION being used. In the example, DP2 is used (also refer to Section 4.3.2, Bus topology) Then save and compile. Then download HW Config into SIMOTION. HW Config can now be closed.

SIMOTION is now integrated into the existing project.

5 Example project


Co

pyr

igh

t

Sie

me

ns

AG

20

12

All

righ

ts r

ese

rve

d

5.4.2 Basic commissioning of the SINAMICS drives (without safety)

Description Remark

Open SCOUT / STARTER from the SIMATIC project (-> double click on "Commissioning")

Go online

Start the automatic configuration of the drives.

Select the "Servo" control type for both drives.

5 Example project


V1.2, Item-ID: 31410726

Co

pyr

igh

t

Sie

me

ns

AG

20

12

All

righ

ts r

ese

rve

d

Description Remark

Go offline and "Save and Compile"

Post configuration, drive 1 In the Project Navigator for drive 1 (SERVO_02), open the configuration window. "Configure DDS" starts the drive wizard configuration offline Note: Only the steps that require changes from the drive wizard configuration are illustrated below.

Post configuration, drive 1 A signal for "Infeed in operation" (p0864) must be configured. Here, fixed binector 1 is used in the example. Note: In real applications, please do not connect the infeed in operation signal p0864 to 1.

5 Example project


Co

pyr

igh

t

Sie

me

ns

AG

20

12

All

righ

ts r

ese

rve

d

Description Remark

Post configuration, drive 1 The PROFIdrive message frame (p0922) must be set for the drive. Message frame type 105 is used here in the example.

Post configuration, drive 2 Start the Configurator as described for drive 1 (drive 2 is SERVO_03). A signal for "Infeed in operation" (p0864) must be configured. Here, fixed binector 1 is used in the example. Note: In real applications, please do not connect the infeed in operation signal p0864 to 1. Note: Only the steps that require changes from the drive wizard configuration are illustrated below.

5 Example project


V1.2, Item-ID: 31410726

Co

pyr

igh

t

Sie

me

ns

AG

20

12

All

righ

ts r

ese

rve

d

Description Remark

Post configuration, drive 2 The second drive does not have a Drive-CLiQ encoder; the motor must be manually selected. A 1FK7022 - 5AK71 - 1AG0 motor is used in the example.

Post configuration, drive 2 Just like the motor, the encoder must also be manually selected. The is also realized using the type number (MLFB).

5 Example project


Co

pyr

igh

t

Sie

me

ns

AG

20

12

All

righ

ts r

ese

rve

d

Description Remark

Post configuration, drive 2 The PROFIdrive message frame (p0922) must be set for the drive. Message frame type 105 is used here in the example.

The TM54F is automatically created, if for the automatic configuration, it was connected to the D435 via Drive-CLiQ. The topology for the function example can be seen here.

Save the configuration, then go online and download the modified project.

5 Example project


V1.2, Item-ID: 31410726

Co

pyr

igh

t

Sie

me

ns

AG

20

12

All

righ

ts r

ese

rve

d

Description Remark

For the SERVO_02 object, open the "Speed controller" window using the Project Navigator. For both drives, in the example, the speed controller was set as shown here: P gain = 0.1 Nms/rad Reset (integral) time = 10ms

On both drives, several parameters now have to be adapted in the expert list. Adaptation to 230V operation. Configuring the OFF3 ramp.

Interconnect alarm acknowledgement with -S9 (= DI 6 SINAMICS Integrated).

p2101 = r722.6 in the expert list of the CU

Now copy RAM to ROM (on SINAMICS Integrated), download the configuration into the PG and save.

5 Example project


Co

pyr

igh

t

Sie

me

ns

AG

20

12

All

righ

ts r

ese

rve

d

5.5 Parameterizing the safety functions in SINAMICS Integrated

5.5.1 Configuring the message frame

Description Remark

In SCOUT, open the window to configure the PROFIdrive message frame

Insert the message frame extension for the so-called safety data block. 3 words are required to transfer data from the drive to SIMOTION. Insert this message frame extension for both drives. Select message frame type 390 for the CU.

Transfer changes into the HW Config.

The message frame (telegram) configuration should now look like it is shown here (assuming that the same address has been assigned).

Save, go online and download the configuration.

5 Example project


V1.2, Item-ID: 31410726

Co

pyr

igh

t

Sie

me

ns

AG

20

12

All

righ

ts r

ese

rve

d

5.5.2 Configuring the fail-safe TM54F terminal module

Note: The fail-safe terminal module must be configured online.

Description Remark

Open the "Safety Integrated" Window of the TM54F and activate the commissioning mode with "Change settings". The password for the first commissioning is "0".

"Configuration" window The following have to be configured in the example:

Assignment, drives / drive groups

Discrepancy time F-DI

F-DI for fail-safe acknowledgement

Signal source for forced dormant error detection

5 Example project


Co

pyr

igh

t

Sie

me

ns

AG

20

12

All

righ

ts r

ese

rve

d

Description Remark

"Drive group 1" window The following have to be configured in the example:

STO statically inactive

SS1 via F-DI 0

SOS via F-DI 1

SS2 and SLS statically inactive

"Drive group 2" window The following have to be configured in the example:

STO via F-DI 0

SS1, SS2 and SOS statically inactive

SLS via F-DI 2

5 Example project


V1.2, Item-ID: 31410726

Co

pyr

igh

t

Sie

me

ns

AG

20

12

All

righ

ts r

ese

rve

d

Description Remark

"Outputs" window The following have to be configured in the example:

1st signal for F-DO 0 with checkback signal SSM for drive group 1.

2nd signal F-DO 0 with checkback signal SSM for drive group 2.

Copy parameters and then open the dialog box to change the password.

Assign a new password. The value "1" is used in the example.

Activate settings

Execute RAM to ROM backup (start with "OK").

Note: The system can be immediately restarted. However, it is recommended to configure the safety functions of the axes beforehand.

5 Example project


Co

pyr

igh

t

Sie

me

ns

AG

20

12

All

righ

ts r

ese

rve

d

5.5.3 Configuring the safety functions in the drives

Notes:

The safety functions in the drives must be configured online.

Only the windows are described in which parameter changes are required.

For both drives, safety functions STO, SS1, SS2, SOS, SLS and SSM are commissioned so that they are able to be controlled. However, for drive 1, the example is restricted to selecting SS1 and SOS. STO and SLS are controlled for drive 2.

The safety functions are configured precisely the same way for both drives.

Description Remark

Open the "Safety Integrated" window of drive 1 & 2 (SERVO_02 & SERVO_03) and activate the commissioning mode using "Change settings". The default safety password for first commissioning is "0".

5 Example project


V1.2, Item-ID: 31410726

Co

pyr

igh

t

Sie

me

ns

AG

20

12

All

righ

ts r

ese

rve

d

Description Remark

"Safety Integrated" window The following have to be configured in the example:

Select control with "Motion monitoring via TM54F"

Set enable signals to "Enable".

"Configuration" window The following have to be configured in the example: Velocity limit (SSM) with 100 mm/min Signal source, test stop with DI7 of SINAMICS Integrated

5 Example project


Co

pyr

igh

t

Sie

me

ns

AG

20

12

All

righ

ts r

ese

rve

d

Description Remark

"Safe stops" window The following have to be configured in the example: Delay time SS1 -> Pulse suppression = 500msec Delay time selection SOS -> SOS active = 500msec Delay time SS2-> SOS active = 500msec Acceleration monitoring = 500mm/min Shutdown speed SS1 = 100mm/min Standstill tolerance SOS = 2.5mm

"Safely limited speed" window The following have to be configured in the example: n_max for stage 1 = 625mm/min

Copy parameters and then open the dialog box to change the password.

5 Example project


V1.2, Item-ID: 31410726

Co

pyr

igh

t

Sie

me

ns

AG

20

12

All

righ

ts r

ese

rve

d

Description Remark

Assign a new password. The value "1" is used in the example.

Activate settings

Execute RAM to ROM backup. Axial backup is sufficient (start with "Axis parameters"). Note: Only restart the system after configuring has been completed.

For Version V2.5 (SINAMICS Integrated), now for both drives, the clock cycle synchronous internal PROFIBUS still has to be adapted.

1. p10 = 95 2. p9761 = password (in the example "1") 3. p9510 = 1 4. p9700 = 57 hex 5. p9701 = AC hex 6. p10 = 0

Now, copy from RAM to ROM (in SINAMICS Integrated).

Carry out a Power On reset.

Go online, download the configuration into the PG and save.

If you have carried out the safety commissioning for all drives, with Emergency Stop deselected, you can operate the drives from the control panel or SIMOTION.

5 Example project


Co

pyr

igh

t

Sie

me

ns

AG

20

12

All

righ

ts r

ese

rve

d

The use of the safety functions integrated in the drive is selected and these can be activated or deactivated using the operator control elements at the F-CPU.

Only the following messages should be visible.

However, these messages do not influence the functionality described above. They only state that the test stop of the safety functions in the drives is required (A1697) or the forced dormant error detection of the TM54F must be executed (A35014). They are alarms, i.e. the drives can be switched-on and operated.

5.5.4 Configuring the safety data block on the SINAMICS side

The message frame extension for the so-called safety data block was created in Section 5.5.1. Here, the objective is to supply this data block with the required data from SINAMICS Integrated. 6 bytes / 3 words are required. The data is sent from the drive to SIMOTION. No safety signals are sent from SIMOTION to the drive. The user connects up the process data using the BiCo interconnection in SINAMICS. The sequence of the individual signals in the safety data block must not be changed. The checkback signal bits of the drive safety functions are transferred in the first word.

5 Example project


V1.2, Item-ID: 31410726

Co

pyr

igh

t

Sie

me

ns

AG

20

12

All

righ

ts r

ese

rve

d

The following BiCo interconnection must be made for each drive:

The status word is then available at parameter r2089[3].

The effective setpoint speed limiting when selecting SLS (r9733) is transferred as floating-point number in the second and third words.

The interconnection of the safety datablock on the drive side has the following assignment:

The SINAMICS safety status signals are shown in the SIMOTION system variables D435.Axis_1.drivedata.drivesafetyextendedfunctionsinfodata.state.

The value of the setpoint speed limit is shown in D435.Axis_1.drivedata.drivesafetyextendedfunctionsinfodata.safespeedlimit.

Safety status word r2089[3]

effective setpoint speed limiting r9733 [0] = p9531 [x] * p9533 / p9520 (x: active SLS stage)

5 Example project


Co

pyr

igh

t

Sie

me

ns

AG

20

12

All

righ

ts r

ese

rve

d

5.6 SIMOTION

5.6.1 Creating SIMOTION axes

On the SIMOTION side, the axes should be created as follows using the Commissioning Wizards. SERVO_02 is assigned to Axis_1, SERVO_03 is correspondingly connected to Axis_2. The procedure is shown for an axis (Axis_1) as example. The two axes must be configured before the project is downloaded into SIMOTION.

Description Remark

Start the Commissioning Wizards by double-clicking on "Insert Axis" in the Project Navigator. In the example, the first axis is called "Axis_1". "Speed control" and "Positioning" are activated.

The default values are kept. It involves a linear axis with electric drive.

5 Example project


V1.2, Item-ID: 31410726

Co

pyr

igh

t

Sie

me

ns

AG

20

12

All

righ

ts r

ese

rve

d

Description Remark

Also in the "Units" window, in the example, the default values are kept.

Modulo correction is not activated in the example.

5 Example project


Co

pyr

igh

t

Sie

me

ns

AG

20

12

All

righ

ts r

ese

rve

d

Description Remark

The assignment between SIMOTION object (Axis_1) and the SINAMICS axis (SERVO_02) is established in this window. Transfer data from the drive (Normalization speed and maximum speed). Check as to whether PROFIdrive message frame 105 is selected. Open the following window using the "Change PROFIdrive message frame" button.

As the SINAMICS drives have now been configured, here a check is only made as to whether the values were correctly accepted. Generally, changes are not required. It is especially important that you check the message frame extension of 3 words on the input side as this is required to transfer safety data from the drive to SIMOTION.

5 Example project


V1.2, Item-ID: 31410726

Co

pyr

igh

t

Sie

me

ns

AG

20

12

All

righ

ts r

ese

rve

d

Description Remark

The encoder is assigned here. The encoder data can be transferred into the Wizard using the "Data transfer from the drive" button.

The additional encoder data are displayed here. Changes are not required if data transfer from the drive was performed error-free.

5 Example project


Co

pyr

igh

t

Sie

me

ns

AG

20

12

All

righ

ts r

ese

rve

d

Description Remark

Complete the Wizard to create the axis object on SIMOTION.

After completing the Commissioning Wizards, for the example, only a few parameter changes are required. These are shown in the following windows. "Default value" window Set the velocity to a value of 83.33 mm/s (this corresponds to 300 rpm). The value of 333.33mm/s2 is entered for the acceleration and deceleration.

5 Example project


V1.2, Item-ID: 31410726

Co

pyr

igh

t

Sie

me

ns

AG

20

12

All

righ

ts r

ese

rve

d

Description Remark

"Limits" window Set the maximum velocity to a value of 500mm/s.

"Control" window The Servo gain factor is set to a value of 12 1/s in the example.

For the second axis, there are differences in the "Drive assignment" window. Here, enter the logical hardware addresses according to Servo_03.

5 Example project


Co

pyr

igh

t

Sie

me

ns

AG

20

12

All

righ

ts r

ese

rve

d

Description Remark

For the second axis, there are also differences in the "Encoder assignment" window. The encoder data can be transferred into the Wizard using the "Data transfer from the drive" button.

For the second axis, there are also differences in the "Encoder data" window. The additional encoder data are displayed here. Changes are not required if data transfer from the drive was performed error-free.

5 Example project


V1.2, Item-ID: 31410726

Co

pyr

igh

t

Sie

me

ns

AG

20

12

All

righ

ts r

ese

rve

d

Description Remark

As the "Safety alarms" of SIMOTION do not completely comply with the specification, it is recommended that these are hidden for both axes. The window is opened by selecting the TechFault task in the execution system and then pressing the "Alarm configuration" button. In this example, the axis-specific responses are also not based on these alarms. Note: From Version 4.1 SP4 onwards the alarms are working correct. But it is still recommended not to use this alarms for the programming of the axis-specific responses.

After the two axes have been commissioned on the SIMOTION side, the project must be saved and downloaded into SIMOTION (in the Project Navigator, select D435).

If commissioning was carried out as shown here, then all of the settings for the safety block are correct. Now, it only has to be checked that the start address was correctly entered (276 for Axis_1 and 320 for Axis_2)

Axis_1

Axis_2

5 Example project


Co

pyr

igh

t

Sie

me

ns

AG

20

12

All

righ

ts r

ese

rve

d

5.6.2 SIMOTION programs

The programs used in the function example are briefly presented in this section. The program code and a very detailed description will not be given as the program itself has comments.

ST programs include the comments directly in the code. For MMC programs, commented blocks are identified by a green triangle in the upper righthand corner. The comment can be opened by selecting the block and opening a menu with the righthand mouse key. Here, the "Enter comment ..." entry must be selected.

5.6.2.1 IO_ReadWrite (reading in or writing digital I/Os)

The digital inputs of SINAMICS Integrated of the SIMOTION D435 are used to control (open-loop) axis motion. These inputs are read into SIMOTION via the I/O variable "io_cu320_inword". The outputs of SINAMICS integrated can be controlled via the "io_cu320_outword" variable; however, this is not applicable for this example. The inputs are used, e.g. to switch-on the drives, start travel programs, acknowledge faults and to start the test stop or the forced dormant detection.

The two variables are created as shown as follows in the Project Navigator under "I/O".

In this example, SINAMICS Integrated provides the DIs at address 298 (corresponds to PZD 2 of the Control Unit in the send direction). Address 298 should also be used for the outputs (corresponds to PZD 2 of the Control Unit, receive direction).

The "IO_ReadWrite" program was taken from the FAQ with number 29063656. The program parts not required were subsequently removed. Detailed documentation as well as the program code can be downloaded under the following link:


The program is executed in the background task and provides the signals for the program sequence of SIMOTION at the digital inputs of SINAMICS Integrated via the variables mentioned above.

5.6.2.2 Axis_01.mmc_bg_task1 (sequential control system for Axis_1)

The upper drive of the demonstration case (Axis_1; or SERVO_02) is controlled using this program. The program is cyclically processed in the background task and is responsible for switching-in/switching-out the axis enable signals, the fault acknowledgement as well as starting and stopping the travel program "mt_axis_1".

Program functions: -S5 (DI 0) setting or withdrawing enable signals for Axis_1 -S6 (DI 1) starting or stopping the travel program "mt_axis_1". -S9 (DI 6) acknowledging alarms

5.6.2.3 Axis_02.mmc_bg_task2 (sequential control system for Axis_2)

The lower drive of the demonstration case (Axis_1; or SERVO_02) is controlled using this program. The program is cyclically processed in the background task and is responsible for switching-in/switching-out the axis enable signals, the fault acknowledgement as well as starting and stopping the travel program "mt_axis_2".


5 Example project


V1.2, Item-ID: 31410726

Co

pyr

igh

t

Sie

me

ns

AG

20

12

All

righ

ts r

ese

rve

d

Program functions: -S7 (DI 2) setting or withdrawing enable signals for Axis_2 -S8 (DI 3) starting or stopping the travel program "mt_axis_2". -S9 (DI 6) acknowledging alarms

5.6.2.4 Axis_01.mt_axis_1 (travel program for Axis_1)

The travel program comprises 3 travel commands, which are cyclically called from "mmc_bg_task1", as long as a HIGH signal level is present at -S1. This means that after starting the travel program once, "endless motion" of the axis is executed until this is interrupted by selecting a safety function or using a LOW signal level at -S1. This program is executed in MotionTask_3. This task is cyclically started from program "Axis_01.mmc_gb_task1".

5.6.2.5 Axis_02.mt_axis_2 (travel program for Axis_2)

The travel program comprises 3 travel commands, which are cyclically called from "mmc_bg_task2", as long as a HIGH signal level is present at -S3. This means that after starting the travel program once, "endless motion" of the axis is executed until this is interrupted by selecting a safety function or using a LOW signal level at -S3. This program is executed in MotionTask_4. This task is cyclically started from program "Axis_02.mmc_gb_task2".

5.6.2.6 Axis_01.mt_safety_axis_1

The axis-specific responses to selecting or deselecting the safety functions are executed in this program. As several safety functions can be simultaneously active, the priority must first be determined before the axis-specific response can be executed. To do this, the value of a variable is determined, which can then be used to select the response (using a CASE statement). In the example, the subsequently described responses are initiated for the individual functions. After they have been executed, the variables for the state of the individual safety functions (determined in ST_Main.extsafety) as well as also for the priority assignment (determined in Axis_01.mt_safety_1) are reset. This program is executed in MotionTask_6.

STO When selecting STO, no special response is necessary as the impulses are immediately suppressed. When deselecting, a response is also not necessary as after deselecting STO, a new ON command must be set.

SS1 When selecting SS1, the axis must be switched into the follow-up mode and the "Axis_01.mt_axis_1" motion program interrupted. To do this, MotionTask_3 and the actual traversing command are interrupted. When deselecting SS1, MotionTask_3 is reset so that it can be restarted. As SS1 automatically results in an STO, a new ON command is required to restart axis motion.

SS2 When selecting SS2, the axis must be switched into the follow-up mode and the "Axis_01.mt_axis_1" motion program interrupted. To do this, MotionTask_3 and the actual traversing command are interrupted. MotionTask_3 is continued when SS2 is deselected. The motion is automatically continued when deselected. An additional command is not necessary.

SOS When selecting SOS, axis motion is stopped down to standstill in the closed-loop position controlled mode using a STOP command. MotionTask_3 is then interrupted in order to prevent axis travel initiated by the next positioning command. When SOS is deselected, MotionTask_3 is continued again and the next pending

5 Example project


Co

pyr

igh

t

Sie

me

ns

AG

20

12

All

righ

ts r

ese

rve

d

positioning command executed. This means that also here, a command is not necessary to restart axis motion.

SLS When selecting SLS, the maximum permissible velocity (SIMOTION variable: pluslimitsofdynamics.velocity) when positioning is reduced to the value that is transferred from SINAMICS Integrated (via the so-called safety data block) to SIMOTION. Motion is now executed at a reduced velocity. When deselecting SLS, this limit value is reset to the original value.

5.6.2.7 Axis_02.mt_safety_axis_2

See 6.6.2.6, whereby this program is processed in MotionTask_7 and axis motion of Axis_2 is monitored using MotionTask_4.

5.6.2.8 ST_VarGlobal

Variables required to evaluate the safety status word are defined in this ST program.

5.6.2.9 ST_Main

This program comprises the three subprograms "startup", "extsafety" and "techfault".

Note: From Version 4.1 SP4 onwards the SIMOTION safety messages 50201 to 50203 are working correct. In earlier versions the messages do not completely comply with the specification. But we always recommend to evaluate the safety status cyclically and not to use the alarms for the axis-specific response.

"startup" In this program, the axis instances are assigned, i.e. it is defined as to which axis corresponds to which variable. Further, the velocity limit of the SIMOTION configuration project is buffered here in a variable. When selecting SLS, this value is overwritten and when deselected, must be available again. The program is processed in the StartupTask.

"extsafety" The safety status work is evaluated in this program in order to obtain information as to which safety functions are in which state. A distinction is made between the states "selected" (coming event), "active" "deselected" (going event) and "inactive". Depending on this information, the motion task is then started, which includes the program for the axis-specific response to safety functions (MotionTask_6 for Axis_1 and MotionTask_7 for Axis_2).

In the example, the program is processed in the IPO task; however, this is only necessary if the SS2 or SS1 functions are being used. Without these two functions, processing in the Background Task is sufficient. When selecting safety functions SS1 or SS2, the drive immediately decouples itself from the higher-level setpoint of SIMOTION when the function is selected. It is now important to prevent a following error from occuring that would then result in pulse suppression. This is the reason that in these cases, processing must be as fast as possible. The SOS and SLS functions have a configurable timer between selecting and activating; this is the reason that there is more time available for the SIMOTION response.

"Techfault" This involves a dummy program that must be integrated in the TechnologicalFaultTask. If this is missing, then for a TechnologicalFault alarm, the operating state of SIMOTION changes into the "STOP" operating state.

5 Example project


V1.2, Item-ID: 31410726

Co

pyr

igh

t

Sie

me

ns

AG

20

12

All

righ

ts r

ese

rve

d

5.6.2.10 other_MMCs.peripheralfault

This involves a dummy program that must be integrated in the PeripheralFaultTask. If this is missing, then for a Peripheral-Fault alarm, the operating state of the SIMOTION changes into the "STOP" operating state.

5.6.2.11 other_MMCs.executionfault

This involves a dummy program that must be integrated in the ExecutionFaultTask . If this is missing, then for a Execution-Fault alarm, the operating state of the SIMOTION changes into the "STOP" operating state.

5 Example project


Co

pyr

igh

t

Sie

me

ns

AG

20

12

All

righ

ts r

ese

rve

d

5.6.3 Configuration of the execution system

The various SIMOTION programs must now be assigned to various tasks. The function example is based on the following configuration.

5 Example project


V1.2, Item-ID: 31410726

Co

pyr

igh

t

Sie

me

ns

AG

20

12

All

righ

ts r

ese

rve

d

5.6.4 SIMOTION messages

5.6.4.1 Safety message

On the SIMOTION side, there are 3 messages for the extended safety functions.

50201: Safety alarm in the drive

50202: Drive starts Safety Integrated Extended function

50203: Drive completes Safety Integrated Extended function

Presently, these messages should still not be used for configuring the axis-specific responses of SIMOTION.

5.6.4.2 Other messages

When selecting the different safety functions, additional messages are displayed. These are expected and do not represent incorrect behavior.

20005: Device type: X, log. address: Y faulted. This fault also occurs when selecting STO and SS1 and indicates that the drive has shut itself down.

30002: Command aborted (reason: X, Command type: Y) This message should also be monitored when selecting STO and SS1 as well as when "stopping" positioning by shutting down -S6 or S8. The reason for this message is that the actual positioning command was interrupted before or during processing.

40002: Programmed velocity is limited The fault occurs when SLS is selected if the configured velocity lies above the limit for SLS.

40005: Missing enable signals(s) (Parameter1: X) and/or incorrect mode (Parameter2: Y) The fault occurs when STO is selected and means that for a pending motion command, the axis enable signals are missing.

5.7 Download of the project example

Up until now, the configuration of the function example was described step-by-step. The following steps should now be followed if the project example is to be directly downloaded into the hardware.

To start, all of the components (S7-F-CPU, SIMOTION and SINAMICS Integrated) should be generally reset or reset to the factory setting.

mk:@MSITStore:C:\PROGRA~1\Siemens\Step7\u7umc\help\simotion\to_tp\04_10\u7al04hat08a.chm::/html/___Befehlstyp.de.htm

5 Example project


Co

pyr

igh

t

Sie

me

ns

AG

20

12

All

righ

ts r

ese

rve

d

5.7.1 Downloding the S7-F-CPU project configuration

To start, the HW configuration of the S7-F-CPU must be downloaded. The HW configuration is opened by double-clicking on "Hardware".

Depending on the default values and the previous configuration on the F-CPU side, if required, the baud rate of the PC/PG interface must be adapted to download the hardware configuration of the F-CPU. If SIMOTION and the F-CPU have the same PROFIBUS address (2 is the default value for both), then it is only necessary to first connect the F-CPU with the PC/PG in order to download the HW configuration. Therefore, it is only necessary to change the bus address and the baud rate to the values specified in Section 3.3.1. SIMOTION can now also be reintegrated into the PROFIBUS network. The baud rate must be again changed according to 3.3.1 before you can go online.

Note: If a safety program existed on the CPU beforehand, then this is password-protected. This must be known for the download. If it is not known, then the memory card must be deleted using a suitable device (e.g. SIEMENS PG). If the card is deleted or formatted using a card reader, the card will be destroyed.

After the HW configuration has been downloaded, the program blocks must be downloaded to the F-CPU.

The window to download the safety functions is first opened using the "yellow" button in the function bar. The download is then initiated from this window using the "Download" button. The remaining (non-safety-oriented) blocks are then downloaded normally.

5 Example project


V1.2, Item-ID: 31410726

Co

pyr

igh

t

Sie

me

ns

AG

20

12

All

righ

ts r

ese

rve

d

5.7.2 Downloading the project configuration of SIMOTION and SINAMICS Integrated

Also here, the HW configuration of the SIMOTION should be downloaded first. Without this step, generally it would not be possible to obtain an online connection to SINAMICS Integrated. The HW configuration is opened by double-clicking on "Hardware".

After the download, SCOUT is opened from the SIMATIC project (double-click on "Commissioning").

The complete configuration of SIMOTION and SINAMICS Integrated can now be downloaded from here.

After the download, various safety faults are present as the serial numbers of the encoder modules, motor modules and the TM54F do not match those of the devices that were used to generate the project example. Now, for each series commissioning, the new serial numbers must be transferred into the safety configuring. This is done using "Confirm HW replacement" The simplest way is to open the safety screen form on both drives and there, press the "Confirm HW replacement" button.

5 Example project


Co

pyr

igh

t

Sie

me

ns

AG

20

12

All

righ

ts r

ese

rve

d

This function does not exist as button for the TM54F. Here, the safety screen should also be opened and the commissioning mode selected using the "Change settings" button and exited again using "Activate settings". To do this, the safety password ("1") must be entered.

The backup procedure from RAM to ROM must then be initiated for SINAMICS Integrated and a restart carried out (Power On reset).

6 Contact


V1.2, Item-ID: 31410726

Co

pyr

igh

t

Sie

me

ns

AG

20

12

All

righ

ts r

ese

rve

d

5.8 Acceptance test

To verify safety-oriented parameters, an acceptance test must be performed after the machine has been commissioned for the first time and also after changes are made to safety-oriented parameters. The acceptance test must be appropriately documented. The acceptance reports must be adequately stored and archived.

The acceptance test must be carried out after parameterization has been completed and a Power On reset.

Information about the acceptance test, the acceptance report and an example of an appropriate acceptance report is provided in the "Function Manual SINAMICS S120 Safety Integrated" (FHS) in the Chapter, Acceptance test and acceptance report.

6 Contact

Siemens AG

Industry Sector I DT MC PMA APC Frauenauracher Straße 80 D - 91056 Erlangen mailto: [email protected]

mailto:[email protected]?subject=MC-FE-I-007-V12-DE%20,%20Beitrags-ID:%2031410726

Documents

Controlling a D435 via TM54F and F-CPU Function Example No