Content      ..     84      85      86      87     ..

SINUMERIK 840D sl. Service - Configuring Commissioning. Manual (2011-2020) - page 86

Configuring screen objects

9.6 Screen object Application View

9.6

Screen object Application View

9.6.1

Properties and configuration

The "Application view" screen object permits the positioning of a frameless client area within

WinCC RT Advanced, in which an external application is displayed during runtime. The

application to be integrated must meet the requirements (Page 146) and be tested during

runtime based on the configuration to ensure that it does not lead to any unintended behavior.

Configuration

You will find the screen object on the task card "Tools" below "Controls".

Figure 9-6

Inserting a screen object with drag and drop

● You can configure the application view several times within one screen.

● Application views must not overlap. If an "Extend[...]" area is parameterized, it must also be

taken into consideration during positioning.

● Different application views are not allowed to use the same XML description file, although

the same application can be specified in different XML description files.

SINUMERIK Integrate Create MyHMI /WinCC V16

Configuration Manual, 12/2019, 6FC5397-8FP40-0BA2

143

Configuring screen objects

9.6 Screen object Application View

● Applications that block or filter mouse or keyboard inputs or demand such inputs exclusively

for themselves.

● Applications that prevent the focus of the operation from being forwarded.

Such applications must not be used in conjunction with the application view.

Optimization of applications to be integrated

If you develop a new application - or adapt an application - to integrate this in WinCC RT, you

should observe the following notes:

Element or property

Instructions to be observed

Main window (top-level window)

The application should only use one single main window (top-level window).

If the application opens several main windows, an option for switching between

them must be available within the application. Switching between different win-

dows using Ctrl + TAB or Alt + TAB can be inhibited by project settings.

Window size or scaling

The application should be infinitely and completely scalable, i.e. when changing

the size of the main window, subordinate elements should be considered (e.g.

additional windows, menus, toolbars).

The size of message dialogs, modal dialogs etc. must match the smallest config-

ured application view.

Window title

If you would like to use the "TitlePattern" setting when configuring the application

view in order to assign different windows to your application, the window title must

be unambiguously named in order for it to be assigned.

Use of standard dialogs or dialog classes

In certain circumstances, the use of standard dialogs can enable the user to exe-

cute unforeseeable actions. For example, a user could execute any applications

(e.g. "Open file" or "Print")

by means of an "Open file" dialog. Actions of this kind cannot be monitored by the

application view or the WinCC RT Advanced.

Standard dialogs can demand a certain minimum size. Check whether this mini-

mum size matches the size of your application or that of the configured application

view.

Opening of files by the application

The active directory of the WinCC RT Advanced is the directory in which the fwc-

file is located. Remember this when opening files without a path specification.

(e.g. configuration files)

Window designs or skins

Rounded corners and/or shadows on the window frame can result in small areas

of the desktop becoming visible and operable. Therefore do not use any designs/

skins of this type.

Controlled termination of the application

The application and any associated processes must require no more than 10

seconds (parameterizable) in which to close in a controlled manner (Windows API

function "WM_CLOSE"). If this waiting time is not set or is exceeded, all associated

processes are terminated by the WinCC RT Advanced using the Windows API

function "TerminateProcess".

It is thus possible that it cannot wait for "Save" dialogs before terminating the

application.

Several instances of the same applica-

If several instances of the same application are to be active at the same time, you

tion

must ensure that no conflicts between process or Windows names occur.

SINUMERIK Integrate Create MyHMI /WinCC V16

Configuration Manual, 12/2019, 6FC5397-8FP40-0BA2

147

Configuring screen objects

9.6 Screen object Application View

9.6.5

Operation during runtime

In the screen object "Application view", the configured external application is displayed during

runtime and can be operated accordingly.

Figure 9-7

Application view at runtime - Example using embedded Windows Editor with hidden title and menu bars

Wherever possible, the window size of the application is automatically adapted to the

application view. Automatic positioning excludes context menus and windows whose change

