Content      ..     17      18      19      20     ..

SINUMERIK 840D sl. Service - Functions. Manual (2018-2020) - page 19

Mode group, channel, program operation, reset response

3.5 Program operation

Search path

The PROG_EVENT program must be located in one of the following cycle directories. The

following search path is passed through when the parameterized event occurs:

1.

/_N_CUS_DIR/ (user cycles)

2.

/_N_CMA_DIR/ (manufacturer cycles)

3.

/_N_CST_DIR/ (standard cycles)

The first program found with the name specified in MD11620 $MN_PROG_EVENT_NAME is

executed.

Note

• The specified program name is checked syntactically as in case of a subprogram name, i.e. the

first two characters must be letters or underscores (no digits). Prefix (_N_) and suffix (_SPF)

of the program names are added automatically, if not specified.

• The same protection mechanisms that can be activated for cycles (protection levels for

writing, reading, etc.) are activated.

Behavior when starting a user ASUB

The behavior of the function "event-driven program call" upon start of a user ASUB from the reset

channel status can be set channel-specific with the machine data:

MD20109 $MC_PROG_EVENT_MASK_PROPERTIES.Bit 0 = <value>

Bit

Value

Meaning

0

0

The PROG_EVENT program is started when one of the events parameterized with

MD20108 occurs.

1

The PROG_EVENT program is not started when one of the events parameterized with

MD20108 occurs.

Behavior when the single-block processing is set

The behavior of the "event-driven program call" function for set single-block processing can be

set channel-specific with the following machine data:

MD20106 $MC_PROG_EVENT_IGN_SINGLEBLOCK.Bit <n> = <value>

Bit

Value

Meaning: In the PROG_EVENT program, the single-block processing for event:

0

0

Part program start: acts

1

Part program start: is suppressed

1

0

Part program end: acts

1

Part program end: is suppressed

2

0

Channel reset: acts

1

Channel reset: is suppressed

3

0

Run-up: acts

1

Run-up: is suppressed

Basic functions

Function Manual, 10/2020, 6FC5397-2GP40-0BA1

67

Mode group, channel, program operation, reset response

3.5 Program operation

If the single-block processing is suppressed, the PROG_EVENT program is processed without

interruption.

Note

• MD20106 $MC_PROG_EVENT_IGN_SINGLEBLOCK affects all single-block processing types.

• The single-block processing in the PROG_EVENT program can be disabled with the following

setting:

MD10702 $MN_IGNORE_SINGLEBLOCK_MASK, bit 0 = 1 (prevent single-block stop)

The settings in MD20106 $MC_PROG_EVENT_IGN_SINGLEBLOCK then do not act.

Behavior when the read-in disable is set

The behavior of the "event-driven program call" function in case of set read-in disable

(DB21, ... DBX6.1 = 1) can be set channel-specific for each initiating event with the following

machine data:

MD20107 $MC_PROG_EVENT_IGN_INHIBIT.Bit <n> = <value>

Bit

Value

Meaning: In the PROG_EVENT program, the read-in disable for event:

0

0

Part program start: acts

If the PROG_EVENT program is terminated with the RET command, no executable

block is created

1

Part program start: is suppressed

If the PROG_EVENT program is terminated with the RET command, an executable

block analog to M17 is created.

1

0

Part program end: acts

1

Part program end: is suppressed

2

0

Channel reset: acts

1

Channel reset: is suppressed

3

0

Run-up: acts

1

Run-up: is suppressed

Suppress updating of the display of the program and channel statuses

To prevent flickering when displaying the program and channel statuses on the HMI user

interface, the display refresh can be suppressed for the execution of the normally very brief

PROG_EVENT program. The program and the channel status before activation of the

PROG_EVENT program then remain visible in the display.

MD20192 $MC_PROG_EVENT_IGN_PROG_STATE.Bit <n> = <value>

Bit

Value

Meaning: While processing the PROG_EVENT program, the refresh of the display

of the program and channel statuses for event:

1

0

Part program end: Not suppressed

1

Part program end: Suppressed

2

0

Channel reset: Not suppressed

1

Channel reset: Suppressed

Basic functions

68

Function Manual, 10/2020, 6FC5397-2GP40-0BA1

Mode group, channel, program operation, reset response

3.5 Program operation

Bit

Value

Meaning: While processing the PROG_EVENT program, the refresh of the display

of the program and channel statuses for event:

3

0

Run-up: Not suppressed

1

Run-up: Suppressed

Note

The system variables $AC_STAT and $AC_PROG are not affected by this function, i.e. in the

running event-driven user program, $AC_STAT is set to "active" and $AC_PROG to "running".

NC/PLC interface signals DB21, ... DBX35.0-7 ("Program status ..." and "Channel status ...") also

remain unaffected.

Response for DB21, ... DBX7.2 / 3 / 4 (NC stop ...)

The response of the "event-driven program call" function for "NC stop", "NC stop at block limit"

and "NC stop axes plus spindle" can be set channel-specific for the part program end, channel

reset and ramp up events with the following machine data:

MD20193 $MC_PROG_EVENT_IGN_STOP.Bit <n> = <value>

Bit

Value

Meaning: The PROG_EVENT-program for NC stop and event

1

0

Part program end: is stopped/prevented

1

Part program end: is processed completely

2

0

Channel reset: is stopped/prevented

1

Channel reset: is processed completely

3

0

Run-up: is stopped/prevented

1

Run-up: is processed completely

Application example

An edge change of the interface signal DB21, ... DBX7.3 (NC stop) initiated by the operator by

pressing the NC Stop key during a channel reset or power-up is ignored during the execution of

the PROG_EVENT program and so an undesired stop behavior at the machine is prevented.

Note

Programming DELAYFSTON/DELAYFSTOF in the PROG_EVENT program cannot replace the

behavior set with MD20193. NC stop before executing the DELAYFSTON command can still

cause an interruption.

Basic functions

Function Manual, 10/2020, 6FC5397-2GP40-0BA1

69

Mode group, channel, program operation, reset response

3.5 Program operation

3.5.12.3

Programming

PROG_EVENT program

End of program

The following must be kept in mind, if the user program is to be activated through the part

program start.

• The user program must be ended with M17 or RET.

• A return jump with the REPOS command is not permissible.

Block display

The display can be suppressed in the current block display using the DISPLOF attribute in the

PROC statement.

Communication to the PLC user program

User M functions programmed in the PROG_EVENT program can inform the PLC user program,

e.g. about the processing status of the PROG_EVENT program.

System variable

Query for triggering event

The initiating event can be queried in the PROG_EVENT program with the following system

variables:

<value> = $P_PROG_EVENT (event-driven program call active)

Value

Meaning: Activation by

1

Part program start

2

Part program end

3

Channel reset

4

Power-up

5

