Guide to Nested Subprograms on Fanuc, Siemens, and Mitsubishi

Introduction

An uncommanded incremental positioning shift that crashes the machine turret directly into a vise jaw, chuck, or clamp is the immediate physical consequence of failing to manage active modal states across nested subprogram levels. When a nested subprogram modifies coordinate systems, switches to incremental positioning (G91), or alters feedrates but terminates with a return block (M99 or M17) before restoring the calling program's absolute coordinate system (G90), subsequent paths will execute from incorrect relative positions. The operator sees the axis shift unexpectedly off-path, followed by a violent collision that shatters the tool, damages the spindle, and turns the workpiece into scrap. Preventing these catastrophic system halts requires programmers to establish strict coordinate isolation, understand hardware-specific nesting boundaries, and configure search parameters across Fanuc, Siemens, and Mitsubishi controls.

Technical Summary

Technical Specification	Details
Command Codes	Fanuc: M98, M198, M99 Siemens: Alphanumeric Name, PROC, M17, RET Mitsubishi: M98, M198, M99
Modal Group / Modality	Subprogram Call and Return Control / Modal-Code
Brands Covered	Fanuc, Siemens, Mitsubishi
Critical Parameters	Fanuc: 3457 (Search path), 0010#4 (PRG9) Siemens: SAVE attribute, VAR keyword Mitsubishi: #8876 (M198 device), #8129 (Search priority)
Main Constraint	Nesting depth: Max 4 levels (Fanuc), Max 8/16 levels (Siemens), Max 8/10 levels (Mitsubishi). No nested external M198/EXTCALL calls.

Quick Read

• Modal State Restoration: Explicitly restore absolute coordinates (G90) and cancel compensations immediately before the subprogram return block to prevent coordinate bleeding.
• Nesting Limit Boundaries: Keep nested calls within the strict hardware-defined depth limits of 4 levels for Fanuc, 8 to 16 for Siemens, and 8 to 10 for Mitsubishi.
• Subprogram Parameter Lock: Lock editing permissions for O8000 and O9000 macro series on Fanuc by setting parameters 0389#2 (PRG8) and 0010#4 (PRG9) to 1.
• External Media Calls: Execute larger files directly from memory cards or data servers using M198 (Fanuc/Mitsubishi) or EXTCALL (Siemens) to bypass internal memory constraints.
• Direct Storage Routing: Route Mitsubishi subprograms to specific hardware storage media in the call block using the local ,D address (0 to 4).
• Automated Modal Save: Declare the SAVE attribute in Siemens PROC headers to automatically save and restore coordinate frames and modal G-codes.

Basic Concepts

The practical programming effect of nested subprograms is the ability to highly compress complex, repetitive tool paths by stacking sub-routines inside one another, dramatically reducing memory consumption and simplifying edits for features like grid hole patterns or roughing passes. Instead of repeating identical geometric blocks in the main program, developers can write these routines once as standalone files and call them sequentially. This modular structure keeps program sizes small and allows programmers to update specific machining sections without editing the entire master file. If you are new to subprograms, check our guide on writing and calling subprograms to understand the basics.

Control brands diverge in how they locate, call, and execute these sub-level files. Legacy platforms require strict numeric O-number naming conventions, while modern controls allow descriptive alphanumeric names. Subprograms can also be executed modal-like across different coordinates, or streamed dynamically from external hardware interfaces to bypass internal memory constraints entirely. Because a subprogram executes as an active extension of the calling program, modal states like feedrates and positioning coordinates flow fluidly across levels, requiring strict programming practices to avoid coordinate bleeding. For related cycle techniques, you can refer to the G83 deep hole peck drilling cycle and the G84 rigid tapping cycle.

Command Structure

The syntax and structure of a nested subprogram call require the control's interpreter to parse the target program name or number, the starting block, and the repetition count. In traditional environments, the M98 command initiates a jump, redirecting execution to the subprogram stored in the CNC memory. Once the interpreter reads the subprogram, it executes the blocks sequentially. Upon reaching the end of the subprogram, a return block redirects the execution pointer back to the calling program. If repetitions are specified, the interpreter loops through the subroutine the commanded number of times before resuming the main program sequence.