of position and size are prevented by the application itself.

If problems are detected by the application view, this is indicated in the application view (see

table).

Only the message "No application window available" can intentionally be displayed to the

operator.

● The same application should be used in different application views and is currently being

displayed in another.

● The application has been minimized and can be maximized by the operator by clicking or

tapping on the message.

SINUMERIK Integrate Create MyHMI /WinCC V16

Configuration Manual, 12/2019, 6FC5397-8FP40-0BA2

149

Configuring screen objects

9.6 Screen object Application View

Troubleshooting

Problem

Possible cause

Error message "Application has been closed."

The application has been closed by the user or has crashed.

Error message "XML file is invalid."

XML file is damaged or the XML content or parameterization

is invalid.

Error message "Application could not be started."

The EXE file of the application could not be found or is invalid

or damaged.

The application is used in several application views and the

parameters for "DestroyAppAtScreenChange" (Page 144)

are incorrectly set.

Application view does not display the application or is dis-

The application is used in several application views and the

played in black.

parameters for "DestroyAppAtScreenChange" (Page 144)

are incorrectly set.

Content of the application view is flickering or appears and

disappears in an uncontrolled manner.

The application view displays windows that do not belong to

The runtime parameters (Page 144) are incorrectly set.

the embedded application.

The "TitlePattern" parameter (Page 144) is activated and in-

correctly set.

The application view does not display all (required) windows

The "TitlePattern" parameter (Page 144) is activated and in-

of the application.

correctly set.

The window is minimized.

Error message "No application window available".

The "TitlePattern" parameter (Page 144) is activated and in-

correctly set.

The application is used in several application views and is

currently being displayed in another.

The window is minimized.

Parts of the application are inadvertently cut off or are located

The parameters for "Extend[...]" (Page 144) are incorrectly

outside the application view.

set.

SINUMERIK Integrate Create MyHMI /WinCC V16

150

Configuration Manual, 12/2019, 6FC5397-8FP40-0BA2

Configuring screen objects

9.7 Image object, Fanuc SDF display

9.7

Image object, Fanuc SDF display

9.7.1

Properties and configuration

Screen object "Fanuc SDF display" allows a client area to be located within the WinCC

Runtime, in which, during the runtime, the external "FANUC SDF" application can be displayed.

This means that the HMI of a FANUC control system can be displayed and used within a user-

defined WinCC Runtime.

Configuration

You will find the screen object on the task card "Tools" below "Controls".

Figure 9-8

Insert FANUC SDF view

Note

Requirements for display during runtime

In order to guarantee that the Fanuc SDF view functions correctly during runtime, certain

conditions must be met (Page 152).

SINUMERIK Integrate Create MyHMI /WinCC V16

Configuration Manual, 12/2019, 6FC5397-8FP40-0BA2

151

Configuring screen objects

9.8 Changing client area screen objects using runtime scripting

9.8

Changing client area screen objects using runtime scripting

The following screen objects differ regarding the options available using runtime scripting. For

example, because the objects within the WinCC runtime only provide client areas for external

applications.

● NC operating display

● Fanuc SDF display

● Application display

● NC keyboard display

For these objects, it can make sense to use runtime scripting, as especially the "Visible" and

"Position" properties of these screen objects can only be set using scripting - and not using

animation.

The following properties can be parameterized using runtime scripting:

Table 9-4

Properties that can be changed using runtime scripting

Property

Type

Access

Example

Enabled

Bool

True

Height

Scalar (int)

Read only

480

Left

Scalar (int)

345

Object name

String

Read only

Application_View_1

Top

Scalar (int)

160

Type

String

Read only

HMICameraView

Visible

bool

True

Width

Scalar (int)

Read only

640

Figure 9-9

Adapting the properties of the screen object application display using runtime scripting

SINUMERIK Integrate Create MyHMI /WinCC V16

154

Configuration Manual, 12/2019, 6FC5397-8FP40-0BA2

Using system functions

