451

Identify the program line number where the alarm occurred from the control display or alarm history.

Review the program block for any G-codes or M-codes that are not supported in multi-spindle mode (check your machine-specific programming manual for restricted commands).

Verify that canned cycles (G73, G74, G76, G83, G84, etc.) used are compatible with multi-spindle operations and properly formatted with correct address codes.

Remove or replace the illegal command with multi-spindle compatible programming, or restructure the program to execute incompatible commands outside of multi-spindle mode.

Check the program block at alarm for proper spindle address format (verify whether your system uses S1=/S2=, or other addressing method per your control specifications).

Verify that all spindle addresses referenced in the program correspond to physically available spindles on your machine configuration.

Ensure that spindle commands are not mixed between single-spindle format (S____) and multi-spindle format in the same block or mode.

Correct the spindle addressing syntax to match the required format for your specific Fanuc control and multi-spindle configuration, then reset and restart the program.

Review the program sequence leading up to the alarm for any commands that would cause spindle conflicts (e.g., both spindles commanded to different modes simultaneously).

Check for proper use of spindle synchronization commands (such as G199/G198 or machine-specific sync codes) and verify they are correctly paired and sequenced.

Verify that tool change commands, spindle orient commands (M19), and other preparatory functions are properly coordinated and not creating timing or operational conflicts.

Restructure the program sequence to eliminate conflicts, ensuring proper spindle mode transitions, adequate dwell times if needed, and correct synchronization command usage.

Always perform a dry run in single block mode after modifying multi-spindle synchronization to verify safe operation.