324

Review the active NC program at the alarm point. Identify if G70, G71, G72, or G73 is active and locate any G65 or G66 commands within the cycle definition or between the cycle call and its termination.

Check the program structure: G70-G73 cycles reference a sequence number range (P_Q_ format). Verify no G65/G66 calls exist within the referenced sequence number block that defines the cutting path.

Restructure the program by moving the macro call outside the G70-G73 cycle. Execute G65/G66 before initiating the repetitive cycle or after cycle completion (after the G70-G73 block executes fully).

Ensure G67 is used to cancel modal G66 macro calls before starting G70-G73 cycles if modal macros are active from previous program sections.

If macro functionality is required during the cycle, consider using non-interruption type subprogram calls (M98) instead, or incorporate the logic directly into the cycle path definition between the P and Q sequence numbers.

Search the NC program for M99 P____ commands within or during the execution of G70-G73 cycles. Check both the main cycle block and the sequence number range referenced by the P_Q_ addresses of the cycle.

Verify parameter 3406 bit 1 (M99 P-address jump enable). Navigate to SYSTEM > PARAM and check if this function is enabled. Note that even if enabled, it cannot be used during G70-G73 execution.

Do not modify parameter 3406 to resolve this alarm; the restriction is by design for program integrity.

Eliminate the M99 P-address from the repetitive cycle section. Use standard program flow with M99 (simple return) or restructure using M98 subprogram calls that complete normally without interruption-type jumps.

If complex program branching is required, complete the G70-G73 cycle first, then implement M99 P-address or G65/G66 macro logic in subsequent program blocks after the cycle terminates.

Review program sections preceding the G70-G73 cycle for G66 modal macro call commands. Trace backward from the alarm point to identify if G66 was issued without a corresponding G67 cancellation.

Insert G67 (modal macro call cancel) immediately before the G70, G71, G72, or G73 command to ensure no modal macros are active when the repetitive cycle begins execution.

Check program structure for proper pairing: every G66 should have a corresponding G67. Implement G67 at program initialization (near program start) and before all G70-G73 cycles as preventive measure.

Verify the macro program called by G66 is not creating additional nested interruptions. Check the custom macro program for any internal G65 calls or M99 P-address commands that might compound the interruption issue.

After correcting, perform a dry run with single block execution to confirm G67 properly cancels the modal call before the repetitive cycle executes.