10.1 Configuring SINUMERIK PI services as system functions

Further information

Information about general functions for WinCC can be found in the information system. This

contains not only detailed descriptions, but also Tooltips directly for the individual functions.

10.1.2

Functions for the NC part program view screen object

Introduction

In order also to be able to operate the "NC part program view" screen object externally or,

depending on the functionality, to allocate an appropriate authorization, command buttons can

be hidden in the screen object during configuration. The required functionality can be triggered

via softkeys with various authorization levels.

Procedure

To add a new function, proceed as follows:

1. Open the editor for screens.

2. Select the "NC part program view" screen object.

3. In the inspector window, switch to "Properties > Events".

4. To add a new function, select it from the "<Add function>" dropdown list in the "keyboard

operation for screen objects" directory.

Figure 10-1

"Keyboard operation for screen objects" functions

SINUMERIK Integrate Create MyHMI /WinCC V16

156

Configuration Manual, 12/2019, 6FC5397-8FP40-0BA2

Using system functions

10.1 Configuring SINUMERIK PI services as system functions

Functions available for the "NC part program view" screen object

The following functions influence the "NC part program view" screen object:

Table 10-1

Functions for the NC part program screen object

Function

Meaning

ScreenObjectCursorDown

Performs the <down> key function on the the

specified screen object.

ScreenObjectCursorUp

Performs the <up> key function on the the speci-

fied screen object.

ScreenObjectPageDown

Performs the <page down> key function on the the

specified screen object.

ScreenObjectPageUp

Performs the <page up> key function on the the

specified screen object.

PartProgramListDirDown

Navigate and select in the list directory.

PartProgramListDirUp

Navigate and select in the list directory.

PartProgramListRefresh

Update directories in the list box

PartProgramListSelectNCPartProgram

Open the selected part program for editing on the

NC.

10.1.3

Function for the current block display

The PrepareActualNCBlockForDisplay function is used to monitor the execution of the

traversing blocks of an NC traversing program on the HMI device. This function is used to save

the current, previous and next traversing block of an NC part program currently being

processed in a channel from the NC to local variables.

Procedure on the HMI device

● The PrepareActualNCBlockForDisplay function starts when a screen is opened.

● A non-configured NC tag block is activated with the configured cycle.

● On each cyclic reading operation of the NC tag block, the tag block is divided into three parts

and stored in the local tags of the previous, current and subsequent set.

● The local variables can be displayed on the screen as outputs.

SINUMERIK Integrate Create MyHMI /WinCC V16

Configuration Manual, 12/2019, 6FC5397-8FP40-0BA2

157

Using system functions

10.1 Configuring SINUMERIK PI services as system functions

Procedure

1. Select the function in the screen editor for "Select screen" (the screen is selected) from

"Events > Structured > Add function" in the "SINUMERIK" directory.

Figure 10-2

Current block display

2. Specify three local tags of type String of length 66.

3. Within a screen, create three output fields each with one of these tags.

4. Now configure the PrepareActualNCBlockForDisplay function as the open screen trigger.

5. Then specify the corresponding NC, the channel from which the current block is to be read,

the cycle, and the three local string tags as parameters for this function.

Parameter

Meaning

Data type

Connection

Name of the connection to the NC.

ASCII characters

Can be viewed under: "PC-Sys-

tem_1 > HMI_RT_1 > Connec-

tions".

Channel

Channel from which the program

Constant or variable

is to be read; 1 - max. 10

Cycles (100 ms)

Update time as a multiple of 100

Constant

ms: 1 - 600 (equal to 100 millisec-

onds - 1 minute)

Previous block (output)

Local tag for the traversing block

String tag

that precedes the current travers-

ing block

Current block (output)

Local tag for the current traversing

String tag

block

Next block (output)

Local tag for the traversing block

String tag

that follows the current block

10.1.4

Start/stop PLC by means of a function

You can set a SINUMERIK PLC to RUN or STOP mode by means of a function.

