What causes Siemens SINUMERIK alarm 61361?

Variable data type mismatch - _PROTVAL[] contains incompatible data type for logging operation. Array index out of bounds - specified index in _PROTVAL[] exceeds allocated array size. Variable memory allocation failure - insufficient system memory to record the variable value. Read/write permission conflict - variable is protected or locked during CYCLE105 execution. Uninitialized variable reference - _PROTVAL[] contains null or undefined value at specified index.

How do I fix Siemens SINUMERIK alarm 61361?

1. Verify _PROTVAL[] array dimensions and data types in the active part program and machine parameter settings - confirm variable is properly declared and matches expected logging format 2. Check CYCLE105 invocation syntax and parameter passing - ensure correct array indices are being referenced and no arithmetic errors exist in index calculation 3. Review system memory status and available heap space using diagnostics menu - clear temporary variables or increase work memory allocation if necessary 4. Inspect variable protection settings in NC program and machine parameters - remove any read locks or write restrictions on _PROTVAL[] elements 5. Reset the affected channel and reload the part program - verify alarm clears and variable logging functions normally on subsequent CYCLE105 execution

Siemens SINUMERIK codes

axismd.ai

Siemens SINUMERIK Controller

Servo/Axis · Intermediate · 30-60 minutes

Alarm 61361

Siemens 840D 61361 - Channel Block: Variable cannot be recorded

The alarm is triggerd by the following cycles: CYCLE105. The value specified in _PROTVAL[] cannot be logged. Remedy: Check parameter _PROTVAL[].

Siemens SINUMERIKServo/AxisIntermediate30-60 minutes

61361

Siemens 840D 61361 - Channel Block: Variable cannot be recorded

Channel Block: Variable cannot be recorded

The alarm is triggerd by the following cycles: CYCLE105. The value specified in _PROTVAL[] cannot be logged. Remedy: Check parameter _PROTVAL[].

Safety

Refer to Siemens documentation
Ensure qualified technician performs repairs

Common Causes

Variable data type mismatch - _PROTVAL[] contains incompatible data type for logging operation
Array index out of bounds - specified index in _PROTVAL[] exceeds allocated array size
Variable memory allocation failure - insufficient system memory to record the variable value
Read/write permission conflict - variable is protected or locked during CYCLE105 execution
Uninitialized variable reference - _PROTVAL[] contains null or undefined value at specified index

Troubleshooting Steps

1Verify _PROTVAL[] array dimensions and data types in the active part program and machine parameter settings - confirm variable is properly declared and matches expected logging format
2Check CYCLE105 invocation syntax and parameter passing - ensure correct array indices are being referenced and no arithmetic errors exist in index calculation
3Review system memory status and available heap space using diagnostics menu - clear temporary variables or increase work memory allocation if necessary
4Inspect variable protection settings in NC program and machine parameters - remove any read locks or write restrictions on _PROTVAL[] elements
5Reset the affected channel and reload the part program - verify alarm clears and variable logging functions normally on subsequent CYCLE105 execution

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.