Siemens controls implement a highly advanced, alphanumeric naming system where subprograms are called directly by their filenames. Rather than relying on rigid O-numbers, Siemens subroutines can accept parameters passed by value or reference, which are declared in a PROC header. The return from a Siemens subroutine is terminated using M17 or RET. In contrast, Fanuc and Mitsubishi utilize legacy register architectures, requiring macro options to transfer values, or forcing programmers to rely on volatile common or global variables. The parameters and syntax addresses govern how the control searches, repeats, and returns from these routines.

Command Syntax Addresses:

• Fanuc Standard Call: M98 P_ L_ ;
• Fanuc External Call: M198 P_ ;
• Fanuc Return: M99 ;
• Siemens Definition: PROC <program name> (<ParamType> <ParamName>, VAR <ParamType> <ParamName>) [SAVE]
• Siemens Call: <program name> (<Param1>, <Param2>) or MCALL <program name>
• Siemens Return: M17 or RET
• Mitsubishi Standard Call: M98 P__ H__ L__ ,D__ ; or M98 <file name> H__ L__ ,D__ ;
• Mitsubishi External Call: M198 P__ L__ ; or M198 <file name> L__ ;
• Mitsubishi Return: M99 P__ ;

Parameter / Address	Control Brand	Description	Value Range / Settings
P	Fanuc / Mitsubishi	Program number identifier of the subprogram to call.	Up to 8 digits
L	Fanuc / Mitsubishi	Number of repetitive executions for the subroutine.	1 to 9999
H	Mitsubishi	Starting sequence number (N-number) within the called subprogram.	Valid N-number
,D	Mitsubishi	Explicit device number routing for searching files.	0 to 4
<file name>	Mitsubishi	Direct alphanumeric name call of the subprogram file.	Up to 32 characters
PROC parameter types	Siemens	Data types accepted by the subroutine (e.g., REAL, INT, CHAR, BOOL).	Standard variable types
VAR	Siemens	Keyword to declare that a parameter is passed by reference.	Keyword
SAVE	Siemens	Attribute to save and restore active modal settings and frames.	Attribute flag

Brand Applications

Fanuc CNC Integration

Fanuc's nested subprogram environment uses parameter-driven mechanisms to manage access and safety. In this system, parameter 0010#4 (PRG9) restricts access to the 9000-series macro programs, while parameter 0389#2 (PRG8) performs the same function for 8000-series programs.

To invoke a standard nested subroutine, programmers program an M98 block specifying the program number and loops, such as: M98 P1000 L5 ;. External routines are streamed using: M198 P50 ;, while subprograms end with: M99 ;.

Type	Name / Code	Description and Settings
Parameter	0010#4 (PRG9)	Prohibits editing of subprograms 09000 to 09999 when set to 1 (not prohibited when 0).
Parameter	0389#2 (PRG8)	Prohibits editing of subprograms 08000 to 08999 when set to 1 (not prohibited when 0).
Parameter	3404#2 (SBP)	Specifies if address P in M198 refers to file number (0) or program number (1).
Parameter	6005#0 (SQC)	Determines if subprogram sequence number call is not used (0) or used (1).
Parameter	3457	Configures the folder hierarchy search path (LIB, MC1/MC2, SYS folders) to locate files.
Alarm	0077	TOO MANY SUB, MACRO NESTING: Nesting depth exceeded, or nested M198 call.
Alarm	1080	DUPLICATE DEVICE SUB PROGRAM CALL: Nested M198 call inside active M198 program.
Alarm	1091	DUPLICATE SUB-CALL WORD: Multiple call words found in the same block.
Alarm	0076	PROGRAM NOT FOUND: Called subprogram number not found in memory or folder paths.
Version	0001#1 (FCV)	Legacy tape compatibility. Setting to 1 parses P-code to merge repetition and program number.

Warning: Neglecting to switch from incremental positioning back to absolute positioning before the M99 command will cause coordinate offset drift, leading to hard collisions.

Siemens SINUMERIK Integration