SINUMERIK Integrate Create MyHMI /WinCC V16

158

Configuration Manual, 12/2019, 6FC5397-8FP40-0BA2

Using system functions

10.1 Configuring SINUMERIK PI services as system functions

Procedure

To add a new function, proceed as follows:

1. Open the editor for screens.

2. In the Inspector window, switch to "Properties > Events".

3. To add a new function, select it from the "<Add function>" drop-down list in the

"SINUMERIK" directory.

Figure 10-3

System functions

The following functions are available:

- LogoffNC (Page 160)

- ChangeNCPassword (Page 161)

- LogonNC (Page 161)

- ConfigureNCMachineData (Page 162)

- ResetNC (Page 162)

- AcknowledgeNCCancelAlarms (Page 162)

- SetNCUserFrame (Page 162)

- StartNCPIService (Page 163)

- SelectNCPartProgram (Page 164)

10.1.5.2

LogoffNC

Description

This function clears the NC password. Following this, the keylock switch acts.

SINUMERIK Integrate Create MyHMI /WinCC V16

160

Configuration Manual, 12/2019, 6FC5397-8FP40-0BA2

Using system functions

10.2 Configuring FANUC system functions

10.2

Configuring FANUC system functions

10.2.1

Configuring function keys by means of system functions

The system function "SwitchFanucCNCScreen" is available in WinCC for the FANUC CNC/

PMC communication driver. This enables you to configure the special FANUC function keys in

WinCC screens, for example as individual command buttons.

Figure 10-4

Function keys as command buttons

Description

With this function, a request is made via the FANUC CNC/PMC connection to switch to a

specific screen of the FANUC CNC/PMC user interface.

Parameters

Meaning

Connection

Name of the connection that has been configured by means of the FANUC CNC/

PMC communication driver.

Screen ID

ID of the FANUC screen to which you wish to switch:

● Position

● Program

● Offset

● System

● Message

● Graph

● Custom

● Custom2

10.2.2

Function when restarting

Description

The "ResetFanucCNC" function externally restarts the FANUC control system. For example,

you can configure this function as event, type "Click" for a button.

Parameter

Meaning

Connection

Name of the connection to the FANUC control system. Only

connections via the "FANUC CNC/PMC" communication driv-

er are permissible.

SINUMERIK Integrate Create MyHMI /WinCC V16

166

Configuration Manual, 12/2019, 6FC5397-8FP40-0BA2

Loading and linking the configuration

12.2 Integrating WinCC Runtime into the OEMFrame area of SINUMERIK Operate

Procedure

To integrate the Runtime in SINUMERIK Operate, follow these steps:

1. On the PC system, click in the Windows Start menu on "Start > Siemens Automation >

SINUMERIK > Integration Sinumerik Operate English Tool".

The "Integration SINUMERIK Operate" dialog opens.

Figure 12-1

Example of a completed "Integration SINUMERIK Operate" dialog

2. Make the required settings:

Setting

Procedure

Softkey position

The drop-down list shows the currently free, assignable horizontal softkeys.

Select an available softkey (default softkey = 7).

Project file

The TIA Portal configuration file of the WinCC RT Advanced can be entered by

means of the input box. The configuration file is displayed with the "Browse"

button.

WinCC RT as

Here you specify if the WinCC Runtime application covers up SINUMERIK

power up applica-

Operate when it starts up.

tion

● NO: SINUMERIK Operate is not covered.

● YES: SINUMERIK Operate is covered.

SINUMERIK HMI

Here you can define whether the header of SINUMERIK Operate (display of the

header visible

operating area, operating mode, alarms, etc.) is to be visible for the WinCC

application.

● NO: Header is not visible.

● YES: Header is visible.

If YES is entered here, the location of the header on the configuration interface

of each WinCC screen must be kept free for this. See: Configuration of the

screen size (PC systems) (Page 68)

SINUMERIK Integrate Create MyHMI /WinCC V16

Configuration Manual, 12/2019, 6FC5397-8FP40-0BA2

