220-0019

Check System Resources

Press MOD key, navigate to System Info menu to view memory usage and active processes. Look for unusually high memory consumption or process counts.

Normal memory usage should be below 80% during typical operation

Close Unnecessary Applications

Exit any non-essential TNC applications like file managers, calculators, or multiple program editors that may be consuming system resources.

Do not force-close machining processes during active operations

Perform Controlled Restart

Execute a controlled TNC restart via MOD > System > Restart to clear memory leaks and reset process handles.

Save all active programs and tool tables before restart

Monitor Resource Usage

After restart, monitor system resources during normal operation to identify if specific operations trigger excessive resource consumption.

Check System Log

Navigate to MOD > Diagnostics > System Log to review recent communication errors or process failures that preceded the alarm.

Look for recurring error patterns or timestamps matching the alarm occurrence

Reset Communication Subsystem

Access MOD > System > Service > Communication and select 'Reset Internal Communication' to reinitialize message queues.

This will temporarily interrupt all internal TNC communications

Verify Queue Status

Use diagnostic menu to check queue status and verify all client queues are properly initialized and accessible.

Queue status should show 'Active' for all critical system processes

Test Communication Functions

Test basic TNC functions like program loading, tool management, and axis communication to verify restored functionality.

Review Boot Sequence Log

Access MOD > Diagnostics > Boot Log to identify any processes that failed to initialize during TNC startup.

Failed processes typically show error codes or timeout messages in the boot log

Restart Failed Processes

Navigate to MOD > System > Process Manager to identify and restart any failed or stopped critical processes.

Only restart processes you can identify as non-critical to machine operation

Check Process Dependencies

Verify that all prerequisite processes and services are running before attempting to restart the failed process.

Process dependencies are typically listed in the Process Manager details view

Perform Cold Boot

If process restart fails, perform a complete TNC cold boot to ensure proper initialization sequence of all system processes.

Check Network Configuration

Navigate to MOD > System > Network Settings to verify IP configuration, subnet masks, and gateway settings are correct.

Document current settings before making any changes

Test Network Connectivity

Use built-in ping utility in MOD > Diagnostics > Network Test to verify basic network connectivity to known hosts.

Ensure network tests don't interfere with active DNC operations

Reset Network Interface

Disable and re-enable the network interface through MOD > System > Network > Interface Control to reset communication queues.

Wait 30 seconds between disable and enable operations

Verify Queue Recreation

Check that network-related communication queues are properly recreated after interface reset using diagnostic tools.