Siemens SINUMERIK systems do not use numerical O-numbers, instead invoking subroutines directly by their alphanumeric names. Program parameters can be passed to these subroutines using the PROC command in the subroutine declaration.

To call a subprogram by name, use: SUB_NAME(parameters). The return block is written as: M17 or RET, with RET allowing multiple level jumps like: RET("N200", 2) ;.

Type	Name / Code	Description and Settings
Parameter	PROC Param Types	Formal parameter data types accepted by the subprogram (e.g., REAL, INT, CHAR, BOOL).
Parameter	VAR	Keyword to declare that formal parameters are passed by reference rather than value.
Parameter	SAVE	Attribute that automatically saves and restores modal G-codes and coordinate frames upon return.
Alarm	14012	Maximum subroutine level exceeded: Exceeding nesting depth (8 levels for 808D, 16 levels for 840D/828D).
Alarm	14011	Program not existing or will be edited: Subprogram file missing or currently open in HMI editor.
Alarm	14013	Number of subroutine passes invalid: Subroutine repeat count invalid or out of range.
Version	808D vs 828D/840D sl	SINUMERIK 808D restricts nesting to 8 levels, while 828D and 840D sl support up to 16 levels.

Warning: Calling an active subprogram file that is currently being edited in HMI will instantly trigger Alarm 14011 and halt the machine.

Mitsubishi CNC Integration

Mitsubishi controllers support direct physical storage media routing inside the call block. Programmers configure storage destinations using parameters #8876 and #8880 to map device destinations to the local ,D address.

To call a subprogram from the card reader using sequence start block N100, program: M98 <PATTERN.PRG> H100 ,D1 ;. Return to the calling program is terminated via: M99 ;.

Type	Name / Code	Description and Settings
Parameter	#8876	Storage device configuration for M198 external subprogram calls (G=HD, R=M-Card, D=Server, N=USB).
Parameter	#8880 to #8884	Maps device destinations to addresses ,D0 through ,D4 (M=Memory, E=Memory 2, G=HD, R=M-Card, D=Server).
Parameter	#8129	Subprogram search priority (0=commanded program number, 1=4-digit O-number, 2=8-digit O-number).
Alarm	P230	Subprogram nesting over: Exceeding nesting depth, or M198 call inside data server program.
Alarm	P231	No sequence No.: The return block sequence number destination (M99 P) not found in calling program.
Alarm	P232	No program No.: Commanded program number or angle-bracket filename not found in specified device.
Version	M70V vs M80V	M70V/M700V series support nesting up to 8 levels deep, while modern M80V/M800V support up to 10 levels.
Version	M800VW vs M800VS	If parameter #8876 is blank, M800VW/M80VW defaults to Data server, while M800VS/M80V defaults to Front-side SD card.

Warning: Disrupting the connection to external storage during execution will trigger a P232 alarm and cause a dangerous emergency stop mid-cycle.

Brand Comparison

Topic	Fanuc	Siemens	Mitsubishi
Subprogram Call Command	M98 (Internal), M198 (External)	Alphanumeric program name or CALL / PCALL / MCALL	M98 (Internal/External), M198 (External)
Return Command	M99	M17 or RET	M99
Alphanumeric Names	— (no source)	Yes (direct name designation)	Yes (using <filename> syntax)
Max Nesting Depth	4 levels (8 with macros)	8 levels (808D), 16 levels (840D sl / 828D)	8 levels (M70V), 10 levels (M80V)
Parameter Passing	— (no source)	Yes (local parameters declared in PROC)	— (no source)
Storage Media Selection in call	Global search folder parameter (3457)	Path search / Memory	Yes (via ,D device address in block)
Mode retention on return	Manual restoration	Automatic (via SAVE attribute on PROC)	Manual restoration

Technical Analysis

An analytical review of these three CNC architectures reveals different approaches to subprogram execution, memory scoping, and parameter transfer. Siemens models its execution on high-level PC programming languages, allowing programmers to define local scopes and parameter passing mechanisms directly in the subprogram header. By using the VAR keyword in the PROC line, Siemens enables call-by-reference execution, allowing subprograms to modify and return calculations to the parent program. Fanuc and Mitsubishi utilize legacy register architectures, requiring macro options like G65 or G66 to transfer values, or forcing programmers to rely on volatile common or global variables, which introduces the risk of modal data corruption.

