104

Note the program line number where alarm occurred and review the O-number program on the CNC display or using EDIT mode.

Identify all variable references (#xxx) on the alarm line and verify each number is within valid range: #1-#33 local, #100-#199 common saved, #500-#999 common, #1000-#9999 system variables per your control model.

Check for indirect addressing like ##i where variable #i may calculate to zero, negative, or exceeds maximum. Insert a debug line before alarm to display calculated value: #3000=##i (displays on screen).

Correct the variable number to valid range or fix the calculation logic. If using system variables, consult parameter manual section 4 for your specific control series (0i, 30i, 31i, etc.) to verify valid system variable ranges.

System variable ranges differ between control models - using 31i variables on a 0i control will trigger this alarm

Examine the exact syntax at the alarm line. Look for: missing # symbol before variable number, spaces between # and number like '# 100', or letters mixed with numbers like '#1O0'.

Verify no decimal point appears in the variable identifier itself (e.g., #100.5 as identifier is illegal, though #100=5.5 is valid). The variable number must be a whole integer.

Check for special characters or invalid expressions like #[100+5] which may not be supported. Use proper indirect addressing format: ##100 or #[#100] depending on control series.

Correct syntax errors and verify program with 'O' search or background edit check if available. Compare against working programs using similar variable structures.

Use the control's search function to find ALL instances of the problematic variable format throughout the entire program

Check if variable #0 is being written to or used in calculations. #0 is null by definition and cannot be assigned a value - it can only be used to clear other variables like #100=#0.

#0 is permanently null and read-only - any attempt to assign a value to #0 triggers this alarm

Review program logic to ensure all variables are initialized before use. Add conditional checks: IF[#100NE#0]THEN #110=#100 to verify variable contains valid data before operations.

Check parameters 6000-6009 (macro variable access restrictions) and 6010-6019 (common variable range settings). Verify the variable range being accessed is enabled and not password protected.

Changes to 6000-series parameters require power cycle and may affect other programs - document current values before modification

If using custom macro B features, verify parameter 6001#0 (custom macro) is set to 1. Test with a simple variable assignment like #100=1 in MDI mode to confirm variable system is functioning.