Detailed description
2.8 Single block
Basic logic functions: Mode group, channel, program operation, reset response (K1)
Function Manual, 11/2006, 6FC5397-0BP10-2BA0
145
2.8.3 Single block stop: inhibit according to situation
Suppress stopping in single cases
Depending on
MD10702 $MN_IGNORE_SINGLEBLOCK_MASK (Prevent single block stop)
setting bits 0 to 12 = 1 can suppress stopping at the end of the block during the following
machining processes.
Program execution must not stop after single blocks in the case of the following even if
block-by-block processing is selected:
1. An internal Asub
2. during a user ASUP
3. Subroutines with the attribute DISPLOF
4. Intermediate blocks
5. Block search group blocks
6. Init blocks
7. Blocks, which cannot be reorganized
8. Blocks, which are not repositionable
9. A repositioning block, which contains no traversing information
10. A prerun/main run/synchronization block, due to REORG
11. at a Tool selection block.
12. At a GET block
13. During a single block type 2
Sequence
If an ASUB is activated during the single block, for example, execution of the ASUB is
completed. The deceleration movement does not take place until after the end of the ASUB
or the first IPO block in which single-block suppression is not activated. If the velocity is too
large for the deceleration to be performed in this block (with continuouspath mode G64
active), G64), further block changes are allowed.
For decoding single block, MD10702 is only effective with "internal ASUB", "user ASUB" and
"subroutines with the attribute DISPLOF". In these cases, it is already clear at the time of
interpretation that the block belongs to one of the above categories. In these cases, further
blocks can be generated.
SBLON in ASUB
The single block stop of an internal ASUP or user ASUP that is suppressed with MD10702
$MN_IGNORE_SINGLEBLOCK_MASK can be reactivated in ASUP by programming SBLON.
This functionality can be suppressed again with MD20117
$MC_IGNORE_SINGLEBLOCK_ASUB. The SBLON command then becomes ineffective.