Nesting hierarchies also reflect distinct hardware philosophies. Fanuc's 4-level nesting limit requires programmers to maintain simplified, shallow call trees. Siemens provides up to 16 nesting levels, but because these levels are shared dynamically between user subprograms, standard canned cycles, and manufacturer OEM background routines (such as spindle speed clamps or turret control macros), this budget can be quickly depleted. Mitsubishi occupies a middle ground, offering 8 levels on legacy M70V series and 10 levels on newer M80V controls. Exceeding these limits on any control immediately halts execution, demonstrating the necessity of tracing call depths across all active systems.

Directory routing and safety controls differentiate these platforms. Fanuc utilizes parameter 3457 to search a rigid, automated folder hierarchy, while Mitsubishi allows direct physical routing via the ,D address or angle-bracket filenames like <PART.PRG>. Siemens isolates subprogram calls to the local workpiece directory unless an EXTERN declaration is declared. Siemens enforces an HMI edit safety lock (version 5 and higher) that prevents NC Start if the called file is open on the screen, a feature not natively present on Fanuc or Mitsubishi systems.

Program Examples

Fanuc Nested Subprogram Example

This example demonstrates a main program (O0001) calling a nested subprogram (O1000) five times to perform repetitive coordinate-shifted cuts.

O0001 (MAIN PROGRAM) ;
"
"G90 G54 G00 X0 Y0 Z10.0 ; Pre-position axes to workpiece absolute zero
"
"M98 P1000 L5 ; Call subprogram O1000 five times sequentially
"
"G00 Z50.0 M30 ; Retract Z axis and terminate main program ;
"
"O1000 (SUBPROGRAM) ;
"
"G91 G01 Z-2.0 F150 ; Switch to incremental mode, feed Z axis down by 2.0 mm
"
"G90 G01 X50.0 F300 ; Switch back to absolute positioning, feed X axis to 50.0 mm
"
"G91 G01 Z2.0 ; Incremental Z axis retract by 2.0 mm
"
"G90 G01 X0 ; Absolute X return to zero
"
"M99 ; Return control to main program

dry run

During a dry run, the Fanuc controller moves the machine axes to X0, Y0, and Z10.0 in absolute positioning mode. Upon reading M98 P1000 L5, it jumps to subroutine O1000. In O1000, the controller switches to incremental mode (G91) to plunge Z by 2.0 mm, then reverts to absolute mode (G90) to cut to X50.0. After doing an incremental retract of Z by 2.0 mm, the tool returns to X0 in absolute mode. The controller executes this entire subprogram loop five times in total, leading to a total incremental Z depth of 10.0 mm. It then returns to the main program, retracts to Z50.0, and ends the cycle via M30.

Siemens Alphanumeric Subprogram Example

This program utilizes Siemens alphanumeric calling conventions with parameter passing in a PROC header, automatically protecting the coordinate system using the SAVE attribute.

; Main Program (MAIN_PROG.MPF)
"
"N10 G90 G54 G00 X0 Y0 Z10.0 ; Pre-position tool to absolute zero
"
"N20 MCALL CUT_POCKET(3.0, 150.0) ; Modally register subroutine CUT_POCKET
"
"N30 X50.0 Y50.0 ; Automatically execute subprogram at coordinate 1
"
"N40 X100.0 Y50.0 ; Automatically execute subprogram at coordinate 2
"
"N50 MCALL ; Deselect the modal subprogram call
"
"N60 G00 Z50.0 M30 ; Retract Z and end main program ;
"
"; Subprogram CUT_POCKET.SPF (stored in SPF directory)
"
"PROC CUT_POCKET(REAL DEPTH, REAL FEED) SAVE DISPLOF ;
"
"G91 G01 Z=-DEPTH F=FEED ; Incremental plunge based on DEPTH parameter
"
"G90 G01 G41 X0 Y0 ; Absolute positioning with tool radius compensation active
"
"G03 X0 Y0 CR=25.0 ; Interpolate circular pocket profile
"
"G40 G01 X0 Y0 ; Cancel tool radius compensation
"
"G91 G01 Z=DEPTH ; Incremental retract of Z axis
"
"M17 ; End subroutine and return control

