Siemens SINUMERIK codes
Siemens SINUMERIKProgram/G-codeIntermediate30-120 minutes

61356

Siemens 61356 - Block : File for logfile is being used

Block: File for logfile is being used

The log file is already used by an NC program

Root Cause Summary

Alarm 61356 is triggered when CYCLE106 (a Siemens canned cycle for probing/measurement) attempts to write to a logfile that is already open or locked by another NC program or task. This is a file resource conflict in the NCK that prevents simultaneous write access to the specified logfile parameter.

Safety

  • Only qualified personnel should diagnose and clear control alarms; follow the machine builder's safety procedures and lockout/tagout where hardware work is required.

Causes and Fixes

  1. 1

    Access Diagnostics > Parameter > Machine Data (MD) or Startup Data (SD) menu on the control panel. Navigate to MD21090 or search for _PROTNAME[1] parameter.

    Do not modify parameters while programs are running on other channels.

  2. 2

    Note the current logfile path assigned to _PROTNAME[1]. Verify the file location and name (typically in /NC_PRG/LOGFILES/ directory on SINUMERIK 840D).

  3. 3

    Check if the same logfile is referenced in other active NC programs or CYCLE106 calls across multiple channels using program search function in NCK Editor.

  4. 4

    Assign a unique logfile path per channel or program instance by modifying _PROTNAME[1] to include channel-specific identifiers (e.g., _PROTNAME[1] = '/NC_PRG/LOGFILES/LOG_CH%_PROTNAME[0]') or append timestamp variables.

Service Recommended confidence

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.