179

Appendix

13

13.1

SINUMERIK functions, which can be triggered using certain events of

the WinCC RT Advanced

Introduction

The following tables list the functions for the relevant WinCC objects and their associated

events that are used for SINUMERIK with SIMATIC Panels. These functions are indicated by

a crpss in the table.

In the following five tables, these are the WinCC objects

● Tags

● Function keys

● Buttons

● Screen

● Alarms

● OCX

● Script

● Scheduler

SINUMERIK functions, which can be triggered using certain events of the WinCC RT Advanced, part 1

Object

Variables

Softkey

Global

Local

Event

Value

Upper limit ex-

Lower limit

Release

Press

Release

Press

changed

ceeded

fallen below

Functions

SetS7OperatingMode

X

X

X

X

X

X

X

AcknowledgeNCCancelA-

X

X

X

X

X

X

X

larms

LogonNC

X

X

X

X

X

X

X

LogoffNC

X

X

X

X

X

X

X

ChangeNCPassword

X

X

X

X

X

X

X

SetNCUserFrame

X

X

X

X

X

X

X

SelectNCPartProgram

X

X

X

X

X

X

X

PrepareActualNCBlockFor-

Display

StartNCPIService

X

X

X

X

X

X

X

ResetNC

X

X

X

X

X

X

X

SINUMERIK Integrate Create MyHMI /WinCC V16

Configuration Manual, 12/2019, 6FC5397-8FP40-0BA2

181

Appendix

13.1 SINUMERIK functions, which can be triggered using certain events of the WinCC RT Advanced

Object

Variables

Softkey

Global

Local

Event

Value

Upper limit ex-

Lower limit

Release

Press

Release

Press

changed

ceeded

fallen below

Functions

ConfigureNCMachineData

X

X

X

X

X

X

X

ScreenObjectCursorUp

X

X

X

X

ScreenObjectCursorDown

X

X

X

X

ScreenObjectPageUp

X

X

X

X

ScreenObjectPageDown

X

X

X

X

PartProgramListSelectNC-

X

X

X

X

PartProgram

PartProgramListDirUp

X

X

X

X

PartProgramListDirDown

X

X

X

X

PartProgramListRefresh

X

X

X

X

SINUMERIK functions, which can be triggered using certain events of the WinCC RT Advanced, part 2

Object

Command buttons (system key)

Global

Local

Event

Release

Press

Release

Press

Function

SetS7OperatingMode

X

X

X

X

AcknowledgeNCCancelAlarms

X

X

X

X

LogonNC

X

X

X

X

LogoffNC

X

X

X

X

ChangeNCPassword

X

X

X

X

SetNCUserFrame

X

X

X

X

SelectNCPartProgram

X

X

X

X

StartNCPIService

X

X

X

X

ResetNC

X

X

X

X

ConfigureNCMachineData

X

X

X

X

SINUMERIK Integrate Create MyHMI /WinCC V16

182

Configuration Manual, 12/2019, 6FC5397-8FP40-0BA2

Appendix

13.1 SINUMERIK functions, which can be triggered using certain events of the WinCC RT Advanced

SINUMERIK functions, which can be triggered using certain events of the WinCC RT Advanced, part 3

Object

Screen

Messages

Alarm

Event

Events

Built up

Discon-

Activate

Clear

Acknowledge

Edit

Activate

Clear

Edit

nected

Functions

LogonNC

X

X

LogoffNC

X

X

ChangeNCPassword

X

X

SetNCUserFrame

X

X

X

X

X

X

X

X

X

SelectNCPartPro-

X

X

X

X

X

X

X

X

X

gram

PrepareActualNC-

X

BlockForDisplay

StartNCPIService

X

X

X

X

X

X

X

X

X

ResetNC

X

X

X

X

X

X

X

X

X

ConfigureNCMachi-

X

X

X

X

X

X

X

X

X

neData

ScreenObjectCursor-

X

X

Up

