1095

Press EDIT key, search for the program number displayed with alarm 1095 (typically shown as program name or O-number in alarm message). Navigate to PROGRAM screen and locate the specific N-block number if referenced.

Examine the macro call statement for I, J, K arguments using indirect addressing (e.g., I#100 J#101 K#102 repeated more than 10 times). Count all I, J, K argument pairs/sets within the single block or G65 macro call statement.

Restructure the macro program to reduce type-II argument sets to 10 or fewer. Break complex calculations into multiple macro calls using G65 P____ with separate argument sets, or use direct assignment to local variables within the macro body instead.

Ensure macro variable numbers (#100-#199 for local variables, #500-#999 for common variables) are correctly referenced per Fanuc macro programming standards.

Verify parameter 6000#0 (macro executor enable) is set to 1 if alarm persists. Reset alarm using RESET key and re-execute program in single block mode (press SINGLE BLOCK key) to confirm correction.

Navigate to SYSTEM > PROGRAM > display the affected macro program (typically O9000-O9999 range for user macros). Scroll through entire program checking for garbled characters, missing EOB markers (;), or unexpected special characters in I, J, K argument fields.

If using battery-backed SRAM, check battery voltage at DIAGNOSIS > PMC > BATTERY screen or amplifier LED indicators for low battery condition.

Compare the CNC-resident macro program against the original proven backup file. Use EDIT mode to list entire program to external device (CF card, USB, or RS-232C) and perform byte-by-byte comparison with master program.

Delete corrupted program using O____ DELETE operation in EDIT mode. Re-transfer the validated macro program from external source using proper communication settings: parameter 0020 (I/O channel), 0101-0104 (baud rate, stop bits, parity), ensuring XON/XOFF or DC codes match.

Always backup all CNC programs and parameters to CF card or external device before deletion operations. Use SYSTEM > FILE > BACKUP function.

Execute a full parameter initialization check by reviewing parameters 6000-6009 (macro settings) for correct configuration. Confirm parameter 3202#4 (macro alarm enable) is properly set to generate appropriate macro alarms.

Identify all nested macro calls in the program structure. Navigate to EDIT screen, search for all G65 P____ statements, and document the macro call hierarchy (parent program calling sub-macros). Check parameters 6001-6009 for macro call nesting limits.

Review each nested macro level for I, J, K argument usage. Calculate cumulative type-II argument sets across all nesting levels. Fanuc controllers track argument context across nesting, and cumulative indirect arguments may trigger alarm 1095.

Maximum macro nesting depth is typically 4 levels (parameter 6009). Exceeding this causes separate alarm 3004.

Refactor nested macros to use common variable passing (#500-#999 range) instead of argument passing through I, J, K parameters. Assign values to common variables in parent macro, read them directly in child macros without G65 argument specification.