dry run

In a dry run of the Siemens program, the controller first executes absolute positioning to X0, Y0, and Z10.0. The MCALL command in block N20 registers CUT_POCKET as a modal subroutine. Moving to N30 (X50.0 Y50.0) positions the axes, pauses, and calls the subroutine with parameter values 3.0 and 150.0. The subroutine begins execution under the SAVE attribute, which captures the active absolute state of the parent program. It performs the pocket cut using incremental moves, retracts, and returns via M17. The control automatically restores the absolute G90 state and proceeds to N40 (X100.0 Y50.0) to repeat the process. Finally, block N50 cancels the modal routine call before Z retracts to 50.0 mm and ends with M30.

Mitsubishi Alphanumeric Subprogram Example

This program demonstrates Mitsubishi's ability to call an alphanumeric filename from a specific storage device using the ,D parameter address.

O0002 (MAIN PROGRAM) ;
"
"G90 G54 G00 X0 Y0 Z10.0 ; Pre-position tool to workpiece absolute zero
"
"M98 <ROUGH-CUT.PRG> H200 L3 ,D1 ; Call file ROUGH-CUT.PRG from device 1 starting at sequence N200
"
"G00 Z50.0 M30 ; Retract and terminate main program ;
"
"; ROUGH-CUT.PRG (stored on CF Card - Device 1)
"
"O2000 (SUBPROGRAM) ;
"
"N100 G01 Z-5.0 F100 ; This block is bypassed due to sequence search block H200
"
"N200 G91 G01 Z-2.0 F120 ; Subroutine execution starts here; incremental feed
"
"N300 G90 G01 X30.0 Y30.0 F250 ; Absolute positioning tool path cut
"
"N400 G91 G01 Z2.0 ; Incremental Z retract by 2.0 mm
"
"N500 G90 G01 X0 Y0 ; Return to absolute X0 Y0 position
"
"M99 ; Return control to main program

dry run

During a dry run on the Mitsubishi system, the tool is pre-positioned at X0, Y0, and Z10.0. When executing the M98 block, the controller accesses device 1 (the CF Card) to open the file ROUGH-CUT.PRG. It searches the subroutine for block N200 as specified by address H200. block N100 is skipped entirely. Execution starts at N200 with an incremental Z move, followed by absolute profiling cuts. The tool then retracts, returns to absolute coordinates, and encounters the M99 block. The controller repeats this loop three times before returning to the main program to retract Z and end via M30.

Error Analysis

Brand	Alarm Code	Trigger Condition	Operator Symptom	Root Cause / Fix
Fanuc	0076	Called program number not found in memory or search folders.	The machine halts instantly, showing a "PROGRAM NOT FOUND" error message.	Check parameter 3457 folder paths and verify the O-number file is present in memory.
Fanuc	0077	Subprogram or macro nesting depth exceeds the maximum permissible limit.	The CNC halts mid-cycle, presenting a "TOO MANY SUB, MACRO NESTING" error.	Verify execution nesting levels do not exceed 4 (or 8 including macro calls).
Fanuc	1080	Nested M198 external device call executed within an active M198 subprogram.	The controller freezes execution and displays a "DUPLICATE DEVICE SUB PROGRAM CALL" error.	Avoid nested M198 calls. Transfer secondary subroutines to internal SRAM.
Fanuc	1091	More than one subprogram call instruction specified in the exact same block.	The interpreter halts and outputs a "DUPLICATE SUB-CALL WORD" error.	Isolate each subprogram call command into its own block.
Siemens	14011	Called subroutine is missing, unreleased, or open for editing.	The controller halts execution, displaying a "program not existing or will be edited" message.	Close the file in the HMI to release the edit lock. Verify path in _N_SPF_DIR.
Siemens	14012	Nesting depth limit of program levels is exceeded.	The system stops with a "maximum subroutine level exceeded" message.	Review nesting levels. Siemens canned cycles consume up to 3 levels; structure calls at level 12 or above.
Siemens	14013	Number of subroutine passes is specified incorrectly or is out of range.	The control rejects execution, showing "Number of subroutine passes invalid".	Check and correct the number of passes value in the subroutine call.
Mitsubishi	P230	Subprogram nesting depth exceeded, or M198 call made inside data server program.	The control halts and displays a "Subprogram nesting over" error.	Verify nesting levels do not exceed 8 (M70V) or 10 (M80V). Restructure M198 calls.
Mitsubishi	P231	Sequence number designated as the return destination cannot be found in calling program.	The interpreter faults out, displaying a "No sequence No." error.	Verify that the sequence number programmed after P in the M99 block exists in the calling program.
Mitsubishi	P232	Designated program number or filename not found in specified device.	Execution stops, showing a "No program No." error.	Verify device insertion, parameter mapping of addresses, and name length under 32 characters.

