What causes Siemens SINUMERIK alarm 6510?

Parameter or machine data configuration error. Hardware fault on the NC or drive component. Part program error or illegal command. Communication fault between NC and drive or I/O modules. Software or firmware error requiring system restart.

How do I fix Siemens SINUMERIK alarm 6510?

1. Note the complete alarm text including any axis, channel, or block number values. 2. Check for related alarms active simultaneously in the SINUMERIK alarm list. 3. Power cycle the machine to clear transient faults. 4. Review the SINUMERIK machine data for parameters related to the alarm. 5. Consult the Siemens SINUMERIK alarm manual for alarm 6510 detailed remedy.

axismd.ai

Siemens SINUMERIK Controller

Servo/Axis · Intermediate · 30-120 minutes

Alarm 6510

Siemens 840D 6510 - Too many part programs in the NC memory

Alarm 6510 triggers when the NC file system reaches its maximum inode capacity, preventing creation of new part programs, drive data files, or system files in NCK memory. This occurs across all file types managed by the SINUMERIK file system, not just user part programs, and typically manifests during startup or program loading operations.

Siemens SINUMERIKServo/AxisIntermediate30-120 minutes

6510

Siemens 840D 6510 - Too many part programs in the NC memory

Too many part programs in the NC memory

Root Cause Summary

Alarm 6510 triggers when the NC file system reaches its maximum inode capacity, preventing creation of new part programs, drive data files, or system files in NCK memory. This occurs across all file types managed by the SINUMERIK file system, not just user part programs, and typically manifests during startup or program loading operations.

Safety

Refer to Siemens documentation
Ensure qualified technician performs repairs

Causes and Fixes

1
Access the NCK file system via HMI menu: Diagnostics > File Management > NC Programs or via Siemens OPC/DNC interface. Count total .mpf, .spf, .h, and .src files present.
Do not attempt deletion during active CNC cycle; stop all program execution first.
2
Identify and archive obsolete part programs to external storage. Prioritize deletion of backup files (.bak), old revisions, and unused .h header files. Use HMI delete function or FTP to remove files from /nck directory.
Verify file backups exist before deletion; SINUMERIK does not have undelete capability.
3
Perform warm restart (NCK reset without power-down) via HMI: Utilities > System > Warm Start or press NC RESET button. Monitor alarm log to confirm 6510 clears.
4
Establish file management procedure: Monitor NCK file system usage via Diagnostics menu monthly. Set threshold alert when file count exceeds 80% of maximum inode capacity to prevent future occurrences.

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.