313

Navigate to SYSTEM > PARAM and locate Parameter 5130 (maximum thread lead increment for variable-lead threading). Note the current value in millimeters or inches depending on system units (G20/G21).

Review the program line causing alarm 313 and verify the K address value. For G34 (variable-lead threading increasing), check that K value does not exceed Parameter 5130. Calculate total lead change: initial lead (F) + (K × number of spindle revolutions).

Either reduce the K value in the program to stay within Parameter 5130 limits, or increase Parameter 5130 if the application requires larger lead increments and machine mechanics support it.

Increasing Parameter 5130 requires understanding of machine mechanical limits, spindle synchronization capabilities, and maximum axis feed rates. Consult machine builder specifications before modification.

After correction, reset alarm with RESET key, return to program start or safe line, and test threading cycle in single block mode with feedrate override at 50% to verify proper execution.

Examine the G34 or G35 block in the program where alarm occurred. Verify the K address does not contain a minus sign (e.g., K-0.5 is invalid). Also check for variable assignments (#100=-0.5 followed by K#100) that may pass negative values.

If decreasing lead is required, use G35 (variable-lead threading decreasing) with a positive K value instead of G34 with negative K. G35 is specifically designed for threads with decreasing pitch.

Correct the program by removing the negative sign and ensuring proper G-code selection (G34 for increasing lead, G35 for decreasing lead). Verify F address (initial lead) is also positive and within valid range.

Reset alarm, verify program logic in EDIT mode, and dry run the corrected threading cycle with spindle override to confirm proper lead progression without actual cutting.

If K address references a macro variable (e.g., K#500), navigate to SYSTEM > MACRO > VARIABLE and check the current value of the referenced variable. Verify it is defined, positive, and within Parameter 5130 limits.

Review macro program logic for calculation errors. Check arithmetic operations that compute K value for divide-by-zero, overflow conditions, or operations that could produce negative results. Insert M00 and use DPRNT or external variable monitoring to debug values.

Add conditional checks in macro program before G34/G35 execution: IF[#500 LE 0]THEN #3000=1(K VALUE ERROR). Ensure variable initialization at program start and validate calculated values are within acceptable range.

Test corrected macro program in single block with background edit enabled. Monitor variable values in real-time through SYSTEM > MACRO > VARIABLE screen during execution to confirm proper K value calculation.

Macro variable #3000 generates operator message alarm. Use this for custom validation but ensure it does not interfere with production cycle if improperly triggered.