Heidenhain codes
HeidenhainServo/AxisIntermediate30-120 minutes

130-00A4

HEIDENHAIN 130-00A4 - File access not possible

File access not possible

Another application already has the target file open, so the control cannot read or write it. The file is locked by an exclusive handle.

Root Cause Summary

This alarm indicates the TNC operating system encountered a file I/O error preventing read or write operations. The root cause is typically related to storage medium issues (full disk, hardware failure, read-only mount), file permission conflicts, or interrupted network connectivity when accessing remote file systems. The control's Linux-based file system requires proper permissions and healthy storage media for normal operation.

Safety

  • Refer to Heidenhain service manual
  • Ensure qualified technician performs repairs

Causes and Fixes

  1. 1

    Check available disk space

    Press MOD key → select 'File Management' → check the status bar at bottom of screen showing free space on TNC:\ drive. Verify at least 100 MB free space is available.

    The TNC requires free space not just for new files but also for temporary files during program execution and system logging. Aim for 10-15% free space minimum.

  2. 2

    Delete unnecessary files

    Navigate to TNC:\temp\ and TNC:\log\ directories and delete old log files, backup files (.bak), and temporary files. Also check TNC:\nc_prog\ for outdated programs.

    Use the 'File Info' function (soft key) to sort by date or size to identify large or old files for deletion.

  3. 3

    Check write protection

    In File Manager, select the file or directory and press 'File Info' soft key. Check if 'Read Only' attribute is set. If so, use 'Change Attributes' soft key to remove write protection.

    Do not remove write protection from system files in TNC:\system\ unless specifically instructed by service documentation.

  4. 4

    Verify CF card physical lock

    If alarm persists, power down control and check if CF card has physical write-protect switch in locked position. Move switch to unlocked position if needed.

    Always perform a controlled shutdown via MOD → Shut Down before powering off to prevent file system corruption.

DIY Feasiblehigh confidence

Call a technician if:

  • ·File system corruption detected
  • ·Network infrastructure issues
  • ·Repeated alarms after following all steps

Prevention

  • Establish file access protocols for networked systems
  • Regular backup of critical files to prevent corruption
  • Coordinate tool table access between operators and programmers
  • Monitor network drive connectivity status

Common Mistakes

  • Forcing file operations while background processes are running
  • Not checking all channels in multi-channel systems
  • Interrupting system backup operations
  • Ignoring network connectivity status indicators

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.