100106

Check memory status via HMI

Navigate to Diagnostics > Service > Memory and check available space on CF card and internal memory. Minimum 10% free space required.

Use machine data MD11210 $MN_MEMCARD_MEMORY_SIZE to verify CF card capacity

Delete unnecessary files

Access Program Manager > WorkPieces and delete old part programs, backup files (.BAK), and temporary files (.TMP) to free up space.

Always backup critical programs before deletion

Archive programs to external storage

Use Data In/Out function to transfer older programs to USB or network drive, then remove from CF card.

Set up automatic archiving using MD20734 $MC_ARCHIVE_MEMORY_LIMIT

Verify memory allocation

Check MD11200 $MN_MEMCARD_ENABLE and MD11220 $MN_MEMCARD_PART_PROG_MEM settings to ensure proper memory allocation for part programs.

Run CF card diagnostics

Navigate to Diagnostics > Service > Memory > CF Card Test to check for bad sectors and file system integrity.

Backup all data before running diagnostics

Check CF card status LEDs

Observe CF card activity LED on NCU. Continuous red or erratic flashing indicates card issues. Normal operation shows brief green flashes during access.

Monitor DB380.DBX0.0 (CF card ready signal) in PLC diagnostics

Perform file system repair

Use Service > Memory > Repair File System function. This runs CHKDSK equivalent on the CF card to repair minor corruption.

System will restart after repair operation

Replace CF card if necessary

If diagnostics show multiple bad sectors, replace CF card with Siemens-approved industrial grade card. Restore from backup after replacement.

Check file attributes

In Program Manager, right-click the program file and verify Properties. Remove read-only or write-protection attributes if present.

Use MD20110 $MC_WRITE_PROTECTION to check global write protection status

Verify program execution status

Ensure the program being edited is not currently selected for execution. Check NC Start disable and program status in channel diagnostics.

Never edit programs during active machining operations

Close all program editors

Exit all open program editors and file browsers. Check if multiple HMI sessions have the same file open simultaneously.

Monitor DB21.DBX1.0 for program editor active status

Reset file system locks

Perform NCK reset (Power On Reset) to clear any stuck file handles or access locks in the system.

Run NCU memory test

Navigate to Diagnostics > Hardware > NCU > Memory Test to check internal RAM and flash memory integrity.

Memory test requires system restart and may take 10-15 minutes

Check system error logs

Review Diagnostics > Alarms > Alarm Log for hardware-related errors (61xxx series) that may indicate memory subsystem issues.

Look specifically for alarms 61440-61499 indicating NCU hardware faults

Monitor system temperatures

Check NCU temperature readings in Hardware Diagnostics. Overheating can cause memory write failures. Verify cooling fans operation.

NCU should operate below 55°C ambient temperature

Contact Siemens service

If memory tests fail or hardware errors persist, document error patterns and contact Siemens technical support for NCU replacement evaluation.

Verify network connectivity

Check Ethernet connection status in Diagnostics > Communication > Ethernet. Ping network storage server to verify connectivity.

Use MD11410 $MN_NETWORK_DRIVE_ENABLE to check network storage configuration

Refresh network drive mappings

Navigate to Settings > Network Drives and refresh or re-establish connections to mapped network storage locations.

Ensure network credentials are current and valid

Test local save operation

Attempt to save the program locally to CF card first, then copy to network location to isolate network vs. local storage issues.

Monitor DB380.DBX12.0 for network drive ready status