HEIDENHAIN TNC 335 Technical Manual - Manual (Page 554)

9-2
TNC 360 1 Introduction 8/95
1 Introduction
OEM cycles (customized macros) are programmed in HEIDENHAIN dialogue as NC programs.
OEM cycles cannot be created in ISO format!
By using these cycles in a main program created in the HEIDENHAIN dialogue or in accordance with
ISO, repetitive machining tasks or machine-specific functions can be executed with a single call. The
execution of OEM cycles can be influenced by parameter transfer (see also TNC User's Manual).
OEM cycles can be divided into "DEF-active" and "CALL-active" OEM cycles. The DEF-active cycles
are effective immediately upon definition, without CYCL CALL, M89 or M99. The CALL-active cycles
must be called with a CYCL CALL, M89 or M99.
Up to 32 different OEM cycles can be produced, tested and stored in the NC program memory.
In order not to tie up the NC program memory (RAM) with the OEM cycles and their dialogues, it is
possible to store this data in the PLC EPROM.
Permitted functions in OEM cycles
– Tool call.
– M functions apart from M02, M30, M06, without program-run stop.
– Nesting OEM cycles:
Other OEM cycles or standard cycles can be called in the OEM cycles (nesting depth four levels).
– Calling OEM cycles from a main programs that is transmitted "blockwise" and executed
simultaneously. The OEM cycles must be stored in the control unit memory (EPROM or RAM).
– Calling HEIDENHAIN dialogue or ISO programs in OEM cycles. The called programs are not
displayed.
Functions not permitted in OEM cycles
– M functions M02, M30, M06 with program-run stop.
– Programmed STOP block.
– Definition of cycle 14 "Contour":
Cycle 14 "Contour" must be defined in the main program.
– Repetition of sections of program with CALL LBL ... REP .../...:
OEM cycles with program-section repeats stored in PLC EPROM cannot be executed. However,
program-section repeats can also be programmed via the Q parameter function (IF ... GOTO LBL
...) (see the "Bolt hole circle" example).