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

100100

Siemens 840D 100100 - Record length reached

Record length reached

Siemens SINUMERIK operator message 100100: Record length reached. This is an informational message from the SINUMERIK control indicating a system status or operation result that may require operator action.

Root Cause Summary

SIEMENS alarm 100100 'Record length %1 reached' occurs when the SINUMERIK system's internal data recording buffer has exceeded its maximum capacity. This typically happens during trace recording, measurement functions, or when diagnostic data collection reaches predefined memory limits in the NCK or HMI subsystems.

Safety

  • Refer to Siemens documentation
  • Ensure qualified technician performs repairs

Causes and Fixes

  1. 1

    Check active trace recordings

    Navigate to Diagnostics > Service > Trace and verify if any trace recordings are currently active or stuck in recording mode.

    Use CTRL+T shortcut to quickly access trace functions

  2. 2

    Clear trace buffer

    Stop all active traces and clear the trace buffer via 'Delete all traces' function in the trace menu.

    Save any required trace data before clearing as this action is irreversible

  3. 3

    Adjust trace parameters

    Check MD11600 TRACE_RECORD_LENGTH and MD11610 TRACE_BUFFER_SIZE settings. Reduce recording duration or increase buffer size if memory permits.

    Set trace trigger conditions more precisely to avoid unnecessary data collection

  4. 4

    Restart NCK if necessary

    If buffer cannot be cleared, perform NCK reset via Startup > Reset > NCK Reset to reinitialize trace subsystem.

DIY Feasiblehigh confidence

Call a technician if:

  • ·Memory hardware issues suspected
  • ·Repeated alarms after all buffer clearing attempts
  • ·NCK fails to restart properly

Prevention

  • Implement automatic trace and log file rotation
  • Monitor memory usage regularly via service displays
  • Set appropriate buffer sizes based on application requirements
  • Establish routine maintenance schedule for clearing diagnostic data

Common Mistakes

  • Ignoring the alarm and continuing operation without clearing buffers
  • Increasing buffer sizes without considering available memory
  • Clearing data without proper backup procedures
  • Not identifying the specific recording function causing the overflow

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.