ScreenObjectCursor-

X

X

Down

ScreenObjectPage-

X

X

Up

ScreenObjectPage-

X

X

Down

PartProgramListSe-

X

X

lectNCPartProgram

PartProgramListDir-

X

X

Up

PartProgramListDir-

X

X

Down

PartProgramListRe-

X

X

fresh

SINUMERIK functions, which can be triggered using certain events of the WinCC RT Advanced, part 4

Objects

OCX

Script

OCX (ScreenItem)

InScripts

Event

Press, Release, Click,

Activate

Deactivate

Change (or Toggle when

used on a Switch), Switch-

On, SwitchOff

Functions

SetS7OperatingMode

X

X

X

X

AcknowledgeNCCancelAlarms

X

X

X

X

SINUMERIK Integrate Create MyHMI /WinCC V16

Configuration Manual, 12/2019, 6FC5397-8FP40-0BA2

183

Appendix

13.1 SINUMERIK functions, which can be triggered using certain events of the WinCC RT Advanced

Objects

OCX

Script

OCX (ScreenItem)

InScripts

Event

Press, Release, Click,

Activate

Deactivate

Change (or Toggle when

used on a Switch), Switch-

On, SwitchOff

Functions

LogonNC

X

X

X

X

LogoffNC

X

X

X

X

ChangeNCPassword

X

X

X

X

SetNCUserFrame

X

X

X

X

SelectNCPartProgram

X

X

X

X

PrepareActualNCBlockForDisplay

StartNCPIService

X

X

X

X

ResetNC

X

X

X

X

ConfigureNCMachineData

X

X

X

X

ScreenObjectCursorUp

X

X

X

ScreenObjectCursorDown

X

X

X

ScreenObjectPageUp

X

X

X

ScreenObjectPageDown

X

X

X

PartProgramListSelectNCPartProgram

X

X

X

PartProgramListDirUp

X

X

X

PartProgramListDirDown

X

X

X

PartProgramListRefresh

X

X

X

SINUMERIK functions, which can be triggered using certain events of the WinCC RT Advanced, part 5

Object

Scheduler

Event

ExpireTime

ScreenChange

ChangeUser

AlarmOverflowBuffer

StartUp

Shut-

Down

Function

LogoffNC

X

X

SINUMERIK Integrate Create MyHMI /WinCC V16

184

Configuration Manual, 12/2019, 6FC5397-8FP40-0BA2

Fundamentals

3.3 Safety functions integrated in the drive

3.3

Safety functions integrated in the drive

SINUMERIK Safety Integrated plus supports, through SINAMICS Integrated (as

subcomponent of the NCU), the SINAMICS Safety Integrated Functions (Page 79). These

safety functions integrated in the drive can communicate with the process via safety-relevant

input/output signals. They can be implemented for each individual axis and spindle.

Differentiation by scope

Based on the scope of the available functions and the licensing required, a distinction is made

between "Basic Functions" and "Extended Functions":

● Safety Integrated Basic Functions are always included as part of the standard scope of the

drive, and can be used without an additional license. These functions do not require an

encoder and/or do not place any special requirements on the encoder used.

● Safety Integrated Extended Functions require an additional license (Page 39). Extended

Functions with encoder require a safety-relevant encoder concept (Page 183).

Differentiation by application

Based on the specific application, safety functions integrated in the drive can be split up into

three main classes:

● Functions for safely stopping the drive, without having to disconnect the power from the line

supply

● Functions for safely monitoring the motion of a drive

● Functions for safely monitoring the position of a drive

Listing of all functions by application

Table 3-1

Functions for safely stopping the drive, without having to disconnect the power from the line supply

Safety Function

Scope

Brief description

Configuration via

Safe Torque Off

Extended

Safe Torque Off is a safety function that prevents the drive from re-

STO Extended

(STO)

starting unexpectedly in accordance with EN- 60204-1. STO prevents

(Page 260)

the supply of power to the motor, which can produce a torque. This is