After output of the last action block after Block search (see "Automatic Start of an ASUP after

block search (Page 124)")

Query of the current channel

The channel in which the PROG_EVENT program is processed can be determined with the

following system variables:

<value> = $P_CHANNO (query the current channel number)

Note

The PROG_EVENT program is processed in the channel in which the initiating event occurred.

Power-up is an event that takes place concurrently in all channels.

Basic functions

70

Function Manual, 10/2020, 6FC5397-2GP40-0BA1

Mode group, channel, program operation, reset response

3.5 Program operation

Program code

Comment

IDS=1 EVERY $A_INA[1]>5.0 DO

$A_OUT[1]=1

ENDIF

RET

ENDIF

RET

Example 2: ; Call the PROG_EVENT program for channel reset

Parameterization

MD20108 $MC_PROG_EVENT_MASK = 'H04'

Call of _N_PROG_EVENT_SPF for:

• Operator panel reset

Programming

Program code

Comment

PROC PROG_EVENT DISPLOF

N10 DRFOF

; Deactivate DRF offsets

N20 M17

Example 3: Initialization of the function

Parameterization

Machine data assignment, extract from the commissioning file (_N_INITIAL_INI)

Program code

Comment

CHANDATA(3)

; Initialization for channel 3

$MC_PROG_EVENT_IGN_INHIBIT='H01F'

$MC_PROG_EVENT_MASK='H04'

; Event: Channel reset

Meaning

The PROG_EVENT program _N_CMA_DIR/_N_PROG_EVENT_SPF is started for channel reset in

the 3rd channel and processed until program end, irrespective of whether or not the read-in

disable is activated or deactivated.

Basic functions

72

Function Manual, 10/2020, 6FC5397-2GP40-0BA1

Mode group, channel, program operation, reset response

3.5 Program operation

3.5.13

Influencing the stop events by stop delay areas

3.5.13.1

Function

Stop delay area

The response to a stop event can be influenced by the conditioned interruptible area in the NC

program. Such a program area is called a stop delay area.

Within the stop delay areas there should be no stop and the feedrate should not be changed.

Stops do not take effect until the program section has been completed.

This has the following advantages:

• A program section is processed without a drop in velocity.

• If the user aborts the program after a stop with reset, the aborted program block is after the

protected section. This program block is a suitable search target for a subsequent block

search.

• The following main run axes are not stopped as long as a stop delay area is in progress:

- Command axes

- Positioning axes that travel with POSA

Application

Example: Machining a thread.

Definition

The definition of a stop delay area is made in the part program with the predefined DELAYFSTON

and DELAYFSTOF procedures (see "Programming (Page 76)").

Stop events

Overview of the events that cause a stop:

Event

Reaction

DB21, ... DBX7.7 (reset) or DB11 DBX20.7 (mode group reset)

Immediate

NC program: M30

Alarm 16954

User interrupt to start an ASUP:

Delayed

FC 9 or DB10 DBB1 (setting the digital NC inputs for the PLC)

DB21, ... DBX6.2 / DB31, ... DBX2.2 (clear distance-to-go) channel/axis-specific

Immediate

DB21, ... DBX6.3 (clear the number of subprogram repetitions)

Delayed

DB21, ... DBX6.4 (program level abort)

Delayed

Basic functions

Function Manual, 10/2020, 6FC5397-2GP40-0BA1

73

Mode group, channel, program operation, reset response

3.5 Program operation

Event

Reaction

Stop because of single block

Delayed

• In the stop delay area:

The NC stops at the end of the 1st block outside the stop delay area.

• Single block is active before the stop delay area:

NC stops at each block limit, i.e. also in the stop delay area:

DB21, ... DBX7.2 (NC stop at the block limit)

This deselects the stop delay area!

DB11 DBX21.7 (activate single-block type A)

Delayed

DB11 DBX21.6 (activate single-block type B)

Delayed

DB21, ... DBX7.4 (NC stop) and DB11 DBX0.6 (mode group stop, axes plus

Immediate

spindles)

DB21, ... DBX7.3 (NC stop at block limit) and DB11 DBX0.5 (mode group stop)

Delayed

NC program: Stop because of empty overstore buffer

Alarm 16954

NC program: Programmed or implicit STOPRE

Alarm 16954

NC program: M0 or M1

Alarm 16954

DB21, ... DBX7.2 (NC stop at the block limit)

Delayed

Subprogram end should always deselect the stop delay area.

System error

NC program: WAITM

Alarm 16954

NC program: WAITE

Alarm 16954

NC program: INIT with parameter "S"

Alarm 16954

NC program: MMC (STRING, CHAR)

Alarm 16954

DB21, ... DBB26 (activate/deactivate skip block)

Delayed

DB21, ... DBB26 (deactivate skip block)

Delayed

DB21, ... DBX0.6 (activate DryRun)

Delayed

DB21, ... DBX0.6 (deactivate DryRun)

Delayed

DB21, ... DBX6.1 (read-in disable)

Delayed

Alarm: Alarm configuration STOPATENDBYALARM

Immediate

Alarm: Alarm configuration STOPBYALARM

Immediate

Internal: Stop after alarm for empty IPO buffer

Immediate

Internal: Stop after alarm for empty IPO buffer

Immediate

NC program: Alarm 16954 for LFON

Alarm 16954

NC program: WAITMC

Alarm 16954

NC program: NEWCONF

Alarm 16954

NC program: NEWCONF

Alarm 16954

OPI: PI "_N_SETUDT"

Delayed

Extended stop and retract

Delayed

DB31, ... DBX3.0 (accept external work offset)

Delayed

OPI: PI "_N_FINDST" STOPRUN

Alarm 16955

Alarms with NOREADY response

Immediate

DB21, ... DBX7.2 == 1 (NC stop at block limit)

Delayed

DB21, ... DBX7.3 == 1 (NC stop)

DB21, ... DBX7.4 == 1 (NC stop, axes plus spindles)

DB21, ... DBX6.1 == 1 (read-in disable)

Delayed

Basic functions

74

Function Manual, 10/2020, 6FC5397-2GP40-0BA1

Mode group, channel, program operation, reset response

3.5 Program operation

Event

Reaction

DB21, ... DBX2.0 == 1 (single block)

Delayed

Reaction

• Immediate

Stops immediately, even in the stop delay area. Designated as a "hard stop event".

• Delayed

Does not stop (even short-term) until after the stop delay area. Is known as a "soft stop event".

• Alarm 16954

Program is aborted because illegal program commands have been used in the stop delay area.

• Alarm 16955

Program is continued, an illegal action occurred in the stop delay area.

• Alarm 16957

The program area (stop delay area) enclosed by DELAYFSTON and DELAYFSTOF could not be activa-

ted. As a result, every stop will take effect immediately and is not subject to a delay! This will always

occur when the deceleration begins before the stop delay area but ends within the stop delay area.

Likewise, if the stop delay area is entered with an override of 0, the stop delay area also cannot be

activated. (Example: A G4 before the stop delay area allows the user to reduce the override to 0. The

next block in the stop delay area then begins with override 0 and the described alarm situation

occurs.)

Note

MD11411 $MN_ENABLE_ALARM_MASK (activation of warnings) Bit 7 activates this alarm.

Note

Some NC events are stopped for only a short time, in order to perform a switching operation, and

restart immediately. This includes, e.g. an interrupt that stops the NC program briefly in order to

start the associated ASUP. These events are also allowed in the stop delay area, however they are

pushed back to its end and are thus considered "soft stop events".

Note

If a "hard" stop event coincides with the "stop delay area", the entire "stop delay area" is

deselected! Thus, if any other stop occurs in this program section, it will be stopped immediately.

A new program setting (new DELAYFSTON) must be made in order to start a new stop delay area.

3.5.13.2

Parameterization

Machine data

Stop response for G331/G332

For tapping without compensating chuck (G331, G332), the stop response can be set as follows:

Basic functions

Function Manual, 10/2020, 6FC5397-2GP40-0BA1

75

Mode group, channel, program operation, reset response

3.5 Program operation

MD11550 $MN_STOP_MODE_MASK

Bit

Value

Meaning

0

0 (default)

Results in an implicit stop delay range if G331/G332 is active - and path motion

or a dwell time (G4) was also programmed.

1

A stop while G331/G332 is active is possible in the following situations:

• The continuous path mode is interrupted (G64).

• A dwell time (G4) is programmed between the G33x blocks.

NC commands DELAYFSTON and DELAYFSTOF must be used to define a stop

delay range.

3.5.13.3

Programming

Defining a stop delay range (DELAYFSTON, DELAYFSTOF)

The predefined DELAYFSTON and DELAYFSTOF procedures are used to define a conditionally

interruptible range in the part program (stop delay range).

Note

DELAYFSTON and DELAYFSTOF are not permitted in synchronized actions!

Syntax

DELAYFSTON

DELAYFSTOF

Meaning

DELAYFSTON:

Defining the start of a stop delay range

Alone in the block:

Yes

DELAYFSTOF:

Define the end of the stop delay area

Alone in the block:

Yes

Programming example

The following program block is repeated in a loop:

Program code

N99 MY_LOOP:

N100 G0 Z200

N200 G0 X0 Z200

Basic functions

76

Function Manual, 10/2020, 6FC5397-2GP40-0BA1

Mode group, channel, program operation, reset response

3.5 Program operation

Program code

N300 DELAYFSTON

N400 G33 Z5 K2 M3 S1000

N500 G33 Z0 X5 K3

N600 G0 X100

N700 DELAYFSTOF

N800 GOTOB MY_LOOP

In the following diagram it can be seen that the user pressed "Stop" in the stop delay range, and

the NC started braking outside the stop delay range, i.e. in block N100. That causes the NC to

stop at the beginning of N100.

1& VWRSSW

1

* =

1

* ;

1

* ; =

1

*

=

;

1

*

=

;

6WRS EXWWRQ

6WRS EXWWRQ GXULQJ D *

=

PDFKLQLQJ

Additional information

End of subprogram

DELAYFSTOF is activated implicitly at the end of the subprogram in which DELAYFSTON is called.

Nesting

If subprogram 1 calls subprogram 2 in a stop delay area, the whole of subprogram 2 is a stop

delay area. In particular, DELAYFSTOF in subprogram 2 has no effect.

Example:

Program code

Comment

N10010 DELAYFSTON

; Blocks with N10xxx program level 1.

N10020 R1 = R1 + 1

N10030 G4 F1

; Stop delay area starts.

N10040 subprogram2

; Interpretation of subprogram 2.

N20010 DELAYFSTON

; Ineffective, repeated start, 2nd level.

Basic functions

Function Manual, 10/2020, 6FC5397-2GP40-0BA1

77

Mode group, channel, program operation, reset response

3.5 Program operation

Program code

Comment

N20020 DELAYFSTOF

; Ineffective, end at another level.

N20030 RET

N10050 DELAYFSTOF

; Stop delay end of range at the same level.

N10060 R2 = R2 + 2

N10070 G4 F1

; Stop delay area ends. From now, stops act immediately.

System variables

The following system variables can be queried to determine whether part program processing

is currently in a stop delay area:

• in the part program with $P_DELAYFST

• in synchronized actions with $AC_DELAYFST

Value

Meaning

0

Delay stop range not active

1

Delay stop area active

3.5.13.4

Supplementary conditions

Overlap

If two stop delay areas overlap, one from DELAYFSTON/DELAYFSTOF and the other from

MD11550 $MN_STOP_MODE_MASK, the largest possible stop delay area will be generated.

Dwell time (G4)

G4 is permitted in the stop delay area. Other part program commands that cause a stop in the

meantime (e.g. WAITM) are not permitted and trigger the alarm 16954.

Override

If the override is changed before a stop delay area, the override takes effect in the stop delay

area.

If the override is changed in the stop delay area, the change takes effect after the stop delay area.

Note

Override = 0

If the override is reduced to 0 before a stop delay area, the stop delay area cannot be activated.

Feed disable

DB21, ... DBX6.0 The feed disable has no effect in the stop delay area; the program does not stop

until after the stop delay area.

Basic functions

78

Function Manual, 10/2020, 6FC5397-2GP40-0BA1

Mode group, channel, program operation, reset response

3.5 Program operation

Single block

If the single block is activated in the stop delay area, the NC stops at the end of the first block

outside the stop delay area.

If the single block is already selected before the stop delay area, the NC stops at each block limit,

i.e. also in the stop delay area! This deselects the stop delay area.

3.5.14

Adapting the size of the interpolation buffer

MD28060

The channel-specific interpolator executes prepared blocks from the interpolation buffer during

the part program run. The maximum number of blocks requiring space in the interpolation

buffer at any given point in time is defined by the memory configuring MD28060

$MM_IPO_BUFFER_SIZE (number of NC blocks in the IPO buffer (DRAM)). For some applications

it may be meaningful not to use the full buffer capacity in order to minimize the "interval"

between preparation and interpolation.

SD42990

The number of blocks in the interpolation buffer can be restricted dynamically to a smaller value

than in MD28060 $MC_MM_IPO_BUFFER_SIZE (number of NC blocks in the IPO buffer (DRAM)),

minimum 2 blocks, with the setting data SD42990 $SC_MAX_BLOCKS_IN_IPOBUFFER (max.

number of blocks in the IPO buffer).

Values of setting data SD42990 $SC_MAX_BLOCKS_IN_IPOBUFFER:

Value

Effect

< 0

No interpolation buffer limit active.

The max. possible IPO buffer as set in MD 28060: MM_IPO_BUFFER_SIZE is acti-

vated.

or 1

The minimum permissible IPO buffer with two blocks is activated.

< MM_IPO_BUFFER_SIZE

The IPO buffer is activated with no more than the maximum specified number of

blocks.

>= MM_IPO_BUFFER_SIZE

The IPO buffer is activated with the number of blocks specified in MD 28060:

MM_IPO_BUFFER_SIZE.

Basic functions

Function Manual, 10/2020, 6FC5397-2GP40-0BA1

79

Mode group, channel, program operation, reset response

3.5 Program operation

3.5.15

Basic block display (only for ShopMill/ShopTurn)

3.5.15.1

Function

In ShopMill/ShopTurn, a so-called basic block display can be used in addition to the existing block

display to show all blocks that produce an action on the machine.

The end positions actually approached are shown as an absolute position. The position values

refer either to the workpiece coordinate system (WCS) or the settable zero system (SZS).

The number of LookAhead display blocks stored in the display buffer depends on the number of

prepared blocks in the relevant processing state in the preprocessing buffer of the control. If a

preprocessing stop is processed, the number of display blocks is reduced to zero and increases

again after the stop is acknowledged. In the case of REORG events (e.g. mode change, ASUB

start), the display blocks stored for LookAhead are deleted and preprocessed again afterwards.

Values processed in the basic block display coincide with the:

• Selected tools

• Feedrate and spindle speed

• Position values actually approached

Exceptions:

With active tool radius compensation, deviations can occur.

For modulo axes, the programmed value is displayed in the basic block display. This value can

also lie outside the modulo range.

Activating/deactivating basic block display

The basic block display can be activated/deactivated in the following setting data:

SD42750 $SC_ABSBLOCK_ENABLE (enabling the basic block display)

3.5.15.2

Parameterization

Configure basic block display

The basic block display can be configured via the following machine data:

NC machine data for basic block display

Meaning:

MD28400 $MC_MM_ABSBLOCK

Activate basic block display

MD28402 $MC_MM_ABSBLOCK_BUFFER_CONF[2]

Size of the display buffer

Machine data display

Position values to be set:

MD9004 $MM_DISPLAY_RESOLUTION

for metric dimensional notation

MD9011 $MM_DISPLAY_RESOLUTION_INCH

for imperial dimensional notation

MD9010 $MM_SPIND_DISPLAY_RESOLUTION

Coordinate system to be set for spindles display

resolution

MD9424 $MM_MA_COORDINATE_SYSTEM

for WCS or SZS actual value display

This display machine data is copied to NC machine data

MD17200 $MN_GMMC_INFO_UNIT[0] (global HMI information) to MD17200

$MN_GMMC_INFO_UNIT[3]. This permits access from the NC to this display machine data.

Basic functions

Function Manual, 10/2020, 6FC5397-2GP40-0BA1

81

Mode group, channel, program operation, reset response

3.5 Program operation

3.5.15.3

Structure for a DIN block

Structure of display block for a DIN block

Basic structure of display block for a DIN block

• Block number/label

• G command of the first G group

(only if changed as compared to the last machine function block).

• Axis position

(sequence corresponding to MD20070 $MC_AXCONF_MACHAX_USED (machine axis

number valid in the channel)).

• Further modal G commands

(only if changed as compared to the last machine function block).

• Other addresses as programmed.

The display block for the basic block display is directly derived from the programmed part

program blocks according to the following rules:

• Macros are expanded.

• Skip identifiers and comments are omitted.

• Block number and labels are transferred from the original block, but omitted if DISPLOF is

active.

• The number of decimal places is defined in display machine data MD 9004, MD 9010 and MD

9011 via the HMI.

HMI display machine data

Access in the NC machine data

MD9004 $MM_DISPLAY_RESOLUTION

MD17200 $MN_GMMC_INFO_NO_UNIT[0]

MD9011 $MM_DISPLAY_RESOLUTION_INCH

MD17200 $MN_GMMC_INFO_NO_UNIT[1]

MD9010 $MM_SPIND_DISPLAY_RESOLUTION

MD17200 $MN_GMMC_INFO_NO_UNIT[2]

MD9424 $MM_MA_COORDINATE_SYSTEM

MD17200 $MN_GMMC_INFO_NO_UNIT[3]

• Programmed axis positions are represented as absolute positions in the coordinate system

(WCS / SZS) specified in MD9424 $MM_MA_COORDINATE_SYSTEM (coordinate system for

actual value display)

Note

The modulo correction is omitted for modulo axes, which means that positions outside the

modulo range can be displayed. It also means that the basic block display differs from the

position display in which values are always modulo-converted.

Basic functions

84

Function Manual, 10/2020, 6FC5397-2GP40-0BA1

Mode group, channel, program operation, reset response

3.6 Program control

Original block:

Display block:

N710 Y157.5 G42

N710 Y157.5 G42

N720 Z-67.5 RND=7.5

N720 Z-67.5 RND=7.5

• With the EXECTAB command (processing a table of contour elements), the block generated

by EXECTAB is shown in the display block.

Original block:

Display block:

N810 EXECTAB (KTAB[5])

N810 G01 X46.147 Z-25.38

• With the EXECSTRING command, the block generated via EXECSTRING is displayed in the

display block.

Original block:

N910 DEF STRING[40] PROGSTRING = "N905 M3 S1000 G94 Z100 F1000 G55"

N920 EXECSTRING(PROGSTRING)

Original block:

N905 Z100 G55 G94 M3 S1000 F1000

3.6

Program control

3.6.1

Overview

The control system provides various functions for controlling the execution of an NC program.

These functions are predominantly used for testing and running-in a new part program. Using

these functions significantly reduces the danger to the machine and time required during the

test phase.

Several program control functions can be activated at the same time to achieve a better result.

Functions

The following program control functions are available:

• Program test (Page 89)

• Dry run feedrate (Page 92)

• Reduced rapid traverse (Page 94)

• Programmed stop (Page 94)

• Handwheel offset (Page 95)

• Skipping program blocks (Page 96)

Basic functions

Function Manual, 10/2020, 6FC5397-2GP40-0BA1

87

Mode group, channel, program operation, reset response

3.6 Program control

Note

Tool management

Because of the axis disable, the assignment of a tool magazine is not changed during program

testing. A PLC application must be used to ensure that the consistency between the data in the

tool management system and the magazine is not corrupted.

3.6.3

Dry run feedrate

Function

To reduce the processing time during the program test, traversing motion can be executed faster

by activating the drive run feedrate. For example, for G01, G02, G03, G33, G34, G35, G95, the

test feedrate applies instead of the programmed feedrate.

NOTICE

Destroyed tool or workpiece as a result of excessively high cutting velocities

When a workpiece is machined with the dry run feedrate function active, the resulting cutting

velocities may lie outside the permissible range and lead to destruction of the tool and / or

workpiece.

As a consequence, the dry run feedrate should only be used for the program test.

Activation

The dry run feedrate is selected at the user interface in the AUTOMATIC and MDI modes, and can

be activated when automatic operation is interrupted or at the end of the block.

Selection

The "Dry run feedrate" function is selected for the channel displayed in the "Machine" basic

display via the user interface, e.g. SINUMERIK Operate:

1. Softkey: Operating area "Machine" > "Program control"

2. "Program control" menu: select checkbox "Dry run feedrate (DRY)".

The following signal is set in the HMI/PLC interface to request that the PLC user program activates

the function:

DB21, ... DBX24.6 (dry run feedrate selected) == 1

Basic functions

92

Function Manual, 10/2020, 6FC5397-2GP40-0BA1

Mode group, channel, program operation, reset response

3.6 Program control

The PLC then transfers the selection signal to the corresponding activation signal of the NC/PLC

interface.

Note

The function may also be directly activated via the PLC user program by setting the

corresponding activation signal in the NC/PLC interface.

Activation

To request that the NC activates the function, the PLC user program must set the following NC/

PLC interface signal:

DB21, ... DBX0.6 (activate dry run feedrate) == 1

Feedback signal

The following NC/PLC interface signal is set as feedback signal to the PLC user program that the

function is active in the NC:

DB21, ... DBX318.6 (dry run feedrate active) == 1

Parameterization

Dry run feedrate

The dry run feedrate effective in the channel is set using:

SD42100 $SC_DRY_RUN_FEED = <dry run feedrate>

Note

Revolutional feedrate

The dry run feedrate also replaces the programmed revolutional feedrate in program blocks with

G95.

Dry run feedrate mode

The dry run feedrate mode is set with:

SD42101 $SC_DRY_RUN_FEED_MODE = <value>

<Val-

Meaning

ue>

0

The maximum from SD42100 and the programmed feedrate are effective as dry run feedrate.

1

The minimum from SD42100 and the programmed feedrate are effective as dry run feedrate.

2

SD42100 is effective as dry run feedrate.

10

The same as for a value of 0, except for thread cutting (G33, G34, G35) and tapping (G331,

G332, G63): For these functions, the programmed feedrate applies.

11

The same as for a value of 1, except for thread cutting (G33, G34, G35) and tapping (G331,

G332, G63): For these functions, the programmed feedrate applies.

12

The same as for a value of 2, except for thread cutting (G33, G34, G35) and tapping (G331,

G332, G63): For these functions, the programmed feedrate applies.

Basic functions

Function Manual, 10/2020, 6FC5397-2GP40-0BA1

93

Mode group, channel, program operation, reset response

3.6 Program control

1

1

1

1

1

1

1

1

1

1

1

1

Program code

Comment

N10 …

; Is executed

/N20 …

; Skipped

N30 …

; Is executed

/N40 …

; Skipped

/N50 …

; Skipped

/N60 …

; Skipped

N70 …

; Is executed

Skip levels

Blocks can be assigned to skip levels (max. 10), which can be activated via the user interface or

the PLC user program.

The assignment is made in the NC program using a forward slash, followed by the number of the

skip level. Only one skip level can be specified for each block.

Example:

Program code

Comment

/ ...

; Block is skipped (1st skip level)

/0 ...

; Block is skipped (1st skip level)

/1 N010...

; Block is skipped (2nd skip level)

/2 N020...

; Block is skipped (3rd skip level)

/7 N100...

; Block is skipped (8th skip level)

/8 N080...

; Block is skipped (9th skip level)

/9 N090...

; Block is skipped (10th skip level)

Basic functions

Function Manual, 10/2020, 6FC5397-2GP40-0BA1

97

Mode group, channel, program operation, reset response

3.6 Program control

Note

The levels to be skipped can only be changed when the control system is in the STOP/reset state.

Note

The number of skip levels that can be used depends on a display machine data.

Note

Skipping blocks also remains active during block searches.

Note

System and user variables can also be used in conditional jumps in order to control program

execution.

Selection

Skip levels for the channel displayed in the "Machine" basic display are selected via the user

interface, e.g. SINUMERIK Operate:

1. Softkey: Operating area "Machine" > "Program control"

2. "Program control" menu: Select checkbox "Skip level... (SKP)".

The associated signal is set in the HMI/PLC interface to request that the PLC user program

activates the selected skip level:

DB21, ... DBX26.0 (skip blocks of the 1st skip level) == 1

DB21, ... DBX26.1 (skip blocks of the 2nd skip level) == 1

DB21, ... DBX26.7 (skip blocks of the 8th skip level) == 1

DB21, ... DBX27.0 (skip blocks of the 9th skip level) == 1

DB21, ... DBX27.1 (skip blocks of the 10th skip level) == 1

Note

The function may also be directly activated via the PLC user program by setting the

corresponding activation signal in the NC/PLC interface.

Activation

To request that the NC activates the skip level, the PLC user program must set the appropriate NC/

PLC interface signal:

DB21, ... DBX2.0 (skip blocks of the 1st skip level) == 1

DB21, ... DBX2.1 (skip blocks of the 2nd skip level) == 1

Basic functions

98

Function Manual, 10/2020, 6FC5397-2GP40-0BA1

Mode group, channel, program operation, reset response

3.6 Program control

Suppressing single block machining for the complete NC program

If the deactivation of single block machining (SBLOF) is programmed in the first line (PROC ...)

of a main program, this remains valid until the end of the NC program or until the NC program

is canceled. The NC program is then executed without stopping when in the single block mode.

If deactivating single block machining (SBLOF) is programmed in the first line (PROC ...) of a

subprogram, this remains valid until the end of the NC program or until the NC program is

canceled. With the programmed return command, the decision is made whether to stop at the

end of the subprogram:

• Return with M17: Stop at the end of the subprogram

• Return with RET: No stop at end of subprogram

Suppressing single block machining within the NC program

If the deactivation of single block machining (SBLOF) is programmed in a block within an NC

program, then single block machining is deactivated from this block onward up to the next

programmed activation of single block machining (SBLON) - or at the end of the active

subprogram level.

Syntax

Suppressing single block machining for the complete NC program:

PROC ... SBLOF

Suppressing single block machining within the NC program:

SBLOF

SBLON

Meaning

PROC:

First operation in a program

SBLOF:

Predefined procedure to deactivate single block machining

Alone in the block:

Yes, possible in the PROC block

Effectiveness:

Modal

SBLON:

Predefined procedure to activate single block machining

Alone in the block:

yes

Effectiveness:

Modal

Basic functions

102

Function Manual, 10/2020, 6FC5397-2GP40-0BA1

Mode group, channel, program operation, reset response

3.6 Program control

Example 2: A cycle is to act like a command for a user

Initial situation: Single block machining is active.

Main program:

Program code

N100 G1 X10 G90 F200

N120 X-4 Y6

N130 CYCLE1

N140 G1 X0

N150 M30

Cycle CYCLE1:

Program code

Comment

N100 PROC CYCLE1 DISPLOF SBLOF

; Suppress single block machining for the com-

plete program.

N110 R10=3*SIN(R20)+5

N120 IF (R11 <= 0)

N130 SETAL(61000)

N140 ENDIF

N150 G1 G91 Z=R10 F=R11

N160 M17

The cycle CYCLE1 is processed with active single block machining. CYCLE1 is processed for active

single block machining, i.e. the Start key must be pressed once to process CYCLE1.

Example 3: An ASUB, which is started by the PLC in order to activate a modified zero offset

and tool offsets, is to be executed invisibly

Program code

Comment

N100 PROC NV SBLOF DISPLOF

; Suppress single block machining and block

display.

N110 CASE $P_UIFRNUM OF

0 GOTOF _G500

1 GOTOF _G54

2 GOTOF _G55

3 GOTOF _G56

4 GOTOF _G57

DEFAULT GOTOF END

N120 _G54: G54 D=$P_TOOL T=$P_TOOLNO

N130 RET

N140 _G54: G55 D=$P_TOOL T=$P_TOOLNO

N150 RET

N160 _G56: G56 D=$P_TOOL T=$P_TOOLNO

N170 RET

N180 _G57: G57 D=$P_TOOL T=$P_TOOLNO

N190 RET

Basic functions

104

Function Manual, 10/2020, 6FC5397-2GP40-0BA1

Mode group, channel, program operation, reset response

3.6 Program control

Program code

Comment

N200 END: D=$P_TOOL T=$P_TOOLNO

N210 RET

Example 4: Specific stopping in the subprogram

Initial situation:

• Single block machining is active.

• MD10702 $MN_IGNORE_SINGLEBLOCK_MASK, Bit12 = 1

Main program:

Program code

Comment

N10 G0 X0

; single block stop

N20 X10

; single block stop

N30 CYCLE

; Traversing block generated by the cycle.

N50 G90 X20

; single block stop

M30

Cycle CYCLE:

Program code

Comment

PROC CYCLE SBLOF

; Suppress single block machining

N100 R0=1

N110 SBLON

; No single block stop due to MD10702 bit12 = 1

N120 X1

; single block stop

N140 SBLOF

N150 R0=2

RET

Example 5: Suppression of single block machining with program nesting

Initial situation:

• Single block machining type 2 is active.

• The program execution shall not be interrupted in the SBLON block

(MD10702 $MN_IGNORE_SINGLEBLOCK_MASK, Bit12 = 1)

Program code

Comment

N10 X0 F1000

; single block stop

N20 UP1(0)

PROC UP1(INT _NR) SBLOF

; Deactivate single block machining for

UP1

N100 X10

N110 UP2(0)

PROC UP2(INT _NR)

N200 X20

N210 SBLON

; Activate single block machining

N220 X22

; single block stop

Basic functions

Function Manual, 10/2020, 6FC5397-2GP40-0BA1

105

Mode group, channel, program operation, reset response

3.6 Program control

execution and are traversed at maximum speed, a stop should be made after each G0 block (stop

situation "Transition G0 → G0").

Positioning a workpiece

In machine tools, many machine functions are implemented with auxiliary functions (M/H

functions) or cycles (subprograms) (e.g. tool change, traverse steady rest to the workpiece,

etc.). When positioning a workpiece, the machine operator usually wants to execute such

machine functions somewhat more slowly to ensure that no collisions occur. With the aid of the

"Configured stop" function, the operator can stop the program before the start of the cycle or

before the auxiliary function is started and then set the override switch down to 0%. Then the

operator continues program execution with NC start. The block with the cycle or auxiliary

function is loaded and traversing is started by turning on the override switch.

Note

The override value can also be set to 0% via the PLC user program.

Another critical situation when positioning a workpiece is the start of motions involving large

masses or bodies. The "Configured stop" function can also be used to make stops before such

motions if a suitable stop situation has been defined prior to the program start.

3.6.10.2

Selecting and activating

Selection

It is possible to select the "Configured stop" function for the channel displayed in the root screen

"Machine" in all modes via the operator interface.

E.g. SINUMERIK Operate:

1. Operating area "Machine" > "Program control"

2. "Program control" window: select "CST configured stop"

The relevant stop situations are selected via the corresponding selection box in the "Program

control" window. All of the stop situations that were defined during commissioning are listed

there.

To select the function and the relevant stop situations, the channel must be in the "Reset" or

"Interrupted" state:

DB21, … DBX35.7 == 1 (channel status "reset")

DB21, ... DBX35.6 == 1 (channel state "interrupted")

The following signal is set in the HMI/PLC interface to request that the PLC user program activates

the function:

DB21, ... DBX24.1 (activate configured stop) == 1

Note

The function may also be directly activated via the PLC user program by setting the

corresponding activation signal in the NC/PLC interface.

Basic functions

Function Manual, 10/2020, 6FC5397-2GP40-0BA1

109

Mode group, channel, program operation, reset response

3.6 Program control

Setting data

Definition of stop situations

The stop situations for the configured stop are defined by the following setting data:

Setting data

Meaning

SD42220 $SC_CFG_STOP_ARRAY[<n>] = "<Name>"

NC functions and subprograms before which stops are to be made

<Name>:

Name of the NC function/subprogram

Data type:

STRING

The following are permitted:

• M/H/T/D function calls

The following syntax rules must be observed:

- No address extensions are supported for D.

- The value of the auxiliary function is always a

positive INTEGER value, including 0.

- Negative INTEGER values for the address exten-

sion are permitted for M functions.

Example: "M[-5]=3"

- An asterisk (*) is permitted as a wildcard.

Example: "M[*]=87" / "M*=87"

• Subprogram names

Valid nomenclature: "_N_..."

<n>:

Array index

Data type:

INT

Range of values:

0 ... 19

Examples:

• $SC_CFG_STOP_ARRAY[0] = "M=87"

• $SC_CFG_STOP_ARRAY[1] = "_N_CS_TOOL"

• $SC_CFG_STOP_ARRAY[3] = "_N_MY_TOOL_CHANGE"

SD42222 $SC_CFG_STOP_MASK

G function transitions at which a stop should be made

Bit 0

G0 → G0

Bit 1

G0 → Not-G0

Bit 2

Not-G0 → G0

SD42224 $SC_CFG_STOP_ARRAY_MASK

Release of SD42220 $SC_CFG_STOP_ARRAY[<n>]

Bit 0

Release of SD42220 $SC_CFG_STOP_ARRAY[0]

Bit 1

Release of SD42220 $SC_CFG_STOP_ARRAY[1]

Bit 19

Release of SD42220 $SC_CFG_STOP_ARRAY[19]

Note

The valid nomenclature and syntax rules must be observed when specifying the NC function or

subprogram name.

In the event of an error, alarm 16968 "Machine data $SC_CFG_STOP_ARRAY contains invalid

syntax" is displayed.

Basic functions

Function Manual, 10/2020, 6FC5397-2GP40-0BA1

111

Mode group, channel, program operation, reset response

3.6 Program control

Program code

N40 G1 X40

N50 G0 X50

N60 M30

Program execution 1

NC start

→ The program starts. Stops at the end of block N30 at position X = 30.

NC start

→ Output of the M function, the program is continued without further stops

until the end of the program.

Program example 2

Program code

N10 G0 X10

N20 G0 X20

N30 G1 X30 M88 F1000

N40 G1 X40

N50 G0 X50

N60 M30

Program execution 2

NC start

→ The program starts. Stops at the end of block N20 at position X = 20.

NC start

→ The output of the M function takes place in block N30, the program is con-

tinued without further stops until the end of the program.

Program example 3

Program code

N10 G0 X10

N20 G0 X20

N30 G1 X30 F1000

N35 WHEN TRUE DO M88

N40 G1 X40

N50 G0 X50

N60 M30

Program execution 3

NC start

→ The program starts and is executed until the end of the program. The aux-

iliary function call in the action part of the synchronized action does not

result in a program stop.

Basic functions

114

Function Manual, 10/2020, 6FC5397-2GP40-0BA1

Mode group, channel, program operation, reset response

3.6 Program control

Program code

Comment

N200 T1

; NC start required to continue the program and for tool

change

N250 G1 X9

N300 G1 Z100

N350 G1 X20

N400 G1 Z10

; No stop because T2 not in $SC_CFG_STOP_ARRAY

N500 T2

N550 G1 X9

N600 G1 Z100

N650 G1 X20

N700 G1 Z10

; Stop at Z10 X20

N800 T3

; NC start required to continue the program and for tool

change

N850 G1 X8

N900 G1 Z100

N950 G1 X20

N1000 G1 Z10

N2000 M30

; Stop due to end of program

Note

Without tool management, the T functions are treated like any other auxiliary functions. This

allows a selective stop before a specific tool change (as shown in the example).

This is not possible with tool management. Here stops can only be made before each tool change

(with the stop situation "T[*]=*").

Basic functions

116

Function Manual, 10/2020, 6FC5397-2GP40-0BA1

Mode group, channel, program operation, reset response

3.7 Block search, types 1, 2, and 4:

3.6.11

Status

The currently selected settings for program control can be read through system variables:

• In the part program via preprocessing variables:

System variable

Type

Meaning

$P_ISTEST

BOOL

Program test active

$P_DRYRUN

BOOL

Dry run feedrate active

$P_ISRG0

BOOL

Reduced rapid traverse active

$P_ISPROGSTOP

BOOL

Programmed stop 1 (M01) active

$P_ISDRF

BOOL

Handwheel offset active

$P_ISSKIP

BOOL

Skip block active

• In the part program and in synchronized actions via the main run variable:

System variable

Type

Meaning

$AC_PROGINF

INT

Active program control

The value is bit-coded. These individual bits have the following mean-

ing:

Bits 0 ... 9

Skip level 0 ... 9 active

Bit 10

Dry run feedrate active

Bit 11

Programmed stop 1 (M01) active

Bit 12

Handwheel offset active

Bit 13

Single block active

Bit 14

Reduced rapid traverse active

Bit 15

Feed stop active

Bit 16

Program test active

Bit 17

Associated help function (M-1) active

Bit 18

Configured stop active

Further information: List Manual System Variables

3.7

Block search, types 1, 2, and 4:

Function

Block search offers the possibility of starting part program execution from almost any part

program block.

This involves the NC rapidly performing an internal run through the part program (without

traversing motions) to the selected target block during block search. Here, every effort is made

to achieve the exact same control status as would result at the target block during normal part

program execution (e.g. with respect to axis positions, spindle speeds, loaded tools, NC/PLC

interface signals, variable values) in order to be able to resume automatic part program

execution from the target block with minimum manual intervention.

Basic functions

Function Manual, 10/2020, 6FC5397-2GP40-0BA1

117

Mode group, channel, program operation, reset response

3.7 Block search, types 1, 2, and 4:

Time sequence

%ORFN VHDUFK DFWLYH

'%

'%;

$FWLRQ EORFN DFWLYH

'%

'%;

/DVW DFWLRQ EORFN DFWLYH

'%

'%;

&KDQQHO VWDWXV UHVHW

'%

'%;

&KDQQHO VWDWXV LQWHUUXSWHG

'%

'%;

①

Start block search

②

Search target 1 found

③

Start block search

④

Search target 2 found

⑤

NC start - output action blocks

⑥

Last action block

Action blocks

During a block search type 2 or type 4 (block search with calculation to ...), actions such as tool

(T, D), spindle (S), feedrate programming or M function outputs are collected. With NC start to

execute the action blocks, the collected actions are output to the PLC.

Note

With NC start for the action blocks, the spindle programming collected during block search type

2 or type 4 (block search with calculation to ...) (S value, M3 / M4 / M5 / M19, SPOS) becomes

active.

The user has to ensure in the PLC user program that the tool can be operated or the spindle

programming is reset or not output:

DB31, ... DBX2.2 = 1 (spindle reset).

Constraints

Continuation mode after block search type 4

If initial programming of an axis is performed incrementally to a block search type 4 (block

search with calculation to block end point), the programmed incremental value can be added to

Basic functions

120

Function Manual, 10/2020, 6FC5397-2GP40-0BA1

Mode group, channel, program operation, reset response

3.7 Block search, types 1, 2, and 4:

When the alarm is displayed can be set via machine data:

MD11450 $MN_SEARCH_RUN_MODE, Bit 0 = <value>

<val-

Meaning

ue>

0

With the change of the last action block after a block search, the following takes place:

• Execution of the part program is stopped

• DB21, ... DBB32.6 = 1 (last action block active)

• Display alarm 10208

1

With the change of the last action block after a block search, the following takes place:

• Execution of the part program is stopped

• DB21, ... DBB32.6 = 1 (last action block active)

• Only display alarm 10208 if DB21, ... DBX1.6 == 1 (PLC action ended)

In combination with the alarm, the following interface signals are set:

• DB21, ... DBX36.7 = 1 (NC alarm with machining standstill is pending)

• DB21, ... DBX36.6 = 1 (NC alarm channel-specific is pending)

3.7.2.3

Spindle functions after block search

Control system response and output

Whether the spindle-specific auxiliary functions collected during block search are automatically

output to the PLC in the action block or user-specifically at a later time can be set in

MD11450 $MN_SEARCH_RUN_MODE, Bit 2 = <value>

<val-

Meaning

ue>

0

Output of spindle-specific auxiliary functions collected during block search (M3, M4, M5, M19,

M70) in action blocks.

1

The spindle-specific auxiliary functions collected during block search are not output in the

action block.

They can be output at a later time, for example, in an ASUP. The spindle-specific auxiliary

functions collected are stored in system variables:

System variables

The spindle-specific auxiliary functions collected during block search are stored in the following

system variables:

System variable

Description

$P_SEARCH_S [ <n> ]

The spindle speed or cutting speed last programmed

$P_SEARCH_SDIR [ <n> ]

Spindle direction last programmed

$P_SEARCH_SGEAR [ <n> ]

Gear stages last programmed M function

$P_SEARCH_SMODE [ <n> ]

Spindle mode last programmed

Basic functions

Function Manual, 10/2020, 6FC5397-2GP40-0BA1

123

Mode group, channel, program operation, reset response

3.7 Block search, types 1, 2, and 4:

System variable

Description

$P_SEARCH_SPOS [ <n> ]

Spindle position or traverse path last programmed by means

of M19, SPOS or SPOSA

$P_SEARCH_SPOSMODE [ <n> ]

Position approach mode last programmed by means of M19,

SPOS, or SPOSA

<n>: Spindle number

For later output of the spindle-specific auxiliary functions, the system variables can be read, for

example, in an ASUB, and output after output of the action blocks:

DB21, ... DBX32.6 == 1 (last action block active)

Note

The contents of the system variables $P_S, $P_DIR and $P_SGEAR may be lost after block search

due to synchronization operations.

For more detailed information on ASUB, block search and action blocks, see Sections "Output

suppression of spindle-specific auxiliary functions (Page 743)" and "Program test (Page 89)."

3.7.2.4

Reading system variables for a block search

In part programs, values can be read from the areas processing, main run, or servo/drive via

system variables:

$P_...

Preprocessing-related system variables contain programmed values

$A_...

Main-run-related system variables contain current values

$V_...

Servo/drive-related system variables contain current values

Because no blocks enter the main run during a block search of type 2 and type 4 (block search

with calculation to ...), main run and servo/drive-related system variables are not changed

during the block search. Where necessary, for these system variables, the block search must

specially handled in the NC program by querying whether a block search is active $P_SEARCH

(block search active).

Preprocessing-related system variables provide correct values in all search types.

3.7.3

Automatic start of an ASUB after a block search

Parameter assignment

Making the function effective

The automatic ASUB start after a block search is activated by the following MD setting:

MD11450 $MN_SEARCH_RUN_MODE, bit 1 = 1

Program to be activated

In the default setting, the program _N_PROG_EVENT_SPF is activated from the directory

_N_CMA_DIR as ASUB after the block search by changing the last action block. If another

Basic functions

124

Function Manual, 10/2020, 6FC5397-2GP40-0BA1

Mode group, channel, program operation, reset response

3.7 Block search, types 1, 2, and 4:

program is to be activated, then the name of this user program must be entered in the following

machine data:

MD11620 $MN_PROG_EVENT_NAME

Behavior when the single-block processing is set

The following channel-specific machine data are used to set whether the activated ASUP will be

processed without interruption although single-block processing is set or whether single-block

processing will be activated:

MD20106 $MC_PROG_EVENT_IGN_SINGLEBLOCK, bit 4 = <value>

<val-

Meaning

ue>

0

Single-block processing is active.

1

Single-block processing is suppressed.

Behavior when the read-in disable is set

The channel-specific machine data is used to set whether the ASUP will be processed without

interruption although read-in disable (DB21, ... DBX6.1 = 1) is set, or whether the read-in disable

will be effective:

MD20107 $MC_PROG_EVENT_IGN_INHIBIT, Bit 4 = <value>

<val-

Meaning

ue>

0

Read-in disable is active.

1

Read-in disable is suppressed.

Note

For more information on parameterizing MD11620, MD20108, and MD20107, see Section

"Parameterization (Page 66)."

Programming

The event by which the ASUP has been started is stored in the system variable $P_PROG_EVENT.

On automatic activation after a block search, $P_PROG_EVENT returns the value "5."

Sequence

Sequence of automatic start of an ASUB after a block search

1. User: Activation of the block search type 2 or type 4 (block search with calculation to ...) via

the operator interface

2. Search for the target block with collection of auxiliary functions

3. Stop after "Search target found ⇒ display of alarm 10208 "Continue program with NC start"

4. User: NC start to execute the action block s⇒ DB21, ... DBX7.1 = 1 (NC start)

5. Execution of the action blocks

Basic functions

Function Manual, 10/2020, 6FC5397-2GP40-0BA1

125

Mode group, channel, program operation, reset response

3.7 Block search, types 1, 2, and 4:

When the search target is reached, the program execution is stopped and the search target

displayed as current block. After each located search target, a new block search can be repeated

as often as you want.

Changing the search target specifications

You can change the search target specifications and block search function before every block

search start.

Example: Execution sequence with cascaded block search

• RESET

• Block search up to search target 1

• Block search up to search target 2 → "Cascaded block search"

• NC Start for output of the action blocks → Alarm 10208

• NC Start → Continue program execution

%ORFN VHDUFK DFWLYH

'%

'%;

$FWLRQ EORFN DFWLYH

'%

'%;

/DVW DFWLRQ EORFN DFWLYH

'%

'%;

&KDQQHO VWDWXV UHVHW

'%

'%;

&KDQQHO VWDWXV LQWHUUXSWHG

'%

'%;

Figure 3-2

Chronological order of interface signals

3.7.5

Examples for block search with calculation

Selection

From the following examples, select the type of block search that corresponds to your task.

Basic functions

Function Manual, 10/2020, 6FC5397-2GP40-0BA1

127

Mode group, channel, program operation, reset response

3.7 Block search, types 1, 2, and 4:

Type 4 block search with calculation at block end point

Example with automatic tool change after block search with active tool management:

1. Set machine data:

MD11450 $MN_ SEARCH_RUN_MODE to 1

MD11602 $MN_ASUP_START_MASK Bit 0 = 1 (ASUP Start from stopped state)

2. Select ASUP "BLOCK_SEARCH_END" from the PLC via FB4 (see also Function Manual "PLC and

Basic Program", Section "Basic PLC program").

3. Load and select part program "WORKPIECE_1".

4. Block search to block end point, block number N220.

5. HMI signals "Search target found".

6. NC Start for output of action blocks.

7. With the PLC signal:

DB21... DB32.6 (last action block active)

the PLC starts ASUB "BLOCK_SEARCH_END" via FC9 (see also Function Manual "PLC and Basic

Program", Section "Basic PLC program").

8. After the end of the ASUP (can be evaluated, e.g. via M function M90 to be defined, see

example for block N1110), the PLC sets signal

DB21, ... DBX1.6 (PLC action complete).

Alternatively, NC/PLC interface signal:

DB21-DB30 DBB318 bit 0 (ASUP is stopped)

can be scanned.

As a result, Alarm 10208 is displayed, i.e. other actions can now be performed by the

operator.

9. Manual operator actions (JOG, JOG-REPOS, overstoring)

10.Continue part program with NC Start.

\

7RRO FKDQJH SRLQW

$SSURDFK PRYHPHQW

7DUJHW EORFN 1

$SSURDFK SRLQW

[

Figure 3-3

Approach motion for block search to block end point (target block N220)

Note

"Block search at contour" with target block N220 would generate an approach motion to the

tool change point (start point of the target block).

Basic functions

128

Function Manual, 10/2020, 6FC5397-2GP40-0BA1

Mode group, channel, program operation, reset response

3.7 Block search, types 1, 2, and 4:

Type 2 block search with calculation at contour

Example with automatic tool change after block search with active tool management:

1. to 3.

Same as example for Type 4 block search

4.

Block search at contour, block number N260

5. to 10.

Same as example for Type 4 block search

\

7RRO FKDQJH SRLQW

$SSURDFK PRYHPHQW

$SSURDFK SRLQW

[

Figure 3-4

Approach motion for block search at contour (target block N260)

Note

"Block search to block end point" with target block N260 would result in Alarm 14040 (circle end

point error).

Part programs for Type 4 and Type 2

PROC WORKPIECE_1

Program code

Comment

; Main program

;Machine contour section 1 with "CUTTER_1"tool

N100 G0 G40 X200 Y200

; Deselect radius compensation

N110 Z100 D0

; Deselect length correction

;End of contour section 1

;

;Machine contour section 2 with "CUTTER_2"tool

N200 T="CUTTER_2"

; Preselect tool

N210 WZW

; Call tool change routine

N220 G0 X170 Y30 Z10 S3000 M3 D1

; Approach block for contour section 2

N230 Z-5

; Infeed

N240 G1 G64 G42 F500 X150 Y50

; Start point of contour

N250 Y150

Basic functions

Function Manual, 10/2020, 6FC5397-2GP40-0BA1

129

Mode group, channel, program operation, reset response

3.8 Block search Type 5 (SERUPRO)

3.8.2

Repositioning to the contour (REPOS)

The "Reposition to the contour" (REPOS) function can be used to continue an interrupted

machining at the interrupted location. Unlike REPOS, SERUPRO permits the "refetching" or

"repetition" of a program section. For this purpose, once SERUPRO has found the target block,

the contour is positioned at the location selected with REPOS mode and the machining

continued.

SERUPRO: Set REPOS response

The REPOS behavior, i.e. the behavior in the repositioning block, is set with the following

machine data:

MD11470 $MN_REPOS_MODE_MASK = <REPOS mode>

<REPOS mode>

Bit

Value

Meaning

0

0

An interrupted delay time is repeated

1

An interrupted delay time is continued

1

-

Reserved

2

0

DB31, ... DBX10.0 (REPOS delay) not considered in the repositioning deceleration

block.

1

DB31, ... DBX10.0 (REPOS delay) considered in the repositioning deceleration block.

3

0

SERUPRO: Only path axes traverse in the repositioning block

1

SERUPRO: Path and positioning axes traverse concurrently in the repositioning

block

4

0

REPOS: Only path axes traverse in the repositioning block

1

REPOS: Path and positioning axes traverse concurrently in the repositioning block

5

0

During the interruption, changed feedrates and spindle speeds act only after the

first part program block following the interruption location

1

Modified feedrates and spindle speeds during the interruption are valid immedi-

ately from the interruption point onward, i.e. they are already valid in the residual

block and are given priority. This behavior relates to every REPOS operation.

6

0

SERUPRO: In the repositioning block, neutral axes and positioning spindles traverse

as path axes.

1

SERUPRO: In the repositioning block, neutral axes and positioning spindles traverse

as command axes.

Neutral axes and positioning spindles are repositioned after SERUPRO.

For neutral axes, where it is not permissible to reposition them, the REPOS delay

must be set: DB31, ... DBX10.0 = 1 (REPOS delay)

7

0

The REPOS delay is not enabled.

1

The REPOS delay is enabled.

Axes with active REPOS delay (DB31, ... DBX10.0 == 1), which are neither geometry

nor orientation axes, are not traversed when repositioning.

Basic functions

Function Manual, 10/2020, 6FC5397-2GP40-0BA1

135

Mode group, channel, program operation, reset response

3.8 Block search Type 5 (SERUPRO)

CAUTION

Risk of collision

MD11470 $MN_REPOS_MODE_MASK, Bit 3 or Bit 4 = 1

The user alone is responsible for ensuring that the concurrent traversal of the axes in the

repositioning block does not cause any collision on the machine.

Repositioning with controlled REPOS

The REPOS mode can be specified for the path axes via the NC/PLC interface:

DB21, ... DBX31.0 - 2 (REPOS mode)

The REPOS mode is programmed in the NC program, and defines the approach behavior (see

Section "Repositioning with controlled REPOS (Page 142)").

The REPOS behavior of individual axes can also be controlled via NC/PLC interface signals, and

must be enabled using machine data:

MD11470 $MN_REPOS_MODE_MASK BIT 2=1.

Path axes cannot be influenced individually. For all other axes that are not geometry axes, REPOS

of individual axes can be prevented temporarily and also delayed. NC/PLC interface signals can

be used to subsequently re-enable or to continue blocking individual channel axes that REPOS

would like to traverse.

DANGER

Risk of collision

Signal DB31, ... DBX2.2 (delete distance-to-go) produces the following dangerous behavior

when function "Prevent repositioning of individual axes" is selected:

MD11470 $MN_REPOS_MODE_MASK.bit 2 == 1

As long as an axis is programmed incrementally after the interruption, the NC approaches

different positions than those approached with no interruption.

See the example below: Axis is programmed incrementally

Basic functions

136

Function Manual, 10/2020, 6FC5397-2GP40-0BA1

Content      ..     17      18      19      20     ..