What causes Siemens SINUMERIK alarm 61360?

CYCLE106 called without required parameters or with null/undefined parameter values. Incorrect parameter data type passed to CYCLE106 (expecting numeric, received string or vice versa). Parameter variable not initialized before CYCLE106 call. Missing or corrupted cycle definition file for CYCLE106. Syntax error in cycle call statement preventing parameter parsing.

How do I fix Siemens SINUMERIK alarm 61360?

1. Review the NC program at the point where CYCLE106 is called and verify all required parameters are explicitly defined and passed with correct syntax 2. Check parameter data types against CYCLE106 documentation to ensure compatibility (INT, REAL, BOOL as applicable) 3. Confirm all parameter variables are initialized with valid values before the CYCLE106 call 4. Verify CYCLE106 cycle file exists in the program directory and is not corrupted; reload from backup if necessary 5. Execute RESET to clear alarm, then single-block step through the cycle call to isolate the exact parameter causing the issue

Siemens SINUMERIK codes

axismd.ai

Siemens SINUMERIK Controller

Servo/Axis · Intermediate · 20-45 minutes

Alarm 61360

Siemens 840D 61360 - Channel Block: Log job undefined - continue with RESET

Alarm triggered by following cycle: CYCLE106. Cycle CYCLE106 was called by an incorrect parameter. Remedy: Check cycle call for CYCLE106, specifically the call parameter.

Siemens SINUMERIKServo/AxisIntermediate20-45 minutes

61360

Siemens 840D 61360 - Channel Block: Log job undefined - continue with RESET

Channel Block: Log job undefined - continue with RESET

Alarm triggered by following cycle: CYCLE106. Cycle CYCLE106 was called by an incorrect parameter. Remedy: Check cycle call for CYCLE106, specifically the call parameter.

Safety

Refer to Siemens documentation
Ensure qualified technician performs repairs

Common Causes

CYCLE106 called without required parameters or with null/undefined parameter values
Incorrect parameter data type passed to CYCLE106 (expecting numeric, received string or vice versa)
Parameter variable not initialized before CYCLE106 call
Missing or corrupted cycle definition file for CYCLE106
Syntax error in cycle call statement preventing parameter parsing

Troubleshooting Steps

1Review the NC program at the point where CYCLE106 is called and verify all required parameters are explicitly defined and passed with correct syntax
2Check parameter data types against CYCLE106 documentation to ensure compatibility (INT, REAL, BOOL as applicable)
3Confirm all parameter variables are initialized with valid values before the CYCLE106 call
4Verify CYCLE106 cycle file exists in the program directory and is not corrupted; reload from backup if necessary
5Execute RESET to clear alarm, then single-block step through the cycle call to isolate the exact parameter causing the issue

Seeing Multiple Alarms?

Seeing another alarm with this one? Enter the code.

Get machine-aware diagnosis

AxisMD logs alarms against your actual machines, tracks patterns, and gives AI context your manual doesn't have.

Start free

Was this guide helpful?

Always verify with your machine manual or a certified technician before performing service procedures.