Basic

STO/SS1 Basic

equivalent to stop Category 0.

(Page 259)

Safe Stop 1 (SS1,

Basic

Safe Stop 1 is based on the "Safe Torque Off" function. This means

time-controlled)

that a Category 1 stop in accordance with EN 60204-1 can be imple-

mented.

Safe Stop 1 (SS1,

Extended

SS1 Extended

time and accelera-

(Page 263)

tion controlled)

Safe Brake Control

Basic

Safe Brake Control is used to safely control a holding brake.^{1) 2)}

SBC (Page 262)

(SBC)

Extended

Safe Brake Test

Extended

The diagnostic function "Safe Brake Test" function (SBT) checks the

SBT (Page 281)

(SBT)

required holding torque of a brake (operating or holding brake). ³⁾

The "Safe Brake Test" (SBT) diagnostic function is suitable for safety

functions up to Category 2 according to ISO 13849-1.

Safe Stop 2 (SS2)

Extended

Safe Stop 2 is used to safely brake the motor with a subsequent tran-

SS2 (Page 104)

sition into the "Safe Operating Stop" state (SOS). This means that a

Category 2 stop in accordance with EN 60204-1 can be implemented.

Safety Integrated plus

Commissioning Manual, 12/2019, 6FC5397-1FP40-6BA3

25

Fundamentals

3.3 Safety functions integrated in the drive

Safety Function

Scope

Brief description

Configuration via

Safe Stop 2 with ex-

Extended

The 'Safe Stop 2 with external stop' (SS2E) safety function is used to

SS2E (Page 107)

ternal stop (SS2E)

brake the motor safely. The drive does not automatically brake the

motor, but instead follows the specified speed setpoint.

Safe Stop 2 Exten-

Extended

The "Safe Stop 2 Extended Stop and Retract (SS2ESR)" safety func-

SS2ESR

ded Stop and Re-

tion is used to brake the motor safely. The drive does not automatically

(Page 111)

tract (SS2ESR)

brake the motor, but instead follows the specified speed setpoint. This

can also result in fast retraction motion. During the delay time p9554,

the brake ramp (SBR) and the acceleration (SAM) are not monitored,

and there is no standstill detection. SOS becomes active after delay

time p9554 has expired.

Safe Operating

Extended

Safe Operating Stop is used to protect against unintentional move-

SOS (Page 114)

Stop (SOS)

ment. The drive is in closed-loop control mode and is not disconnected

from the power supply.

1)

Note regarding Power/Motor Modules in the chassis format:

For the chassis format, SBC is only supported by Power/Motor Modules with the number 3 or higher at the last position of

the Article number. For this design, a Safe Brake Adapter is also required.

2)

Note regarding Power/Motor Modules in blocksize format:

blocksize Power Modules additionally require a Safe Brake Relay for this function.

3)

The Safe Brake Test is purely a diagnostic function, but for organizational reasons is included in the list of Safety Integrated

Extended Functions.

Table 3-2

Functions for safely monitoring the motion of a drive

Safety Function

Scope

Brief description

Configuration via

Safely-Limited

Extended

Safely-Limited Speed monitors that the drive does not exceed a preset

SLS (Page 271)

Speed (SLS)

speed/velocity limit.

Safely-Limited Ac-

Extended

Safely-Limited Acceleration monitors (the same as SLS) the acceler-

SLA (Page 175)

celeration (SLA)

ation, and intervenes when a limit value is violated.

Safe Speed Moni-

Extended

Safe Speed Monitor is used for safely identifying when a speed limit is

SSM (Page 274)

tor (SSM)

fallen below in both directions of motion, e.g. to identify zero speed. A

failsafe output signal is available for further processing.

Safe Direction

Extended

Safe Direction is used to safely monitor the direction of motion.

SDI (Page 276)

(SDI)

Table 3-3

Functions for safely monitoring the position of a drive

Safety Function

Scope

Brief description

Configuration via

Safely-Limited Po-

