Programming and Operating Manual (Milling)
114
6FC5398-4DP10-0BA1, 01/2014
Example:
EXTCALL ("D:\EXTERNE_UP\RECHTECKTASCHE")
Note
External subroutines must not contain jump statements such as
GOTOF
,
GOTOB
,
CASE
,
FOR
,
LOOP
,
WHILE
, or
REPEAT
.
IF-ELSE-ENDIF
constructions are possible.
Subroutine calls and nested
EXTCALL
calls may be used.
RESET, POWER ON
RESET and POWER ON cause external subroutine calls to be interrupted and the associated load memory to be erased.
Example
Processing of external customer USB memory stick
The "Main.mpf" main program is stored in NC memory and is selected for execution:
N010 PROC MAIN
N020 G0 X10 Y10
N030 EXTCALL ("D:\EXTERNE_UP\BOHRUNG")
N040 G0 X20 Y20
N050 M30
The "BOHRUNG.SPF" subprogram to be reloaded is located on the USB memory sticker.
N010 PROC BOHRUNG
N020 G1 F1000
N030 X=10 Z=10
N040 G0 X50 Y50
N050 M17
8.16
Timers and workpiece counters
8.16.1
Runtime timer
Functionality
The timers are prepared as system variables ($A...) that can be used for monitoring the technological processes in the
program or only in the display.
These timers are read-only. There are timers that are always active. Others can be deactivated via machine data.
Timers - always active
●
$AN_SETUP_TIME
Time since the last control power-up with default values (in minutes)
It is automatically reset in the case of a "Control power-up with default values".
●
$AN_POWERON_TIME
Time since the last control power-up (in minutes)
It is reset to zero automatically after each power-up of the control system.
Timers that can be deactivated
The following timers are activated via machine data (default setting).
The start is timer-specific. Each active run-time measurement is automatically interrupted in the stopped program state or for
feedrate-override-zero.
The behavior of the activated timers for active dry run feedrate and program testing can be specified using machine data.
