22058

Review the NC program block sequence around the alarm location. Identify the COUPLE command that triggered alarm 22058 and note the spindle numbers involved (leading and following).

Check all active COUPLE statements in the running program or initialization code. Use Siemens SINUMERIK debugging tools to inspect the current coupling state via MD 37100 (Spindle coupling) parameters and the coupling register. Verify which spindles are currently configured as leading versus following members.

Inspect HMI > Diagnosis > Parameters > Machine Data > Spindle Data (MD 37xxx) to view real-time coupling status.

If chained couplings are functionally required, restructure the NC program to DECOUPLE the first coupling before establishing the second. Ensure the leading spindle in the new coupling is not an active following member in any existing coupling.

SINUMERIK does not support multi-level coupling hierarchies; all couplings must share the same leading spindle or involve different spindle sets entirely.

Verify MD 37110, MD 37120, and MD 37130 (spindle coupling parameters) are correctly configured for your application topology. Confirm that the coupling definition does not inadvertently reference spindles that are already bound in other couplings via initialization data or macro calls.

Access HMI > Parameters > Machine Data > Spindle and check MD 37110 (Spindle coupling enable flag) and MD 37115 (Spindle coupling spindle assignment). Document the preconfigured coupling relationships defined at machine startup.

Cross-reference the machine data coupling assignments with the COUPLE command in the failing NC block. If the leading spindle from the COUPLE command is already listed as a following spindle in MD 37115, this is the source of the conflict.

Machine-level couplings defined in MD take precedence over NC-level COUPLE commands and cannot be overridden during program execution.

Modify the machine data coupling configuration or the NC program to eliminate the cascade. Either remove the conflicting pre-configured coupling from MD 37115 or change the COUPLE command to use a different spindle as the leading member.

After modification, reload the machine data (via HMI > Service > Update Machine Data or warm start) and retrigger the NC block to confirm alarm 22058 no longer occurs.

Review the PLC program logic associated with spindle control (typically in OB 3xx blocks for synchronous actions). Search for COUPLE/DECOUPLE function calls or synchronous spindle assignments that may be triggered automatically when specific spindles are activated.

Check FB blocks related to spindle management; many Siemens systems use function blocks like SYNCH_SPINDLE or vendor-supplied coupling logic.

Enable NCK trace or PLC diagnostic mode to log all COUPLE/DECOUPLE commands executed during the program run. This will reveal whether the PLC is establishing a coupling that conflicts with the NC block's intended coupling.

Use HMI > Diagnosis > Trace to capture NCK function calls and timing of coupling events.