Application Note

A severe spindle crash that shatters carbide tooling and scraps the workpiece is the direct physical consequence of failing to isolate coordinate changes inside nested subprograms. When a subroutine alters positioning to incremental (G91) or shifts the coordinate system but exits via M99 or M17 without reverting to absolute (G90), the interpreter carries the modified coordinate system back to the calling level. The operator sees the axis traverse off-path, driving the tool spindle directly into a chuck, vise jaw, or securing clamp. To secure operations, programmers must establish a strict policy of restoring all coordinate modes and canceling compensations immediately before the subroutine return command. On Fanuc systems, parameters 0010#4 (PRG9) and 0389#2 (PRG8) must be locked to prevent operators from editing tool-change or measurement macros.

Related Command Network

• writing-and-calling-subprograms: Establishes the foundational logic of subroutine organization, showing the transition from single programs to modular calls.
• g83-deep-hole-peck-drilling-cycle: Invokes a peck drilling canned cycle that can be nested inside custom subprograms to handle deep-hole grid patterns.
• g84-g74-rigid-tapping: Calls a rigid tapping cycle within nested subroutines to automate internal threading across multiple coordinate locations.
• G65 Simple Macro Call: Executes a macro program for a single block while passing local variables to macro registers, similar to subprogram calls but with parameter support.
• G66 Modal Macro Call: Instructs the control to execute a macro subroutine modally after every subsequent motion block until canceled.

Conclusion

Deploying a standardized programming checklist is the most effective method for eliminating coordinate shifts and nesting depth alarms in CNC manufacturing. Placing coordinate system restores (G90) and active compensation cancels (G40, G49) immediately before any return block (M99 or M17) secures the calling program's tool paths. Locking subprogram edit parameters and verifying nesting limitations on each machine series prevents unauthorized changes and buffer overflows, ensuring stable, crash-free automated production runs.

Frequently Asked Questions

Why does a nested subprogram cause coordinate shifts in the calling program?

Coordinate shifts occur when modal commands, such as G91 incremental positioning or coordinate system rotations, are not explicitly restored inside the subprogram before returning. The controller continues to execute the remaining main program coordinates using the modified modal values, which shifts the entire tool path relative to the workpiece. Practical Action: Place a modal reset block containing G90 and any active compensation cancel codes (G40, G49) immediately before the M99 or M17 return block.

How can we prevent operators from accidentally modifying nested macro subprograms?

Critical subroutines, such as tool-change macros and probe programs, are typically registered under program numbers in the 8000 and 9000 ranges. If editing permissions are left open, operators can easily overwrite or delete files during setup, resulting in axis collisions during automated runs. Practical Action: On Fanuc systems, change parameter 0010#4 (PRG9) to 1 to lock 9000-series programs, and set parameter 0389#2 (PRG8) to 1 to lock 8000-series programs.

What is the difference between call-by-value and call-by-reference parameter passing in subprograms?

Call-by-value passes a static copy of a variable's value to the subroutine, protecting the main program's variable from being modified by the subprogram. Call-by-reference, declared using the VAR keyword in Siemens, passes direct access to the variable's memory address, allowing the subprogram to overwrite and return the new value back to the parent program. Practical Action: Use the VAR keyword in the PROC definition line only when you want the subprogram to update and return modified parameters to the main program.