509

Check current program structure

Press EDIT mode, then LIST PROG to view the main program. Look for M98 calls and note the subprogram numbers (P values). Count how many levels deep the calls go by following each M98 to its corresponding O-number subprogram.

Trace the call stack

Starting from the main program, manually trace each M98 call. Write down the call chain (e.g., Main->O1001->O1002->O1003...) until you reach the deepest level. If you count more than 10 levels, you've found the problem.

Use the SEARCH function in EDIT mode to quickly jump between O-numbers when tracing calls

Restructure program hierarchy

Reorganize the program structure to reduce nesting depth. Combine simple subprograms into larger ones, or restructure the call sequence to use fewer nested levels. Consider using G65 macro calls for some operations instead of M98 subprogram calls.

Test revised program

Load the restructured program and run it in single block mode first, then normal execution to verify the nesting alarm is resolved and machining operations remain correct.

Identify the failing line

Note the line number shown with the 509 alarm. Press EDIT mode and navigate to that line number using the cursor keys or SEARCH function to see which M98 call triggered the alarm.

Check for circular references

From the failing M98 line, trace the subprogram it calls. Look for any M98 calls within that subprogram that reference back to previously called programs. Create a map of all M98 calls to visualize the calling pattern.

Look for subprograms that call themselves (same O-number) or create loops like O1001->O1002->O1001

Break the recursive loop

Eliminate the circular reference by removing the problematic M98 call or restructuring the logic. If the recursion was intentional for repetitive operations, replace it with a proper loop using G91.1 or L-word repeat counts.

Verify program flow

Run the corrected program in Graphics mode first to verify the toolpath is correct, then execute in single block to confirm no recursion occurs.

Locate M98 lines with L-words

In EDIT mode, use the SEARCH function to find all instances of 'M98' in your program. Look specifically for M98 calls that include L-word repeat counts (e.g., M98 P1001 L5).

Calculate effective nesting depth

For each M98 with L-word, multiply the repeat count by the nesting depth of the called subprogram. If any combination exceeds 10 levels total, this is your problem source.

Remember that L5 means the subprogram runs 5 times consecutively, but each execution adds to the stack depth

Reduce L-word counts or restructure

Either reduce the L-word repeat counts to stay within the 10-level limit, or move the repetitive operations into the subprogram itself using coordinate shifts or variables instead of multiple calls.