PS112

Press RESET to clear the alarm, then navigate to the program screen to identify the exact line number where PS112 occurred. Note the O-number and sequence number displayed in the alarm history.

Review the macro program line containing division operations (e.g., #100=#101/#102 or IF[#10/#11 GT 5]). Check the CURRENT PROGRAM screen or MDI to examine macro variable values at time of alarm.

Navigate to SYSTEM > MACRO > VARIABLE to display current macro variable values. Verify the divisor variable (#xxx) is not zero or <null>. Check if the variable was properly initialized earlier in the program.

Add conditional logic before division operations (e.g., IF[#102 NE 0]THEN #100=#101/#102) or initialize variables at program start (#102=1.0) to prevent division by zero conditions.

Ensure the initialized value makes sense for the application to avoid incorrect calculations.

Check parameter 6001 (SYSTEM > PARAM > search 6001) to verify macro variable retention settings. Bit 0 (CVC) determines if common variables #100-#199 are retained at power-off.

Review program initialization section to ensure all variables used as divisors are assigned non-zero values before use. Pay special attention to subroutines that may be called with unexpected variable states.

If using system variables (#3xxx series) or read-only variables, verify they contain valid data. Navigate to SYSTEM > MACRO > VARIABLE and scroll to system variables to check current values.

Some system variables may read as zero in certain machine states (e.g., tool not in spindle, probe not triggered).

Modify the macro program to validate divisor variables before division operations. Use WHILE or IF statements to check for zero values and either assign defaults or trigger controlled alarm messages.

Identify the macro statement causing PS112 from the alarm screen. Break down complex expressions into separate assignment statements to isolate which division operation is failing (e.g., split #1=#2/[#3-#4] into #10=#3-#4, then #1=#2/#10).

Use single block mode (SINGLE BLOCK button ON) and navigate to SYSTEM > MACRO > VARIABLE screen. Step through the macro program using CYCLE START to monitor variable values changing in real-time and identify when divisor becomes zero.

Ensure machine is in a safe position and all axes are clear before stepping through motion commands.

Review input parameters passed to the macro via G65/G66 or direct variable assignment. Verify that calling programs or operator input (via #3xxx custom macro variables) provide valid ranges that prevent zero divisors in calculations.

Add range checking and error handling at the beginning of the macro. Use IF[ABS[#xxx] LT 0.0001]THEN #3000=100(USER ALARM) to trap invalid inputs before division operations occur.