125-0072

Access File Manager

Press PGM MGT key, then select 'TNC:\' and navigate to 'system' folder, then 'backup' subfolder to view all existing backup files and their timestamps.

Verify backup file naming

Check SystemLog.txt (TNC:\system\log\SystemLog.txt) to identify exact filename the control is searching for. Compare this with actual files present in backup directory.

The log entry will show the complete path and filename that triggered the alarm, making it easy to identify naming mismatches.

Create new backup file

If backup file is genuinely missing, press MOD key, select 'System Backup', choose 'Create Backup', and save with the expected filename. Ensure proper selection of components (Machine Parameters, PLC, Tool Table, etc.).

Clear alarm and retest

Press CE key to clear alarm. If alarm was triggered by startup routine, power cycle the control to verify successful backup file access.

Check backup path parameters

Press MOD key, select 'Machine Parameters', search for MP7295 (backup file path). Verify the complete path syntax matches actual file location (e.g., TNC:\system\backup\machine.bak).

On iTNC 530 and TNC 620/640, multiple backup parameters may exist for different backup types (machine, system, tool data). Check all related MP729x parameters.

Verify PLC backup calls

If machine uses PLC-triggered backup/restore, access PLC program (MOD > PLC > Edit) and search for backup-related function calls (typically FN17 or OEM-specific functions) that may reference incorrect file paths.

Correct path configuration

Update machine parameter with correct path or comment out automatic restore function if not needed. Ensure path uses proper TNC syntax (TNC:\ prefix for internal storage).

Changing machine parameters requires appropriate password access level. Document original values before making changes.

Test configuration

After correcting path, perform manual backup/restore test via MOD > System Backup to verify control can properly access the configured location.

Check network connectivity

Press MOD key, select 'Network Settings', verify Ethernet connection status shows 'Connected'. Ping the network backup server address to confirm network accessibility.

Use Diagnostic tools in MOD > System Information to verify active network connections and IP configuration.

Verify network drive mapping

In File Manager (PGM MGT), check if network drives are properly mounted. Network paths typically shown as NET:\ or custom mapped drive letters. Attempt to browse to backup location manually.

Test network credentials

Navigate to MOD > Network Settings > SMB Settings. Re-enter username and password for network share access. Test connection by accessing a file on the network share through File Manager.

Network credential changes may affect other network-dependent operations. Coordinate with IT department if necessary.

Configure alternative backup location

If network backup is not critical, update backup path in MP7295 to use local storage (TNC:\system\backup) until network issues are resolved. Create new backup to local location.

Review SystemLog for network errors

Check TNC:\system\log\SystemLog.txt for network timeout or access denied messages that coincide with the alarm timestamp. This will confirm network-related root cause.

Check drive accessibility

Press PGM MGT and attempt to navigate through TNC:\ directory structure. If folders appear empty, show errors, or File Manager responds slowly, this indicates potential file system issues.

Do not perform file system operations while NC programs are running or during active machining operations.