Exten-

Safely-Limited Position ensures that a freely definable traversing

SLP/SP (Page 278)

sition (SLP)

ded¹⁾

range is not left.

Transferring safe

Exten-

The "Transfer safe position values (SP)" function enables you to trans-

position values

ded¹⁾

fer a safe position to a higher-level control via PROFIsafe.

(SP)

Safe cams (SCA)

Exten-

Safe electronic cams enable a secure, axis-specific range detection or

SCA (Page 284)

ded¹⁾

a work zone / protection zone delimitation.

1)

For SINAMICS, these Safety Functions are called "Advanced".

Safety Integrated plus

26

Commissioning Manual, 12/2019, 6FC5397-1FP40-6BA3

Fundamentals

3.5 Safety-relevant processing using NCU components

Details on internal processing of safety-related communication

1&8

) ',

&8

) '2

,I UHTXLUHG DGGLWLRQDO

) 3/&

GLVWULEXWHG , 2 V\VWHPV

IDLOVDIH '3 VWDQGDUG VODYHV

6DIHW\

3$(

SURJUDP

3$$

352),1(7 352),VDIH

'%

'%

352),%86 352),VDIH

6,& 6&&

7UDQVIHU

352),VDIH

1&.

7UDQVIHU

$;

$;

6,& 6&&

7UDQVIHU

352),VDIH

'5,9(

352),VDIH

$;

$;

00

$;

,I UHTXLUHG DGGLWLRQDO GULYHV

0RQLWRULQJ

'5,9( &/L4

$;

$;

Figure 3-1

Component diagram for processing safety-relevant information and data

Table 3-4

Subcomponents of the NCU

F-PLC

● Processing safety-relevant internal and external signals in the safety-relevant

PROFIsafe host

user program (safety program)

See: Safety program of the F-PLC (Page 45)

● Processing status and control signals (SIC/SCC) via the corresponding axis

DB (axis1 [DB31] ... axis 31 [DB61])

See: PLC user interface (DB3x) (Page 206), SIC/SCC (Page 205)

NC

● Transfers status and control information (SIC/SCC, axis DB) between the F-

PLC and DRIVE

● Transfers PROFIsafe telegrams (safety program, PAE/PAA) between F-PLC

and DRIVE

● Reads-in safety-relevant messages/signals from the message buffers of SI-

NAMICS Safety Integrated into the NC alarm buffer

Safety Integrated plus

30

Commissioning Manual, 12/2019, 6FC5397-1FP40-6BA3

Fundamentals

3.6 Hardware components

3.6

Hardware components

Overview

The SINUMERIK Safety Integrated plus (F-PLC) safety solution places specific requirements

on the hardware components that are used.

Independent of the scope of the Safety Functions used, you can use failsafe SIMATIC and

standard I/O for PROFIBUS DP (Page 33) or PROFINET IO (Page 33) - as known from

SIMATIC Safety.

The drive system that you can use (Page 34) depends on whether a safety-relevant encoder

is used - and which axis type is to be used.

3.6.1

Configuration diagram, SINUMERIK Safety Integrated plus

Hardware components

The following diagram shows an overview of a possible structure with failsafe hardware

components.

PROFIBUS/PROFIsafe

SRVVLEO\ DGGLWLRQDO GLVWULEXWHG , 2

V\VWHPV IDLOVDIH ,2 VWDQGDUG

GHYLFHV '3 VWDQGDUG VODYHV

'LVWULEXWHG , 2

SINUMERIK

Operator panel front with TCU

V\VWHP H J (7

6

&8

ZLWK H[WHUQDO GULYH

Industrial Ethernet

PROFINET/PROFIsafe

SINUMERIK 840D sl

Figure 3-2

Configuration diagram: Hardware structure with SINUMERIK Safety Integrated plus

Safety Integrated plus

32

Commissioning Manual, 12/2019, 6FC5397-1FP40-6BA3

Content      ..     84      85      86      87     ..